Hey There,
I've searched ages for an answer, didn't find anything. Please help me!
Story:
I've bought an xperia mini and rooted it with the doomlord_v3 script. Everything was fine... until I accidentally uninstalled Busybox. Titannium stopped working and Bloatware is all over the place!
What I tried:
I can't reinstall Busybox, even though I still have root access. So far I've tried the following Methods:
-Running the Doomlord Script one again
-Stephen Stericson Installer
-Resetting my Phone (+erase of personal data & sd card)
=>Didn't help a bit, I still had root access and errors stayed the same
-Doomlordscript
-JRummy16 Installer
=> tells me, everything is installed, but after installation still shows: not installed
-Stephen Streicson Installer
=> want's to get root access, even though I granted su rights
-Doomlordscript
Since the accident, the Doomlordscript returns the following lines:
---------------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Drücken Sie eine beliebige Taste . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- pushing zergRush"
720 KB/s (23056 bytes in 0.031s)
--- correcting permissions
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- executing zergRush
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2584 KB/s (1075144 bytes in 0.406s)
--- correcting permissions
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- remounting /system
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- copying busybox to /system/xbin/
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- correcting ownership
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- correcting permissions
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- installing busybox
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- correcting permissions
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- correcting symlinks
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
- exec '/system/bin/sh' failed: No such file or directory (2) -
--- rebooting
ALL DONE!!!
Drücken Sie eine beliebige Taste . . .
Click to expand...
Click to collapse
Questions:
What can i do to make busybox work again?
Is there an even harder reset (xperia mini), with the consequence, that the Phone is really in factory state and zergling rush will work again?
Where can I find an answer?
Please Help me! For you are a great hero of humanity.
was Busybox installed in the bin or xbin? ...more it seems that the system partition is read-only mode, to install you have to move it to RW (read / write) mode.
most complete reset would be reflashing a new rom.
it looks like that script "Doomlordscript" fails, because it tries to use busybox itself, the binary "sh" is part of busybox too.
So hm i would guess you could put the busybox onto your device by hand and then create all the symlinks like "sh" to "busybox sh" yourself...
google: "busybox symlink" etc.
use adb shell to copy busybox to your sdcard
Thank you for both of your replies.
I tried to make the installer install both to /xbin and /bin. When everything still worked, busybox was installed in xbin. Sorry for beeing a noob, but how do I mount the partition in RW mode?
I did root my device with the zerg exploit, but the bootloader is still locked. I am now searching for methods that don't require unlocking the bootloader. If anything fails and flashing is my last option, I will have to do it though. Does anyone of you know where to aquire an original rom to flash?
So i tried to follow Dark3n and I am now stuck here:
D:\>adb devices
List of devices attached
425839.... device
D:\>adb shell "su"
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Since every singele tutorial/how to about installing busybox manually requires the adb shell working, I don't really know how to move on. Is there a file explorer, which doesn't require busybox and would enable me to make the needed directories?
You could just try some, "SD Maid" in my signature has an explorer.
There is root explorer, ES File explorer, etc. plenty in the market...
Don't know if they will work though, what happens if you just type "adb shell"...
D:\>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
I found a place where I can download the latest images. I've aleady tried es file explorer, but I don't see the System folder. After Starting SD Maid the following Message Comes up. I translated it from German to English, I might have chosen a formulation different from the original english Error.
Busybox error! Could not use our Busybox :-( To prevent unindended behavior SD Maid will terminate. Please try to restart SD Maid, or reinstall it.....
Click to expand...
Click to collapse
What do you mean by "our busybox" I suppose you don't have an Busybox integrated in you App.
Stupid question:
Does Flashtool require an unlocked bootloader, in oder to flash an original rom?
I have a busybox in my app, but it needs to be set up too.
Apparently basic system tools are missing to set it up.
Hm im running out of ideas here...
I think that busybox uninstaller did remove its own Shell, but not the System link. A solution would be to push a shell in the expected directory. Adb push is working. Unfortunately I don't know where to acquire the original shell, nor where to push it.
Sent from my ST15i using XDA App
Probably have to push it to /system somewhere, but you have to make system writeable i think "adb remount" should do that.
Solved
I solved the Problem by flashing my device.
I've falshed my Phone with the Flashtool. I did try it several times and encountered several errors to wich I will describe the solution here.
At first I workt in an XP environment and Flashtool didn't recognize my Phone, consequeltly t've tried to install several drivers. All failed.
In an Win 7 environment I also failed at the beginning. Flashtool did always ask me wich Phone I did connect and did not recognize it when i I plugged it in flash mode. Log:
27/028/2011 11:28:25 - INFO - Searching Xperia....
27/028/2011 11:28:25 - ERROR - Please plug you device in flash mode
27/028/2011 11:28:26 - INFO - Searching Xperia....
27/028/2011 11:28:26 - ERROR - Please install or reinstall device drivers from drivers folder
27/028/2011 11:28:27 - INFO - Device connected in flash mode
27/028/2011 11:28:27 - INFO - Searching Xperia....
27/028/2011 11:28:27 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/028/2011 11:28:28 - INFO - Searching Xperia....
27/028/2011 11:28:28 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/028/2011 11:28:29 - INFO - Searching Xperia....
Click to expand...
Click to collapse
I finally succeeded when I uninstalled all drivers related to my Phone with USB-deviewer and installed the GordonsGate drivers(you can find them in /flashtool/drivers). Then I connected my Phone in MTP-mode with debugging enabled. Flashtool did not ask to recognize my Phone as it did before, nor did it report wich Phone I connected. Still flashing worked. (With an Xperia Mini you go in flash mode by pressing the Volume Down Button). Log:
27/041/2011 11:41:52 - INFO - Searching Xperia....
27/041/2011 11:41:52 - ERROR - Please plug you device in flash mode
27/041/2011 11:41:53 - INFO - Searching Xperia....
27/041/2011 11:41:53 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:54 - INFO - Searching Xperia....
27/041/2011 11:41:54 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:55 - INFO - Device connected in flash mode
27/041/2011 11:41:55 - INFO - Searching Xperia....
27/041/2011 11:41:55 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:56 - INFO - Searching Xperia....
27/041/2011 11:41:56 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:57 - INFO - Searching Xperia....
27/041/2011 11:41:57 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:58 - INFO - Searching Xperia....
27/041/2011 11:41:58 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/041/2011 11:41:59 - INFO - Searching Xperia....
27/041/2011 11:41:59 - ERROR - USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/042/2011 11:42:00 - INFO - Searching Xperia....
27/042/2011 11:42:00 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&10EF021E&0&5
27/042/2011 11:42:00 - INFO - Start Flashing
27/042/2011 11:42:00 - INFO - VER="R9A029";DATE="20110701";TIME="12:40:00";
27/042/2011 11:42:00 - INFO - Flashing loader
Click to expand...
Click to collapse
Thank you for your Help
I am happy to check out i was of some help for you.
please help me, what is daemon? this is what I got
-----------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible
-----------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 N
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur devi
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
-----------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- cleaning
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing zergRush"
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- executing zergRush
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing busybox
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- remounting /system
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- copying busybox to /system/xbin/
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting ownership
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- installing busybox
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing SU binary
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting ownership
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting permissions
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- correcting symlinks
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- pushing Superuser app
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- cleaning
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- rebooting
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
ALL DONE!!!
Press any key to continue . . .
Can anyone tell me what's the problem here?
---------- Post added at 10:10 PM ---------- Previous post was at 09:20 PM ----------
ah, i think I got it, I just rebooted my phone, thanks
It seems like your ADB drivers aren't properly installed. Ceck put this toutorial:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Edit: Just saw everything is already fine
KillX Kernel
(version 3.4.7)
/!\ DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK / RUIN YOUR PHONE IN ANY WAY /!\
What is ...?
{
"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"
}
What is USB Force Fast Charge?
This allows one to force AC charging for any charger that is detected as USB (e.g. many car chargers) and pull the full current the charger can support.
It also provides additional security when connecting to public charging stations because by forcing AC charging, USB/adb data transfers are disabled, protecting your data.
Fast charge can be toggled by issuing:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
and off:
echo 0 > /sys/kernel/fast_charge/force_fast_charge
Click to expand...
Click to collapse
What is I/O Scheduler?
Input/output (I/O) scheduling is a term used to describe the method computer operating systems decide the order that block I/O operations will be submitted to storage volumes.
I/O Scheduling is sometimes called 'disk scheduling'. I/O schedulers can have many purposes depending on the goal of the I/O scheduler, some common goals are:
+ To minimize time wasted by hard disk seeks.
+ To prioritize a certain processes' I/O requests.
+ To give a share of the disk bandwidth to each running process.
+ To guarantee that certain requests will be issued before a particular deadline.
Click to expand...
Click to collapse
What is msm_thermal?
Kernel based 3-phase thermal control.This replaces your /system/bin/thermald binary which is renamed by the installer to thermald_bkp
Check /sys/kernel/msm_thermal/conf/ for the thermal configuration
allowed_max_high = highest threshold (phase 3)
allowed_max_low = remove the throttling if we cooled down to this (clr_thrshold)
allowed_max_freq = max frequency if throttled (limit)
[...]mid[...] = same as above, just for phase 2
[...]low[...] = Lowest threshold (phase 1)
check_interval_ms = how often shall we check? (sampling rate)
Default: 1000ms = 1sec
Click to expand...
Click to collapse
What is msm_mpdecision?
Kernel based multi core decision
This replaces your /system/bin/mpdecision binary which is ignored in init.rc and renamed by the installer to mpdecision_bkp
+ cpu auto-hotplug/unplug based on system load for MSM multicore cpus [should cpu(x) be online or not?]
+ single core while screen is off
+ extensive sysfs tuneables
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
Code:
startdelay = time until mpdecision starts doing it's magic (20000)
delay = time between checks (70)
pause = if something else plugs in the cpu, fall asleep for 3000ms (3 secs)
scroff_single_core = if the screen is off, don't plug in cpu1/2/3. Additionally: Unplug all cpus except cpu0 when screen is turned off (1)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
min_cpus = min cpus to be online, cannot be < 1. Default: 1
max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
idle_freq = a value against that will be checked if a core +/- is requested. (486000)
If cpu0 is below that value and a core up of another cpu is requested, nothing will happen.
If any other cpu is above that value and a core down of that cpu is requested, nothing will happen. (otherwise it would now put down that cpu even though it is still working, which isn't what we want)
Hot plug thresholds (aka now it gets 'complicated')
This small formula calculates which value will be used: (number_of_cpus_online - 1) * 2
The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.
nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)
Example:
Code:
One cpu is online.
(1 - 1) * 2 = 0 ergo:
nwns_threshold_0 = cpu1 will be hotplugged at this value
((1 - 1) * 2) + 1 = 1
nwns_threshold_1 = cpu0 will be unplugged at this value
Since we can't unplug cpu0 this is '0'.
Two cpus are online.
(2 - 1) * 2 = 2 ergo:
nwns_threshold_2 = cpu2 will be hotplugged at this value
((2 - 1) * 2) + 1 = 3
nwns_threshold_3 = cpu1 will be unplugged at this value
etc...
The default values are:
NwNs_Threshold: 12, 0, 25, 20, 32, 28, 0, 35
TwTs_Threshold: 140, 0, 140, 190, 140, 190, 0, 190
Where the position and function of the number equals the result of the above explained formula
Click to expand...
Click to collapse
Features:
Code:
[FONT=Arial Black][SIZE=2]
* /system rw
* support init.d
* adb root
* swap on
* USB Force Fast Charging
* NTFS, CIFS
* sound hack: Beats
* reduce battery usage: RCU_FAST_NO_HZ = ON
* XZ compressed kernel
* latest wwe boot.img-ramdisk
* Volt control (undervolt or overvolt)
* bus speed max 625 Mhz
* zram
* thermalD
* msm_mpdecision
* allow flash LEDs camera to be used at [B]1% battery[/B] (v[SIZE=2]3.2.4 and below[/SIZE])
* allow WiFi networks with low signal to be seen
* frandom support
* sweep2wake
* gpu cmdline
* gpu freq
(3D: 550000000, 500000000, 450000000, 400000000, 300000000, 266667000)
(2D:200000000, 266667000, 300000000)
* I/O Scheduler : noop, deadline, cfq, sio, row, fiops, bfq
* CPU Governor : msm-dcvs, userspace, powersave, ondemand, performance, Lionheart, DanceDance
* OC : 192000~1910000 [/SIZE][/FONT][CENTER][B][FONT=Arial][SIZE=2][FONT=Arial]
Please read Change log for more info.[/FONT][/SIZE][/FONT][/B][/CENTER]
Installation:
[!] Make sure your device is unlocked and you have CWM/TWRP installed
[!] S-OFF
Code:
1. Download the file
2. flash in recovery ( copy to sdcard or use adb sideload )
Reboot n Enjoy
Thank`s to:
Linus Torvalds, showp1984, faux123, Zarboz, dsb9938, elkay, crpalmer, chad0989, codeaurora.org, kernel.org, linux-foundation.org, xda-developers.com, HTC and all kernel and rom dev !!!
Click to expand...
Click to collapse
DNA_JB_KERNEL_2 | LK_DNA | Beastmode-DNA | Droid DNA Cubed
Click to expand...
Click to collapse
Please use and enjoy it, and if you can make a donation of any amount, I'd appreciate it immensely
Change Log
KillX v1.0.1
Code:
Wed Mar 13 01:50:36 MYT 2013 : Initial release
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
FIX:
(compile error)
* msm: kgsl: Reduce cmd buffer size for adreno_iommu_setstate
* ignore -Wmaybe-uninitialized
* DIV usage mismatch
* #warning "TODO: return_address should use unwind tables"
Set:
* disable /system protect
* version 1.0.1
I/O Scheduler:
* SIO
Add:
* support init.d
* adb root
* swap On
(usb)
* Allow skipping device resume during system resume
* Prevent system suspend when HSIC device is active
* Unknown chargers = AC
* USB Force Fast Charging - Use base from Chad Froebel
INFO:
1. Fast charge can be toggled by issuing:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
and off:
echo 0 > /sys/kernel/fast_charge/force_fast_charge
KillX v1.2.3
Code:
Mon Mar 18 01:30:34 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
FIX:
* sched : rq->lock recursion
* mmc : possible memory leak
* Make : FIOPS Scheduler
* GPU : speed
Set:
* no git local version change (new version!)
* JIT compiler : packet filters default
* Compiler flags
* linaro -O3 compliance
* Not set, CONFIG_THERMAL_PM8XXX
* version 1.2.3
Add:
* support for Google Snappy compression.
* support for FUDGESWAP
* ThermalD (/sys)
* NTFS, CIFS
I/O Scheduler:
* FIOPS
* ROW
Lib:
* memcopy : use glibc [memcpy memmove efficiency issue]
* string : use glibc version [patch memcpy memmove]
Scheduler:
* autogroup patch group by current user android UID instead of task ID
* compute time-average nr_running / run-queue
CPU:
* allow CPU-based alignment handling
* update cpu_power <--according--> cpu load
* optimized RWSEM algorithm
* crypto : Add optimized AES and SHA1 routines
* sched : Improve scalability via 'CPU buddies'
* msm : acpuclock-krait: NULL terminate L2 table for find_cur_l2_level()
* slab : allocator that focuses on per-CPU scaling, SLQB
BUS:
* speed max -> 600
GPU:
* calc busy interval considering GPU freq as float
Sync:
* do_fsync() -> fget_light()
* dynamic sync control
KillX v1.2.9
Code:
*[I]base on Killx Kernel v1.2.3[/I]*
Mon Mar 25 05:11:37 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
Add:
* voltage control
BUS:
* speed max -> 625 MHz
GPU:
* gpu_freq,(bus freq 4) = 500000000
* idle_timeout 10 to HZ/5
* remove strtstp_sleepwake = true
Set:
* FIOPS = Default IO
* PERFLOCK = Off
* local version auto off
* version 1.2.9
+ Increase battery life? Try underclocking and reducing the voltage. [B][U]nandroid backup 1st before playing with it ![/U][/B]
KillX v1.4.3
Code:
Wed Mar 27 01:30:34 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
FIX:
* memory leak in cpufreq stats
* vfs,pipe counter breakage
* keys,race with concurrent install_user_keyrings()
* compat_rw_copy_check_uvector() misuse in aio, readv, writev,
* iommu/msm: the include guard in iommu.h
* ARM: VFP: emulation of second VFP instruction
* ARM: scheduling while atomic warning in alignment handling code
* ARMv7: perf: EVTYPE_MASK to include NSH bit
* crypto: user - info leaks in report API
* compile error, crypto ("")
Add:
* sound hack: Beats
GPU:
* msm: kgsl: Make the GPU device aware of the next pending event
* msm: kgsl: Remove lowest power level
Set:
* [B]reduce battery usage[/B]: RCU_FAST_NO_HZ = ON
* version 1.4.3
* sched : remove HTC attempt to patch exit/rename race condition
* hw_random : make buffer usable in scatterlist
* cifs : ensure that cifs_get_root() only traverses directories
* NFS : Don't allow NFS silly-renamed files to be deleted, no signal
KillX v1.5.3
Code:
Fri Mar 29 11:20:30 MYT 2013 (linux kernel 3.4.11)
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
FIX:
* ipv4 : bug in ping_err()
* sysctl: null checking in bin_dn_node_address()
* rtnl : info leak on RTM_GETLINK request for VF devices
Add:
* PM/Sleep: wakeup_source_activate and deactivate, no wakeup events
* BFQ I/O schedulers
Remove:
* power: legacy wakelock code
Set:
* version 1.5.3
* PM/Sleep: Look for wakeup events in later stages of device suspend
* PM/Sleep: Change wakeup source statistics to follow Android
* XZ compressed kernel
KillX v1.6.5
Code:
Wed APR 10 10:22:30 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
FIX:
* posix-cpu-timers: nanosleep task_struct leak
* clock-8960 : gfx3d, VDD_DIG_HIGH
* fs : proc,stat: not showing all cpus
* fs : cifs, warning: 'midQ' may be used uninitialized in this function
Add:
* tun : add a missing nf_reset() in tun_net_xmit()
* Makefile: Snapdragon optimizations
* GPU : 2d_freq, 3d = 5 level (550000000)
* cgroup : generic cgroup subsystem permission checks
Remove:
* sysctl.conf
Set:
* Disable CONFIG_MSM_SHOW_RESUME_IRQ
* Don't force RUN_QUEUE_STATS to be on
* version 1.6.5
Update:
* new wwe boot.img-ramdisk
* rwsem: steal writing sem for better performance
KillX v2.1.0
Code:
Wed APR 17 12:34:45 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
FIX:
* LOAD_FREQ : avoids loadavg Moire http://ripke.com/loadavg/moire
* resume drivers/video/backlight/adp88?0_bl.c
* tmpfs : use-after-free of mempolicy object
* drivercore: ordering between deferred_probe and exiting initcalls
* clock-8960: gfx3d
Add:
* cmdline function for GPU control (default: 3dgpu=500000000 2dgpu=300000000)
! need s-off to change this value with aroma installer.
Remove:
* duplicate: drivers/staging/media/Kconfig
* cpu_is_msm8625
* logcat (disable logcat - performance boost & save memory)
Set:
* msm_hsic: decrease timeout, 500 to 120
* CONFIG_DEBUG_SECTION_MISMATCH=y
* version 2.1.0
OC:
* 192000~1674000
msm/mdp/fb/thermal:
* Send fake vsync only when enabled from userspace
* Disable vsync in video off.
* force vsync in board file
* display : Fix flickering when BLT is enabled/disabled
* display : blt always enabled for 720p,1080p, secure buf
* reduce verbose messages, Limiting cpu
* drivers.thermal: updating msm8960tsens
* Patching thermalD upstream
tty:
* Prevent deadlock in n_gsm driver
* set_termios/set_termiox should not return -EINTR
cpufreq:
* cpufreq: Convert the cpufreq_driver_lock to a rwlock
* cpufreq: Convert the cpufreq_driver_lock to use RCU
mmu_notifier:
* have mmu_notifiers use a global SRCU
* make the mmu_notifier srcu static
* unregister NULL Pointer deref and multiple
drm/udl/usb:
* make usage as a console safer
* disable fb_defio by default
* don't add inferred modes for monitors that don't support them
* Fill depth/bits_per_pixel for C8 format
* Use C8 instead of RGB332 when determining the format from depth/bpp
* bind driver to correct device
* vgacon/vt : clear buffer attributes when we load a 512 character font (v2)
* Driver core : treat unregistered bus_types as having no devices
* futex : Mark get_robust_list as deprecated
* inotify : remove broken mask checks causing unmount to be EINVAL
* fs/block_dev.c: page cache wrongly left invalidated after revalidate_disk()
* ocfs2 : unlock super lock if lockres refresh failed
* mm/fadvise.c : drain all pagevecs if POSIX_FADV_DONTNEED fails to discard all pages
* umount oops when remove blocklayoutdriver first
* NLM : Ensure that we resend all pending blocking locks after a reclaim
* ALSA : hda - Release assigned pin/cvt at error path of hdmi_pcm_open()
KillX v2.1.2
Code:
Thu Apr 18 11:06:32 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
Add:
* init files
Set:
* safe default min and max speeds
KillX v2.3.1
Code:
Mon Apr 22 10:02:03 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
Fix:
* drivers/video: fsl-diu-fb: pixel formats for 24 and 16 bpp
* fbcon : don't lose the console font across generic->chip driver switch
* fb : rework locking to fix lock ordering on takeover
* fb : Yet another band-aid for fixing lockdep mess
* mmc : sdhci-esdhc-imx: host version read
* hid : wiimote: nunchuck button parser
* net : infinite loop in __skb_recv_datagram()
* net : compile error when SOCK_REFCNT_DEBUG is enabled
* sock_diag : out-of-bounds access to sock_diag_handlers
* usb : ehci-omap: autoloading of module
Add:
* msm: mpdecision: in-kernel CPU hotplug management
Set:
* safe default min and max speeds
* bridge: priority of STP packets
* use memcpy for copy to/from user-space
Arm:
* PXA3xx: program the CSMSADRCFG register
* 7643/1: sched: correct update_sched_clock()
Gpu:
* gpu: 3dgpu remove 27000000,level=4, change valid_freq for 2dgpu&3dgpu
* init_level 3 (3D&2D)
Net:
* xen-netback: correctly return errors from netbk_count_requests()
* xen-netback: cancel the credit timer when taking the vif down
* ipv6 : use a stronger hash for tcp
* vlan : adjust vlan_set_encap_proto() for its callers
* dca: check against empty dca_domains list before unregister provider
* usb: usb-storage: unusual_devs update for Super TOP SATA bridge
KillX v2.5.8
Code:
Mon Apr 29 01:14:58 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
Fix:
* cpuinit: #2
find -name "*.c" | xargs sed -i "s/ __cpuinit / /g"
* cpuexit: #1
find -name "*.c" | xargs sed -i "s/ __cpuexit / /g"
* cpuinitdata: #1
find -name "*.c" | xargs sed -i "s/ __cpuinitdata//g"
* cpuinit: #3
find -name "*.c" | xargs sed -i "s/ __cpuinit$//g"
* cpuinit: #4
find arch/ -name "*.h" | xargs sed -i "s/ __cpuinit//g"
* cpuinit: #5
find -name "*.c" | xargs sed -i "s/^__cpuinit //g"
* cpuinit, manual fixups
* init/Kconfig : typo SLQB
* ARM: 7011/1 : Add ARM cpu topology definition #2
* scheduler : compute time-average nr_running per run-queue #2
* scheduler : Re-compute time-average nr_running on read
* proc : enhance time-average nr_running stats #2
* posix-cpu-timers: nanosleep task_struct leak
* USB : serial: null-pointer dereferences on disconnect
Add:
* Lionheart Governor
* Dance Dance Governor
* Zram
* allow flash LEDs to be used at 1% battery
* allow WiFi networks with low signal to be seen
* frandom support
Set:
* Lionheart Governor as default
* changed max readahead buffer size to 2048
* wifi: enabled PM_FAST by default
* row default IO
* GPU : 3dgpu=450000000 2dgpu=266667000 cmdline
* safe default min and max speeds #2
* version 2.5.8
Remove:
* adaptive in init.target.rc (because all htc decisions moved to kernel code)
Makefile:
* kernel: Makefile, CONFIG_CC_OPTIMIZE_ALOT
* adding config variable for Os/O2/O3 compilation
* acpu : export krait variant to debugfs
* rwsem : Writer lock-stealing
* PM : Introduce suspend state PM_SUSPEND_FREEZE
(saves less power because the system is still in a running state)
* wakelock: suspend_freeze
* b43 : Increase number of RX DMA slots
+ mod with aroma installer !
KillX v2.5.9
Code:
Tue Apr 30 18:18:45 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
Fix:
* kernel init.d, setting script
Aroma installer:
* msm_mpdecision idle_freq - done
* gpu o/c freq
Set:
* version 2.5.9
KillX v3.0.0
Code:
Thu May 9 10:51:22 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
Fix:
* acpu_freq_tbl_8064_slow
* block : ext_devt_idr handling
* block : synchronization and limit check in blk_alloc_devt()
* cgroup : exit() vs rmdir() race
* cpufreq : default value
* cpuset : cpuset_print_task_mems_allowed() vs rename() race
* fs : possible use-after-free with AIO
* idr : a subtle bug in idr_get_next()
* multiple definition of `cmdline_3dgpu' & `cmdline_2dgpu'
* net/sunrpc: 'subbuf.[...]' may be used uninitialized
* nfsd : memleak
* ocfs2 : ocfs2_init_security_and_acl() to initialize acl correctly
* ocfs2 : possible use-after-free with AIO
* perf tools: build with bison 2.3 and older
* s2w leds
* target : divide by zero bug in fabric_max_sectors
* target : lookup of dynamic NodeACLs during cached demo-mode operation
* vhost : length for cross region descriptor
Add:
* cpu min/max, screen off, gov, io cmdline
* cpu oc to 1910000 (no option in aroma installer)
* sweep2wake
* target : missing mapped_lun bounds checking during make_mappedlun
Remove:
* cpufreq remove msm-dcvs (aroma)
* if overclock
* sched: HTC attempt to patch exit/rename race condition
Aroma installer:
* CPU min/max/screen off cmdline
* IO cmdline
* fix replace boot cmdline
Set:
* MSM_MPDEC_PAUSE 3000
* Makefile: kernel: workqueue O3 compilation
* config : CONFIG_MUTEX_SPIN_ON_OWNER=y
* config : CONFIG_UACCESS_WITH_MEMCPY = No
* config : FREQ_STAT & Detail
* version 3.0.0
* vreg core krait* 1450000
Cleanup:
* board-deluxe_ub1-gpu code
* ASoC : wm2200: correct IN2L and IN3L digital mute
* Kconfig : Enable cmdline khz/gov/maxscroff command parsing
* comedi_fops: update
* ftrace : Call ftrace cleanup module notifier after all other notifiers
* fuse : don't WARN when nlink is zero
* media : rc: unlock on error in show_protocols()
* ocfs2 : ac->ac_allow_chain_relink=0 won't disable group relink
* posix-timer: Don't call idr_find() with out-of-range ID
* pstore : Avoid deadlock in panic and emergency-restart path
* quota : autoload the quota_v2 module for QFMT_VFS_V1 quota format
* staging : comedi: comedi_fops: update
* staging : comedi: disallow COMEDI_DEVCONFIG on non-board minors
* staging : comedi: ni_labpc: correct differential channel sequence for AI cmd
* staging : comedi: ni_labpc: set up command4 register *after* command3
* svcrpc : make svc_age_temp_xprts enqueue under sv_lock
* unbreak automounter support on 64-bit kernel with 32-bit userspace (v2)
KillX v3.2.1
Code:
Wed May 15 00:01:59 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
Ramdisk
* init.rc s-on 1
* init.target.rc
Aroma
+ S-Off / S-On user
+ msm_mpdecision boost cpu min, on/off
+ set default Max Screen Off clock @ 540mhz
Fix:
* Bluetooth: not closing SCO sockets in the BT_CONNECT2 state
* Btrfs : don't drop path when printing out tree errors in scrub
* Btrfs : race between mmap writes and compression
* Btrfs : space leak when we fail to reserve metadata space
* sysfs : handle failure path correctly for readdir()
* sysfs : race between readdir and lseek
* usb : gadget: udc-core: regression during gadget driver unbinding
* usb : xhci: TRB transfer length macro used for Event TRB
Revert:
* vreg[VREG_CORE]
Remove:
* video: msm:mdp pr_warn _mdp_histogram_crtl start false
Use:
* __ARCH_HAS_SA_RESTORER
Update:
* dynamic filesync: add some cache optimizations v1.1
* efivars
* mach-msm: Kconfig
* msm_mpdecision
* msm_thermal
* row io
Set:
* Btrfs: limit the global reserve to 512mb
* version 3.2.1
* efivars : explicitly calculate length of VariableName
* loop : prevent bdev freeing while device in use
* net/irda : add missing error path release_sock call
* nfsd4 : reject "negative" acl lengths
* pnfs-block : removing DM device maybe cause oops when call dev_remove
* vt : synchronize_rcu() under spinlock is not nice
KillX v3.4.5
Code:
Sun May 19 10:40:39 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
Aroma
+ wipe dalvik-cache
+ fix writeprop
Add:
* drivers: base: sw_sync
Fix:
* bonding : disabling of arp_interval and miimon and arp_interval
* ks8851 : interpretation of rxlen field
* net : *_DIAG_MAX constants
* unix : race condition in unix_release()
* fs : sync.c vfs_emergency_remount
Remove:
* bonding : already created master sysfs link on failure
* drivers : cpufreq, CONFIG_CPUFREQ_LIMIT_MAX_FREQ
* net : WARN_ON() in net_enable_timestamp()
Revert:
* dynamic filesync : add some cache optimizations v1.1
* video : msm:mdp pr_warn _mdp_histogram_crtl start false
* revert : allow flash LEDs to be used at 1% battery
Update:
* ipv6 : addrconf
* ipv6 : ip6_input
* sysfs : dir.c
* base.img
Set:
* version 3.4.5
* aoe : reserve enough headroom on skbs
* bonding : get netdev_rx_handler_unregister out of locks
* sky2 : Receive Overflows not counted
* sky2 : Threshold for Pause Packet is set wrong
* tcp : preserve ACK clocking in TSO
* tcp : undo spurious timeout after SACK reneging
* thermal : shorten too long mcast group name
* tracing : Prevent buffer overwrite disabled for latency tracers
KillX v3.4.7
Code:
Wed May 22 22:43:58 MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
Add:
* cifs : Add handling of blank password option
* cifs : Allow passwords which begin with a delimitor
Set:
* version 3.4.7
EXPECTED CHANGELOG
KillX vx.x.x
Code:
xxx xxx xx xx:xx:xx MYT 2013
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1)
todo:
Confirmed:
- KillX Kernel can be applied on Sense 5 Build (front camera with face sensor not working)
- Can not be applied on KillX Rom (Leaked sense 5), A4TW BOA Butterfly / Sense 5 4.2.2 ROM
- It proved, better battery life !
want more? Compile it by yourself !
DOWNLOADS :
* Kernel Base : Butterfly WWE 3.4.10 v4.1 1.09.707.4 99.5MB
OLD Version
Code:
[1] [URL="http://192.210.138.17/KillX/killx101.php"]killx1.0.1.zip[/URL] [B]MD5[/B]: d4aa61db1130f3977e6f6f16a3a7eb01
- killx1.img [B]MD5[/B]: 1e513e257e8678a59c98b2fa371974e7
- killx_mod_1.0.1.zip [B]MD5[/B]: f54973ba06656c4fc4015a4fc9b57d6d
[2] [URL="http://192.210.138.17/KillX/killx123.php"]killx1.2.3.zip[/URL] [B]MD5[/B]: 0f3a5fd4668800399cb7d1aa24c62cde
- killx123.img [B]MD5[/B]: 8274d050edfc636d4b0be0e56c5aed96
- killx_mod_1.2.3.zip [B]MD5[/B]: 2620b024ff1cff495b38da6b401b3912
* re upload on : 2:01 AM 3/19/2013 : fix [B]updater-script[/B] *
[3] [URL="http://192.210.138.17/KillX/killx129.php"]killx1.2.9.zip[/URL] [B]MD5[/B]: 4a78c2846c54c9ac0dfc44109e630af7
- killx129.img [B]MD5[/B]: ab4c4f9b7472d5da3e23a6d565c4426e
- killx_mod_1.2.9.zip [B]MD5[/B]: 4e2788e38a4cae6f8276aecab418cb4e
[4] [URL="http://192.210.138.17/KillX/killx143.php"]killx1.4.3.zip[/URL] [B]MD5[/B]: 017d2dccfd64d5425ad412460bb10780
- killx143.img [B]MD5[/B]: 41617e99b02986d96c731893fdd7e397
- killx_mod_1.4.3.zip [B]MD5[/B]: 991bee91acd69c7ded980f12429e63df
[5] [URL="http://192.210.138.17/KillX/killx153.php"]killx1.5.3.zip[/URL] [B]MD5[/B]: e578399c3b7b34008c4f54446a819f89
- killx153.img [B]MD5[/B]: 71d8e116f87ad7a77796fa8cbac80b89
- killx_mod_1.5.3.zip [B]MD5[/B]: a1e7c03fd6ab60aac742b752eb11a9e8
[6] [URL="http://192.210.138.17/KillX/killx165.php"]killx1.6.5.zip[/URL] [B]MD5[/B]: eac178abd293cbaaa430b72ef1b3a7b9
- killx165.img [B]MD5[/B]: 66fd326783c5e2efe2979bc79ad03499
- killx_mod_1.6.5.zip [B]MD5[/B]: 8864afc3cc85d1e6331f361cc06d2dd0
[7] [URL="http://192.210.138.17/KillX/killx210.php"]killx2.1.0.zip[/URL] [B]MD5[/B]: a87746438d57145de5221b5ab0de28a9
- killx210.img [B]MD5[/B]: 47bf37a9418ffef2971f573347607287
- killx_mod_2.1.0.zip [B]MD5[/B]: ad537a6e56c13c2105e0b238e98441ba
[8] [URL="http://192.210.138.17/KillX/killx212.php"]killx2.1.2.zip[/URL] [B]MD5[/B]: 8501e8dc3ef82451e6b7268c35826d5d
- killx212.img [B]MD5[/B]: 419b3071d6bcec40458532ac5d04f32f
- killx_mod_2.1.2.zip [B]MD5[/B]: 12cdf8507cd7c0aece29b9a4eb11368b
[9] [URL="http://192.210.138.17/KillX/killx231.php"]killx2.3.1.zip[/URL] [B]MD5[/B]: 0d5061e8a26d5fc13058adddcf821579
- killx231.img [B]MD5[/B]: caa9315de125554893c6d6aed6bc1d04
- killx_mod_2.3.1.zip [B]MD5[/B]: 63002dccc0aa2187bdc33053d9293a29
[10] [URL="http://192.210.138.17/KillX/killx258.php"]killx2.5.8.zip[/URL] [B]MD5[/B]: c5dcf1c2038084b18bfb4e50d8fb55fc
- killx258.img [B]MD5[/B]: 6c41a02a34ef861bcae6fe79f4a7e2ce
- killx_mod_2.3.1.zip [B]MD5[/B]: 1d4ac941599803956d854ef43e09ea79
Code:
---[ start this version, recommended you to have s-off 1st ]---
[11] [URL="http://192.210.138.17/KillX/killx259.php"]killx2.5.9.zip[/URL] [B]MD5[/B]: 966450358494c90fd83ad317cc32ff12
[12] [URL="http://192.210.138.17/KillX/killx300.php"]killx3.0.0.zip[/URL] [B]MD5[/B]: c7b11fe979e5fe5c2db75dcb0ccd4e16
[13] [URL="http://192.210.138.17/KillX/killx321.php"]killx3.2.1.zip[/URL] [B]MD5[/B]: d3633ca6d8ba61a693697e622834ac42
[14] [URL="http://192.210.138.17/KillX/killx345.php"]killx3.4.5.zip[/URL] [B]MD5[/B]: f11014172208bb297787ba176506f34e
[15] [URL="http://192.210.138.17/KillX/killx347.php"]killx3.4.7.zip[/URL] [B]MD5[/B]: df6bd4822d28c61f83c9ae13e38f2f84
S-On user : Please follow this step
My GitHub
will this work on stock rom? any chance of exfat support?
Can flash for unrooted rom?
hi, i am using "Virtuous Butterfly" rom and its based on "1.12.709.1". so can you make a boot.img for this too?
Re: [KERNEL][13.03.2013] Butterfly KillX v1.0.1
Thx! Mate testing now^^
Sent from my HTC Butterfly using xda premium
deweylim said:
will this work on stock rom? any chance of exfat support?
Click to expand...
Click to collapse
Try it, this kernel is build for X920D.
intania said:
Can flash for unrooted rom?
Click to expand...
Click to collapse
You will need the bootloader unlocked to be able to use and flash with fastboot. Unrooted rom, no problem.
ruthless10001 said:
hi, i am using "Virtuous Butterfly" rom and its based on "1.12.709.1". so can you make a boot.img for this too?
Click to expand...
Click to collapse
If you have X920D, no problem. Just flash this kernel and modules..
it2007me said:
DOWNLOADS :
Code:
[B][URL="http://forum.xda-developers.com/attachment.php?attachmentid=1800028&d=1363115916"]killx1.0.1.zip[/URL]
- killx1.img
- killx_mod_1.0.1.zip
MD5: d4aa61db1130f3977e6f6f16a3a7eb01
Kernel Base On: Butterfly WWE 3.4.10 v4.1 1.09.707.4 [URL="http://dl4.htc.com/RomCode/Source_and_Binaries/dlxub1-jb-crc-3.4.10-8bc6f3ed.zip"]99.5MB[/URL]
[/B]
kernel-source-code
Enjoy It~!
Click to expand...
Click to collapse
Thanks for new custom kernnel for Butterfly. I flashed it. All went smoothly. I'll report latter.:laugh::laugh::laugh::laugh:
Anyway I can bribe you to make one for the x920e?
jlevy73 said:
Anyway I can bribe you to make one for the x920e?
Click to expand...
Click to collapse
ok, i will try..but i don't have X920E, will you test it for me?
Hello i am using your other kernel, do i need to flash again the boot.img? im asking cause i am 5km away from my pc, i cant flash boot.img of this kernel. TIA
it2007me said:
ok, i will try..but i don't have X920E, will you test it for me?
Click to expand...
Click to collapse
It would be my pleasure to test.
royskeyz said:
Hello i am using your other kernel, do i need to flash again the boot.img? im asking cause i am 5km away from my pc, i cant flash boot.img of this kernel. TIA
Click to expand...
Click to collapse
if want this kernel..you have to flash the boot.img of this version.
Because we don't have S-Off yet for Butterfly, need a pc to flash a kernel (use fastboot.exe)
jlevy73 said:
It would be my pleasure to test.
Click to expand...
Click to collapse
can u sent me your boot.img(X920E), i don't want to d.load the whole x920e RUU
it2007me said:
can u sent me your boot.img(X920E), i don't want to d.load the whole x920e RUU
Click to expand...
Click to collapse
sure, here you go.
Re: [KERNEL][13.03.2013][X920D] Butterfly KillX v1.0.1
Awesome, testing now with sio and init.d
EDIT: is it possible to put in row instead of sio? I believe you compiled sio as modules, same should be achievable for row.
Sent from my HTC Butterfly using xda app-developers app
Can you ported Droid DNA kernels like this(Beastmode Viverrine B3.8 | S2W MPDEC ThermalD, 1.9ghz, Linaro 4.8 -O3) : http://forum.xda-developers.com/showthread.php?t=2021714 for X920D\X920E users? Or simply added Sweep2Wake and OC CPU/GPU for your kernel?
*** ##TUTORIAL ...
HOW to Port ROMs...
For Begineers & Advanced Users
Almost Any Device to Any Device!
ONLY FOR MEDIATEK SoCs
In This Guide You'll Learn..
How to Port ROMs From the Same CPU
HOW TO PORT ROM FROM
DIFFERENT SoC!!!!!
Works for-
MT6589 to MT6577
MT6582 to MT6572
MT6577 to MT6575
Only ICS to ICS & JB to JB
May also work with 4.1 to 4.2
No Need of Source Code
No Need of Kernel Source
No Need of **ANDROID KITCHEN
No Need of LINUX...
Requirements:
* A Brain
* Patience
*Es File Explorer or
*Bluetooth File Transfer
*Rom toolbox
* Stock ROM
* And a Little Respect!!
So now Lets Begin...
PORTING For Same SoCs ( Ex: MT6572 to
MT6572)
:good:
Porting procedures rom (MT6589, MT6582, MT6572) (or
vice versa)
Read and follow the steps well both individually correctly:
* Extrack rom port into a folder that is named PORT
* Extrack stock rom into a folder that is named STOCK
* Note both good
* Copy and replace files Stock to PORT as follows:
* System / vendor
* System / usr
* System / lib / modules
* System / lib / hw
* System / lib / libncurses.so
* System / etc / firmware
* System / etc / vold.fstab
* System / etc / vold.fstab.nand
* System / etc / bluetooth
* Open build.prop and find a line of text as follows:
ro.mediatek.platform = MT65xx
(Converted to the type of your device)
example:
ro.mediatek.platform = MT6572
* META-INF/google/android open, then open the updater-
script file using a text editor
* Add this line between the lines of "set_perm"
set_perm (0, 0, 0644, "/ system/vendor/lib/hw/
gralloc.mt65xx.so");
[Replace with your mt65xx cpu]
example
set_perm (0, 0, 0644, "/ system/vendor/lib/hw/
gralloc.mt6572.so");
* Now Go back to the Rom folder and Take the boot.img
and decompile it with any bootimg-unpack tool! (This
step can be skipped)
* Now delete and rename the zImage boot.img-ramdisk
to PORT-Ramdisk
* Now Do the Same for Stock boot.img and open the
folder named PORT-ramdisk and copy all the files from PORT-
boot.img-ramdisk to ramdisk of boot.img Stock Cell
* Now Go to boot.img-ramdisk and open init.rc
* Now find these lines and replace with your cpu
Chip # Create Property
on early_property: ro.hardware = mt6589
setprop ro.mtk.hardware mt6589
on early_property: ro.hardware = mt6589
setprop ro.mtk.hardware mt6589
example
# Create Chip Property
on early_property: ro.hardware = mt6582
setprop ro.mtk.hardware mt6589
on early_property: ro.hardware = mt6572
setprop ro.mtk.hardware mt6589
For Fixing Problems...
*system/etc/permissions
*system/etc/security
*system/etc/audio
*system/etc/wifi
*system/lib/drm
*system/lib/egl
*system/lib/soundfx
END STAGE
# Before zipping Cusrom make sure the contents of the
folder Port has an arrangement like this
- Meta-Inf
- system
- boot.img
# If it is like a living doing just above the zipping process
by using Es file Explorer or Bluetooth file transfer similar applications,
* A few - Good luck *
------Niks--------
wow, is it possible to do it with the newer SOC's ? for example the MTK6752?