Well, there was a lot of chatter today about the speed increases on cyanogen's JF-1.51 ROM today, attributed to some changes in the ramdisk (see below). Attached is a boot.img with the same modifications but for Haykuro's 6.0r1 build - go ahead and download it now or read on for more details. Note: you'll only notice a difference if you run your apps/cache from your SD card.
The Changes
The only change is to mount your SD card's ext2 partition with the 'noatime' option. This is exactly what cyanogen did in his JF build, as per his post here. I also added the 'nodiratime' option. This is merely a very minor change in the runme.sh script of the boot ramdisk. [See below for more info on the ext3 mod, added 05/27/09]
By default, ext2 maintains the last access time ('atime') of every file and directory in the filesystem. This means that every time you access (read or write to) a file, this time will be reset and you'll be writing to your SD card. Two problems: 1) SD cards are slow as it is; requiring a write every time you access a file is going slow your whole system down. 2) SD cards fail after enough writes to the same location, so you're reducing your card lifetime by not having these options.
ext3 'auto' mod
Cyanogen added this to his latest build, so again, merely making this available for Haykuro 6.0r1 users. He wrote a bit more detail here which is working reading too.
In short: No other ROMs or app2sd solutions handle a clean shutdown of the ext2 partition, and Android doesn't have fsck tools. The result is that shutting down or crashing can corrupt your ext2 partition and you can lose data. Meanwhile, ext3 is a journaling file system; it recovers gracefully from unclean shutdowns. It's also backwards compatible, you can still mount an ext3 as ext2, you just lose journaling capability.
The mod mounts the 2nd SD partition as type 'auto', which means it will read your existing partition as ext2 and in the future as ext3 if you upgrade. This is more for advanced users but I'll try post some simple instructions below. Make sure you download the boot-haykuro-6.0r1-atime-ext3.zip image.
What about hero? (added 06/06/09)
This is a modded kernel 2.6.29 with unionfs support from daproy. Besides the atime+ext3 stuff, by request I also added support to run /system/init.rc and /data/init.rc (needed by some scripts).
http://turtle.wastelands.net/dragon/...uto-initrc.zip
See also:
1) Daproy's release: http://forum.xda-developers.com/showthread.php?p=3905574#post3905574
2) Release in this thread: http://forum.xda-developers.com/showpost.php?p=3909682&postcount=10
Note: you also need to
1) adb remount
2) push wlan.ko /system/lib/modules
How to apply
Download and unzip the file to get your new boot.img
Option 1:
Code:
adb push boot.img /sdcard
adb shell
# cat /dev/zero > /dev/mtd/mtd2 write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/boot.img
(or mount your SD card, copy the image, and run the above commands in a terminal).
Option 2:
1. Boot into fastboot mode (boot with power+camera)
2. fastboot flash boot boot.img
How to check if it's working
Type 'mount' in an adb shell or your phone's terminal, and look for the 'noatime' and 'nodiratime' option on your ext2 mount point. (If you go ahead with the ext3 mod and upgrade, you'll see it will show up as ext3 in the mount list below).
Code:
$ adb shell
# 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/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext2 rw,[b]noatime,nodiratime[/b],errors=continue 0 0 <--
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8 0 0
If things go wrong
If for some reason you can't boot after trying this, you can restore your system simply by reapplying Haykuro's image (boot with power+home and alt-s). Alternatively, I'm attaching the original boot.img as well, which you could reflash with option 2 above.
How to upgrade your ext2 partition to an ext3
I found this really easy on Linux. People can write about alternative methods, but this worked great for me: (substitute /dev/sdb2 below as necessary)
1. Connect to USB and mount your SD card in Android
2. Unmount your ext2 partition from inside linux (e.g. sudo umount /dev/sdb2)
3. sudo tune2fs -j /dev/sdb2 (this adds a journal to the filesystem)
4. adb shell, reboot (or just reboot phone without tapping 'turn off USB storage')
Even though I found this really simple and didn't even bother to make a back up first, I'm really familiar with Linux and linux filesystems -- this should be considered advanced use, and I'm not responsible for you losing your entire ext3 partition.
Note - I agree with cyanogen; I don't think the journal writes is a big performance impact or will wear out your card. This is a relatively small amount of extra data on each write... very low performance/wear impact and for me very worth the benefits.
References
1. Original launch thread of cyanogen's JF 1.51 build
2. Boot Image how to referenced by cyanogen's post
I'm also attaching my compiled versions of mkbootfs and mkbootimg in case anyone wants to play around without downloading and compiling the 2.3 GB Android source.
Worked like a charm thanks man!
This worked perfectly for me! Great job on this; noticable speed improvements for me
Not a great improvement.. Apps are starting circa a second faster..
anyone try this or have a method for Haykuro's Hero build?
boot.img for JACHero r1.4
jroid said:
anyone try this or have a method for Haykuro's Hero build?
Click to expand...
Click to collapse
Which build? I think beta 4 is out yes? I haven't moved over to Hero yet because of the bluetooth issue. Nevertheless, I just made a boot.img for JACHero1.4 - it's untested, but can't imagine it giving any problems... you can always just reapply the update.zip if things go wrong (I still take no responsibility though ). It will probably work with the recent hero builds, let me know how it goes.
I was reffering to the official build he dropped w/ rosie.
thanx I'll give it a shot
confirmed. works on hero build.
very noticeable speed improvement. thanks
# cat /dev/zero > /dev/mtd/mtd2 write: No space left on device
cat /dev/zero > /dev/mtd/mtd2 write: No space left on device
write: No space left on device
# flash_image boot /sdcard/boot.img
flash_image boot /sdcard/boot.img
# mount
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/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8 0 0
# reboot
reboot
C:\>adb shell
# mount
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/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8 0 0
#
Click to expand...
Click to collapse
confirmation #2 it works on hero w/ Rosie
From another thread:
http://forum.xda-developers.com/showpost.php?p=3905574&postcount=42
daproy said:
Ok I reverted the recent commits to the 2.6.29 tree and camera works fine again and I patched in UnionFS. Sorry for the mess guys. I guess it shows I should have tested it before uploading. I put the kernel zImage in there separate as well in case people wanted to make their own boot.img
http://drop.io/tgbvqky
Click to expand...
Click to collapse
For those that were asking, here are some mods to daproy's great work.
* Mounts the 2nd partition as type 'auto' - ext3 if u have it, else ext2.
* Mounts with noatime and nodiratime options
* Includes appropriate calls to /system/init.rc and /data/init.rc
http://turtle.wastelands.net/dragon/android/hero-boot-unionfs-2-atime-auto-initrc.zip
Kinslayer81 said:
From another thread:
http://forum.xda-developers.com/showpost.php?p=3905574&postcount=42
For those that were asking, here are some mods to daproy's great work.
* Mounts the 2nd partition as type 'auto' - ext3 if u have it, else ext2.
* Mounts with noatime and nodiratime options
* Includes appropriate calls to /system/init.rc and /data/init.rc
http://turtle.wastelands.net/dragon/android/hero-boot-unionfs-2-atime-auto-initrc.zip
Click to expand...
Click to collapse
Hey thanks for the new kernel package.
Simple question.
I had now problem fastbooting the boot.img or adb pushing the wlan.ko but what do I do with the kernel file? Anything, or is it just there in case I want to make changes to the boot or wlan.ko files?
Ext3 on flash media drastically reduces the lifetime because of the frequent writes to the journal, a simple search on google brings up tons of things against the idea, yaffs2 or jffs would be a better decision because it is optimized for flash media and has a journal, not everyone has a class 6 sdhc, and ext3 will cause curruption in any lower class sd, and it will reduce a class's lifetime as well, there is plenty of docs and specs on this, if u prefer speed over reliability/sd lifetime have fun
defconoi said:
Ext3 on flash media drastically reduces the lifetime because of the frequent writes to the journal, a simple search on google brings up tons of things against the idea, yaffs2 or jffs would be a better decision because it is optimized for flash media and has a journal, not everyone has a class 6 sdhc, and ext3 will cause curruption in any lower class sd, and it will reduce a class's lifetime as well, there is plenty of docs and specs on this, if u prefer speed over reliability/sd lifetime have fun
Click to expand...
Click to collapse
This has been discussed ad nauseam.
Even in average high use (compiling the linux kernel!), ext3/journalling with the noatime option results in LESS THAN A 4% INCREASE IN WRITES. Even an abnormal case ('make clean' on the linux kernel, i.e. deleting literally thousands of files) maxed out at a 40% increase, which for deletes really isn't such a big deal. http://thunk.org/tytso/blog/2009/03/01/ssds-journaling-and-noatimerelatime/
Yaffs2, etc, ARE WORSE FOR YOUR SD CARD, which implements it's own hardware anti wear levelling. If you have the hardware and software both swapping around locations, you're doing more work, making things slower, and shortening the life of your card. Flash file systems are contra indicated for SD and other such media.
And it's not about preferring speed over reliability. Ext3 will be slightly slower than ext2, but it's definitely more reliable, because when you shut down, your phone crashes or something else goes wrong, it can recover gracefully instead of YOUR EXT2 PARTITION BECOMING CORRUPT and you losing your data.
I hope this issue is closed now.
ccyrowski said:
Hey thanks for the new kernel package.
Simple question.
I had now problem fastbooting the boot.img or adb pushing the wlan.ko but what do I do with the kernel file? Anything, or is it just there in case I want to make changes to the boot or wlan.ko files?
Click to expand...
Click to collapse
Yea I did the steps with the boot.img and wlan.ko and it appears to be working (noatime and nodiratime are showing). But whats the deal with the kernal file?
sacredsoul said:
Yea I did the steps with the boot.img and wlan.ko and it appears to be working (noatime and nodiratime are showing). But whats the deal with the kernal file?
Click to expand...
Click to collapse
It was included by daproy for ROM developers. I just left it in there to provide the complete package. You can safely ignore it
Kinslayer81 said:
It was included by daproy for ROM developers. I just left it in there to provide the complete package. You can safely ignore it
Click to expand...
Click to collapse
Ah. Thanks man! Enjoying my speedy JACHero Optimized build with this boot.img.
i pushed the wlan and use fastboot to flash the boot.img but when i check with the "mount" command it shows :
i'm using Jac's ROM
/dev/block/mmcblk0p2 /systemsd ext2 rw,errors=continue 00
instead of this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0
I get a wifi unable to start.
ifconfig tiwlan0 in Terminal returns No such device. Any help guys? Yes I tried rebooting already.
EDIT: Posted this on JACHero thread too. Posting here to get more response...
adb remount
adb push wlan.ko /system/lib/modules
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Shanker>cd C:\android-sdk-windows-1.5_r1\tools
C:\android-sdk-windows-1.5_r1\tools>adb remount
remount succeeded
C:\android-sdk-windows-1.5_r1\tools>adb push wlan.ko /system/lib/modules
1117 KB/s (676043 bytes in 0.591s)
C:\android-sdk-windows-1.5_r1\tools>
Click to expand...
Click to collapse
I rebooted and I still cant start wifi. Btw I am using the kinslayer81 boot.img for JACHero 1.4...
namsir said:
i pushed the wlan and use fastboot to flash the boot.img but when i check with the "mount" command it shows :
i'm using Jac's ROM
/dev/block/mmcblk0p2 /systemsd ext2 rw,errors=continue 00
instead of this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0
Click to expand...
Click to collapse
i got the samething.... when i check to see if its working with "mount"
it doesnt show the noatime, nodiratime :\
Kinslayer81 said:
From another thread:
http://forum.xda-developers.com/showpost.php?p=3905574&postcount=42
For those that were asking, here are some mods to daproy's great work.
* Mounts the 2nd partition as type 'auto' - ext3 if u have it, else ext2.
* Mounts with noatime and nodiratime options
* Includes appropriate calls to /system/init.rc and /data/init.rc
http://turtle.wastelands.net/dragon/android/hero-boot-unionfs-2-atime-auto-initrc.zip
Click to expand...
Click to collapse
can we do aufs/unionFS on Haykuro's original hero build? I've got the new boot.img and wlan.ko and ext3 FS, just wondering what I would need to do.
htc one s tmobile us
I have bootloader and fastboot unlocked
I have recovery (official cwr touch) and adb functionality
I have ROM and adb functionality
Its the first build of cm9 without 1. sdcard mount 2. USB_lun0 3 mobile access or 4 wifi. I know... pretty ****ty place to be. But it is what it is
I've been trying to 1 create symlink between system and sdcard and then mount it.... so I can push a ROM to it and then flash it...or so I can push my backup file back in it and then mount with clockwork and restore... I even tried pushing a modaco ROM to /data/ and then try "recovery --update_image /data/mod.zip" but of course cwr isn't amon-ra and will not allow for flashing from anyplace but sdcard
I can write **** to sdcard....I just cannot get it mounted in recovery or Usb .I wiped my sdcard from fastboot "clear storage" and have tried many things. But that's irrelevant because do have my original Nannie saved to my computer...
I can write/push/files to sdcard... I just cant get the phone to see it.
I need help to 1 access sdcard and boot a normal ROM or 2 fastboot a Nannie back in but that's not possible without plain .img files or 2 somehow boot a ROM from a partition I can see...
I've tried many many things. I can remount it gives me rw when I remount... but the phone or the computer cannot see this...yet.
I even tried RUUing the euro version and of course that failed. I just need to flash a different ROM and the trick is getting the phone or recovery to mount sdcard.
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Fire\tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT24HWxxxxx recovery
C:\Fire\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb remount
* daemon not running. starting it now *
* daemon started successfully *
remount failed: Success
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nodev,noatime,nodiratime,user_xattr,barrier
=1,data=ordered 0 0
~ # # echo 1 > /sys/class/usb_composite/rndis/enable
# echo 1 > /sys/class/usb_composite/rndis/enable
~ # # echo 0 > /sys/class/usb_composite/rndis/enable
# echo 0 > /sys/class/usb_composite/rndis/enable
~ # # echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
~ # # echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
~ # ls
ls
boot
cache
data
datadata
default.prop
dev
devlog
emmc
etc
init
init.rc
internal_sdcard
mtdcache
proc
res
root
sbin
sd-ext
sdcard
sys
system
tmp
~ # cd sdcard
cd sdcard
/sdcard # ls
ls
mod.zip
/sdcard # recovery --flash_update mod.zip
recovery --flash_update mod.zip
sh: /sbin/postrecoveryboot.sh: not found
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Fire\tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT24HW408152 recovery
C:\Fire\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb remount
* daemon not running. starting it now *
* daemon started successfully *
remount failed: Success
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nodev,noatime,nodiratime,user_xattr,barrier
=1,data=ordered 0 0
~ # # echo 1 > /sys/class/usb_composite/rndis/enable
# echo 1 > /sys/class/usb_composite/rndis/enable
~ # # echo 0 > /sys/class/usb_composite/rndis/enable
# echo 0 > /sys/class/usb_composite/rndis/enable
~ # # echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
~ # # echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
~ # ls
ls
boot
cache
data
datadata
default.prop
dev
devlog
emmc
etc
init
init.rc
internal_sdcard
mtdcache
proc
res
root
sbin
sd-ext
sdcard
sys
system
tmp
~ # cd sdcard
cd sdcard
/sdcard # ls
ls
mod.zip
/sdcard # recovery --flash_update mod.zip
recovery --flash_update mod.zip
sh: /sbin/postrecoveryboot.sh: not found
recovery --flash_update mod.zip
recovery --flash_update mod.zip
exit
exit
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount /sdcard
mount /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0 /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0 /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mmcblk /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2/dev/block/mmcblk /sdcard
mount -o rw,remount -t yaffs2/dev/block/mmcblk /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount -o rw,remount -t yaffs2/dev/block/mmcblk0 /sdcard
mount -o rw,remount -t yaffs2/dev/block/mmcblk0 /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount -o rw,remount
mount -o rw,remount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nodev,noatime,nodiratime,user_xattr,barrier
=1,data=ordered 0 0
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34 /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34 /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34
~ #
Sent from my Amazon Kindle Fire using xda premium
maybe you should use code tags in the future to distinguish it from normal text. your post is a little bit confusing because of it's length ...
now to your issue:
boot into cwr
select "mounts and storage" -> "mount /sdcard"
now you can push files to /sdcard/
adb push rom.zip /sdcard/
I get Error to mount sdcard when I try to get CWR to get a file off sdcard
and when I try to mount usb -
Error - no ums_lunfile found
Sorry for being so verbose and wordy, the problem is simple, cant mount, cant get to usb.
Trying to create symlink but I dont see a vold file in here... so I am trying to make one...
this blows -----
only thing left for me to do is wait for RUU or find a boot.img and a system.img to fastboot in.
is there anyway to convert the cwr ext4 backups into .img's?
or is there definitely NO way to flash a ROM from /data/ or other partition in clockwork? any other recoveries for the htc one s? amon?
this blows!! if I can find a usable vold.fstab to use or some way to mount sdcard in recovery I would be all set!! but theres no way to mount sdcard or even ums_lunfile.
Will have to either figure something out but I would appreciate direction. thanks.
im on gtalk at joshcues
Can you boot into the os? If you can have you tried automount from the market. No experience with a phone with no external sdcard yet so i don't know if that will help at all tbh. My wife just got one so i guess I'll be learning now
automount just saves you a couple steps when you plug the device into the computer -- so you dont have to enable usb mount..although i am now trying a bunch of apps.
Yes I can boot into OS -- ive been trying different vold files... no luck so far. I can install any app I want, Ive been using stericsons Remount and Android Root Toolkit Beta https://play.google.com/store/apps/details?id=sa.root.toolkit&feature=search_result to quickly remount rootfs as rw... but it never sticks -- still, they are helpful... at least i have full adb control and am able to play with droid explorer because i am all adb'ed out for now.
if only I could at least enable wifi or get the radio going.. i would be fine with the phone without a sdcard... its kind of funny... but yes i can boot into OS, but
androidcues said:
or is there definitely NO way to flash a ROM from /data/ or other partition in clockwork?
Click to expand...
Click to collapse
did you try to make a link from /sdcard to /data/sdcard/?
mkdir /data/sdcard
ln -s /data/sdcard/ /sdcard/
if that does not work it would be interresting to know what your friend did to the device. have you tried to manually mount the sdcard?
[URL="http://pastebin.com/UMtJK88h"][URL="http://pastebin.com/xBH4Wge3"]http://pastebin.com/YUsCQsrf[/URL][/URL]
Ive got data/sdcard symlink set up and mounted. But recovery cannot flash or restore from data/sdcard. The first time I had the regular mnt/sdcard that I restored from.... but this time I cannot find mnt/sdcard.
Made link to /system/sdcard but cant make it pop up in recovery...
All thats left for me is to find either the fresh rom waiting to be flashed OR the two backups waiting to be restored that reside on sdcard. So, the last thing to do is to get sdcard to freaking pop up in clockwork recovery.
i got somewhere... but not quite at the finish line. Any suggestions? do I need to rebuild the sdcard file system from scratch? Will check back sometime this week... but golly...
jodue said:
did you try to make a link from /sdcard to /data/sdcard/?
mkdir /data/sdcard
ln -s /data/sdcard/ /sdcard/
if that does not work it would be interresting to know what your friend did to the device. have you tried to manually mount the sdcard?
Click to expand...
Click to collapse
I am now able to see sdcard from the phone using file manager and adb -- there is a /data/sdcard/ now that is read write and has a nandroid waiting for me as well as a fresh modaco.zip rom
However I still cannot mount sdcard manually and when I get to recovery it is looking for sdcard in /mnt/sdcard/ not /data/sdcard/
androidcues said:
I am now able to see sdcard from the phone using file manager and adb -- there is a /data/sdcard/ now that is read write and has a nandroid waiting for me as well as a fresh modaco.zip rom
However I still cannot mount sdcard manually and when I get to recovery it is looking for sdcard in /mnt/sdcard/ not /data/sdcard/
Click to expand...
Click to collapse
as i said before ... why don't you just make a link /sdcard that points to /data/sdcard ?
ln -s /data/sdcard /sdcard
how would you do that? can I create a link using adb? I'm in the same situation except that I formatted my system folder because I had no idea mounting wouldn't work (I"m coming from a different phone).
Thanks in advance.
I tried to create a link using
Code:
adb shell
ln -s /data/sdcard /sdcard
no luck. any other idea?
jodue - I can (and have) link I can see sdcard file (with a modaco rom zip waiting on it, as well as clockwork/backup/2012-5-1xxxx) from the following links -
/data/sdcard
/system/sdcard
i sometimes have them written as mnt/sdcard but they never survive a boot.
I unable to mount sdcard in recovery using either or both of those links
I do not (yet) know how to manually add a ums_lunfile to a ROM that does not yet have it incorporated.
I have played with the permissions, looking at my other devices and seeing how other versions of ROMs have different permissions on the same app I am missing a vital switch that will allow Clockworkmod to see the sdcard. The phone may not be seeing the sdcard but it is definitely there, but cant I try to create a link between the Recovery and the sdcard?
I have messed with the vold.fstab and build.prop files in many many different ways (always restoring to default files after each attempt)
I do not (yet) know how to enable wifi on a ROM that does not yet have it incorporated.
I do not (yet) know how to enable bluetooth on ROM that does not yet have it incorporated.
I do not (yet) know how to enable the mobile connection on a ROM that does not yet have it incorporated.
So either I am going to figure out the top three items, or I am going to figure out how to mount my sdcard or have Clockworkmod recognize my SDcard so it can simply 1. restore back to normal or 2. flash a proper zip file.
It is like this phone is on perpetual vacation unless a number of things happen.... kind of funny...Id really like to fix it before the RUU comes out because once it does.. thatll be a lot of searching (Im now trying the Bing search engine because Google didnt find the answer) for nothing!
LuckyMethod said:
I tried to create a link using
Code:
adb shell
ln -s /data/sdcard /sdcard
no luck. any other idea?
Click to expand...
Click to collapse
did you mount and as root?
it's probably the best and simplest solution for you guys to reflash with a stock RUU. i am sure that it's possible to restore a backup from the state you are in however it's hard without actually having the device in front of me ^^
good luck!
bored of waiting for ruu -- another effort
allrighty just logging some more efforts to my morbid problem - the goal was to boot into recovery and then mount..
mount /dev/block/mmcblk0p36 (36 wasnt there, tonight it was mmcblk0p34) /sdcard
or
mount -o bind /data /sdcard
i was able to make both succeed (in recovery) but clockwork did not agree, so thus unable to mount sdcard in recovery so I could restore or flash a proper rom.
I then tried flashing diff recoveries... to eliminate the off chance that it was a problem with particular cwm builds... i flashed stock recovery and then tried to make it flash rom from "internal" storage but of course HTC has that stock recovery looking for very specific files... so my "update.zip" went nowhere (pushed to both /data and /system as im not surre where it flashes from....
then i tried the modaco unofficial cwm nontouch recovery -- that did not want to mount...
then i tried the official cwm nontouch 5831 recovery (the touch recoveries take up space and I cant see the logfile in those)
i think i got somewhere with the mounting in recovery -- i wasted too much time trying to mount in runtime (upon boot) --
next ideas or where shall I go from here? Im not done by any means... anyone happen to know exactly what file the STOCK recovery is looking for when it tries to "flash update from internal storage"
any ideas, i will try. Heres a bunch of pastebins...http://pastebin.com/eTJuJuy9 and http://pastebin.com/0vUdaLvB and http://pastebin.com/qUSJMLpn and http://pastebin.com/fGkHzgbw and i am going to try some more on my windoze 8 system at home because the usb twatholes on this machine are pretty much unreliable.
steps -- I could find out if my mounting and binding needs more followup, I could find a system.img to fastboot I could find a way to flash from /data I could find a way to freaking mount another external drive I could pray like crazy that AmonRa gets a HTC One S and puts his flashable-from-anyplace-other-than-sdcard awesomeness on it....but thats about as crazy as the thought of a HTC guy dropping in here and asking me if I would mind testing his RUU.
cheers and thanks for whatever ideas you have no matter how crazy they sound. Waiting for a RUU is about as much fun as waiting for water to boil.
this is resolved.
lesson to be learned -- flashing an alpha build of a "work in progress" rom without the ability or proper OS to create your own .img files is going to 1. break things 2. cause silly threads like this, 3. force you to learn a lot more about android file systems and 4. wait for a RUU that may never come
xkonni was so kind to make me an updated system.img and accompanying boot.img from which I flashed through fastboot and then that was that.
htc sense makes no sense... but it makes no sense to recklessly flash files without reading the thread itself!! although I am just overjoyed I dont have to see sense again!
hey,
i have the identical problem and i am trying hard to solve this. but till now, i wasnt´t successfull. Is it possible that i use the files? It seems worth a try.
thx
---------- Post added at 11:44 PM ---------- Previous post was at 11:13 PM ----------
i now see that it is impossible to resore any nandroid backup in recovery, because CW doesnt find the sd-card, mounting and usb mounting doesnt´t work,too.
but the crazy thing is: after formating the sd-card i have access in windows but still not in recovery
So, let me get this straight --
You had this same issue -- could not get clockwork to see sdcard much less mount it or access sdcard?
When you were in Android you could not see sdcard or system would not see sdcard?
When you were in ADB you could see sdcard and mount it but it would never stay mounted? Did you try #mount -o bind? did you try to create link to sdcard? (of course did you mount as read/write first?) If so, let me know
You PM'd me and told me about a successful RUU you found that solved it... thats great -- but do you know why trhe problem happened in the first place?
The first time.. it was probably because I flashed a total alpha rom and shouldnt have...
but now.. it happened after I was already established..
I dont know why it happened.... I just know how to get out of it. Last night I got the flash itch and wanted to see what MIUI was up to and once again I ventured out into miui and once again I got bit hard. All of a sudden (I may have accidentially erased sdcard from one of those settings or wiped it) I could not see sdcard.... so i boot into clockwork and lo and behold.. clockwork was up to its old tricks of "cant mount sdcard!!!" and "no umslun0file!!!!" so I was like wow, whats going on?
I want to know WHY this is happening... the "fix" is there, but i dont know why this is happening.
Two things -- 1. This kind of problem has existed but most devices have removable sdcards. so its easy to give up and get a new sdcard.. etc... (problem doesnt get solved it gets trashed) but now... this problem needs to be resolved.. is there a defect? if so.. then how can we resolve these defects without having to replace the entire phone?
partitioning
yesterday... while in CM9... I decided that I wanted to try a repartition. So i pull all files from sdcard onto my desktop. Then I tried to format sdcard with Windows 8. Bizarre thing -- the computer could mount sdcard and all.. but then I got an error when I tried to do a simple format with Windows it wouldnt do it... I shrugged and booted into recovery and had clockwork do the partition...
i set my partition limits and then it proceeded to partition.. but it was "finished partitioning" less than 2 seconds later. I thought that was odd it should take at least a few moments. So maybe Clockwork could not partition or it did not? I dont know yet.
What benefit do phones with built in solid state drives or nonremovable sdcards have? Whats the point? I never had an issue with any of the dozens of sdcards -- some failed, but i simply got a new one or fixed it.