Hello, can any of you tell me how to remove bootloader and kernel from a ROM before installing it?
It's a long story, but I need to make that happen somehow.
I have ROMs in ZIP and the .md5 formats. Thanks!!
Related
i am not overly familiar with many things regarding different kernels and how to work with them, so i was wishing a few questions that i had could be clarified by someone who knows:
1. when a kernel is flashed? i mean except for the times when we flash kernel.zips via recovery, is it flashed whenever we install a custom rom? or is it flashed with bootloaders when we flash firmware?
2. I am using CM12 official nightly and facing camera frizz issues. I came across a post in the official CM12 thread where they said flashing a modified kernel supposedly fixed this problem. Now my question is, after flashing a custom kernel, is there any way to go back to the stock one? by stock i mean either the one i was on right before flashing the custom kernel or stock moto g kernel provided by motorola?
that also begets the question, can kernels be backed up like roms using recovery?
gearguy365 said:
i am not overly familiar with many things regarding different kernels and how to work with them, so i was wishing a few questions that i had could be clarified by someone who knows:
1. when a kernel is flashed? i mean except for the times when we flash kernel.zips via recovery, is it flashed whenever we install a custom rom? or is it flashed with bootloaders when we flash firmware?
2. I am using CM12 official nightly and facing camera frizz issues. I came across a post in the official CM12 thread where they said flashing a modified kernel supposedly fixed this problem. Now my question is, after flashing a custom kernel, is there any way to go back to the stock one? by stock i mean either the one i was on right before flashing the custom kernel or stock moto g kernel provided by motorola?
that also begets the question, can kernels be backed up like roms using recovery?
Click to expand...
Click to collapse
1. The kernel is first flashed when you install a ROM. You are supposed to flash a custom kernel after flashing a ROM otherwise the rom zip will overwrite it. It doesn't matter if you install it in the recovery or the boot loader.
2. To go back to the stock kernel just take it from the zip of the ROM and flash in the bootloader
where can i find the kernel inside the rom zip?
and if i want the stock motorola kernel that comes with factory firmwares
how can i collect that?
A ROM.zip contains the system folder and a boot.img
The kernel is in the boot.img
So if u flash a different kernel and still facing problems then flash the ROM again.
mistercheese said:
A ROM.zip contains the system folder and a boot.img
The kernel is in the boot.img
So if u flash a different kernel and still facing problems then flash the ROM again.
Click to expand...
Click to collapse
flashing only the boot.img of a rom wont bring back the default kernel?
and is there any way to make a flashable zip of a kernel from that particualr boot.img?cause all the kernels i see (like donkey kang/customized cm12 kernel) there are all distributed in .zip format.....
I have kernel 3.0.101 and AOSP 6.0.1 ROM from GHsR in my GT-I9105P, TWRP 2.8.40 and locked bootloader. So, how I can unlock bootloader and flash custom kernel without data loss (factory reset)? I can without factory-reset flash custom kernel? What newest kernel flash? I new at that, so please put your tutorials step-by-step.
There aren't custom kernels on 6.0.x ROMs, it's so difficult making a good kernel and need a lot of time and knowledge for making one good. Then, if anyone would create a group that have some knowledge for editing the kernel then we can have custom kernels, otherwise, we must keep the stock with some things putted in it. The bootloader is everytime unlocked because you can go to the recovery everytime and you can do what the recovery can do...
matteo0026 said:
There aren't custom kernels on 6.0.x ROMs, it's so difficult making a good kernel and need a lot of time and knowledge for making one good. Then, if anyone would create a group that have some knowledge for editing the kernel then we can have custom kernels, otherwise, we must keep the stock with some things putted in it. The bootloader is everytime unlocked because you can go to the recovery everytime and you can do what the recovery can do...
Click to expand...
Click to collapse
OK, thanks. Theard end
I have build a flashable rom from stock firmware 6.0.1 (merlin) with android kitchen but i don't have the knowledge how to make update-script for flashing with TWRP... Can someone plz make a update-script for me so that i can flash that stock firmware with TWRP.
Please....
amritmalviya said:
I have build a flashable rom from stock firmware 6.0.1 (merlin) with android kitchen but i don't have the knowledge how to make update-script for flashing with TWRP... Can someone plz make a update-script for me so that i can flash that stock firmware with TWRP.
Please....
Click to expand...
Click to collapse
if you have ant custom rom (say lineage OS for merlin), take the meta-inf folder from there. i would give but mine is from osprey, it should be same but dont want to take any risk that can brick your device
Rohi09 said:
if you have ant custom rom (say lineage OS for merlin), take the meta-inf folder from there. i would give but mine is from osprey, it should be same but dont want to take any risk that can brick your device
Click to expand...
Click to collapse
I already extract one from lineage os (merlin) and ised it in stock rom and tried to flash with twrp but it gives me error code 6, i have not much knowledge how to edit a updater script, if you can help me it would be very grateful to me, i will definitely hit that thumb's up button..
Evening everybody. I had to do a recovery to unbrick my phone and I am now on the above build. Now I cannot install a custom build Nouget ROM as it will not allow me. I have twrp installed and unlocked but will not let me install anything else. Can anyone help and advise what I can do to fix this please. Cheers Freddy
Chose one of the signed flashable zips from here : https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
These are stock ROMs
And just flash from twrp. Once you are done you are in a "stable condition" and you'll be able to flash whatever you want.
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.