• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ClockWorkMod v5.0.2.7 (file system/recovery utility) update 01/12/12 FIXED

hroark I was going to pm you but dont work I talked to a guy on the optimus forum that did cwm recovery and asked him about enabling usb storage in recovery and this is what he said.

Quote:
Originally Posted by new optimus
hey I have a question for you regarding how you fixed the error with connect as usb storage while in cwm.

I also have a samsung prevail and we have cwm recovery for it and get that same error when you try to us usb storage.

I realize you may not know or work on this phone but perhaps some insight to what you did would help.:D

you have to find the path to the lun0/file in sys, the Optimus's was in sys/devices/platform/msm_hsusb/gadget/lun0/file, and add that path in the BoardConfig.mk.
__________________
:rolleyes: Honeycomb is for tablets silly rabbit!! :D

Official Donate link for Dev/mod work.

PlayfulDroidz Wiki
user_online.gif


Click to expand...

So I went snooping through the phones sys files and sure enough I found it in the exact same place as he says.
 
new optimus said:
hroark I was going to pm you but dont work I talked to a guy on the optimus forum that did cwm recovery and asked him about enabling usb storage in recovery and this is what he said.



So I went snooping through the phones sys files and sure enough I found it in the exact same place as he says.
Click to expand...


trust me, i searched and could not find it
 
new optimus said:
could not find what?
lun0/file
I found it
/sys/devices/platform/msm_hsusb/gadget/lun0/file

you open lun0 and there is a file named file. that is it.
in lun0 folder is a folder named power and 2 files
they are named

file
uevent
Click to expand...

I can believe that i did not find that before, i must have been looking in the wrong folder or something

my android build system hard drive took a dump, so i need to set it up again, but once i do, i will create a new version of cwm
 
hroark13 said:
I can believe that i did not find that before, i must have been looking in the wrong folder or something

my android build system hard drive took a dump, so i need to set it up again, but once i do, i will create a new version of cwm
Click to expand...
ya I didnt think it would be in the /sys folder, thought system perhaps.
 
so in that new version of cwm, can you stop 'wipe data' from wiping sd-ext. as it stands, when you odin and reinstall that a2sd.zip all user apps come right back. granted they don't have settings but a titanium data restore puts you back in business immediately.

and yes, internal storage is still different when using this method to swap rfs to ext4.
 
inigomontoyasr said:
so in that new version of cwm, can you stop 'wipe data' from wiping sd-ext. as it stands, when you odin and reinstall that a2sd.zip all user apps come right back. granted they don't have settings but a titanium data restore puts you back in business immediately.

and yes, internal storage is still different when using this method to swap rfs to ext4.
Click to expand...

well my drive crashed, and kernel.org was hacked and is now down, so I cant re-downloaded source files, so this will have to wait
 
inigomontoyasr said:
so in that new version of cwm, can you stop 'wipe data' from wiping sd-ext. as it stands, when you odin and reinstall that a2sd.zip all user apps come right back. granted they don't have settings but a titanium data restore puts you back in business immediately.

and yes, internal storage is still different when using this method to swap rfs to ext4.
Click to expand...

that would not be a factory wipe, and I am not too sure where that would be changed

changing the BoardConfig.mk for the lun file will be pretty easy to do, once I get the sources
 
hroark13 said:
that would not be a factory wipe, and I am not too sure where that would be changed

changing the BoardConfig.mk for the lun file will be pretty easy to do, once I get the sources
Click to expand...

well I fixed the USB mounting, but not the factory wiping the sd-ext, that is a little beyond me, and i am not sure it should be done anyway
 
yeah. factory should leave only system apps. that's a good improvement, though. now we won't have to adb push files in clockwork, right?
 
Thanks, guys - new optimus & hroark13. People here sure don't just sit hitting F5 to refresh I'll be following this from now on.
 
limited said:
What does having the USB mass storage in CWM allow you to do?
Click to expand...


It allows you to transfer files without rebooting your phone. Like that one time when I wanted to flash a theme, I downloaded it to my computer, then went into recovery. I forgot to move the zip to my phone, so I had to reboot, move the zip, then go into recovery again. Really irritating.

Also, I'm sure it's useful if someone gets bootloops, you could get someone's nandroid to restore your phone. I've done that before :)
 
Ok put the new cwm on. Works like a charm, just tested it out. Now I understand what it's for :).

One question about CWM, can you rename the backup folders? does it care if the folder isn't a timestamp?
 
limited said:
Ok put the new cwm on. Works like a charm, just tested it out. Now I understand what it's for :).

One question about CWM, can you rename the backup folders? does it care if the folder isn't a timestamp?
Click to expand...

cant rename, that breaks the MD5 checksum, and then you cant restore it

that is something i dont know how to change
 
so inside the the new zip file there is this file "hk_1_2_cwm_rev_4" is that a kernal ? Do I just unzip and install it with cwm, or do I have to use odin to install that ?
 
now that i have done it i guess i should probably not have worried about making a2sd work on shabbykernel. all the odin images and clockworkmods come with hroarkernel.
 
does installing a new recovery do anything to my dqta and/or apps? i've installed cwm so many times but it's always been after odin recovery. thanks in advance
 
You must log in or register to reply here.
Back
Top Bottom