[SuperR Kitchen] thgxda:
Hi,

so first post for me in the forum ...

I have the very same problem with CM13, I was not able to get it running in any way, so I ended up here, to build a modified ROM. But I don't get it, see next post :(

I'll write an other post about my efforts getting init.d work on CM13 and put a link in here, to not to be OT!

Kind regard, thgxda

---------- Post added at 01:19 PM ---------- Previous post was at 12:37 PM ----------

Hi everybody,

reason for all the work is, that I want to get crond-support on my smartphone, for this I need a working init.d, what seems not be the case in the lastest cm13 builds for my device.

First try, building a ROM was "manual" with the bootimg_tools, it looked "successful", but I was not able to boot with the ROM at all.

Finally I ended up here, and while the program looks really great, I'm not able to use it correctly :(

The ROM I am building is just some MBs instead of beeing mostly the same size then the original, so probably I'm doing s.th. wrong and hopefully s.b. has an advice for me.

That's what I was doing:

What Kitchen version?

- v0.9.6.7

What Linux are you running?

- openSUSE 12.3 x86_64

What device are you working on (make/model)?

- Motorola Moto G 4G xt1039

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)

- cm-13.0-20151215-NIGHTLY-peregrine.zip

What Android version?

- Android 6.0, CyanogenMod 13.0

What perm method (set_perm, set_metadata, sparse_dat)?

- sparse_dat

What did you do after extracting and before building?

- nothing

Were there errors on the screen if you scroll up in the terminal?

- no

Can you send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)?

- No links allowed for me right now:

download.cyanogenmod.org -> cm-13.0-20151215-NIGHTLY-peregrine.zip

sha1: 40e3a755f0cadec9e375bafe639b203b2bd01cc1

So first try building a new ROM without modifying anything.

Starting SupeR's Kitchen as root, does not work as user, create project:

# ./superr

1) Create new project
Enter new project name (spaces will be replaced with _):
cm13_peregrine_151215tg

Copy latest CM-image to my project:

# cp -p cm-13.0-20151215-NIGHTLY-peregrine.zip SuperRs_Kitchen/superr_cm13_peregrine_151215tg/

Extract the ROM:

4) Extract for new ROM
Should we extract cm-13.0-20151215-NIGHTLY-peregrine.zip to cm13_peregrine_151215tg? y/n y
Extracting system.new.dat, system.transfer.list, and boot.img ...
.....
This ROM is Lollipop or beyond.

Would you like to use sparse dat images (recommended)? y/n y

The answer to this question will show when flashing
the zip and will be converted into the zip name when
the zip is built.

What is the name of your zip?
cm-13.0-20151215-NIGHTLY-peregrine_tg

->
CURRENT PROJECT: cm13_peregrine_151215tg
ANDROID VERSION: 6.0.1
...

And finally building a "new" one:

CURRENT PROJECT: cm13_peregrine_151215tg
ANDROID VERSION: 6.0.1

...
8) ROM tools

...
1) Deodex ROM (CURRENT: Deodexed)
2) Root/Unroot ROM (CURRENT: Rooted)
3) User app support (CURRENT: Add support)
4) Change perm type (CURRENT: sparse_dat)
5) Asserts: Add/Change devices (CURRENT: cm_peregrine)
6) Debloat Menu
7) Build Menu

...
1) Build full ROM Zip

Should we zipalign before building the ROM? y/n n

Choose system partition detection method
1) Device through adb shell (recommended)

...
cm-13.0-20151215-NIGHTLY-peregrine_tg.zip has been created in cm13_peregrine_151215tg. Enjoy!

Press ENTER to return to ROM Tools

And the "result":

ls -lh SuperRs_Kitchen/superr_cm13_peregrine_151215tg/cm-13*
-rw-r--r-- 1 root root 5,9M 16. Dez 11:42 SuperRs_Kitchen/superr_cm13_peregrine_151215tg/cm-13.0-20151215-NIGHTLY-peregrine_tg.zip
-rw-r--r-- 1 root root 276M 16. Dez 00:06 SuperRs_Kitchen/superr_cm13_peregrine_151215tg/cm-13.0-20151215-NIGHTLY-peregrine.zip

So while the original CM13 ROM has a size of 276MB, the new one is only 6MB big, so probably I'm doing s.th. wrong.

Any idea how to solve this?

Thanks a lot for your support,

kind regards,

thgxda

---------- Post added at 01:28 PM ---------- Previous post was at 01:19 PM ----------

Dear MODs,

please could you separate this two messages?

It is just not indented to have them together, but I'm not allowed to do so!

Thanks a lot, thgxda