Ok, here is one with a fixed up recovery.fstab: http://goo.im/devs/bigbiff/quincyatt.img
Grabbing it now - will report back shortly with the results. :good:
Ok, here is one with a fixed up recovery.fstab: http://goo.im/devs/bigbiff/quincyatt.img
Ok, here is one with a fixed up recovery.fstab: http://goo.im/devs/bigbiff/quincyatt.img
Now it sees all partitions, except internal storage. Attached recovery log.
Same link, I uploaded one with /emmc as internal storage. Thanks for testing.
Same link, I uploaded one with /emmc as internal storage. Thanks for testing.
I can now browse both internal and external storage, but I cannot mount either of them for usb storage. Everything else looks good, as far as I can tell.
What happens when you try to mount USB? Also can you tell me if backing up and restoring 4.3 roms as well as installing works?
When I try to mount, the screen changes to the "unmount" button - but the drives are not visible on my pc. I had to click the unmount button a few times, to get the screen back to the mount screen - almost as if the touchscreen was unresponsive.
I will test backing up, restoring, and installing a little later - I actually have a new AOKP build finishing up, to test all this with later today.
Can you upload a recovery.log with you testing the mount usb feature?
That's what I posted a few posts back - that recovery3.txt is the log from after trying to mount a few times.
Sent from my SGH-I717 using XDA Premium 4 mobile app
That's what I posted a few posts back - that recovery3.txt is the log from after trying to mount a few times.
Sent from my SGH-I717 using XDA Premium 4 mobile app
USB Mass Storage still isn't working with that image either.Can you try this image: http://techerrata.com/bigbiff/quincyatt-twrp.img and see if USB Mass Storage is working?
Can you pull /tmp/recovery.log and dmesg after you try to mount?
Looks like dmesg was pulled from your ubuntu. Please pull it from TWRP.
Lol - sorry man, doing too many things at one time. Here is dmesg from recovery.
<6>[ 2.113494] Initializing USB Mass Storage driver...
<6>[ 2.113677] usbcore: registered new interface driver usb-storage
<6>[ 2.113800] USB Mass Storage support registered.
<6>[ 2.113891] usbcore: registered new interface driver ums-alauda
<6>[ 2.114044] usbcore: registered new interface driver ums-cypress
<6>[ 2.114227] usbcore: registered new interface driver ums-datafab
<6>[ 2.114349] usbcore: registered new interface driver ums-freecom
<6>[ 2.114532] usbcore: registered new interface driver ums-isd200
<6>[ 2.114654] usbcore: registered new interface driver ums-jumpshot
<6>[ 2.114837] usbcore: registered new interface driver ums-karma
<6>[ 2.114959] usbcore: registered new interface driver ums-onetouch
<6>[ 2.115142] usbcore: registered new interface driver ums-sddr09
<6>[ 2.115264] usbcore: registered new interface driver ums-sddr55
<6>[ 2.115447] usbcore: registered new interface driver ums-usbat
<6>[ 2.115661] usbcore: registered new interface driver usb_ehset_test
<6>[ 2.116058] peripheral driver registered w/ tranceiver
<4>[ 2.116180] msm_otg_sm_work 1798 id=0 OTG_STATE_UNDEFINED
<6>[ 2.118530] android_usb gadget: Mass Storage Function, version: 2009/09/11
<6>[ 2.118652] android_usb gadget: Number of LUNs=2
<6>[ 2.118804] lun0: LUN: removable file: (no medium)
<6>[ 2.118896] lun1: LUN: removable file: (no medium)
/sys/devices/platform/msm_hsusb/gadget/lun0/file
/sys/devices/platform/msm_hsusb/gadget/lun1/file
Code:<6>[ 2.113494] Initializing USB Mass Storage driver... <6>[ 2.113677] usbcore: registered new interface driver usb-storage <6>[ 2.113800] USB Mass Storage support registered. <6>[ 2.113891] usbcore: registered new interface driver ums-alauda <6>[ 2.114044] usbcore: registered new interface driver ums-cypress <6>[ 2.114227] usbcore: registered new interface driver ums-datafab <6>[ 2.114349] usbcore: registered new interface driver ums-freecom <6>[ 2.114532] usbcore: registered new interface driver ums-isd200 <6>[ 2.114654] usbcore: registered new interface driver ums-jumpshot <6>[ 2.114837] usbcore: registered new interface driver ums-karma <6>[ 2.114959] usbcore: registered new interface driver ums-onetouch <6>[ 2.115142] usbcore: registered new interface driver ums-sddr09 <6>[ 2.115264] usbcore: registered new interface driver ums-sddr55 <6>[ 2.115447] usbcore: registered new interface driver ums-usbat <6>[ 2.115661] usbcore: registered new interface driver usb_ehset_test <6>[ 2.116058] peripheral driver registered w/ tranceiver <4>[ 2.116180] msm_otg_sm_work 1798 id=0 OTG_STATE_UNDEFINED <6>[ 2.118530] android_usb gadget: Mass Storage Function, version: 2009/09/11 <6>[ 2.118652] android_usb gadget: Number of LUNs=2 <6>[ 2.118804] lun0: LUN: removable file: (no medium) <6>[ 2.118896] lun1: LUN: removable file: (no medium)
Can you look and see if the lun files have anything in them? Can you paste the contents of
Code:/sys/devices/platform/msm_hsusb/gadget/lun0/file /sys/devices/platform/msm_hsusb/gadget/lun1/file
lun0/file has just one line:
/dev/block/mmcblk0p28
lun1/file has just one line:
/dev/block/mmcblk1
So, TWRP is doing it's thing but the kernel isn't presenting them. What OS are you using?
For those of you wondering, 2.5.0.0 does not have the screen timeout issue that affected some people. The new timeout is pretty slick actually.