i'm trying to build an aosp rom for my samsung galaxy s duos(gt-s7562). what modifications do i do so that the rom can work on my phone.
i've downloaded one file from samsung open source website this files contain two things called platform.tar.gz and kernel.tar.gz
how do i go about this.
i'm running the latest firmware update and the phone is rooted and has clockworkrecovery mod on it
Hi Guys ,
I am using LG Optimus One (P500),I had some problems in making custom ROM for this device.
I was following this guide-- [UltimateGUIDE][How-to]Create your Own Custom ROM an easy way|Android Secrets By GuneetAtwal.
By this i was complete all the procedure that gives in the guide. Ex- Installing Kitchen , Setup kitchen , creating a working folder by Using A base ROM. In my case base ROM is- CM 10.1 Jellybean 4.2.2
After i was creating a working folder successfully. then i was Change/modify/update rom . Ex- i was adding apps on my rom. in apps folder ..
After i was done all changes , modification in ROM ,Now time to creating rom using working folder.
now i start cygwin,
.enter option 99 - "biuld rom from working folder" , After build option and few more enters.
When its all done i was find a folder inside "cygwin/home/yousername/kitchen" called output.zip
===========================================PROBLEM================================================
When i was flashing ROM into the mode recovery its says Failed.:crying::crying::crying::crying::crying:
In my Case Recovery is TWRP 2.6.3.0
=======================================================================================================
Can Anyone tell me solution for this problems because i am beginner. So tell please me guys i need HELP:crying:
PLEASE GUYS HELP ME :crying::crying:.
primekook said:
Hi Guys ,
I am using LG Optimus One (P500),I had some problems in making custom ROM for this device.
I was following this guide-- [UltimateGUIDE][How-to]Create your Own Custom ROM an easy way|Android Secrets By GuneetAtwal.
By this i was complete all the procedure that gives in the guide. Ex- Installing Kitchen , Setup kitchen , creating a working folder by Using A base ROM. In my case base ROM is- CM 10.1 Jellybean 4.2.2
After i was creating a working folder successfully. then i was Change/modify/update rom . Ex- i was adding apps on my rom. in apps folder ..
After i was done all changes , modification in ROM ,Now time to creating rom using working folder.
now i start cygwin,
.enter option 99 - "biuld rom from working folder" , After build option and few more enters.
When its all done i was find a folder inside "cygwin/home/yousername/kitchen" called output.zip
===========================================PROBLEM================================================
When i was flashing ROM into the mode recovery its says Failed.:crying::crying::crying::crying::crying:
In my Case Recovery is TWRP 2.6.3.0
=======================================================================================================
Can Anyone tell me solution for this problems because i am beginner. So tell please me guys i need HELP:crying:
PLEASE GUYS HELP ME :crying::crying:.
Click to expand...
Click to collapse
Was the base rom for your device. It is most likely that you are using a base that is not for your device so the kernel is wrong.
zelendel said:
Was the base rom for your device. It is most likely that you are using a base that is not for your device so the kernel is wrong.
Click to expand...
Click to collapse
But i am already use this ROM on my device , this specially build for my device as wel as kernel also..
Hey, I've been working on porting CyanogenMod 9 to my phone (Sony Xperia E - we already have CM10, but stock ICS is faster than it, and I decided to try CM9). I'm trying to follow the guide here: http://wiki.cyanogenmod.org/w/Doc:_porting_intro I've already built CM10.1 for the Nexus 7, so I'm okay with all the breakfast nanhu and stuff.
My question is this - to make the device and vendor folders, I can use mkvendor.sh, but it says it works only for devices that:
use a standard boot.img file, using the standard Android conventions and headers. It won't work for devices that deviate from this standard (Nook Color, Touchpad, etc.).
Click to expand...
Click to collapse
Since the Xperia E doesn't have a recovery mode, the recovery has to be built into the kernel, ie. the boot.img. Does this mean I can't use the stock ICS boot.img file for this?
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
FIRST OF:
You warranty is now void dont point at me if Broken or ill laugh at youbla bla you already know it
THIS IS NOT MY ROM! ALL CREDITS TO MAKING IT, GO TO THE AOSPA TEAM!!! I JUST EDITED TIME VALUES TO THE YEAR 2020
So i found (and "restored") this old paranoid Android 8.1 build...a lot of features missing like Theme manager but with built in Substrat um support? Everything Working
OEM image Version 17 for Android 8.1 Loire required
Rom download:
https://drive.google.com/file/d/1C6iliMInY5pH9mVwPiKUdzc1VFSNnvSe/view?usp=drivesdk
You can get that image Here:https://developer.sony.com/file/dow...s-for-aosp-oreo-android-8-1-kernel-4-4-loire/
Known bugs: Reinstall needed if navbar turned off and on
You dont tell me
Because I can't fix it
Gapps not included but found Here:https://opengapps.org
Special thanks to: Paranoid Android Team for making this Rom
And Me for " restoring" it I guess
Some random said:
FIRST OF:
You warranty is now void dont point at me if Broken or ill laugh at youbla bla you already know it
THIS IS NOT MY ROM! ALL CREDITS TO MAKING IT, GO TO THE AOSPA TEAM!!! I JUST EDITED TIME VALUES TO THE YEAR 2020
So i found (and "restored") this old paranoid Android 8.1 build...a lot of features missing like Theme manager but with built in Substrat um support? Everything Wirkung and OEM image Version 17 for Android 8.1 Loire required
Rom download:
https://drive.google.com/file/d/1C6iliMInY5pH9mVwPiKUdzc1VFSNnvSe/view?usp=drivesdk
You can get that image Here:https://developer.sony.com/file/dow...s-for-aosp-oreo-android-8-1-kernel-4-4-loire/
Known bugs: Reinstall needed if navbar turned off and on
You dont tell me
Gapps not included but found Here: Opengapps.org
Special thanks to: Paranoid Android Team for making this Rom?
Me for " restoring" it???
I really dont know
Click to expand...
Click to collapse
Wow someone actually thanked this!
Oh and by The way this Rom is rootable and should Have full xposed support too
For those who aren't clear, this guy changed the build date of AOSPA 8.1.0 to 2020, so that it could be installed over latest stock firmware. The build on AOSPA website was throwing errors while flashing, because it was built before .118 firmware.
Personally i'm not using this one (still waiting for PA9 stable) but i can see this coming in handy. Good work.
Yeah wasnt really hard or something just needed some converters and thats it
Hi, I want to try Paranoid Android on my Xperia X but neither the official image on aospa official site neither this version worked for me. The rom is correctly flashed on my device but after the sony logo image I have a black screen with the error message "Your device has failed verification and will not work properly." and then it shuts down.
I flashed the ODM oem.img v17 for Android 8.1 before flashing the AOSPA zip.
Do you know how to solve this problem?
DaNi95 said:
Hi, I want to try Paranoid Android on my Xperia X but neither the official image on aospa official site neither this version worked for me. The rom is correctly flashed on my device but after the sony logo image I have a black screen with the error message "Your device has failed verification and will not work properly." and then it shuts down.
I flashed the ODM oem.img v17 for Android 8.1 before flashing the AOSPA zip.
Do you know how to solve this problem?
Click to expand...
Click to collapse
Hey!
Currently my Xperia X is broken...
But try reflashing the latest stock Oreo before using this
DISCLAIMER
This rom is usable BUT it's just a old development build with a patch applied
There are a lot of bugs
If you find one please report it to me
I'm going to put that bug into OP
Some random said:
Hey!
Currently my Xperia X is broken...
But try reflashing the latest stock Oreo before using this
DISCLAIMER
This rom is usable BUT it's just a old development build with a patch applied
There are a lot of bugs
If you find one please report it to me
I'm going to put that bug into OP
Click to expand...
Click to collapse
I've tried flashing AOSPA after reflashing the stock Oreo and my Xperia X got stuck on Sony logo. I didn't flash the ODM oem image after reflashing stock Oreo