I want to play with flashing the unofficial CM11 kernel onto different roms. How do you extract the CM11 Kernel from CM11 roms and flash to another rom? I've read in years past you can take things out of the rom zip file and throw it into a different zip and flash.
Thanks!
Extract the ROM zip and take out the boot.img. This is the kernel. It can be flashed via fastboot or flashify.
Sent using xda-developers app
Hi all,
Since a few days I'm trying to update my Nexus 5 to Android 4.4.4 but everything I've tryed has failed !
Today I'm running stock ROM 4.4.2 + root + TWRP recovery + Xposed
What I've tryed :
_ OTA : device reboot on recovery and does nothing
_ Flash stock using the latest Nexus Rom Toolkit from Wug Refresh : device reboot on bootloader and get stuck on a "downloading..." message while PC get stuck on "downloading bootloader"
_ Flash zip from TWRP : tryed several zip, all of them has failed
I don't know what to do next, so now I'm asking your help...
Also I hope this post is in the right section !
Download vomer's stock rooted 4.4.4 rom from the development section and dirty flash it from custom recovery. This should do the job.
You can find the mentioned rooted stock in my signature, section 6.6
Sent from my Nexus 5 using Tapatalk
Before trying this custom ROM could you explain me the difference with the stock ROM and why I cannot flash the stock one ?
Is it because I have Xposed or something ?
And also after flashing the custom by vomer, can I try to flash again the stock one ?
3RR0R404 said:
Before trying this custom ROM could you explain me the difference with the stock ROM and why I cannot flash the stock one ?
Is it because I have Xposed or something ?
And also after flashing the custom by vomer, can I try to flash again the stock one ?
Click to expand...
Click to collapse
The One which we are telling you to flash is the stock rom. Yes, it's because you have Xposed and other modules installed.. God knows what changes it has made to system.
There's no need to flash the factory images again as vomer's thread contains the stock itself.
- Sent from an IceCold Hammerhead!
3RR0R404 said:
Before trying this custom ROM could you explain me the difference with the stock ROM and why I cannot flash the stock one ?
Is it because I have Xposed or something ?
And also after flashing the custom by vomer, can I try to flash again the stock one ?
Click to expand...
Click to collapse
All of your questions have already been answered, except the Vomer ROM one. While technically a custom ROM, it is only stock ROM with root. So going back to pure stock would be pointless.
Edit: ninja by @vin4yak
I have come from a nexus and an htc drvice. When I flash a rom for the g3...does it also flash the kernel with it? Does it flash firmware as well? With htc devices....there were specific firmwares that were compatible with only aosp roms and some with the manufacture skin.
Just need to know if the rom zip flashes everything to make the rom work correctly...or if there are additional steps.
thanks
So the situation currently is that I have flashed CM 13 to my Galaxy S4 Mini and I also flashed a custom kernel (from a different person) after. I am experiencing some multi-touch issues when using the antutu multitouch test. I wanted to see if it was the kernel that was causing it and if the stock kernel would fix the issue, however, to do this I need the original stock CM 13 kernel but I don't know where I can find the zip file to flash it. Can anyone help out?
Please and thanks!!
EDIT: Never mind I've figured it out. If anyone is in the same boat, simply extract the boot.img from your CM13 ROM zip file (this is the image file which contains the respective kernel) and use Flashify (requires root) to flash your stock CM13 kernel that you just extracted from your ROM zip file.
Hello everybody! I have a problem: I wanted to install custom ROM via Safestrap 3.71. I made all the wipe. But at the end of the installation, I get an error: set_metadata_recursive some changes failed. And so in each ROM. After that, ROM does not load: black screen after the logo Samung Custom. How to deal with this?
[R]ainbow[D]ash said:
Hello everybody! I have a problem: I wanted to install custom ROM via Safestrap 3.71. I made all the wipe. But at the end of the installation, I get an error: set_metadata_recursive some changes failed. And so in each ROM. After that, ROM does not load: black screen after the logo Samung Custom. How to deal with this?
Click to expand...
Click to collapse
Was it a true custom ROM? Or was it a modified stock ROM?
If it was a custom ROM such as Cyanogenmod or LineageOS, that's the problem.
Safestrap is intended to be used with modified stock ROMs that are based on stock kernel, not CM, AOSP or Lineage based ROMs.
Typically, Safestrap is used on devices with locked bootloader, these devices can't use CM, AOSP or Lineage based ROMs, these ROMs are built to be flashed via custom recovery such as TWRP.
If you have an unlocked bootloader and you want to use custom ROMs then you'll have to flash TWRP then use TWRP to flash the ROM.
If your device does not have an unlocked bootloader but you want to use Safestrap then you need to install TouchWiz(TW)/stock based ROMs.
There is a difference.
Also, when using Safestrap, you have to leave the stock rom in one slot and place the new ROM in a different slot. You can't overwrite the existing stock ROM with the new ROM, that causes issues and the device won't boot.
You will probably have to flash your stock firmware via Odin and start over with root and flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Was it a true custom ROM? Or was it a modified stock ROM?
If it was a custom ROM such as Cyanogenmod or LineageOS, that's the problem.
Safestrap is intended to be used with modified stock ROMs that are based on stock kernel, not CM, AOSP or Lineage based ROMs.
Typically, Safestrap is used on devices with locked bootloader, these devices can't use CM, AOSP or Lineage based ROMs, these ROMs are built to be flashed via custom recovery such as TWRP.
If you have an unlocked bootloader and you want to use custom ROMs then you'll have to flash TWRP then use TWRP to flash the ROM.
If your device does not have an unlocked bootloader but you want to use Safestrap then you need to install TouchWiz(TW)/stock based ROMs.
There is a difference.
Also, when using Safestrap, you have to leave the stock rom in one slot and place the new ROM in a different slot. You can't overwrite the existing stock ROM with the new ROM, that causes issues and the device won't boot.
You will probably have to flash your stock firmware via Odin and start over with root and flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I was flashing the modified ROM on the stock kernel. I put in the recovery on slot-rom1. I tried to flash: CarHD, KushanROM, GOLDENEYE and Omega. And still it does not work out
[R]ainbow[D]ash said:
I was flashing the modified ROM on the stock kernel. I put in the recovery on slot-rom1. I tried to flash: CarHD, KushanROM, GOLDENEYE and Omega. And still it does not work out
Click to expand...
Click to collapse
Do you still have your original stock ROM in one of the slots? Or did you overwrite it? If you overwrite it, you messed up. As stated earlier, you'll probably have to flash the original stock firmware via Odin.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Do you still have your original stock ROM in one of the slots? Or did you overwrite it? If you overwrite it, you messed up. As stated earlier, you'll probably have to flash the original stock firmware via Odin.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
The stock slot remained intact. But if I take the kernel from OC3, then the device will also not boot up and the recovery will become non-working.
Send me the stock ROM for flashed the custom ROM through the Safestrap. And send me the version of the Safestrap for custom ROM
I understood what the problem is. I installed another ROM NB1 and it all worked for me.