[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Hey everybody! haha

Been fighting this issue for a loooong time. I thought I would hit you guys up for some insight. I am fully prepared to believe that I and a few others have missed some stupid little setting some place, who knows. Whatever it is, I'm sure it isn't anything I have ever dealt with before. Maybe one of the CM/TWRP guys has seen this type of thing before?

Problem:

unmounted sdcard0 regardless of conventional/standard methods. Confirmed over multiple actual devices. HW fault is ruled out, for sure. Also common is that the internal sdcard remains intact and usable in recovery and under other roms.

The problem can't be found in the usual places one would look. ex: storage.xml, fstab.qcom, init.qcom.rc, qcom-common/rootdir/etc... It is specific to this repo. While custom, omni seems to be a cm/aosp blend + twrp. However, the cm base is a bit distant now and has basically lost relevance.

Source:

https://github.com/orgs/DirtyUnicorns-KitKat

ROM Base:

Omnirom

Device:

msm8660 based devices (pretty much all device folders required being twrped) Changes/additions to the rootdir/recovery folders throughout device tree. Device specific twrp settings in board configs.

Base Recovery:

TWRP

Since:

The internal card has never mounted.

Gerrit?:

Yes, yes, yes and yes. lol Omni, CM, AOSP + some that I can't remember at the moment have been reviewed and patches/picks applied in multiple combinations.

Source trees:

Different combinations of device, hardware, system and or vold, external, build, bionic, bootable, vendor. Have compiled and booted combinations of all these over time.

A bunch of other quality devs have worked on resolving this. Others have suggested that the twrp recovery used as the base recovery can be ruled out. However, I have easily worked on this the most and I haven't been able to rule it out. That said, I really don't know that much at all about twrp or how much it really effects the rom in the end. Omni's porting tut, what it is, directs you away from their website to deestroy's xda thread that has instructions on how to compile cm7 twrp recovery. You have to pick out of it what may be relevant to the device tree adds. Without the various twrp tags, you can't even lunch the compiler.

Another thought is that it might be a permissions thing. Running the rom, it does seem to have some awareness of the partition. I have also tried turning off selinux before building but that makes no difference. Perhaps some policy setting I haven't seen?

A lot of things have been ruled out. If it isn't recovery, it will probably turn out to be some stupid setting/switch call, link or something changed way back in the omni source. Likely because they have little support for "Skyrocket" like/age devices. i777 and a lot of 9000 series samsung devices.

Logs:

http://pastebin.com/B4fc4ckh

http://pastebin.com/rZaRjU8f

http://pastebin.com/jW5WdLFU

http://pastebin.com/U83XpdCT

http://pastebin.com/eaar7Vwi

http://pastebin.com/1KyB1ygj

These are compiled examples for testing and feedback on the sdcard0 issue. I'm letting these out as unofficial examples and while really cool, don't reflect what will be the next official release.

Use gapps or not. Sometimes there is one bootloop on first boot and doesn't reoccur. It might be a symptom of the problem tho? Maybe it is here where a conflict happens and the system reverts to some soc provision or other safety setting?

Skyrocket:

http://d-h.st/vEO

Hurc:

http://d-h.st/Peg

If anybody feels into looking at this, I would be very thankful.

PM me if you want. This way it would likely be faster?