Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=n3&type=nightly
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 12.1 Nightlies for the Oppo N3, ROM for the Oppo N3
Contributors
invisiblek
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Nightly
Created 2015-04-20
Last Updated 2015-04-19
my n3 is n5207 edition , after flashed the cm roms lately , it can't find the baseband, can't find usim, can't use the mobile network
anyone could help me ?
the cm roms before 20140422 worked well , the roms after 20140424 can't find the baseband
---------- Post added at 05:07 AM ---------- Previous post was at 04:54 AM ----------
many chinese n3 users meet the problem like me , after flash the cm rom ,they can't find baseband
i ask question in oppoforums and pull a issues on github , yet it seems no one care.
many chinese n3 users are girls and english are not very well , so we hope cm rom makers can see the issues
thanks for your work
Does this still happen with the newest builds? If yes, please post a radio logcat from boot(ideally taken via 'adb logcat -b radio' via PC)
maniac103 said:
Does this still happen with the newest builds? If yes, please post a radio logcat from boot(ideally taken via 'adb logcat -b radio' via PC)
Click to expand...
Click to collapse
the newest builds don't work either , how can i get a radio logcat from boot?
my n3 edition is n5207 ,maybe n5209 and n3 international edition worked well
easyinplay said:
the newest builds don't work either , how can i get a radio logcat from boot?
Click to expand...
Click to collapse
This post has some instructions. The command you'll need is 'adb logcat -b radio > log.txt'. I'd also be interested in the output of 'adb shell getprop'.
maniac103 said:
This post has some instructions. The command you'll need is 'adb logcat -b radio > log.txt'. I'd also be interested in the output of 'adb shell getprop'.
Click to expand...
Click to collapse
i am a new member here , and i can't upload a file . so i paste a url can download it.
1、the cm old version 20150422 which can work on my n5207 , the modem seems ok
h t t p s : // mega.nz/#!FBZnWbiB
2、the latest cm version 20150528 , my n5207 can't find baseband
---------- Post added at 02:48 AM ---------- Previous post was at 02:38 AM ----------
easyinplay said:
i am a new member here , and i can't upload a file . so i paste a url can download it.
1、the cm old version 20150422 which can work on my n5207 , the modem seems ok
h t t p s : // mega.nz/#!FBZnWbiB
2、the latest cm version 20150528 , my n5207 can't find baseband
Click to expand...
Click to collapse
the link is not correct , so i change it
the cm old version 20150422 log and screeshots:
mega.nz/#!5Z4jxIbL!pzT2TaaYHNMmaEqcKoawbQfrSZBIcJ5wy98II7eXyr0
mega.nz/#!kcgnRKZY!YyOR4_c18KEjGOBnVIjdv_MAPULp9814IdRUFGchsbk
mega.nz/#!EFQxUDRS!EA2gNOnIokyT4cukKPpEQDbcdT-JNiUzoPjv-zOhMhw
---------- Post added at 03:31 AM ---------- Previous post was at 02:48 AM ----------
easyinplay said:
i am a new member here , and i can't upload a file . so i paste a url can download it.
1、the cm old version 20150422 which can work on my n5207 , the modem seems ok
h t t p s : // mega.nz/#!FBZnWbiB
2、the latest cm version 20150528 , my n5207 can't find baseband
---------- Post added at 02:48 AM ---------- Previous post was at 02:38 AM ----------
the link is not correct , so i change it
the cm old version 20150422 log and screeshots:
mega.nz/#!5Z4jxIbL!pzT2TaaYHNMmaEqcKoawbQfrSZBIcJ5wy98II7eXyr0
mega.nz/#!kcgnRKZY!YyOR4_c18KEjGOBnVIjdv_MAPULp9814IdRUFGchsbk
mega.nz/#!EFQxUDRS!EA2gNOnIokyT4cukKPpEQDbcdT-JNiUzoPjv-zOhMhw
Click to expand...
Click to collapse
the latest cm build 20150528 log and screeshots on my N5207
mega.nz/#!IMBmUBxA!XL7G7L2vnYHB2Mt8r011E77gf68p4Juzeo1QmRK6DQE
mega.nz/#!gEhxQahR!qtRHsASlOwGNkCW1UMzw3JewtYgkqeSR38Cw0FIBviI
mega.nz/#!4URUWSTC!zVBDDcdhN-cdIoowhu7TZNP8ljXTB0nDnO3K3rm3fSk
The logcats unfortunately aren't radio logcats, but main logcats - you forgot to add the '-b radio' command line parameter. Can you please re-do them like this:
- Enter 'adb logcat -v time -b radio > log.txt' into the command terminal window, but don't press 'enter' yet
- Reboot your phone
- While the phone is rebooting and showing the Oppo logo, press 'Enter' in the command terminal
- (It should say 'Waiting for device' now and start capturing stuff as the phone is booting)
- Wait for about 1 minute after entering your PIN
- Upload the captured text file
Thanks.
maniac103 said:
The logcats unfortunately aren't radio logcats, but main logcats - you forgot to add the '-b radio' command line parameter. Can you please re-do them like this:
- Enter 'adb logcat -v time -b radio > log.txt' into the command terminal window, but don't press 'enter' yet
- Reboot your phone
- While the phone is rebooting and showing the Oppo logo, press 'Enter' in the command terminal
- (It should say 'Waiting for device' now and start capturing stuff as the phone is booting)
- Wait for about 1 minute after entering your PIN
- Upload the captured text file
Thanks.
Click to expand...
Click to collapse
i am sorry to reply so late.but when i press "enter" when showing the oppo logo , it say error:device not found . when cm logo show , it semms ok
the new log.txt of cm-20150531
mega.nz/#!5dxUDSiI!M1cZ8Gj23EQoym8eF5k-nTOfs9CwBmpy5eXfYK9z9PA
easyinplay said:
the new log.txt of cm-20150531
mega.nz/#!5dxUDSiI!M1cZ8Gj23EQoym8eF5k-nTOfs9CwBmpy5eXfYK9z9PA
Click to expand...
Click to collapse
That one looks better, thanks. It looks like your RIL daemon gets stuck for some reason. Let's see whether we can find something by enabling more debug output. Please do the following:
Enable root access for ADB under Settings -> developer options
run 'adb root'
run 'adb shell cat /proc/cmdline' and post the output here
run 'adb shell setprop persist.radio.adb_log_on 1'
run 'adb reboot'
grab a new radio logcat as above and re-upload it
Additionally, please also post the output of 'adb shell getprop'.
Thanks.
maniac103 said:
That one looks better, thanks. It looks like your RIL daemon gets stuck for some reason. Let's see whether we can find something by enabling more debug output. Please do the following:
Enable root access for ADB under Settings -> developer options
run 'adb root'
run 'adb shell cat /proc/cmdline' and post the output here
run 'adb shell setprop persist.radio.adb_log_on 1'
run 'adb reboot'
grab a new radio logcat as above and re-upload it
Additionally, please also post the output of 'adb shell getprop'.
Thanks.
Click to expand...
Click to collapse
thanks for your kind. the new test files here:
mega.nz/#!5YxQSQTQ!w-3wNAfmeaGXPgnOKBb6qdXwcerO3kCQkYGRutKuKlU
Thanks. When comparing your log to mine, it looks like the RIL library wants to talk to the firmware, but doesn't get any response. It may be that the new proprietary libraries comitted on 4/23 need updated firmware, without us being aware of that yet.
Can you please try to get your firmware updated? The process for that is this:
- Make a backup of your CM installation via recovery
- Install the stock ROM (from here) via recovery
- Boot it, let it check for OTAs and install them, if there are any
- Reinstall CM
- See whether things improve
If that works, we'll probably need to include the firmware into CM and/or make a separate flashable zip, but before doing that I'd want to see whether this actually helps.
maniac103 said:
Thanks. When comparing your log to mine, it looks like the RIL library wants to talk to the firmware, but doesn't get any response. It may be that the new proprietary libraries comitted on 4/23 need updated firmware, without us being aware of that yet.
Can you please try to get your firmware updated? The process for that is this:
- Make a backup of your CM installation via recovery
- Install the stock ROM (from here) via recovery
- Boot it, let it check for OTAs and install them, if there are any
- Reinstall CM
- See whether things improve
If that works, we'll probably need to include the firmware into CM and/or make a separate flashable zip, but before doing that I'd want to see whether this actually helps.
Click to expand...
Click to collapse
flash latest cm build after i flash stock rom
i have tried this many time , it seems not work
i will try one more time today , but i think this problem may related with difference between n3 international edition and chinese edition
When you flash the stock ROM, please also take note of the baseband version displayed there after receiving the latest OTA.
Thank you for your hardwork. My brother owns a Chinese N3, so I'm in with you guys for a couple of days with the N5207 development. Downloading the latest firmware now. Is there anything I can help with ?
Edit: Can someone post the DL links for the last working CM12.1 for N5207 in case of something bad goes wrong ? CM links are dead
Edit 2: Installed the 20150606 build, both sims work
this is my test result today , i tried three n3 editions stock rom
1、try n5207 stock rom , then flash cm bulid 20150606 , the mobile network is still broken
2、try n5209 stock rom , then flash cm bulid 20150606 , the mobile network is still broken
3、try n5206 stock rom , then flash cm bulid 20150606 , the mobile network finally work
so i think the baseband between three editions are different
thank you all reply to this problem
easyinplay said:
this is my test result today , i tried three n3 editions stock rom
1、try n5207 stock rom , then flash cm bulid 20150606 , the mobile network is still broken
2、try n5209 stock rom , then flash cm bulid 20150606 , the mobile network is still broken
3、try n5206 stock rom , then flash cm bulid 20150606 , the mobile network finally work
so i think the baseband between three editions are different
thank you all reply to this problem
Click to expand...
Click to collapse
How come ? Mine's a N5207, I wiped the entire system folder, dalvik cache and data using twrp, then proceed to install CM, flash stock recovery to get it to boot since there's kinda a bug which prevented the phone to boot normally, setting things up then flash twrp, flash gapps. Done
vusun123 said:
How come ? Mine's a N5207, I wiped the entire system folder, dalvik cache and data using twrp, then proceed to install CM, flash stock recovery to get it to boot since there's kinda a bug which prevented the phone to boot normally, setting things up then flash twrp, flash gapps. Done
Click to expand...
Click to collapse
I am sorry , i post a wrong message. yesterday , i didn't wipe the system folder. i tried just now , it works well.
thanks for your work. this is a good news for chinese n3 users.
CM 12.1 on my n5207 auto reboot many times every day for no reason. how can i solve this problem? i will be glad for your reply
Auto reboot as in 'shows the boot animation again without showing the Oppo logo before' (and you don't have to enter you SIM PIN again)? If yes, that's something we're looking into and doesn't happen on the N3 only, but also on other devices. Unfortunately it's pretty hard to debug this issue.
maniac103 said:
Auto reboot as in 'shows the boot animation again without showing the Oppo logo before' (and you don't have to enter you SIM PIN again)? If yes, that's something we're looking into and doesn't happen on the N3 only, but also on other devices. Unfortunately it's pretty hard to debug this issue.
Click to expand...
Click to collapse
as you describle, i didn't show oppo logo when rebooting. thanks for your reply
Introduction
NOTE:
Hello everyone, this is my first kernel for the Moto G4 Plus. I will try to maintain a stable kernel however bugs might arise since I'm not a super star kernel developer. I hope you enjoy the releases.
Important information
I will not reply to complains that do not include clear steps to reproduce the bug, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
Features
Here are the major features of the kernel (feel free to explore Github)
Update to date with the latest Linux upstream version (3.10.108-EOL)
Westwood as the default congestion algorithm with many more to choose from
Several subsystems converted to use power efficient workqueues
Compiled with Google's arm-eabi 4.9 toolchain
Audio control from flar2
Downloads
Oreo 8.0 : https://sourceforge.net/projects/babyfish-kernel/files/athene/oreo_caf/
Nougat 7.1 : https://sourceforge.net/projects/babyfish-kernel/files/athene/nougat_caf/
Nougat 7.0 Stock :https://sourceforge.net/projects/babyfish-kernel/files/athene/stock_nougat/
Installation:
NOTE: Please make sure that you return to the stock kernel of the ROM before flashing this kernel. The kernel is unified for Moto G4 and the Plus variant so everything should be working fine.
Install the latest adb and fastboot: https://developer.android.com/studio/releases/platform-tools.html#download
Grab the boot image from the download links above
Method 1:
Using adb and fastboot
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Reboot and profit!
Method 2: TWRP
Keep the bootimage on your phone's storage and boot to TWRP.
Install > Select Install Image > Choose the image > Boot partition > Reboot
Changelog
28 November 2017
Oreo-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Nougat-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Stock N:
Code:
FAQs
1.1 Q Can you help me I have this problem?
1.1 A I will surely try to help if proper bug reporting is done as per the fashion described above.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not add any useless governors or features that I don't find practical.
1.3 Q: How do I control the kernel?
1.3 A: I recommend using EX Kernel Manager or Kernel Auditor (Both need root)
1.4 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.4 A: The kernel doesn't drain any battery unless you have overclocked it, I have kept it at stock frequencies and voltages. Use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
The various other developers for their patches (if you want a specific mention, please let me know)
All of you guys for viewing the thread
Thiago Neves @lcrd512 and Abhijeet Bohra.
Kernel source links.
8.0.0 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/oreo_caf
7.1 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/nougat_caf
7.0 Stock :
If you like my work, buy me an Appy Fizz or whatever you like
https://www.paypal.me/tywinlannister7 :good:
XDA:DevDB Information
Reviver Kernel, Kernel for the Moto G4 Plus
Contributors
tywinlannister7
Source Code: https://github.com/tywinlannister7/android_kernel_motorola_msm8952
Kernel Special Features:
Version Information
Status: Stable
Created 2017-11-28
Last Updated 2018-12-10
Screenshots
Some Screenshots
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing. ?
tywinlannister7 said:
Some Screenshots
Click to expand...
Click to collapse
Which ROM is this?
Ayan Uchiha Choudhury said:
Which ROM is this?
Click to expand...
Click to collapse
DU 12 oreo
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Thanks for the new addition in the family.
I hope this will be the favorite member of the family:laugh:
Where is the love for stock user?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
There is a link for stock rom in the op though?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
Stock version won't be released any sooner. I don't have the time for it right now and compilation process of stock kernel is a bit different than CAF kernels. Maybe before the second week of January.
briatide said:
There is a link for stock rom in the op though?
Click to expand...
Click to collapse
Empty as of now
ganeshkmr21 said:
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Click to expand...
Click to collapse
IDK I don't have the time, we already have so many ROMs available. Creating a new ROM will be adding it to the huge list already available, from AOSP to LineageOS to Dirty Unicorns. I would rather work on optimizing what we have. Quality > Quantity.
jyoti.id said:
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing.
Click to expand...
Click to collapse
Yes. 7.1 version for all N custom ROMs and 8.0 for all the O custom ROMs
DU 12 oreo
Blueman1990 said:
DU 12 oreo
Click to expand...
Click to collapse
about DU 12 oreo where can i get it ?
many thanks
i love new system
Does not boot on LOS15. Can anyone else confirm? Cant do logs cause my data port on my phone is broken. It sits on the boot screen like its loading but never fully boots.
Thank you bro!! finally an oreo kernel!
Where I can get DU 12?
Does this have color management?
And which kennel manager should i use with this?
Thanks
harshal2234 said:
Where I can get DU 12?
Click to expand...
Click to collapse
Its not out yet I guess
---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------
Ashishliterally said:
Does this have color management?
And which kennel manager should i use with this?
Thanks
Click to expand...
Click to collapse
Bro its just a 2 page thread. At least read. That question has been answered, in the OP!
Can't I get the unofficial build?
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Same for me. On LOS 14.1, XT1643
---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
I don't think so. If magisk is installed/flashed once, then no need of flashing ever again until you freshly install the rom. (AFAIK)
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
Same happened with me I was on Invicta os 8.0
########## #############
Official TWRP with prebuild Kernel is available here:
https://forum.xda-developers.com/mi-mix-2/development/recovery-twrp-3-2-1-0-xiaomi-mi-mix-2-t3780525
########################
Greetings flashaholics!
As usual before flashing this TWRP make an complete backup of your system!!!
Why another TWRP?
you'll get the latest TWRP release with most recent features & bugfixes
build live from sources - no prebuild kernels/files
more partitions to backup/restore supported
made project treble compatible by adding vendor & vendor_image partitions (leaving cust partition available for legacy purposes)
double tap to wake display
survives installation of official MIUI Global/CN ROMs (read INFO section to know how to achive that result exactly)
DOWNLOAD TWRP 3.2.3-0
... please see also supplemental infos & tool downloads below in INFO section
Please leave feedback for the beta. Does it work well? Did you encounter any problems? THX
Important changes in latest 3.2.3-0 build: 20180815-2003
based on fresh MIX 2 OmniRom base files and new msm8998 common sources - speed seems to be upgraded a little
previous changelog:
TWRP 3.2.3-0 based - build on Nextgen-Networks build environment with latest kernel 4.4.78
"FrankenTab" - mixed fstab v1 & v2 layout to achive de-/encryption and also keep as much partitions available as possible
treble compatible (by adding vendor & vendor_image partitions)
backup write speed restored (80 MB/s for file systems / 110 MB/s for imaged drives) and stayed compatible with OmniRom power/storage/kernel settings
Build completely live from latest build tree files - prebuild kernel fragments not needed anymore *yay*
en-/decryption support
ADB/MTP support
display brightness fixed - it's bright again! (see detailed notes in download section if it did not work for you)
additional partitions backup & restoreable (20 overall)
doupble tap to wake display is supported
display works when booting from LOS/OmniRom/RR to recovery via menu
survives installation of official MIUI Global/CN ROMs (OTA not tested yet)
Tested and perfectly working with ROMs as follows
MIUI 8.8.9 xiaomi.eu
MIUI 8.7.x xiaomi.eu
MIUI 8.6.x xiaomi.eu
MIUI 8.6.21 CN / xiaomi.eu
MIUI 8.6.14 Global
MIUI 8.6.8 CN
MIUI 8.5.11 Global
MIUI 8.5.8 Global / CN / xiaomi.eu
MIUI 8.5.2 Global
MIUI 8.4.26 by xiaomi.eu
LineageOS 15.1 build 20180501
OmniRom 8.1.0-20180430 HOMEMADE
INFO:
official MIUI Global/CN ROMs installation survival: dont reboot after ROM installation/update - just start a new flash session and flash latest magisk beta in a separate process - thats all! (OTA survival has not been tested by now)
If your TWRP gets constantly overwritten then flash the no-verity-opt-encrypt-1.6.zip right after your flashed TWRP to your device and right after each install/update of an original XIAOMI ROM from (en.)miui.com.
Procedure not needed for xiaomi.eu based ROMs.
Download no-verity-opt-encrypt 1.6 here
To make the flashing a little more convenient I've written a little windows script that utilizes adb/fastboot and presents all recovery images in its folder for your flashing happiness
This package also contains a script to remove/bypass the pin/passcode/pattern you've set - this could help then restoring an backup and the definitely correct pin/passcode/pattern is not accepted afterwards
Download recovery-flash.cmd 1.29 here
need an matching firmware for your device?
Download here from the Xiaomi Firmware Updater project on XDA (downloads in post 2)
Some very clarifying official information about en-/decryption types and how it works: https://source.android.com/security/encryption/
take a look here to have a full backup with internal storage covered also: [URL="https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217]Info & Download TiPatch[/URL]
For more detailed changelogs visit the download page.
Updated versions will be announced in this thread.
Instructions how to setup & build your own TWRP:
https://github.com/nextgen-networks/android_device_xiaomi_chiron-OMNI/blob/android-8.1_v10/README.md
Sourcecode (updated 2018-08-15 / v13):
Modified TWRP: https://github.com/nextgen-networks/android_bootable_recovery
Device-Tree (Device): https://github.com/nextgen-networks/android_device_xiaomi_chiron-OMNI
Device-Tree (SOC): https://github.com/nextgen-networks/android_device_xiaomi_msm8998-common
Kernel: https://github.com/omnirom/android_kernel_xiaomi_msm8998
Vendor-Tree (Device/SOC): https://github.com/DonkeyCoyote/proprietary_vendor_xiaomi
Thanks, works great so far.
As mentioned in the Lineage thread I intend to you encryption, neither the MIUI nor the iceman TWRP recoveries manage to mount my encrypted LineageOS storage, they just fail after the prompt.
Under this recovery I don't get a prompt.
Just wanted to mention, I will use it and test it anyway if encryption is not working yet, I will manage somehow.
Iam on Lineage. But after flashing TWRP not starting, only the fastboot mode
---------- Post added at 06:43 PM ---------- Previous post was at 06:36 PM ----------
https://www.nextgen-networks.de/de/...17-twrp-recovery-3-2-1-0-universal-build.html
It this the right Recovery?
Feenfleisch said:
Iam on Lineage. But after flashing TWRP not starting, only the fastboot mode
---------- Post added at 06:43 PM ---------- Previous post was at 06:36 PM ----------
https://www.nextgen-networks.de/de/...17-twrp-recovery-3-2-1-0-universal-build.html
It this the right Revolver?
Click to expand...
Click to collapse
Hey @Feenfleisch,
yes it is the correct link.
What exact commands did you use to flash TWRP?
Did the device does not boot at all or only when booting to recovery?
Only then ist booting recovery. Ich flash with Flashify
---------- Post added at 07:02 PM ---------- Previous post was at 06:57 PM ----------
The TWRP fromm the last link work (twrp-3.2.1-0-chiron_raupe-20180104-1520.img), the TWRP from your first Link not work. Maybay the wrong link?
Feenfleisch said:
Only then ist booting recovery. Ich flash with Flashify
---------- Post added at 07:02 PM ---------- Previous post was at 06:57 PM ----------
The TWRP fromm the last link work (twrp-3.2.1-0-chiron_raupe-20180104-1520.img), the TWRP from your first Link not work. Maybay the wrong link?
Click to expand...
Click to collapse
Uuuuuuups
Link leaded to Mi MIX instead of Mi MIX 2 download.
I fixed that ...
Thanks for the hint.
I've heard about several issues with flashify - better use fastboot.
USB MTP/ADB Sideload does not seem to work for me. IceMan's TWRP does.
Uploading to Google drive latest release
https://drive.google.com/file/d/1egaT1P66oEc1M0_S-tNXjG43nTLCDr3z/view?usp=drivesdk
DaCoolX said:
USB MTP/ADB Sideload does not seem to work for me. IceMan's TWRP does.
Click to expand...
Click to collapse
I'll investigate that (expect an update for this issue next week).
Thanks for reporting!
allrockedout said:
Downloads taking like 20 minutes I'll upload it to Google drive when done....
https://drive.google.com/file/d/1szvkblRyxxcVqVSqu7ejxhIkd07SUIqD/view?usp=drivesdk
Click to expand...
Click to collapse
... hmm this is very unusual - tested the speed to server and it took me a couple of seconds.
If you host the file as mirror please keep an eye for updated versions in future.
raupe said:
... hmm this is very unusual - tested the speed to server and it took me a couple of seconds.
If you host the file as mirror please keep an eye for updated versions in future.
Click to expand...
Click to collapse
Yeah I'll keep it updated of course. Plan on keeping this phone for a while. So I flashed twrp 3.2.1-0 image in twrp rebooted back into twrp..now my file storage is encrypted again. So I'll have to wipe data again... Ugh ok I'll test it out.
Cheers - downloading now.
This is vanilla TWRP right? Tired of seeing different themes, Chinese or other "customizations" in other TWRPs.
Sent from Xiaomi Mi Mix 2 @ LineageOS 14.1
I had to flash back to epic twrp. Couldn't remove encyption. After wiping data and rebooting to system than back to twrp. Everything was encrypted.
AndyYan said:
Cheers - downloading now.
This is vanilla TWRP right? Tired of seeing different themes, Chinese or other "customizations" in other TWRPs.
Sent from Xiaomi Mi Mix 2 @ LineageOS 14.1
Click to expand...
Click to collapse
Jepp this is stock/vanilla TWRP.
The only change i've made was to activate NTFS support some Qualcom specific stuff and disable the annoying "mouse" cursor that is present on default builds.
As you can read in comments (here and in Mi MIX forum) there are some hick-hacks with encryption.
This take a more deep dive because of the huge amount of variants the encryption has made from (a.k.a.: every OS build of MIUI/LOS/RR/Epic/mi-globe may use an different approach/driver for encryption).
There seems to be an problem with software and hardware encryption that conflicts with each other (see LineageOS change id 199842)
allrockedout said:
I had to flash back to epic twrp. Couldn't remove encyption. After wiping data and rebooting to system than back to twrp. Everything was encrypted.
Click to expand...
Click to collapse
Greetings @allrockedout!
Thanks for your report!
Just to figure out what leads to this behavior - could you give some information about your current firmware version, build date of the epic rom you used and what kernel the device info states?
Thanks in advance!
raupe said:
Greetings @allrockedout!
Thanks for your report!
Just to figure out what leads to this behavior - could you give some information about your current firmware version, build date of the epic rom you used and what kernel the device info states?
Thanks in advance!
Click to expand...
Click to collapse
I'm on Global Developer beta
Greetings readers!
I've build a new version today that contains some different en-/decryption libraries.
Please give it a shot and as always: Feedback is very welcome
Download: https://www.nextgen-networks.de/de/downloads/category/15-xiaomi-mi-mix-2.html
For those with touchscreen issues:
There have been made no kernel changes so dont expect any changes here.
is it suit for oreo cause my mix2 already update to 8.0, developer edition
ShawnLukeLee said:
is it suit for oreo cause my mix2 already update to 8.0, developer edition
Click to expand...
Click to collapse
Will be fine
ShawnLukeLee said:
is it suit for oreo cause my mix2 already update to 8.0, developer edition
Click to expand...
Click to collapse
Jipp, should work with 8.0/8.1 - sources used for building are 8.1 based.
I can give more detailed feedback if I'm selected for XIAOMI Android 8 global dev ROM next week.
Note: I have only tested this on Mate 10 Pro, so I don't know if it works on Mate 10. Title will stay until tested
Kernel downloads: https://github.com/Ante0/BKL_OREO_EMUI8/tree/master/releases
Source used: https://github.com/Ante0/BKL_OREO_EMUI8
Currently upstreamed to: 4.4.130
4.4.60 and above contains Blu_Active governor
Windows: https://mega.nz/#!NTgEFKiZ!4nB6QuznpI-Q4R8mtJENZ34KV4YNr6aUIlMTyTYOQcQ
Download Kernel_Pack_tool_windows.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_windows folder, open a command prompt in the extracted folder and run "pack_kernel.bat 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
Linux: https://mega.nz/#!Ne5mXATT!FXjWsnY61VewihTWagrJ09G6jv15_y4BlS_R0HDQ5UM
Download Kernel_Pack_tool_linux.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_linux folder, open a terminal in the extracted folder and run "./pack_kernel.sh 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
If you get permission errors you may have to chmod +x pack_kernel.sh and mkbootimg
UPDATE: I have changed sources to use Honor View 10 instead as camera works here (and everything else) and I'm also upstreaming it. Currently at 4.4.52: https://github.com/Ante0/BKL_OREO_EMUI8.0
Downloads will come soon. I will make a new script to change patch level instead of changing each image (from 2017-12 to 2018-09) as it takes time and space on my mega.
This does not set selinux to permissive all the time, you have to use 'setenforce 0' to enable permissive, this is to only enable it when you need it.
All this does is let us use 'setenforce' again, since Huawei decided to disable it in Oreo.
Could be useful for V4A and other sound mods, since they usually require permissive. Or anything else that could need permissive.
V4A still doesnt work with permissive, something else needs fixing
Note: This is for Security Patch level 2018-01. If yours is 2017-12 or 2018-02 you will bootloop.
This is because --os_patch_level must match ro.build.version.security_patch in /vendor/build.prop
If so you need to repack kernel and change --os_patch_level to match your version.
I will keep my github updated with security patches from Google, but if Huawei changes something in their own source it won't be in this kernel.
Mate 10/Mate 10 Pro downloads: https://mega.nz/#F!FbBBCaIS!YYH94l12su3HcsbwIqDygg
(Check Settings -> About - "Android security patch:" to get the correct patch level.
If it says 1 January 2018, download and flash 201801 kernel. 1 February 2018: 201802 and so on.)
Flash using: Fastboot flash kernel kernel.img
Mate 10 Kernel source: https://github.com/Ante0/ALP_OREO_EMUI8
Mate 10 Pro Kernel source: https://github.com/Ante0/BLA_OREO_EMUI8.0
Update 10/2: Added Wireguard support, for those who like to use VPNs.
Added some simple build scripts
Please note that portrait mode in camera has been broken with custom kernel since BLA-L29C432B137
Not working on BLA-L09, error mode boot image load failed.
Will try on ALP and report later
Edit: Failed flash due partition lenght get error
smariob said:
Will try on ALP and report later
Edit: Failed flash due partition lenght get error
Click to expand...
Click to collapse
Bordo_Bereli51 said:
Not working on BLA-L09, error mode boot image load failed.
Click to expand...
Click to collapse
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.
ante0 said:
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.
Click to expand...
Click to collapse
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?
@ante0
Thank you for the new kernel!!!
Keep up the good work dev :good::good::good:
smariob said:
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?
Click to expand...
Click to collapse
No. Kernel is separate. Magisk goes in ramdisk.
Before oreo ramdisk and kernel was merged in the boot partition, but now they're split into ramdisk and kernel partitions.
So you only need to flash kernel to kernel.
Congrats for the first Mate 10 kernel, mate![emoji482]
noob question here: setenforce 0 is written in terminal or adb? how to?
Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.
Bordo_Bereli51 said:
Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.
Click to expand...
Click to collapse
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Saadkhalid786 said:
noob question here: setenforce 0 is written in terminal or adb? how to?
Click to expand...
Click to collapse
terminal.
Or use the Magisk Module as Bordo_Bereli51 suggested.
Though if you don't have any app or something that needs permissive it's no use in running it at all times.
ante0 said:
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Click to expand...
Click to collapse
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Bordo_Bereli51 said:
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?
Click to expand...
Click to collapse
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
I am already doing that but wanted to know if he had stock but I am almost finished getting stock kernel
Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
According to Kconfig, it's not used. So there must be a vibrator elsewhere.
ante0 said:
According to Kconfig, it's not used. So there must be a vibrator elsewhere.
Click to expand...
Click to collapse
Yes, looks like that driver is disabled, but i still didn't found another vibrator/motor.
lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.
Bordo_Bereli51 said:
lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.
Click to expand...
Click to collapse
It's set to always permissive.
Edit: And for me it bootloops for some reason.
ante0 said:
It's set to always permissive.
Click to expand...
Click to collapse
Which is why I want it in order to get V4A working
I am on kangvip rom.
Bordo_Bereli51 said:
Which is why I want it in order to get V4A working
Click to expand...
Click to collapse
I've tried with permissive, doesn't work with the Magisk Modules...
You might have luck with installing to /system and /vendor manually.
Kangvip might be why the kernel is not working for you, they usually incorporate their own hacks.
Hi all!
I am NFound. I came to you from a branch ZTE Axon 7, now I will be with you :cyclops:
TWRP 3.2.3-3 by NFound
The main differences:
- Go to the latest Android 8.1.0 sources
- Full support for treble-roms
- Integrated my theme Nubia Red
- Backups are saved to the folder Nubia_Z17S
- Added the item "Resetting passwords"
- Added point on / off "Flashlight"
- Add backup /persist
- Minor edits navigation menu
- Packaged in an .exe file, the program will automatically unlock the bootloader and will flush the TWRP
Installation instructions: video instruction
Source-code:
Device
TWRP
Download
Thanks dude. Appreciate the work. Frustrating that there is no developers for the z17s. Is porting the z17 oreo official rom to z17s something that is possible?
devast8ndiscodave said:
Thanks dude. Appreciate the work. Frustrating that there is no developers for the z17s. Is porting the z17 oreo official rom to z17s something that is possible?
Click to expand...
Click to collapse
Hello! I'll see what i can do
NFound said:
Hello! I'll see what i can do
Click to expand...
Click to collapse
Can this also use on a z17 ?
aljoscha81 said:
Can this also use on a z17 ?
Click to expand...
Click to collapse
No, only Z17S
TWRP 3.2.3-2:
- Delete flag wipeui EFS and USB
NFound said:
No, only Z17S
TWRP 3.2.3-2:
- Delete flag wipeui EFS and USB
Click to expand...
Click to collapse
I ve test it on z17 and it is booting can you maybe easy compile it also for z17 that would be great cause we don't got a fully treble compatible recovery but we got a trebelized rom the mokee 81 or maybe you can guide me how to compile for z17
Preview AOSP Extended 8.1.0 FULL TREBLE on Nubia Z17S
it would be great to see for z17 nx563j too
Yes that would be very nice cause i think the only dev for treble we got on the mokee team is also gone there are long time no updates and we are there with a treble rom what is very cool many thanks so far but for a fully useable rom we need more updated vendor image for example i think i am able to boot android 9 pie aosp and pixel expirience too but with many bugs and we got no fully working treble twrp
But once again this twrp is for z17s right ?but i am able to boot it on z17 8gb128gb too and use it without problems so far touch working etc. .....
Will test it a bit longer want to make a clean install of latest mokee 81 now will report later if it work with this recovery!
NFound said:
Preview AOSP Extended 8.1.0 FULL TREBLE on Nubia Z17S
Click to expand...
Click to collapse
Finally some activity for the Z17S This Treble Rom is looking great. Is it already possible to download this rom?
Hi, thread name now says NX563J, too. No comments here and no info in your initial post about it. Does it work now for the Z17??
Update the recovery works also on nx563j superb thanks very much
NFound said:
Hello! I'll see what i can do
Click to expand...
Click to collapse
Thanks a lot the recovery is amazing im running a treble enabled 9 rom for now if you want to test for me is everything working after some user give me a hint how to solve the sound bug when you want to test here is the thread where the procedur is written
https://forum.xda-developers.com/pr...device-development/gsi-arrowos-t3835111/page5
It is in the last post
aljoscha81 said:
Thanks a lot the recovery is amazing im running a treble enabled 9 rom for now if you want to test for me is everything working after some user give me a hint how to solve the sound bug when you want to test here is the thread where the procedur is written
https://forum.xda-developers.com/pr...device-development/gsi-arrowos-t3835111/page5
It is in the last post
Click to expand...
Click to collapse
Which rom are you running now?
Update to 3.2.3-3:
- Added the ability to clean OTG-drives
- Flashlight now activates / deactivates 2 LEDs at once
- In the reboot menu, the boot loader signing and disabling encrypt on stock 7.x roms
- Added .sh script so that TWRP does not fly off after reboot to system
- Modified the theme
Download
Thanks again for this. Running android 9 now on my z17s. Much appreciated.
TWRP is very good. I have a small request to add Chinese because my English is not very good (I basically use Google Translate)
Hello,
I tried by many way to flash the recovery but It reboot in fastboot saying "no kernel (boot partition is bad)". So I flashed back my old recovery and I'm stuck here.
I've also tried the .exe and it stuck with a "waiting for devices"
Can someone help me ? My project was to flash the @NFound treble base and install Pixel Experience 9.0.
Thank you for your future responce
Jep found some system do not can hang in errors but you know maybe the wrong turn .....i found out better do never restore vendor .img but only vendor for this recovery is ......still working
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
I am on patched vendor
Got do that by myself but this vendor img is flashable and good still don't know what rro.apk works better in vendor but this used from original thresd latest in 1.2 or so and i am on from the 15.1 lineage one. ....
Sry man but this man does the .img is cool cause he owned a z17s but vendor worked with old kernel
---------- Post added at 12:34 AM ---------- Previous post was at 12:31 AM ----------
Do you can install latest gsi withit?
---------- Post added at 12:42 AM ---------- Previous post was at 12:34 AM ----------
You all don't ever try out mod kernel ? Do got faster charge.....?the device is also qc3 or?
---------- Post added at 12:49 AM ---------- Previous post was at 12:42 AM ----------
I own only z17 not s version but the dev had a 1.3 version but so not for nx563j make that a difference?......
---------- Post added at 12:50 AM ---------- Previous post was at 12:49 AM ----------
So it's for gsi......
---------- Post added at 12:58 AM ---------- Previous post was at 12:50 AM ----------
Omg this device got double front cam right that runs me out of knowledge **** i own a biT Of NoThing!........................!