Post Reply

[KERNEL][GPL]2013-03-02 b24 motley kernel for the Prime (4.2.2 alpha)

6th March 2012, 05:08 AM   |  #1  
_motley's Avatar
OP Senior Member
Thanks Meter: 2,407
 
858 posts
Join Date:Joined: Aug 2010
Donate to Me
_motley kernel for the Prime

Disclaimer: You know the gig...I am not responsible for damaging your device or voiding your warranty. Play at your own risk!

New version released for testing on 4.2.2 ROMs I see popping up since this is likely our future unless Asus releases something. I have been dev'ing for the N4 and N7 lately, so I haven't had a lot of time to keep up with the Prime. However, I wanted to stop by to share the kernel I built over the course of the last two nights for my own device.

Features:
  • Forked from namidairo (thanks!)
  • OC to 1.7GHz
  • GPU OC to 600MHz - configurable from 520-650MHz (see below)
  • Voltage Control (use Trickster or System Tuner)
  • Removed system_mode from Asus - boots to 1.4GHz - control with standard apps (use Trickster or System Tuner)
  • FSYNC - 3 modes (see below) (use Trickster)
  • Linaro built with optimizations
  • Kernel log spam reduced - important for our crappy eMMC
  • optimized ARM RWSEM algorithm
  • Other misc tweaks (see github)

Build 24 (beta)
  • Initial release for 4.2.2
  • AnyKernel install works on 32GB Primes only
  • Added blob based installs for CM 10.1 and PA. Read notes carefully below when choosing an install zip.

motley_anykernel_tf201_build_24.zip - 32 GB Primes ONLY (any 4.2.2 custom ROM)
motley_b24_CM.zip.zip - CM10.1 based ROMs only (blob based install for 32/64GB Primes)
motley_b24_AOSP_PA.zip - PA/AOSP 4.2.2 ROMs only (blob based install for 32/64GB Primes) (only tested on PA thus far! Using PA ramdisk as donor.)

Git repo:
https://github.com/motley-git/android_kernel_asus_tf201


GPU OC

Examples:

Code:
echo 520 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Code:
echo 650 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc

FSYNC Control

Notes: I thought about combining these options, but many kernel apps already support these two options. So, I have them both and they can be controlled in combination to give us the 3 modes. If you set fsync_enabled = 0 it will be OFF regardless of how Dyn_fsync_active is set.

3 Modes:

Dynamic (default in b35 and higher)- fsync is asynchronous when screen is on, when screen is off it is committed synchronously
dynamic fsync ON
fsync ON
Code:
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
Off (best performance, less safe) - fsync is always asynchronous (b32 and prior builds)
dynamic fsync OFF
fsync OFF
Code:
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
Stock (safest) - fsync is always committed synchronously
dynamic fsync OFF
fsync ON
Code:
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
There is a lot of info out there on fsync, that will not be discussed here. I have run fsync off on several devices for awhile now and haven't experienced any issues. If you are using a device that is not stable and crashes alot, I recommend enabling it via init.d or script manager on boot.


See all my old tf201 kernel versions for ICS here:
 

Requirements (please read carefully!)
  • alpha version is stable for most, but changes often until we hit a good stable version. Let me know how it works!
  • Do a CWM backup so you can restore your boot.img and ROM if necessary!
  • 64GB tabs please use blob based install with ramdisk. Anykernel method may not work on 64GB tablets
  • Recommend 1.6 or 1.7GHz. I have scored 14300+ on Antutu with 1.7GHz. 1.8 is just not necessary IMO and generates too much heat.
  • ICS ROMs only
  • You must be rooted with busybox. Busybox is used for init.d support.
  • You must be unlocked (Asus Unlock Tool provided on their web site)
  • Official CWM with latest update (see http://forum.xda-developers.com/show....php?t=1533697)
  • You should have your current full and a stock ROM including kernel on your sdcard (just in case). This is always a good idea anyhow.
  • Beware of third party tweaks that may conflict. If you have installed another app that will load conflicting kernel modules or provide overclocking capability for the stock kernel, please uninstall or disable this on boot before you install this kernel. For example, if you are using ATP Tweaks and are loading the CFQ or SIO schedulerd at boot, it can cause a crash as soon as the conflicting kernel module loads into memory. This kernel now includes the many features that folks were previously using kernel modules for. Since this kernel supports these features natively, you know longer need to load a kernel module manually or via a third party application unless the feature is not listed above. For example, if you use CIFS Manager, you should remove the requirement to load the CIFS kernel module in the settings as it is no longer needed with this kernel.

Stock/AOKP versions
  • Still using stock broadcom WiFi drivers (module built by me match stock modules)
  • Still use same scaling scripts from before (cpu3.sh etc.) or installed 2.6.11 first and then flash this kernel to be sure you have them right.
  • Same system modes apply as before (system_mode=3 for 1.6GHz, system_mode=4 for 1.7GHz, system_mode=5 for 1.8GHz etc.)

Generic kernel versions
  • Supports Gummy, Team EOS, and CM9 since they have the same WiFi driver implemented in their device trees.
  • No need to use an OC app (SetCPU, No-frills etc.) to set the clock.
  • WiFi driver is built-in (no kernel modules) using opensource broadcom drivers (nl80211)
  • KSM=y (ROM needs to enable KSM in dalvik and set scan in the init file like in CM9)
  • Overclock - needs init.d to be functional to run a init.d script on boot (see sample script below).
  • Same system modes apply as before (system_mode=3 for 1.6GHz, system_mode=4 for 1.7GHz, system_mode=5 for 1.8GHz etc.)
  • If you don't get deep sleep, make sure you have implemented the init.d script properly. "echo N > /sys/module/cpu_tegra3/parameters/no_lp" seems to be necessary on generic ROMs to get the proper deep sleep.



"Lite" kernel
This kernel version has been kept very close to stock form, except for OC and some basic features. The kernel won't be updated often, only when Asus releases new versions or an important fixable bug is discovered.

"Lite" Features
  • Based on stock Asus v9.4.2.28 base
  • Simple I/O scheduler as the default
  • OC from 1.5 to 1.7GHz (system_mode 3 = 1.5GHz, 4 = 1.6GHz, 5 = 1.7GHz)
  • Compiler optimizations (-o2), ARM toolchain - Code Sourcery Lite 2010.09-51
  • initramfs changes from stock - init.d support (your ROM must have the /system/etc/init.d folder and busybox) and the default.prop has been updated with ro.secure=0 (for "adb remount")
  • CIFS support (built-in, no need for kernel module)
  • NTFS/exFAT modules are provided in stock ramdisk - uses stock Tuxera modules. See http://www.tuxera.com/) - modules are loaded during init automatically with included initramfs.
  • Kernel compression mode LZMA
  • Input devices - PS3 (stock), XBox (CONFIG_INPUT_FF_MEMLESS and CONFIG_JOYSTICK_XPAD_FF), Other input device support (CONFIG_HID_APPLE, CONFIG_INPUT_MOUSEDEV, CONFIG_HID_LOGITECH)
  • Networking/VPN - in addition to stock: CONFIG_L2TP, CONFIG_IP_ADVANCED_ROUTER, CONFIG_NET_IPIP, CONFIG_NET_IPGRE, CONFIG_IP_MULTIPLE_TABLES, CONFIG_INET_AH, CONFIG_INET_IPCOMP, CONFIG_INET_XFRM_TUNNEL, CONFIG_INET_XFRM_MODE_TUNNEL, CONFIG_INET_XFRM_MODE_BEET, CONFIG_L2TP_DEBUGFS, CONFIG_L2TP_V3, CONFIG_L2TP_IP, CONFIG_L2TP_ETH, CONFIG_PPP_MULTILINK, CONFIG_PPPOE

v1.0.0

Stock ROM with ramdisk and 1.7GHz heat script (init.d added, unsecured ramdisk)
CWM flashable: motley_lite_stock_full_kernel_and_ramdisk_1.0.0_build_1.zip
(Stock and stock-based ROMs only - 32GB and 64GB primes)

Anykernel for Stock or AOKP (won't touch your ramdisk, heat, or init.d scripts)
CWM flashable: motley_lite_anykernel_stock_and_AOKP_1.0.0_build_1.zip
(32GB stock-based ROMs or AOKP primes only!)

AOKP MS 6.1 with full ramdisk and 1.7 init.d OC script
CWM flashable: motley_lite_v1.0.0b_build_1_for_AOKP_MS_6.1.zip (updated zip 7/16/2012 10:40pm - will OC to 1.7 on boot, WiFi is working for me)
(AOKP only - 32GB and 64GB primes)

Generic Anykernel for EOS, Gummy, CM9 (won't touch your ramdisk or init.d scripts)
CWM flashable: motley_lite_generic_anykernel_v1.0.0_build_2.zip
(32GB EOS, Gummy, CM9 primes only!)



Alpha 3.x kernel
A more experimental kernel, with stable versions along the way.
Release Notes - motley kernel for the Transformer Prime.pdf

Features - includes alpha
  • Asus v9.4.2.28 base with Asus keyboard dock support
  • Overclocking options: 1.6, 1.7, or 1.8GHz performance mode (choice of Asus modes)
  • Compiler optimizations (-o2)
  • I/O schedulers - CFQ (default), SIO, NOOP, and deadline
  • ZRAM (must be enabled by a script...see example below)
  • MMC drivers back-ported from Nvidia 3.1 kernel
  • Governors - optimized Interactive (default), Performance, On Demand, Power Saver
  • initramfs changes from stock - init.d support (your ROM must have the /system/etc/init.d folder and busybox) and the default.prop has been updated with ro.secure=0 (for "adb remount")
  • CIFS support (built-in, no need for kernel module)
  • NTFS/exFAT modules are provided in stock ramdisk - uses stock Tuxera modules. See http://www.tuxera.com/) - modules are loaded during init automatically with included initramfs.
  • Kernel compression mode LZMA
  • Userspace voltage control/undervolting (UV)- experimental, don't set on boot until you test your settings (use SetCPU or other voltage tweaking tool) (thanks richardtrip)
  • Input devices - PS3 (stock), XBox (CONFIG_INPUT_FF_MEMLESS and CONFIG_JOYSTICK_XPAD_FF), Other input device support (CONFIG_HID_APPLE, CONFIG_INPUT_MOUSEDEV, CONFIG_HID_LOGITECH)
  • Networking/VPN - in addition to stock: CONFIG_L2TP, CONFIG_IP_ADVANCED_ROUTER, CONFIG_NET_IPIP, CONFIG_NET_IPGRE, CONFIG_IP_MULTIPLE_TABLES, CONFIG_INET_AH, CONFIG_INET_IPCOMP, CONFIG_INET_XFRM_TUNNEL, CONFIG_INET_XFRM_MODE_TUNNEL, CONFIG_INET_XFRM_MODE_BEET, CONFIG_L2TP_DEBUGFS, CONFIG_L2TP_V3, CONFIG_L2TP_IP, CONFIG_L2TP_ETH, CONFIG_PPP_MULTILINK, CONFIG_PPPOE
  • MMC - CONFIG_ZIMMER by HTC Studio Engineering (reference OneX kernel) - Experimental - can't find the source of this hack, so it may be an HTC original or a variant of another hack upstream. It increases vm swappiness to 100 by default to force swapping of dead RAM. The theory is to clear out the stale RAM and open up the RAM for something more useful. While this may be counter-intuitive to I/O performance since swapping equates to more disk i/o, the code changes also implement some changes to the block, fs, and mm portions of the kernel. Essentially, from what I can tell, it flags and handles disk operations (aka "bios") differently if they are involved in swap operations (going to or coming from swap). A "bio" is essentially a manifest of an ongoing I/O block device operation, what sectors and memory locations it contains etc. Once the RAM is freed up, I have also been increasing the Dalvik vm RAM settings in the build.prop (see Demandarin's build.prop post) to allow for more RAM consumption.
  • Turned off GENTLE_FAIR_SLEEPERS - Theoretically should improve UI performance on Android.
  • ARM toolchain - Code Sourcery Lite 2010.09-51
  • Many other performance tweaks and many Nvidia patches/bug fixes applied beyond the stock version. See the release notes or github for details.

alpha v3.0.7.0 - fix deep sleep issue

Stock ROM with ramdisk and 1.7GHz heat script (init.d added, unsecured ramdisk)
CWM flashable: motley_stock_full_kernel_and_ramdisk_3.0.7.0_b302.zip(build 302)
(Stock and stock-based ROMs only - 32GB and 64GB primes)

AOKP build 40 with full ramdisk and 1.7 init.d OC script
CWM flashable: z_motley_tfp_v3.0.7.0_b302_for_AOKP_build_40_1.7GHz.zip(build 302)
(AOKP only - 32GB and 64GB primes)

Anykernel for Stock or AOKP (won't touch your ramdisk, heat, or init.d scripts)
CWM flashable: z_motley_anykernel_stock_and_AOKP_3.0.7.0_b302.zip (build 302)
(32GB stock-based ROMs or AOKP primes only!)

Generic Anykernel for EOS, Gummy, CM9 (won't touch your ramdisk or init.d scripts)
CWM flashable: motley_tfp_anykernel_generic_3.0.7.0_b303.zip (build 303)
(32GB EOS, Gummy, CM9 primes only!)


alpha v3.0.6.10 - fixed wifi issues in 3.0.6.9

Stock ROM with ramdisk and 1.7GHz heat script (init.d added, unsecured ramdisk)
CWM flashable: motley_stock_full_kernel_and_ramdisk_3.0.6.10.zip (build 247)
(Stock and stock-based ROMs only - 32GB and 64GB primes)

AOKP build 40 with full ramdisk and 1.7 init.d OC script
CWM flashable: z_motley_tfp_v3.0.6.10_for_AOKP_build_40_1.7GHz.zip (build 247)
(AOKP only - 32GB and 64GB primes)

Anykernel for Stock or AOKP (won't touch your ramdisk, heat, or init.d scripts)
CWM flashable:z_motley_anykernel_stock_and_AOKP_3.0.6.10.zip (build 247)
(32GB stock-based ROMs or AOKP primes only!)

Generic Anykernel for EOS, Gummy, CM9 (won't touch your ramdisk or init.d scripts)
CWM flashable: motley_tfp_anykernel_generic_3.0.6.10.zip (build 250)
(32GB EOS, Gummy, CM9 primes only!)

Older alpha 3.0.x versions can be found in post 803
Many are stable on v3.0.5 if the above versions don't work for you.


v2.6.11 build 100 2012-04-22

Asus stock-based ROMs (aroma installer): motley_tfp_2.6.11_Turge_installer.zip
Flash with CWM to run the installer and pick your heat!

Other ROMs: see alpha version 3.0.x above as previous generic kernels discontinued due to wifi incompatibility other than AOKP.

Installation

1. Backup stock boot.img (just do a full backup with the latest CWM)
See http://forum.xda-developers.com/show....php?t=1533697

2. Flash the proper zip with CWM


--------------------------------------------------------------------------------------------------------------------------------------
If you want to set your modes and play with the scripts manually as before see this post:
http://forum.xda-developers.com/show...&postcount=278)
Don't set your core_cap_level higher than 1400mV as it is the highest core voltage available.
system_mode numbers (3=1.6GHz, 4=1.7GHz, 5=1.8GHz)

--------------------------------------------------------------------------------------------------------------------------------------

Going back to stock:
If you want to revert to stock boot image including stock kernel from your backup
Use your CWM backup. You can do a selective restore and just restore your boot.img

If you want to revert back to your Asus scaling scripts
Flash the stock scaling script: Stock_scripts_1_to_5.zip
--------------------------------------------------------------------------------------------------------------------------------------

Github rep: https://github.com/motley-git/TF201-Kernel

--------------------------------------------------------------------------------------------------------------------------------------
Past versions

v2.5.8 build 71 (GPU Love) 2012-04-14
CWM flashable zip: v2.5.8
Aroma installer with heat scripts: motley_tfp_2.5.8_Turge_installer.zip

v2.4 build 34 (Neon glitter) 2012-04-06
CWM flashable zip: Attachment 986645

v2.3 build 25 (Need for speed)
CWM flashable zip: Attachment 978413

v2.2 build 23 (No fools, more Asus Tweaks)
CWM flashable zip: Attachment 976821

Thanks to:
  • Asus for the awesome machine and kernel source
  • viperboy, jermaine151, MasterZen88, di11igaf, Diamondback and shaky156 for sharing their knowledge and tools
  • raman84 (RaYmAn) and others for the blob tools that work on transformer
  • Turge - awesome Aroma installer base creation for us!
  • amarullz - Aroma Installer
  • Doktaphex - touch recovery thread used by Turge for the touchscreen components.
  • AnyKernel - Koush and TeamDRH (and Jermaine for bringing it to the Prime)
  • All of those that have helped with testing! Special thanks to CekMTL for his troubleshooting skills and Deathmo for really going above and beyond to help out.

Sample overclock init.d script example (needed for AOKP or generic roms). AOKP uses /system/etc/init.d/cpu_overclock, so I recommend you edit that file for AOKP since it is already working.

Code:
#!/system/bin/sh 
echo 4 > /sys/module/cpu_tegra/parameters/system_mode
echo 1350 > /sys/kernel/tegra_cap/core_cap_level
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/platform/tegra_grhost/enable_3d_scaling
echo 10 > /sys/module/cpu_tegra3/parameters/mp_overhead
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
setprop power.saving.mode 1
setprop persist.tegra.NV_FPSLIMIT 0
setprop persist.sys.NV_FPSLIMIT 0
setprop persist.sys.NV_POWERMODE 0

echo 1700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo N > /sys/module/cpu_tegra3/parameters/no_lp
Sample ZRAM init script (thanks show-p1984) (needs to be run as "su" using script manager):

Code:
#!/system/bin/sh
# auto zram activation init script with busybox search
# by show-p1984

echo "[90ZRAM]: Firing up /system/etc/init.d/90zram";

if [ ! -e /sys/block/zram0/disksize ] ; then
        echo "[90ZRAM]: ERROR unable to find /sys/block/zram0/disksize";
        echo "[90ZRAM]: Is this a ZRAM kernel?";
        echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
else
        #find busybox in /system
        bblocation=$(find /system/ -name 'busybox')
        if [ -n "$bblocation" ] && [ -e "$bblocation" ] ; then
                echo "[90ZRAM]: busybox found in:" $bblocation;
                echo "[90ZRAM]: Setting ZRAM disksize.";
                echo $((100*1024*1024)) > /sys/block/zram0/disksize

                echo "[90ZRAM]: Starting ZRAM...";
                bblocation=${bblocation%/*}
                cd $bblocation
                ./busybox mkswap /dev/block/zram0
                ./busybox swapon /dev/block/zram0

                echo "[90ZRAM]: ZRAM activated.";
        else
                echo "[90ZRAM]: ERROR! busybox not found!";
                echo "[90ZRAM]: Is busybox installed? Symlinks set?";
                echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
        fi
fi
Last edited by _motley; 11th March 2013 at 02:04 AM.
The Following 106 Users Say Thank You to _motley For This Useful Post: [ View ]
6th March 2012, 05:54 AM   |  #2  
di11igaf's Avatar
Recognized Developer
Flag East Coast
Thanks Meter: 666
 
1,760 posts
Join Date:Joined: Sep 2010
Donate to Me
More
nice work man, i was getting ready to implement this myself. they made that pretty easy right.. at first i thought it was gonna be a pita until i looked a little deeper and saw most of what we need is already there.
6th March 2012, 06:10 AM   |  #3  
_motley's Avatar
OP Senior Member
Thanks Meter: 2,407
 
858 posts
Join Date:Joined: Aug 2010
Donate to Me
Quote:
Originally Posted by di11igaf

nice work man, i was getting ready to implement this myself. they made that pretty easy right.. at first i thought it was gonna be a pita until i looked a little deeper and saw most of what we need is already there.

Thanks, yeah not too bad. There is a lot more "nanny" code in tegra 3 than in tegra 2. Tempted to tweak some of it, but decided it was best to take baby steps! Kind of hoping we can get a community version going once some of us do some study and get our feet wet.

Cheers
The Following User Says Thank You to _motley For This Useful Post: [ View ]
6th March 2012, 06:37 AM   |  #4  
demandarin's Avatar
Recognized Contributor
Flag Alexandria, Va
Thanks Meter: 2,045
 
6,979 posts
Join Date:Joined: Apr 2010
More
is it possible to convert this into an apk form like EZOverclock? where there is no need for unlocking and CWM. all needed is rooted device and installing the app. just curious

great work though. plus u mentioning 1.8Ghz might be the final straw needed to push me over the edge to unlock..lol cant wait to see it implemented. I'm holding back so badly with all this new developement coming out for prime. its really starting to blow up in here and temptation to unlock is eating me up
6th March 2012, 06:41 AM   |  #5  
Senior Member
Thanks Meter: 14
 
324 posts
Join Date:Joined: Nov 2008
So like a retard I flashed boot.img.zip instead of extracting the boot.img out first

-_-

It is entirely my fault but any help would be appreciated

My TP hangs at he Eee Pad logo
Any hopes of holding vol down + power button sends me straight to wipe data or fastboot menu (I CANT ACCESS THE RECOVERY TRIED 99999 TIMES TO DO IT WITH VOL DOWN + POWER)
Tried doing the following:

fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 flash boot boot.img (original stock boot.img found here http://forum.xda-developers.com/show....php?t=1514088

Still it hangs at Eee Pad logo if I don't do anything. If I tried the Volume down + power goes straight back to wipe data or fastboot.

ANY thoughts?

tHANKS
6th March 2012, 10:16 AM   |  #6  
MasterZen88's Avatar
Senior Member
Thanks Meter: 804
 
462 posts
Join Date:Joined: Feb 2012
Donate to Me
Quote:
Originally Posted by tassadar898

So like a retard I flashed boot.img.zip instead of extracting the boot.img out first

-_-

It is entirely my fault but any help would be appreciated

My TP hangs at he Eee Pad logo
Any hopes of holding vol down + power button sends me straight to wipe data or fastboot menu (I CANT ACCESS THE RECOVERY TRIED 99999 TIMES TO DO IT WITH VOL DOWN + POWER)
Tried doing the following:

fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 flash boot boot.img (original stock boot.img found here http://forum.xda-developers.com/show....php?t=1514088

Still it hangs at Eee Pad logo if I don't do anything. If I tried the Volume down + power goes straight back to wipe data or fastboot.

ANY thoughts?

tHANKS


Try using the following commands in APX mode. To access APX mode:
1. Undock transformer prime
2. Hold power+ up key.
3. Install naked drivers (http://forum.xda-developers.com/show....php?t=1514942)
4. Screen will be black but once connected to a pc you should see it in device manager.
The Following User Says Thank You to MasterZen88 For This Useful Post: [ View ]
6th March 2012, 11:00 AM   |  #7  
benefit14snake's Avatar
Senior Member
Flag Henrico, VA
Thanks Meter: 177
 
812 posts
Join Date:Joined: Dec 2011
More
Nice stuff! Flashed and all is well but 1.7ghz plus antutu. Equals sad prime. 2 reboots and one crash to homescreen (it didn't force close though)

Balanced works fine.
Edit: anything that is cpu intensive makes my prime sad reboot time lol. Meh I probably need more volts.

Sent from my Transformer Prime TF201 using Tapatalk
Last edited by benefit14snake; 6th March 2012 at 11:06 AM.
6th March 2012, 12:08 PM   |  #8  
jermaine151's Avatar
Senior Member
Flag Columbus, Ohio
Thanks Meter: 3,306
 
3,981 posts
Join Date:Joined: Jun 2010
Donate to Me
More
Good job motley!!
6th March 2012, 01:55 PM   |  #9  
Diamondback's Avatar
Developer Committee / Senior Moderator / Recognized Developer
Thanks Meter: 6,355
 
4,390 posts
Join Date:Joined: Jan 2010
More
Quote:
Originally Posted by tassadar898

So like a retard I flashed boot.img.zip instead of extracting the boot.img out first

-_-

It is entirely my fault but any help would be appreciated

My TP hangs at he Eee Pad logo
Any hopes of holding vol down + power button sends me straight to wipe data or fastboot menu (I CANT ACCESS THE RECOVERY TRIED 99999 TIMES TO DO IT WITH VOL DOWN + POWER)
Tried doing the following:

fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 flash boot boot.img (original stock boot.img found here http://forum.xda-developers.com/show....php?t=1514088

Still it hangs at Eee Pad logo if I don't do anything. If I tried the Volume down + power goes straight back to wipe data or fastboot.

ANY thoughts?

tHANKS

You need to repack the correct boot.img as a blob file. Fastboot doesnot work the way you use it.
Fastboot can't flash raw imgs, you need to repack them before as a blob file.

Search goolge for blobtools, there is a thread on xda with both linux and a windows version.
6th March 2012, 01:59 PM   |  #10  
Diamondback's Avatar
Developer Committee / Senior Moderator / Recognized Developer
Thanks Meter: 6,355
 
4,390 posts
Join Date:Joined: Jan 2010
More
And now @OP
I guess the kernel itself is based on the outdated ASUS source?

And for the next build, maybe make a verion where you overclock the 1.6GHz mode instead of the Performance mode?
Most (if not all) who would use such a kernel, use some kind of tool/app/rom which can access the 1.6 Ghz mode anyway, so you are better of tweaking the 1.6Ghz mode

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools
Display Modes