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.
Related
Ok, so I was trying to reflash the modified rc30 update to start from scratch because when trying to do the auto rotate browser tweak I kept getting the not enough space message. I rebooted into recovery mode thinking all I had to do was run the update and it didn't do it. I thought maybe I needed to reflash the modified recovery image so I did that, but now when I reboot into recovery mode I get the G1 logo and then a blank screen. I tried pushing home+back to restart and get nothing. So I used adb to push the recovery image on the device and I get "no space left on device" Tried doing a factory reset and it hangs up on a blank screen there too. can I just wipe the data partition to fix it then reflash the recovery image to the device? The phone works fine, I just can't do anything with recovery. Can someone help me out here in getting back recovery mode? Thanks
When you tried to push the recovery image, did you do so to the sdcard?
I am referencing these pages:
http://android-dls.com/wiki/index.php?title=Keeping_Root
http://code.google.com/android/reference/adb.html
Just remount /system as rw and adb push the recovery.img directly in. Also, if you have the engineering bootloader installed, you could try using fastboot to reflash the recovery partition from the bootloader.
doesn't mount -o remount,rw /dev/block/mtdblock3 /system remount the system as rw? That's what i've been doing, and still says device full. I went in and tried by putting the file on the sd card and then flashing it but get the same message. I don't have the engineering bootloader yet that was next on my list. Is there a way to see what is on my partition so I can remove things to free up space?
jdwme said:
doesn't mount -o remount,rw /dev/block/mtdblock3 /system remount the system as rw? That's what i've been doing, and still says device full. I went in and tried by putting the file on the sd card and then flashing it but get the same message. I don't have the engineering bootloader yet that was next on my list. Is there a way to see what is on my partition so I can remove things to free up space?
Click to expand...
Click to collapse
If you're on RC30 v1.2 put the recovery.img in /data not /system
so then my it should look like this?
mount -o remount,rw /dev/block/mtdblock3 /data
cd /data
cat /sdcard/recovery_testkeys.img > recovery.img
flash_image recovery recovery.img
jdwme said:
so then my it should look like this?
mount -o remount,rw /dev/block/mtdblock3 /data
cd /data
cat /sdcard/recovery_testkeys.img > recovery.img
flash_image recovery recovery.img
Click to expand...
Click to collapse
mtd3 is system. mtd5 is userdata. Don't execute that first step! userdata partition is rw anyway. Just start with step 2.
ok, i did execute the first step in the terminal emulator, is that bad? i will try it now starting with just cd /data
jdwme said:
ok, i did execute the first step in the terminal emulator, is that bad? i will try it now starting with just cd /data
Click to expand...
Click to collapse
Not sure. What do you get if you type mount with no args in the terminal emu?
nothing, it just goes to the next line and lets me enter in the next step. is there a way to flash from the standard bootloader?
jdwme said:
nothing, it just goes to the next line and lets me enter in the next step. is there a way to flash from the standard bootloader?
Click to expand...
Click to collapse
Really? What it should do is return a list of mounted devices, like so (this is a Mod RC30 v1.2 device):
Code:
# mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/loop0 on /system/modules type cramfs (ro)
/dev/block/loop1 on /system/xbin type cramfs (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8)
Stock bootloader can't be used to flash images to the mtd partitions.
ok i misunderstood, i did type just mount now and it shows what you posted. could i have two modified recovery images on there and it cant pick one so thats causing the problem?
Did you change directory to /data? If you can't get it to work from the terminal, as long as you have the recovery.img in /data, just power the G1 off completely and power it back on. It automatically writes the recovery partition every time you cold boot.
Btw make sure that in the mount report the following two lines read exactly as such:
Code:
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
yeah the mount report shows just that. i have cold rebooted everytime i tried to flash, then powered off and tried to boot back up in recovery mode and it doesnt work, gives the g1 logo then screen is black.
jdwme said:
yeah the mount report shows just that. i have cold rebooted everytime i tried to flash, then powered off and tried to boot back up in recovery mode and it doesnt work, gives the g1 logo then screen is black.
Click to expand...
Click to collapse
On your cold reboots were you seeing the flashing screen (arrow onto chip) before booting into Android?
nope, only showed that when i was able to upgrade to modified rc 30 or run the update in recovery mode
jdwme said:
nope, only showed that when i was able to upgrade to modified rc 30 or run the update in recovery mode
Click to expand...
Click to collapse
Are you sure you have the recovery.img in the /data directory? Strange. Maybe someone else has some ideas about whats going on here?
So I decided to show all my partitions listed on the system using cat
/proc/partitions and this is what I got. Does this look normal? Not sure
what it looks like on anyone else device
major minor #blocks name
7 0 2248 loop0
7 1 3176 loop1
31 0 256 mtdblock0
31 1 5120 mtdblock1
31 2 2560 mtdblock2
31 3 69120 mtdblock3
31 4 69120 mtdblock4
31 5 76544 mtdblock5
179 0 7977472 mmcblk0
179 1 7973376 mmcblk0p1
I pushed it to the data directory before, followed the instruction thread, but using oi file manager recovery.omg shows in system, nothing shows in data
so does anyone have any ideas? I was thinking about going back to rc29 to try and fix this but without being able to get recovery mode to come on I can't do it, I also can't flash over to the dev boot loader
jdwme said:
so does anyone have any ideas? I was thinking about going back to rc29 to try and fix this but without being able to get recovery mode to come on I can't do it, I also can't flash over to the dev boot loader
Click to expand...
Click to collapse
Give me an IM if you want. I may be able to help fix your recovery mode. (debugging things like that is such a pain on a forum. real-time is much easier)
i know theres a thread but i'm confuse about what to install and run to transfer my apps to my sd card.
my sd card is already partitioned to 6gb fat32 and 2gb ext2 and its rooted with jf1.41 as well.
please give me a specific instructions cuz im a noob when it comes to adb shell sdk cmd or whatever computer words.
thanks in advance!
Well i'm a noob as well can't seam to finish the last step myself but i'll try my best.
Just a wild gues u r running Windows right?
yeah im using windows xp but it has vista transformation pack if that will make a difference.
Ok.
Have u got "modified mountd & init.zip (685 Bytes, 475 views)" wich is an attachement at the bottom of http://forum.xda-developers.com/showthread.php?t=468959 ???
Download this small zip from http://modmygphone.com/wiki/index.php/Setting_up_ADB . Unzip the files to a desktop and copy it to system folder after that follow this link http://www.computerhope.com/issues/ch000549.htm.
let me know when u r done???
But remember i am also a big time noob but just trying to help as much as i can when no one else will so if i get some thing wrong don't get angry with me just let me know what i told u that was wrong and that way we can help each other out and correct one n other.
Zionator said:
But remember i am also a big time noob but just trying to help as much as i can when no one else will so if i get some thing wrong don't get angry with me just let me know what i told u that was wrong and that way we can help each other out and correct one n other.
Click to expand...
Click to collapse
if you copy the modified mount.conf and init.rc files to the SD card at the root then this would be the way in "Terminal":
$su
#busybox cp -a /sdcard/mount.conf /system/etc/mount.conf
#busybox cp -a /sdcard/init.rc /system/init.rc
#mkdir /system/sd
now that the modified files are there you MUST reboot .. this is all done after you have root and after you have done the double partitions on your SD card .. once you reboot you should go back to the "Terminal" to make sure everything's good
$su
#busybox df -h
if you don't see a line like this:
/dev/mmcblk0p2 1.5G 94.4M 1.3G 7% /system/sd
then something didn't mount properly .. so if you DO see this line now you can continue:
#busybox cp -a /data/app /system/sd
#rm -r /data/app
#ln -s /system/sd/app /data/app
#busybox cp -a /data/app-private /system/sd
#rm -r /data/app-private
#ln -s /system/sd/app-private /data/app-private
now the apps are all on the EXT2 partition of the MicroSD .. happy downloading
I don't know what i have done wrong but eveything i try i keep getting errors and u have been more then help full but i am proberly to stupid to do it my self and i know i can do it if only i could find a video toturial from youtube or so but can't find any so i am stuck here.
But thank you very much for all ur help i would never have gotten to the last step with out ur help.
So now my only option is a help video or remote pc help if that is possible.
Ps. xda should make u a Moderator or Admin cause u r very help full and u know what u r talking about.
Zionator said:
I don't know what i have done wrong but eveything i try i keep getting errors and u have been more then help full but i am proberly to stupid to do it my self and i know i can do it if only i could find a video toturial from youtube or so but can't find any so i am stuck here.
But thank you very much for all ur help i would never have gotten to the last step with out ur help.
So now my only option is a help video or remote pc help if that is possible.
Ps. xda should make u a Moderator or Admin cause u r very help full and u know what u r talking about.
Click to expand...
Click to collapse
it's a nice thought .. not really sure i'd want to hold that kind of responsibility tho .. i think it'd be like calling me "Mr. President" when i drive the local garbage truck .. these guys are doing great here .. i'm just glad to lend a hand and hope it helps out
Hey guys just thought i'd chime in.
Firstly just to clarify are you using adb from your windows system or are you trying to do this all on the terminal app because these commands are issued to terminal after replacing both mount.conf and init.rc as described above
$su
#busybox df -h
as above you should see a line "/dev/SOMETHING" "size data" "/system/sd"
if you don't see this line then there's most likely a problem with your card format, did you make sure you had fat32 first then ext2 in that order on the card, fat32 must be first. i find it helps to check if camera can use the sdcard, if it can't, reformat, unmount and check camera again.
Assuming you've gotten this right so far
#busybox cp -a /data/app /system/sd
#rm -r /data/app
#ln -s /system/sd/app /data/app
#busybox cp -a /data/app-private /system/sd
#rm -r /data/app-private
#ln -s /system/sd/app-private /data/app-private
and hopefully your apps should all work, but not appear as downloaded in the market (don't worry this'll change if you reinstall them from the market)
if you're using adb from windows to try the above the commands will be slightly different:
Procedure:
***********************************************************
- this can be skipped if you've already replaced the mountd.conf and init.rc
adb remount
adb shell mkdir /system/sd
adb shell ls /system
adb push LOCATION OF FILE/mountd.conf system/etc/mountd.conf
adb push LOCATION OF FILE/init.rc system/init.rc
(LOCATION OF FILE = the folder you have the modified files)
adb shell
reboot
***********************************************************
If you've skipped ahead
adb remount
adb shell
busybox df -h
as above you should see a line "/dev/SOMETHING" "size data" "/system/sd"
Again if this line doesn't exist you've missed something, go back
busybox cp -a /data/app/ /system/sd
rm -r /data/app/
ln -s /system/sd/app /data/app
busybox cp -a /data/app-private /system/sd/app-private
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
reboot
and hopefully your apps will all work and again, not appear in market.
If this doesn't help please advise what error messages you are getting and exactly where everythings going wrong, maybe we can get you back on track.
just reformated the card from fat 16 to fat 32 as u said hope it works now lol.
And thanks for the help.
Keep u posted.
C:\Users\Illuminator\Desktop>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 48.4M 0 48.4M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 67.5M 67.5M 0 100% /system
/dev/block/loop0 1.4M 1.4M 0 100% /system/modules
/dev/block/loop1 3.1M 3.1M 0 100% /system/xbin
/dev/block/mtdblock5 74.8M 44.6M 30.1M 60% /data
/dev/block/mtdblock4 67.5M 1.3M 66.2M 2% /cache
/dev/block/mmcblk0p1 1.3G 4.0K 1.3G 0% /sdcard
#
--------------------------------------------------------------
# busybox cp -a /data/app/ /system/sd
busybox cp -a /data/app/ /system/sd
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
The list goes on and on. puha need a smoke.
But thanks for help.
why does it say "No space left on device"???
C:\Users\Illuminator\Desktop\G2>adb push C:\Users\Illuminator\Desktop\G2\/mountd
.conf /system/etc/mountd.conf
failed to copy 'C:\Users\Illuminator\Desktop\G2\/mountd.conf' to '/system/etc/mo
untd.conf': No space left on device
Ok might be fine but better safe than sorry your last line says:
/dev/block/mmcblk0p1 1.3G 4.0K 1.3G 0% /sdcard
That means that you're sdcard in fat32 format is only 1.3gbs in size is that correct? I assume this means you're using the sdcard that came free with the phone (2gb) if your card is larger say an 4 or an 8 something has gone wrong, but if this is correct lets move on.
cool so your sdcard is now partitioned fat32 -1.3gb followed by 0.7gb ext2
better safe than sorry redownload http://forum.xda-developers.com/attachment.php?attachmentid=139735&d=1230107855 the files and place them (the 2 files, not the folder) in the same folder as adb (do not mount your usb card)
>adb remount
>adb push mountd.conf system/etc/mountd.conf
>adb push init.rc system/init.rc
>adb shell
#mkdir /system/sd
#ls /system
(make sure a folder called sd exist)
#reboot
When your android reboots
>adb remount
>adb shell
#busybox df -h
Cross fingers, pray, beg, bargain and look for the line
"/dev/SOMETHING" "size data" "/system/sd"
in case this doesn't work i'm going to pm you my email, we can chat on google messenger and try and get this sorted
Quick question are you remembering to "adb remount" when you attach the phone - if you don't the phone wont be writable, which may explain the no space issue here:
C:\Users\Illuminator\Desktop\G2>adb push C:\Users\Illuminator\Desktop\G2\/mountd
.conf /system/etc/mountd.conf
failed to copy 'C:\Users\Illuminator\Desktop\G2\/mountd.conf' to '/system/etc/mo
untd.conf': No space left on device
*********but here you are trying to write to a location that doesn't exist, unless you see the magic line ending system/sd you cannot proceed
# busybox cp -a /data/app/ /system/sd
busybox cp -a /data/app/ /system/sd
cp: write error: No space left on device
cp: write error: No space left on device
Jesus this is killing me!!! yesterday i got all the way to step.12
And yes the sd came with the phone sdcard in fat32 -1.3gb followed by 0.7gb ext2 - yes that's correct.
And in case u where woundering then yes my phone is rooted wich was a pice of pie compered to this lol.
---------------------------------------------------------------------
C:\Users\Illuminator\Desktop>adb remount
remount succeeded
C:\Users\Illuminator\Desktop>adb push mountd.conf system/etc/mountd.conf
failed to copy 'mountd.conf' to 'system/etc/mountd.conf': No space left on devic
e
C:\Users\Illuminator\Desktop>adb push C:\Users\Illuminator\Desktop\/mountd.conf
system/etc/mountd.conf
failed to copy 'C:\Users\Illuminator\Desktop\/mountd.conf' to 'system/etc/mountd
.conf': No space left on device
C:\Users\Illuminator\Desktop>
You're not kidding i've done this 5 times (on 3 phones - updates) never had this much trouble!
do you have the same problems if you sit the files on your sdcard and do the following? if so as much as it sucks to lose your data i would strongly suggest doing a wipe before hand (reboot phone holding home and at prompt alt + w)
>adb shell
#busybox cp -a /sdcard/mount.conf /system/etc/mount.conf
#busybox cp -a /sdcard/init.rc /system/init.rc
#mkdir /system/sd
C:\Users\Illuminator\Desktop>adb shell mkdir /system/sd
mkdir failed for /system/sd, File exists
fantastic, well that's something! how about the other two did both copy successfully? and if so does the magic line appear after reboot?
faithnolonger said:
fantastic, well that's something! how about the other two did both copy successfully? and if so does the magic line appear after reboot?
Click to expand...
Click to collapse
Just restarting the phone but for some reason all the app are copyed to the fat32 part of the sdcard lol.
oh no for some odd reason the sdcard is not working no more???
--------------------------------------------------------------------
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 48.4M 0 48.4M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 67.5M 67.5M 0 100% /system
/dev/block/loop0 1.4M 1.4M 0 100% /system/modules
/dev/block/loop1 3.1M 3.1M 0 100% /system/xbin
/dev/block/mtdblock5 74.8M 44.6M 30.1M 60% /data
/dev/block/mtdblock4 67.5M 1.3M 66.2M 2% /cache
#
------------------------------------------------------------------------
Just wiped the system on the phone and reinstalling the JFv1.31
wow that's not right your apps should not be there:S
ok maybe time to go to real time chat i've got my android next to me, i've pm'd you my email address, you can message me over IM
Ok thanks i am ready in chat mode hehe.
when i type any of the adb command stuff i keep getting error: device not found. i don't know what to do next.
I managed to break my micro sd card in half today and I wasn't able to pickup a class 10 or 6 replacement locally so I thought I could use some of the 6gb of internal memory as a virtual filesystem to get me out of trouble.
So, after quickly looking at the android docs and the supported busybox commands I created a 2gb sdcard.img in /data and mounted to /sdcard. I copied some files to it with astro filemanager and fired up raging thunder 2 and it went ahead and downloaded the game data to /sdcard/ and worked correctly.
But, a few apps won't recognise it as an sdcard (Motorola SD card and phone storage settings applet) as well as things like PlayPro (states I have no sdcard present). I thought perhaps I could modify the /etc/vold.fstab file to auto mount the sdcard.img I created using vi but I'm a bit clueless as to what I should change on the dev_mount /sdcard line to get it automounted at boot and hopefully fool the rest of the apps into thinking it is a physical sdcard.
Can anyone possibly point me in the right direction? Not sure how to invoke cmd mode in vi using the milestone qwerty either but I'll keep digging.
What I did (roughly), maybe I'm going about it wrong but any advice would be appreciated.
1. rooted device
2. installed the free terminal app from the market
3. fired up the terminal shell
4. su
5. dd if/dev/zero of=/data/sdcard.img bs=1024 count=1 seek=2000000
6. busybox mkfs.vfat /data/sdcard.img (didn't seem to support -F 32)
7. busybox mount -o loop /data/sdcard.img /sdcard/
+ 1 for this, it would be great to can use internal storage for user data
Why do you let this nice post die.. so "flibbulator" found anything more out?.. I'd like to know more.. like if you got it to work with Music Players and Video players??
Try to mount /data/sdcard.img to /mnt/sdcard (/sdcard is a link to /mnt/sdcard)
or try "export EXTERNAL_STORAGE /sdcard"
I made in a different way: created a 4GB storage.img in /data and mounted it in /sdcard/storage, so internal storage is finally usable for user data
the problem was to set mount point on boot, I can't find a way to execute a script on boot (you can't permanently modify init.rc)
flibbulator said:
What I did (roughly), maybe I'm going about it wrong but any advice would be appreciated.
1. rooted device
2. installed the free terminal app from the market
3. fired up the terminal shell
4. su
5. dd if/dev/zero of=/data/sdcard.img bs=1024 count=1 seek=2000000
6. busybox mkfs.vfat /data/sdcard.img (didn't seem to support -F 32)
7. busybox mount -o loop /data/sdcard.img /sdcard/
Click to expand...
Click to collapse
I have actually tried this on my Droid2Global, and I get the error "unknown operand if/dev/zero" I feel like I am missing the point or do not fully understanding how to use the "dd" command?
the correct syntax is:
dd if=/dev/zero of=/data/sdcard.img bs=1024 count=4194340
4194340 --> 4GB
patton82 said:
the correct syntax is:
dd if=/dev/zero of=/data/sdcard.img bs=1024 count=4194340
4194340 --> 4GB
Click to expand...
Click to collapse
Thank you bro.
Quick question I keep getting these errors. I do have a folder in "/" named "sdcard-int"
Better Terminal Emulator Pro
/ # busybox mount -o loop /data/sdcard.img /sdcard-int/
mount: can't setup loop device: No such file or directory
/ # busybox mount -o /data/sdcard.img /sdcard-int
mount: can't read /etc/fstab: No such file or directory
/ #
Sent from my DROID2 GLOBAL using Tapatalk
you can't place anything in root folder, /sdcard is a link to /mnt/sdcard and is created by init.rc (you can't edit init.rc, it's provided by boot.img, so need to extract from boot.img and repack)
I made in this way but I have to manually execute a script or a command from terminal after every boot to mount storage.img
mkdir /sdcard/storage
su
dd if=/dev/zero of=/data/storage.img bs=1024 count=4194340
busybox mkfs.vfat /data.storage.img
mount -o loop -t vfat /data/storage.img /sdcard/storage
Will be lost anything after reboot when use this storage?
Sent from my MotoA953 using XDA App
all the stuff in img file will not be lost, as long as you put it in /data/
on the contrary the mount point must be restored after reboot
patton82 said:
you can't place anything in root folder, /sdcard is a link to /mnt/sdcard and is created by init.rc (you can't edit init.rc, it's provided by boot.img, so need to extract from boot.img and repack)
I made in this way but I have to manually execute a script or a command from terminal after every boot to mount storage.img
mkdir /sdcard/storage
su
dd if=/dev/zero of=/data/storage.img bs=1024 count=4194340
busybox mkfs.vfat /data.storage.img
mount -o loop -t vfat /data/storage.img /sdcard/storage
Click to expand...
Click to collapse
Thank you, I will use the Thank you button when I login via PC.
I still get the same error, I know that I'm doing something incorrectly or maybe I don't understand "mount" comment correctly?
/ $ su
/ # mkdir /sdcard/storage
/ # dd if=/dev/zero of=/data/storage.img bs=1024 count=41943404194340+0 recordsn
4194340+0 records out
4295004160 bytes (4.0GB) copied, 339.823883 seconds, 12.1MB/s
/ # busybox mkfs.vfat /data/storage.img
/ # mount -o loop -t vfat /data/storage.img /sdcard/storage
mount: can't setup loop device: No such file or directory
/ #
I am using my sdcard also, I'm not too sure if that makes any difference?
Sent from my DROID2 GLOBAL using Tapatalk
Better terminal pro uses BASH shell, I presume
try to switch to android shell, in preferences
or to use terminal emulator (free) from market
Okay, I tried Android Terminal Emulator, and this is a new error.
export PATH=/data/local/bin:$PATH
$ $ su
# mount -o loop -t vfat /data/storage.img /sdcard/storage
ioctl LOOP_SET_FD failed: Device or resource busy
#
Not too sure where to go now. I thank you again for all your help, and time.
Sent from my DROID2 GLOBAL using Tapatalk
resource busy, you have to reboot the phone
I use Gscript lite, add a script with the string
mount -o loop -t vfat /data/storage.img /sdcard/storage
and create a shortcut to homescreen, so when I reboot, I can mount the img file in one click
Cool mod for my ROM. Could I take it??
sure, they are simple shell commands
the best would be to do what happen with Samsung Galaxy S: internal storage mounted as sdcard and physical sdcard mounted in a folder /sdcard/sd
storage.img is 3-4 times faster than my peak 8GB class 6
There is an application "Autostart" in the market, which can automatially execute a script with root after boot up.
I up because I'm now also interested in making profit of the huge internal storage. I'd like to put my wikipedia data from wikidroyd to the internal storage. Hopefully I'm skilled enough to follow the given steps...I doubt that though
fKngFtd said:
Okay, I tried Android Terminal Emulator, and this is a new error.
export PATH=/data/local/bin:$PATH
$ $ su
# mount -o loop -t vfat /data/storage.img /sdcard/storage
ioctl LOOP_SET_FD failed: Device or resource busy
#
Not too sure where to go now. I thank you again for all your help, and time.
Click to expand...
Click to collapse
Guys, I need your help! I have exactly. The same problem:
Every time I try to mount my storage.img I get
Ioctl LOOP_SET_FD failed: Device or resource busy.
I rebooted several times and also tried to mount smaller images (first I tried 3gb then I tried 1mb).
Any solution?
Edit: I solved it myself. I always forgot to punch in busybox before the command. Now it worked for me!!
I do have a question now. With help of Gscript I made a shortcut to mount the storage.img to my sdcard. But my pc wont recognise the sdcard as long as the image is mounted. What is the command to unmount the partition so I wouldnt have to reboot my phone before connecting it to the pc...?
Any help is much appreciated! Thx
(Something like busybox unmount -o loop -t vfat...?)
Sent from my MotoA953 using XDA App
Hi I have to following problem and can't find the answer with google.
I have routed my AC100.
Code:
sudo adb shell
$
su
#
so I believe the AC100 is rooted
next
Code:
#mount
/dev/block/mmcblk3p1 /system ext2 ro,relatime 0 0
therefore I did
Code:
mount -o remount,rw -t ext2 /dev/block/mmcblk3p1 /system
mount
/dev/block/mmcblk3p1 /system ext2 rw,relatime 0 0
so I think the disk has been successfully re-mounted in re-write mode.
however whenever I do something like
Code:
sudo ./adb pish com.google.android.maps.xml /system/etc/permissions
I get
Permission denied
I would be grateful if someone could point me in the right directions.
Many thanks
Frank
Hi guys,
If any one getting error while remounting system partition in rw mode using adb, please follow these steps :
C:\Android\android-sdk-windows\tools> adb remount
remount failed: No such file or directory
SOLUTION:
Connect to your device usb adb: [FOR ROOTED DEVICES ONLY]
C:\Android\android-sdk-windows\tools> adb shell
$su
#mount -o remount,rw /dev/stl12 /system
(do your desired work like copy some files on system/media folder , then remount the system partition in ro mode again)
# cd /
#mount -o remount,ro /dev/stl12 /system
#exit
$exit
Thats all
FYI if you want to know the dev partitions mounted on your device :
C:\Android\android-sdk-windows\tools> adb shell
$ su
# mount
cheers
Did you map the other partitions by any chance? I'd like to be able to make a full backup to eventually be flashed back with Heimdall or ODIN. I already have a system.rfs (stock + root) that could be made in a tar image.
I've see tutorials for other Samsung phones but these need to be adapted to our exact setup. I haven't found anything generic enough to know how to go about mapping things.
It might also help those who flashed GT-S5660 ROMs on the Bell Canada GT-S5660M, as the screen brightness issues sound very much like kernel issues to me...
I can't quite tell what the difference is between stl and bml either. (I'll probably try dd'ing the different blocks, except stl5, and peek around with a hex editor...)
Goodbye,
Darkshado