Hi all,
i´m testing francos kernel for now. But if i want to get back to Stock, where i can download it ? Searched all thru but found nothing.
Thanks for help!
peste
peste76 said:
Hi all,
i´m testing francos kernel for now. But if i want to get back to Stock, where i can download it ? Searched all thru but found nothing.
Thanks for help!
peste
Click to expand...
Click to collapse
If you want to go back to stock, either reflash the stock ROM, or extract the .zip file and then use fastboot to flash boot.img in it "fastboot flash boot boot.img"
kyokeun1234 said:
If you want to go back to stock, either reflash the stock ROM, or extract the .zip file and then use fastboot to flash boot.img in it "fastboot flash boot boot.img"
Click to expand...
Click to collapse
ahh, boot.img - how noobish from me Thanks a lot.
Yes boot.img. If you want to go back to stock... If you want ONLY kernel, you should search it up, because I don't know which file does that...
Let me explain it a little bit more. boot.img is ramdisk+kernel. There's another file I believe that only handles kernel. But if you want to go back to stock, you'll need to flash ramdisk too (Since Franco uses its own ramdisk). I hope that helped you
boot.img = ramdisk+zImage
zImage = kernel
thanks kyokeun1234.
One thing you guys need to keep in mind is that some custom kernels (like franco's) change some files on your ROM (i.e., system partition), so flashing just the stock boot image is not going to be enough. (Don't ask me which files, as I can't remember right now, but there is a few, i.e., 1-3.)
efrant said:
One thing you guys need to keep in mind is that some custom kernels (like franco's) change some files on your ROM (i.e., system partition), so flashing just the stock boot image is not going to be enough. (Don't ask me which files, as I can't remember right now, but there is a few, i.e., 1-3.)
Click to expand...
Click to collapse
Yeah, I always forget that, but actually I am aware of some kernels tweak/place init.d scripts, for example, and that could conflict with stock or any other kernel.
I'll be sure to add that to the usual procedure, making a mental note. thanks efrant.
efrant said:
One thing you guys need to keep in mind is that some custom kernels (like franco's) change some files on your ROM (i.e., system partition), so flashing just the stock boot image is not going to be enough. (Don't ask me which files, as I can't remember right now, but there is a few, i.e., 1-3.)
Click to expand...
Click to collapse
So basically flashing the whole Rom is the only choice
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
You can use franco's app to restore your stock kernel without re flashing your rom.
Sent from my Galaxy Nexus using Tapatalk 2
kyokeun1234 said:
So basically flashing the whole Rom is the only choice
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
It depends on the kernel. What I would do personally is: before flashing a custom kernel, open up the file that you are flashing, and see which files it is replacing (aside from boot.img). Then I would back those up. That way, if you ever want to go back to stock, you just have to replace those files.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
It depends on the kernel. What I would do personally is: before flashing a custom kernel, open up the file that you are flashing, and see which files it is replacing (aside from boot.img). Then I would back those up. That way, if you ever want to go back to stock, you just have to replace those files.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Oh thanks! It's been long time since I've learned a new thing I'll keep that in mind!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Related
Hey just 2 quick questions in the way of Kernels.
1 what is the best kernel for saving battery available for the galaxy Nexus?
2. How would I go back to the stock kernel after flashing a custom one? (how do I revert back)
Thanks!
Sent from my GNex running gummy v0.7.0
Hydera5 said:
Hey just 2 quick questions in the way of Kernels.
1 what is the best kernel for saving battery available for the galaxy Nexus?
2. How would I go back to the stock kernel after flashing a custom one? (how do I revert back)
Thanks!
Sent from my GNex running gummy v0.7.0
Click to expand...
Click to collapse
I love Francos Kernel, and I think most people on this forum will tell you the same. For now, its the bomb diggity. As for reverting back, you should be making a nandroid backup in Rom Manager before every flash just incase something goes wrong so you dont lose anything. Flashing that nandroid back will give you your old kernel back.
No need for nandroids, if you want to revert to stock kernel, just grab stock from zip, extract boot.img
Reboot phone into boot loader/fastboot, 'fastboot flash boot boot.img', done.
Hi,
I was wondering where I would be able to find the stock kernel used with Roman's AOKP (b38) for the Galaxy Nexus (GSM).
Main reason is I am wishing to try franco's 181 with 384 GPU, but would like the option to switch back to stock if I find that franco's isn't as smooth or reliable.
Thanks in advance.
mk_ln said:
Hi,
I was wondering where I would be able to find the stock kernel used with Roman's AOKP (b38) for the Galaxy Nexus (GSM).
Main reason is I am wishing to try franco's 181 with 384 GPU, but would like the option to switch back to stock if I find that franco's isn't as smooth or reliable.
Thanks in advance.
Click to expand...
Click to collapse
Settings - about phone - kernel version. I think it's faux's kernel, at least used to be. Or just flash the rom again, it'll put back the stock (rom) kernel.
thanks, but doesn't flashing the rom again wipe data?
mk_ln said:
thanks, but doesn't flashing the rom again wipe data?
Click to expand...
Click to collapse
It doesn't, no
thanks again for the quick reply, and yes, it does seem that the kernel used is faux's kernel (017+). currently faux's seems to be on 018.
mk_ln said:
thanks again for the quick reply, and yes, it does seem that the kernel used is faux's kernel (017+). currently faux's seems to be on 018.
Click to expand...
Click to collapse
Not always necessary to update, 17+ is a heck of a kernel..
maybe it was just me, but it seems you were right about kernel 017; I probably should have left everything as it was.
after flashing franco's as well as faux's 018, it seemed that 017 was actually slightly smoother. in order to get back to 017 i did as you suggested and flashed the entire rom. unfortunately all my gmail accounts were lost/forgotten as well as the gapps; opening gmail would result in a crash w/o a message...same thing happened with the play store and i had to reinstall the gapps.
i was thinking about flashing just the boot.img from the flashable zip using fastboot, but i wasn't, and still am not, sure if that would have provided me the same result as flashing through CWM.
If you reflash the rom you have to reflash the gapps and you should be fine.
"Long is the way, and hard, that out of hell leads up to light."
Nandroid. It will backup the kernel, just make sure if you go back, you restore system as well because each kernel can have a few libs with it that another might not.
Also, you should be in the ha bit of making a nandroid whenever you flash something, until you can verify there are no bugs you can't live with.
Sent from my Sensation using Tapatalk 2
mk_ln said:
maybe it was just me, but it seems you were right about kernel 017; I probably should have left everything as it was.
after flashing franco's as well as faux's 018, it seemed that 017 was actually slightly smoother. in order to get back to 017 i did as you suggested and flashed the entire rom. unfortunately all my gmail accounts were lost/forgotten as well as the gapps; opening gmail would result in a crash w/o a message...same thing happened with the play store and i had to reinstall the gapps.
i was thinking about flashing just the boot.img from the flashable zip using fastboot, but i wasn't, and still am not, sure if that would have provided me the same result as flashing through CWM.
Click to expand...
Click to collapse
That is exactly what you should have done. Just restoring boot.img is only the kernel. I do it all the time.
RogerPodacter said:
That is exactly what you should have done. Just restoring boot.img is only the kernel. I do it all the time.
Click to expand...
Click to collapse
thanks.
just to confirm, is the command "fastboot boot boot.img" or "fastboot flash boot.img"...? or perhaps something else entirely?
Fastboot flash boot boot.img
"Long is the way, and hard, that out of hell leads up to light."
thanks!
Hello,
i recently installed 3rd party kernel on my rom and i would like to revert back to the rom stock kernel, i'm aware that i can flash boot.img, but I got a bit confused when I tried to flash it via gnex toolkit - what options shall I choose ? permanent/temporary - and which section shall I select after that screen ? unless of course there are easier methods to install boot.img - such as through manual adb fastboot command.
any help would be greatly appreciated,
Thanks!
If you want the rom stock kernel just reflash the rom.
"Long is the way, and hard, that out of hell leads up to light."
thanks, of course that's an option, but i was trying to avoid that, anyhow I managed to install just the stock kernel without having to reflash rom - i used gnex toolkit, copied boot.img (extracted from rom) into appropriate toolkit folder and selected the first option (boot) and voila i have the rom stock kernel...thanks anyway.
If you had a nandroid with that stock kernel just do advanced restore of the boot.img only.
Was this a question or a statement? As its in the q&a section, people gave you suggestions and you reply by correcting them and telling them what you did.
Why even ask or post it in the q&a thread??? (question)
Sent from a phone...
this seamer
@edfunkycold
easy mate, chill...was just a question, I didn't correct anyone, just wanted to let anyone know that I sorted it out somehow...perhaps it can help other users, especially newbies like me..
@jerrycycle
thanks mate!
zeelog said:
@edfunkycold
easy mate, chill...was just a question, I didn't correct anyone, just wanted to let anyone know that I sorted it out somehow...perhaps it can help other users, especially newbies like me..
Click to expand...
Click to collapse
I wasn't in attack mode just inquisitive as I didn't understand is you were asking or saying. Suggestion maybe you should update title of thread and place [fixed] or something like that. Glad you got it worked out. Another question for you, why where you so opposed to just reflashing your rom? You don't have to wipe just flash right over and in less than 1 minute it would have been done and the kernel your rom came with back on?
Sent from a phone...
Sorry repost please delete
edfunkycold said:
I wasn't in attack mode just inquisitive as I didn't understand is you were asking or saying. Suggestion maybe you should update title of thread and place [fixed] or something like that. Glad you got it worked out. Another question for you, why where you so opposed to just reflashing your rom? You don't have to wipe just flash right over and in less than 1 minute it would have been done and the kernel your rom came with back on?
Sent from a phone...
Click to expand...
Click to collapse
ed, for the simple reason that i'm using paranoidandroid, now imagine i have tons of apps using different lcd densities, thus reflashing the rom would have resulted in re-setting the densities for each and every app from scratch (at least i'm assuming that would have happened) - i wouldn't have bothered if i was using another rom such as aokp or something similar...
edfunkycold said:
Was this a question or a statement? As its in the q&a section, people gave you suggestions and you reply by correcting them and telling them what you did.
Why even ask or post it in the q&a thread??? (question)
Sent from a phone...
Click to expand...
Click to collapse
Because the first suggestion (flash a stock rom) doesn't make sense. Why would he flash a stock ROM when all he wanted was the stock kernel? (Yes, it was not written clearly, but it was pretty obvious he wanted to flash the stock kernel, not the stock ROM...)
joshnichols189 said:
If you want the rom stock kernel just reflash the rom.
"Long is the way, and hard, that out of hell leads up to light."
Click to expand...
Click to collapse
It said reflash rom it didn't say anything about stock. He wanted the kernel which his rom came with.
simply by flashing it over his existing setup without wiping would have replaced the kernel to what he wanted and maintained all his settings as he currently has them. Simple less than 1 minute resolve. But hey he did it anyway the long route by extracting and flashing image on fastboot. That he resolved what he was trying to accomplish is all that matters. Symantics about which way may have been easier is of no consequence, I was just curious as to why he didn't try what seemed as the simplest route.
efrant said:
Because the first suggestion (flash a stock rom) doesn't make sense. Why would he flash a stock ROM when all he wanted was the stock kernel? (Yes, it was not written clearly, but it was pretty obvious he wanted to flash the stock kernel, not the stock ROM...)
Click to expand...
Click to collapse
Sent from a phone...
The way i see it, OP should just use the tools, not the toolkits.
Simply rebooting to bootloader, extract boot.img from his current rom, 'fastboot flash boot boot.img' would avoid reflashing the entire rom.
Or, through a previously taken nandroid, choose advanced restore in recovery, and only restore boot.img.
Sent from my i9250
hello.
so, if I recently flashed a custom kernel (franco) by installing from .zip through cwm, and I wanted to restore the stock jb kernel,
do i just restore the boot.img on cwm or do i have to restore system.img (or any other image) as well?
thanks!
Only boot.img
Sent from my Galaxy Nexus using xda premium
zephiK said:
Only boot.img
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks! i was just confused because there were other files in franco's .zip besides the boot.img and was wondering what those were for? do they change anything else?
or reflash your JB rom
maatae said:
thanks! i was just confused because there were other files in franco's .zip besides the boot.img and was wondering what those were for? do they change anything else?
Click to expand...
Click to collapse
they are apart of the modifications that franco did (such as the sdcard binary)
but +1 to what acloh said... best thing to do is just reflash the base ROM. if gapps are needed then flash gapps right after you flash the ROM as well.
zephiK said:
they are apart of the modifications that franco did (such as the sdcard binary)
but +1 to what acloh said... best thing to do is just reflash the base ROM. if gapps are needed then flash gapps right after you flash the ROM as well.
Click to expand...
Click to collapse
I see. Thanks! Stupid question...how do you reflash stock rom? I tried installing the original ota zip i used updating takju to jb but got a status 7 error. As of now I've just done a full restore of a cwm backup I did right before flashing Franco. Help?
maatae said:
I see. Thanks! Stupid question...how do you reflash stock rom? I tried installing the original ota zip i used updating takju to jb but got a status 7 error. As of now I've just done a full restore of a cwm backup I did right before flashing Franco. Help?
Click to expand...
Click to collapse
You should always look inside the kernel zip and see what files it's going to modify. Then back up those files before flashing it.
If you've restored your nandroid (pre-franco), then you should be good to go for the OTA (assuming you didn't change anything else...)
efrant said:
You should always look inside the kernel zip and see what files it's going to modify. Then back up those files before flashing it.
If you've restored your nandroid (pre-franco), then you should be good to go for the OTA (assuming you didn't change anything else...)
Click to expand...
Click to collapse
so even if I'm already on the version I want (4.1.1) after the restoration, I should still reinstall the takju4.0.4 ->4.1.1 OTA.zip?
Also, are there any recommended caches I should clear after changing kernels?
Thank you.
maatae said:
so even if I'm already on the version I want (4.1.1) after the restoration, I should still reinstall the takju4.0.4 ->4.1.1 OTA.zip?
Also, are there any recommended caches I should clear after changing kernels?
Thank you.
Click to expand...
Click to collapse
?? Not sure I understand. If you restored 4.1.1, then you obviously do not need any update.
No, you don't have to wipe any caches.
efrant said:
?? Not sure I understand. If you restored 4.1.1, then you obviously do not need any update.
No, you don't have to wipe any caches.
Click to expand...
Click to collapse
Ok, thank you. I guess my main question was whether or not I have to wipe caches in between kernel switches. Again, Thanks!
I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?
Robert00001 said:
I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?
Click to expand...
Click to collapse
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.
simms22 said:
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.
Click to expand...
Click to collapse
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.
simms22 said:
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.
Click to expand...
Click to collapse
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?
Robert00001 said:
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?
Click to expand...
Click to collapse
It gets you whatever kernel was originally in the ROM.
063_XOBX said:
It gets you whatever kernel was originally in the ROM.
Click to expand...
Click to collapse
Okay thanks for the replies.
Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
Even the .IMG files are easy enough to handle, OK so perhaps it might cost you a little money but within the Franco app (I don't know about others as not tried them) but you can simply just choose to restore a .IMG kernel file be it stock (which I have a copy of if you wanted it?) So you can swap and change as you wanted and the plus side of flashing this way is that you avoid the long reboot time dues to catch building again due to ram disk changes. I really think this is the best way of flashing kernels and certainly the easiest way if you wanted to carry on back to the OTA update route from Google.
For instance, I'm running stock takju rom 4.2.1 rom with Franco kernel and I have the stock boot loader and baseband and recovery and to install an OTA I just need to delete just one file and restore back to stock kernel that OTA update will install without troubles
Sent from my Galaxy Nexus