if you are using voltage control, it prompts you to make a recovery zip incase of something like that. its called vcrecovery.zip or something like that. itll be on your sd card and flashable via cwm. idk what nstools does or not, havent used it yet, im in the process of flashing this kernel now on my girls epic (she has mine today :/ .) but this is a prime example of why you should always make a nandroid before playing with uv, and why you should never set boot settings until youre absolutely sure. sorry bro, youre gonna have to either restore an old backup, or start clean.
edit: you might try just flashing cm9, aokp, or whatever rom youre using without doing a data wipe, that should flash their stock kernel and remove boot settings, then you would be able to keep all your data, but if its been corrupted from bad shutdowns/freezing/locking up, youre kinda outta luck. youll have to restore an old backup or flash the rom and kernel again fresh. try that, just wipe dalvik and cache, let us know if it works, good luck.
---------- Post added at 10:57 AM ---------- Previous post was at 10:37 AM ----------
at first i was like:
what happened to samurai and wheatly!?!?
but then i read that you "tweaked conservative, and tweaked ondemand." did you tweak conservative to act a little more like samurai and ondemand to act a little more like wheatly? thats what it seems like.
oh yeah and, i see that someone posted you can adjust the gpu voltage via nstools (which i havent gotten around to downloading yet.) Does this kernel also allow for GPU overclocking?
---------- Post added at 11:23 AM ---------- Previous post was at 10:57 AM ----------
hey, found this on nstools thread on xda, if thats what you used, maybe it will help:
- If something bad happenned and you want to reset NSTools config,
install reset_nstools.zip in recovery (if its not work, try to mount /data from recovery menu before applying the zip)
- If you want to switch kernel, i recommend to uncheck 'restore on boot' setting.
It will reset to default kernel setting. You can recheck that after reboot.
- starting in v1.8 app will detect kernel version on boot, if the version has changed the settings will be discarded.
- The new permission on v1.12 and up: read contacts is used for detect missed call. You can check the source code on my github to make sure this app don't read/send your contacts data.
- read this thread about CPU governor
- for those who have problem with smartassV2 governor settings, ask your kernel developer to patch their source, see this post
Originally Posted by krfoy
just fix the issue in smartassV2 (link: https://github.com/abev66/linux_NS_I...78b8567efa9bc2
it's not a NSTools issue.
hope that helps you out some bro.