Hello,
I have a OnePlus One running on CM 13.0
I have MultiRom installed and I have this error showing on the front page of the app - "doesn't have hexec-hardpoot patch!". I tried to install Kernal 6.0.x (my primary ROM is CM 13.0) through the app, but I couldn't. When I try to install the Kernal I get an error during the instillation saying "needs recovery".
I don't really know a lot about this stuff so excuse my ignorance, but how do I install the needed recovery so that I will be able to install the Kernal.
I have TWRP installed in my phone. I swap my primary ROM with a secondary one few days ago. I am not sure if this was caused the issue.
ali282h said:
Hello,
I have a OnePlus One running on CM 13.0
I have MultiRom installed and I have this error showing on the front page of the app - "doesn't have hexec-hardpoot patch!". I tried to install Kernal 6.0.x (my primary ROM is CM 13.0) through the app, but I couldn't. When I try to install the Kernal I get an error during the instillation saying "needs recovery".
I don't really know a lot about this stuff so excuse my ignorance, but how do I install the needed recovery so that I will be able to install the Kernal.
I have TWRP installed in my phone. I swap my primary ROM with a secondary one few days ago. I am not sure if this was caused the issue.
Click to expand...
Click to collapse
Hello ali282h,
I don't know about the needs recovery error during the installation, but if it's saying doesn't have kexec-hardboot patch then you have to find an kernel that fits ur cm-13.0 rom with kexec-hardboot patch included. I assume that when you've switched ur external rom with ur primary that the external rom that you were using didn't had an kexec-hardboot patch included so try another kernel with kexec-hardboot patch included.
Hope this would help you with ur problem:good:
Thank you. I will give it a try.
ali282h said:
Thank you. I will give it a try.
Click to expand...
Click to collapse
if you want you existing primary, i can propose 2 kernels. 1 is Boeffla kernel and the other lightening CM13 kernel.
Instructions in their thread. However, if you plan to use multirom for a while, the latest update has kexec workaround. (multirom settings from TWRP- check multirom page last 2-3 pages). or i would entirely recommend you to keep a kexec patced rom as primary to negate any issues which may arise.
Thank you for the suggestions. I am actually using the 'workaround' feature in TWRP.
I have a question in regard to Boeffla. In the official website.. (http://boeffla.de/index.php/downloads/current-kernel-versions) It says 5.2 next the Oneplus One CM 13.0 Stable. I am confused as to what 5.2 really means. Is this the Android version? CM 13 is based on Android 6.0! I just don't want to flash the wrong one and end up with a boot loop. Do you think the kernel I mentioned is compatible with my phone (OnePlus One - CM 13.0 - Android 6.0.1)
Thank you!
Related
Are there any CM12 builds (or variants) for OnePlus that are compatible with MultiROM? I got so confused reading how to flash Temasek's version that I gave up. There was one that was compatible and it worked until the latest firmware was released. Just wondering if MultiROM is worth it for CM12 builds?
Thanks in advance.
sanjsrik said:
Are there any CM12 builds (or variants) for OnePlus that are compatible with MultiROM? I got so confused reading how to flash Temaseks version that I gave up. There was one that was compatible and it worked until the latest firmware was released. Just wondering if MultiROM is worth it for CM12 builds?
Thanks in advance.
Click to expand...
Click to collapse
I tried to flash latest nightly with MultiROM, result is bootloop for CM12.
You can make CM12 as primary ROM and keep KitKat based ROMs as secondary
(Clean flash is needed for above statement)
sanjsrik said:
Are there any CM12 builds (or variants) for OnePlus that are compatible with MultiROM? I got so confused reading how to flash Temasek's version that I gave up. There was one that was compatible and it worked until the latest firmware was released. Just wondering if MultiROM is worth it for CM12 builds?
Thanks in advance.
Click to expand...
Click to collapse
I was able to do this.
I used the following workaround:
1) Install MultiROM
2) Backup your primary ROM
3) Flash the Lollipop ROM as primary ROM
4) Backup the Lollipop ROM
5) Restore the backup of your CM11S? ROM
6) In the TWRP recovery go to MultiROM -> add ROM -> from backup
7) Enjoy!
I'd like to include a link where i found this but unfortunately I can't (I need 10 posts). I do know that it is the first/second link if you google this: [WORKAROUND - MULTIROM] How to avoid "error executing updater binary in zip"
But if you're interested PM me.
No need to do any of those swapping ROM things anymore
Search keyword multirom in the temasek thread and you will find multirom edited ROMs that you can add and they will work. Just make sure you install the multirom app from play store and update to the latest on your primary ROM if there are any updates.
Only requirement is that your primary ROM needs to have a custom kernel. You can flash ak kernel on your primary. Make sure you get the right version for whatever ROM is your primary. Or your can simply install the kernel from within multirom app if you don't care about custom features with custom kernels and that will work also
Sent From Lollipopified Bacon Goodness!
Hi,
I was trying to install Ubuntu Touch (Stable 11 & 13) alongside my Resurrection Remix (M-6.0.1) [May 24 Release] internal ROM.
Followed all the steps mentioned in Multirom v33b, installed latest TWRP, Kernel (6.0.x) & recovery.
The UT build (Stable 11 & 13 - tried separately) downloads and installs successfully. Yet on selecting from Multirom Grub/bootloader it reboots and gets stuck at Oneplus boot screen, never boots into Ubuntu Touch.
Anyone tried it, faced such issues and fixed....
Your help will be much appreciated.
Cheers
bump
mandrax.prime said:
Hi,
I was trying to install Ubuntu Touch (Stable 11 & 13) alongside my Resurrection Remix (M-6.0.1) [May 24 Release] internal ROM.
Followed all the steps mentioned in Multirom v33b, installed latest TWRP, Kernel (6.0.x) & recovery.
The UT build (Stable 11 & 13 - tried separately) downloads and installs successfully. Yet on selecting from Multirom Grub/bootloader it reboots and gets stuck at Oneplus boot screen, never boots into Ubuntu Touch.
Anyone tried it, faced such issues and fixed....
Your help will be much appreciated.
Cheers
Click to expand...
Click to collapse
There is a problem with the latest recovery. Flash this recovery 'TWRP_multirom_bacon_20160221-01.img' from multirom recovery folder and it'll get installed without any errors
TRIED!!
sandesh780 said:
There is a problem with the latest recovery. Flash this recovery 'TWRP_multirom_bacon_20160221-01.img' from multirom recovery folder and it'll get installed without any errors
Click to expand...
Click to collapse
TRIED MANY OTHER BUILDS OF MULTIROM TWRP!!
NO USE..still the same issue..
but on using too old builds will not allow us to install ubuntu...
it says "update recovery and multirom to install ubuntu!!"
I can confirm using TWRP_multirom_bacon_20160221-01.img solves the issue. Thank you very much @sandesh780
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
dark_prince said:
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
Click to expand...
Click to collapse
Thanks for your reply. That surprises me that there still isn't an miui 8 developer ROM out yet for this device. Probably shall never come in that case.
Good to hear that f2fs is supported by cm14 though. Will certainly be running this once I receive my new cases to replace the girly pink cover my mi4c currently houses
danbrown162 said:
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
Click to expand...
Click to collapse
Just flash miui 8 from xiaomi.eu ones. It supports flashing via twrp.
DESCRIPTION:
Hey guyz..... Me Hassan Mirza from Pakistan
Today am here with a new thread and I Have a good news for you....
As you know, The other methods are old now and also, in Nougat, there is root which needs to mount system each time you need to use it,,, so Today, your system mount and root problem solved... Phh or Magisk, you choose
Releasing Elite Kernel v2 ported from P9 Lite
Its PreRooted, System RW available for all time, Titanium backup works perfectly and Magisk work too for it to hide root
With this you can flash anything and see in SYSTEM ! VIPER...adaway no systemless...etc...
DISCLAIMER:
I will Provide correct info and help......All This you are gonna do is At your Own Risk... Damage to your device of any type is at your Own Responsibility,,, Don't point finger at me or I will Just Laugh at you...
Install:
1.) Download this Elite Kernel for Honor 8 CxxB36x v2
2.) Put in Root of SD Card.
3.) Flash this in Latest Recovery for Nougat.
4.) See if Superuser app installed, if not install Phh Superuser from google play.
5.) And you are ROOTED.
The file it's boot.img is based upon L04-C567B360, modded and signed for boot.
Its Adviced to remove pattern Lock and Fingerprint Lock before installing.... just adviced,,,
If you like, donate
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
Changelog in 2nd post...
This is Based on Stock Huawei Kernel, Not compiled by Me...
Contributors:
@HassanMirza01 for doing all this
@phhusson for his wonderful work of making Phh superuser
@Telperion as he got my attention for doing this
Status:
Status: Stable
Stable Release Date: 2017-04-27
Created on: 2017-04-04
Last Updated on: 2017-04-27
CHANGELOG:
2017-04-04 Elite Kernel for B3xx by [email protected] v1: Initial release,
2017-04-27 Elite Kernel for B3xx by [email protected] v2: The Most wanted MagiskSU released with Proper Support,,, Use with Cautions...
This is all really good stuff.
Thank you for sharing your work
John
Guyz if this kernel didnot working, booting for you or crashing your settings app,,, send me the boot.img file of your own variant of Honor 8... I will see into it...
awesome! Thanks for your hard work on this! Will this work with the LineageOS build that @surdu_petru and team have been working on?
I think no.... Like Lineage 14.1 for P9 lite,,, we need to go to MM to install it... So lineage kernel according to my guess, works on MM based roms so Elite Kernel wont work with it :/
HassanMirza01 said:
I think no.... Like Lineage 14.1 for P9 lite,,, we need to go to MM to install it... So lineage kernel according to my guess, works on MM based roms so Elite Kernel wont work with it :/
Click to expand...
Click to collapse
So this doesn't work on nougat? I guess the support for magisk tells me it doesn't. Bummer.
If the kernel is based on B360 then it should work with N and not MM. The Lineage rom right now is using the stock N kernel with no changes to it. They are not building a N kernel inline with Lineage as there's no source code out for it.
I guess my question is, would it be possible to flash Lineage, and then flash this kernel over it?
my Kernel is on Nougat based ROM not on MM but someone should try it on lineage too.....and tell the result...
@HassanMirza01 -- kernel works and PHH SU works and can R/W /system/. One issue I noticed however is that "Revoke USB Debugging Authorizations" has disappeared from my Developer menu. On the Honor 8 with Nougat I frequently have to revoke and reset authorizations to get it to work properly. I was able to get it working again by flashing the stock boot and rooting with the linked zip.
Magisk, however, crashes the phone on installation attempt, even with SELinux set to permissive. It causes a reboot when 'setting up the environment' either through Magisk Manager or TWRP. It appears that the P9 Lite kernel must have proper loop support whereas the Honor 8 still doesn't even with tweaks. It was speculated that since on the P9 Lite Magisk wouldn't work on Nougat, but on the P9 Lite after flashing this kernel and flashing Magisk in permissive SELinux mode, it installed successfully, that a similar path might work on the Honor 8. Then again, perhaps something is workable.
Either way, thanks for looking into this. :good:
https://drive.google.com/file/d/0B0zE1Kk8sIB6eVplODFjaTh4Q0U/view?usp=drivesdk
i will release a next build soon for some bugs fixes.... also, magisk proper support is coming soon,,,
Here's a log of what happens when I try to flash Magisk.
bro send me recovery log,,, i cant understand the one you send above...
Here is a zipped boot.img for honor 8 frd-l19 C432b360
HassanMirza01 said:
bro send me recovery log,,, i cant understand the one you send above...
Click to expand...
Click to collapse
Unfortunately Recovery crashes before it can write what happened to the log. That kernel crash log up above is the closest info we can probably get.
I attached the TWRP log though anyway.
Telperion said:
Unfortunately Recovery crashes before it can write what happened to the log. That kernel crash log up above is the closest info we can probably get.
I attached the TWRP log though anyway.
Click to expand...
Click to collapse
Also another log, this one shows the beginning stages of the flash and where the crash happens. (Search Magisk in the text file)
Expected release date: when kernel source comes out.
Just to makes this clear, we have no proper loop support and thats why magisk will not work (just take the dmesg from the user above as example, it tries to create a new loop volume and directly crashes ..)
Regards
svardman said:
Here is a zipped boot.img for honor 8 frd-l19 C432b360
Click to expand...
Click to collapse
Bro i didnot find the boot.img in your provided zip... Just check the size of your uploaded zip...
HassanMirza01 said:
Bro i didnot find the boot.img in your provided zip... Just check the size of your uploaded zip...
Click to expand...
Click to collapse
My Bad, gonna fix it later on today,
Does the new version of TWRP thats released help this ?
I know i was finnaly able to just Flash TWRP > flash SUPERSU 2.79 to root and thats it ! no pre modfiied boot.img needed . perfectly working now
I'm not responsible for any damage to your device of any sort.
By flashing this, you take responsibility of anything that happens.
Process at your own risk!
If you want to check - please make backup. Better to store all partitions.
What works
audio
bluetooth
brightness
call/LTE (mondrianlte)
camera
DRM
OTA
video
wifi
wifi display
What doesn't work
Back camera preview : wrong rotation on preview in default app Fixed build 20221204
SELinux Fixed build 20221130
Instructions:
0. Patched TWRP for FOTA : mondrianwifi / mondrianlte
1. Factory reset if coming from another ROM.
2. Install ROM
3. Install GApps (optionally) [Recommended BiTGApps ARM 13]
4. Install Magisk 25.2 (optionally)
Sources & Changes:
Device tree mondrianwifi
Device tree mondrianlte
Kernel tree
Vendor tree mondrianwifi
Vendor tree mondrianlte
TWRP tree mondrianwifi
TWRP tree mondrianlte
Download:
Downloads: mondrianwifi / mondrianlte
Note to users: I'm not responsible if you brick your tablet. See the disclaimer above.
Contributors
LineageOS team for source code.
@retiredtab for helping make mondrianwifi to work on Android12
@khalvat for its work on porting msm8974 to Android12 (https://github.com/LineageOS-UL)
@pocketrule, @bierma32, @Yxo 6o6uka for willing to test WIFI builds and leaving feedback
@bmwdroid for willing to test LTE builds and leaving feedback
ROM OS Version: 13.0
Version Information
Status: Nightlies
Created 2022-11-27
Last Updated 2023-01-05
THX @phoval for the New LOS 20 Version.
Installed this as update over the Version 20221010 without issue's.
FOTA update notification works .
New build: SeLinux is enforcing
Perfect !!!
Amazing !!
Thank you @phoval !!!
Hello, good job.
Thank you @phoval
Installed and runs smooth. Sound, video & wifi works. Excelled work.
Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers
@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204
cwokel said:
Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers
Click to expand...
Click to collapse
bierma32 said:
@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204
Click to expand...
Click to collapse
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz
@chkdsk90
Charge your battery to 100% and try another clean install, format also system and data .
chkdsk90 said:
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz
Click to expand...
Click to collapse
Provide logcat.
zram boot img was alpha kernel for test.
The changes are includes since 2nd december build.
how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar
chkdsk90 said:
how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar
Click to expand...
Click to collapse
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.
pocketrule said:
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.
Click to expand...
Click to collapse
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file
chkdsk90 said:
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file
Click to expand...
Click to collapse
It's patched for FOTA. A simple internet search reveals, that fota stands for "Firmware Over-the-Air" 😉️ I.e. you can download and update the rom directly from the rom itself. If you (always) download and flash the rom manually / separately, you don't need the patched rom.
One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?
If I get a app not responding message and I hit wait it will repeatedly pop up despite the app responding again (dirty flash). Otherwise first impressions of this rom are good.
Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today
cwokel said:
One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?
Click to expand...
Click to collapse
Just disable it in system > buttons. It's customization during first setup.
You can enable gesture navigation too.
jacomail95 said:
Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today
Click to expand...
Click to collapse
If someone can find me one to buy?