FORUMS

Earthquake Early Warning in Your Pocket

Probably all of us reading this have a smartphone in our pocket. For many of us, the … more

Sony: The OEM You Want To Save

In our recent Discuss article, we asked you readers on which OEM you would like to help. While the … more

How to Lock and Protect Your Apps – XDA Xposed Tuesday

The smartphone revolution has passed. Everybody has mobile apps. Some of … more

Which OEM Would You Like to Help?

Most manufacturers have moments of greatness and moments of decadence, and in the past few years … more
Thread Deleted Subscribe to Thread Email Thread
Prev Previous Post   Next Post Next
I try to implement 2nd-init method (Motorola Milestone/Defy/etc) to hijack ramdisk.
With this method, we can change stock ramdisk, and we can boot CM with stock kernel...
Here's KeiranFTW's original thread too: http://forum.xda-developers.com/show....php?t=2608408, but I used 2nd-init instead of chroot

So, i'm done with following steps:
Successfully implement recovery and hijack ramdisk...
I can replace ramdisk contents with new one...
I can boot CM10.2, but it has defects:
Kernel and user space graphical drivers are mismatch, screen is yellowish (no blue), and a lots of mdp errors in dmesg, and no boot animation
no radio
there's some problem with /data/ / sdcard mount...

So i call for help, because i've limited time for this project, but it can interesting...

If you want to try it, do the following steps:
get hijack from here: https://github.com/dh-harald/hijack-ramdisk-huashan
get CM from source (preferred) or fxp, and delete boot.img from zip (and connected lines from update-script)
(optional) replace jelly.tar and recovery.tar to your device specific ramdisks, if you're on other device than Xperia SP
go to recovery, apply CM, (optional gapps), copy chargemon and hijack.tar to /system/bin and fix rights, and factory reset...
install 4.3 kernel only via flashtool (if you aren't on 4.3)...

Known problem, that you need original kernel modules too, to get wifi working (not tested)

I think, it's mainly CM configuration, but it maybe helps, when CM team starts to use Sony's 4.3 kernel based CM kernel...

Any helps are welcome...

Here's a screenshot about cm and locked bootloader and stock kernel... It's a bit confusing, because when i screenshot it via ddms, colors are fine, but in screen, there's no blue color, only yellow...

EDIT:
I've found that radio/fs problems are selinux related...

EDIT: Current status:
No wifi
No sdcard on /sdcard (only /data/media)
Got baseband, but still no radio
Visible glitches, yellowish screen (aosp <-> caf ?)
Attached Thumbnails
Click image for larger version

Name:	Screenshot_baseband.png
Views:	1060
Size:	129.9 KB
ID:	2593125  
Last edited by dh.harald; 21st February 2014 at 10:26 PM.
The Following 12 Users Say Thank You to dh.harald For This Useful Post: [ View ]
Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes