Hey guys,
i'll try to get an Ubuntu Touch port running on my Tablet.
I've taken UbPorts 5-1 branch and synced it with cm12-1 cm sony source. The cm files build fine.
For the ubuntu files i removed ant-wirless to build the files.
After build finished sucessfully i added the ubuntu specific kernel configs and build again. Without any erros
Now i want to boot that baby but i don't get past the Xperia Bootloader screen.
I can't enable last_kmsg to debug the deivce because i get build errors otherwise.
So what i think of at the moment is that there are some wrong parameter for the sony boot.img ... but not sure about that.
Maybe somone of you can help me bring up that baby for us all.
Cheers
Moritz
Hey, did you get any luck with this? I am currently trying to port it to the Z3
CedArctic said:
Hey, did you get any luck with this? I am currently trying to port it to the Z3
Click to expand...
Click to collapse
no not really
Hahaha I posted before I found you on freenode xD
Related
Hey guys!
Android is quite the amazing OS.
We all love flashing Custom ROMs
on our fancy devices, and many of
us enjoy the challenge of making, or
porting an OS from another device
to our own.
I made this thread in hopes that we
could get together, collaborate,
and help one another on our Ports
for the AT&T S4.
Knowledge is power, and while I
don't personally have a strong
background in development, or any
actual education with the Android
OS, I have learned soo much from
the amazing people here, and from
the various threads, guides, and
tutorials on XDA.
Let's get stuff booting as a team!
-------------------------------------
Porting Projects:
-------------------------------------
⇨ ColorOS V2 -
└http://forum.xda-developers.com/showthread.php?t=2745676 (WIP)
⇨ Lewa OS V5 - (WIP)
⇨ Flyme OS V3 - (Failed to Flash)
⇨ MoKee OS - (Finished)
⇨ IUNI OS -
⇨ Ubuntu Touch -
Reserved - just in case.
Started a BaiduCloud Port which is now finished going to flash if no testers are available. Will post results here.
EDIT: Hung at bootscreen - pulling a log tomorrow!
Thanks to @kylecore and @mauserruger for testing!
Adizzzle said:
Started a BaiduCloud Port which is now finished going to flash if no testers are available. Will post results here.
EDIT: Hung at bootscreen - pulling a log tomorrow!
Thanks to @kylecore and @mauserruger for testing!
Click to expand...
Click to collapse
Got stuck at boot screen as well, unfortunately couldn't pull a log as I had to restore and go to bed asap for work today haha
ColorOS Github Info
You can merge this Pull Request by running
git pull https://github.com/APAR1992/build patch-1
Or view, comment on, or merge it at:
**https://github.com/ColorOS/build/pull/2
Commit Summary
Update*util.mk
File Changes
M*util.mk*(4)
Patch Links:
https://github.com/ColorOS/build/pull/2.patchhttps://github.com/ColorOS/build/pull/2.diff
hey buddy
im trying to port Flyme OS from Meizu MX3 to i9500
but im having with patching the kernel
i cant get BOOTCLASSPATH from MX3 kernel
maybe they used u boot
AL_IRAQI said:
hey buddy
im trying to port Flyme OS from Meizu MX3 to i9500
but im having with patching the kernel
i cant get BOOTCLASSPATH from MX3 kernel
maybe they used u boot
Click to expand...
Click to collapse
I'm gonna look into it after work.
Mind sending me the boot.img
And I can scour through it?
Also didn't you create the Prism Color ROM?
Was wondering how you made that using
TW as a base.. I can't get mine to boot!
Cheers!
Adizzzle said:
I'm gonna look into it after work.
Mind sending me the boot.img
And I can scour through it?
Also didn't you create the Prism Color ROM?
Was wondering how you made that using
TW as a base.. I can't get mine to boot!
Cheers!
Click to expand...
Click to collapse
boot.img
http://pc.cd/iP5
no i modified chinese version
Smali editing is very time consuming
Hello everybody. i serached the net a bit and found this guide on how to port CM11 to our devices
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
my phone is still on service (two weeks now )
but i thought before i get it back if someone wanted to try to make it happen.
i wouldnt say im that much of a developer so i think theres people out there that can make this happen faster than me.
anyway i thought to start this thread so people can try it out and talk about what we have to do and help people out with the progression.
Help appreciate
invaderjohn said:
guide on how to port CM11 to our devices
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
if someone wanted to try to make it happen.
i wouldnt say im that much of a developer
Click to expand...
Click to collapse
Any help is greatly appreciated!
I have set up a ubuntu box and got the cm sources.
I followed the instructions to build the device files from boot.img
Tweaked the BoardConfig.mk and can build recoverys from source now using the stock kernel.
Only problem with this is the 'dtb' part of the recovery.img.
I use Android Image Kitchen to copy the original recovery dtb to the ones i have build.
[Q]Can anyone tell me how to build dtb in the recovery at build time?
I have downloaded the android and kernel source from LG for D620.
Source from LG
[Q] Can anyone tell me how to merge them with the CM source?
In general i need some help to build the kernel from source, the instructions in the LG source don't work for me.
Zaaap
Zaaap72 said:
Any help is greatly appreciated!
I have set up a ubuntu box and got the cm sources.
I followed the instructions to build the device files from boot.img
Tweaked the BoardConfig.mk and can build recoverys from source now using the stock kernel.
Only problem with this is the 'dtb' part of the recovery.img.
I use Android Image Kitchen to copy the original recovery dtb to the ones i have build.
[Q]Can anyone tell me how to build dtb in the recovery at build time?
I have downloaded the android and kernel source from LG for D620.
https://www.lg.com/global/support/opensource/opensourceList?types=NAME&search=d620
[Q] Can anyone tell me how to merge them with the CM source?
In general i need some help to build the kernel from source, the instructions in the LG source don't work for me.
Zaaap
Click to expand...
Click to collapse
is this any help for you?
http://forum.xda-developers.com/showthread.php?t=1748297
and perhaps you can find a solution on the dtb here?
http://forum.xda-developers.com/showthread.php?t=2428117
Hi guys,
I bought this device a week ago, highly impressed with it.I'm not interested in tweeking it yet as I'm trying to get my lg o3d also a working cm11.I do follow this forum all the time and also leading as I mess around with my old phone, but if I know something I would try to help. To add sources to cm try this guide, its most recent and very helpful.
http://forum.xda-developers.com/showthread.php?t=2814763
:thumbup:
Sent from my GT-i8190 using XDA Free mobile app
Hi everyone, who still browses these threads.
It's pretty obvious that development for our devices is practically dead. But as I noticed pretty recently - devices like Xperia T or S III mini are one of the first to get Lineage OS. I believe someone spoke about starting new development for Xperia P and I'm interested in any news. Also, I have two Xperia U devices laying around so I'd be willing to help out. Tell me, what you think. Can we push P, U, Sola or Go any further? It seems like a fun challenge to me...
The sony devices with novathor chipset i almoast dead duo to the low chip power an some developers have left this phones ... but are some developer like hakx20 is still working on cm12.1 and lineage 13 for xperia p and kebabra10 a rusian developer is trying to build lineage 14 for xperia p ... i hope to get a bugles lineage 13 on my phone
@HiR3x thanks for mentioning me but well kadabra10 gave up already and well im working on Oreo which is almost done just need to get working boot.img. But well yeah this is just for Xperia P and well once i got it booting i will release all the device tree sources so other devs can use them.
---------- Post added at 06:17 PM ---------- Previous post was at 05:58 PM ----------
thedeermaster said:
Hi everyone, who still browses these threads.
It's pretty obvious that development for our devices is practically dead. But as I noticed pretty recently - devices like Xperia T or S III mini are one of the first to get Lineage OS. I believe someone spoke about starting new development for Xperia P and I'm interested in any news. Also, I have two Xperia U devices laying around so I'd be willing to help out. Tell me, what you think. Can we push P, U, Sola or Go any further? It seems like a fun challenge to me...
Click to expand...
Click to collapse
If you have 2 Xperia U you could be a tester if you want but well still need to finish oreo then we can test
And to answer the second question then yes we can push our devices a lot more then LP yeah sure we didnt get MM or N but well with help of @ChronoMonochrome i pushed the device a lot and well i got an zip file of Oreo that will 90% work but well i still didnt get working boot.img which im working on i had a holiday for few days because Christmas and all that stuff but well i need to start working on it again.
So Plan is like this:
1. Working boot.img with disabled SElinux
2. Test the zip
3.5. If it doesnt boot find a fix.
4. Fix bugs
The problem is that i needed to delete entire SEpolicy stuff in device tree to get it compile because it wasnt updated from LP and well MM changed a lot of SElinux stuff so the first thing to do is to disable SElinux totally in kernel if that boots up then we can move on and start to create SEpolicy again from scratch (I could use some help on creating the SEpolicy).
And once thats done fix the bugs that were introduced in Oreo bringup.
Also i know 8.0 is not up to date but well once i get this booted up i will surely download LineageOS15.1 sources and build them.
So what i can say at the end is that its not 100% sure that we will get Oreo running but well its 90% possible that we will get it booted up.
So just wait its gonna take some time since im the only dev doing the work.
Hi Guys,
I have found cm12.1 and cm13 for our Xperia P in a Webstite.
Cm12.1 is really stable and works like a charm.But Cm13 has more Bugs like Camera,Wlan etc.
Lets start
Installation - CyanogenMod 12.1
Next, you need the CyanogenMod ROM.zip, the appropriate GApps, and the corresponding boot.img - which also contains the Custom Recovery TWRP to flash and successfully boot the Android 5.1.1 based ROM. Copy the CyanogenMod 12.1 ROM.zip to Euner Xperia P, and reconnect it to your PC in fastboot mode, as described in the previous section. For the next step, the boot.img must be in your fastboot folder. Opens the input prompt and returns there
PHP:
Fastboot flash boot cm121_boot.img
on. Next, you reboot your Xperia P by either turning the device off and back on again. Or the command in the input prompt
PHP:
Fastboot reboot
Or use Flashtool for flashing of kernel
. Once the SONY label appears with the graphic of the CyanogenMod STE project, press the volume down and power button several times to reboot the device. Swiped at the start in the query to the right to allow changes to the system partition. Now select the menu item "Wipe> Advanced Wipe" and tick "System, Data, Cache" and "Android Secure" and confirm the selection by swiping again. To complete the installation, go back to the Install menu and navigate to the location where you previously copied the ROM and GApps. Flashes them one by one and reboots the Xperia P.
The first boat takes up to 10 minutes, and ends in the menu for the initial setup, as you are used to with a new device. Congratulations, you have successfully installed CyanogenMod on your Xperia P! Bold among you, can also try the
Installation - CyanogenMod 13
It is same as CM12.1
CyanogenMod 13, which is based on Android 6, but is still in an early development phase.
Credits
@Xperia-STE Team
@smartphone-guru.
I tried_ this version of cm12.1 its most stable than any other version but not very fluent in use.
But almost perfect for dailyuse
GAPPS error
I have flashed cm12.1 into my LT22i. But have an issue with GAPPS. Play store isn't lunching and it keeps closing up. Otherwise it's good rom, UI felt like butter
sz_ashik said:
I have flashed cm12.1 into my LT22i. But have an issue with GAPPS. Play store isn't lunching and it keeps closing up. Otherwise it's good rom, UI felt like butter
Click to expand...
Click to collapse
You have to install Gapps via cmw again. The best one is open gapps
CM12.1 Works perfectly!, I have not yet seen the first bug
jao6622 said:
CM12.1 Works perfectly!, I have not yet seen the first bug
Click to expand...
Click to collapse
is it better than cm11 final (m12)?
Hi, I gave to my brother my old Xperia P, and I wanted to upgrade to KK because is almost the most bug free (just A2DP not working that is important to me), and I wanted to know the bugs for lollipop if someone can give that information. Thanks!
Enviado desde mi Xperia Z2 mediante Tapatalk
Dagalur said:
is it better than cm11 final (m12)?
Click to expand...
Click to collapse
sorry , I don't have tested that rom :s
This ROM is old and newer build are already out but latest is 20161002 i think . There is link https://drive.google.com/drive/u/0/folders/0B4AOy62JMc5gaUpYbUFMVkdGRUk those are build by @CBNUKE i will download cm12.1 source and compile at least the latest source if it will even compile since i tried to fix cm13.0 and cannot make it to compile but i will try harder and maybe one day i will do it but for now i have holidays so i will compile cm12.1 hopefully. For now use CBNUKE build.
Bugs
Meloferz said:
Hi, I gave to my brother my old Xperia P, and I wanted to upgrade to KK because is almost the most bug free (just A2DP not working that is important to me), and I wanted to know the bugs for lollipop if someone can give that information. Thanks!
Enviado desde mi Xperia Z2 mediante Tapatalk
Click to expand...
Click to collapse
Camera Recording is Sometimes not working
A2DP totally not working
NFC not even recognized by system
but other things work.
---------- Post added at 10:21 PM ---------- Previous post was at 10:18 PM ----------
Dagalur said:
is it better than cm11 final (m12)?
Click to expand...
Click to collapse
Well its stable fast and usable for daily use but dont know if its faster but its good ROM.
---------- Post added at 10:32 PM ---------- Previous post was at 10:21 PM ----------
Dont expect that we will ever get CM13.0 on Nypon cause of hard building part and that BT is disabled because if its not u will get boot-loop.
i would need a dev that already ported a rom to help me with this.
Its not easy to port it.
Any help from a dev or porter is needed to make CM13.0 to work cannot do it on my own.
Good and bad news
First good news : i have managed to build lineage OS 13.0 and not bad news TWRP looks ugly bad text and the entire UI is not right how it should be and next problem rom is not bootable after kernel screen there is no boot animation just black screen forever . But i will try to fix it i updated TWRP to 3.0.2.0 and still the same UI problem so probably Kernel Issue but weird that i didnt even touch kernel source and still problem.
Thats it for now I will try to fix it.
And if anybody who have experience in this can help me i will be happy.
Maybe @CBNUKE will have spare time to help me with it.
Thanks.
Update on Development (Not yet working but close)
Found the problems source: I did forgot to patch the source on my first build so of course it cannot even boot. But now i little bit screwed my source code of lineage OS by trying to find solution to errors that popped out by applying patches.
So will re download source and hopefully after patches i will get working bootable ROM (Really Hopefully)
I will post a new Thread about it if i get at least basic stuff working.
And of course i will post the ROM itself if it will work.
And again any help from somebody willing to help and knows basic stuff about ROM porting will be Welcome.
OK not Working but here is it.
Test on YOUR OWN RISK.
IM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE OR IF YOU GET BOOTLOOP !!!!!!!!!!!
SO IF ANYTHING BAD HAPENS TO PHONE IM NOT RESPONSIBLE FOR IT !!!!
MAKE BOOT AND SYSTEM BACKUP BEFORE FLASHING !!!!
I have builded the ROM with patches but the same errors remain like bad UI in TWRP and not bootable system it will not even show Boot Animation but if anybody want to test it here is the ROM:
HTML:
https://ufile.io/un7oe
.
i have some patches that i havent applyed so will apply those and see what errors will it fix.
And if anybody flash it and know this errors then please tell me how to fix them
EDIT: added another patches like build patch and external_icu patch hwcomposer patch libhwui patch ste mutimedia patch (3 of them) and still not even a boot screen im woried that i will not even make this rom bootable
EDIT2: maybe found a way to fix it i probably need edited frameworks and system/core folder so going to do this few days later then will post and update if its was sucess or again a fail.
So i downloaded cm 12.1 source and will build daily build for this device until i figure out what the hell is wrong with Lineage 13.0 and cm 12.1 build will come out in few days need to configure the source for our device.
EDIT: I dont want you to be unhappy but there is like 1% change that i can fix all the problems in CM13.0 without a good team of devs and testers i cant do anything so dont expect ever daily runner baser on CM13.0 or even basic stuff working on it im student 17 years old yes i have a lot of C experience 9 years but thats doesnt change that i cannot do everything alone or with help of @AGONTUK its just lot of stuff to fix mainly boot so if anybody with some experience in this can help i will be happy.
i have all needed sources on my github so if anybody can help do it on github: My Github.
Have first build of CM 12.1 but i can see boot animation this time but it doesn't boot yet but another biiiig problem is no TWRP.
Main priority is TWRP so faster I can fix it the better: Probably will use android 5.1.1 repo TWRP and update to 3.0.2.0 TWRP if this will not help then maybe it's releated to not bootable system maybe have a fix but it needs more time.
And second priority is bootable system: I might have solution to this one but not totally sure.
Third priority after we have bootable using ROM is to make it fast:
1. Linaro instead art.
So in few days or week or so will post update how it's going. Maybe sooner if I get working build.
Haxk20 said:
Have first build of CM 12.1 but i can see boot animation this time but it doesn't boot yet but another biiiig problem is no TWRP.
Main priority is TWRP so faster I can fix it the better: Probably will use android 5.1.1 repo TWRP and update to 3.0.2.0 TWRP if this will not help then maybe it's releated to not bootable system maybe have a fix but it needs more time.
And second priority is bootable system: I might have solution to this one but not totally sure.
Third priority after we have bootable using ROM is to make it fast:
1. Linaro instead art.
So in few days or week or so will post update how it's going. Maybe sooner if I get working build.
Click to expand...
Click to collapse
Can you make a deodexed CM12.1 build? all builds from CBnuke are odexed
jao6622 said:
Can you make a deodexed CM12.1 build? all builds from CBnuke are odexed
Click to expand...
Click to collapse
Checked system/app and dont saw any odex files so yes i can make deodexed rom.
And also i have fixed TWRP error and tested just kernel and can boot rom with it now just to make system boot
Main issue with TWRP is FIXED even on CM13.0 and CM12.1 its fixed but both still dont boot up cm 12.1 atleast show me boot animation but cm 13.0 didnt do even that and its stuck at black screen i send few people message to help me with this and waiting for reply. Im looking trought my CM12.1 boot.log and i cannot find the error still what is causing it to not boot. And also i changed CM12.1 boot animation to the one included in LineageOS.
The problem was in TWRP that it choosed wrong PIXEL_FORMAT_BRGA_8888 instead of our PIXEL_FORMAT_RGB_565 so now it looks good now.
Here is link to this build: CM12.1 NOT BOOTABLE WITH FIXED TWRP FOR HELPING WITH FIX.
PLEASE IF YOU DONT KNOW WHAT YOU ARE DOING DONT INSTALL IT ITS STILL NOT BOOTABLE ROM.
Well cm12.1 still not booting at all but I'm going to delete the source and redownload by tutorial by friend (helping a lot Thanks) and if that fails I don't know then but hopefully we will get working build of cm12.1 and for now I'm deleting cm13.0 source since it needs a lot of work to be usable but will talk with SergeyL (he have device with same cpu) and will see how will that work if his work will be usable then if everything works perfectly (unlikely) then maybe cm14.1 but as I said unlikely so wait in few days for hopefully build of cm 12.1
Its working !!!
The best news i can tell you i want to share my Working build of CM12.1 !!! The build will be avaiable to download in few days in new thread (will tell the name later) but best of all is that working stuff is exactly like CBNUKE builds and the boot took 10 seconds Wooow.
Got new security patches 1.11.2016 (no newer since CM12.1 got no new updates.
Thats all i wanted to share.
---------- Post added at 11:53 PM ---------- Previous post was at 11:42 PM ----------
Its still build on CM source but will download Lineage Source and compile again but with cm source it was just test if i can build it and yes i can so after compiling Lineage will publish here
Saw it on Sony development Web yesterday...it will be awesome if any developers can make a fully functional rom
Well, haven't you seen the 7.1.1? The dev is still working on it, and the next build will be on O. We're working on it now. We have a channel for the news - https://t.me/joinchat/AAAAAELTVKqh1eeAesWWXw.
p.s. Thread must be deleted now, IMHO.
Thumbs-up to kamil ochman and other devs for your great work
To do list
https://gist.github.com/bartcubbins/69d44e166b529de192f2621b498f8030
What? Me?
Hi,
I downloaded the AOSP sources from Sony the other night to build a barebones from for my Z3. However, the Leo wasn't in the device tree, but what I did see were options for the E2303 & E2333. This was for 8.0.0 OPR3, mind you, so is an Oreo.
I was successful in building the images required for flashing, however the kernel fails to boot due to missing DTB. I am currently attempting to fix this so that the boot.img will boot and hopefully have a working Oreo for our M4. The inline kernel fails, so if anyone with skills in this particular area would be greatly appreciated. I'm not a developer, merely a tinker with determination. I am currently trying different patches seen on github for tulip, however no matter what I do I can not get the missing DTB into boot.img.
Dutch Burdock said:
I was successful in building the images required for flashing, however the kernel fails to boot due to missing DTB. I am currently attempting to fix this so that the boot.img will boot and hopefully have a working Oreo for our M4. The inline kernel fails, so if anyone with skills in this particular area would be greatly appreciated.
Click to expand...
Click to collapse
Write me in PM as quick as possible, we have a team of devs, and your help will be appreciated)