yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] vinjurr:
RaymanFX beta 3 is out,

Now, RaymanFX kitkat beta 3 is out, may kindly repack for dual boot. thanks:D
[Sony Xperia S, Acro S, Ion] zaidx:
Hi

Can you repack beta 3 cm11 for native please
[Sony Xperia S, Acro S, Ion] rolex0815:
OpenSEMC - BETA 3

bm_native_OpenSEMC-kk-beta3.zip

http://www13.zippyshare.com/v/84411931/file.html

bm_loop_OpenSEMC-kk-beta3.zip

http://www13.zippyshare.com/v/39165388/file.html

UNTESTED!
[Sony Xperia S, Acro S, Ion] vinjurr:
Thanks a lot. Happy new year 2014, I have loaded xperia s Native successfully.
[Sony Xperia S, Acro S, Ion] vinjurr:
Dual Boot option missing. repack not properly done:crying:
[Sony Xperia S, Acro S, Ion] rolex0815:
What are you talking about? :confused:
[Sony Xperia S, Acro S, Ion] elias234:
[MENTION=834547]letama[/MENTION]

What devices u working on these days?

I wish u can port This Dual boot to xperia z

One of the features that make xperia s better than xperia z
[Sony Xperia S, Acro S, Ion] letama:
I'm working mostly on my note 3, though I didn't have time to do anything significant on it yet.

If XZ is close to note3, boot manager won't be as easy, kernel is much bigger on these new beasts. No way to get it running on note 3 without repartitionning. And gpt partitions means that it can't be repartitionned as easily as XS :).
[Sony Xperia S, Acro S, Ion] nghiemdung:
[MENTION=3393933]steryman[/MENTION] could you make native for Jellyslim rom??

Here's the link for that rom

http://d-h.st/6FR
[Sony Xperia S, Acro S, Ion] monivan:
How could i install eXistanZ_Ultra rom and kernel on native? I can't find the file on the list. Pls help
[Sony Xperia S, Acro S, Ion] darkon11:
Is there a way to port this to Xperia p
[Sony Xperia S, Acro S, Ion] SMARTHACKER67:
help

can any one confirm that the OPEN SEMC BETA 3 NAtive is working properly on device or not??

since i saw the comment of boot option missing .
[Sony Xperia S, Acro S, Ion] vinjurr:
Android 4.4.2 KitKat MoKee ROM For Xperia S–Unofficial

Can anybody repack for dual boot MoKee kitkat rom at http://true-android.blogspot.in/2014/01/android-442-kitkat-mokee-rom-for-xperia.html

thanks:D
[Sony Xperia S, Acro S, Ion] dermaze:
Doomlord as Native Kernel

Hello,

is there a way to repack Doomlords v6 kernel for the native partition?

I ask this, because I'd like to have the 6.2.B.1.96 ROM on my native partition, but it comes without kernel.

So I've tried to repack the kernel with the provided script in the OP (long-range shot, I know...), but to no avail, I just got error messages and no output .zip

Repacking the above mentioned ROM .zip worked fine with the script.

I'd like to use that kernel, as the above combination works very good as a single-boot system so far. But any other JB kernel suitable for the .96 fw would also be ok.

I've done quite some searches, but it seems as if the relevant knowledge could be in some brains around here, and not with google ;)

Edit: Now I could repack DoomLords v06 Kernel with letama's tool, doing the same as I did before - no idea why it worked this time. I'll test it for 1-2 days, let's see if it's really fine (6.2.B.1.96 deodexed etc + DoomLord Kernel on native) ...
[Sony Xperia S, Acro S, Ion] zaidx:
Wow

I didn't know that mokee rom is available on our device

I might give that a shot :D
[Sony Xperia S, Acro S, Ion] vinjurr:
pl see i am already running on Xperia S
[Sony Xperia S, Acro S, Ion] nghiemdung:
Please anyone could make this. Really want it but can't find out to do by myself
[Sony Xperia S, Acro S, Ion] nisu4717:
Mokke as loop plz.....

If any 1 has time....
[Sony Xperia S, Acro S, Ion] S-AJAD:
any body can help me to use Repackager package ?

i can't undersand this but i want to Repackage my rom for loop boot

i think i need Noob friendly guide

sorry for my english

tnx bro
[Sony Xperia S, Acro S, Ion] S-AJAD:
+1

any body can help us ?

mokke for loop please
[Sony Xperia S, Acro S, Ion] dermaze:
Hello, and thanks for the repack!

I've tested the loop ROM and it boots up just fine, running smooth. But I cannot see the sdcard (although it's there when I boot native or enter the loop's recovery) and of course that makes it pretty useless. Seems like the problems encountered with the beta1, I guess.

Did anybody else encounter that problem? And, more important, is there a solution?
[Sony Xperia S, Acro S, Ion] rolex0815:
Sometimes a reboot might help. I encountered this problem on loop sometimes too. No way to reproduce it, but it seems from time to time the correct mount point is lost.

You can try to use a file manager with root option and look around within the directory structure. Try /sdcard or /sd or /storage
[Sony Xperia S, Acro S, Ion] dermaze:
Hello,

I've done this, and also tried to ln -s the /sd directory (that's where my sdcard has been mounted to, where is yours mounted?) onto /storage/sdcard0, but this does not work - although as su, it tells me that this system is read-only ("Mount" tells me something different).

Any hints how I could fix this?

- A workaround would be to link it with the appropriate method (which I don't know yet)

- Or to pass on the right mountpoints at bootup - but where can I edit the mountpoints? the vold.fstab does not exist in 4.4...

Are all users of OpenSEMC 4.4b3 experiencing this (when installed on loop)?

Edit: Meanwhile I could link the /sd folder to /storage/sdcard0, then e.g. TitaniumBackup also recognizes it as backup folder. But the camer just states "insert sdcard" (or something similar). When I reboot, the link is gone again (not very surprising)

... I need a proper fix here ...
[Sony Xperia S, Acro S, Ion] rolex0815:
That's bad, I'm using the native version and this works flawlessly.
[Sony Xperia S, Acro S, Ion] devillnside:
yup im facing the exact same issue with the sdcard with beta 3 on loop partition
[Sony Xperia S, Acro S, Ion] dermaze:
I think I could narrow down the problem meanwhile:

In order to mount the loop partitions (the three .ext4 files you can see on your sdcard), this partition is mounted by init.semc.rc (placed in initramfs) to the folder /sd before it can be mounted by calling "mount_all semc.fstab" (which is the way it is mounted normally, as well as in the native rom).

My guess is, that one device cannot be mounted twice, and thus the second attempt (mounting it to /storage/sdcard0) has to fail. Am I right here?

Now come the tricky part(s):

- I tried to simply symlink /storage/sdcard0 to the beforehand mounted /sd, but this did not work (booted normally, but /sdcard and /storage/sdcard0 was empty just as before)

- I tried to mount /sd earlier ("on init" instead of "on fs")with the mount-command in init.semc.rc and link the other folders to /sd. I think that's a bad solution anyway, as the mount is not handled by vold any more (this would be the standard behaviour I guess). Anyway, the system boots up normally, but the normal sdcard folders are empty (and /sd is mounted).

- I called "mount_all semc.fstab" before mounting the loop-partitions and gave the /storage/sdcard0/ path for the mounting them. Felt dirty.... ;) who knows where else the /sd folder is used in this modded version? But: system booted up, but it was not as snappy as normally. Success?? The sdcard data is finally in its right place, no /sd folder any more, BUT: The Camera and Music app do not see the stored pictures / music (plenty on the sdcard...). --- EDIT: see below ---

So I'd say I've really tried here, but now is the moment to call for some kernel / script magic: [MENTION=834547]letama[/MENTION] , you there? ;) I guess the repacking script messes up something, maybe the permissions aren't as flexible with the 4.4 system as they were earlier? Is there some link missing? I have no idea...

Attached you find the modified initramfs.loop.gz, for anyone who wants to continue the hunt or just to make clear what I described earlier. If you want to, just replace the initramfs.loop.gz in your rom zip to try it on your loop system. Of course I'll take no responsibilities for destroyed, burning, or berserking phones. It is my first time touching the kernel, and as most of you may know - first times can be messy ;)

I'll be damned!! After resetting gallery, camera and apollo in ->settings->apps and rebooting, all of my music and pictures show up in the apps!! It seems like it's done! But I'm still not sure whether I messed something else up by my modifications, so please: somebody with real knowledge about this things, look it through...

And of course the repacker script still does not work properly on the kk roms (I've tried OpenSEMC beta3 and PureSlim kk, so almost the same I guess)...

EDIT: camera is still not working, although I can see my pictures in the gallery and in the camera app (!) - it is asking for a sd-card and I cannot take any pictures... (tried to clear data, tried by wiping cache & dalvik cache, no changes)
[Sony Xperia S, Acro S, Ion] enriquettoo:
JellySlim repackaged

I have repackaged JellySlim (thread: JellySlim_FullPower** [HSD Project 4]) with Letama's tool and changing initramfs.loop.gz.

Uploaded Native: https://dl.dropboxusercontent.com/u/33953874/bm_native_BM-JellySlim4.zip

NOT TESTED.

Meanwhile, I'm trying Loop version (not uploaded yet, maybe tomorrow).

EDIT: Flashed Loop with errors (kernel+cpio size is too big), but it works :eek: (don't know if is because it flashed it over .96 Yakandu (here)

Attached recovery.log
[Sony Xperia S, Acro S, Ion] letama:
Well, tough question.

Yes, permissions are less flexible and there have been big changes regarding sdcard with kitkat. And yes, loop is relying on having internal mounted to /sd, and it could interfere with vold. However, you really want vold to work, doing it by symlink or mounting again to /sdcard will confuse Android.

logcat (from boot) should be explicit about vold problem, and you can also investigate vdc command that let you give commands to vold and see its status.

If you post a good logcat *:v from startup, I'll try to take a look.
[Sony Xperia S, Acro S, Ion] enriquettoo:
Native for JellySlim_FullPower**[HSD Project 4]: bm_native_BM-JellySlim4.zip

Not Tested

Loop for JellySlim_FullPower**[HSD Project 4]: bm_loop_BM-JellySlim4.zip

Working fine.
[Sony Xperia S, Acro S, Ion] devillnside:
i think im beginning to get what ur sayin!! gonna give this a try!!
[Sony Xperia S, Acro S, Ion] SMARTHACKER67:
repack request

can any one repack this as native and loop also please

its MIUI

http://xdaforums.com/showthread.php?t=2463579

i tried some link but links are dead.

thanx in advance :good::good: :good: :good: :good:
[Sony Xperia S, Acro S, Ion] dermaze:
Hello,

here come the logcats. I read them with "adb logcat -v long > name of problem.txt", hopefully that's what you call a good logcat. Or what did you mean with "*.v" ?

I had a look into them, but this is also the first logcat I made so far, so I have not experience there. Anyway, to me it seemed like the logcat service runs after the mounting is done, starting with trim-area things. I guess it is the process which is called right after the mounting operations in the init.semc.rc, am I right?

To the logcats: there are three in the .zip, one with the normal, repacked rom and two with the modified system, running with the modified initramfs.loop.gz I posted above.

Maybe you can figure something out!
[Sony Xperia S, Acro S, Ion] dermaze:
Hi [MENTION=834547]letama[/MENTION],

At the moment I'm trying something else, unfortunately it leaves me hanging at the SEMC logo. But I think the methodology could solve our problem in an elegant way, maybe somebody know how to modify it in a way it works. The main aspects are two separate mount calls:

- first the init.semc.rc calls "mount_all fstab.vold.semc", this should mount the sdcard under /storage/sdcard0

- then init.semc.rc executes losetup to make the /storage/sdcard0/*.ext4 files accessible as block devices

- then init.semc.rc calls "mount_all fstab.block.semc", here the block devices get mounted as /data, /system, and /cache

Even when changing the mount flag "noexec" to "exec" in the fstab.vold.semc, it hangs at the SEMC logo...

Attached you find the according initramfs.loop.gz with the two fstabs (just the old one, splitted up). Maybe I made a mistake somewhere or I'm missing a detail, shouldn't this method work? And another question, out of curiousity: why did you introduce the /sd mountpoint for the sdcard in the first place?
[Sony Xperia S, Acro S, Ion] letama:
Vold problem is there:

[ 01-18 14:29:48.699 164: 219 E/cutils ]
Failed to chown(/mnt/media_rw/sdcard0/.android_secure, 1023, 1023): Operation not permitted

[ 01-18 14:29:48.699 164: 219 W/Vold ]
fs_prepare_dir failed: Operation not permitted

[ 01-18 14:29:48.699 164: 219 E/Vold ]
Failed to mount secure area (Operation not permitted)

[ 01-18 14:29:48.699 164: 219 D/Vold ]
Volume sdcard0 state changing 3 (Checking) -> 1 (Idle-Unmounted)

[ 01-18 14:29:48.699 164: 219 W/Vold ]
Returning OperationFailed - no handler for errno 1

chown is not possible on a fat partition, I don't know why vold tries to do that with a vfat filesystem. Maybe a missing flag in fstab ?

Well, you have an interesting idea, however you won't be able to know when vold has finished mounting sdcard. It takes time as vold checks file system and sdcard won't be mounted when you will try to mount loops.

I introduced /sd mountpoint because I need internal storage mounted to be able to mount loops and I wanted to avoid any collision with vold work. Vold expects sd umounted at startup and having it mounted before for loop at same location is causing problems.
[Sony Xperia S, Acro S, Ion] dermaze:
continuing...

The last two days I tried to have vold mount the sdcard to /storage/sdcard0 before the loop devices are set up. But I just couldn't achieve this. If someone has a comprehensive list of vold / fstab flags, please let me know!

My next approach was to leave vold out, but then the camera does not recognize the external memory (although the gallery can see all the pictures there). The logcat of the camera firing up without success tells me that it reads the ExternalStorageState, which returns "unmounted". So the only thing would be to set "Android.OS.Environment.ExternalStorageState" to "mounted" (It this is the correct string, I also read about MEDIA_MOUNTED), but I don't know how or when to do this.

Maybe you have some more ideas about this, because I'm about to give up. Probably the best way would still be to have vold mount it, but for that scenario I only get the SEMC logo and cannot get any logcats therefor.
[Sony Xperia S, Acro S, Ion] letama:
Well, no idea... I'd be interested to see how things are mounted in semc kitkat on native if anyone could show me the result of "mount" after boot. It could be a simple mount option missing on /sd mountpoint.
[Sony Xperia S, Acro S, Ion] enriquettoo:
Here is it:

u0_a54@nozomi:/ $ mount

rootfs / rootfs ro,seclabel,relatime 0 0

tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,seclabel,relatime 0 0

selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0

/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0

none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0

/dev/block/mmcblk0p12 /system ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0

/dev/block/mmcblk0p13 /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0

/dev/block/mmcblk0p14 /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0

/dev/block/mmcblk0p10 /data/idd ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier,data=ordered 0 0

/dev/block/vold/179:15 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:15 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

u0_a54@nozomi:/ $
[Sony Xperia S, Acro S, Ion] letama:
[MENTION=5435249]dermaze[/MENTION], I'd try to mount internal storage to /sd like the original script does, with adding uid=1023,gid=1023 as option, something like:

mount vfat /dev/block/mmcblk0p15 /sd utf8,uid=1023,gid=1023
[Sony Xperia S, Acro S, Ion] nisu4717:
Can some1 give me

Eos 4.0 4.2.2 version as netive..plz.

Links is in index thread of development.
[Sony Xperia S, Acro S, Ion] rolex0815:
[MENTION=5435249]dermaze[/MENTION]

What happens if use the initramfs.loop.gz attached?

It's the one I'm using to run stock ROM .96 on loop.

So just replace it within the flashable zip.
[Sony Xperia S, Acro S, Ion] dermaze:
Hello, and thank you for the files!

I had a short look into the init files, there are quite some differences. I'll try the quick&dirty method (copy & run), but most likely I'll have to adjust some things. Anyway, there are some nice ideas there, for example did I also want to use the "on property" triggers, and with those examples it might finally work :)

But I can try it this night earliest, let's see...

EDIT: I've tried your proposed method, however after getting to the cyanogenmod boot animation, it crashes rather hard and reboots. But thanks for the effort!
[Sony Xperia S, Acro S, Ion] dermaze:
Hi,

here's the loop and the native version of EOS 4.0 4.2.2 rom.

I have not tested them, so please report your findings (success / problems).
[Sony Xperia S, Acro S, Ion] dermaze:
Hello,

that's it!

I almost cannot believe it, everything is working now - only because of those flags by which the camera as well is granted write access. When looking at the logcat (attached below), you can see that vold gives up on mounting sdcard0. So it's not some "sdcard mounted" flag in the android system, leaving me with the conclusion it has to be the write permission. Or are there any other interpretations?

For everyone with the same problem but no desire to unpack / modify / repack the initramfs: Here you can have the Kernel / Initramfs only as a flashable .zip. It will say "DoomKernel", but that's only because I used his Kernel.zip for that :p

Of course the right thing to do now would be to change the repacker script, but I'd like to leave this to [MENTION=834547]letama[/MENTION].

Thanks to all of you for helping!
[Sony Xperia S, Acro S, Ion] letama:
Cool!

The options only specify which linux user is mapped to vfat filesystems, so all files on vfat mounted like that will appear to belong to that user. If the user is the wrong one, permissions are messed up.

I can't really adjust repackager script for that, it's a kitkat specific issue and could be even build dependent, user id depends on android build...
[Sony Xperia S, Acro S, Ion] SMARTHACKER67:
some one please. i really need

can any one repack this as native please

its MIUI

http://xdaforums.com/showthread.php?t=2463579

i tried some link but links are dead.

thanx in advance :good::good: :good: :good: :good:
[Sony Xperia S, Acro S, Ion] nisu4717:
I tried loop version.working ok.but facing a problem of airplane mod.it gets on off on off itself.but I thought it is a bug if rom.same problem in slimbean buildes 7 and 8 without dual boot.

Thanks
[Sony Xperia S, Acro S, Ion] dermaze:
Hi, [MENTION=834547]letama[/MENTION]

the ID 1023 belongs to media_rw, I guess this will be the same on every device? I tried to mount the sdcard with "media_rw" instead of "1023" as IDs, but this did not work (hang on OpenSEMC logo).

So if we found a way to read the number-ID belonging to media_rw, you might be able to include this into your scirpt, after all? But I don't know how to do that, can we work with variables in the init.rc?

My method to find it out was to enter the following in a console, which returns the desired numbers:

su root
su media_rw
id

But is it even possible to parse anything in init.rc? Maybe outsourcing it to a .sh script may work...
[Sony Xperia S, Acro S, Ion] dermaze:
Hi,

here's the native and the loop version of MIUI v5. Both have not been tested by me, so please report your findings.
[Sony Xperia S, Acro S, Ion] SMARTHACKER67:
Friend the native version i have tested is not working. Rom not booting i am requesting you look for the possible solution.

Thank you for repacking.

When i open zip i found these two files seems like two files missing that are mostly comman in all zips i have seen some called zimage and.xxxxxxxxx.Gz file

http://www.4shared.com/photo/UQXAQUJPba/Screenshot_2014-01-22-21-33-19.html
[Sony Xperia S, Acro S, Ion] SMARTHACKER67:
help

i am having problem

whenever i tried to flash the any new native or loop rom the rom flashes successfully and boots up for the first time but after restating the device.

nothing works and stuck on opensemc logo for native rom and stock rom on loop partition stuck on repair sign.

for loop rom i have no other option rather than deleting partition recreating them and again freshly installing the rom.

but for native i am not able to find any solution and same happens. if i restore the backup system either on loop or native.

i always wipe everything before installing (dalvik,cache,system,data). all system boots up for first time and after rebooting they wont.

is there any solution [MENTION=834547]letama[/MENTION]

thankx in advance
[Sony Xperia S, Acro S, Ion] dermaze:
Hello, you're right, the kernel is missing - no wonder nothing good happens when you try to boot ;) I don't know how you could boot into any system like that anyway, I guess your old kernels are still in place and trying their best. But of course that messes up anything.

Attached you find DoomLord's Kernel (it is also the .96 based one, so it should work) for native and loop partition.

I'm using the native version together with .96 deodexed stock fw, there it's perfect. For the loop version, I don't know - try at your own risk.

Of course, all the credits go to DoomLord for his kernel!

Just flash it from the appropriate recovery (native or stock I mean), you should not have to re-flash your MIUI rom. If there are problems - make a clean install nevertheless.
[Sony Xperia S, Acro S, Ion] SMARTHACKER67:
thanx friend

thanx bro its working perfectly(native) :good: :good:
[Sony Xperia S, Acro S, Ion] SMARTHACKER67:
error help

i am getting this error whenever i am trying to flash any flash-able zip.

in the loop rom only i am getting this error.

BTW im using stock jelly bean rom on loop.

my recovery log

http://www.4shared.com/file/6rHwpM3Iba/recovery.html
[Sony Xperia S, Acro S, Ion] letama:
Can you upload to pastebin or elsewhere ? Don't want to register with 4shared...
[Sony Xperia S, Acro S, Ion] SMARTHACKER67:
sorry

i am so sorry for that . i completely forgot that new user has to register before downloading.

anyways

heres link https://app.box.com/s/8v45ebr6772e8w8i4073

BTW after 5-6 times restart and switching from loop kernel to native . now am able to flash the same zip files but i got this issue many times .

hope u will come up with solution.

thanks in advance. :good: :good: :good:
[Sony Xperia S, Acro S, Ion] letama:
Well, I'm not sure what's the problem exactly. However, I noticed that you installed zip from /sd directory, you should avoid using this one and try to use /sdcard/ instead. I use /sd/ internally to map loops, TWRP is using /sdcard to mount internal storage.
[Sony Xperia S, Acro S, Ion] SMARTHACKER67:
thank you so much

thank you so much for solution. i will take care of that from now onwards

:good:

:good:

:good:
[Sony Xperia S, Acro S, Ion] letama:
You tried and it worked ?

I'm not sure this is the problem, it's just the only thing that looked strange in the logs.