Database Users

[REQ] Stock Kernel 2.3.4

can anybody deliver the stock 2.3.4 kernel as an image to reflash via recovery if one wants to go back from a custom kernel?
would be easier, than using an old backup or reflash the whole ROM due to lost data, apps, sms, etc.

Second to that....maybe someone can help us.
Best Regards

Third to that! Want to try custom kernel, but don't want reflash whole image, if I'll not like it.

evlevl said:
Third to that! Want to try custom kernel, but don't want reflash whole image, if I'll not like it.
Click to expand...
Click to collapse
do a nandroid backup. it saves kernels

Flashing back stock kernel will not allways help , because some other alterations (e.g. in intit.d) will still remain .. But if you want the stock 2.3.4 kernel .. you can download the full rom posted by me or given in an other thread .. set a side the boot.img and flash it with fastboot ( fastboot flash boot boot.img)
If you do not want to download load an entire rom I attached the stcok 2.3.4 kernel .

Bandis710 said:
Flashing back stock kernel will not allways help , because some other alterations (e.g. in intit.d) will still remain .. But if you want the stock 2.3.4 kernel .. you can download the full rom posted by me or given in an other thread .. set a side the boot.img and flash it with fastboot ( fastboot flash boot boot.img)
If you do not want to download load an entire rom I attached the stcok 2.3.4 kernel .
Click to expand...
Click to collapse
excellent, thanx mate! i don't want to flash a whole rom just to get back on stock kernel, because all the backing up and restoring if not necessary is boring...
and does that really set back all changes, a custom kernel does on my phone? aren't there also always some folders in the zip-files of customs?

Well, now I see a reason why there is no "default kernel".
It's because all these custom kernels consist not only from "boot.img", but also from a number of "init.d scripts", "*.so modules", etc, which are obviously different from kernel to kernel. So because of that you cannot have an universal "stock" kernel, but rather a whole stock ROM.
Thanks a lot for all of you who comment that request, now the situation with kernels is more clear.

While all the above is sensible, it should be possible with a modicum of planning to go back and forth between a custom kernel and the stock one. I feel the question is more: is it worth the trouble versus flashing again? Probably not.
1 - Nandroid backup.
2 - Examine the scripts and files included in the custom kernel's zip.
3 - Back up what is replaced, patched or deleted outright from stock.
4 - Note what is added by the custom kernel.
When you want to revert to stock, reflash boot.img from stock, and either adb push the stock backup files back, or create your own update zip with a proper script to finish the job.

[GUIDE][18th Dec][4Noobs] Flashing a Custom Rom & Kernel Using Fastboot

Installing Custom Rom and Custom Kernel
Pre-Requisites
Download Any Custom Rom For Your Device From XDA.
Download Any Custom Kernel For Your Device.
Have a device with a unlocked bootloader.
Download this fastboot package.
We will refer to the downloaded custom kernel as [highlight]CKernel[/highlight] and the Custom Rom as [highlight]CRom[/highlight].
Flashing the Custom Kernel
Copy the [highlight]CROM.zip[/highlight] file to your sd card
Extract the Fastboot package to a folder and copy the [highlight]CKernel.img[/highlight] file to the same location.
Shift + Right Click the folder and press "Open Command Window Here".
Reboot your phone in to fastboot (Press search and connect USB cable , may be different for some 2011 devices).
Blue LED should be switched on. This means your in fastboot. Now you need to type.
Code:
fastboot flash boot CKernel.img
After a few seconds it should be done and say "Completed" or something similiar.
Installing A Custom Rom
Reboot your phone in to recovery (Keep Tapping Vol Down or Back or Another key when device is booting).
Format the phone "Factory Reset".
Next press "Install Any Zip From SD Card".
Select the [highlight]CRom.zip[/highlight] file that we copied over earlier and press yes/accept/apply.
After a few minutes it should be done and say "Installed or Applied or Success".
Now reboot your phone and wait patiently.
If everything is done correctly then you should now be running your [highlight]CRom [/highlight]​e.g. AOKP, CM, MIUI, Etc.
Installing Google Apps (may not be needed depending on the ROM)
Download the latest google apps that corresponds with your android version from goo.im/gapps.
Copy the download zip to your SD Card.
Reboot your phone in to recovery (Press the button you pressed earlier while phone is at the logo again).
Next press "Install Any Zip From SD Card".
Select the GoogleApps*.zip or GApps.*.zip file and press yes.
After a few minutes it should be done and say "Installed or Applied or Success".
Now reboot your phone and wait patiently.
You now should be running your custom kernel, custom rom and have the latest gapps installed.
[no longer linking tutorials to my site as currently messing around with my site so links may break, to prevent this i will post them here since i found a html to vbcode converter aswell ]

Thanks... But you need to change
Copy the CKernel.zip file to your sd card
Click to expand...
Click to collapse
to
Copy the CRom.zip file to your sd card

Could you please include an example?
Because Lupus Kernel + Cyanogenmod doesn't work for me.
Error Status 7 (tried both latest 7 and 9)
Lupus recovery itself works(and since it still boots i guess so does the kernel itself), but flashing Cyanogenmod doesn't.

What lupus kernel are you using? If youre using lups v8 then choose aosp ics under boot menu of whatever slot your using. If your using lupus v10 or lupus ics/gb those dont work with cm9 so those could be your problems
Sent from my Xperia Play (r800x)

LuPuS_zeus_ICS-GB_v3-ram(2) is the one i'm using.
I got it from here: http://forum.xda-developers.com/showthread.php?p=38988056
and choose it because it was the only still supported one for android 4 without beta in the name.
So i have no idea.
btw: cm7 doesn't work either, same error.

Beta means it supports the stock ics beta rom not the kenels a beta. Lol use lupus jb v8 or turbo kernel 3.1. Both support cm9. You just have to choose it under rom type when going into recovery
Sent from my Xperia Play (r800x)

turbo: can't use it because it requires the flashtool that doesn't work
v8: tested, nice but unusable with cm9 because of graphic glitch and doesn't find the sd card (and bootloop + graphic glitch with CM7)
ALso another problem:
The phone doesn't enter fastboot anymore, lupus goes into recovery instead...

543563465643534 said:
turbo: can't use it because it requires the flashtool that doesn't work
v8: tested, nice but unusable with cm9 because of graphic glitch and doesn't find the sd card (and bootloop + graphic glitch with CM7)
ALso another problem:
The phone doesn't enter fastboot anymore, lupus goes into recovery instead...
Click to expand...
Click to collapse
Try the fxp kernel. Just extract it from the rom zip and flash. Also to get the kernel to stop booting remove the battery and wait 30 seconds. Then put it back and quickly enter fastboot by plugging in and holding search button.
Sent from my Xperia Play (r800x)

Since when does turbo kernel REQUIRE flashtool?
Sent from my R800i using Tapatalk 2

@fma965
this guide:
http://forum.xda-developers.com/showthread.php?t=1817548
Step 1 GSM (Germany)
requires an ftf file which i thought requires the flashtool for using.
@abdel12345
Freexperia?
Is it the boot.img?
I'm new to this flashing thing, last time i did it(on my magic) there was just the romand no manual Kernel messing.
btw, fastboot works now, seemed to be a problem with the cheap micro USB cable. I also really appreciate your help, thank you guys.
Everything works now with CM9 and FXP Kernel!

543563465643534 said:
@fma965
this guide:
http://forum.xda-developers.com/showthread.php?t=1817548
Step 1 GSM (Germany)
requires an ftf file which i thought requires the flashtool for using.
@abdel12345
Freexperia?
Is it the boot.img?
I'm new to this flashing thing, last time i did it(on my magic) there was just the romand no manual Kernel messing.
btw, fastboot works now, seemed to be a problem with the cheap micro USB cable. I also really appreciate your help, thank you guys.
Everything works now with CM9 and FXP Kernel!
Click to expand...
Click to collapse
Wrong link? that is turbo kernel thread and no mention of "Germany" ???
Yh the boot.img, Recovery is on the kernel partition so you can't flash a kernel from the recovery aka the kernel partition, i think this is correct??? if not then any 1 feel free to correct me

That's correct, but Germany is one of the countries using "GSM" not "CDMA", that's what i meant.
But thanks for the help and the short guide(but is still think a total newb tutorial should include an example if 2 or more components are needed).

Thank You. This worked for me today.

[Q] Backup Kernel How To question

Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,

youpiyo said:
Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,
Click to expand...
Click to collapse
What type of ROM are you using? You have to be using a compatible kernel. AOSP ROM's won't work with a stock kernel, and you can't cross Android version between system and kernel. Using any custom kernel developed for your phone with this guide will work okay however.

Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?

youpiyo said:
Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?
Click to expand...
Click to collapse
My best guess is find out which partition it is and use the dd command OR download the ODIN of your firmware version and extract the boot.img. However, it would be easier to just use a custom kernel designed for your phone as if you back it up like that you either have to make it into a flashable zip or use heimdall to restore it every time.
Sent from Black<3's I337 running Foxhound ROM

Thanks for your answer.
That's weird as a nandroid is doing the job,that is hard to find how to backup a kernel.
anyway, I guess my best chance is to download a custom kernel and apply it after installation of the cutom rom. At first boot re apply a backup kernel with an app as flashify.
thanks youpi

Not able to Flash any kernel

Im facing a weird issue.
Not able to flash any new kernel.
Im rooted, Xposed on stock ROM with TWRP 2.8.7.0 recovery.
Flashing the Kernel through TWRP says success, however when I go to my phone settings I get the kernel number of stock Kernel - attached file shows this
Also notification LED etc not working as in Squid's kernel. How else can I find out whether the kernel is flashed or not?
And if not then why am I not able to flash it?

Post here a copy of "/cache/recovery/last_log" file, of course you're still on stock kernel.

dhruvwali said:
Im facing a weird issue.
Not able to flash any new kernel.
Im rooted, Xposed on stock ROM with TWRP 2.8.7.0 recovery.
Flashing the Kernel through TWRP says success, however when I go to my phone settings I get the kernel number of stock Kernel - attached file shows this
Also notification LED etc not working as in Squid's kernel. How else can I find out whether the kernel is flashed or not?
And if not then why am I not able to flash it?
Click to expand...
Click to collapse
yup faced this issue many times
just use flashify app from play store and see if that works ! (worked for me )

Found the issue, was using the earleir version of TWRP, 2.8.7, not the latest 2.8.7.0_v2. As soon as I flashed that the kernel flashing got fixed.

[help] flashing stock kernel back

Hi, i have a moto g4 plus XT1644 U.S Model. I flashed lineage os 14.1 with elemental x kernel. I'd like to know how to flash back the original kernel on this device since i can't find any "understandable" guide. From what i understood i have to go back to the stock nougat rom and then i'd be fine...? Thanks in advance!

Prowy333 said:
Hi, i have a moto g4 plus XT1644 U.S Model. I flashed lineage os 14.1 with elemental x kernel. I'd like to know how to flash back the original kernel on this device since i can't find any "understandable" guide. From what i understood i have to go back to the stock nougat rom and then i'd be fine...? Thanks in advance!
Click to expand...
Click to collapse
By original kernel, do you mean the kernel that came with LineageOS or are you referring to the kernel that came with the Motorola stock ROMs?
If you mean flashing the kernel that came with LineageOS, you can extract the boot.img from the LineageOS zip you flashed with, which is the LineageOS kernel - a good file manager app (e.g. Amaze) should allow you to view the zip file (no need to extract the whole zip file) and extract the boot.img to your Downloads folder. Ideally, perform this extraction step on your device to minimise the chances of corruption (hopefully TWRP would stop a corrupted image being flashed!)
Then:
Reboot to TWRP recovery.
Backup your existing system, just in case anything happens.
Head back up to Install, press Install.
Tap 'Install Image'
Navigate to the boot.img that you extracted from the LineageOS zip (e.g. in your Downloads folder).
Select 'boot' as the target partition.
Wait for your new kernel to flash.
Tap on the back button and head to 'Wipe'
Wipe cache and Dalvik
Reboot.
If anything happens, you can reboot to your TWRP recovery and restore the backup you made. For future reference, if you flash a ROM, back up your boot.img (which contains your kernel) before flashing a new kernel on top. That way, you have an existing copy of your original kernel ready to revert back to.
If you want to revert back to your stock, Motorola, kernel, then your best bet is to flash the whole stock ROM, so you'll have a stock system. I would not recommend flashing a stock kernel onto a custom ROM (custom kernels, like ElementalX, are okay on stock ROMs, but check the custom kernel first). For the latest Nougat stock ROM, here's the fastboot ROM https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 but be aware this will replace your custom ROM with the stock ROM, stock recovery and stock kernel. TWRP and root and any modifications on your custom ROM will be erased and your data may be wiped too. Back up accordingly and it may be worth moving your data off your device as a precaution.
Any more questions, please ask/research before you perform anything. Good luck either way.

echo92 said:
By original kernel, do you mean the kernel that came with LineageOS or are you referring to the kernel that came with the Motorola stock ROMs?
If you mean flashing the kernel that came with LineageOS, you can extract the boot.img from the LineageOS zip you flashed with, which is the LineageOS kernel - a good file manager app (e.g. Amaze) should allow you to view the zip file (no need to extract the whole zip file) and extract the boot.img to your Downloads folder. Ideally, perform this extraction step on your device to minimise the chances of corruption (hopefully TWRP would stop a corrupted image being flashed!)
Then:
Reboot to TWRP recovery.
Backup your existing system, just in case anything happens.
Head back up to Install, press Install.
Tap 'Install Image'
Navigate to the boot.img that you extracted from the LineageOS zip (e.g. in your Downloads folder).
Select 'boot' as the target partition.
Wait for your new kernel to flash.
Tap on the back button and head to 'Wipe'
Wipe cache and Dalvik
Reboot.
If anything happens, you can reboot to your TWRP recovery and restore the backup you made. For future reference, if you flash a ROM, back up your boot.img (which contains your kernel) before flashing a new kernel on top. That way, you have an existing copy of your original kernel ready to revert back to.
If you want to revert back to your stock, Motorola, kernel, then your best bet is to flash the whole stock ROM, so you'll have a stock system. I would not recommend flashing a stock kernel onto a custom ROM (custom kernels, like ElementalX, are okay on stock ROMs, but check the custom kernel first). For the latest Nougat stock ROM, here's the fastboot ROM https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 but be aware this will replace your custom ROM with the stock ROM, stock recovery and stock kernel. TWRP and root and any modifications on your custom ROM will be erased and your data may be wiped too. Back up accordingly and it may be worth moving your data off your device as a precaution.
Any more questions, please ask/research before you perform anything. Good luck either way.
Click to expand...
Click to collapse
Thank you so much, it's ok if i lose all my data,twrp by flashing the stock rom via dab. I just wanted to be sure that i would go back to the stock kernel as well (If i'll ever have problems with the EX Kernel).
Do you think EX kernel would give my device better battery life?

Prowy333 said:
Thank you so much, it's ok if i lose all my data,twrp by flashing the stock rom via dab. I just wanted to be sure that i would go back to the stock kernel as well (If i'll ever have problems with the EX Kernel).
Do you think EX kernel would give my device better battery life?
Click to expand...
Click to collapse
with ex kernel you have the option to underclock your device. you may want to try it if you are interested in saving battery!

Ayan Uchiha Choudhury said:
with ex kernel you have the option to underclock your device. you may want to try it if you are interested in saving battery!
Click to expand...
Click to collapse
What's the recommended values for our moto g4 plus?

while flashing ex kernel you'll see 4 values of frequency. choosing any one of them will suffice. I would not recommend going for other values.
hit the thanks button if it helped!

Ayan Uchiha Choudhury said:
while flashing ex kernel you'll see 4 values of frequency. choosing any one of them will suffice. I would not recommend going for other values.
hit the thanks button if it helped!
Click to expand...
Click to collapse
Didn't know that, i 'll give it a try thanks!

Not booting up
I did as it is said above and the stock booted fine.
there was a software update and after installing it, the phone isn't booting up.
Please help, thank you in advance
ps i had element x kernel before relocking