Related
So, nobody answered and I had to create this topic.
1) I have RC29
2) When I try to use the MOUNT command in pTerminal I ALWAYS get:
roootfs / rootfs ro 0 0
etc.
3) When I use
mount -o remount rw /system
I ALWAYS get:
mount: Operation not permitted.
4) When:
cd /system
cat /sdcard/recovery_testkeys.img > recovery.img
I ALWAYS get:
cannot create recovery.img: read-only file system
PS All files are there. The update's name is written right - update.zip. I've used pTerminal.
So, do I have the Root Access or not and am i doing smth wrong??
Appreciate any help\advices.
Thanks.
Have you tried doing this through the telnetd way?
BAD_BOY_KIEV said:
So, nobody answered and I had to create this topic.
1) I have RC29
2) When I try to use the MOUNT command in pTerminal I ALWAYS get:
roootfs / rootfs ro 0 0
etc.
3) When I use
mount -o remount rw /system
I ALWAYS get:
mount: Operation not permitted.
4) When:
cd /system
cat /sdcard/recovery_testkeys.img > recovery.img
I ALWAYS get:
cannot create recovery.img: read-only file system
PS All files are there. The update's name is written right - update.zip. I've used pTerminal.
So, do I have the Root Access or not and am i doing smth wrong??
Appreciate any help\advices.
Thanks.
Click to expand...
Click to collapse
You have to use the telnetd command first to exploit the root access. There are other threads that tell you how. Basically telnet into the phone then execute the commands.
If you look in your PM box. i sent you a link with step by step instructions yesterday!
Cannot root RC29 - read only file error
Hi,
I did it also thru Telnet but get the same message...any tips to root the phone? I am still sending that automatic SMS...
Thanks, M
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)
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
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.
To those of you who followed link here: don't rush ahead and execute adb command. Read the thread in its entirety, since it contains typos and trial n error.
Gl, hf
Hi. I've been stupid. U may flame me but plz also provide some advice to swallow it with.
I followed bad advice and flashed cwm 5xxxx. After that tried to run superwipe, which got stuck after a few steps. To my horror i realized i had run it from internal. Of course it wiped itself and i got stuck mid-partinioning i think.
Since cwm don't read ext sd i tried to push new recovery via easyflasher, but i can't seem to get a driver that lets my pc interact with the device.
Instead discovered i have adb acess if connected when device is in cwm. From there tried to run PERI v 0.4. At first step, trying to push recovery i get a message of no space available. I think this is due to borked partitioning with superwipe. I guess I can repartition with cwm, but now I've messed so much up I don't wanna do anything more without proper advice.
Thanks
bump
If you have adb access, then use it to push a new rom.
"adb push {shiny new rom or recovery} /sdcard/"
You might have to change /sdcard/ to whatever cwm 5x uses?
Then you can just flash it from cwm.
EDIT: I just saw that you have the tf101G - it might work, but you probably have to find the right rom or recovery.
sent from my transformer
gee one said:
If you have adb access, then use it to push a new rom.
"adb push {shiny new rom or recovery} /sdcard/"
You might have to change /sdcard/ to whatever cwm 5x uses?
Then you can just flash it from cwm.
EDIT: I just saw that you have the tf101G - it might work, but you probably have to find the right rom or recovery.
sent from my transformer
Click to expand...
Click to collapse
Good advice, problem is that im not very savvy. How do i execute that command and what if i need to repartition the internal sd?
When running oneclickrecovery i get following prompts:
Uh-oh! I'm softbricked or have a recovery-bootloop! D:
Never fear sir and/or madam! PERI is here! -trips-
Adb needs to be fully working for this to work properly.
Note that this will wipe your current recovery.
Also note that this may not work, don't taze me bro!
Run? Close if you want to cancel.
Press any key to continue . . .
List of devices attached
0123456789ABCDEF recovery
If you see your device here this will work, if not fix adb.
Press any key to continue . . .
running fix...
dd: writing '/dev/block/mmcblk0p3': No space left on device
4097+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.345431 seconds, 5.8MB/s
rebooting tab, if at any step it doesn't reboot turn off and turn back on
Once back into an adb possible state continue...
Press any key to continue . . .
Pushing new recovery...
1331 KB/s (4599884 bytes in 3.374s)
Running wolf's exploit...
mv: can't rename '/data/local/tmp': No such file or directory
Going...
ln: /data/local/tmp: No such file or directory
Done!
Now lets reboot your TF again...
Continue when back into ADB again...
Press any key to continue . . .
Flashing new recovery...
dd: can't open '/sdcard/recoveryblob': No such file or directory
Done!
Continue to reboot your tab, do the button combination to test recovery.
(Hold volume-down as it's rebooting and press vol-up to enter recovery)
Press any key to continue . . .
Hopefully that fixed everything!
Press any key to continue . . .
Of course nothing was fixed and I still have cwm 5xxx which can't flash from ext sd. If I can only get another recovery I can flash any rom and that's that.
In device manager the device shows up as android adb interface when booted into cwm. I also have a device named android composite adb interface, but with a warning sign on it.
This is getting tiresome...
Edit: tried using quick adb pusher, but get message that i cant mount as r/w. In cwm cant mount data or sdcard/.android_secure.
Fun thing is I dont have root either.
It looks like your partitions are unformatted.
I think you need to get to a root shell via adb in recovery
- put your phone on recovery and plug into your computer
- type "adb remount" (you might get an error) then type "adb shell"
- you'll be in a terminal shell
- type "mount" to see how/what your sdcard is doing. Look for the line that has /sdcard on it. It might be something like /dev/block/mmcblk0p1 mounted at /sdcard blah blah...
- now to format your sdcard, type "mke2fs /dev/blah/whereever/your/sdcard/is/mounted/from/above"
- allow it to complete and type "exit". you might have to reboot your tab to get everything to remount
- once your tqab is back in recovery, type on your computer "adb push [some new recovery that uses the external sdcard or a new rom] /sdcard"
- if you have recovery bootloops, google around, there is a fix that wipes the reboot command from the misc partition. You can type it from an adb shell it's something like "dd if=/dev/block/zero of=/be/carefule/because/you/have/a/tf101G bs=1 count=13"
- Google is your friend. Linux is your friend. This is a bit of a high level overview, so you'll have to fill in the details yourself. Keep in mind that I don't have a tf101G and I never tried this before (a benefit of never using superwipe!)
Good luck!
OK. I'd like to try the method u describe but as I mentioned I'm really not tech savvy. I don't even know how to get to the point where I type "adb remount". Do I just open a cmd prompt? Tried that - didn't work.
I have downloaded sdk manager for when I did some stuff with my phone earlier and have the basic packages installed.
Are you on Windows? I think it's a path issue. You either need to put everything in the same folder and run everything from there or put adb in your path. I don't use Windows, so that's probably the best advice I can give you. "which adb" and "echo $PATH" probably won't work in Windows like they do in linux.
Ehm.. too techie answer for me to comprehend.
Yes I'm on win 7.
Put what in same folder as what?
Run from there by right clicking empty space in folder and choosing cmd?
What do you mean by putting adb in my path?
For some reason, lots of people on windows just put the recovery/rom and adb in the same folder and run it from there in the command prompt. Put it all in one place and use the cd command in the terminal to get there.
sent while running with scissors
Lol. Don't cut urself man. I might need your help again
I'll try later when kids asleep.
Allright. Learning curve is steep but im clinging on to it:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,ac
l,barrier=1,data=ordered)
~ # mke2fs /dev/block/mmcblk0p2
mke2fs /dev/block/mmcblk0p2
mke2fs 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p2 is apparently in use by the system; will not make a filesys
tem here!
~ # exit
exit
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Any ideas?
You're almost there... You're /cache partition is already formatted (ext4) Be careful since you can really mess things up with the wrong commands or mis-typed commands.
It looks like you need to mount your sdcard manually. I'm not sure which partition it is. I'll check the stock rom in a little while- I have to run some errands while it downloads.
OK, I downloaded the stock rom and had a look at the /etc/recovery.fstab file in the stock recovery. Should be what we need.
Put your tablet in recovery. Then, in a windows terminal, type "adb remount" and then "adb shell" This wil put you into an android terminal. I don't know if you need read/write permissions in CWM? Who knows? Typing commands in here is the same as typing commands on your tablet (if anyone used the command line any more).
type "ls /dev/block/" and you should see a long list of - look for mmcblk1p1 or mmcblk1. It will probably be the first one.
type "ls /" and look for /sdcard. If it's not there type "mkdir /sdcard" This step creates the mount point if it doesn't exist.
Now type "mount /dev/mmcblk1p1 /sdcard" - Substitute whichever one is in your /dev/block directory from above.
EDIT: If you get errors that it's not formatted or "specify the type" then we'll have to format it first. "mke2fs /dev/block/mmcblk1p1"
Now, in a different windows terminal, type "adb push [a new rom/recovery] /sdcard/"
In CWM, you should be able to flash whatever you pushed there.
If it flashes, but you get bootloops or boot back into CWM, you probably have the dreaded CWM bootloops. You can fix that by typing "dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=15" in the terminal as the first step after "adb shell" For this you will need root access (with the # prompt, not $) Type "su" if you don't ahve the # prompt. It might work? Note that this is experimental and wipes out a bit of your misc partition. I have no idea of what else is on there, so there might be unintended consequences.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ls /dev/block/
ls /dev/block/
loop0 loop3 loop6 mmcblk0p1 mmcblk0p4 mmcblk0p7 platform
loop1 loop4 loop7 mmcblk0p2 mmcblk0p5 mmcblk1
loop2 loop5 mmcblk0 mmcblk0p3 mmcblk0p6 mmcblk1p1
~ # ls /
ls /
cache proc system
data res tmp
default.prop root ueventd.goldfish.rc
dev sbin ueventd.rc
etc sdcard ueventd.ventana.rc
init staging
init.rc sys
~ # mount /dev/mmcblk1p1 /sdcard
mount /dev/mmcblk1p1 /sdcard
mount: mounting /dev/mmcblk1p1 on /sdcard failed: No such file or directory
~ #
I tried pushing anyway, but can't still mount sdcard on cwm from pad interface.
As for the sdcard contents, I have nothing there that can't be deleted.
use "mount /dev/block/mmcblk1p1 /sdcard" No need to repeat the ls commands.
Sorry for not answering rapidly. Baby chose this night to be at his worst.
First
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # mount /dev/block/mmcblk1p1 /sdcard
mount /dev/block/mmcblk1p1 /sdcard
~ #
New cmd
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push cwm-6.0.1.2-t
ouch-external.zip /sdcard/
1332 KB/s (5070063 bytes in 3.715s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Can't mount sdcard frow cwm. Can I also flash new rck manually?
Tried reboot and mounting again manually, but cwm won't mount.
Maybe try "mount /dev/block/mmcblk1 /sdcard" ???
I get invalid argument on that command.
What if we forget cwm and try format to default partinioning and push stock?
You could try pushing the stock rom to your tablet and then flashing it via the staging partition. The rom is about 522M, so you might need the sd card, but otherwise, you can push it anywhere it will fit. Staging partition is /dev/block/mmcblk0p4. Google around, the info is certainly in this forum. As long as you can get a root shell via adb, you can flash it. The stock rom is on the Asus sight. Just keep unzipping it until you see the blob file.
Of course, you can flash anything you want via the staging partition, if it's packed in a blob format. You might consider flashing a rooted rom instead of the stock.
I have stock on hd. Shall I mount staging via same commands as i mounted sdcard? Push there via adb. Then what command to flash the blob? The blob has no file extension. Shall i keep it that way?
Edit: ok i tried to unpack the recoveryblob from my desired version of cwm, but tool stopped working during process of writing recoveryblob.sos. I got the tool here http://forum.xda-developers.com/showpost.php?p=21620550&postcount=24
Next problem:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # mount /dev/block/mmcblk0p4
mount /dev/block/mmcblk0p4
mount: can't find /dev/block/mmcblk0p4 in /etc/fstab
~ #
Edit 2: I finally managed to get apx working if it somehow can help.