Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,805,892 Members 42,868 Now Online
XDA Developers Android and Mobile Development Forum
View Poll Results: Since it's a community project , what name do you want for the rom?
OrmusRom 18 30.00%
OrionRom 20 33.33%
SigmaRom 4 6.67%
DroidRom 4 6.67%
ZeusRom 9 15.00%
Other 6 10.00%
Multiple Choice Poll. Voters: 60. You may not vote on this poll

[WIP][4.4.2 PORT][SAMMY]OrionRomV1b[Project]

Tip us?
 
Ganjax
Old
#321  
Ganjax's Avatar
Senior Member
Thanks Meter 151
Posts: 505
Join Date: Jan 2011
Location: Piotrków Trybunalski
Can't u edit dorimanx kernel for make it work? There are 3 versions, v8 for stock roms, v9 and v10 for aosp/cm bases, it's possible to complie i think. But i can be wrong.
Good News Is No News!
 
PolishVodka
Old
#322  
Senior Member
Thanks Meter 1,932
Posts: 770
Join Date: Oct 2012
Quote:
Originally Posted by I98 View Post
Hello,
I know that you have a kernel problem, but since the note 2 is xhdpi doesn't that mean that if the rom were bootable most things would be larger than they should be?As for the boot img I tried unpacking it but kept on getting errors.
Thanks
XHDPI resolution doesn't matter couse everything is scaled to DPI values (for S2 default 240), so everything should be OK.
For kernel - first must be a sure, which changes are needed in ramdisk side. Unpack Note 2 kernel (if u can), and unpack any S2 kernel for 4.4.X for initramfs (this script should do this: https://github.com/davidmroth/Extract-Kernel-Initramfs ).
Than you need to unpack boot.cpio (ramdisk) via command - cpio -id < ../boot.cpio , do a necessary changes and repack again to .cpio archive - find * | cpio -o -H newc | gzip > ../boot.cpio.gz
gzip -d boot.cpio.gz
And now you have initramfs for stock KitKat ROM, but you must now download any kernel source you want for I9100 and build kernel with: CONFIG_INITRAMFS_SOURCE=/directory to initramfs folder on your PC.
Everything you must do on Linux.
The Following 5 Users Say Thank You to PolishVodka For This Useful Post: [ Click to Expand ]
 
gerryS2
Old
#323  
Member
Thanks Meter 82
Posts: 90
Join Date: Apr 2013
Location: Avellino
Hi to all, I have a suggestion to overcome the problem of the boot. Since a while I'm working on a port of 4.2.2 of S2 plus through the insertion of missing methods, classes, and even libraries in the framework folder. For now I managed to bring: TwLauncher, AccuweatherWidget, Calculator, JobManager, MusicPlayer and ecc. . The suggestion is to take a rom 4.4.2 aosp or other and insert the file twframework.jar and twframework-res.apk in framework file. I noticed that the twframework does not need to be declared in the boot, but you must enter a touchwiz.xml file in the folder /system/etc/permissions/ . With this system you can install apps of S5 that require TouchWiz library.
I now do not have time to make this attempt, but if someone wants to can try my idea and let me know if it works.
The Following 4 Users Say Thank You to gerryS2 For This Useful Post: [ Click to Expand ]
 
I98
Old
#324  
Senior Member
Thanks Meter 108
Posts: 155
Join Date: May 2013

 
DONATE TO ME
Quote:
Originally Posted by gerryS2 View Post
Hi to all, I have a suggestion to overcome the problem of the boot. Since a while I'm working on a port of 4.2.2 of S2 plus through the insertion of missing methods, classes, and even libraries in the framework folder. For now I managed to bring: TwLauncher, AccuweatherWidget, Calculator, JobManager, MusicPlayer and ecc. . The suggestion is to take a rom 4.4.2 aosp or other and insert the file twframework.jar and twframework-res.apk in framework file. I noticed that the twframework does not need to be declared in the boot, but you must enter a touchwiz.xml file in the folder /system/etc/permissions/ . With this system you can install apps of S5 that require TouchWiz library.
I now do not have time to make this attempt, but if someone wants to can try my idea and let me know if it works.
Hello
The boot.img has to be unpacked and modified in order to run properly, but the problem is the boot.img is hard to unpack and I don't know how to do so, if we manage to unpack it,it will be the last step in porting.
Thanks
The Following 2 Users Say Thank You to I98 For This Useful Post: [ Click to Expand ]
 
kris_l
Old
#325  
Junior Member
Thanks Meter 7
Posts: 28
Join Date: Jun 2012
Quote:
Originally Posted by I98 View Post
Hello
The boot.img has to be unpacked and modified in order to run properly, but the problem is the boot.img is hard to unpack and I don't know how to do so, if we manage to unpack it,it will be the last step in porting.
Thanks
Why do you try to unpack boot.img instead of build kernel from scratch. You can build i.e dorimanx kernel and it would be much easier to do than unpack just boot.img. Tried to build Gustavos but there is a problem with initramfs and you get bootloop on it. Why don't you ask Cybernetus or computoncio for help. They build dorimanx kernel so it wouldn't be problem for them to make few modifications to it and build it for us.
The Following 3 Users Say Thank You to kris_l For This Useful Post: [ Click to Expand ]
 
ipapun4545
Old
#326  
Senior Member
Thanks Meter 15
Posts: 116
Join Date: Aug 2012
Location: Bhubaneswar
is this project dead??
 
ahmedelhofy
Old
#327  
ahmedelhofy's Avatar
Senior Member
Thanks Meter 184
Posts: 361
Join Date: Apr 2012
Location: Shebin El-Koum
Quote:
Originally Posted by ipapun4545 View Post
is this project dead??
Probably..... :/

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes