[Kernel] [CDMA] [Unlocked Bootloader] Stock with overclock/recovery [V1.0] - Xperia Play Android Development

R800x Users, I have just compiled a kernel based of the 3.0.1.E.0.88 Sources.
I need a few testers, Big update, read the update section for v.2 (2012 Feb 12)
Pax
Update 01: 2012 February 08 1500 CST:
Code:
Working:
Stock kernel (no overclocking yet)
Boots
No random reboots (yet)
Autobrightness is disabled (as it was in 2.3.3 update)
Not Working:
Wifi (came from DooMLoRD's Kernel, need to check coming from stock update: need to flash Doom's stock wifi)
Recovery (need to look into this, in the meanwhile, use market link below)
Will be added Later:
Governers
I/O Schedulers
Overclocking
Auto-rooting
Note: This kernel's ramdisk is ro.secure = 0, which means it can be rooted, you'll just have to do the work.
Update 2012 February 08 -- 1900
Attached boot.img
Update: 2012 February 12 -- 2020
Code:
Big update to the kernel
I switched from my ramdisk, which ended up being a headache to DooMLoRD's v10 ramdisk
That means:
Wifi Works
Autoroot (should) work (I haven't tested it yet)
Recovery Works
New Splash on boot (thanks [URL="http://forum.xda-developers.com/showthread.php?t=1494076"]KeiranFTW[/URL] )
What I've added:
Overclocking is possible up to 2.0ghz (be warned, I have not had a chance to completely test it out, and my device only works up to 1.6ghz) (Freqs are from DooM v10)
Governors added:
brazillianwax
smoothass
smartassv2
savagedzen
interactivex
lagfree
Scary
smartass
Original governers
UPDATE: 2012 Feb 12 1055
Noticed that when I switched to DooMLoRD's ramdisk, autobrightness got re-enabled. Fixed that. Uploaded new kernel.
UPDATE: 2012 Feb 13 1335
Changed version from .2 to 1.0
Added IO Schedulers:
Anticipatroy
CFQ
V(R)
SIO
UPDATE: 2012 Feb 13 -- 1400
Realized last update unintentionally removed governors, as soon as I get a stable internet connection, i'll upload completely working kernel.
UPDATE: 2012 Feb 13 -- 1525
Uploaded fixed kernel.
Note: I am not to be held responsible if your device fails you. By flashing this, you are taking your device's ability to work into your own hands. ESPECIALLY WITH OVERCLOCK. TEST BEFORE YOU DECIDE TO SET ON BOOT. IF YOUR PHONES FAILS YOU, IT IS YOUR RESPONSIBILITY
Follow these instructions from Doom if you don't know what to do
download the boot.img
save the boot.img in the folder with fastboot binaries (fastboot.exe files)
power down device
start device in fastboot mode
use the following command to flash the boot.img
Code:
fastboot -i 0x0fce flash boot boot.img
reboot phone and enjoy the kernel
What's Left to be added:
What do people want?
To get into recovery, use the exact same key as you would on DooM's
Sources for code:
Github -- Ramdisk (From ftf, if you really want to mess with this, have fun, but it's not worth the time.): https://github.com/paxchristos/R800x-Ramdisk
Github -- Kernel Source: https://github.com/paxchristos/R800x-2.3.3-Kernel
Big thanks to Keiran/Doom for the help in getting this to work.

---

Reserved for future use

---

Any modifications regarding I/O schedulers & CPU governors? Any additional kernel modules?

---

CrimsonKnight13 said:
Any modifications regarding I/O schedulers & CPU governors? Any additional kernel modules?
Click to expand...
Click to collapse
There well be, as of right now, this is pretty much an alpha release. I'm in class for a little bit, then I'm going to actually flash it (
I just did a fastboot boot) and start bug checking ...
Sent from my R800x using Tapatalk

---

paxChristos said:
R800x Users, I have just compiled a kernel based of the 3.0.1.E.0.99 Sources.
I need a few testers, I will post soon (I literally just got it to boot)
expect more info soon!
Pax
Click to expand...
Click to collapse
I'm game for trying it out.

---

With this kernel we can overclock? Like with SetCPU?

---

I'll try this later when some other stuff is fixed. But nice job.

---

Is this a kernel for 2.3.3?
What's to prevent you from grabbing sources from a later version and doing this?

---

i think this kernel is for unlocked bootloaders???
Because locked can't flash kernels

---

nickholtus said:
i think this kernel is for unlocked bootloaders???
Because locked can't flash kernels
Click to expand...
Click to collapse
There can be kernels that can be flashed with CWM Recovery.
I'm SOOO ready to test! Hit me with your best shot!
EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol

---

Nope we can't flash kernels with cwm on SEMC devices

---

PariahLantern said:
Is this a kernel for 2.3.3?
What's to prevent you from grabbing sources from a later version and doing this?
Click to expand...
Click to collapse
I have a R800x (the Verizon Xperia Play) and I play to focus development on sources exclusively for the R800x. If the R800x gets new sources, I will update code based on that, not sources for GSM.
nickholtus said:
i think this kernel is for unlocked bootloaders???
Because locked can't flash kernels
Click to expand...
Click to collapse
You are correct sir, I was updating between classes and posted the wrong info *fixed*
Selim873 said:
There can be kernels that can be flashed with CWM Recovery.
I'm SOOO ready to test! Hit me with your best shot!
EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol
Click to expand...
Click to collapse
Sorry, only for unlocked boot loaders, my bad
Eventually I might get into other development. First I wanna get this working, perfectly.
nickholtus said:
Nope we can't flash kernels with cwm on SEMC devices
Click to expand...
Click to collapse
Yupp, the /boot partition is locked so we can't flash kernels that way
(hint: if you do (from terminal emulator as root) cat /proc/mtd and you see /boot, you can use CWM to flash kernels.)

---

Kernel v.1 is uploaded and attached to post 1

---

Selim873 said:
There can be kernels that can be flashed with CWM Recovery.
I'm SOOO ready to test! Hit me with your best shot!
EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol
Click to expand...
Click to collapse
Probably. We are gonna end up finding another exploit.

---

paxChristos said:
Yupp, the /boot partition is locked so we can't flash kernels that way
(hint: if you do (from terminal emulator as root) cat /proc/mtd and you see /boot, you can use CWM to flash kernels.)
Click to expand...
Click to collapse
nope u cant see /boot and it cant be flashed to using CWM (on xperia devices)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

DooMLoRD said:
nope u cant see /boot and it cant be flashed to using CWM (on xperia devices)
Click to expand...
Click to collapse
Couldn't we not "find" the boot partition values and then mount the boot partition? Would require a little kernel editing but would be well worth it.

---

KeiranFTW said:
Couldn't we not "find" the boot partition values and then mount the boot partition? Would require a little kernel editing but would be well worth it.
Click to expand...
Click to collapse
I didn't think about that! I would love to try to get at it, but I'm only a user and know nothing of development... I'm sure that'll get cracked eventually.

---

Selim873 said:
I didn't think about that! I would love to try to get at it, but I'm only a user and know nothing of development... I'm sure that'll get cracked eventually.
Click to expand...
Click to collapse
The only problem (that I can see) with what Keiran is suggesting is that the you'd need a custom kernel to affect the /boot partition, which once again, makes it useless for anybody with a locked bootloader...

---

paxChristos said:
The only problem (that I can see) with what Keiran is suggesting is that the you'd need a custom kernel to affect the /boot partition, which once again, makes it useless for anybody with a locked bootloader...
Click to expand...
Click to collapse
I understand that, but since it was based off the stock kernel, would the values be the same for everybody with a locked bootloader? I know that you meant when you said that, but what I was thinking was that someone could dig around the kernel to find those values and what trigger the /boot partition in the first place, then use the correct adb shell command, whatever it is, to make that show up on locked devices. Whether the device is on it's recovery mode (Back+Power) or fastboot (Search+Power) state. Like I said, I don't know anything about developing, and I might just be walking off a cliff at the moment, but it's just a thought.
EDIT: As in looking and thinking on the modified "stock" kernel, and applying on the locked devices. Trial and Error.

---

Just a quick update,
I'm trying to get the overclocking working, but right now it's being a stone cold b*tch with compiling
As soon as I get it working, i'll upload a new kernel version