[ROM]PMID4311 Modified Stock

[elektrik]

While packaging 'tun.ko' with the ROM is probably a good idea, very few people will actually need to load it. In most cases, the version built into the kernel is sufficient to connect to a corporate VPN. If this ROM has init.d support, you can install this yourself using a script containing no more than "insmod /system/vendor/modules/tun.ko".

Unfortunately dolorespark, I've had quite a bit of trouble modifying the stock PMID4311 ROM. I'm not even at the point of adding init.d support-that OEM partition is limiting what I can do with it. If I simply build the ROM without it, it fails to run. If I modify certain things and include it, the changes work on first boot, but are overwritten on next boot. I can't figure out what's making the changes after the first reboot, and I can't seem to 'crack open' the OEM fex to see what's inside (I thought it was cramfs, but apparently I'm either doing something incorrectly, it's encrypted or it's not cramfs-not sure).

[dolorespark]

that OEM partition is limiting what I can do with it. If I simply build the ROM without it, it fails to run. If I modify certain things and include it, the changes work on first boot, but are overwritten on next boot. I can't figure out what's making the changes after the first reboot, and I can't seem to 'crack open' the OEM fex to see what's inside (I thought it was cramfs, but apparently I'm either doing something incorrectly, it's encrypted or it's not cramfs-not sure).

I'm at work right now, so I may get some details wrong, but... in init.rc, you should see something like "service preinstall" that runs a 'preinstall.sh' script. There's also a property trigger to start "preinstall" - I think it's "on sys.boot.completed". Look at the script (so you know what it does), then delete it and everything that causes it to run.

Also, I'm pretty sure that the OEM partition is cramfs but from what I've read, there are different incompatible flavors. I can't remember if I finally got it mounted on the tab or if I had to do so in Linux. Either way, there wasn't much if anything worth saving (if you go back to the post for my CM10 announcement, you'll find a link to a package with all the apps that were on the tab).

[elektrik]

I'm at work right now, so I may get some details wrong, but... in init.rc, you should see something like "service preinstall" that runs a 'preinstall.sh' script. There's also a property trigger to start "preinstall" - I think it's "on sys.boot.completed". Look at the script (so you know what it does), then delete it and everything that causes it to run.

Also, I'm pretty sure that the OEM partition is cramfs but from what I've read, there are different incompatible flavors. I can't remember if I finally got it mounted on the tab or if I had to do so in Linux. Either way, there wasn't much if anything worth saving (if you go back to the post for my CM10 announcement, you'll find a link to a package with all the apps that were on the tab).

Thanks for the suggestion-I'll try that. Honestly, I believe I tried to delete that information in the past, but I've tried SO MANY things that didn't work, that perhaps I tried what you suggested in conjunction with something that hosed the ROM.

[bbsux]

elektrik,
could you do that fix to (that allows programs like titanium backup to be able to write to the sdcard [extsd]) and release a new pmid4311 image?

[Magister]

You can edit the file, I did it with TotalCommander, I guess you can use about any file explorer that can edit file, as long as you give it the root permission.

[elektrik]

Easy guys-I gotta see if dolorespark's advice actually works before I start that type of stuff

[elektrik]

UPDATE: doloresparks advice did help-at least somewhat-I was able to get rid of that nasty OEM partition, however it's caused a few more problems I'm still sorting out-thanks dolorespark for the clarity I needed.

...with that said, I'm WAY past the point of just modified stock, so I'm just going to go all the way and push ahead to create 'Elektricity ROM' ICS for this little guy....

[elektrik]

I can confirm that the em543 v2 file DOES work with the pmid4311. It looks exactly the same but is branded a little different (boot screens, I don't know what else)

about reads

em543 instead of pmid4311

4.04
baseband 1.4rc3
kernel
3.0.8
Jul 5 15:16:33 CST 2012

build #
em543-20120726

Ok, I think I may just buy one of these little beasties for myself to work on...