Hey guys,
I'm just curious and actually quite new to the "sideload-ing" thing and ADB. So, I was wondering if it was possible to sideload a stock ROM when on a custom ROM? or do you just use the CWM recovery to flash the stock ROM? or by using Odin?
Hi,
Dudes I know some advantages of custom recoveries over stock recovery. It gives u freedom to flash any custom zip. I have a doubt, what if a stock software update zip is flashed with custom recoveries?. Can it be successfully flashed ??? If not, then what error will be thrown ???
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.....
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.
I want a custom ROM and I'm wondering if its possible or if it will brick.
I'm going to guess no because there's no way to install a custom recovery which you'd need to install the rom.
Firstly, there don't seem to be any custom roms compatible with fit US Snapdragon variants. Secondly, we don't have a custom recovery but we could use Flashfire. So no, you can't flash a custom rom because there aren't any compatible yet.