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

Root [Recovery][CWM] ClockworkMod v6.0.3.7 (~WORKING!)

junkie2100 said:
well, i just google the hell out of things lol. it takes time though and can be very difficult to find obscure info
Click to expand...

As do I. Sometimes I get lucky, other times not so much. It's been hard working this in while also fitting in family + work. At least CWM is working.
 
i have no life, so i can spend that kind of time lol. no job, no real social interaction, just play on a phone or computer all day
 
but yea check out the aurora repo, the fstabs should be compatible i think they use the by-name format. and the proprietary files should come pretty close
 
junkie2100 said:
but yea check out the aurora repo, the fstabs should be compatible i think they use the by-name format. and the proprietary files should come pretty close
Click to expand...

The fstabs are almost identical. Check my repo again. When creating it, the initial sync uploaded old files :confused:
 
to get external to mount you need to define LUN
in BoardConfig.mk it'd look something like this:
BOARD_UMS_LUNFILE := "/sys/devices/platform/msm_hsusb/gadget/lun0/file"
(might need to be edited with proper locations) but this should fix external mounting
 
rbheromax said:
to get external to mount you need to define LUN
in BoardConfig.mk it'd look something like this:
BOARD_UMS_LUNFILE := "/sys/devices/platform/msm_hsusb/gadget/lun0/file"
(might need to be edited with proper locations) but this should fix external mounting
Click to expand...

I figured as much. Where do I locate this file?

Er, nvm, found it. :)
 
yep, there may be slightly more to it than just that entry but thats the gist of it. also the internal/external switch is triggered by actually mounting internal via the fstab if im not mistaken. youll have to find the right fstab setup, but usually internal isnt the best option anyhow. it tends to get erased with the data partition causing you to lose your backups every time you mess with stuff in cwm
 
just change the mount points really. external sd changes to /externalsd instead of /sdcard, and i think if you do mmcblk0 with no partition number itll mount internal, that goes in /internalsd
 
the exact partition number of the internal sd you should be able to figure out by looking at /proc/partitions

open it in a text editor on the phone or pc, or adb shell in/pull up terminal and cat /proc/partitions

the block sizes are in kb. so about 4000000 is 4gb
 
or not... hell i dont know lol, ive only tried it once but it wont work on the warp 4g apparently. at least i dont think it does. try it, may work for you

its /external_sd and /internal_sd btw
 
cooldudezach said:
And before you ask, I haven't been successful in getting CM10.1 to boot. (Sits on the picture of the android forever) Not sure why, really. I'm new to building CM, so help would be appreciated!

As I stated, it just sits on the picture of the startup android image. I do have limited adb access, so I can reboot the device but can't open the shell (get a file not found error, so I assume /system isn't mounting somehow)
Click to expand...

Yea thats not mounting system correctly. Can you post a link for the boot.img from build?
 
rbheromax said:
Yea thats not mounting system correctly. Can you post a link for the boot.img from build?
Click to expand...
I'm going to rebuild it while I'm out to lunch, then post it. I don't have it anymore atm. Also, I haven't synced the 4.4 branch at all yet, still on 10.1.

Edit:
Okay, so I'm not going to build it. I'm getting this error for whatever reason >.<
Code: 
hardware/qcom/display/libexternal/external.cpp:451:31: error: aggregate 'qhwc::ExternalDisplay::post()::mdp_display_commit ext_commit' has incomplete type and cannot be defined
 
cooldudezach said:
I'm going to rebuild it while I'm out to lunch, then post it. I don't have it anymore atm. Also, I haven't synced the 4.4 branch at all yet, still on 10.1.

Edit:
Okay, so I'm not going to build it. I'm getting this error for whatever reason >.<
Code: 
hardware/qcom/display/libexternal/external.cpp:451:31: error: aggregate 'qhwc::ExternalDisplay::post()::mdp_display_commit ext_commit' has incomplete type and cannot be defined
Click to expand...

are you building with display variant set to caf?

also, you may very well have to do some major tweaking of the includes. generally a modded msm_mdp.h has to be used in the /include/linux/ directory of the device tree but has to be based on the kernel. my current issues seem to be ion related though im sure thats not the only problem
 
junkie2100 said:
are you building with display variant set to caf?

also, you may very well have to do some major tweaking of the includes. generally a modded msm_mdp.h has to be used in the /include/linux/ directory of the device tree but has to be based on the kernel. my current issues seem to be ion related though im sure thats not the only problem
Click to expand...
I'm not sure. I had it working originally, but along the lines it got messed up. Now I'm just trying to get CM11 to build. -_-
 
You must log in or register to reply here.
Back
Top Bottom