Overclocking w/ BAMF - Thunderbolt General

okay guys, I know im getting pretty annoying here, but I cannot seem to correctlu flash a kernel to save my life. yesterday, I tried to flash Imoseyon's kernel, and got stuck in another boot loop! seriously, if you can help me correctly flash a kernel to overclock, you are jesus.

Runn3rLogic said:
okay guys, I know im getting pretty annoying here, but I cannot seem to correctlu flash a kernel to save my life. yesterday, I tried to flash Imoseyon's kernel, and got stuck in another boot loop! seriously, if you can help me correctly flash a kernel to overclock, you are jesus.
Click to expand...
Click to collapse
What version of ClockworkMod are you using, and how exactly are you trying to flash the kernel? Are you wiping Dalvik before you flash it?

I wrote in your other post to use older recovery 3.0.2.5 always flash everything in recovery, and always wipe cache and divlik before you flash anything just good practice.
Sent from my Synergized BOLT VIA XDA app
"If i helped you please thank me"

Related

[Q] What's the deal with kernels?

Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Mr.Clark said:
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Click to expand...
Click to collapse
1) No, you should not wipe anything before flashing a kernel. You should however do a NANDroid backup.
2) You should be able to but it will wipe your kernel.
3) Restore your backup from #1
Mr.Clark said:
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Click to expand...
Click to collapse
flashing a kernel doesnt wipe your phone, it simply replaces whatever kernel is in your phone at the moment.
kenvan19 said:
1) No, you should not wipe anything before flashing a kernel. You should however do a NANDroid backup.
Click to expand...
Click to collapse
Right. Guess what my next question will be
kenvan19 said:
2) You should be able to but it will wipe your kernel.
3) Restore your backup from #1
Click to expand...
Click to collapse
2) Is fine, as once I've figured out how to NANDroid backup, re-flashing it should be easy enough. 3) Is fine, once I've taken the backup in the first place.
simms22 said:
flashing a kernel doesnt wipe your phone, it simply replaces whatever kernel is in your phone at the moment.
Click to expand...
Click to collapse
Excellent, thanks!
Ok. So all the NANDroid guides I've seen here start with ADB and Fastboot (which I remember doing when I rooted the phone), but then they say about flashing alternative recovery images... is that necessary? Or is that what the fastboot thing was?
I've just checked and ADB still works, so if fastboot is an alternative recovery image, am I good to take a NANDroid backup, and if so, how do I do that?
If Fastboot is not an appropriate recovery image, do I need Clockwork Recovery (is that different to the "CWM" I see mentioned around here?)?
The Nexus S guide I read said that there was a NANDroid option in the Clockwork Recovery. Now this isn't in my recovery options, obviously, but I assume with ADB, a command prompt and a few instructions, I can do it manually. Maybe.
Bear with me guys, I'll get there eventually...
Ok, scratch the NANDroid questions. NANDroid is a backup tool contained in the Clockwork Mod recovery image.
Using Fastboot, you can boot from the recovery image without flashing it (using this guide here), so I've still got whatever recovery image I got when I did Paul's rooting technique, but have booted into CWM once to do the NANDroid backup.
I may flash CWM later, that's a task for another day.
So. Now I've got the backup (and thus, booting from that image again later, the ability to restore from it), I can try flashing the kernel. Which I can do from the regular recovery image.
Mr.Clark said:
Ok, scratch the NANDroid questions. NANDroid is a backup tool contained in the Clockwork Mod recovery image.
Using Fastboot, you can boot from the recovery image without flashing it (using this guide here), so I've still got whatever recovery image I got when I did Paul's rooting technique, but have booted into CWM once to do the NANDroid backup.
I may flash CWM later, that's a task for another day.
So. Now I've got the backup (and thus, booting from that image again later, the ability to restore from it), I can try flashing the kernel. Which I can do from the regular recovery image.
Click to expand...
Click to collapse
To flash from the stock recovery you must rename files update.zip just FYI. I've said it before and I'll say it again; there are no possible negative repercussions from flashing a non-stock recovery image.
Apparently it was unsigned, so the stock recovery wouldn't do anything with it.
Back in CWM and it worked fine. I may have to flash that, it's damned useful...
So now I have a new kernel!
Thanks for all your help
Mr.Clark said:
Apparently it was unsigned, so the stock recovery wouldn't do anything with it.
Back in CWM and it worked fine. I may have to flash that, it's damned useful...
So now I have a new kernel!
Thanks for all your help
Click to expand...
Click to collapse
It is very useful indeed! Enjoy your kernel
Ah, am I right in thinking that if I flash CWM, I can't revert back to stock if I want to?
I'm hoping to do nothing permanent at this point...
Mr.Clark said:
Ah, am I right in thinking that if I flash CWM, I can't revert back to stock if I want to?
I'm hoping to do nothing permanent at this point...
Click to expand...
Click to collapse
Yes, you can flash back. Not only can you but depending on how you did flash the recovery the phone may revert it on your behalf. I know mine has several times, like any time I reboot. There's ways to stop it from doing that but I don't mind.
To get the stock recovery back if it isn't automatically restoring means flashing an NAND from the Dev section here.
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
nicholasbgr said:
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I use overclocked with voodoo and setcpu...you can keep it set to 1000 and not over the stock limit.
Bionix 1.3 is solid and no OC
Sent from my Nexus S using XDA App
nicholasbgr said:
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you flash the Trinity max kernel and do not adjust the clock you will have everything your asking for. This kernel boots at stock and has Voodoo and ext4 built in.
icandy75 said:
If you flash the Trinity max kernel and do not adjust the clock you will have everything your asking for. This kernel boots at stock and has Voodoo and ext4 built in.
Click to expand...
Click to collapse
So your saying the trinity max kernel has voodoo built in?
Sent from my bionix nexus s
mrnexus said:
So your saying the trinity max kernel has voodoo built in?
Sent from my bionix nexus s
Click to expand...
Click to collapse
That is exactly what he is saying, yes =)
Thanks guys, I'm gonna take a look at your recommendations as soon as I get some spare time.
Do all the trinitys have voodoo
Sent from my bionix nexus s
mrnexus said:
Do all the trinitys have voodoo
Sent from my bionix nexus s
Click to expand...
Click to collapse
No, only the most recent ones.
kenvan19 said:
No, only the most recent ones.
Click to expand...
Click to collapse
Such as:
Sent from my bionix nexus s

[Q] Why can I not install a new Kernel?

Hi All
Finally plucked up the courage to register and ask a question after lurking for the good part of 2 years.
I've an i9020A and have flashed CyanogenMod 9 v4.0.3 v1.0 which is great, however I wanted to try Steve Garon's kernel which just wont take.
I reboot into Recovery, wipe Dalvik Cache a couple of times, install Steve's kernel which apparently flashes no problem.
I reboot and get the optimising Android applications screen then check my kernel under settings.
It is still the original KalimochoAz kernel and I cannot turn on my wireless.
Now this has happened previously when trying to also update my kernel under CDTDroid's AndroidMe 1.2 which I could only fix by restoring back to 1.1.
Any idea on what may be wrong here guys?
Appreciation in advance.
Lally
Have you tried just flashing again? A bad flash often results in wifi not working and may be the cause of the about page showing the old kernel. Remember to wipe dalvik cache again, too.
Thanks for the reply Harbb, do you mean a re flash of the Kernel or ROM? If Kernel then yeah I have done, same scenario. I'll also try a re download of the Kernel to see if that improves anything but this is much akin to me trying to update from Speedy3 to Speedy4 under AndroidMe 1.2 which was unsuccessful.
Just the kernel, as you've already tried. Just remember to do a NANDroid backup (CWM --> backup & restore --> backup) when you have a stable, working ROM. Can save you alot of trouble if you don't have a relatively recent one.
Also, are you using CWM 5.0.2.0? And could it be that your phone isn't particularly happy about the 1100mhz OC with Steve Garon's kernel?
I'd suggest updating CWM recovery to the latest version.
Sent from my Nexus S using xda premium
Cheers for the help guys.
Yes, using 5.0.2.0, but something is not right cause I just tried to flash CWR again from within Rom Manager (4.8.1.3) and it gets to around 95% and the app gives 'Rom Manager is not responding.
Looks like I'll have to try a complete wipe and reflash.
Will report back the results.
Forget rom manager all together.
Download the recovery you want to use.
Flash it via fastboot
flash kernel.
I'd do what albundy said - flash a new recovery through fastboot and make sure the bootloader is unlocked (vol. up + power --> bootloader: unlocked)
Ok, downloaded CM9 1.1, redownloaded Steves kernel, reinstalled recovery from fastboot.
Wiped and formatted everything twice then installed from scratch.
So far everything is good, still getting errors on Superuser, but installing again via recovery seems to fix that issue.
Cheers chaps.
Good to know Lally, happy you got it sorted out.
Cheers Harbb, the test will be when I want to change the kernel again I suppose, one complete wipe and install a day is enough

[Q] I need help fixing my phone - Tried downgrading the rom, now won't boot

So I used to run the CM7 rom, then upgraded to a ISC WIP. Well, it was pretty unstable, and wanted a stable rom, so tried restoring my old CM7 backup, and now when I turn on my phone, it shows the HTC splash screen, the goes black (screen still on), and won't go past that. I realize now I downgraded the firmware, and you can't do that.
My buddy said I need to get some toolkit and reset EVERYTHING back to stock roms, re-root and all that. So can some generous person link to all that? I see a lot of it in the Inspire 4G forums, but want to make sure I have it all. And after I flash all the stock stuff, can I restore that CM7 backup (clockwork recovery mod)?
Thanks in advance for the help/reply, much appreciated.
If you can get into hboot, this may help you:
http://forum.xda-developers.com/showthread.php?t=1396229
pazzo02 said:
If you can get into hboot, this may help you:
http://forum.xda-developers.com/showthread.php?t=1396229
Click to expand...
Click to collapse
That's what I was looking at, wasn't 100% sure if it's the right tut for me. Thanks for the reply!
Do I need to reinstall recovery, or flash the stock rom?
Oathdynasty said:
Do I need to reinstall recovery, or flash the stock rom?
Click to expand...
Click to collapse
You should follow the steps to reinstall recovery, then go to flashing a rom. You only need to go through the "flashing a stock rom" section if you had problems reinstalling recovery. Just read through all the steps and you'll get it.
Oathdynasty said:
Do I need to reinstall recovery, or flash the stock rom?
Click to expand...
Click to collapse
If you are S-OFF you just can flash a new recovery image and then flash any rom you want. You will have to do it from command prompt...
if you need help in doing that, just let me know...
glevitan said:
If you are S-OFF you just can flash a new recovery image and then flash any rom you want. You will have to do it from command prompt...
if you need help in doing that, just let me know...
Click to expand...
Click to collapse
I could use some help haha. I tried downloading the stock rom (PD98IMG.zip) from multiupload, but it'd down, and the mirror says it'll take several hours.
Oathdynasty said:
I could use some help haha. I tried downloading the stock rom (PD98IMG.zip) from multiupload, but it'd down, and the mirror says it'll take several hours.
Click to expand...
Click to collapse
Look in the second post in that thread. The OP noted last month that there were probs with multiupload and posted an alternate dl.
pazzo02 said:
Look in the second post in that thread. The OP noted last month that there were probs with multiupload and posted an alternate dl.
Click to expand...
Click to collapse
I got it. I went on the cyanogenmod irc, and they helped me. I didn't have to flash anything stock, I rebooted into my bootloader, went into recovery, wiped system, data, dalvik, cache.... All that, flashed cm7 and restored
Sent from my Desire HD using Tapatalk
Good. Glad you got it fixed
Oathdynasty said:
I got it. I went on the cyanogenmod irc, and they helped me. I didn't have to flash anything stock, I rebooted into my bootloader, went into recovery, wiped system, data, dalvik, cache.... All that, flashed cm7 and restored
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Glad you got it sorted out, To be honest that is the first thing you do when a rom wont boot. Whenever you restore a backup it is best to wipe first

[Q] EB GB2.3.3 1.0.9 switching to EB GB 2.3.7?

So I have Eagleblood 2.3.3, 1.0.9 and looking to switch to this one: http://forum.xda-developers.com/showthread.php?t=1124522
Im not sure but i think this is the latest Eagleblood Rom out....correct me if im wrong.
1) So can I just flash this new Rom like any other or do i need to do some other stuff to the phone first?
2) If you guys recommend switching, which kernel should i get and how do you install a kernel?
Right now im just running EB1.0.9 with no extra kernel. Im not familiar with kernels.
2) How and when do I flash a Kernel? Before, after, or while you are flashing a Rom?
3) Do you wipe anything when installing a kernel?
TheKid1 said:
So I have Eagleblood 2.3.3, 1.0.9 and looking to switch to this one: http://forum.xda-developers.com/showthread.php?t=1124522
Im not sure but i think this is the latest Eagleblood Rom out....correct me if im wrong.
1) So can I just flash this new Rom like any other or do i need to do some other stuff to the phone first?
2) If you guys recommend switching, which kernel should i get and how do you install a kernel?
Right now im just running EB1.0.9 with no extra kernel. Im not familiar with kernels.
2) How and when do I flash a Kernel? Before, after, or while you are flashing a Rom?
3) Do you wipe anything when installing a kernel?
Click to expand...
Click to collapse
ya caught me in a good mood this morning... heres what you do:
1) yes, but you will want to do a full wipe to avoid lagging and force-closing of apps after the install.
2) there are only 3 kernels for this device Faux123's, Morfic's (my personal favorite) and Harsh's just read the first posts and some of the latiest comments to get an idea of what does and does not work in each (or just flash em all, theres only 3)
you flash kernels the same way you flash a rom, just wipe cache after you flash it, and if you want to go back to no kernel, just re-flash your ROM and it will replace the kernel with the stock one
3)just cache.
good luck! and if you have some time, read This it explains all of this and more but better than me.
Klathmon said:
2) there are only 3 kernels for this device Faux123's, Morfic's (my personal favorite) and Harsh's
3)you flash kernels the same way you flash a rom, just wipe cache after you flash it
Click to expand...
Click to collapse
Are you saying there are only 3 Kernels for the G2X in general or only 3 kernels for eagleblood roms?
And did you mean wipe cache "before" you flash a kernel?
TheKid1 said:
Are you saying there are only 3 Kernels for the G2X in general or only 3 kernels for eagleblood roms?
And did you mean wipe cache "before" you flash a kernel?
Click to expand...
Click to collapse
only 3 kernels total faux morfic and harsh and thats all of em.
they faux and morfic's have a few different versions, but if you read the posts and threads you can see the differences between them
and no, you wipe cache after you flash the rom/kernel
Klathmon said:
only 3 kernels total faux morfic and harsh and thats all of em.
they faux and morfic's have a few different versions, but if you read the posts and threads you can see the differences between them
and no, you wipe cache after you flash the rom/kernel
Click to expand...
Click to collapse
But hasn't it always been to clear cache and then install a custom rom? Its like in the direction of every rom?
Sent from my LG-P999 using xda premium
Just wanted to point out that harsh's kernel is designed for ICS. Best not to try to install it on a GB based rom.
Jakkumn said:
Just wanted to point out that harsh's kernel is designed for ICS. Best not to try to install it on a GB based rom.
Click to expand...
Click to collapse
oh ****! yeah dont flash Harsh's
thats what i get for assuming he wanted ICS...
NekoNyapii said:
But hasn't it always been to clear cache and then install a custom rom? Its like in the direction of every rom?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
its honestly not that big of a deal for cache, you wipe data before, and ideally you wipe cache after (just in case the flash puts something retarded in there)
either way your fine really

Cannot flash new kernel

Hi xda. I just installed (flashed) cyanogenmod 9 on my nexus s, after getting bored with the stock kernel so I flashed trinity ics kernel. Now when I try and flash a new kernel nothing changes, cwm recovery said it flashed successfully. The procedure I did when I installed it was:
1) install zip from SD card
2) choose zip
3) yes
4) reboot system
Is there anything I did wrong? Do i need to clean the cache and dalvik cache?
Sent from my Nexus S using xda premium
How are confirming that it did not flash?
Clockwork recovery said it was successfully installed. Also the version of the kernels are right for my rom (ics)
Sent from my Nexus S using xda premium
You missed understood me.
How are you checking/confirming that the kernels you flashed after trinity are not actually flashing/ booting/being used or how ever you want to phrase it?
cm changed their ramdisk(again). so now custom kernels without cm ramdisk wont boot cm. as always, cm likes to "break" things. complain to cm. i recommend other non cm based roms, like rasbean jelly. it doesnt have as much junk included and is a faster/smoother experience than cm. many kernel developers arent willing to cater to cm anymore because of these changes they constantly make. enough is enough.
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
maybe so, bit i dont see a mention of a boot animation
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
ah, ok. i reread the op very slowly.
op, did you check the kernel version in your about phone? other kernels wont get rid of the boot animation unless they offer a boot animation or include a script to delete it.
Yeah. But he is saying he doesn't see a change. Implying the phone boots up as it did prior.
He is also on cm9 , not the new cm10 that botched things up again.
That is why I am trying to get him to confirm how he is checking if the kernel changed. Almost certain its the op just seeing the boot animation and thinking that it didn't change due to that.
Op. Go to settings /about phone and look at kernel version. Flash a different kernel again. Check again.
I am confirming that it did not flash by going to settings and then about phone. In kernel it still says Trinity kernel rather that matrix kernel or air kernel (2 roms I've tried flashing).
Sent from my Nexus S using xda premium
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
[/QUOTE]
albundy2010 said:
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
Click to expand...
Click to collapse
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.[/QUOTE]
albundy2010 said:
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
Click to expand...
Click to collapse
Ok ll try that
You can flash my cm compatible kernel.
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
p1gp3n said:
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I gave up and flash a new rom and kernel thanks for the help.

Categories

Resources