[Kernel] - AwesomeSauce[2wcr][usb host]

**LaloHigh** · 10-07-2012, 04:50 PM

If you want I could test, just pm me a link.

**thicklizard** · 10-07-2012, 04:56 PM

Originally Posted by LaloHigh

If you want I could test, just pm me a link.

What max speed do you want?

Sent from my EVO using Tapatalk 2

**LaloHigh** · 10-07-2012, 05:00 PM

2.1, I was able to oc at 2.1 before with the older base kernel

**LaloHigh** · 10-07-2012, 07:28 PM

Ok here are my findings with raisedboot. stock 2.13 deodex- boots fine, cpu1 always offline I can enable mpdecision but then it won't go offline, and while checking stats it never hits 2.1 only up to 1.5 even thou I have it set to 2.1. Using no-frills by the way.

On viper4g 2.0.2 and chubbz 4.5 v2, both act exactly the same as I mentioned on my other post. If nofrills not granted su permission at an early stage when sense is loading after a phone reboot it will lock up. This is how the kernel begins after a fresh kernel install. See max clock freq.

**Sullivan7221** · 10-09-2012, 12:23 AM

ok, ill try yo keep this simple.... long story short, i need help. ive been boot looping for more than 2 hours now and i dont know what else to do. now, long story.
i was running venom rom v2.0.2 and had no issues. i installed awesomsauce 2.2 (oc1.89) and it installed fine and ran fine. as a matter of fact, oc'd @ 1.89 using the badass governer and sio scheduler i hit a quadrant of over 6900!! so then i got greedy and figured id try the OC 2.1ghz version. It said it installed but i just boot looped over and over and over. so i tried again, same thing. so i tried to reinstall the 1.89 version, still boot looping. i tried reinstalling the rom, still boot looped. i tried again, same thing. so tried restoring a backup, i have one of the stock rom from right after getting root and of the venom rom and like everything else after flashing they say successful but they boot loop as well. so i looked into pushing the boot.img with fastboot and i couldnt get the laptop to find the device. i then tried the htc dumlock method in twrp and reflashed both kernels and still never booted. now, ive givin up...for tonight anyways!! i just dont know what else to try. i can get back to bootloader and recovery all i need to, but it doesnt appear to flash anything correctly.

hboot 1.15, s-on of course
hardware 003
twrp 2.2.2
regaw/htc dev unlocked
sdk installed with platform-tools, adb works fine for pushing and pulling built apks and apktools work for building them.

if any other info is needed to hrlp me trouble shoot this i will gladly provide what i can. for now, im wo tired and pissed i can hardly see straight... so im off to bed. thanks all and especially thicklizard for a great kernel!!!!

**jelive** · 10-09-2012, 04:53 AM

Perhaps recovery has minor corruption...shows successful flash/restore but maybe it really isn't...??

**urrgevo** · 10-09-2012, 05:11 AM

Originally Posted by jelive

Perhaps recovery has minor corruption...shows successful flash/restore but maybe it really isn't...??

Hopefully its something like that. @sullivan, what I would try is to pull off everything from the internal and external storage, then wipe the internal storage and format the external.sdcard, and grab a fresh download of a Rom and go from there. Wipe repeatedly pre flash, I've heard some say twrp has intermittent wiping issues. If its a no go then idk, I would try and see if I could reinstall twrp somehow at that point. Unfortunately that's all I have to offer in the way of advice, good luck man. Hopefully you were just tired and frustrated and missed a step in your process that caused this :/

**debarron** · 10-09-2012, 06:02 AM

You probably need to get your laptop to recognize your phone so you can fastboot flash a working kernel since your s-on. Your phone has to be in "fastboot usb" mode. From what I've read, your phone has to be able to boot up for the s-on installer to work, which would be why reflashing the 1.89 kernel isn't working.

**Sullivan7221** · 10-09-2012, 07:46 AM

so i managed to push a new recovery.img and boot.img to the device via fastboot ("fastboot devices" found the device, last night i was trying "adb devices") .....and after this it booted!!!!!!!! I SHOULD BE GOOD NOW.... i hope. atleast now i know how to fastboot a boot.img and what not... i had never done it before. thanks for the help guys.

**Sullivan7221** · 10-09-2012, 07:54 AM

so what should the kernel version read after installing the the boot.img from version 2.2 (1.89)??? , mine reads "3.0.8-01680-gb6402b4 root@ABM303 #1 SMP PREEMPT". This isnt right is it?? doesnt it usualy say awesomesauce x.xxxx????

EDIT 1:nevermind, its the stock kerenl. odd. ill try to push it again.
EDIT 2: tried again, now it reads 3.0.8Awesomesauce.....!!!!!!!!!!