Database Info

[TOOL] Kernel Update Utility 0.9 - Flash kernels easily!

Kernel Update Utility 0.9​YouTube video​"Making kernel flashing a bit easier"​
About:
This lightweight tool takes a kernel, and flashes it to your device. You can give it the kernel in zImage or CWM flashable zip format. Some people have come across bootloops when using clockworkmod to flash kernels, hopefully this tool will prove to fit better for the job. It can also push and apply kernel modules. I have now flashed a kernel using this tool more times than I can count, and not a single bootloop or failed flash.
This tool is ideal for people who do not want to mess with command lines, and people who want the job done fast and easy.
System requirements:
Windows XP SP2 or higher
.NET 4.0
HTC Sync (or ADB drivers)
Rooted, ENG S-OFF Desire HD
Changelog:
0.9:
- Added support for Lee's kernels
0.8:
- Added support for Kamma's new kernels
0.7:
- Fixed Windows XP file not found -bug
- Optimized the code further
0.6:
- Most cmd windows hidden
- Better instructions in module pushing
- Out of beta!
0.5a:
- Optimized a lot of code
- Improved SU permissions; fixed modules not getting pushed with phones that do not have root adb by default
- Cleans up /system/lib/modules to ensure cp functionality
0.4:
- It is now possible to choose multiple modules
- It cleans up afterwards
0.3:
- CWM zip file flashing, pushes all modules
- Space in filename -bug fixed
0.2:
- Initial release
Click to expand...
Click to collapse
If you like my work, please consider (or just hit the thanks button ):

Hi,
thanks !!
Please add more selections for ko files:
- tun.ko
- cifs.ko
- other
with friendly greet
starbase64

Yeah, I will
I will also make this work with CWM flashable zips, I am programming that in right now.

Hi,
good news, thanks.
with friendly greet
starbase64

It can now flash zip files that would usually be flashed in clockworkmod. Using my app to flash it should reduce the possibility of a bootloop. Also the space in filename -bug has been fixed.
e: Another update, now for selecting and applying kernel modules. Please leave feedback! Is there something I should change? Any features you would like to see in this tool?
Keep in mind that this tool can also be used for recovering from some bootloops, where kernel itself is not properly flashed. In some situations, however, boot.img corrupts in CWM flash, then you will have to restore a partial nandroid.

thanks.. now i wish there is a tool for pushing ENG hboot and CWM recovery .. where is unrevoked

Well, I can enable my tool to flash a recovery, but because flashing hboot is so risky, I think I will not do that feature..
So, are people interested in a recovery flasher?

So now I can flash the .zip files that before I was flashing with the recovery with this application?

Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.

jkoljo said:
Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.
Click to expand...
Click to collapse
Wow it's amazing guy!!! i have tried now, with, before my htc desire hd was going in eternal bootloop with origianl rom and 1,2 kernel now it's ok really tank you!!!

No problem, glad it helped!

Hi,
support for german users here > www.handy-faq.de
with friendly greet
starbase64

Noob question but how can you revert back to original kernal?
Not tried this yet But this is What I been waiting for. How long does the process take?
Thanks
Sent from my Desire HD using XDA App

Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?

Deicist said:
Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?
Click to expand...
Click to collapse
Same issue here, does not push the wifi module

Strange, it does push it for me. I'll investigate. It may have something to do with root rights, does bcm4329.ko appear to your sdcard?

Nope, doesn't appear in sdcard.
For further info I tried it with 0.3 as well, same result.
Also, none of the modules get pushed, it's not just the wifi one.

My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!

jkoljo said:
My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!
Click to expand...
Click to collapse
Nope, will not push wifi module, all phone settings are as per instructions

Which rom are you on? Do you have HTC Sync 3.0 on your computer?
Try pushing modules manually as per Apache14's thread first post, if it works then the problem is propably in my tool, if it does not work, the problems is at your end.

[JIT Updated 31/12/10] Frozen Eclair- For 2.21 & AND NOW 2.34.1 Firmwares

Firstly I am posting this with permission of [email protected] Modaco. All props go to him for the origina JIT files - buy him a beer or summat.
Original Thread (Modaco)
For all those asking what JIT is this is a good explanation:
What is JIT for Android
Please don't flood the thread asking what JIT is - Google is your friend.
Disclaimer: I will not be held responsible for any damage to your phone, your PC or indeed your life from following this guide. The steps in this guide worked for me. Doing this kind of thing could affect your warranty and all that so have a long hard think about it before you go ahead. If anything goes wrong and you get into a bootloop or something then use my debricking guide posted in this forum. Make a backup first by Tenfars Clockwork Mod for Defy
After I attempted JIT in a half arsed way previously and not getting good results (force closes etc). Antibyte has done it the right way and compile his "Frozen Eclair" JIT package.
NB: if you have removed apps this will add them back in as it is based on all the apps from the stock rom.
Ok So this is super easy now - one update.zip applied via Tenfars Clockworkmod Recovery Get it Here! - so no excuses not to give it a try! You won't be sorry.
As always start by making a backup via Clockwork Recovery.
There are now 2 packages - Choose the one for the the appropriate stock ROM you use (2.21 or 2.34.1), make sure you choose the right one for godsake or bad things will most probably happen!
Download FrozenEclairDefy_V2.zip Here for 2.21 Stock ROMs
Download FrozenEclair_V2.34.1.zip Here from 2.34.1 No Blur Stock ROMs
Instructions:
Place the FrozenEclair.....zip on the root of your sdcard
Boot into recovery
Select "Install zip from SDCARD"
Select "Choose zip from sdcard"
Select FrozenEclairDefy......zip from the list
Select "YES - Install - FrozenEclair......zip
The above will then install and then you just need to reboot. 1st boot will take longer than usual while it rebuilds the dalvik cache.
For some reason this removes root, so just reroot by Z4Root or your preferred method once the phone has rebooted. This will also mean you will have to reapply your overclock if you use milestone overclock (well it did for me anyways!)
##If you get any untoward things happening like force closes/apps not working my advice is to 1) reflash the .sbf (you follow my guide for this) and if that doesn't work 2)do a full wipe of all data. This is hacking and stuff like that happens all the time so be prepared##
MY Advice if you want to change to 2.34.1 ROM from 2.21. Follow this process:
Back up all user apps/their data by titanium backup.
Boot into recovery and make a backup of your 2.21 ROM.
Then wipe data/cache in the recovery options.
Using the debranding guide, flash the 2.34.1 firmware.
After 1st boot it will be as if you have a new phone.
Install z4root - root the badboy.
Then after reboot install Tenfars ClockworkMod - apply the mod and boot into it
Flash the deodex/JIT package.
After 1st reboot, reroot with Z4root.
Reinstall titanium back up from the market and reinstall you user apps/data.
Reset up your system settings.
Once you've got it back how you like it, boot back into recovery and back up the new rom.
So to reitterate thanks for this go to:
Antibyte @ Modaco for the JIT Files and full Update.zip 2.21 ROM
Paul @ Modaco for the deodexed/optimised app/framework for the 2.21 ROM
Me for the XDA guide and the original Update.zip for V1 and the deodexed app/framework for 2.34.1 ROM, and the JIT update.zip
Sorensiim for the generous hosting of all my files, meaning direct downloads and no shady file sharing sites - good lad!
Changelog:
19/12/10:
Frozen Eclair V1 - JIT For Defy
Tut on deodexing rom
Update.zip for installing JIT
20/12/10:
Frozen Eclair V2 - JIT For Defy
Recompiled and more optimisations
Whole process automated in 1 easy update.zip that includes deodexing and installing JIT.
Tut/OP updated to reflect the above changes
31/12/10:
Frozen Eclair V2.34.1 for 2.34.1 No Blur Stock ROM released

Wow! A preemptive thanks from me to you and the guys at Modaco!
Sent from my MB525 using XDA App

Hey
stupid question maybe, but what is JIT good for?

so what is JIT exactly? ( all i know so far is that it makes your quadrant scores higher so i assume it makes your phone faster in general or onlky in games?) and have you had any problems yet?

Great ! But what's MCR optimised ?

kendael said:
Great ! But what's MCR optimised ?
Click to expand...
Click to collapse
Paul runs the apks through his optimisation process, I don't know exactly what it does, but i trust Paul -but if you don't then just use the standard deodexed apps

For those that don't know I have added a link to the OP which gives a pretty decent explanation for what JIT for android is, or you could google "what is android jit" and you''ll find plenty of info lets use this thread to discuss this mod and any bugs etc.

I just read the introduction of Dalvik JIT. This is really amazing. I will try it later, since it will affect the warranty anyway.

Everythings works well. Quadrant with 900 mhz before JIT= 1175. Quadrant with 900 mhz with JIT installed = 1280. Thanks Paul! Good work. Keep it up.

Wow this sounds great! Thanks.

Can anyone tell me why i get an Unrecognized option '-h' for dalvikvm -h? I wanted to test if JIT is realy enabled.

# dalvikvm -h
dalvikvm -h
Unrecognized option '-h'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all}
-Xnoquithandler
-Xjnigreflimit:N (must be multiple of 100, >= 200)
-Xjniopts:{warnonly,forcecopy}
-Xdeadlockpredict:{off,warn,err,abort}
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgenregmap
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
Configured with: debugger profiler jit show_exception=1
Dalvik VM init failed (check log file)
-----------------------------------------------------------------
This is the output from that on mine it doesnt mean anything however
Key line is this:
Configured with: debugger profiler jit show_exception=1
however if you do a logcat you will see the following from time to time proving jit is enabled:
12-19 14:53:55.641 1678 1681 I dalvikvm: Jit: resizing JitTable from 4096 to 8192

You are right. I have checked it with logcat.

Thanks Higgsy and everyone else involved. The first few runs on quadrant got about the same scores as before, but it just now returned a 1223.

Zaben said:
Thanks Higgsy and everyone else involved. The first few runs on quadrant got about the same scores as before, but it just now returned a 1223.
Click to expand...
Click to collapse
whats your linpack - are you overclocked?

Higgsy said:
whats your linpack - are you overclocked?
Click to expand...
Click to collapse
Stock 800 Mhz, I haven't messed with that stuff yet. The best I could get out of Linpack is 11.934. Neither Linpack or Quadrant are consistent. Quadrant scores vary from 937 to 1223. I haven't been able to reproduce the 1223 score.
I'm reverting here in a sec. The accounts problem has it where I can't get contacts to open. I may try again next weekend from a fresh reset.

Applied it fine and is working OK so far. Thanks! Quadrant on stock is 1241 now.
Loving the recovery applied zip. I would like to create one for the deodexed/optimised files as well - is there a FAQ about creating these?

A++ on this, defy is a really nice phone, thanks to dev efforts

Version 2 and fully automated update.zip process updated in the OP

whenever i enter recovery, it says "Can't open /cache/recovery/command" and there is no "install ZIP from SD CARD" option only reboot system now, apply sdcard:update.zip, wipe data/factory reset, and wipe cache partition. help

[ROOT] unrevoked3 v3.31 (with support for new HBOOT, now with amend scripting!)

Hi!
On behalf of the unrevoked team, we're proud to announce the new release of unrevoked -- version 3.3. This version adds support for HBOOT 2.02 and 2.10, and also adds support for the new OTA, 3.70.651.1.
You can get it at our site, http://www.unrevoked.com/recovery/ .
New in this release is ClockworkMod 3.0.0.2. We and Koush have been working hard on getting ClockworkMod all set and safe on EVO 4G; ClockworkMod is now using the latest EVO 4G kernel, for one, and now has nandroid options to back up your WiMAX keys. It also encodes your phone's serial number in the WiMAX backup, which greatly reduces the risk of restoring the wrong WiMAX image to the wrong phone. Please try it out!
We'll be watching this thread off and on. There are a few known glitches; carefully read the frequently asked questions in the "More Info" section, linked from the page above.
Thanks for everyone's support and assistance -- and have a happy new year!
joshua
unrevoked
UPDATE:
I just pushed out 3.31, which fixes a bunch of small issues that people were having, and backs down to Clockwork 2.6.0.1. This adds support for Amend scripting back in, but keeps all the good changes from 3.0.0.2 -- WiMAX backup, and the new kernel with support for new hboot partitions. I tested this pretty thoroughly -- I fully erased my WiMAX partition with erase_image wimax (don't try this at home!), and then restored it from a backup I took with Clockwork 2.6.0.1. My keys were intact, and my 4G still works. More detail about the changes can be found in the changelog. Thanks!

You guys are the best!!!!!!!!

so im guessing you fixed the recovery. because in my testing with the new version of cw...on older hardware with the new hboot it wouldnt back up squat...and there have been reports of people noting being able to flash things with the new version on new hardware or not being able to boot.
thanks for the hardwork

Sweet! will be trying this on my new EVO tonight... will update how it goes.
Thanks guys for the hard work!

This is great news.
I'm going to hold off on doing anything for now until the flashing issues are completely figured out and there is a solid 3.2 build out.
Thanks for all of your hard work guys.

Is the new version setup to install the old 2.5 version of Clockwork if you use it against an older partition structure? Word is that Clockwork 3.0.0.2 is not backwards compatible with the old partition structure.

bkrodgers said:
Is the new version setup to install the old 2.5 version of Clockwork if you use it against an older partition structure? Word is that Clockwork 3.0.0.2 is not backwards compatible with the old partition structure.
Click to expand...
Click to collapse
didnt work in my testing...but i am just one person. all though i got the same results across 3 evo's two old 0003 and one newer 0003 (with the new camera)

Soooooo stoked for this!!!

VERY NICE!!!!

Quick question, I don't have 4g in my area yet so I haven't gotten 4g connected yet. So should I flash the new wimax radio and start my new restorations from there or just leave it as is and keep my old backups along with whichever new ones I create?
Sent from my PC36100 using XDA App

did this and it worked use it guys make sure you follow everything. Unrevoked team cwr gave me some problems while rebooting it gave me lines on my screen it looks scary but it works so i just switch to amon recovery anyways thanks

First post so please be kind!!!
Downloaded 3.3 but the reflash.app won't open on my Mac. I get the "The application Reflash quit unexpectedly". I had done it before on 3.2 and no issues using the same cpu. Please help.

revel1973 said:
First post so please be kind!!!
Downloaded 3.3 but the reflash.app won't open on my Mac. I get the "The application Reflash quit unexpectedly". I had done it before on 3.2 and no issues using the same cpu. Please help.
Click to expand...
Click to collapse
sno leopard only. sorry...

running on Ubuntu, ran it in terminal as "sudo ./reflash" as to give it root permssions and it pushed the recovery in no time but has been stuck on "installing unrevoked3 service" for about 10 minutes now....afraid to unplug/close it. any help/clues?

no workie on mac
does not work on mac.. help please
Process: Reflash [1592]
Path: /Volumes/unrevoked Recovery Reflash Tool/Reflash.app/Contents/MacOS/Reflash
Identifier: com.unrevoked.reflash
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1478]
Interval Since Last Report: 67764 sec
Crashes Since Last Report: 14
Per-App Interval Since Last Report: 0 sec
Per-App Crashes Since Last Report: 13
Date/Time: 2010-12-31 18:17:57.903 -0800
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: A75357B4-8467-4198-A16A-F271443B65A6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
unknown required load command 0x80000022

just did my wife phone on a mac with snow leopard and it worked just fine. the trick was that i had debugging already enabled when i loaded unrevoked so i disabled it then enabled it while still on unrevoked and it worked.

jorge.l.diaz said:
does not work on mac.. help please
Process: Reflash [1592]
Path: /Volumes/unrevoked Recovery Reflash Tool/Reflash.app/Contents/MacOS/Reflash
Identifier: com.unrevoked.reflash
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1478]
Interval Since Last Report: 67764 sec
Crashes Since Last Report: 14
Per-App Interval Since Last Report: 0 sec
Per-App Crashes Since Last Report: 13
Date/Time: 2010-12-31 18:17:57.903 -0800
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: A75357B4-8467-4198-A16A-F271443B65A6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
unknown required load command 0x80000022
Click to expand...
Click to collapse
same error i got on leopard. you need snow leopard.

How would I go about upgrading my hboot so that I can use the new cmw, and root with this method.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!

I Can Backup My Original Evo Rom But I Can't Flash Any. I Get The Lines Too. Should I Just Flash An Older Clockworkmod Or Just Go To Amon's ?
&& I'm On A Old Recovery ( 2.5.0.1 ) . It Looks Like 3.0.0.2 Doesn't Work . Or Am I Wrong ?
I'm A Rookie . -_-
Btw , I'm Trying To Flash Salvage-Mod .9.3 Gingerbread .

I cannot flash a new rom either, it cannot access my SD card.......?

[DEV][WIP] Jelly Bean / CM10.1 (4.2.2) Beta 1 - 3.1 kernel - Last Update 07.01.2014

Android 4.2.2 / Jelly Bean for Toshiba Folio 100
This is the current state of CyanogenMod 10.1 for the Toshiba Folio 100
It is an update from DerArtem's version. I call it Beta 1 (not because it is béta software, but I wanted to restart renumbering instead of calling it Alpha 3)
Added
- Overclock up to 1.6Ghz (tough 1.6 does not increase performance in bechmarks on top of 1.4Ghz) -> Max score in antutu between 11500 and 12500. Be careful, not all units can go up to 1.6Ghz.
- Reclaimed 15Mb from the HDMI buffer (a little bit more memory)
- Latest CM10.1
- some clock fixes (20121215) + SOD workaround for 1.6Ghz (20121220)
- enabled low mem patch in cm10.1 patch (20121220)
- deadline I/O scheduler (not by default, but can be enabled in developer mode) (20140107)
- some exernel libs were not compiled in (could fix huwei usb stick) (20140107)
What does not work
- Everything that didn't work in Derartem's Alpha 2
- HDMI (though this also didn't work on my Folio in Derartem's Alpha 2)
Also see Alpha 2 notes:
CM10.1 Alpha2
Installation:
Install the correct recovery using fastboot (3Xpower & Vol+, fastboot erase recovery, fastboot flash recovery recovery.img)
Copy everything on an SD card and install the ROM using the recovery (Power&Vol+, Vol+, Vol-, Vol+).
Important for everyone having the 4Gb /data partition:
You must do a full wipe and format "/data and /data/media (/sdcard)" before installing the ROM using CWM recovery. /data partition will then be 12Gb.
Notes (for anyone who want to try):
- Recovery didn't change, so you can probably use the Derartem's recovery
- You can try upgrade the ROM without wipe if your previous ROM was Derartems CM10.1 alpha 2 (just install it in recovery)
Download
Recovery
CM 10.1 installation file (zip) 20131215
CM 10.1 installation file (zip) 20131220
CM 10.1 installation file (zip) 20140107
Gapps:
Gapps non-neon
Source code
Kernel source
Credits:
DerArtem
Nopy
m32
guevor
The Cyanogenmod Team
The other Tegra Dev Teams where we have borrowed code (Adam, GTab, Vega, AC100, Acer Iconia, Xoom)

Have a problem.. 1'4 and perfomance does stop my folio.. and the tabletui zip wont install on this beta, trying to install the oc kernels but only get text!.. could you help me... i was waiting so long for a OC!. Thx!!

uc370 said:
Have a problem.. 1'4 and perfomance does stop my folio.. and the tabletui zip wont install on this beta, trying to install the oc kernels but only get text!.. could you help me... i was waiting so long for a OC!. Thx!!
Click to expand...
Click to collapse
Can you tell me what you are trying to do?
The zip installer already has the newest kernel in there (max 1.6, but with lp0 sleep), so no need to install the kernels.
Does it stop immediately after selecting 1.4 ghz, or a bit after?
The performance governor keeps speed at max all the time. This will get the cpu overheated after some time. I would suggest the combination of 1.4 and interactive (= only run at 1400 up when needed)
Also a good tip: try lagFix (fstrim) from the play store. It runs fstrim on the ssd.
I'll check the links of the kernels

spicyalan said:
Can you tell me what you are trying to do?
The zip installer already has the newest kernel in there (max 1.6, but with lp0 sleep), so no need to install the kernels.
Does it stop immediately after selecting 1.4 ghz, or a bit after?
The performance governor keeps speed at max all the time. This will get the cpu overheated after some time. I would suggest the combination of 1.4 and interactive (= only run at 1400 up when needed)
Also a good tip: try lagFix (fstrim) from the play store. It runs fstrim on the ssd.
I'll check the links of the kernels
Click to expand...
Click to collapse
google in its repositories for tegra kernel has the same problem, currently they work on LP2 - so we are not alone.
Hav You access to other device with tegra 2 chip ? I have xoom 2, but it isnt mine - from my custommer, so bricking it is a bad idea

m32 said:
google in its repositories for tegra kernel has the same problem, currently they work on LP2 - so we are not alone.
Hav You access to other device with tegra 2 chip ? I have xoom 2, but it isnt mine - from my custommer, so bricking it is a bad idea
Click to expand...
Click to collapse
As far as I know, there is almost no tegra 2 device completely without sod (see forums, even the galaxy R has problems). Some version are better than others, and some stock roms are good in hiding it.
I have access to a sony tablet with a tegra 2. But it is not a developer friendly device.
It has quite a big batterry, and judging from how it sleeps: it does not go into sleep mode and keeps wifi on (loosing 30% battery in 8 hours of sleep). Compared to the battery size of the folio (which drains 80% in 8 hours with wifi lock, but has a smaller and worn battery), it means the sony tablet does not sleep at all and just disables the screen.

spicyalan said:
Can you tell me what you are trying to do?
The zip installer already has the newest kernel in there (max 1.6, but with lp0 sleep), so no need to install the kernels.
Does it stop immediately after selecting 1.4 ghz, or a bit after?
The performance governor keeps speed at max all the time. This will get the cpu overheated after some time. I would suggest the combination of 1.4 and interactive (= only run at 1400 up when needed)
Also a good tip: try lagFix (fstrim) from the play store. It runs fstrim on the ssd.
I'll check the links of the kernels
Click to expand...
Click to collapse
Im trying all combinations.. A2 with kernels and B1 alone.. Finally links ok.
B1 witn 1,4 freezes after 10-20 seconds of use at 1400.. Interactive works better than ondemand..
Does anyone hace problems With google play?.. it gives error upgrading or downloading

uc370 said:
Im trying all combinations.. A2 with kernels and B1 alone.. Finally links ok.
B1 witn 1,4 freezes after 10-20 seconds of use at 1400.. Interactive works better than ondemand..
Does anyone hace problems With google play?.. it gives error upgrading or downloading
Click to expand...
Click to collapse
Not all Tegra2's are created equal, so some might respond better or worse on overclocks.
V1 has quite some agressive overvolting, so doesn't overclock well. All after (including the kernel in B1) have lower voltages.
There is now a V4 kernel with work towards the SOD issue and some small adjustments in the overclocking at 1.4 and 1.6 Ghz.
I don't have an issue with google play. Did you install the non-neon google apps (linked on both A2 an B1)?

So good!... no freezes.. overclocked to 1400. Smooth and fast!!
Thx!!!! New tablet again? With B2

uc370 said:
So good!... no freezes.. overclocked to 1400. Smooth and fast!!
Thx!!!! New tablet again? With B2
Click to expand...
Click to collapse
Cool - same result 1400 without freeze at boot and while working, previous rom just stopt at cm-boot icon, next one at 1.4 just makes some artefacts - but this one just works.
Big thanks
---------- Post added at 10:49 PM ---------- Previous post was at 10:42 PM ----------
spicyalan said:
As far as I know, there is almost no tegra 2 device completely without sod (see forums, even the galaxy R has problems). Some version are better than others, and some stock roms are good in hiding it.
I have access to a sony tablet with a tegra 2. But it is not a developer friendly device.
It has quite a big batterry, and judging from how it sleeps: it does not go into sleep mode and keeps wifi on (loosing 30% battery in 8 hours of sleep). Compared to the battery size of the folio (which drains 80% in 8 hours with wifi lock, but has a smaller and worn battery), it means the sony tablet does not sleep at all and just disables the screen.
Click to expand...
Click to collapse
soo bad soo good - this time we are very happy which one documentation and where did You found ? I'm very interested Yours patches give my folio second life -
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
spicyalan said:
Android 4.2.2 / Jelly Bean for Toshiba Folio 100
This is the current state of CyanogenMod 10.1 for the Toshiba Folio 100
It is an update from DerArtem's version. I call it Beta 1 (not because it is béta software, but I wanted to restart renumbering instead of calling it Alpha 3)
Added
- Overclock up to 1.6Ghz (tough 1.6 does not increase performance in bechmarks on top of 1.4Ghz) -> Max score in antutu between 11500 and 12500
- Reclaimed 15Mb from the HDMI buffer (a little bit more memory)
- Latest CM10.1
- some clock fixes (20121215)
What does not work
- Everything that didn't work in Derartem's Alpha 2
- HDMI (tough this also didn't work on my Folio in Derartem's Alpha 2)
Also see Alpha 2 notes:
CM10.1 Alpha2
Installation:
Install the correct recovery using fastboot (3Xpower & Vol+, fastboot erase recovery, fastboot flash recovery recovery.img)
Copy everything on an SD card and install the ROM using the recovery (Power&Vol+, Vol+, Vol-, Vol+).
Important for everyone having the 4Gb /data partition:
You must do a full wipe and format "/data and /data/media (/sdcard)" before installing the ROM using CWM recovery. /data partition will then be 12Gb.
Notes (for anyone who want to try):
- Recovery didn't change, so you can probably use the Derartem's recovery
- You can try upgrade the ROM without wipe if your previous ROM was Derartems CM10.1 alpha 2 (just install it in recovery)
Download
Recovery
CM 10.1 installation file (zip)
CM 10.1 installation file (zip) with newer kernel
Gapps:
Gapps non-neon
Source code
Kernel source
Credits:
DerArtem
Nopy
m32
guevor
The Cyanogenmod Team
The other Tegra Dev Teams where we have borrowed code (Adam, GTab, Vega, AC100, Acer Iconia, Xoom)
Click to expand...
Click to collapse
1.6 the problem was sleep mode at minimal speed - now I'm waiting for sleep mode - SOD
after few minutes of sleep(power down from start menu) only reset helps

soo bad soo good - this time we are very happy which one documentation and where did You found ? I'm very interested Yours patches give my folio second life -
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
1.6 the problem was sleep mode at minimal speed - now I'm waiting for sleep mode - SOD
after few minutes of sleep(power down from start menu) only reset helps
Click to expand...
Click to collapse
I have used this post and did the changes on top of the latest DerArtem release (source is available). For the missing information (e.g. voltage table and correct values) I looked at the Xoom and Acer sources (though these had to be adjusted later on, but they were better starting points than taking random values)
1.6ghz works fine on my unit (even in heavy 3D gaming), except for the resume SOD at this speed.
I'm currently testing a workaround (nothing fancy. Just limiting to 1Ghz when screen goes off, and restore original max after screen is turned on). It seems to work fine.
There is still no fix for the "generic" SOD some have reported on all speeds.
Something has to be different, but we don't know what. I've been trying to generate an SOD my folio the whole evening (and this morning) and resulting in having only one SOD on my Nexus 7 (2012) :silly:
everyone that wants to help with the SOD investigation, please visit this post:
post

Hi everyone.
I have a problem with connection to my Folio 100 in fastboot mode.
When I write fastboot devices appear just this: K fastboot
I think, that must be some numbers or something else, but not just a letter!!!
And when I write fastboot erase recovery, then appear this: FAILED <command write failed <No such file or directory>>
Can someone explain what I can do now?

miro_mad said:
Hi everyone.
I have a problem with connection to my Folio 100 in fastboot mode.
When I write fastboot devices appear just this: K fastboot
I think, that must be some numbers or something else, but not just a letter!!!
And when I write fastboot erase recovery, then appear this: FAILED <command write failed <No such file or directory>>
Can someone explain what I can do now?
Click to expand...
Click to collapse
No idea... Is this linux or windows?
Where did you get fastboot from (download source)?
What is the output of the command "fastboot devices"?

I have placed an update online.
- V6 kernel (SOD workaround on 1.6 Ghz overclock)
- Cyanogenmod low memory patch for dalvik: I'm not sure how much difference this will make. (My folio feels faster/smoother, but it could be a placebo effect...).
Can be installed on top of an existing CM10.1 without data loss (CWM, install zip. You might need to reinstall gapps-nonneon too)

spicyalan said:
No idea... Is this linux or windows?
Where did you get fastboot from (download source)?
What is the output of the command "fastboot devices"?
Click to expand...
Click to collapse
Windows 7 x86.
I've download fastboot from here http://forum.xda-developers.com/showthread.php?t=1941183
Output of the command "fastboot devices" is K fastboot.
I've tried with different fastboot files, but always output is the same!
When I try with "adb devices", then I got the numbers of my device, but in fastboot just K.

miro_mad said:
Windows 7 x86.
I've download fastboot from here http://forum.xda-developers.com/showthread.php?t=1941183
Output of the command "fastboot devices" is K fastboot.
I've tried with different fastboot files, but always output is the same!
When I try with "adb devices", then I got the numbers of my device, but in fastboot just K.
Click to expand...
Click to collapse
Weird,
I have adb and fastboot running on linux (the easiest way), but I also have fastboot on an X64 Windows 7 laptop for quick test-flashing. Here I just installed the Google Android SDK (and worked out-of-the-box), as long as I don't connect it when the Folio is "on" (if it is on, it will mount its files to the windows laptop, but fastboot won't work after that anymore).

All, I have some good an bad news
I have been trying to get kitkat running on the Folio 100.
Good News:
- Got it to compile and generate images.
- Got recovery working (it can install kitkat images. Due to SELINUX I got into some size issues, but got that resolved
Bad News:
- after install, it stays running on the boot animation. Any idea how to check why this happens (ADB will not work in this stage, I think)?
Other bad news:
- The battery of my folio is completely busted (the thing will only run on charger now). Only battery I found on aliexpress was €40.. which is too expensive for an old crappy tablet with a cracked screen.
Linked good news:
- As it is not useful anymore, it can be used exclusively for testing....

Keep going!!
Kitkat on our folio.. not dreamable!!

uc370 said:
Keep going!!
Kitkat on our folio.. not dreamable!!
Click to expand...
Click to collapse
I'm a bit stuck.
Recovery works (it needs a new version with Selinux), but Rom stays stuck on boot animation (and no way to debug...)

spicyalan said:
I'm a bit stuck.
Recovery works (it needs a new version with Selinux), but Rom stays stuck on boot animation (and no way to debug...)
Click to expand...
Click to collapse
Not done any android rom development, but isn't there a log output at least?
Also wasn't there some quite vital parts to the folio that KitKat dropped support for?
Would love to see this working though. Good luck!

EnergyUK said:
Not done any android rom development, but isn't there a log output at least?
Also wasn't there some quite vital parts to the folio that KitKat dropped support for?
Would love to see this working though. Good luck!
Click to expand...
Click to collapse
The xoom guys also got kitkat running.. so it is possible.
(And they use the old 2.6 kernel)
Gapps might be troublesome, but some versions with neon stuff ripped out are popping up.
Adb won't work unless it can boot (and not easy to access any log on the filesystem).

[Solved] WiFi wont turn on after flash!

Hi!
I have an android tablet but I don't know exactly what device it is. Here is everything what I have found:
-Brand: RK3026
-Model: Q8
-Android: 4.2.2 (SDK: 17)
-Kernel: Linux version 3.0.36+ ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC)) #69 SMP PREEEMPT Thu Jan 16 15:50:05 HKT 2014
-Number of the version of the software: rk3026-eng 4.2.2 JDQ39 eng.lijian.20140107.155201 test-keys
-CPU Model: Rockchips Cortex-A9 (Dual Core, freq: 312-1008MHz)
-Renderer: Mali-400 MP
-Resolution: 800x480
-Rear and front camera: 1,9 MP (1600x1200) and 0,3 MP (640x480)
-Ram: 512MB
-System storage: 0,98GB
-Internal storage: 1,90GB
-GPU version: OpenGL ES 2.0
Also I got some manual but there was only "MID Android". Tablet looks like THIS.
First I rooted my device with chinese program called Vroot. Then I installed TWRP and I made backup with it. Then I tried to flash this rom (made by Cash1977) but I didn't flash it with kernel partion so I ended up to a bootloop. Then I tried to restore TWRP backup but the I noticed that it was not proper. The system part size was only 4kt. When I did restore backup my TWRP said "no os installed are you sure you wish to reboot". When I rebooted it ended up to a bootloop again.
Then I tried to flash this rom (made by Oma) but it didn't work. I used rkandroidtool v1.37. First I think that I used wrong kernel so I tried with several kernels and got messed up device badly. I almost bricked it once for good but then I tried different tool called androidtool v2.1. Then I flash with Cash's rom and this kernel (3.0.36+ (lijian) #69) and device booted up nicely. Only porblem is now that wifi is not working
The issue: If I try to turn wifi bar on it will automatic slide to off position. It says that "turning wifi on" but nothing happens. When I go settings>advanced I noticed that mac address is unavailable. Also when I go settings>about tablet>status I found put that imei is unknow.
So far I have tried to flash different rom (the oma's one again) and it works perfectly but wifi not. I have also tried to restore my TWRP again but it says "no os installed". I have also tried to wifi fix app and FXR wifi fix app but they are not helping. FXR wifi fix stops when it says "reading profiles". Can anyone help me?
EDIT: I find this thead and there is the same problem! How I can find those same files (libhardware.so ,libhardware_legacy.so , rkwifi.ko, wlan.ko and 8188eu.ko) for my device. Is the any change that thay still are there somewhere in my TWRP backup?
EDIT2: I think that I find the problem. When I go to the /system/lib/modules/ I find there file named "rkwifi.ko.3.0.8+". I'm using kernel which is 3.0.36+ so I need module for 3.0.36+, right?
EDIT3: Here is the answer to my problem:
"Idea for fix wifi
Check in your stock. If your stock rom run module diver on environment with 3.0.36+ of wifi driver you must replace files to custom rom.
how to:
1. Replace libhardware.so and libhardware_legacy.so from stock rom in /system/lib/
2. Replace module driver files from stock rom in /system/lib/modules/
-8188eu.ko
-8188eu.ko.3.0.36+
-8192cu.ko
-8192cu.ko.3.0.36+
-rkwifi.ko
-rkwifi.ko.3.0.36+
-wlan.ko
-wlan.ko.3.0.36+
3. If another wifi chip make the same too for environment with 3.0.36+
4. If stay problem. to replace all files in folder /system/etc/firmware from stock rom to custom rom folder /system/etc/firmware
Hope to fix your problem.
sorry for bad english language.
Anucha. " Origanlly posted here
Where I can find those files for my device? Can I use just any file named like above?
Solution: Turns out that that my wifi is actually Atheros AR9271 so all I need to do was flash Oma Cube U25GT2-H JB v1.0 rom with my genuine kernel. Everything is working now!