(Series 2 Release 4)
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
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.
*
*/
http://www.cmxlog.com/12
Before you install make sure to do a factory reset. First boot after install can leave your device at a black screen for up to 5 minutes. Be patient.
Not working:
Radio is probably working now but I can't test that functionality.
Downloads
Mod edit: links removed, project has been abandoned.
Source code
* CyanogenMod
https://github.com/CyanogenMod
* Device specific repos
https://github.com/eousphoros/android_device_samsung_klimtlte.git
Credits:
@crpalmer for his work porting cm12 to the picassowifi. It was of great help getting cm12 on the sm t700/t705
@nvertigo67 && @UpInTheAir for their kernel magic and misc fixes
Unofficial Build instructions
Code:
# [ -e /usr/lib/apt/methods/https ] || {
apt-get update
apt-get install apt-transport-https
}
# apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9
# sh -c "echo deb https://get.docker.com/ubuntu docker main\
> /etc/apt/sources.list.d/docker.list"
# apt-get update
# apt-get install lxc-docker
# git clone https://github.com/stucki/docker-cyanogenmod.git
# cd docker-cyanogenmod
# ./run.sh
# repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
# repo sync
# source build/envsetup.sh
# breakfast klimtwifi
// you will need to extract the binary blobs from your device.
# git clone https://github.com/eousphoros/android_device_samsung_klimtlte.git device/samsung/klimtlte
# brunch klimtlte 2> errors
Great!!!! Thank you man, this is awesome!!!:good:
Dowloading.....
Fwiw the biggest change other then the addition of the radio I've noticed is the t705 has a different partition layout then the t700. (System/UserData) are different sizes.
eousphoros said:
Fwiw the biggest change other then the addition of the radio I've noticed is the t705 has a different partition layout then the t700. (System/UserData) are different sizes.
Click to expand...
Click to collapse
Ahhhhh that was why when t705 users flashed the t700 lollipop zip file,it ended up with an error saying that partition cannot be mounted
Trach said:
Ahhhhh that was why when t705 users flashed the t700 lollipop zip file,it ended up with an error saying that partition cannot be mounted
Click to expand...
Click to collapse
Yep. The silly thing is its only a couple megabyte difference. Not sure why samsung decided to do it like that.
eousphoros said:
Yep. The silly thing is its only a couple megabyte difference. Not sure why samsung decided to do it like that.
Click to expand...
Click to collapse
I have a theory about that
And thanks for upgrading my T705!
Please make a cm 12 for t805
mohammadkh2 said:
Please make a cm 12 for t805
Click to expand...
Click to collapse
If someone sends me a device.
In other news.
<6>[ 4.030565] [B1: cbd: 2382] mif: misc_ioctl: umts_boot0: IOCTL_MODEM_ON
No mobile data?
Does no Radio related functions mean no mobile data and Wifi?
eousphoros said:
Yep. The silly thing is its only a couple megabyte difference. Not sure why samsung decided to do it like that.
Click to expand...
Click to collapse
Trach said:
Ahhhhh that was why when t705 users flashed the t700 lollipop zip file,it ended up with an error saying that partition cannot be mounted
Click to expand...
Click to collapse
I tried last night to flash this first build with TWRP 2.8.5 and I got error saying that partition cannot be mounted; does it happend also if I use the Cyanogen Recovery?
sandrixroma said:
I tried last night to flash this first build with TWRP 2.8.5 and I got error saying that partition cannot be mounted; does it happend also if I use the Cyanogen Recovery?
Click to expand...
Click to collapse
Nope the Cm recovery is for the 705
Gesendet von meinem klte mit Tapatalk
hiowa93 said:
Nope the Cm recovery is for the 705
Gesendet von meinem klte mit Tapatalk
Click to expand...
Click to collapse
I thought that also TWRP was made for T705, I succesfully flash many rom (CM11, Iron,...). Ok, this evening I'll try the CM Recovery, thank you!
Change log
Is there a change log, to see what has changed since the last release?
Radio related functions
Data and call not work
Official T700 CM12 http://download.cyanogenmod.com/?device=klimtwifi
But What this? http://download.cyanogenmod.com/?device=klte not for T705?
dlw starting...i'll back soon!
Ths
B
Will it work if I flash the CM recovery using Flashify?
sandrixroma said:
I tried last night to flash this first build with TWRP 2.8.5 and I got error saying that partition cannot be mounted; does it happend also if I use the Cyanogen Recovery?
Click to expand...
Click to collapse
You will probably need to use a klimtlte recovery.
godraxe said:
Data and call not work
Official T700 CM12 http://download.cyanogenmod.com/?device=klimtwifi
But What this? http://download.cyanogenmod.com/?device=klte not for T705?
Click to expand...
Click to collapse
Like I said in the first post radio related functions are not working in this first build.
walkerl said:
Is there a change log, to see what has changed since the last release?
Click to expand...
Click to collapse
There is no last release. That is what series 1 release 1 means. You are welcome to look at my github to see the changes between klimtwifi and klimtlte so far.
What did you do re write the partition table? Is it possible to do what you've done to the 805
jonnycarter said:
What did you do re write the partition table? Is it possible to do what you've done to the 805
Click to expand...
Click to collapse
I didn't rewrite the partition table. Instead I just corrected the values in the make files for klimtlte. As for the 805 I believe there is someone else working on that device.
Can you provide a link or a reference for this other person please. Appreciated muchly.
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Disclaimer:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you. Hard. A lot.
*/
These are 32-bit CyanogenMod 12 builds.
They will be obsolete when official nightlies are available.
Quickly created from the 'cm-11.0' sources, because we can, and it's fun!
Downloads:
https://basketbuild.com/devs/cdesai/cm
What doesn't work:
Dual SIM (Single SIM operation is fine)
FM Radio (no audio)
All major hardware features are mostly working just fine, unless mentioned above.
Installation:
Backup your data
Install it from recovery
Optionally install the Google Addon
Reporting Bugs:
You are allowed to report bugs only in this thread. Note that this is a preview release and non-device specific bugs will not be accepted. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the build again to get rid of the modifications before reporting.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Credits:
Myself, varunchitre15 and everyone else involved in coding and debugging.
XDA:DevDB Information
CyanogenMod 12, ROM for the YU Yureka
Contributors
cdesai, varun.chitre15
Source Code: https://github.com/chirayudesai/android_kernel_yu_msm8916
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: First / Shipping build
Version Information
Status: Testing
Created 2015-02-28
Last Updated 2015-02-28
Reserved for changelog
The build is pretty old.. and has the Phone UI bug..
When can we expect another build..?
varun.chitre15 said:
Reserved for changelog
Click to expand...
Click to collapse
Dev
How about 64bit??
for me single sim also not working.............and not rooted
zeetherocker said:
The build is pretty old.. and has the Phone UI bug..
When can we expect another build..?
Click to expand...
Click to collapse
Yeah, this was what we had right now, but a new build will come as soon as either of us (me or Varun) find some time to build and test.
RajGopi said:
Dev
How about 64bit??
Click to expand...
Click to collapse
You'll have to wait for the official update for that.
sharan565 said:
for me single sim also not working.............and not rooted
Click to expand...
Click to collapse
You need to flash the older baseband (from the factory images, dated Dec 5. 2014.)
The newer version that shipped with the latest OTA doesn't work.
cdesai said:
Yeah, this was what we had right now, but a new build will come as soon as either of us (me or Varun) find some time to build and test.
Click to expand...
Click to collapse
Could you release the device sources so that we could have a look at them and try solving those Phone UI problems.. I know you are concerned about people cooking various roms with unfinished sources.. but is there a way you can provide sources to the devs who wanna help?
@cdesai @varun.chitre15
I'd really appreciate it if you released your sources.. Otherwise can guys please help us out with our sources.. I could really use some help with ril.. got the Sim working with incoming calls and messaging working perfectly but outgoing calls have a problem.. I could really use some help..
Link to my repo : https://github.com/zeetherocker/android_device_yu_tomato
Hoping for a positive reply thank you..
zeetherocker said:
The build is pretty old.. and has the Phone UI bug..
When can we expect another build..?
Click to expand...
Click to collapse
make a script and execute via script manager (with su and boot option enabled)
Code:
#!/system/bin/sh
chown system /sys/devices/virtual/touchscreen/touchscreen_dev/gesture_ctrl
chgrp radio /sys/devices/virtual/touchscreen/touchscreen_dev/gesture_ctrl
cdesai said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Disclaimer:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you. Hard. A lot.
*/
These are 32-bit CyanogenMod 12 builds.
They will be obsolete when official nightlies are available.
Quickly created from the 'cm-11.0' sources, because we can, and it's fun!
Downloads:
https://basketbuild.com/devs/cdesai/cm
What doesn't work:
Dual SIM (Single SIM operation is fine)
FM Radio (no audio)
All major hardware features are mostly working just fine, unless mentioned above.
Installation:
Backup your data
Install it from recovery
Optionally install the Google Addon
Reporting Bugs:
You are allowed to report bugs only in this thread. Note that this is a preview release and non-device specific bugs will not be accepted. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the build again to get rid of the modifications before reporting.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Credits:
Myself, varunchitre15 and everyone else involved in coding and debugging.
XDA:DevDB Information
CyanogenMod 12, ROM for the YU Yureka
Contributors
cdesai, varun.chitre15
Source Code: https://github.com/chirayudesai/android_kernel_yu_msm8916
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: First / Shipping build
Version Information
Status: Testing
Created 2015-02-28
Last Updated 2015-02-28
Click to expand...
Click to collapse
A few weeks ago I was able to successfully flash this ROM..but when I tried it today it gave me bootloop frequently..can anyone tell me what is the reason....I wiped all the data..cache..dalvik cache before flashing this
SWAP3093 said:
A few weeks ago I was able to successfully flash this ROM..but when I tried it today it gave me bootloop frequently..can anyone tell me what is the reason....I wiped all the data..cache..dalvik cache before flashing this
Click to expand...
Click to collapse
come on man! don't quote the whole thing.
and try flashing again also by wiping your /deta/media (will wipe all your data on internal memory like pics etc.)
abhifx said:
come on man! don't quote the whole thing.
and try flashing again also by wiping your /deta/media (will wipe all your data on internal memory like pics etc.)
Click to expand...
Click to collapse
I tried multiple times..wiped everything....tried different recoveries also..still it bootloops..and sorry for that whole quoting if it gave u trouble
SWAP3093 said:
I tried multiple times..wiped everything....tried different recoveries also..still it bootloops..and sorry for that whole quoting if it gave u trouble
Click to expand...
Click to collapse
you are wiping /data only. i was talking about wiping /data/media too as the file system might be getting corrupt resulting in boot loop.
for best result i suggest you fastboot to stock rom and try again. this is more of a sure shot but long cut method.
abhifx said:
you are wiping /data only. i was talking about wiping /data/media too as the file system might be getting corrupt resulting in boot loop.
for best result i suggest you fastboot to stock rom and try again. this is more of a sure shot but long cut method.
Click to expand...
Click to collapse
FYI..I am on a stock rom only..& TWRP recovery flashed..I wiped everything except internal & external storage
cdesai,can you please list out what's working and what's not..?
I know that you had already posted that info i this thread,but i read issues like baseband not working,after installing some of the user got erased their IMEI numbers and problems in outgoing calls as well.
So help me clearing my queries.
If i install the rom what would be the effect i.e. Internal Memory Erased along with photos and installed apps,Root access removed etc.
Thank you in advanced....
Nothing wrong will happen,just flash the rom and flash the 5 dec baseband (google it)and pa lollipop gapps, or better wait for the official update which is rolling on 26 as per the news.
Sent from my Redmi 1S using XDA Free mobile app
or you can wait as soak tests are starting for 64 builds ,refer to yu forums
hello bro when you gonna update this rom......
plz provide bug fixes asap....
shomil49 said:
hello bro when you gonna update this rom......
plz provide bug fixes asap....
Click to expand...
Click to collapse
update???
when yu releases the cm12 ok
and if bugs were this easy,i think i was running cm12 now
just be patient bro.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), 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.
*
*/
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.
These are last known stable builds from work done by qsnc. Latest commits do not work, so I have reverted them to last working point.
Download link : Blog
XDA:DevDB Information
CyanogenMod, ROM for the Sony Xperia Z
Contributors
Daedroza, qsnc
Source Code: https://github.com/daedroza
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-06-29
Last Updated 2016-06-29
Reserved
I tested your build but have bootloop after clean install. Even recovery is not working and I needed to flash boot image from first vanir rom to restore my phone from a backup.
Sent from my c6606 using XDA-Developers mobile app
krisberck said:
I tested your build but have bootloop after clean install. Even recovery is not working and I needed to flash boot image from first vanir rom to restore my phone from a backup.
Sent from my c6606 using XDA-Developers mobile app
Click to expand...
Click to collapse
Same here...
rom requirements?
krisberck said:
I tested your build but have bootloop after clean install. Even recovery is not working and I needed to flash boot image from first vanir rom to restore my phone from a backup.
Sent from my c6606 using XDA-Developers mobile app
Click to expand...
Click to collapse
There are three packages for dogo, odin and yuga. Did you flash yuga package?
New build will be up within 2 hour...
BTW once I get stable device tree for yuga ( dogo is already done as I have the device )....
----- EDIT ---
Found my mistake...
I will work on vanir too tonight as promised
Ahsan008 said:
There are three packages for dogo, odin and yuga. Did you flash yuga package?
Click to expand...
Click to collapse
Of course
Daedroza said:
New build will be up within 2 hour...
BTW once I get stable device tree for yuga ( dogo is already done as I have the device )....
Click to expand...
Click to collapse
Thanks man you made Z fly again
New build is up!
Let me know if any issues...
New build is working. Call also I will test it and report if any problems.
krisberck said:
New build is working. Call also I will test it and report if any problems.
Click to expand...
Click to collapse
And how's it?
DahakePL said:
And how's it?
Click to expand...
Click to collapse
Very good no bugs for now. I will report battery life after 2-4 days of usage.
krisberck said:
Very good no bugs for now. I will report battery life after 2-4 days of usage.
Click to expand...
Click to collapse
And In call audio and mic working?
DahakePL said:
And In call audio and mic working?
Click to expand...
Click to collapse
Yes
Thats Big great News for me. No Bugs?? No reboots? No Call Bugs? No Storage error?No freeze?? I cant believe it . How Update this rom? Via cm download OTA or from the Thread
You need to clean install it. Wipe cache dalvik, data, internal storage from twrp recovery and flash it. You can also download and flash latest pico open gapps. I am using this rom for a couple of hours and no problem so far.
Sent from my Xperia Z using XDA-Developers mobile app
Hey it works pretty good
I flashed it a hour ago and still going strong
EDIT: Works really good, no bugs yet
EDIT2: Calls work fine for now
DahakePL said:
Hey it works pretty good
I flashed it a hour ago and still going strong
EDIT: Works really good, no bugs yet
EDIT2: Calls work fine for now
Click to expand...
Click to collapse
What about battery?
Airless Kernel works?
Kuciak said:
What about battery?
Airless Kernel works?
Click to expand...
Click to collapse
I'm using airless now and no problems.
Battery needs testing
Custom TWRP (TeamWin Recovery Project) Builds for Samsung Galaxy Note 4
Disclaimer:
Code:
/*
*
* Your warranty is now void.
*
* I am 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 recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Fork of TWRP:
This UNOFFICIAL TWRP recovery is built for Samsung Galaxy Note 4 Snapdragon variants in EmotionOS/LineageOS Android 7.1.1 Nougat tree with correct device-specific SELinux policy. It fixed some warnings/errors and differs from the OFFICIAL TWRP in the following ways:
Designed to be built with LineageOS 14.1 only
Customize the mksh prompt and environment by editing mksh/mkshrc
Require fstab v2 syntax
Use external repositories for pigz, exfat, fuse
Power key toggles screen on/off
SuperSU and HTC Dumlock have been removed
Other customizations (see change history)
You can get the OFFICIAL TWRP recovery for Verizon Samsung Galaxy Note 4 (SM-N910V) from here. Other devices can find their variants in the device-specific forums.
Click to expand...
Click to collapse
Versioning:
To help distinguish builds of recovery made from this fork, the minor version digit is replaced with N#. Minor version increments will be handled as needed, independent of TWRP. The major and semi-major version digits follow upstream to roughly indicate feature parity (as close as possible with a fork, anyways).
Click to expand...
Click to collapse
Downloads:
Custom TWRP Builds for Samsung Galaxy Note 4
Click to expand...
Click to collapse
XDA:DevDB Information
TWRP, ROM for the Verizon Samsung Galaxy Note 4
Contributors
hsbadr
Source Code: https://github.com/mdmower/twrp
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Current Stable Version: 3.0.N1-20170205
Stable Release Date: 2017-02-05
Created 2017-02-05
Last Updated 2017-02-05
Reserved
Reserved
Is this twrp required or recommended for your Emo-14.1 builds?
I've found a little bug.
When flashing (there were 3 files added to flash) I turned off the screen using the power button.
After that pressing back the power button vibrated but remained with the screen off, touching the screen had the same effect.
I just waited and turned the phone off.
Next time I flashed the same things without press the power button to turn off the screen and worked fine, even though the screen went off automatically.
razholio said:
Is this twrp required or recommended for your Emo-14.1 builds?
Click to expand...
Click to collapse
Curious about this myself.. and will it affect going back to other ROMs?
how is this different from the TWRP 3.0.2 I am running now on my device? or is this ONLY to flash nougat ROMS?
Delete
TWRP themes dont seem to work with this.
so how exactly would you flash the tar?
6th_Hokage said:
so how exactly would you flash the tar?
Click to expand...
Click to collapse
.tar files are flashed in Odin. You can download the.img custom recovery and flash it in official TWRPapp from the link above
Sent from my Samsung SM-N910G using XDA Labs
Did anyone find the answer to the question whether this had to be used, or just recommended? Also can you use that same recovery to flash other roms?
scottsdca said:
Did anyone find the answer to the question whether this had to be used, or just recommended? Also can you use that same recovery to flash other roms?
Click to expand...
Click to collapse
Well I can confirm official twrp still works for 2/5 and 2/13 ROMs.
Every time I try to install emotionrom it never recognizes my sim, so I'm not sure if it's because I'm not using the right twrp.
Hi, does this comment "* Require fstab v2 syntax" mean we may have issues flashing Roms that are not LineageOS or EmotionOS? (ie touchwiz)
Sent from my SM-N9200 using Tapatalk
IndyRoadie said:
Curious about this myself.. and will it affect going back to other ROMs?
Click to expand...
Click to collapse
happy2472 said:
how is this different from the TWRP 3.0.2 I am running now on my device? or is this ONLY to flash nougat ROMS?
Click to expand...
Click to collapse
scottsdca said:
Did anyone find the answer to the question whether this had to be used, or just recommended? Also can you use that same recovery to flash other roms?
Click to expand...
Click to collapse
fastguy said:
Hi, does this comment "* Require fstab v2 syntax" mean we may have issues flashing Roms that are not LineageOS or EmotionOS? (ie touchwiz)
Sent from my SM-N9200 using Tapatalk
Click to expand...
Click to collapse
Inquiring minds want to know
IndyRoadie said:
Inquiring minds want to know
Click to expand...
Click to collapse
Same questions here
Stuck in a bootloop on 910T...can't even boot into system.
TWRP issue on 910F
I've hit a bug with VERSION twrp-3.0.N1-20170205-UNOFFICIAL-trltexx.tar. Every time I flush with this recovery i get an encryption failed error. I've had to revert back to twrp-3.0.2-0-treltexx in order to flush my ROMs. Hope this helps someone out there.
I successfully loaded LineageOS 14.1 (Android 7.1.1) using a standard TWRP build (found on their Devices page) - I never knew about this build.
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
WhitePugKernel by joe2k01
This kernel is only for AOSP base ROMs: AOSPExtended, LineageOS etc
How to install:
Download the flashable zip
Download (Oreo) the flashable zip
Boot in TWRP
Flash zip
Reboot and you're done
Feautures:
Added blu active governor
ZRAM support with LZ4 compression
XZ and LZO kernel compression support
XBOX joypad support(untested)
MSDOS fylesystem support
NTFS filesystem support
NTFS writing support
HFS filesystem support
HFS+ filesystem support
zen I/O scheduler
maple I/O scheduler
Option to disable fsync
Various optimizations
Donate to IARC or SaveTheChildren
https://www.iarc.fr/en/about/donations.php
http://www.savethechildren.org
Downloads:
V1: Download
V2: Download
V3: Download
V4: Download
V5: Download
XDA:DevDB Information
WhitePugKernel for the Galaxy Tab S2 WIFI 2016, Kernel for the Samsung Galaxy Tab S2
Contributors
joe2k01
Source Code: https://github.com/joe2k01/WhitePugKernel-samsung_msm8976
Kernel Special Features:
Version Information
Status: Stable
Created 2017-06-20
Last Updated 2017-11-13
thanks!! I´ll try it today
Is this for the 713 or 813?
Edit: I dug into the code... For the 813.
New build is up :fingers-crossed:
Changelog:
zen I/O scheduler
sio I/O scheduler
fiops I/O scheduler
Option to disable fsync
Fixing credits in repo, will fix OP later
joe2k01 said:
Fixing credits in repo, will fix OP later
Click to expand...
Click to collapse
What kernel manager do you suggest?
preference said:
What kernel manager do you suggest?
Click to expand...
Click to collapse
Kernel adiutor and LSpeed
When I try to flash both versions, I get error code 1 (something about a failure to repack the zip), Any idea what I'm doing wrong? I'm running the latest build of AOSP Extended.
Sraichvold said:
When I try to flash both versions, I get error code 1 (something about a failure to repack the zip), Any idea what I'm doing wrong? I'm running the latest build of AOSP Extended.
Click to expand...
Click to collapse
Can you send a screenshot of TWRP flash log?
Why do you have reverted this ?
https://github.com/joe2k01/WhitePug...mmit/0b880e9d5aecc5d3d56dc7d2599ebe89856d640b
It's an important change, please correct your merge conflict instead revert all
scafroglia93 said:
Why do you have reverted this ?
https://github.com/joe2k01/WhitePug...mmit/0b880e9d5aecc5d3d56dc7d2599ebe89856d640b
It's an important change, please correct your merge conflict instead revert all
Click to expand...
Click to collapse
This change hasn't been published in a build, so it's a WIP. Be sure that you are in the right before posting please
joe2k01 said:
This change hasn't been published in a build, so it's a WIP. Be sure that you are in the right before posting please
Click to expand...
Click to collapse
Please correct autorship of this kernel
scafroglia93 said:
Please correct autorship of this kernel
Click to expand...
Click to collapse
Almost everything correct, just need to adjust last 2 or 3 commits
joe2k01 said:
Can you send a screenshot of TWRP flash log?
Click to expand...
Click to collapse
Is this what you need? (and thanks for replying)
Sraichvold said:
Is this what you need? (and thanks for replying)
Click to expand...
Click to collapse
Will try to fix this ASAP
joe2k01 said:
Will try to fix this ASAP
Click to expand...
Click to collapse
Thank you! I'm looking forward to using your kernel!
Hi, I just made a tg group for my kernels users. Here is link http://t.me/WhitePugKernels
Sraichvold said:
Thank you! I'm looking forward to using your kernel!
Click to expand...
Click to collapse
Did you retry to flash after a reboot? If yes and no success can you try this:
Boot in recovery
Flash zip
Open a shell and type: cd /tmp/anykernel && ./anykernel.sh
Post output here
joe2k01 said:
Did you retry to flash after a reboot? If yes and no success can you try this:
Boot in recovery
Flash zip
Open a shell and type: cd /tmp/anykernel && ./anykernel.sh
Post output here
Click to expand...
Click to collapse
Here's what I get.
Sraichvold said:
Here's what I get.
Click to expand...
Click to collapse
Thank you. Did you flash any mod to the boot image. You are on AEX right? Are you sure you are flashing only V2?
Disclaimer:
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.
*
*/
This is the first compile of LineageOS 17.1, note it might not boot.
Download:
https://www.androidfilehost.com/?fid=8889791610682913956
Also, this should run on cmi, but not too sure atm.
Kernel source: Xiaomi Mi 10 prebuilt kernel + umi-q-oss kernel for kernel headers
Currently, it is not booting, we are rebasing it to see if it works then.
could it work on umi(mi 10 pro)?
alpaca2333 said:
could it work on umi(mi 10 pro)?
Click to expand...
Click to collapse
Code:
Also, this should run on cmi, but not too sure atm.
Should work, but I don't think we are done with init codes yet.
TipzTeam said:
Code:
Also, this should run on cmi, but not too sure atm.
Should work, but I don't think we are done with init codes yet.
Click to expand...
Click to collapse
expecting your work with hope!
by the way, is the problem with cmi's kernel booting resolved?
alpaca2333 said:
expecting your work with hope!
by the way, is the problem with cmi's kernel booting resolved?
Click to expand...
Click to collapse
Not yet
Good work!
Nice to see some movement in rom developing. Looking forward for everything what comes. Keep up the good work :good:
After the flash of the umi is finished, it will automatically restart to FastBoot ，The question should come from boot.img
Not working. Rebooting to fastboot after installing.
peluillo said:
Not working. Rebooting to fastboot after installing.
Click to expand...
Click to collapse
Try wipe data from twrp
Boot to fastboot
Even i Wiped data and cach
Note:
When rom is installing i se red line say can't maunting partions or something like that
Bootloop
Wysłane z mojego Mi 10 przy użyciu Tapatalka
Does anyone have any idea which recovery is currently the best? I'm currently using recovery-TWRP-3.4.2B-0623-XIAOMI10-CN-wzsx150.img, but nothing works with it either because it can't find the system partion.
Not working,but thank you.
Manaplayer said:
Does anyone have any idea which recovery is currently the best? I'm currently using recovery-TWRP-3.4.2B-0623-XIAOMI10-CN-wzsx150.img, but nothing works with it either because it can't find the system partion.
Click to expand...
Click to collapse
im using 13/3 an decryption an Mount system works
I can choose mount system too, but as selection "wipe system" - there is no system partion chooseable.
Boots directly into fastboot.
Manaplayer said:
Does anyone have any idea which recovery is currently the best? I'm currently using recovery-TWRP-3.4.2B-0623-XIAOMI10-CN-wzsx150.img, but nothing works with it either because it can't find the system partion.
Click to expand...
Click to collapse
I'm using the latest LR Team TWRP for my Mi 10. Its not recommended due to closed source, but it's the only one which handles everything right.
Basecatcherz said:
I'm using the latest LR Team TWRP for my Mi 10. Its not recommended due to closed source, but it's the only one which handles everything right.
Click to expand...
Click to collapse
Can you give me a link to get this? Thank you!
That recovery-TWRP-3.4.2B-0623-XIAOMI10-CN-wzsx150.img is a recovery from the LR-Team, but i don't know if it is the latest one.