[KERNEL] [blu_sp★rk r164] [OOS 2.* / CM]

Status
Not open for further replies.
Search This thread

Part.0

Senior Member
Apr 21, 2016
244
68
hello @eng.stk sir i have some questions.. if i want to backup stock kernel of oos 3.1.3 using twrp v41, so..
1. can i use the same twrp v41 to backup/restore the kernel only on oos 3.1.3. will it works ?
2. or do i need to use stock oos recovery to backup and restore kernel ?
3. if its possible to backup/restore kernel. i only need to choose kernel (boot.img) right ?

i will flash the r173 soon as i get the anwers, i need to backup first in case such problem after flashing.. thank you very much for the hard work and for your remarkable support of opx/oos!

*or anyone got the answers for me? thx
 
Last edited:

Fatsodonkey

Senior Member
Apr 22, 2011
362
55
hello @eng.stk sir i have some questions.. if i want to backup stock kernel of oos 3.1.3 using twrp v41, so..
1. can i use the same twrp v41 to backup/restore the kernel only on oos 3.1.3. will it works ?
2. or do i need to use stock oos recovery to backup and restore kernel ?
3. if its possible to backup/restore kernel. i only need to choose kernel (boot.img) right ?

i will flash the r173 soon as i get the anwers, i need to backup first in case such problem after flashing.. thank you very much for the hard work and for your remarkable support of opx/oos!

*or anyone got the answers for me? thx

I tried it and it works. Only restore boot and voila stock kernel in use. Make a full backup in case there is problems.

r173 reboots in boot animation. So it does not boot though.
 

Part.0

Senior Member
Apr 21, 2016
244
68
I tried it and it works. Only restore boot and voila stock kernel in use. Make a full backup in case there is problems.

r173 reboots in boot animation. So it does not boot though.
thank you for reply. so u have flashed the r173 and got bootloop? and you used twrp v41 to backup/restore the stock kernel? only boot.img right? thx

*can you provide logs when flashed r173, so Dev. can fix it and work on it.. thx
 
Last edited:

pwseo

Member
Dec 13, 2015
27
33
I can confirm the bootloop. Still, since I haven't rooted my phone, it's going to be hard to allow adb to work during boot, thus making it difficult for me to get relevant logs. Any ideas on this? (or, if someone actually has the logs, please provide them!)

EDIT: also, when I restored the boot partition backup with twrp, wifi didn't work, even after clearing cache, etc. I had to dirty-flash OOS 3.1.3 again. Just leaving it here in case someone has the same problem after reverting to the previous kernel.
 
Last edited:
  • Like
Reactions: Part.0

seacowx

Senior Member
May 9, 2016
446
263
I can confirm the bootloop. Still, since I haven't rooted my phone, it's going to be hard to allow adb to work during boot, thus making it difficult for me to get relevant logs. Any ideas on this? (or, if someone actually has the logs, please provide them!)

EDIT: also, when I restored the boot partition backup with twrp, wifi didn't work, even after clearing cache, etc. I had to dirty-flash OOS 3.1.3 again. Just leaving it here in case someone has the same problem after reverting to the previous kernel.
as far as I know you need to backup EFS partition alongside boot partition. EFS may contains IMEI, MaC address for wireless network which needed for Wifi to working.
and the other problem is there should be another two backup contains: modemst1, modemst2 which should be backed up along with boot partition folder. but now I couldn't find it.
I remembered with the previous 5.1.1 rom I had those two modems along with boot partition backup. I don't know if this issue related to OOS3 ROM or TWRP v41 restriction. maybe eng.stk could explain this.. tyvm.
 
Last edited:

Fatsodonkey

Senior Member
Apr 22, 2011
362
55
as far as I know you need to backup EFS partition alongside boot partition. EFS may contains IMEI, MaC address for wireless network which needed for Wifi to working.
and the other problem is there should be another two backup contains: modemst1, modemst2 which should be backed up along with boot partition folder. but now I couldn't find it.
I remembered with the previous 5.1.1 rom I had those two modems along with boot partition backup. I don't know if this issue related to OOS3 ROM or TWRP v41 restriction. maybe eng.stk could explain this.. tyvm.

Yes. Im sorry that i hesitated. Wifi does not infact work with only boot restored.
 

eng.stk

Senior Member
Mar 29, 2011
6,786
58,571
OnePlus 5T
OnePlus 6
I can confirm the bootloop. Still, since I haven't rooted my phone, it's going to be hard to allow adb to work during boot, thus making it difficult for me to get relevant logs. Any ideas on this? (or, if someone actually has the logs, please provide them!)

EDIT: also, when I restored the boot partition backup with twrp, wifi didn't work, even after clearing cache, etc. I had to dirty-flash OOS 3.1.3 again. Just leaving it here in case someone has the same problem after reverting to the previous kernel.

as far as I know you need to backup EFS partition alongside boot partition. EFS may contains IMEI, MaC address for wireless network which needed for Wifi to working.
and the other problem is there should be another two backup contains: modemst1, modemst2 which should be backed up along with boot partition folder. but now I couldn't find it.
I remembered with the previous 5.1.1 rom I had those two modems along with boot partition backup. I don't know if this issue related to OOS3 ROM or TWRP v41 restriction. maybe eng.stk could explain this.. tyvm.
All blu_spark releases modify system partition because of modules, restoring boot and system is needed (is in OP), nothing to do with EFS or any if that.

Sent from my blu_spark'd OnePlus 3 using Tapatalk
 
  • Like
Reactions: trveller72

seacowx

Senior Member
May 9, 2016
446
263
All blu_spark releases modify system partition because of modules, restoring boot and system is needed (is in OP), nothing to do with EFS or any if that.

Sent from my blu_spark'd OnePlus 3 using Tapatalk


got it. simply means dirty flash is needed.
so..any progress on r173 fixing..? as ussual it's not a demand just a wish.. tyvm for all the hard work & support on oos.
 

cktoxin

Member
Jul 18, 2013
10
13
Alright, I've tried installing version 173. Same problem as the rest are reporting: boots into the OOS3 animation for about 8 to 10 seconds then forces a restart, and this process is repeated. I've tried running a logcat with the phone connected to the computer, but it stays on 'waiting for devices.' Hence I'm having trouble getting a logcat done during the boot, I've waited for about 5 minutes, but nothing on the screen. Meanwhile, the animation into rebooting keeps looping. I've tried doing desmg, but the same thing happens: no devices are detected in my cmd screen. When I restore my Boot and System partition, the phone boots fine, and I am able to get a logcat done during boot animation. Of course, this log is useless as I am on stock OOS3 kernel.

Is there anything else I could do to help? I'm quite familiar with googling before I start posting, but I can't find any way to get a log dumped during booting (of the latest kernel). I am on OOS 3.1.3, TWRP 3.0.2-2 | bluspark v41. If you'd like me to do some other kind of logging, I'd be happy to help out, but I'll need some pointers as to how to do it.
 
Last edited:

eng.stk

Senior Member
Mar 29, 2011
6,786
58,571
OnePlus 5T
OnePlus 6
Alright, I've tried installing version 173. Same problem as the rest are reporting: boots into the OOS3 animation for about 8 to 10 seconds then forces a restart, and this process is repeated. I've tried running a logcat with the phone connected to the computer, but it stays on 'waiting for devices.' Hence I'm having trouble getting a logcat done during the boot, I've waited for about 5 minutes, but nothing on the screen. Meanwhile, the animation into rebooting keeps looping. I've tried doing desmg, but the same thing happens: no devices are detected in my cmd screen. When I restore my Boot and System partition, the phone boots fine, and I am able to get a logcat done during boot animation. Of course, this log is useless as I am on stock OOS3 kernel.

Is there anything else I could do to help? I'm quite familiar with googling before I start posting, but I can't find any way to get a log dumped during booting (of the latest kernel). I am on OOS 3.1.3, TWRP 3.0.2-2 | bluspark v41. If you'd like me to do some other kind of logging, I'd be happy to help out, but I'll need some pointers as to how to do it.

I think opx uses console-ramoops, so it should be a menu for dump it on the bootloader.
/proc/last_kmsg can be available in recovery immediately booting to twrp after the reboot I think, search for /sys/fs/pstore/console-ramoops.
I don't have the device and no time for more atm, someone posted logs awhile ago so should be possible to got those @peryndark any help mate?
 

eng.stk

Senior Member
Mar 29, 2011
6,786
58,571
OnePlus 5T
OnePlus 6
blu_sp★rk r174

All right crew!

New beta build is up for OOS 3.1.* Wicked!
This is only compatible with OOS 3.1.*, you need it already installed with new bootloader and flash it with latest TWRP bluspark v41

So, I will give this one last try. blu_spark has to many goodies and optimizations merged, is impossible to me break stuff from ground zero with quality.
I added some Oneplus changes that were missing and a fix to GCC regression @ZaneZam found :good:
Hope it works or at least someone can get some logs :fingers-crossed:
If we can't get nowhere, I'll probably drop support on the opx, I can't do much more :(


  • Same as r173
  • makefile: disable troublesome flags


Keep in mind: This is untested because I don't have the device anymore, so your milage may vary. I am only interested on debugging stuff in stable OOS, I will no longer build for custom ROMs.
Don't spam this thread with ROM problems or SuperSU not flashing, etc. Stick to kernel business.


pp-acceptance-small.png

If you like my work, donations are always welcome (but not mandatory).
Don't forget to hit thanks, it's free ;)
 
Last edited:

cktoxin

Member
Jul 18, 2013
10
13
I think opx uses console-ramoops, so it should be a menu for dump it on the bootloader.
/proc/last_kmsg can be available in recovery immediately booting to twrp after the reboot I think, search for /sys/fs/pstore/console-ramoops.
I don't have the device and no time for more atm, someone posted logs awhile ago so should be possible to got those @peryndark any help mate?

OK I tried running the command
Code:
adb shell su -c cat /sys/fs/pstore/console-ramoops > kmsg.txt

And got this in the resulting text file:
Code:
/sbin/sh: su: not found

Will this help? Anything else I should do?
 

eng.stk

Senior Member
Mar 29, 2011
6,786
58,571
OnePlus 5T
OnePlus 6
OK I tried running the command
Code:
adb shell su -c cat /sys/fs/pstore/console-ramoops > kmsg.txt

And got this in the resulting text file:
Code:
/sbin/sh: su: not found

Will this help? Anything else I should do?

You need to be rooted, if you're already in recovery all commands are made as root so you don't need su
You should cat to a rw location so you can get the file later, like > /sdcard/kmsg.txt
 

Part.0

Senior Member
Apr 21, 2016
244
68
please post results for r174. is it working? as I am away from pc so haven't do backup, and please tell the needed steps if scripts are needed to flash it properly. thanks!
 

cktoxin

Member
Jul 18, 2013
10
13
Alright, this time I ran the command

Code:
cat /proc/last_kmsg > /sdcard/kmsg.txt

Found the kmsg.txt file and it gave me this:
http://pastebin.com/yWUvST0r
Judging from the timestamps it's the correct log. Hope this helps! If anything else is needed please don't hesitate to contact me, looking forward to a working kernel! :good:

Edit: I just realised you put up v174. Will flash and report back. Don't worry, I'll try to provide logs if I can find the time!
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 252
    DWHxIK

    Kernel features:
    • Powered by Ubuntu 16.04.1 x86_64 (sparky VPS @ www.servercore.com.br - thanks @ChristianLetti)
    • Build with custom toolchain blu_naro-6.2 (cortex-a15 neon-vfpv4 hard-float targeted, build with latest Crosstool-NG from developer snapshot Linaro GCC 6.2-2016.09)
    • Full -O3 support with device and target flags enhanced, linaro build improvements, etc
    • Less is more: stockish builds based on android_kernel_oneplus_msm8974
    • Kernel compressed with XZ, custom tweaked RAMdisk with GZIP (best size/efficiency ratio, faster boot, less CPU usage)
    • Removed some debug and logging options
    • ARM enhanced performance and battery patches
    • Upstream and CAF fixes
    • Several CPU Governors (blu_active own governor is default - fastlane mode available!)
    • Voltage Control UV_mV_table (UV down to 675mV possible)
    • Enhanced TCP methods (westwood is default), Network and Wifi tweaks
    • Several I/O control (FIOPS is default), tweaked filesystems (F2FS, ExFAT, NTFS & CIFS)
    • blu_plug: Dynamic Hotplug for onyx
    • Disabled mpdecision
    • Stock thermal driver by default, custom kernel driver available (check this)
    • Optimized RWSEM, AES and SHA1 routines (with NEON support)
    • CAF adaptive LMK
    • Vibrator Strength tunable
    • KGSL fixes and reworked GPU driver (goes to idle @ 27MHz), Adreno Idler GPU Governor on by default
    • KCAL - Advanced color control for Qualcomm MDSS v2 (RGB calibration and post-processing features)
    • USB Fast Charge (USB mode up to 900mA with MTP on)
    • Battery/Notification LED control
    • Multimount fstab (you can use data and cache partitions as f2fs or ext4)
    • CDROM emulation added to mass_storage (full Drive Droid compatible)
    • init.d support (put your scripts in /system/su.d or /su.su.d [systemless SuperSU])
    • Compatible with Kernel Adiutor, Universal Kernel Manage and others

    DOWNLOAD KERNEL ZIP


    Warning: If you come from other kernel, you should dirty flash your ROM before flashing blu_sp★rk zip to avoid problems.
    Reflash ROM -> flash SuperSU -> flash blu_sp★rk.
    Also uninstall or clean data of any kernel control app you're using.

    About bugs and troubleshoots: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock OOS with NO mods whatsoever (apart from root). If you're using custom ROMs you're on your own, I'm only interested on debugging stuff in OOS.
    Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.
    Also don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" , no OT about OTAs, apps, ROM bugs and other userspace stuff. There's threads for it, use them.

    This kernel installer modifies your filesystem, backup your boot.img and system.img with TWRP if you want to go back to full stock.

    If you want to use F2FS, do the following (backup your data before attempt this, it will erase all your Data)
    • Flash latest TWRP and flash latest blu_sp★rk zip
    • Go to Wipe -> Advanced Wipe -> Select only Data -> Repair/Format File system -> Change partition type to F2FS
    • Go to Wipe -> Advanced Wipe -> Select only Cache -> Repair/Format File system -> Change partition type to F2FS
    • Reboot and profit


    pp-acceptance-medium.png

    If you like my work, donations are always welcome (but not mandatory).
    Don't forget to hit thanks, it's free ;)


    Thanks to @franciscofranco, @faux123, @LaboDJ @show-p1984, @flar2, @anarkia1976, @stratosk, @myfluxi, @Christopher83, @hellsgod, @savoca, @squid2
    Special thanks to @DariosF and @ciprianruse88, for the friendship, initial push, knowledge and webart.

    XDA:DevDB Information
    blu_sp★rk onyx, Kernel for the OnePlus X

    Contributors
    eng.stk
    Source Code: https://gitlab.com/engstk/onyx

    Kernel Special Features: Powered by sparky

    Version Information
    Status: Stable
    Current Stable Version: r164
    Stable Release Date: 2016-08-09
    Current Beta Version: r175 OOS 3.1.*
    Beta Release Date: 2016-10-10

    Created 2015-11-17
    Last Updated 2016-10-14
    105
    blu_sp★rk r74

    All right crew!

    New update is up, some nice goodies inside, go get it.
    Probably last update until OP update to OOS 2.2.0
    Also updated TWRP to blu_spark edition r9, with updated components & kernel and usable dt2w

    • makefile: use blu_naro cortex-a15 neon-vfpv4 hard-float toolchain (build with latest Crosstool-NG from developer snapshot Linaro GCC 5.3-2015.12)
    • sched/rt: Reduce rq lock contention by eliminating locking of non-feasible target
    • sched/core: Fix an SMP ordering race in try_to_wake_up() vs. schedule()
    • sched: Fix RLIMIT_RTTIME when PI-boosting to RT, Queue RT tasks to head when prio drops, Fix race in idle_balance()
    • sched/fair: Stop searching for tasks in newidle balance if there are runnable tasks
    • proc: actually make proc_fd_permission() thread-friendly, make proc_fd_permission() thread-friendly
    • mm/slub: don't wait for high-order page allocation
    • fs/buffer.c: increase the buffer-head per-CPU LRU size
    • ASoC: pcm: If pmdown_time is zero then shut down DAPM immediately
    • PM / QoS: Fix workqueue deadlock when using pm_qos_update_request_timeout()
    • cpufreq: ondemand: even if it's not being used it spawns uninterruptible threads
    • timer: Prevent overflow in apply_slack
    • bluetooth: Validate socket address length in sco_sock_bind().
    • net: add validation for the socket syscall protocol argument
    • md: use kzalloc() when bitmap is disabled
    • ipv6: addrconf: validate new MTU before applying it
    • pagemap: do not leak physical addresses to non-privileged userspace
    • wlan: Address buffer overflow due to invalid length

    If you like my work, don't forget to hit thanks :good:
    88
    blu_spark r61

    All right crew!
    New build is up, lot's of nice upstream & CAF updates/improvements, also some goodies from hammerhead marshmallow :cool:

    • defconfig: remove SysV IPC from kernel, remove some debug
    • Failed to load kernel modules
    • msm: ipc_socket: fix leak of kernel memory to userspace
    • Input: optimize events_per_packet count calculation, fix defuzzing logic
    • soc: qcom: smd: Fix SMD packet sync loss issue
    • vidc: Initialize kernel space stack variables, disable CPU L2 cache PC during video sessions
    • net: add length argument to skb_copy_and_csum_datagram_iovec
    • memory hotplug: fix invalid memory access caused by stale kswapd pointer
    • mm: consider all swapped back pages in used-once logic
    • bam_dmux: Fix spinlock lock-up
    • tty: fix memleak in alloc_pid
    • msm: kgsl: Keep the GPU from going into a slumber after a touch event, Do not detect faults when GPU core is idle, Fix Z180 memory leak, set the correct max_state
    • genirq: Sanitize spurious interrupt detection of threaded irqs
    • futex: Prevent attaching to kernel threads
    • hrtimer: Set expiry time before switch_hrtimer_base(), Prevent remote enqueue of leftmost timers, Prevent all reprogramming if hang detected
    • Revert "cpufreq: make the "scaling_cur_freq" sysfs entry pollable"
    • ARM: 7685/1: delay: use private ticks_per_jiffy field for timer-based delay ops
    • ARM: 7653/2: do not scale loops_per_jiffy when using a constant delay clock
    • ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp
    • qup_i2c: Initialize I2C resource before registering.
    • lib: cpu_rmap: avoid flushing all workqueues
    • cpufreq: Protect against hotplug in cpufreq_register_driver()
    • rcu: Yield simpler
    • printk: remove unused code from kernel/printk.c
    • wlan: just shut up...
    • ASoC: msm: qdsp6v2: Silence some noise

    If you like my work, don't forget to hit thanks ;)
    75
    blu_sp★rk r79

    All right crew!

    Since seems likely to OOS 2.2.0 come in February (OP definition of early January lol), I decided to release a new kernel build with some nice improvements.
    Also updated TWRP to blu_spark edition v11.
    You need to update to new TWRP v11 to use with kernel blu_spark r79 (because of f2fs changes in kernel)

    • makefile: use newest and improved blu_naro-5.3, build from developer snapshot Linaro GCC 5.3-2016.01, with updated components and improvements/fixes
    • net: inet_diag: zero out uninitialized idiag_{src,dst} fields
    • UPSTREAM: include/linux/poison.h: fix LIST_POISON{1,2} offset
    • sysfs: check if one entry has been removed before freeing
    • mm: vmscan: support complete shrinker reclaim
    • mm: fix prctl_set_vma_anon_name
    • f2fs: update from msm8974 upstream, catch up to v4.4-rc1
    • defconfig: update f2fs extensions
    • small ramdisk tweaks and fixes

    If you like my work, don't forget to hit thanks :good:
    73
    It's up!

    All right crew!

    Some of you may know me from Nexus and other devices development in Code_Blue and blu_spark projects.
    I decided to release the first kernel for my newest device, the OnePlus X.

    I manage to do a nice and stable base, keep in mind that more stuff will come in the future, patience is a virtue ;)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone