[HOWTO] build eOS in old fashioned way with breakfast -- now with interactive script

eOSWiki HOWTOs
82

Don’t know. For me it looks that the kernel won’t load.

I’m just building a lot of Samsung roms. If I will get access to the roomservice.xml I can try building

1 Like
83

OK - Thank you.

My S4 GT-I9505 Galaxy never showed the required ‘Developer Options’ as described in the generic tutorial.

As a result - I was forced into NEVER allowing reboot after any flash or installation, and manually forcing into recovery mode on first start. Then reboot - This was done after both installing TWRP, and also after installing E.

In this fashion, the installation was perfect.

If not carried out in this way - the ‘phone’ would override the flash and self recover.

So - just out of interest - Do you see any logic in my previous suggestion?

Regards

84

I wipe, I sideload and I click on Reboot System. Nothing special. No problem with the LineageOS 16.0 but the /e/ Pie doesn’t boot at all and it directly goes into download mode, not in recovery mode.

Here is what I used, based on this one.

By the way, why everybody else has a roomservice.xml file with only a few lines, and mine has a lot of elements ? Everything is useful ? Thanks !

1 Like
85

Your roomservice contains all.stuff for a lot of devices, for twrp snd for removing sources.

The xml should be cleaned before using

1 Like
86

@harvey186 has some significant points - and hopefully this may indeed cure the problem.

However - If you still have issues after clean-up, you could try -

Shutdown after new side-load.
Power-up into recovery-mode.
First-time boot the new OS / reboot and allow the new OS to start.

Whatever happens - do please update us on your progress :slight_smile:

All the best!

87

I never use sideload. I’m pushing the eOS.zip to the device and flash it via twrp

1 Like
88

Sadly I don’t know how far I need to clean :yum:
I made two versions :

Very clean : https://del.dog/gprimeltexx-roomservice-very-clean.txt
Very very clean : https://del.dog/gprimeltexx-roomservice-very-very-clean.txt

(The construction of the roomservice.xml file is really something I need to work on, I don’t know what is really needed or not and that will be my main problem for future build for other devices)

89

Let me check tommorow.

In roomservice you have to add the location of sources which are not in LOS sources available.
It’s normally 3 or 4 things
Device tree
Kernel
vendor tree
And sometime device settings

And I have learned Samsung devices are needing much more extra stuff

90

never seen such a chaotic xml as the source one. here I have made it clean
https://del.dog/roomservice_gprimeltexx.txt

Your both are looking also not bad, but I have changed it to the ‘normal’ layout

91

Thank you ! I will try with this. (It might take 2 or 3 days)

92

I’m just building. On repo sync I have found some issues with roomservice.xml.
Here that one with which I’m building now
https://del.dog/gprimelte_new.txt

1 Like
93

My build finished successful https://ecloud.global/s/wi9q9iTFgxM7TDp
could you check if it is booting ?

94

Oh it’s booting ! I can see your “android” boot animation (and now the modifications you made) :yum:

So I guess the issue was the roomservice.xml… I need to learn more about this because if I’m not able to build for a device I own, no need to lose time to build non-working builds for others.

By the way, for my j5nlte I use the “full of thing” roomservice.xml but it worked. I don’t know if I have to keep it or if it’s better to do a clean roomservice.

Thank you, I’m now building with your roomservice in order not to have a custom build (on Windows thanks to WSL, I finally managed to make it worked)

1 Like
95

Nice. hope your build will also work. good luck

2 Likes
96

what is the device name ? Galaxy Grand Prime (SM-G530FZ) or ??

97

Product name : Galaxy Grand Prime
Model : SM-G530FZ
Codename : gprimeltexx

1 Like
98

I used the same roomservice than you (the “new” one) but it’s still not working… I can’t figure out what you did differently than me.

99

No build error.? Crazy

100

You are using 1312.sh? ?
Signature spoofing = No?
All others = Y

This signature spoofing could be the issue

Or do you use 161.sh?

101

For the first time, no error at all from the beginning to the end. (4h of sync + 13h of build process)

I use 161.sh

But the script doesn’t work in WSL, so I have to write manually every command that are in the 161.sh file.

I’m sure it’s not a problem because when I was building in a virtual machine with the script working, the final build wasn’t booting, it was the same problem.

The only thing I changed compared to you is the CCACHE size from 100 to 50.