Hi,
I'm working on a C6603 port for our Xperia SP. This port will NOT be a themed Rom. This is a stock rom for Unlocked Bootloader.
Don't ask for ETAs
Prerequisite
Code:
Your Warranty is void.
If your phone stops working/burst into flames/goes down the toilet, I'm NOT responsible for it.
Since this is a port, I shall be needing a Logcat along with bugs/crashes.
Your device should be rooted and should have custom recovery installed.
Create a Nandroid backup before flashing.
In order to recover, you have got to flash stock rom (4.3) root , install recovery and restore your backup.
If the ROM boots, I shall transfer this thread to the Development Section.
Testers selected:
@noahvt
@jancsessz
Click to expand...
Click to collapse
Work has been resumed !
I need a team of expertise.
Someone who could develop kernel for Rom. I not good at developing kernel.
Combining C5303 zImage and C6603 ramdisk, and changing /dev/block paths in the C6603 ramdisk to C5303 ones should make the ROM boot.'
'
Another problem is to whether use CM11 as base or replace Core files from Android 4.3 to C6603's 4.4.4 ?
Note: Everybody have contributed to this project shall get equal credits, as a team.
Click to expand...
Click to collapse
Delete
Can someone tells what is c6603 port?
ironshadow2 said:
Can someone tells what is c6603 port?
Click to expand...
Click to collapse
C6603 refers to Xperia Z.
Can you tell us more about this ROM? And is it booting?
ironshadow2 said:
Can you tell us more about this ROM? And is it booting?
Click to expand...
Click to collapse
Okay,
This is .283 stock firmware (Android 4.4.4 release) which Sony had released for Xperia Z. While both the device i.e... C6603 & C5303 have a similar hardware setup , I thought why not port it to our Xperia SP ?
About the booting part.....
My Xperia has gone out for repair. I'm currently using a backup phone for the time being. I personally couldn't test it out. That is why I needed testers.
I hope we get a feed back from the testers soon.
Uhm officialy you can not rely on the phones from other users
So best is to test it first, add more details and then ask for tester
mrjraider said:
Uhm officialy you can not rely on the phones from other users
So best is to test it first, add more details and then ask for tester
Click to expand...
Click to collapse
There are already 2 testers.
upload the test file
Did it work?
Not working :/ get bootlop...
@jancsessz
I'll be needing a logcat.
Sorry guys,
I'm stopping the project for now. I have got my Semester End papers going on in College. Will resume the work after 28th of November.
Till then......
PS - If a developer would like to work on the project , I could pass on the files to him/her and would gladly appreciate the work.
Okay,
I have found the root cause of getting bootloop.
.207 kernel doesn't support the current build. Combining zImage of .207 kernel with a modified Ramdisk of .283 kernel of Xperia Z should do the trick. But it'll require an unlocked bootloader.
Gamer R said:
Okay,
I have found the root cause of getting bootloop.
.207 kernel doesn't support the current build. Combining zImage of .207 kernel with a modified Ramdisk of .283 kernel of Xperia Z should do the trick. But it'll require an unlocked bootloader.
Click to expand...
Click to collapse
I will test it..I have an unlocked bootloader!
Yes already my Sp bootloader unlock...
How to create logcat with bootlop ?
I volunteer to test bro.
I want to be tester too
LBL tester here.
Tapatalked via Xperia SP
Any updates? Or still resuming after 28th?
Related
Hi! I just want to ask if its possible to make a fully working CM7? The new Gingerbread is out so all the sources are avilable. Or not? The current CM7's have no camera and a few bugs. The official GB have camera and all...
Is this possible for now or have we to wait until GB x10 is rooted? It would be great to have a great CM7 with all working!
Thx! Ákos
I am also searching for this
ako5 said:
Is this possible for now or have we to wait until GB x10 is rooted? It would be great to have a great CM7 with all working!
Click to expand...
Click to collapse
It should work with the sources from the prerooted ROMs, just a matter of time for someone to port this over. The sources were released a few days back, so a little bit of patience is in order...
muzzl3 said:
It should work with the sources from the prerooted ROMs, just a matter of time for someone to port this over. The sources were released a few days back, so a little bit of patience is in order...
Click to expand...
Click to collapse
Sources ,?? What sources ?? We dint have sources for.our modified kernel
Sent from my X10i using XDA App
i think we need an UNLOCKED bootloader in order to get full working CM, could be wrong tho
Neo said:
What sources ?? We dint have sources for.our modified kernel
Click to expand...
Click to collapse
Wrong word, drivers, working kernel... Either way, asking for it isn't likely to make it happen any faster is it?
Time Machine said:
i think we need an UNLOCKED bootloader in order to get full working CM, could be wrong tho
Click to expand...
Click to collapse
yes but J said freexperia will merge with official cyanogen, so we might get 'unofficial official updates, if you get what I mean.
Hello all,
I have a question regarding my Xperia Z.
I would like to install Cyanogenmod 10.1 (Stable) for my Xperia Z but I do see some various kinds of methods.
1. By using fastboot (Don't know exactely what it does).
2. By using a custom recovery.
Now, my phone is rooted and I do have a custom recovery.
Can I flash Cyanogenmod without unlocking my bootloader? (I don't want to loose Bravia engine and Stamina mode) when I ever decide to go back to stock.
From what I understand, fastboot will flash the CM kernel (not possible with a locked bootloader) while the custom recovery only installs a rom without a kernel.
Does it mean that I will have the stock kernel but with CM rom on it?
A couple of questions comes to mind in total:
- Can I flash CM using custom recovery?
- How to return to stock rom if ever needed (Will i loose my Bravia Engine -> DRM keys)?
- How to update the kernel to a new stock kernel if needed while running CM?
Kind regards,
You can't. You need to unlock your bootloader in order to flash the cm kernel.
Sent from my C6603 using xda app-developers app
ckyy said:
You can't. You need to unlock your bootloader in order to flash the cm kernel.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
But that does mean that I'll loose my DRM keys forever?
I don't want to lose them just in case I need to restore.
And if I unlock my bootloader, how do I exactely flash CM?
Kind regards
Anobiz said:
But that does mean that I'll loose my DRM keys forever?
I don't want to lose them just in case I need to restore.
And if I unlock my bootloader, how do I exactely flash CM?
Kind regards
Click to expand...
Click to collapse
Before unlocking, you can save your DRM keys with this method.
http://forum.xda-developers.com/showthread.php?t=2234627
Here is the updated version...
http://forum.xda-developers.com/showpost.php?p=41683557&postcount=672
thalada said:
Before unlocking, you can save your DRM keys with this method.
http://forum.xda-developers.com/showthread.php?t=2234627
Here is the updated version...
http://forum.xda-developers.com/showpost.php?p=41683557&postcount=672
Click to expand...
Click to collapse
Correct me if I'm wrong, but is the process then the following:
1. Root phone without unlocking bootloader.
2. Install CMW
3. Backup DRM keys.
4. Take Nandroid backup.
5. Save the files of the backups (3 & 4) in a safe location.
6. Unlock bootloader.
7. Flash CM.
For a restore:
1. Reflash stock rom.
2. Restore nandroid backup.
3. Restore backup of DRM keys.
Can you confirm that this process is correct, because I really want to install CM.
Is there a list somewhere (cannot find it on the official CM website) that lists me what kind of bugs there are in a specific CM version (what is not working)?
Kind regards,
Correct me if I'm wrong but weren't at least AOKP and ParanoidAndroid developed for locked bootloaders on other phones? If so, technically it should be possible with our Z, right?
ToinouAngel said:
Correct me if I'm wrong but weren't at least AOKP and ParanoidAndroid developed for locked bootloaders on other phones?
Click to expand...
Click to collapse
I doubt it, but if they were they won't have been a true port.
Honestly, i don't understand the DRM thing. It's not like you lose important features. If you can unlock your bootloader, then do it. Not doing it would be like buying a Ferrari just for your Garage.
Sent from my C6603 using xda app-developers app
ckyy said:
Honestly, i don't understand the DRM thing. It's not like you lose important features.
Click to expand...
Click to collapse
Just because they're not important to you doesn't mean they're not to others, and even if I could unlock I'd probably still be holding off in the hope that someone comes up with an S1Tool that allows Sim and Bootloader unlocking for late 2012, 2013 Xperias.
XperienceD said:
Just because they're not important to you doesn't mean they're not to others, and even if I could unlock I'd probably still be holding off in the hope that someone comes up with an S1Tool that allows Sim and Bootloader unlocking for late 2012, 2013 Xperias.
Click to expand...
Click to collapse
And is there anymore that knows where you can see what kind of things that does not work on CM for the Xperia Z.
I would like to have full funcionality like Radio, NFC, ...
Kind regards,
mate, unless someone finds an exploit, you CANNOT have non stock based roms on a locked bootloader.
Anobiz said:
And is there anymore that knows where you can see what kind of things that does not work on CM for the Xperia Z.
I would like to have full funcionality like Radio, NFC, ...
Kind regards,
Click to expand...
Click to collapse
There are only 2 bugs that I know of: the screen takes 1.5 seconds to wake up after pressing the power button, loudspeaker in calls doesn't work.
I've also heard that hdmi out is broken but I haven't tried.
I'm running Cyanogenmod personally and it's great.
Michealtbh said:
There are only 2 bugs that I know of: the screen takes 1.5 seconds to wake up after pressing the power button, loudspeaker in calls doesn't work.
I've also heard that hdmi out is broken but I haven't tried.
I'm running Cyanogenmod personally and it's great.
Click to expand...
Click to collapse
Thanks for this reply.
And it's not that I don't believe you, but is there a list that contains al the bugs?
Which version do you run? Stable, RC, Nightly?
Kind regards,
Anobiz said:
Thanks for this reply.
And it's not that I don't believe you, but is there a list that contains al the bugs?
Which version do you run? Stable, RC, Nightly?
Kind regards,
Click to expand...
Click to collapse
There is no official bug list afaik, just check the thread.
I usually run the latest nightly.
Michealtbh said:
There is no official bug list afaik, just check the thread.
I usually run the latest nightly.
Click to expand...
Click to collapse
I'm sorry but I don't think there is a thread.
I would like to install it from get.cm so where can I find the thread of the official CM 10.1?
Kind regards,
Changelogs for all phones on get.cm can be found on BBQLog. Xperia Z is here:
http://changelog.bbqdroid.org/#/yuga/next
Use the links at the top to see changes in each version.
Anobiz said:
I'm sorry but I don't think there is a thread.
I would like to install it from get.cm so where can I find the thread of the official CM 10.1?
Kind regards,
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2156919
There is also a discussion thread http://forum.xda-developers.com/showthread.php?t=2265153
You can find official nightly builds here
http://get.cm/?device=yuga
alexp999 said:
Changelogs for all phones on get.cm can be found on BBQLog. Xperia Z is here:
http://changelog.bbqdroid.org/#/yuga/next
Use the links at the top to see changes in each version.
Click to expand...
Click to collapse
I find this better than bbqlog http://mobile.10.1.cmxlog.com/?device=yuga
Hello,
Can you tell me what the difference is between the official Get.cm repo and the freeXperia project.
After that I can install my version of CM.
Thanks for clearing this out.
Kind regards
Anobiz said:
Hello,
Can you tell me what the difference is between the official Get.cm repo and the freeXperia project.
After that I can install my version of CM.
Thanks for clearing this out.
Kind regards
Click to expand...
Click to collapse
No real difference. FXP builds are released weekly while official builds are obviously released daily. The same code gets pushed to both builds afaik
New update (14.3.A.0.757) now rolling to Xperia Z1, Z Ultra and Z1 Compact; fixes KitKat sound bug issue
Sony is now rolling out the Android 4.4.2 KitKat bug-fix, just as it had promised last week. Firmware build 14.3.A.0.757 replaces the previous KitKat build (14.3.A.0.681) and fixes the sound bug issue which frustrated many. The issue related to sounds from the handset being played through the internal, rather than the external speaker.
The update is rolling out across all variants of the Xperia Z1, Xperia Z Ultra and Xperia Z1 Compact. We have included a list of regions where it has currently hit right now, however expect this to broaden over the coming days. If you’ve downloaded it, let us know if it fixes all of the issues you’ve had with the new KitKat build.
http://www.xperiablog.net/2014/04/09/new-update-14-3-a-0-757-now-rolling-to-xperia-z1-z-ultra-and-z1-compact-fixes-kitkat-sound-bug-issue//
This is a new build for the Zultra and Z1 family, placed today:
Will it resolve the Kitkat bugs?
http://developer.sonymobile.com/dow...s/open-source-archive-for-build-14-3-a-0-757/
http://www.quellichetelefonano.it/sony-xperia-e-bug-audio-lattesa-e-finita/
Probably. And some camera problems causing heat
Sent from my C6903 using Tapatalk
This is not a ftf. Can any one gimme a ftf link.
I hope so this is a bug fix version
Sent from my C6903 using xda app-developers app
shahzaib.khan said:
This is not a ftf. Can any one gimme a ftf link.
I hope so this is a bug fix version
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
There's no release yet, still have to wait. This is not the update.
Sent from my C6903 using Tapatalk
Sound bug fix????
im downloading the update but can anyone tell me how to install it??i wish it could fix the sound bug
snigglets said:
im downloading the update but can anyone tell me how to install it??i wish it could fix the sound bug
Click to expand...
Click to collapse
It's very easy to install. Download and unpack the archive. Install your favorite compiler (gcc, clang or something else). Compile binaries from source. Build one ftf from binaries and install it on your phone. Vualya, you have new firmware installed.
Seriously, its only source and nothing else, its not firmware.
romaha said:
It's very easy to install. Download and unpack the archive. Install your favorite compiler (gcc, clang or something else). Compile binaries from source. Build one ftf from binaries and install it on your phone. Vualya, you have new firmware installed.
Seriously, its only source and nothing else, its not firmware.
Click to expand...
Click to collapse
That's a good one! LOL!
@romaha
Haha
Sent from my C6903 using xda app-developers app
if someone compiled share it,may take months for sony to release!
xsony.plus said:
if someone compiled share it,may take months for sony to release!
Click to expand...
Click to collapse
Its not a trivial task. Do not expect to get ftf from source earlier than sony's official update
romaha said:
Its not a trivial task. Do not expect to get ftf from source earlier than sony's official update
Click to expand...
Click to collapse
for someone like DoomLord its just few minutes!
atleast kernel should be easy!
xsony.plus said:
for someone like DoomLord its just few minutes!
atleast kernel should be easy!
Click to expand...
Click to collapse
A great competition. Sony vs DoomLord. Who will be the first? :laugh:
romaha said:
A great competition. Sony vs DoomLord. Who will be the first? :laugh:
Click to expand...
Click to collapse
DoomLord
It's just the opensource code
You still need all the sony private drivers and software.
Luinwethion said:
It's just the opensource code
You still need all the sony private drivers and software.
Click to expand...
Click to collapse
yes,hradware&HAL drivers along customization for each phones.can be ported from previous releases,there is no huge structural differences between 4.3 and 4.4
Shared this link in the Doomkernel thread, so Doom himself can analyze the .tar package and see if it is anything improved / new in those sources or just like the previous KitKat ones..
It's already available in some region !
pivop said:
It's already available in some region !
Click to expand...
Click to collapse
Carrier branded update, it seems?
Destroyedbeauty said:
Carrier branded update, it seems?
Click to expand...
Click to collapse
The tool shows that comm&jur has it also, so maybe not !
pivop said:
It's already available in some region !
Click to expand...
Click to collapse
I just checked, and still there is no upgrade for any country and region
I checked again now, and your result is ok. sorry bro
Hi Guys,
Today my CM11 build succeeded!!
Link: https://www.dropbox.com/sh/uxomzjcjqdug14x/AAC0wf9uRJh2bd3pyESRfDana
Please tell me how it works. Im reaaally curious)
Thanks in advance
I believe @Kali- is already working on it and it's booting and working with few issues, but he's busy with real life stuff. I think the device trees are already up.
Edit http://forum.xda-developers.com/showthread.php?p=52921260
I'd love to see more devs on the Z2 side of things. Think it will be a slow process due to the rooting issues though
Sent from my D6503 using XDA Free mobile app
I for one can't wait for a cm/aosp/pac/pa build for the z2
Can't you use dooms prebuilt kernel which has recovery included? Also Sony have released sources for latest fw, it's referenced in one of the two doom kernel threads
Sent from my D6503 using Tapatalk
Mr.R™ said:
I for one can't wait for a cm/aosp/pac/pa build for the z2
Can't you use dooms prebuilt kernel which has recovery included? Also Sony have released sources for latest fw, it's referenced in one of the two doom kernel threads
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Yeah of course i could. I was allready planning to do so!I
EDIT: I expect my first build to be finished in a few hours. I need some beta testers to test the build. Anyone?
I'm willing to test any builds you create btw
Sent from my D6503 using Tapatalk
Me too
Gesendet von meinem D6503 mit Tapatalk
If you still need the help, my bootloader is unlocked, and ready to flash.
Been waiting ever since we so that preview picture. Hell, i still dont use my Z2 because its so boring with just stock, still use my Nexus 5. Would be nice to see an AOSP/CM rom sure would get this device more exciting.
Also where is the Freexperia team? Have they closed shop, or are they just busy?
nickwarn said:
Also where is the Freexperia team? Have they closed shop, or are they just busy?
Click to expand...
Click to collapse
it is exam time and or they are busy with work see the link above.
pvy
pvyParts said:
it is exam time and or they are busy with work see the link above.
pvy
Click to expand...
Click to collapse
Is kali a memeber of freexperia? Thought he was only on the CM team. It really doesnt matter, it was just that there use to be CM builds and Freexperia so i thought maybe there was a chance they had something going.
nickwarn said:
Is kali a memeber of freexperia? Thought he was only on the CM team. It really doesnt matter, it was just that there use to be CM builds and Freexperia so i thought maybe there was a chance they had something going.
Click to expand...
Click to collapse
My understandnig is FreeXperia is "part" of CM ( not corparate )
i cant comment on who is part of freexperia tho but i thought kali- was.
pvy.
Okay guys, here's an update from me.
Yesterday i was almost done compiling when an error showed op. It had to do something with the recovery. Right now i'm trying to use a prebuilt kernel from DoomLord. When i have got a build i'll send you guys an pm with the link!
Thanks for the update
Sent from my D6503 using Tapatalk
I'm ready to test
Just out of curiosity, which versions of the Xperia Z2 are you coding for?
Any idea if it will run on the Japanese version? (SO-03F) I'm planning on getting one soon and trying to figure out my rooting options first.
Once I get it I'll of course be willing to be a guinea pig as I've got my current phone as a daily driver backup.
domesdkg said:
Just out of curiosity, which versions of the Xperia Z2 are you coding for?
Any idea if it will run on the Japanese version? (SO-03F) I'm planning on getting one soon and trying to figure out my rooting options first.
Once I get it I'll of course be willing to be a guinea pig as I've got my current phone as a daily driver backup.
Click to expand...
Click to collapse
I'm building for the international Z2 (code name: Sirius) Dont know if it will run on your device i'll find that out later.
Currently i'm running into this error guys. Does anybody have any idea?
Code:
using device-specific extensions in device/sony/shinano-common
using custom bootimage makefile device/sony/shinano-common/custombootimg.mk...
using prebuilt boot.img...
using custom bootimage makefile device/sony/shinano-common/custombootimg.mk...
using prebuilt recovery.img...
running: imgdiff -b /tmp/targetfiles-9t0vAB/SYSTEM/etc/recovery-resource.dat /tmp/tmpZwd7Gp /tmp/tmpQcmSqN /tmp/tmpjENpDi
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 971, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 939, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files", line 491, in WriteFullOTAPackage
MakeRecoveryPatch(OPTIONS.input_tmp, output_zip, recovery_img, boot_img)
File "./build/tools/releasetools/ota_from_target_files", line 404, in MakeRecoveryPatch
recovery_type, recovery_device = common.GetTypeAndDevice("/recovery", OPTIONS.info_dict)
File "/home/jaap/Android/CM11/build/tools/releasetools/common.py", line 985, in GetTypeAndDevice
return PARTITION_TYPES[fstab[mount_point].fs_type], fstab[mount_point].device
KeyError: '/recovery'
make: *** [/home/jaap/Android/CM11/out/target/product/sirius/cm_sirius-ota-df84df7ef8.zip] Error 1
Okay guys
Time for the update:
I fixed the error by adding this line to the boardconfig:
TARGET_NO_SEPARATE_RECOVERY := true
Building again now. Tommorow you'll hear more guys!
Okay guys the build is done!! This time the compile gave no errors!
Right now i'm uploading the builds so you guys can test them!!
thanks!
QuickS_NL said:
Okay guys the build is done!! This time the compile gave no errors!
Right now i'm uploading the builds so you guys can test them!!
Click to expand...
Click to collapse
I can't wait to test it out, after month of owning the z2, I just unlocked the bootloader yesterday.
This is pretty exciting
http://developer.sonymobile.com/201...-aosp-for-xperia-on-github-video-open-source/
Enjoy
I wonder if camera and modem will be supported in the future.
well thats good news
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Yeah we already knew because author already posted here http://forum.xda-developers.com/showthread.php?t=2907471
Sent from my D6503 using Tapatalk
Felimenta97 said:
I love how people Hage such amazing text interpretation skills. The device tree was added to Github. There are lots of resources there for third party devs to work on and build their own AOSP, or AOSP based ROM.
But this isn't a official release. There never was. This is meant for developers and developers only.
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
I'd argue it's an official release - a release for developers, but it's still official.
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
funky0308 said:
XDA is starting to be "Vanity Fair"...
Check your informations before you decide to post sensationalistic title like this one...
Click to expand...
Click to collapse
I see this too much... Aka agreement on ur post
And secondary point,
Not a rom, its neither a aosp rom
Yes official but its purely there for CM11, AOSP and any deviant developers to correct problems with their builds or correcr sonys problems
Its a greed thing sony is doing, it will benefit sony as well as xda devs
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Cigaras said:
So... I wont be able to have AOSP rom with locked bootloader on my Xperia?
Click to expand...
Click to collapse
Unlocked bootloaders ONLY. If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void, thus creating problems for Sony, with non Devs users returning phones and help queries etc...
waynekirby said:
If you still had a locked bootloader and ran AOSP, then your warranty wouldn't be void
Click to expand...
Click to collapse
But if AOSP is provided by Sony themselves, why would they threat it as warranty voiding?
Lets take for example Xiaomi, for Mi3 and Mi4 gsmarena.com said that You could choose either MIUI or AOSP, and You get OTA updates for both (I am not sure if that is official, I do not own a Xiaomi device). Would be great if Sony would do something similar, Google Play Edition would also work for me, as long as I get to keep all the Bravia Engine and X-Reality goodness
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
I highly doubt this. If it's true, you should be able to show that, though...
funky0308 said:
I believe it should work on LB.
That's the whole point...
Sony want AOSP users to use their kernels and their fw, work tested in their labs.
It should work on LB as well...
Click to expand...
Click to collapse
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
adyscorpius said:
There is a difference between google play editions and kernel source. If the source is precompiled, its as good as stock. Uncompiled source can be edited to cause serious hardware damage resulting in the void of warranty clause.
Xiaomi is yet to release kernel source for Mi3 and Mi4.
Click to expand...
Click to collapse
I don't understand your point here...
I know there are differences, that's why Sony works on this, officially.
We have CM and AOSP ROMs for Z1/Z2 but Sony now hired guy from here to help them in building AOSP that'll work on LB and is released by Sony.
That way, they still can control and approve what will go to device abd what won't...
Maybe I'm wrong but what's the point of releasing AOSP without kernel support from bootloader?
We already have that..
My guess would be - they want us to use AOSP but they don't want us to unlock bootloader and mess with DRM keys.
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
funky0308 said:
Exactly...that's the whole point.
Finally, someone who understand what I'm trying to say and what's the whole purpose of that project
Click to expand...
Click to collapse
Would be nice if instead of your warrenry being voided, its changed
So free repairs for sony fauls so long as its not caused by you rom
Envious_Data said:
It will work on LB because when sony compile a kernel its got a Sony Signature which matches that of a locked bootloader
So any AOSP compiled rom by sony is for LB
Click to expand...
Click to collapse
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Haldi4803 said:
AOSP compiled ROM from sony ?
i tought we'd only get the source code and nothing more on AOSP ?
Click to expand...
Click to collapse
We only are getting source it seems but to have this for locked bootloaders sony must compile and sign a rom and kernel