Related
Hi Galaxy SII gurus
I run "intratech" 'official stock firmware' with corresponding
"cf-root", I have done so for various gingerbread and I am doing now
for various ICS.
currently
GT-I9100_XEN_I9100XWLPD_I9100XXLPW_I9100XENLP5.tar.md5
CF-Root-SGS2_XX_NEE_LPD-v5.5-CWM5.zip
Once system is stable it runs stable for days/weeks, -but-, my
problem (as also mentioned in xda thread 1635302) is that, when I boot
(this problem has been there with gingerbread and is still there with
ICS):
- system_server uses CPU (load and temperature rise)
- watchdog kills android processes (linux kernel stays up)
and, this goes on in a loop, often for hours. I need to power off and
try again (say, next day when battery again charged and temperature
dropped).
Only with -much- luck it happens that the system boots to a cam
state. and then I can use the phone normally. In fact, it works
perfectly then.
Recently this problem seems to become more prevalent and I have not
been able to use the phone for several days (each time I boot it goes
into, and, not out of, the watchdog loop). In practice, what happens
is that
- all applications (including launcher die)
- system goes back to the animated samsung logo
this loop goes on.
I searched a bit and it seems other people have reported this too but
I don't find a solution. Any help is appreciated.
'top', right after boot
Mem: 824396K used, 26136K free, 0K shrd, 36632K buff, 250616K cached
CPU: 53.1% usr 0.9% sys 0.0% nic 45.7% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 2.84 1.85 0.74 2/1595 6055
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
2082 1830 system S 401m 48.2 0 52.4 system_server
5628 1830 app_208 R 297m 35.8 0 0.5 berserker.android.apps.sshdroidpro
...
I use ssh and rsync to backup to a linux server, so I have a some
files that may be of interest (note that ssh and rsync are not killed
so I can incrementally backup).
/data/log/ contains a file
-rw------- 1 1000 1000 677553 Jun 5 06:07 dumpstate_sys_watchdog.txt.gz
/data/system/dropbox/ -many- files (presumably one per loop)
-rw------- 1 1000 1000 14416 Jun 5 06:07 [email protected]
-rw------- 1 1000 1000 0 Jun 5 06:08 [email protected]
-rw------- 1 1000 1000 261 Jun 5 06:08 [email protected]
for example, I have these files 58 times on 'Jun 5 ' only.
I have captured dmesg and logcat in a file screenlog.txt as follows
- freshly booted phone
- do a first 'dmesg'
- start 'logcat'
- start google play market app and update 2 apps
**** watchdog ****
- wait a bit
- do another 'dmesg'
The information is somewhat overwhelming but one can 'grep' for
watchdog, temperature and system_server processes 2082 and 7102, and
what else..., like, it seems cpu1 turns off/on all the time after
watchdog. Also, sorting the logs gives nice view per category.
Again any help is appreciated!
Thanks
Hi everybody
I feel a bit ashamed to reply my own post, but, here is what I can say
about progress:
I have (in approximately one week) once been able to get a 100% stable
system, but then, after some hours/day of playing around, time came to
reboot, and, since then, I am in the same system_server watchdog loop
for days now: I can do a little bit of work (I am configuring apex
GIU) and then: 'the watchdog barks'.
Searching Google does not tell me enough about this system_server
watchdog boot loop situation, so I hope for rescue here.
Note that I use stock rom with just cf-root.
have a good weekend
ok then, hate to reply again ...
seems a cwm wipe of dalvik cache and regular cache can do wonders:
I booted into stable system again
spoke too soon :-( android boot loop again
here is my guess: I think SD card might have errors ...
final verdict: only complete wipe and reinstall works, (and it works)
however, having literally wiped and formatted nearly everything, ...
only heimdall could flash (others did no longer recognise GSII).
all runs well now (albeit with less apps and less data)
Hello all,
I got a Sony Xperia P (LT22i) last christmas and I have been using a freexperia built ROM ever since. The ROM uses a Cyanogenmod 4.0.4 internally. Unfortunately my phone is often quite slow to respond to user input up to the point where it doesnt even unlock the screen when I press the button. If I use htop via adb I see the following:
Mem: 798852K used, 21644K free, 0K shrd, 17748K buff, 306296K cached
CPU: 56.3% usr 38.9% sys 2.9% nic 0.5% idle 0.0% io 0.0% irq 1.1% sirq
Load average: 5.29 5.61 5.30 4/690 6823
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
4063 4010 system S 384m 47.7 90.1 system_server
791 2 root SW 0 0.0 3.9 [kworker/0:2]
6323 4010 app_66 S 330m 41.0 3.2 net.osmand
3 2 root SW 0 0.0 0.3 [ksoftirqd/0]
1536 1 system S 62044 7.5 0.2 /system/bin/surfaceflinger
863 2 root SW 0 0.0 0.2 [mmcqd/1]
4962 4927 root R 1900 0.2 0.1 top
10 2 root SW 0 0.0 0.1 [ksoftirqd/1]
6212 2 root SW 0 0.0 0.1 [kworker/0:0]
1667 1 root S 5512 0.6 0.1 /sbin/adbd
840 2 root SW 0 0.0 0.1 [kworker/u:4]
3666 2 root SW 0 0.0 0.1 [kworker/u:5]
591 2 root SW 0 0.0 0.1 [av8100_thread]
6590 2 root SW 0 0.0 0.1 [kworker/1:2]
5130 4010 app_65 S 345m 42.8 0.0 {ockplus.android} org.adblockplus.andr
4306 4010 app_41 S 322m 40.0 0.0 {enmod.trebuchet} com.cyanogenmod.treb
4263 4010 app_46 S 318m 39.5 0.0 {e.process.gapps} com.google.process.g
4340 4010 radio S 310m 38.5 0.0 {m.android.phone} com.android.phone
5787 4010 app_64 S 303m 37.7 0.0 {android.youtube} com.google.android.y
5712 4010 system S 302m 37.6 0.0 {ndroid.settings} com.android.settings
The system_server seems to use up the entire CPU time causing my problems. Is there a way to fix the problem, if yes, who would I talk to about this?
Alternatively I would like to use another ROM. I have heard that my device has some quirks making it very hard to use most ROMs (most notably a broken audio driver?). For this reason I originally chose the freexperia builds despite the fact that that android version is not exactly up-to-date.
Is there another ROM that will work properly with my device?
Also I would like to know how to back up the relevant data: When I installed the current ROM, android wouldn't start until I reset the device and wiped the data in the process. I dislike every kind of backup that uses "the cloud" for obvious reasons. I just want to copy the data onto my laptop via USB (without using an App, free or not). I tried using "adb backup" but I am not sure which options I have to select to obtain the relevant data without having a >> 1 GB size BLOB on my laptop. Any ideas about that?
You would have more luck looking in your device specific subforum instead of general area.
http://forum.xda-developers.com/xperia-u
I want to install many apk
so I use ADB to connect smart phone
Can I install apk for ADB one time?
The complete command is always displayed in android studio, i cant be 100% sure about the parameters, but it should be adb install ... (I think android studio uses adb install -p)
Edit: ah no it is pm install instead of adb install
---------------------------------
Phone : Nexus 4
OS :
- KitKat 4.4.4 stock
- Xposed: 58(app_process); 54(bridge)
- SU: SuperSU
- no custom recovery
---------------------------------
4d 61 73 72 65 70 75 73 20 66 74 77
Gesendet von Tapatalk
Masrepus said:
The complete command is always displayed in android studio, i cant be 100% sure about the parameters, but it should be adb install ... (I think android studio uses adb install -p)
Edit: ah no it is pm install instead of adb install
---------------------------------
Phone : Nexus 4
OS :
- KitKat 4.4.4 stock
- Xposed: 58(app_process); 54(bridge)
- SU: SuperSU
- no custom recovery
---------------------------------
4d 61 73 72 65 70 75 73 20 66 74 77
Gesendet von Tapatalk
Click to expand...
Click to collapse
thank you ,I try it
This kernel is based on TeamCanjica/3.0.101 branch and much credit goes to them for doing this
However not everything from TC kernel is there. I'm not happy with the new liveopp algorithm. Also there's no ddr oc as one can get hurt with this now (/data fs corruption). When @ChronoMonochrome improves the implementation, maybe I'll merge it.
Compatibility:
I suspect it should work fine for any CM-11.0 based rom. If someone tests it, I'll add info here
- Stock
- Vanir
- Carbon
- CM11
- CM10.1
- CM10.2
- CM12.1 until I get a proper ramdisk, I don't support this config, besides reboot/poweroff doesnt work on it.
For version r6 you don't need to flash extra ramdisk - it contains all previously gathered ramdisks and uses the right one based on /system/build.prop file - checks ro.build.version.sdk (https://github.com/mkaluza/Samsung_STE_Kernel/blob/master/usr/u8500_initramfs_files/init#L22)
Changes:
Kernel (https://github.com/mkaluza/Samsung_STE_Kernel/commits/3.0.101)
[r5] Full changelog
WARNING - if you have some custom uv/oc, disable it first, as now you'll be using different Vbbx by default (original one). Test your oc/uv again for stability and correct if necessary, or restore Vbbx from your uv script first:
Code:
for f in /sys/kernel/liveopp/arm_step0*; do echo vbbx=0xcc > $f; done
btw novathor settings interfere with mali UV, so I removed them completely from my phone (can't be disabled - unfortunately for them )
Download:
MediaFire all releases
A bonus - a modified torch with high power option - I was always pissed with having to use novathor settings for this...
Install:
Flash update.zip with CWM
Loading modules
There are a few ways to load modules depending on how important those modules are:
1. add module name to /system/etc/modules file (create it if it doesn't exist). Add a name without extension (like cpufreq_lionheart or logger)
(TODO: handle /data/etc/modules as well)
Those modules will be loaded just after /system is mounted
2. use KoControl app (or similar) - those modules will be loaded when system starts up, so use it only for unimportant modules
3. copy it to one of initramfs overlay/modules directory: /efs/common/overlay/modules, /efs/boot/overlay/modules, /efs/recovery/overlay/modules - these modules will be loaded before init even starts - it's useful for filesystem modules like f2fs
Dynamic governor documentation
Since it has many params that depend on each other, some doc is needed:
Dynamic governor documentation
It's a work in progress, so it'll be gradually improved. You can improve the improvement process by letting me know that you use it and whether you like it or not If "not" - then tell me why, maybe something can be done about it. Although it's unlikely that I'll accept feature requests unless I find it useful for myself, feel free to fork the kernel and modify it
LVM
Before anything else, read those and all the stuff those posts tell you to read:
https://www.howtoforge.com/linux_lvm
http://forum.xda-developers.com/nexus-s/general/howto-combined-emulated-storage-nexus-s-t2848752
http://forum.xda-developers.com/nexus-s/general/howto-partitioning-nexus-s-using-lvm-t1656794
http://www.xda-developers.com/android/bypass-nexus-s-storage-restrictions/
If you don't understand something, keep reading. If you still don't understand, leave it for now - It's for your safety.
Later I'll add SGA specific stuff how to make use of our empty /preload partition and get more free space on /data
NFC
The kernel has nfc modules available, so in theory it should work - you just need to load them as described in section on modules.
Load pn544 and/or pn547. You also need nfc-enabled rom (If it doesn't work, then I don't know what else... don't have nfc to test it)
Upgradeable ramdisk
See this file, it tells all the story
https://github.com/mkaluza/Samsung_STE_Kernel/blob/master/usr/u8500_initramfs_files/init
I'll add some comment later
Troubleshooting:
- my wifi isn't working
- TODO: how to report errors to make the difference
XDA:DevDB Information
MK Kernel [3.0.101], Kernel for the Samsung Galaxy S Advance I9070
Contributors
mkaluza
Source Code: https://github.com/mkaluza/Samsung_STE_Kernel
Kernel Special Features: LVM, new dynamic governor, automatic voltage calculation, 630 MB ram
Version Information
Status: Stable
Current Stable Version: r6.0.0.
Stable Release Date: 2015-06-05
Created 2014-12-19
Last Updated 2015-06-05
Thanks to @Reinkaos for beta testing
His report:
Reinkaos said:
OK so here's a report, I use min 200mhz max 1000mhz, continuous usage with wifi on all the time from 100%-4%.
liveopp:
200 = 0x0c
300 = 0x0d
400 = 0x0e
500 = 0x1d
600 = 0x1f
700 = 0x20
800 = 0x21
900 = 0x28
1000 = 0x2c
mali (I use idx 1 and 5)
250mhz = 0x17
400mhz = 0x1b
From BBS dump:
Deep Sleep (): 2 h 15 m 16 s 43.3%
Awake (): 2 h 57 m 4 s 56.7%
Screen On (): 2 h 56 m 28 s 56.5%
Phone On (): 27 s 0.1%
Wifi On (): 2 h 54 m 2 s 55.7%
Wifi Running (): 2 h 54 m 55.7%
No Data Connection (): 5 h 12 m 21 s 100.0%
No or Unknown Signal (): 5 h 12 m 21 s 100.0%
Screen dimmed (): 2 h 56 m 28 s 56.5%
1 GHz (): 36 m 44 s 11.8%
900 MHz (): 8 m 18 s 2.7%
800 MHz (): 9 m 51 s 3.2%
700 MHz (): 11 m 17 s 3.6%
600 MHz (): 12 m 47 s 4.1%
500 MHz (): 14 m 30 s 4.6%
400 MHz (): 16 m 24 s 5.3%
300 MHz (): 5 m 37 s 1.8%
200 MHz (): 1 h 1 m 33 s 19.7%
Deep Sleep (): 2 h 15 m 16 s 43.3%
Just to compare, here are the last 2 test that I did on previous kernel, with the same usage pattern, on interactive:
1
Deep Sleep (): 3 h 52 m 51 s 57.9%
Awake (): 2 h 49 m 36 s 42.1%
Screen On (): 2 h 47 m 57 s 41.7%
Wifi On (): 2 h 43 m 41 s 40.7%
Wifi Running (): 2 h 43 m 39 s 40.7%
No Data Connection (): 6 h 42 m 28 s 100.0%
No or Unknown Signal (): 6 h 42 m 28 s 100.0%
Screen dark (): 2 h 47 m 57 s 41.7%
1 GHz (): 45 m 25 s 11.3%
800 MHz (): 8 m 23 s 2.1%
600 MHz (): 46 m 31 s 11.6%
400 MHz (): 9 m 22 s 2.3%
200 MHz (): 59 m 54 s 14.9%
Deep Sleep (): 3 h 52 m 51 s 57.9%
2
Deep Sleep (): 3 h 58 m 48 s 60.6%
Awake (): 2 h 35 m 12 s 39.4%
Screen On (): 2 h 34 m 32 s 39.2%
Wifi On (): 2 h 32 m 1 s 38.6%
Wifi Running (): 2 h 32 m 38.6%
No Data Connection (): 6 h 34 m 1 s 100.0%
No or Unknown Signal (): 6 h 34 m 1 s 100.0%
Screen dark (): 2 h 34 m 32 s 39.2%
1 GHz (): 33 m 4 s 8.4%
800 MHz (): 9 m 27 s 2.4%
600 MHz (): 49 m 48 s 12.6%
400 MHz (): 9 m 42 s 2.5%
200 MHz (): 53 m 9 s 13.5%
Deep Sleep (): 3 h 58 m 48 s 60.6%
No random reboots. I'm not sure about how fast screen turned on when receiving a call though, since I never pay attention to it in the previous kernel, so can't really compare.
And mtp doesn't work, not sure if that's on my side.
Anyway those dynamic tunables, is there any doc or explanation of each? Will definitely play around with it. Gonna test it again today to see if I ran into problems. Haven't had any problems yet, so far so good :good:
Click to expand...
Click to collapse
mkaluza said:
Thanks to @Reinkaos for beta testing
Click to expand...
Click to collapse
No problem, glad I could help
mkaluza said:
This kernel is based on TeamCanjica/3.0.101 branch and much credit goes to them for doing this
Compatibility:
I use it with Vanir ROM and I don't know how/if it'll work on other roms, but I suspect it's fine for any CM-11.0 based rom. If someone tests it, I'll add info here
Changes:
Ramdisk (https://github.com/mkaluza/ste-ramdisk-vanir/commits/master):
- don't turn zram swap by default (can be turned on via init.d) - it just eats cpu and rarely gives
- removed cm performance profiles - they interfere with init.d/setcpu
- run adb as root by default - it annoyed me to constantly type su, esp. that this su version is a bit lame and su -c "command" doesnt work
Kernel (https://github.com/mkaluza/Samsung_STE_Kernel/commits/3.0.101)
- more liveopp freqs 100-1000 with 100 MHz step
- improved liveopp and mali_boost algorithms (compared to original Vanir Kernel, which is by Team-Exhibit)
- Dynamic cpufreq governor (my design) - brings good performance and battery life together. It's a part of Project Zen (GitHub)
- LiveOPP automatic voltage calculation based on AVS data - It should reduce probability of random reboots, but beware - if you have some custom uv/oc, disable it first, as now you'll be using different vbbs by default (original one). Test your oc/uv again for stability and correct if necessary
- killed u8500 hotplug - it caused problems with audio and didn't bring any more battery time
- disabled highmem - it's not needed with only 768 MB RAM
- added Joel RCU
As a bonus - a modified torch with high power option - I was always pissed with having to use novathor settings for this...
btw novathor settings interfere with mali UV, so I removed them completely from my phone (can't be disabled - unfortunately for them )
However not everything from TC kernel is there - I didn't like the new liveopp algorithm. Also there's no ddr oc as one can get hurt with this when used badly...
Download:
MediaFire
Install:
No update zip for now (if somebody want's to create it then by all means do)
Flash zImage with either Universal Kernel Flasher or just dd:
Code:
dd if=zImage of=/dev/block/mmcblk0p15
unpack modules.zip to /system/lib/modules/
Source:
GitHub
XDA:DevDB Information
MK Kernel [3.0.101], Kernel for the Samsung Galaxy S Advance I9070
Contributors
mkaluza
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r1
Stable Release Date: 2014-12-19
Created 2014-12-19
Last Updated 2014-12-19
Click to expand...
Click to collapse
Wi-fi isn`t working properly. After 1 or two reboots, I can`t switch wi-fi to on . ( commonly problem seen before on other builds )
pictorul20 said:
Wi-fi isn`t working properly. After 1 or two reboots, I can`t switch wi-fi to on . ( commonly problem seen before on other builds )
Click to expand...
Click to collapse
It happens when there's kernel-module mismatch - have you extracted modules.zip into right place? check this again... It works fine for me and @Reinkaos. What does dmesg say just after you try to enable wifi?
There might be some subtle problem with this kernel that is causing random reboots from time to time. For now set your deepest sleep state to 4 (it defaults to 5 now), as I suspect this might be the cause (I removed all oc/uv and mali stuff and it still happens, now testing deepsleep=4).
If a reboot happens, save /proc/last_kmsg somewhere and look for "Unhandled fault: imprecise external abort (0x1c06)". Actually every time a crash happens, save last_kmsg You can use this init.d script to collect it at every system startup (saves them to /data/local/log/last_kmsg
mkaluza said:
There might be some subtle problem with this kernel that is causing random reboots from time to time. For now set your deepest sleep state to 4 (it defaults to 5 now), as I suspect this might be the cause (I removed all oc/uv and mali stuff and it still happens, now testing deepsleep=4).
If a reboot happens, save /proc/last_kmsg somewhere and look for "Unhandled fault: imprecise external abort (0x1c06)". Actually every time a crash happens, save last_kmsg You can use this init.d script to collect it at every system startup (saves them to /data/local/log/last_kmsg
Click to expand...
Click to collapse
sorry, I might said that wrong. I wanted to say that I don-t have wi-fi network at all. I can-t switch it on at all from settings menu. any help would be more than welcome. Ohh, and one last thing. U seem to always do a great job when it comes to " under the hood" customisation and enhanced features . Good work .
pictorul20 said:
sorry, I might said that wrong. I wanted to say that I don-t have wi-fi network at all. I can-t switch it on at all from settings menu. any help would be more than welcome.
Click to expand...
Click to collapse
You said it right and my response is probably correct - you try to tap the wifi button or turn it on in settings and either it turns on for a very brief moment or not at all. That's a sign of module-kernel mismatch. Check again if you extracted those modules (or even better, just do it) - your old modules from vanir won't work with this kernel, there are too many changes.
I'll try to make update.zip later to make install easier.
pictorul20 said:
Ohh, and one last thing. U seem to always do a great job when it comes to " under the hood" customisation and enhanced features . Good work .
Click to expand...
Click to collapse
Thank you
mkaluza said:
You said it right and my response is probably correct - you try to tap the wifi button or turn it on in settings and either it turns on for a very brief moment or not at all. That's a sign of module-kernel mismatch. Check again if you extracted those modules (or even better, just do it) - your old modules from vanir won't work with this kernel, there are too many changes.
I'll try to make update.zip later to make install easier.
Thank you
Click to expand...
Click to collapse
U`re welcome., and yess that-s exactly the problem I`m facing. It`s not quite a hazardous problem but it-`s just a bug somewhere in the kernel probably. It happens. And one last question, first time I had overwrited the modules to the sistem folder ( that-s when i saw 4 the 1st time that my wi-fi isn-t responding at all ) , then ........ I thought I might delete all the modules from lib/modules to prevent any incompatibility with the copyed ones. Now my question is : Everytime i-m installing cm 11 roms or vanir rom , Do I have to copy/paste modules and overwrite them to lib/modules folder, or do I have to wipe all content inside of that folder and only after that paste the modified modules that you posted in this thread?
L.E :. I can-t switch from internal to external also usb connection doesn-t work in windows ( can-t access my internal / external storage from usb cable )even with proper usb drivers installed )
pictorul20 said:
U`re welcome., and yess that-s exactly the problem I`m facing. It`s not quite a hazardous problem but it-`s just a bug somewhere in the kernel probably. It happens. And one last question, first time I had overwrited the modules to the sistem folder ( that-s when i saw 4 the 1st time that my wi-fi isn-t responding at all ) , then ........ I thought I might delete all the modules from lib/modules to prevent any incompatibility with the copyed ones.
Click to expand...
Click to collapse
That shouldn't matter. What "lsmod" says? what happens when you do "modprobe dhd". If it shows some error, do "modprobe dhd; dmesg | tail -n 50" and pm me the output.
pictorul20 said:
Now my question is : Everytime i-m installing cm 11 roms or vanir rom , Do I have to copy/paste modules and overwrite them to lib/modules folder, or do I have to wipe all content inside of that folder and only after that paste the modified modules that you posted in this thread?
Click to expand...
Click to collapse
Overwrite should be enough and yes, you have to do it every time you reinstall rom
pictorul20 said:
L.E :. I can-t switch from internal to external
Click to expand...
Click to collapse
I don't understand...
pictorul20 said:
also usb connection doesn-t work in windows ( can-t access my internal / external storage from usb cable )even with proper usb drivers installed )
Click to expand...
Click to collapse
Ok, than MTP is screwed. I never use it so I didn't see it, and @Reinkaos wasn't sure if it's the kernel or his phone, but now we know it's the kernel.
@mkaluza it would be great if you make a stock kernel too, since cocafe has almost stopped to support our device
Most of us are on stock JB but it would be really nice if you implement a stock kernel that can enhance the performance of our phone
Hoping you'll do it
@pictorul20 I just remembered something - apart from modules mismatch there was some problem with I think firmware paths, but I haven't got slightest idea what was it... @Reinkaos any thoughts?
The funny thing is - I flashed boot.img from original vanir nightly (and copied modules) and wifi ISN'T WORKING After flashing my kernel (not my particular source - just any one build on my machine) it works
I can remember having once the reverse problem (it wasn't working on my kernel) - I know I fixed it somehow and never had it again. I haven't noticed that wifi stopped working on dist kernel because I never again used one...
DAMN... I know it was something simple to do, but hard to find... Anyone? @cocafe maybe you can remember?
Guys, what does command find /system -iname "*bcm*" show?
For me it's this:
Code:
/system/bin/bcm4330.hcd
/system/etc/wifi/bcmdhd_apsta.bin
/system/etc/wifi/bcmdhd_mfg.bin
/system/etc/wifi/bcmdhd_p2p.bin
/system/etc/wifi/bcmdhd_sta.bin
/system/vendor/firmware/fw_bcmdhd.bin
/system/vendor/firmware/fw_bcmdhd_apsta.bin
jadega said:
@mkaluza it would be great if you make a stock kernel too, since cocafe has almost stopped to support our device
Most of us are on stock JB but it would be really nice if you implement a stock kernel that can enhance the performance of our phone
Hoping you'll do it
Click to expand...
Click to collapse
But there's actually not much more to be done Cocafe's kernel is very good. It's actually very similar to 3.0.101 kernel in terms of features. As for power/performance, when dynamic gov is field tested a bit more, I'll merge it and send a pull request to Cocafe. There's no point in keepeng two kernels...
Another thing is, for all of you still on JB - install Vanir. It's ****in awesome. Stable, fast and doesn't drain batt. And when issues with wifi are solved, it'll be even better I'm happy with the speed even on JIT, and on ART it's even faster (I don't use it not because it's unstable, but because while developing performance features I want to be able to see any improvements, and it's hard below some threshold )
mkaluza said:
@pictorul20 I just remembered something - apart from modules mismatch there was some problem with I think firmware paths, but I haven't got slightest idea what was it... @Reinkaos any thoughts?
The funny thing is - I flashed boot.img from original vanir nightly (and copied modules) and wifi ISN'T WORKING After flashing my kernel (not my particular source - just any one build on my machine) it works
I can remember having once the reverse problem (it wasn't working on my kernel) - I know I fixed it somehow and never had it again. I haven't noticed that wifi stopped working on dist kernel because I never again used one...
DAMN... I know it was something simple to do, but hard to find... Anyone? @cocafe maybe you can remember?
Guys, what does command find /system -iname "*bcm*" show?
For me it's this:
Code:
/system/bin/bcm4330.hcd
/system/etc/wifi/bcmdhd_apsta.bin
/system/etc/wifi/bcmdhd_mfg.bin
/system/etc/wifi/bcmdhd_p2p.bin
/system/etc/wifi/bcmdhd_sta.bin
/system/vendor/firmware/fw_bcmdhd.bin
/system/vendor/firmware/fw_bcmdhd_apsta.bin
Click to expand...
Click to collapse
I have no idea, does different firmware had anything to do with it?
Anyway, here's mine
Code:
/system/bin/bcm4330.hcd
/system/etc/wifi/bcmdhd_apsta.bin
/system/etc/wifi/bcmdhd_mfg.bin
/system/etc/wifi/bcmdhd_p2p.bin
/system/etc/wifi/bcmdhd_sta.bin
/system/vendor/firmware/fw_bcmdhd.bin
/system/vendor/firmware/fw_bcmdhd_apsta.bin
@pictorul20 one more thing - can you make sure permissions on modules are 644? because that's what caused wifi not to work (I extracted modules from zip file with total commander to sd card, where default perms are 770), and when I copied them to /system/lib/modules, they remained that way and that was the problem.
mkaluza said:
@pictorul20 one more thing - can you make sure permissions on modules are 644? because that's what caused wifi not to work (I extracted modules from zip file with total commander to sd card, where default perms are 770), and when I copied them to /system/lib/modules, they remained that way and that was the problem.
Click to expand...
Click to collapse
So, I need each module file to set with 644 permission, right? I`ll try and report back if that solved the problem. Thanks
pictorul20 said:
So, I need each module file to set with 644 permission, right? I`ll try and report back if that solved the problem. Thanks
Click to expand...
Click to collapse
Maybe just flash the update.zip from post #1 - it should fix everything and if not, I'll give you instructions how to debug that stuff.
mkaluza said:
Maybe just flash the update.zip from post #1 - it should fix everything and if not, I'll give you instructions how to debug that stuff.
Click to expand...
Click to collapse
I flashed this kernel on my slimsaber and wifi doesn't work.
If can help log just says WifiStateMachine E: Failed to load driver
Wifi problem debugging
hastalafiesta said:
I flashed this kernel on my slimsaber and wifi doesn't work.
If can help log just says WifiStateMachine E: Failed to load driver
Click to expand...
Click to collapse
Yes it does. Logcat is important - it's good you checked there. We'll try to make it compatible with other roms, but you must help me debug it, ok?
@pictorul20 - can you do those steps too?
(all the stuff below has to be done via adb as root). copy/paste all commands, because all the quotes there are important and it's easy to make a mistake
Code:
cd /system/lib/modules
ls -l
check that all modules have 644 permissions (rw-r--r--)
Code:
lsmod
It should say something (for me it's). If nothing is shown, continue anyway (but tell me about it).
bthid 4267 0 - Live 0x00000000
param 10593 0 - Live 0x00000000 (P)
j4fs 66945 1 - Live 0x00000000 (P)
Click to expand...
Click to collapse
Code:
insmod /system/lib/modules/dhd.ko
lsmod
It should not return an error and lsmod should then contain a line similar to this
dhd 430856 0 - Live 0x00000000
Click to expand...
Click to collapse
if however it return some error, do this and send me the output and the error
Code:
insmod /system/lib/modules/dhd.ko; dmesg | tail -n 20
If so far everything is fine, it's time for hacky stuff now
Code:
rmmod dhd
mkdir /tmp/strace
cd /proc/`pidof system_server`/task
for p in `grep -i wifi */comm | cut -f 1 -d '/'`; do n=`cat $p/comm`; strace -tt -p $p -o/tmp/strace/${n}.strace& done
then tap wifi button in quick settings at least twice (not too fast - wait at least 1 sec) and then
Code:
killall strace
zip -r /mnt/sdcard/wifi.strace1.zip /tmp/strace
if you want to look for an error, do
Code:
cd /tmp/strace
grep "= -" *.strace
this will show all failed syscals with (hopefully) some useful info. If it helps you solve the problem, than ok (share it here), if not, continue
Code:
mkdir /tmp/strace2
strace -ff -tt -p `pidof system_server` -o /tmp/strace2/system_server
tap the wifi button as before and press Ctrl-C to kill the command above
Code:
zip -r /mnt/sdcard/wifi.strace2.zip /tmp/strace2
Mail me (mk at flex.pm) both wifi.strace*.zip files from the root of your internal memory.
@mkaluza
EDIT: I messed up with modules for various tests, i restored the original modules, followed your guide and all went fine.
WIFI works with this! Thanks for your work, till now kernel works pretty well.
Just tried the r3 (630mb) and all is good and very smooth.
ORIGINAL POST:
Hello,
this is almost a brand new phone, still no resources over the internet about how to root it.
Is anybody working on it?
Does anybody know a viable solution to effectively root BL8800 Pro without any damage?
Thanks
--------------------------------------------
ROOTING PROCEDURE WITH UBUNTU 22.04 - ONLY FOR PHONE FIRMWARE 20220617v02 (big thanks to adamfahdi)
***WARNING*** THIS IS RISKY: 1 USER REPORTED A BRICKED PHONE WITH BOOT LOOP, ALL OTHERS OK - PLEASE DO NOT CHANGE ANYTHING AND CONTROL SYSTEM VERSION THOROUGHLY
***WARNING*** THIS PROCEDURE WILL WIPE ALL YOUR PHONE CONTENTS, IT'S LIKE A FACTORY RESET, BACKUP ANYTHING YOU NEED BEFORE ACTING!
ACTIONS ON BL8800 Pro PHONE
---> activate developer menu and USB debug on BL8800 Pro
---> check "oem unlocking" in developer menu
---> check "enable USB debug" in developer menu
---> install latest magisk apk (CURRENTLY 25.2)
---> check "enable alternate sources" when installing magisk
---> connect USB cable
---> copy boot.img on phone (downloaded from https://mega.nz/file/rDIAWJaR#TOjmxZl5LdjyVur3lwqP2wgNCm19tNoLhxXioRV8n70 this is for 20220617v02 firmware ONLY!)
---> patch boot.img with magisk
---> copy patched pboot.img on PC
ACTIONS FROM UBUNTU 22.04
---> open terminal
$ sudo apt install adb fastboot
$ adb devices -l
List of devices attached
BL8800PEEAxxxxxxx unauthorized usb:3-2 transport_id:1
---> authorize PC from BL8800 Pro screen
$ adb devices -l
List of devices attached
BL8800PEEAxxxxxxx device usb:3-2 product:BL8800Pro_EEA model:BL8800Pro device:BL8800Pro transport_id:1
---> check if adb is working correctly and reboot to bootloader
$ adb shell
BL8800Pro:/ $ ls
acct bin cache d data_mirror default.prop etc init.environ.rc lost+found mnt oem proc sdcard sys system_ext apex bugreports config data debug_ramdisk dev init linkerconfig metadata odm postinstall product storage system vendor
BL8800Pro:/ $ reboot bootloader
$ fastboot devices
BL8800PEEAxxxxxxx fastboot
$ fastboot flashing unlock
---> press VolumeUP on phone to choose "Yes" <----- THIS WILL WIPE ALL YOUR PHONE CONTENTS!!!
(bootloader) Start unlock flow
OKAY [ 7.348s]
Finished. Total time: 7.348s
$ fastboot flash boot pboot.img <----- THIS MAY BRICK YOUR PHONE!!!
Sending 'boot_a' (40960 KB) OKAY [ 1.368s]
Writing 'boot_a' OKAY [ 0.177s]
Finished. Total time: 1.563s
$ fastboot reboot
EXTRA: PROCEDURE TO RUN APPS THAT DENY EXECUTION WITH ROOTED PHONE
Some sleazy apps (banking, ebay, etc.) check if you have rooted your phone and refuse to run/authenticate/etc.
This is how you can solve this, everything done from MAGISK:
activate Magisk Hide, in the "App" settings section - rename magisk app to whatever you like
activate Zygisk, in the "Magisk" setting section, then reboot
in the "Magisk" setting section, select the rogue apps you want to hide rooting from (e.g. ebay)
in Magisk modules section install "Shamiko" module downloaded from https://github.com/LSPosed/LSPosed.github.io/releases then reboot
in Magisk modules section install "Universal SafetyNet Fix" module downloaded from https://github.com/kdrag0n/safetynet-fix/releases then reboot
check in Magisk modules section that both modules are active and running
EXTRA: in order to check that safetynet fix is working, you may download "YASNAC" app from play store
ENJOY YOUR PHONE!!!
do you only want to root?
Keep in mind:
Rooting may void the manufacturer’s warranty on your device.
Rooting will block the firmware OTA updates.
Required Downloads:1)Download ADB & Fastboot files
2)Blackview USB Drivers install on your pc
3)Download Other Drivers: Mediatek VCOM Drivers or MTK USB Drivers
4)Download And Install the SP Flash tool on your computer
5)Download the latest Blackview Stock ROM and move it to the PC
Download and extract the stock ROM to your PC.
You need to extract the boot image using the MTK Droid Tool
Attach your device via USB cable and copy only the boot.img file from the extracted folder to your device storage
Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
Tap on “Patch Boot Image File”.
Navigate to internal storage and select your phone’s boot image that you transferred earlier.
Wait for a couple of seconds. Magisk will start patching the boot image.
Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the same extracted ROM folder on your PC.
To flash stock rom whit the patched image follow this
Hi, thanks for your answer.
Do these tools also work on linux?
I saw that BL8800 Pro ROM is not available on the page, is there anyother source where I can download or some tool that can make a snapshot from the phone?
I saw that MTK Droid Tool looks like windows only but I am not worried... while the USB drivers are included in linux kernel? Here running ubuntu 22.04, thanks!
Update: I just obtained two firmare files, one maked EEA (likely for Europe) with date 2022-06-17 and another one marked NEU (likely NotEUrope) with date 2022-06-10, both subversion V02 directly from Blackview customer support. This is listing of EEA version:
-rw-rw-r-- 1 1000 1000 41943040 giu 16 19:59 boot-debug.img
-rw-rw-r-- 1 1000 1000 41943040 giu 16 19:59 boot.img
drwxrwxr-x 2 1000 1000 4096 giu 16 19:59 DATABASE
-rw-rw-r-- 1 1000 1000 136976 giu 16 19:59 dpm.img
-rw-rw-r-- 1 1000 1000 148064 giu 16 19:59 dpm-verified.img
-rw-rw-r-- 1 1000 1000 8388608 giu 16 19:59 dtbo.img
-rw-rw-r-- 1 1000 1000 72960 giu 16 19:59 dtbo-verified.img
-rw-rw-r-- 1 1000 1000 2029376 giu 16 19:59 gz.img
-rw-rw-r-- 1 1000 1000 2033072 giu 16 19:59 gz-verified.img
-rw-rw-r-- 1 1000 1000 1226000 giu 16 19:59 lk.img
-rw-rw-r-- 1 1000 1000 1233392 giu 16 19:59 lk-verified.img
-rw-rw-r-- 1 1000 1000 8420336 giu 16 19:59 logo.bin
-rw-rw-r-- 1 1000 1000 8424032 giu 16 19:59 logo-verified.bin
-rw-rw-r-- 1 1000 1000 440624 giu 16 19:59 mcupm.img
-rw-rw-r-- 1 1000 1000 444320 giu 16 19:59 mcupm-verified.img
-rwxrwxr-x 1 1000 1000 64971072 giu 16 19:59 md1img.img
-rw-rw-r-- 1 1000 1000 64982208 giu 16 19:59 md1img-verified.img
-rw-rw-r-- 1 1000 1000 50656 giu 16 19:59 MT6833_Android_scatter.txt
-rw-rw-r-- 1 1000 1000 83956 giu 16 19:59 MT6833_Android_scatter.xml
-rw-rw-r-- 1 1000 1000 2080 giu 16 19:59 pi_img.img
-rw-rw-r-- 1 1000 1000 5776 giu 16 19:59 pi_img-verified.img
-rw-rw-r-- 1 1000 1000 391996 giu 16 19:59 preloader_tf929_dk_dk029_lepton_6833_r0_eea.bin
-rw-rw-r-- 1 1000 1000 428528 giu 16 19:59 scp.img
-rw-rw-r-- 1 1000 1000 435920 giu 16 19:59 scp-verified.img
-rw-rw-r-- 1 1000 1000 11088 giu 16 19:59 spmfw.img
-rw-rw-r-- 1 1000 1000 14784 giu 16 19:59 spmfw-verified.img
-rw-rw-r-- 1 1000 1000 657344 giu 16 19:59 sspm.img
-rw-rw-r-- 1 1000 1000 661040 giu 16 19:59 sspm-verified.img
-rw-r--r-- 1 1000 1000 5135711316 giu 16 19:59 super.img
-rw-rw-r-- 1 1000 1000 970240 giu 16 19:59 tee.img
-rw-rw-r-- 1 1000 1000 977632 giu 16 19:59 tee-verified.img
-rw-r--r-- 1 1000 1000 2343188 giu 16 19:59 userdata.img
-rw-rw-r-- 1 1000 1000 4096 giu 16 19:59 vbmeta.img
-rw-rw-r-- 1 1000 1000 4096 giu 16 19:59 vbmeta_system.img
-rw-rw-r-- 1 1000 1000 4096 giu 16 19:59 vbmeta_vendor.img
DATABASE/
-rw-rw-r-- 1 1000 1000 202741 giu 16 19:59 APDB_MT6853_S01__W2209
-rw-rw-r-- 1 1000 1000 20943 giu 16 19:59 APDB_MT6853_S01__W2209_ENUM
-rwxrwxr-x 1 1000 1000 11093341 giu 16 19:59 MDDB_InfoCustomAppSrcP_MT6833_S00_TF928_R0_6833_NLWCG_V0_1_9_S220505_1_unlwctg_n.EDB
-rwxrwxr-x 1 1000 1000 746087 giu 16 19:59 MDDB.META_MT6833_S00_TF928_R0_6833_NLWCG_V0_1_9_S220505_1_unlwctg_n.EDB
Is this the correct overall filesystem suitable for modifying before flashing?
Thanks
One update: trying to feed scatter.xml file to SP Flash Tool gets the complaint that "MT68 platform not supported on this version" (it's MT6833) but versions following 5.1924 don't have the field for scatter.xml file....
SO at the moment I am stopped at full adb shell to the device, but nothing much more.
Btw, in order to avoid problems I am running tests from inside a W10 VM in vitualbox inside linux.
derjaeger said:
One update: trying to feed scatter.xml file to SP Flash Tool gets the complaint that "MT68 platform not supported on this version" (it's MT6833) but versions following 5.1924 don't have the field for scatter.xml file....
SO at the moment I am stopped at full adb shell to the device, but nothing much more.
Btw, in order to avoid problems I am running tests from inside a W10 VM in vitualbox inside linux.
Click to expand...
Click to collapse
Hi.
Have you tried the Fastboot method?
I also go astray
I am looking for a way to root and I take risky actions. Perhaps I understand it all wrong, but...
I unlocked the bootloader using MTKClient. Then I wanted to create a scatter myself using MTK Droid Tool to get boot.img from the phone. Unfortunately, MTK Droid Tool did not support (I think) memory.
Would you share the boot.img file, please? I'd like to try the Fastboot method.
Thank you.
Hello
First of all, I didn't worry about unlocking bootloader as, pressing power+vol_up buttons when phone is off, already lets you enter to a factory stock bootloader with a menu an option of which can also apply patches, so it looks kinda "ready" without the need of injecting something via fastboot (which is, btw, also an option of that menu). I don't know if that applies for you too, I have a European "EEA" latest firmware version installed.
Second, as written in my previous mail, the tool didn't operate with MT68xx devices, so it couldn't therefore extract anything.
((
I think that either an updated version of that tool comes out (but 6.x versions don't have the "scatter" file field) or we could start from that full firmware that Blackview let me download. I can transfer it to you if needed, you find the file list in my other previous mail.
At the moment the basic idea would be, I think as you might have in mind, once the boot.img file is somehow extracted, patch it with magisk, transfer it to the phone and apply it though the bootloader.
Do you agree?
Pasha
@derjaeger
Thank you for your response
I think you are completely right.
I read everything again and noticed that there are only two ROM files, not this whole list, and that there is some doubt about the scatter file and how SP Flash Tool supports it.
So the new firmware has no obvious procedure to upload it and the boot.img file must first be extracted to use Magisk.
It will be best if I wait for a proven method
I will be grateful for the ROM files, they will certainly be useful. Do you have restrictions on their distribution?
Thank you and best regards.
Saper
Yes, the MT68xx platform is likely to have introduced substantial modifications to the architecture and, therefore, the extraction methods. Is anybody reading this thread aware of new tools?
About the SW, I got no restrictions at all, pls let me know in private how you would like to receive them.
Have anybody here the Stock ROM for the Blackview BL8800 Pro?
Hi, I have it, but you gotta wait up to 25th August, as I am now on holiday.
Sorry, I forgot I had the ready link from the company: https://mega.nz/file/rDIAWJaR#TOjmxZl5LdjyVur3lwqP2wgNCm19tNoLhxXioRV8n70
Please let me know if this helps you to make some progress!
WELL DONE!! i been following this threat and failed to flash the boot.img many times as it's not supported by MTk flash tool- Droid tool SP-FLASH. Been working on this for over month now!! Finally after 9 hours of work non stop got it solved i was able to flash the patched boot.img
BE AWARE!!!! ALL YOUR FILES WILL BE DELETED ----- WARRANTY VOIDED !!
Finally
DONATIONS ARE WELCOMED FOR THE HARD WORK!! CASHAPP: $adamkey99
1-Download - Install - Extract -----> Platform Tools.Zip (ADB-Fastboot) etc,, in the ZIP file
2-rename the patched boot file TO boot.img to the same folder Platform Tools
3- Boot to Recovery & connect USB
4- Choose ENTER Fastboot
5- Choose Reboot to bootloader
6- open the folder Patform Tools and open CMD
7- Type the commend "fastboot devices" letters only!! you'll see your device pop up
8- Type the commend "fastboot flashing unlock" letters only!!
9-you'll see your phone in very small letters saying choose if you want to unlock WARRANTY VODIED
10- choose yes
11- type commend "fastboot flash boot boot.img" Letters only!
12-Type commend "fastboot reboot" Letters only!!
ALL DONE
how to Gain ROOT???
SUPRIZE ME WITH DONATIONS FOR HARD WORK!! CASHAPP: $adamkey99
1-open settings and Enable Developer options
2- Download-Install Dr Fone Root on your computer HERE'S GOOD LINK TO DOWNLOAD: https://myphoneupdate.com/download-dr-fone-root/
3- connect your device via USB and select file transfer
4- Run Dr Fone Root
5- Accept-install anything might pop up on the phone screen
your phone will reboot multiple times very normal
Congratulations!!! ALL DONE
DONATIONS ARE WELCOMED FOR THE HARD WORK!! CASHAPP: $adamkey99
Hello Adam, thanks for your replies.
I am not understanding well, in the first one you talk about a patched boot.img but there's no link to it.
In the second one you talk about using a 3rd party app, but is it safe? How do you know it does not install some unwanted stuff?
So I don't understand if you rooted your phone in the 1st or 2nd way, but how is it behaving? Any slowdowns/crashes/unwanted behaviours?
Thanks
derjaeger said:
Hello Adam, thanks for your replies.
I am not understanding well, in the first one you talk about a patched boot.img but there's no link to it.
In the second one you talk about using a 3rd party app, but is it safe? How do you know it does not install some unwanted stuff?
So I don't understand if you rooted your phone in the 1st or 2nd way, but how is it behaving? Any slowdowns/crashes/unwanted behaviours?
Click to expand...
Click to collapse
Where to get the boot.img??
1- download and extract the stock room for your device using Winrar or any zipping tools : https://mega.nz/file/rDIAWJaR#TOjmxZl5LdjyVur3lwqP2wgNCm19tNoLhxXioRV8n70
2-look inside the stock room folder you just extracted there's boot.img file
3- Copy the boot.img to your device
4- lunch magisk and patch the boot.img you just moved to your device
5- copy the patched boot.img to your pc
now go follow the steps on my first comment
-------------------------------------------------------
No issues at all