Is BluSpark kernel compatible with Hydrogen OS/H2OS? - OnePlus X Q&A, Help & Troubleshooting

I have a very tight schedule, so I couldn't ttry it myself as I use my phone as a daily-driver. Thank you in advacne!

backup in TWRP > try > restore backup or use the kernel
But the OOS version should work

yes it works with hydrogen os,use oos version

Related

[Q] CM11 and twrp?

I want to install CM11 on my M7, but I don't know if CM works with TWRP. The TWRP version is 2.6.3.3. Can I use TWRP, and if I can, do I have to update it?
mrchris814 said:
I want to install CM11 on my M7, but I don't know if CM works with TWRP. The TWRP version is 2.6.3.3. Can I use TWRP, and if I can, do I have to update it?
Click to expand...
Click to collapse
The best thing would be to read carefully the OP of the rom you want to flash. CM has special requirements and you should use the newer TWRP 2.8.0.1; the Port of OnePlus One requires a special TWRP! In any case make sure you make a nandroid backup of your current setup and save it to your computer before flashing the new rom!

[ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates

As OnePlus don't provide download links for all of for their Oxygen OS ROMs & OTA update zips, I've mirrored them on AndroidFileHost and put the links in one post so that they're easy to find.
This is not a support thread for issues you may have with Oxygen OS roms. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread.
There are two types of file for each ROM: signed flashable zips and OTA incremental update zips.
Signed flashable zips: These are recovery-flashable zips of the full ROM that won't overwrite your data partition. They can be flashed via stock or TWRP recovery.
OTA incremental update zips: These are recovery-flashable zips that update your rom to a newer version. They can be flashed via stock or TWRP recovery but will only work on non-rooted devices with no modifications to system files.
I've also included links for TWRP custom recovery and SuperSU
Magisk is also reported to be working with OOS 3.6.0+
NOTE: If you're using XDA Labs, the download links may not work - use a web browser
Signed flashable zips
Oxygen OS 3.6.1: OnePlus2Oxygen_14_OTA_032_all_1710240102.zip
Oxygen OS 3.6.0: OnePlus2Oxygen_14_OTA_031_all_1706262034.zip
Oxygen OS 3.5.9: OnePlus2Oxygen_14_OTA_030_all_1704191749.zip (VoLTE fix)
Oxygen OS 3.5.8: OnePlus2Oxygen_14_OTA_029_all_1703131134.zip
Oxygen OS 3.5.7: OnePlus2Oxygen_14_OTA_028_all_1701052113.zip (Fix for lost IMEI)
Oxygen OS 3.5.6: OnePlus2Oxygen_14_OTA_027_all_1612271635.zip
Oxygen OS 3.5.5: OnePlus2Oxygen_14_OTA_026_all_1612220228.zip
Oxygen OS 3.1.1: OnePlus2Oxygen_14_OTA_021_all_1610121102_wipe.zip
Oxygen OS 3.1.0: OnePlus2Oxygen_14_OTA_020_all_1608262242.zip
Oxygen OS 3.0.2: OnePlus2Oxygen_14_OTA_019_all_1606041303.zip
Oxygen OS 3.0.1 Beta2: OnePlus2Oxygen_14_OTA_018_all_1605231631_OpenBeta2.zip
Oxygen OS 3.0 Beta: OnePlus2Oxygen_3.0_beta_bb10c034d8a4466d.zip
Oxygen OS 2.2.1-2: OnePlus2Oxygen_14_OTA_013_all_1604202136.zip
Oxygen OS 2.2.1: OnePlus2Oxygen_14_OTA_012_all_1602261837.zip
Oxygen OS 2.2.0: OnePlus2Oxygen_14_OTA_011_all_1512111634.zip
Oxygen OS 2.1.2: OnePlus2Oxygen_14_OTA_010_all_1511091726.zip
Oxygen OS 2.1.1: OnePlus2Oxygen_14_OTA_009_all_1510112055.zip
Oxygen OS 2.1: OnePlus2Oxygen_14_OTA_008_all_1509191929.zip
Oxygen OS 2.0.2: OnePlus2Oxygen_14_OTA_006_all_1508211811.zip
Oxygen OS 2.0.1: OnePlus2Oxygen_14_OTA_005_all_1508192013.zip
Oxygen OS 2.0: OnePlus2Oxygen_14_OTA_002_all_1507251956_wipe.zip
OTA incremental update zips
Oxygen OS 3.6.0 > Oxygen OS 3.6.1: OnePlus2Oxygen_14_OTA_031-032_patch_1710240102.zip
Oxygen OS 3.5.9 > Oxygen OS 3.6.0: OnePlus2Oxygen_14_OTA_030-031_patch_1706262034.zip
Oxygen OS 3.5.8 > Oxygen OS 3.6.0: OnePlus2Oxygen_14_OTA_029-031_patch_1706262034.zip
Oxygen OS 3.5.6 > Oxygen OS 3.5.8: OnePlus2Oxygen_14_OTA_027-029_patch_1703131134.zip
Oxygen OS 3.5.7 > Oxygen OS 3.5.8: OnePlus2Oxygen_14_OTA_028-029_patch_1703131134.zip
Oxygen OS 3.5.6 > Oxygen OS 3.5.7: OnePlus2Oxygen_14_OTA_027-028_patch_1701052113.zip (Fix for lost IMEI)
Oxygen OS 3.5.5 > Oxygen OS 3.5.6: OnePlus2Oxygen_14_OTA_026-027_patch_1612271635.zip
Oxygen OS 3.0.2 > Oxygen OS 3.1.0: OnePlus2Oxygen_14_OTA_019-020_patch_1608262242.zip
Oxygen OS 3.0.1 > Oxygen OS 3.0.2: OnePlus2Oxygen_14_OTA_018-019_patch_1606041303.zip
Oxygen OS 3.0 > Oxygen OS 3.0.2: OnePlus2Oxygen_14_OTA_017-019_patch_1606041303.zip
--------------------------------------------------------------------------------------------
Hotfix update for users with Deutsche Telekom & Congstar SIMs
Oxygen OS 2.2.1 > Oxygen OS 2.2.1-2 : OnePlus2Oxygen_14_OTA_012-013_patch_1604202136.zip
--------------------------------------------------------------------------------------------
Oxygen OS 2.2.0 > Oxygen OS 2.2.1: OnePlus2Oxygen_14_OTA_011-012_patch_1602261837.zip
Oxygen OS 2.1.2 > Oxygen OS 2.2.0: OnePlus2Oxygen_14_OTA_010-011_patch_1512111634.zip
Oxygen OS 2.1.1 > Oxygen OS 2.2.1: OnePlus2Oxygen_14_OTA_009-012_patch_1602261837.zip
Oxygen OS 2.1.1 > Oxygen OS 2.1.2: OnePlus2Oxygen_14_OTA_009-010_patch_1511091726.zip
Oxygen OS 2.1 > Oxygen OS 2.1.1: OnePlus2Oxygen_14_OTA_008-009_patch_1510112055.zip
Oxygen OS 2.0.2 > Oxygen OS 2.1: OnePlus2Oxygen_14_OTA_006-008_patch_1509191929.zip
Oxygen OS 2.0.1 > Oxygen OS 2.0.2: OnePlus2Oxygen_14_OTA_005-006_patch_1508211811.zip
Oxygen OS 2.0 > Oxygen OS 2.0.1: OnePlus2Oxygen_14_OTA_002-005_patch_1508192013.zip
TWRP & SuperSU
Oxygen OS 3
Official TWRP custom recovery
Modified SuperSU v2.82 TWRP flashable zip
Modified SuperSU v2.79 TWRP flashable zip
Modified SuperSU v2.76 TWRP flashable zip (Last Chainfire release)
Oxygen OS 2
Official TWRP custom recovery
Latest stable SuperSU
Unofficial Oxygen OS fastboot zips
These contain the complete rom and can overwrite everything including your data partition. These cannot be flashed via recovery - extract their contents and flash via fastboot. Along with the factory images, these contain flash-all bat scripts for fastboot flashing on both the 64GB & 16GB variants.
Using the flash-all bat file will revert your rom to fully stock Oxygen OS and will wipe your data partition (including userdata) and replace any custom recovery with stock. If you wish to keep your custom recovery and/or data, add "REM " (without the quotes) in front of the relevant lines in the bat file before running it. Alternatively, you can just enter each line from the bat file manually in a command window.
Note: The fastboot zips have been updated with new flash-all bat files that now flash the backup partitions too.
Oxygen OS 3.0.2: OnePlus2Oxygen_14_OTA_019_all_1606041303_fastboot.zip
Oxygen OS 2.2.0: OnePlus2Oxygen_14_OTA_011_all_1512111634_fastboot.zip
Oxygen OS 2.1.1: OnePlus2Oxygen_14_OTA_009_all_1510112055_fastboot.zip
The 3.0.2 images are sourced from @fareed_xtreme's Official OP2 Stock Reset to OOS 3.0.2 thread.
The 2.2.0 images are sourced from @fareed_xtreme's Official OP2 Stock Reset to OOS 2.2.0 thread.
The 2.1.1 images are sourced from @paultje162's Unbrick/Recover OnePlus 2 Back to stock 100% thread.
Credits to @fareed_xtreme & @paultje162 :good:
Unofficial Oxygen OS firmware zips
TWRP flashable zips containing just the firmware from Oxygen OS 3
Oxygen OS 3.6.1: OOS_3.6.1_Firmware.zip
Oxygen OS 3.6.0: OOS_3.6.0_Firmware.zip
Oxygen OS 3.5.9: OOS_3.5.9_Firmware.zip
Oxygen OS 3.5.8: OOS_3.5.8_Firmware.zip
Oxygen OS 3.5.7: OOS_3.5.7_Firmware.zip
Oxygen OS 3.5.6: OOS_3.5.6_Firmware.zip
Oxygen OS 3.5.5: OOS_3.5.5_Firmware.zip
Oxygen OS 3.1.1: OOS_3.1.1_Firmware.zip
Oxygen OS 3.1.0: OOS_3.1.0_Firmware.zip
Oxygen OS 3.0.2: OOS_3.0.2_Firmware.zip
Utilities
EFS_Backup.zip
Flashable zip to backup EFS partitions (modemst1 & modemst1). Includes Restore_EFS.bat to restore EFS via fastboot.
My_Backup.zip
Flashable zip to backup EFS partitions (modemst1 & modemst1) and persist partition. Includes restore_all.bat to restore the partitions via fastboot.
Verry nice post , does this mean when i root and use twrp , i cant do otas anymore and have to flash the complete updated rom via twrp ?
Edit and btw who made the twrp zips?
Can i thrust you ? ;D
Gesendet von meinem ONE A2003 mit Tapatalk
Winflo said:
Verry nice post , does this mean when i root and use twrp , i cant do otas anymore and have to flash the complete updated rom via twrp ?
Edit and btw who made the twrp zips?
Can i thrust you ? ;D
Gesendet von meinem ONE A2003 mit Tapatalk
Click to expand...
Click to collapse
That's correct, you can't take OTA updates if you have root.
You can definitely trust @Spannaa, he's a well respected member here at XDA. I'm not sure whether he wants you to thrust him though
It's unknown where the unofficial TWRP comes from but the official TWRP comes directly from the Team Win Recovery Project.
Winflo said:
Verry nice post , does this mean when i root and use twrp , i cant do otas anymore and have to flash the complete updated rom via twrp ?
Edit and btw who made the twrp zips?
Can i thrust you ? ;D
Gesendet von meinem ONE A2003 mit Tapatalk
Click to expand...
Click to collapse
Best to use the official TWRP version. It was made by the twrp developers and tested by me. I would use it over the unofficial one.
In regards to OTA's, they can only be flashed if the system partition is stock. So if you have modified it, by adding root etc, You wont be able to flash the OTA. To resolve it, you can dirty flash the previous recovery and then the OTA. I have also tested this with the official TWRP recovery and it works 100%
Heisenberg said:
That's correct, you can't take OTA updates if you have root.
You can definitely trust @Spannaa, he's a well respected member here at XDA. I'm not sure whether he wants you to thrust him though [emoji14]
It's unknown where the unofficial TWRP comes from but the official TWRP comes directly from the Team Win Recovery Project.
Click to expand...
Click to collapse
Okay , so he made the Rom zips ? Could be compromised easily that was my worrie.
Winflo said:
Okay , so he made the Rom zips ? Could be compromised easily that was my worrie.
Click to expand...
Click to collapse
Well they're signed zips, which means they're created and signed by OnePlus (or their Oxygen team). There's nothing to worry about.
Good to have this on here. There is a thread on the OP forums but I don't go there often
Updating oxygen on my OPT
Hi I have been trying to update my OPT A2001 variant to a higher version of oxygen. However i'm stuck on oxygen 2.0.0. and can't seem to update through recovery and the OTA isn't available at settings.
My bootloader is unlocked and have got TWRP 2.8.7.0-oneplus2 recovery. SuperSU is installed and root checker confirms root access (I can't update binaries though..).
I've tried installing every version of oxygen past 2.0.1 in full versions and the patches. None of them work and they give the same error.
The logs:
Ioperation_start: 'Flashing'
Installing '/sdcard/OTA/OnePlus2OxygenOS2.0.1.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: This package is for "OnePlus2" devices; this is a "oneplus2".
This package is for "OnePlus2" devices; this is a "oneplus2".
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/OTA/OnePlus2OxygenOS2.0.1.zip'
Error flashing zip '/sdcard/OTA/OnePlus2OxygenOS2.0.1.zip'
Updating partition details...
I Data backup size is 4207MB, free: 33647MB.
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
...done
Click to expand...
Click to collapse
I would really appreciate any help. If you need more info, please ask!
Cheers:good:
michalanchelo said:
Hi I have been trying to update my OPT A2001 variant to a higher version of oxygen. However i'm stuck on oxygen 2.0.0. and can't seem to update through recovery and the OTA isn't available at settings.
My bootloader is unlocked and have got TWRP 2.8.7.0-oneplus2 recovery. SuperSU is installed and root checker confirms root access (I can't update binaries though..).
I've tried installing every version of oxygen past 2.0.1 in full versions and the patches. None of them work and they give the same error.
The logs:
I would really appreciate any help. If you need more info, please ask!
Cheers:good:
Click to expand...
Click to collapse
I can see two reasons why you cant use the OTA.
1 If you are using the official twrp recovery, you have the first version, there was a bug in it and the device name was set to oneplus2 and not OnePlus2 That is why you are getting this error: "This package is for "OnePlus2" devices; this is a "oneplus2"." - There has been a newer version (same version number) which has been released to resolve this issue
2 The next reason why you cant update the OTA is you are rooted. You have modified the contents of the system partition. The OTA checks the contents before installing and if different wont install.
I would suggest you do the following:
Update to the current version of TWRP from the site, it is same version number, but newer build
Download the full 2.1 rom and dirty flash.
Root device
You will then be good to go. For future OTA's you will need to un-root and then you will be able to install the OTA's.
Stephen said:
I can see two reasons why you cant use the OTA.
1 If you are using the official twrp recovery, you have the first version, there was a bug in it and the device name was set to oneplus2 and not OnePlus2 That is why you are getting this error: "This package is for "OnePlus2" devices; this is a "oneplus2"." - There has been a newer version (same version number) which has been released to resolve this issue
2 The next reason why you cant update the OTA is you are rooted. You have modified the contents of the system partition. The OTA checks the contents before installing and if different wont install.
I would suggest you do the following:
Update to the current version of TWRP from the site, it is same version number, but newer build
Download the full 2.1 rom and dirty flash.
Root device
You will then be good to go. For future OTA's you will need to un-root and then you will be able to install the OTA's.
Click to expand...
Click to collapse
Thank you very much kind sir for your fast reply and clear feedback/solution I wouldn't have figured that out by myself anytime soon
Have a nice day!
I am currently using oxygen 2.0.3, stock, non rooted. Can I dirty flash the 2.1 rom with stock recovery or should I use TWRP?
Sent from my ONE A2005 using Tapatalk
It should, apparently, work in stock recovery so give it a go
EddyOS said:
It should, apparently, work in stock recovery so give it a go
Click to expand...
Click to collapse
Thanks, worked for me!
Sent from my ONE A2001 using Tapatalk
Worked for me as well. Its the way to go I think.
Sent from my ONE A2001 using Tapatalk
timmberg said:
Thanks, worked for me!
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
Kishes Mist said:
Worked for me as well. Its the way to go I think.
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
Good to know, I wasn't sure if they were TWRP-only
I actually used the latest version of TWRP. But how did it was re flashed 2.0.2 which un rooted then put the 2.1 in a queue so basically it flashed then flashed again all in one go
Sent from my ONE A2001 using Tapatalk
Kishes Mist said:
I actually used the latest version of TWRP. But how did it was re flashed 2.0.2 which un rooted then put the 2.1 in a queue so basically it flashed then flashed again all in one go
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure the cumulative zips overwrite TWRP with stock recovery, so what I did is flash the zip with TWRP, then flash the TWRP recovery image before rebooting. This way you avoid needing a computer or root access to get TWRP installed again.
ΦDroid said:
I'm pretty sure the cumulative zips overwrite TWRP with stock recovery, so what I did is flash the zip with TWRP, then flash the TWRP recovery image before rebooting. This way you avoid needing a computer or root access to get TWRP installed again.
Click to expand...
Click to collapse
The full rom zips don't overwrite TWRP ?
Sent from my OnePlus 2
Spannaa said:
The full rom zips don't overwrite TWRP ?
Sent from my OnePlus 2
Click to expand...
Click to collapse
OK, I just assumed that it did since the 2.1.0 OTA directly from OnePlus overwrote it. I'll keep that in mind next time.
Edit: thanks a lot for sharing these, I already managed to break WiFi the first day with this device by flashing kernels. The full rom zip fixed it right away.
Sent from my ONE A2005 using Tapatalk

Custom recovery and custom ROM

I recently unlocked the bootloader of my oneplus x to install an ota update 2.2.3 oxygen os which downloaded but failed to install. Then a 1 or 2 days ago i got the marshmallow update (pretty late ikr unlike OP3 and OP2). But, i didn't install a custom recovery because on the oneplus site it was written in the ota installation guide that stock recovery is preferred while installing ota updates manually. So FIRSTLY i would like to ask that can i install a custom rom with an unlocked stock recovery or i need a custom recovery. Secondly, is CYANOGENMOD better than oxygen os or should i continue with oxygen os. Thirdly, do i need to root my phone to install custom rom and recovery? Lastly, is all this worth doing ?
You don't need to unlock bootloader for getting OTA updates.
1. You cannot install custom rom through stock recovery. You have to use custom recovery (with bootloader unlocked )i.e., TWRP by bluespark in oos 3.1.3 or later MM version.
Don't flash this recovery if you are using lollipop oos, for lollipop oos use normal twrp.
2. If you want more customizations, themes and root access then go for cyanogen. But if you want stable, with great camera then go for oos.
Personally i prefer oos over cm because camera quality in cm is not comparable as OOS have.
3. You don't need to root your opx to install roms and custom recovery
4. yeah for me its absolutely worth because i can flash what i want and do more things. ?
You can install oos 3.1.3 through twrp as well as stock recovery.
yuv93 said:
You don't need to unlock bootloader for getting OTA updates.
1. You cannot install custom rom through stock recovery. You have to use custom recovery (with bootloader unlocked )i.e., TWRP by bluespark in oos 3.1.3 or later MM version.
Don't flash this recovery if you are using lollipop oos, for lollipop oos use normal twrp.
2. If you want more customizations, themes and root access then go for cyanogen. But if you want stable, with great camera then go for oos.
Personally i prefer oos over cm because camera quality in cm is not comparable as OOS have.
3. You don't need to root your opx to install roms and custom recovery
4. yeah for me its absolutely worth because i can flash what i want and do more things. ?
You can install oos 3.1.3 through twrp as well as stock recovery.
Click to expand...
Click to collapse
Thanks. Btw I think u didn't read it properly or i must not have framed my sentences properly, I had got an OTA update for oos 3.1.3. it's just that I was thinking of flashing cm:good:
androcrazy24 said:
Thanks. Btw I think u didn't read it properly or i must not have framed my sentences properly, I had got an OTA update for oos 3.1.3. it's just that I was thinking of flashing cm:good:
Click to expand...
Click to collapse
Oh I forgot to mention that I have already got the 3.1.3 oos ota update

Updating miui

I Want to update to stable last ver but i have root and various magisk modules, is there a way to update without losing these? Im On stable stock
flash this stock recovery of POCO.
https://drive.google.com/open?id=1O64q5Ldd6KylC3zxlcKm39okFY_-Kjww
download the Update of MIUI ROM and install.
after you boot onto latest MIUI, you can flash TWRP from fastboot with cmd and install MAGISK again.(I also had an instance when i updated the same way but i had Magisk and all the modules active even after updating. Goodluck,though.)
Hit thanks if i helped.
Animesh Singh said:
flash this stock recovery of POCO.
https://drive.google.com/open?id=1O64q5Ldd6KylC3zxlcKm39okFY_-Kjww
download the Update of MIUI ROM and install.
after you boot onto latest MIUI, you can flash TWRP from fastboot with cmd and install MAGISK again.(I also had an instance when i updated the same way but i had Magisk and all the modules active even after updating. Goodluck,though.)
Hit thanks if i helped.
Click to expand...
Click to collapse
Taking the title of the topic, I would like to clarify a doubt: I am in beta 9.1.24, as soon as they launch a new update of the miui beta, I update by the updater of the device? I lose the data or is it the same way it works in the stable updates?
Pavamarea said:
Taking the title of the topic, I would like to clarify a doubt: I am in beta 9.1.24, as soon as they launch a new update of the miui beta, I update by the updater of the device? I lose the data or is it the same way it works in the stable updates?
Click to expand...
Click to collapse
Updating from beta to beta builds will not erase data. But, if you're a Stable user and try to install a beta build through MIUI stock recovery then your data will be erased.

Android 10 Kernel with Wireguard module

There are no Android 10 Kernel threads that I could find, so i want to know if there are any kernels for Android 10 (Currently using the Bliss ROM) that have the Wireguard kernel module ?
Yoda007 said:
There are no Android 10 Kernel threads that I could find, so i want to know if there are any kernels for Android 10 (Currently using the Bliss ROM) that have the Wireguard kernel module ?
Click to expand...
Click to collapse
? KalinaNegev: Continuum Turbulence 2 - Kernel
? Redmi Note 3 Pro (Kenzo)
? By MocaRafee
? 24/03/2020
? Changelog:
* Added back WireGuard Support
* Added some optimization to the Audio
* Overclocked CPU and GPU DDR to 1296MHz and BIMC to 648MHz for the OCed variant
Big thanks to @Krittin for the Overclocked DDR & BIMC
? Additional Info:
* Support AOSP (Nougat, Oreo, Pie, Ten)
? Notes:
* Available 4 version: Normal, Normal with JackFix, OC, and OC with JackFix.
* Some notes about additional optimization based on experience. READ HERE.
Download Link:
MOD EDIT: Link Removed
? Subscribe: nTu21 ?
#kalinanegev #kernel #kenzo
Thanks, the kernel module option is now available in the Wireguard app, but unfortunately is not working - when i click to enable it it tries but does not work. So if you encounter another kernel that supports it in the future, please post the link here.
Yoda007 said:
Thanks, the kernel module option is now available in the Wireguard app, but unfortunately is not working - when i click to enable it it tries but does not work. So if you encounter another kernel that supports it in the future, please post the link here.
Click to expand...
Click to collapse
Try this
Elindir kernel
https://github.com/androbada525/Eli...4/Elindir-v4-60Hz-kenzo-22032020-05.47.08.zip
Note:
Never flash custom kernel over another custom kernel.
Always dirty flash the current rom zip first .
before flashing this kernel. Dirty flash ur current rom zip To restore stock kernel.
Then flash this kernel and wipe cachedalvik.
Thank you! Will try next week (tried the v4 Elindir with no success but did it over another custom kernel, so need to try again over stock ROMs) since before i was trying different kernels i did a nandroid backup, flashed a kernel, then restored the nandroid backup. After restoring a nandroid backup i got a bootloop and had to return to an Android 9 backup., and i am not in the mood to set up my phone again this weekend. Your way (dirty flashing of rom to get old kernel back) sounds much faster heh.
BTW: Is the nandroid backup not working a specific ROM issue (Bliss) or does it happen with all Android 10 ROMS ? I have the latest 3.3.1 official TWRP.
Yoda007 said:
Thank you! Will try next week (tried the v4 Elindir with no success but did it over another custom kernel, so need to try again over stock ROMs) since before i was trying different kernels i did a nandroid backup, flashed a kernel, then restored the nandroid backup. After restoring a nandroid backup i got a bootloop and had to return to an Android 9 backup., and i am not in the mood to set up my phone again this weekend. Your way (dirty flashing of rom to get old kernel back) sounds much faster heh.
BTW: Is the nandroid backup not working a specific ROM issue (Bliss) or does it happen with all Android 10 ROMS ? I have the latest 3.3.1 official TWRP.
Click to expand...
Click to collapse
Stay on android 9 . 10 roms got issues with flashing procedure.
To flash Most of the 10 roms u need to strictly follow
Wipe all, format data, reboot to recovery again , install rom and gapps. Only then 10 will boot.
Even before restoring nandroid u need to do format data command.
They say its happens coz of broken installation script on 10.
Android 9 flashing instruction is very simple.
Factory reset
Install rom and gapps
Reboot.
Now encryption on 10 is fixed in latest havoc, syberia.
I m waiting for bliss to fix it.
Black_Stark said:
Note:
Never flash custom kernel over another custom kernel.
Always dirty flash the current rom zip first .
before flashing this kernel. Dirty flash ur current rom zip To restore stock kernel.
Then flash a kernel and wipe cachedalvik.
Click to expand...
Click to collapse
Or you can just backup the existing boot.img and reflash if needed? No? Also there's this twrp flashable module by AnggaSync which cleans the boot.img for flashing a kernel.

Categories

Resources