I'm running latest L preview (rooted, custom kernel), multiROM.
1. I flashed LRX21O flashable (NOT this one , can't find that one ) as a secondary ROM . It booted up properly etc but it didn't give me any option to restore my previous apps. I tried doing factory reset, reflashed. It didn't help. Is there any way to force it?
2. How do I upgrade my recovery from android L without using pc? (flashify doesn't work on L so I can't flash .img files without PC)?
3. Is it neccesary to flash new radios?
3.1. How do I flash radios if I want to keep my multiROM and L preview as my primary ROM until I move everything to 5.0 final (I am planning to have both ROMs on my phone for a few days until everything is really configured because I don't like it when I find something missing on my new ROM that I just had on a ROM that I just deleted)?
(I have quite fast internet so it is not a problem to download these flashable zips)
Thank you for your time
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.
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.
I have an OnePlus5 with latest Oxygen Os android 7.1.1, rooted with magisk and with TWRP recovery. I flashed yesterday a custom kernel (blu spark), cause i wanted better battery stats. But i dont see any changes. Nor more advanced options, neither visual changes. What does exactly a kernel change to the phone? How does it differ from a custom rom? Do i need extra programs or programming in order to make full use of the kernel?
Now that i have the custom kernel, what actions should i take if :
1) I want install a custom rom
2) I want install stock rom
3) I want install another or stock kernel
When should i take full backup and why? (Nandroid via TWRP or backup with TITANIUM BACKUP??) What about OTA updates? How can i update to newest rom in each case? Each time a new rom update occurs should i take full backup, flash the rom and install them all from the start??
Someone help me please?
Sent from my ONEPLUS A5000 using Tapatalk