[Tutorial] Kernel building instructions for Xperia Z2 - Xperia Z2 Android Development

hello folks!
i have been working on kernels for various xperia devices (around 22 devices or so ) since the Xperia X10...
FIRSTLY the kernel building instructions given by Sony in the README_Xperia are WRONG!!!
huge thanks to @Kali- to fix the dtbTools issue (Z2 needs v2 dtb)!
specific instructions on how to build kernel for Xperia Z2 can be found here:
Instructions for MSM8974AB
I have a very detailed thread with information on how to build kernels for various xperia devices:
[Tutorial] Kernel building instructions for Xperia devices
Please use this thread to post your feedback and incase you need any help with building kernels for this device!
regards,
DooMLoRD

Same makefile fixes are for msm8x28?(Xperia T2 Ultra)
Cheers,
AJ

Abhinav2 said:
Same makefile fixes are for msm8x28?(Xperia T2 Ultra)
Cheers,
AJ
Click to expand...
Click to collapse
havent tested but should work

DooMLoRD said:
havent tested but should work
Click to expand...
Click to collapse
OK thanks sir I'll try and report. Currently trying to somehow root on locked bootloader but couldn't find any vulnerabilities which I can exploit. Will do some more tests to see if I can get something.
Cheers,
AJ

Abhinav2 said:
OK thanks sir I'll try and report. Currently trying to somehow root on locked bootloader but couldn't find any vulnerabilities which I can exploit. Will do some more tests to see if I can get something.
Cheers,
AJ
Click to expand...
Click to collapse
no vulnerabilities currently work... I have been testing on T, SP, Z, Z1, Z2... nothing so far...

DooMLoRD said:
no vulnerabilities currently work... I have been testing on T, SP, Z, Z1, Z2... nothing so far...
Click to expand...
Click to collapse
We can still execute scripts from /data/local/tmp. So as I understand, we need to properly mount system partition as 'rw' with that script?
EDIT: But I guess even for mounting it as rw we need su, so it pretty much comes back to it.
EDIT2: @DooMLoRD, can we put a script in /data/local/tmp, chmod it 0755, and then use it to grep default.prop and change, ro.secure=1 to ro.secure=0? And then with insecure ramdisk(obviously without rebooting or else, it'll load the default value, i.e. , 1), can we try to root it? (But I guess it is read-only also, so is there a way we can change the owner and group to allow changing it as rw?)
Cheers,
AJ

Abhinav2 said:
We can still execute scripts from /data/local/tmp. So as I understand, we need to properly mount system partition as 'rw' with that script?
EDIT: But I guess even for mounting it as rw we need su, so it pretty much comes back to it.
EDIT2: @DooMLoRD, can we put a script in /data/local/tmp, chmod it 0755, and then use it to grep default.prop and change, ro.secure=1 to ro.secure=0? And then with insecure ramdisk(obviously without rebooting or else, it'll load the default value, i.e. , 1), can we try to root it? (But I guess it is read-only also, so is there a way we can change the owner and group to allow changing it as rw?)
Cheers,
AJ
Click to expand...
Click to collapse
It's not that easy...
Sent from my D6503 using XDA Free mobile app

Related

[MODULE-|-SOURCE] Atrix 4G Overclock Module -- Up to 1.5GHz!

Welcome to the Motorola Olympus (Atrix 4G) Overclock Thread!
Well, I didn't know what to do today, so I've created something useful, an Overclock Module. However, this is incomplete and I need help for completing it.
More specifically, I don't know how to replace the already loaded table with the one written in this module. If anyone can help, I would appreciate it!
TRY THIS AT YOUR OWN RISK, I'M NOT RESPONSIBLE IF YOUR PHONES BRICKS.
Status: COMPLETE.
Download:
Compiled module: HERE (Min 200MHz Max 1.4GHz)
Module source: HERE (Outdated. It'll be updated when it'll be cleaned.)
What you need:
1. A brain
2. A ROOTED Atrix
3. Patience
4. PC and SDCARD.
How to load it:
1. Download the compiled module
2. Put it on the root of your sdcard
3. On your ROOTED device, run a terminal emulator and do exactly... this:
Code:
su
cp /sdcard/olympus_overclock.ko /data/
chmod 777 /data/olympus_overclock.ko
cd /data
insmod olympus_overclock.ko
4. Use SetCPU for your profiles
And let me clarify a thing: This isn't a kernel. This is a kernel module
Thanks to:
Skrilax_CZ - Without you, I would never had been completed the work.
iggytom & Bakano - Thanks for your kallsyms logs!
Stay Tuned!
=NOT TESTED....what do you expect...put here some modified kernel and want to us test withou any test made by you? lol
You kiring right?
Exciting but Ill wait till a few brave souls test it out first
Sent from my MB860 using XDA Premium App
is this a joke?
frankiedizzle87 said:
is this a joke?
Click to expand...
Click to collapse
he says "completing and uploading"
...maybe he actually plans on testing it first? or maybe he's just trollin'
I've ever done things that I wanted to do.
I'll receive my Atrix next week, so, for now, it isn't tested and it isn't even completed.
DEVS, I need some help. I've modified the struct and, well, sincerely, I don't know how to load it and replace it to the already loaded frequancy table.
I'm posting the source, being confident on other devs that can help me.
P.S.: The module isn't simply setting the maximum frequency for overclocking. Its concept is rewriting the frequency table for getting better scaling and even better battery life adding underclocking features in the future.
EDIT:
@EclipseX
I'm not posting a kernel. Atrix is locked. Read prior to write things.
@raybond25
I don't mean why some people is accusing of trolling when those people don't know who is that guy that is posting these things....
Looks I
To be interesting. Thanks
Sent from my MB860 using XDA Premium App
kholk said:
I've ever done things that I wanted to do.
I'll receive my Atrix next week, so, for now, it isn't tested and it isn't even completed.
DEVS, I need some help. I've modified the struct and, well, sincerely, I don't know how to load it and replace it to the already loaded frequancy table.
I'm posting the source, being confident on other devs that can help me.
P.S.: The module isn't simply setting the maximum frequency for overclocking. Its concept is rewriting the frequency table for getting better scaling and even better battery life adding underclocking features in the future.
EDIT:
@EclipseX
I'm not posting a kernel. Atrix is locked. Read prior to write things.
@raybond25
I don't mean why some people is accusing of trolling when those people don't know who is that guy that is posting these things....
Click to expand...
Click to collapse
if you had described you just said in your last post in the OP, people wouldn't have been quite as skeptical, it seemed as though you were posting saying you'd already completed (or nearly), but hadn't tested it, and were hoping that others were. That's all.
thanks for the clarification on what this is and what you intend to do
Well yes, I was thinking too much easy because I've done other things like this in the past but then I've discovered that this is different... so..
kholk said:
What you need:
1. A brain
2. A ROOTED Atrix
3. Patience
4. PC and SDCARD.
How to load it:
Click to expand...
Click to collapse
From the testers point of view before we even get to looking at this, which kernel did you design this for being we now have three currently out with the retail, the leaked feb version, and the OTA update. Pleas provide your how too asap before someone dose something wrong and burn out their device. That said I'm waiting till I see a proper OP before I look at this again, good luck.
Well the OTA's out of the question since it can't be rooted
kennethpenn and DG if you guys can make this happen. you will be my heros
Djazin said:
From the testers point of view before we even get to looking at this, which kernel did you design this for being we now have three currently out with the retail, the leaked feb version, and the OTA update. Pleas provide your how too asap before someone dose something wrong and burn out their device. That said I'm waiting till I see a proper OP before I look at this again, good luck.
Click to expand...
Click to collapse
It is a SOURCE.
A source can be compiled on every kernel you want if you've got the source for it.
Anyway, only the retail version source is out, so for now we can compile it only for the OLYFR_U4_1.2.6's kernel ...... when it gets completed.
JoeyGuard said:
kennethpenn and DG if you guys can make this happen. you will be my heros
Click to expand...
Click to collapse
DG is gone completely.
Sent from my MB860 using Tapatalk
Okay guys, I'm going to complete this.
Anyone with the OLYFR_U4_1.2.6 firmware installed can execute this command and upload to me the file?
Code:
cat /proc/kallsyms > /sdcard/kallsyms.log
This command creates a log of the kallsyms in the kallsyms.log file stored on your sdcard.
I need that file for finishing the work.
Thanks!
Here you go. 10char
Response
kholk said:
Okay guys, I'm going to complete this.
Anyone with the OLYFR_U4_1.2.6 firmware installed can execute this command and upload to me the file?
Code:
cat /proc/kallsyms > /sdcard/kallsyms.log
This command creates a log of the kallsyms in the kallsyms.log file stored on your sdcard.
I need that file for finishing the work.
Thanks!
Click to expand...
Click to collapse
Here you go. hope it helps =)
It exceeded allowed file size as a "txt" file, so here it is in rar format
Thanks for the kallsyms.
Examinating and finishing the job.
kholk said:
Thanks for the kallsyms.
Examinating and finishing the job.
Click to expand...
Click to collapse
Im very excited for this kholk I know you're good at these things. I have my fingers crossed
Sent from my MB860 using XDA Premium App
if this is possible WOW whata beast, even my netbooks will be jealous LOL

[HOWTO] Increase available RAM in ROMs based on "That kernel" and "Those libs"

[HOWTO] Increase available RAM in ROMs based on "That kernel" and "Those libs"
Most Atrix users using ROMs with "That kernel" and "Those libs" are stuck with 778MB or 784MB of available RAM (even after applying the ramfix for international Atrix users), but a few users are reporting getting around 855MB of RAM available on their phones. After a quick comparison of the /proc/cmdline on these phones (and since having more RAM can't hurt), here's a guide how to increase your available RAM on these ROMs. This guide is intended for people who have 778-784MB available on their phone when using ROMs based on "That kernel" and "Those libs" with the original ramfix. DO NOT USE ON OTHER ROMS!
WARNING: STOP NOW AND DO NOT FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!!!
PLEASE READ AND UNDERSTAND EVERYTHING BEFORE YOU DO ANYTHING!
I have personally tested this with Somebody's CM10 and AtrICS v2.
It should theoretically work with other ROMs based on "That kernel" and "Those libs", but use it at your own risk!
Now, on to the good part:
1. Get your current /proc/cmdline.
You can do this by using terminal emulator and typing:
su
cat /proc/cmdline
Click to expand...
Click to collapse
or by using a root browser and copy your /proc/cmdline to your sdcard.
A note from NFHimself:
NFHimself said:
Hi,
Please emphasize that the script needs YOUR complete /proc.cmdline in there, from a working phone adb session, not recovery adb session as the recovery has it's own possible /proc/cmdline via a different kernel, etc. You are not just editing the mem=?? stuff.
What would be best is to first create a zip that is plain jane what your /proc/cmdline is or one that uses setcmdline with a blank argument or "". That way you can reset to default in case of errors. Or you can just fastboot flash your boot partition, no need for an sbf.
Cheers!
Click to expand...
Click to collapse
2. Download attached file.
3. Edit the updater-script file in the zip.
Extract the zip and find META-INF\com\google\android\updater-script
Windows users: Edit the file using Notepad. DO NOT USE WORDPAD. WordPad changes the Unix-style CR to Windows style CR-LF, which may cause problems.
Once you open the file, find this in the file:
run_program("/tmp/setcmdline", "[email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:d00:100:800,kpanic:2100:400:800 security=tomoyo mot_prod=1 androidboot.serialno=XXXXX00000");
Click to expand...
Click to collapse
Change the red part with your own cmdline, which you got in step 1. Take care especially on the tegrapart and androidboot.serialno parameters. DO NOT USE A TEGRAPART AND/OR SERIAL NUMBER FROM ANOTHER PHONE!
If your original cmdline that you got in step one was:
[email protected] [email protected] [email protected] vmalloc=320M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=12345ABCDE
Click to expand...
Click to collapse
then you should modify the part of the updater-script mentioned above to look like this:
run_program("/tmp/setcmdline", "[email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=12345ABCDE"
Click to expand...
Click to collapse
Only the change the red part in the script with the red part in your original cmdline. DO NOT MODIFY ANYTHING ELSE!
4. Save the file, and repack the zip.
5. Flash zip.
6. You should now have 855MB of RAM available. Enjoy your extra 70+MB of RAM.
WARNING: DO NOT FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!!!
I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG BECAUSE OF YOU BORKING YOUR CMDLINE!!!
Thanks to: NFHimself for creating the ramfix binary and Ilkinansr92 for his cmdline.
Thanks!!! I will givi it a try.
Edit: Working just fine....thanks again!
from the (m)ATRIX...
Thanks!
Now i have 855mb of RAM available
I have 815mb of ram available and i am using Nottachtrix Rom, i am going to try this method in 2 mins and i will give feedback..
Edit:
it gives me error which number 6 (my rom is working, no problem). i know nottachtirx is not based on that kernel but i had wanted to try it whether work or not.
ramanujan20 said:
I have 815mb of ram available and i am using Nottachtrix Rom, i am going to try this method in 2 mins and i will give feedback..
Edit:
it gives me error which number 6 (my rom is working, no problem). i know nottachtirx is not based on that kernel but i had wanted to try it whether work or not.
Click to expand...
Click to collapse
I got that error too....on JB...but that was because I was doing something wrong.
But I think this is for JB...
Cocolopes said:
I got that error too....on JB...but that was because I was doing something wrong.
But I think this is for JB...
Click to expand...
Click to collapse
are you using something related to "that rom"? (kernel, libs, rom)
jhonnyx said:
are you using something related to "that rom"? (kernel, libs, rom)
Click to expand...
Click to collapse
No...someones Cm10 here...but now is working...I just replace the update script in the zip...and work perfect
from the (m)ATRIX...
successful
oh yeah~
now i have 855mb ram now!
i found that you can copy the file /proc/cmdline to computer,and select the words you need
in this way,you can do it more simple and more safe!
Well. 855 MB RAM. I am using CM10 with that libs.
Thank a lot.
Cocolopes said:
No...someones Cm10 here...but now is working...I just replace the update script in the zip...and work perfect
from the (m)ATRIX...
Click to expand...
Click to collapse
Well, "Somebody's" CM10 IS using the kernel & libs from "That ROM", so I'd say it's very much related.
Can anybody help me i don't even have 500 mb in manage apps - running apps section
International user and using MRom
Sent from Otterbox Atrix 4G Rockz
ranjithkumar1201 said:
Can anybody help me i don't even have 500 mb in manage apps - running apps section
International user and using MRom
Sent from Otterbox Atrix 4G Rockz
Click to expand...
Click to collapse
Have you applied the ramfix? If not download this and apply it and it will fix that problem:
http://forum.xda-developers.com/attachment.php?attachmentid=710806&d=1315237274
Perfect. Thanks !
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
ravilov said:
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
Click to expand...
Click to collapse
Works beautifully on someone's cm10! Big thanks.
Sent from my MB860
ravilov said:
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
Click to expand...
Click to collapse
sorry for ask but i don't get it this is a script to modify the cmdline or is an auto modify tool for the cmdline?
Maibol said:
sorry for ask but i don't get it this is a script to modify the cmdline or is an auto modify tool for the cmdline?
Click to expand...
Click to collapse
Both actually.
It includes a tool that can modify the cmdline, and a script that does modify the cmdline automatically, by utilizing the tool.
ravilov said:
Both actually.
It includes a tool that can modify the cmdline, and a script that does modify the cmdline automatically, by utilizing the tool.
Click to expand...
Click to collapse
thanks nice tool i gon give it a try
Why so some Atrixes have 815 MB RAM and some others 879 MB ?
And ravilov, does your script work on gingerbread ROMs, too?
Sent from my CM7 powered Atrix using TapaTalk \o/
the.cybot said:
And ravilov, does your script work on gingerbread ROMs, too?
Click to expand...
Click to collapse
Actually, I'm not sure. It doesn't seem to work for me. The boot image gets updated correctly but for some reason the new cmdline is not used when the kernel boots. I'm using MROM, latest release. Maybe it works different on another ROM. Maybe this whole cmdline business is specific to stock kernels only. Needs more research.

[PATCH][TX][DEV]kexec hardboot port - dual-boot possible

!!!!!! NOT FULLY TESTED !!!!!!!
This patch is based on Tasssadar's hardboot patch for mako. And I borrowed some code (hardboot page address usage) from alvinhochun's Xperia M port. The kernel source is 9.2.A.0.295 from Sony. Thanks all of above!
Here is Tassadar's original thread which explains what is kexec hardboot and what it does. Apply this patch to your kernel source and it will be capable of booting another kernel/system without reflashing.
Note: KEXEC_HB_PAGE_ADDR doesn't need to be a certain value. In my tests, 0x88000000 and 0x88A00000 both work. However, I don't know if there are significant side effects... There is no ram_console entry in /proc/iomem... The default address calcuated by original patch is 0x88CE0000,which doesn't work, so I removed the calculation code and hardcoded the address (thanks alvinhochun)
Click to expand...
Click to collapse
Usage can be seen in the sh file attached. Sh file is modded on Tasssadar's. Kexec binary is also taken from his github. Thanks again!
Parameters:
--load-hardboot : load the kernel with hardboot request
--initrd : ramdisk path (For 2012 line, that's the ".cpio.gz" file)
--mem-min : where the kernel should be loaded to (lowest address). This is not certain,either. 0x82000000, 0x85000000 both work. You can try different values. (Is there any limitation to this? Plz tell me...) Normally 0x82000000 will be okay.
--command-line : command line for the guest kernel. Note that the arguments appended by bootloader (semcandroidboot.babe1324 etc)need to be added here manually.
Click to expand...
Click to collapse
Now I have successfully dual-booted stock 4.3(205) and OmniROM 4.4 (homemade):
1. re-partition external sdcard to 4 parts. 1 for regular data storage(mmcblk1p1), 1 for /system (mmcblk1p4), 1 for /data (p2) and 1 for /cache (p3).
2. mount /dev/block/mmcblk1p4 to USB storage in TWRP and "dd if=(9.2.A.1.205 system.ext4 extracted from FTF) of=(USB storage)" on computer. You can use a card reader also.
3. modify the fstab files in stock 205 ramdisk to change the devices for /system, /data and /cache. If you want to add recovery, edit their fstabs also. (PERMISSIONS FOR THESE FILES ARE REALLY IMPORTANT! All .rc and fstab should be 644, root:root. Otherwise it won't boot)
4. repack the ramdisk. Push the zImage and ramdisk to the phone and execute the sh file. The phone reboots and stock 4.3 loads.
5. rebooting the phone will go back to host ROM.
Click to expand...
Click to collapse
But there is one problem: in stock 4.3, Baseband is shown as "Unknown" and the phone gets no signal. On the host ROM, it works properly. It seems to be related to TA reading, but I can't think of anything wrong with this...Logcat shows three TA units were missing. But in host ROM, they are shown as missing too. Full logcat attached in zip. I didn't touch any file other than fstab, fstab.qcom and init.target.rc in 205 ramdisk. Stock 4.1 works like a charm though.
Anyone knows? Thanks in advance~
You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app
alanc.1996 said:
You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
New build arrived (2014/05/21). See the separate thread. Following is the old message.
==================
At least it won't reboot ramdomly..but there may be some minor bugs.
Link: http://pan.baidu.com/s/1i3Hq4ip (Password: kpnn)
Internet connection is not very good here so uploading to devhost/mediafire is nearly impossible...
You need to flash the kernel first, then use the recovery to flash the ROM, then flash the kernel again. After system boots, push the modules file to /system/lib/modules
This is based on tital's port. Thanks a lot~
Later I will open a thread to introduce this ROM...
Cool! Will try it out!
Sent from my LT29i using XDA Premium 4 mobile app
Months ago, when I restored an Nandroid backup of 9.2.A.0.295, the same problem appeared. But at that time only mobile service was dead, while WiFi worked. Now mobile service and WiFi are all dead. The screen stops at "Turning on Wi-Fi". However, in dmesg & lsmod, I can see that WLAN driver module has been loaded, with MAC address changed correctly...And in Service Menu(*#*#SERVICE#*#*), Configuration in Service info is dead. Tapping on it will cause the app to stop responding. What is the point?
OK I tried 9.1.B.1.67 firmware. Everything works, including baseband, Wi-Fi and *#*#SERVICE#*#*... However, it's not so attractive as stock 4.3...
Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?
RpRAUC said:
Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?
Click to expand...
Click to collapse
As long as the kernel matches the ROM (phone operates normally when you install the custom kernel as usual), it should be okay...
Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app
Galcactus said:
Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This patch may work on T without any modification, except for the macro name in memory.h
Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app
Galcactus said:
Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
It's already perfectly working...
In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app
Galcactus said:
In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This is a little bit complicated... but I'll try to make a post about this in a few days.
The kernel commits should be the same for TX and T :
https://github.com/updateing/androi...mmit/3d4950e7d3a0cc1549e82fda6c1d961f83e04f4a
https://github.com/updateing/androi...mmit/8843e01fb1b6752768056589a510a2f8985c0884

[P905M LTE and P905][KERNEL] STOCK compiled with SELinux setenfoce command enabled

I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
User esgie confirmed that it works on SM-P905 too!
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
Image sha1sum
b85360a80f6205269b75d9dfabccac211a224d46
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)
No one interested?
Thanks a lot. Will try it.
Sent from my GT-N7100 using XDA Premium 4 mobile app
rodpp said:
I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)
Click to expand...
Click to collapse
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation
esgie said:
Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation
Click to expand...
Click to collapse
Thank you very much for confirm that it works on SM-P905, I'll include this information on the first post.
If you find some WiFi issues don't forget to edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Regards,
Rodrigo.
Already had the property changed in my build.prop, so i'm not exactly sure if the wifi works out of the box or not. Although I confirm that it DOES work with the build.prop modification
And by "does work" I meant both wifi and mobile radio working flawlessly.
gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
Hi there, I tested here and the image is working fine here. The user esgie just confirmed that too, in a P905. Please check the sha1sum of your downloaded image file.
Regards,
Rodrigo.
rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
I probably did something wrong.
I've downloaded again and wiill try once more.
MD5 f39207bd4c45b1854372cd519942a6c2
SHA1 b85360a80f6205269b75d9dfabccac211a224d46
Thanks.
Sent from my GT-N7100 using XDA Premium 4 mobile app
As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?
Please integrate fauxsound
esgie said:
As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?
Click to expand...
Click to collapse
Unfortunately I don't have enough free time, so I don't have plans to work in kernel development. I did this because I was needing it to install some stuffs in my tablet and decided to share it here o XDA where I always found useful things.
If someone wants simple modifications and points some links explaining that I can try without problems.
And if someone have problems preparing an environment to compile the kernel, let me know, I'll be very happy to help.
Regards,
Rodrigo.
koko115 said:
Please integrate fauxsound
Click to expand...
Click to collapse
Do you have a link?
Honestly, I don't know what fauxsound is!
rodpp said:
Do you have a link?
Honestly, I don't know what fauxsound is!
Click to expand...
Click to collapse
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.
Spere said:
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.
Click to expand...
Click to collapse
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.
Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP
js345 said:
Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP
Click to expand...
Click to collapse
Yes, one of my motivations to compile this kernel was to boot Linux images too.
Regards,
Rodrigo.
Enviado de meu SM-P905M usando Tapatalk
rodpp said:
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.
Click to expand...
Click to collapse
I tried to compile the kernel with the patches sugested by the Fauxsound developer but, unfortunately, I have no success.
Probably it will be necessary more kernel modifications to compile it with the Fauxsound patches.
Enviado de meu SM-P905M usando Tapatalk
Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier
orobin said:
Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier
Click to expand...
Click to collapse
The kernel is for P905M/P905...

[Sony] Xperia Open Devices Project

Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Hi,
Glad to see you on these forums
I have been trying to build an AOSP image of the Android M Preview to flash on my z3 tablet compact for a while now and I always get stuck at the exact same time.
My building environment is set up on an Ubuntu VM (14.04 LTS) and when using the make command, I get an error message saying that "/usr/lib/python2.7/subprocess.py" can't be found.
Of course the file is in its place so that's a bit baffling...
Is this problem known to you and is there any solution for it ? :/
Thank you in advance for your reply !
anatole78 said:
Hi,
Glad to see you on these forums
I have been trying to build an AOSP image of the Android M Preview to flash on my z3 tablet compact for a while now and I always get stuck at the exact same time.
My building environment is set up on an Ubuntu VM (14.04 LTS) and when using the make command, I get an error message saying that "/usr/lib/python2.7/subprocess.py" can't be found.
Of course the file is in its place so that's a bit baffling...
Is this problem known to you and is there any solution for it ? :/
Thank you in advance for your reply !
Click to expand...
Click to collapse
there is something wrong with your env please start over following the guide
i am also using ubuntu 14.04LTS and i can confirm that is fine
br
J
PS.
we will update soon M build guide for m-preview-2
jerpelea said:
there is something wrong with your env please start over following the guide
i am also using ubuntu 14.04LTS and i can confirm that is fine
br
J
PS.
we will update soon M build guide for m-preview-2
Click to expand...
Click to collapse
I am a most stubborn man and I've tried following the guide from the start about 10 times last week but to no avail...
The error about the subprocess.py file pops up no matter what I do
Glad to know the m-preview-2 is coming to our Xperia devices !
I finally was able to compile it !
I don't know why but this time Ubuntu prompted me to install phablet-tools saying that "repo" was missing so I did and voilà, the make was successful !
Only problem is flashing the three img files resulted in my SGP611 being stuck in a bootloop
Back on official Lollipop for the moment... Any idea what could cause this ?
Thanks
anatole78 said:
I finally was able to compile it !
I don't know why but this time Ubuntu prompted me to install phablet-tools saying that "repo" was missing so I did and voilà, the make was successful !
Only problem is flashing the three img files resulted in my SGP611 being stuck in a bootloop
Back on official Lollipop for the moment... Any idea what could cause this ?
Thanks
Click to expand...
Click to collapse
probably some missing patches
#adb shell logcat
does wonders in this case
jerpelea said:
probably some missing patches
#adb shell logcat
does wonders in this case
Click to expand...
Click to collapse
Sorry if it's a dumb question but how can I use any adb commands when I'm stuck on the Sony splashscreen/logo ?
anatole78 said:
Sorry if it's a dumb question but how can I use any adb commands when I'm stuck on the Sony splashscreen/logo ?
Click to expand...
Click to collapse
press and keep pressed vol up and power till device reboots
then press volume up to enter fastboot mode
Now you have the opportunity to win Sony devices every 2 months
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/hero-open-source-developers/
Happy cooking
http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/
enjoy
J
Hi all
We have published a new snapshot, zip v14, with camera update (improved quality and stability)
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Enjoy
J
Hi all
I have some more exciting news
http://developer.sonymobile.com/kno...s/how-to-access-uart-ports-on-xperia-devices/
PS.if devices are not listed here they dont have the connector !
Br
J
New updates
http://developer.sonymobile.com/201...wider-range-of-unlocked-xperia-devices-video/
Enjoy
J
We have published new binaries
http://developer.sonymobile.com/downloads/tool/software-binaries-for-aosp-lollipop-android-5-1/
Br
J
Thank you!
Gesendet von meinem SM-G900F mit Tapatalk
Does anybody has a working ROM based on this for the z3tc?
Where is cm13?
Gesendet von meinem SM-G900F mit Tapatalk
Hi all
Blobs v17 are public
Happy easter
J
​
jerpelea said:
Hi all
Blobs v17 are public
Happy easter
J
​
Click to expand...
Click to collapse
Thanks! Happy easter!
Gesendet von meinem Xperia Z3 Tablet Compact Wifi mit Tapatalk
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
2016-04-22: AOSP Marshmallow binaries for Android 6.0 and AOSP Lollipop binaries for Android 5.1 updated with improved connectivity, stability and camera functionality. We’ve also added the second camera actuators for Xperia Z3 and Xperia Z4 tablet. In addition, we’ve added the camera actuator for the Xperia Z5 family for Android 6.0.

Categories

Resources