[2ndboot] Custom kernel (no radio) - Milestone 2 General
Here is a port of 2ndboot to milestone2. It successfully boots new kernel, radio(as expected) is not working... but who uses smartphone as a phone anyway?
If you wish to try it:
1) extract attachment onto your sdcard
2) copy /sdcard/2ndboot_gb/hbootuser to /system/bin
3) chmod +x /system/bin/hbootuser
4) turn off lcd panel(otherwise the new kernel will not initialize display correctly)
5) in one console invoke adb shell cat /proc/kmsg (so that the processor does not sleep to deep... otherwise it can take time before it starts to boot )
5) from another console invoke adb shell /sdcard/2ndboot_gb/2ndboot_gb.sh... and cross your fingers(as it sometimes crashes)
Here is a source code:
hxxp://bitbucket.org/czechop/mils2_2ndboot
NOTE1: it is compiled against froyo kernel, so probably wont work with gb. I've tested it with froyo kernel(MILS2_U6_2.4.24) and tezet's CM10 system(btw really nice rom... and very handy that the same system image can work with both froyo and gb kernels ).
NOTE2: it takes quite a lot of time to boot(if it boots at all), so be patient
NOTE3: if you connect serial(ttl 3.3V) <=> usb converter to micro usb port you can grap early console output from the new kernel(speed 115200)
I'm about to test this over CM10 and GB kernel, will it work anyways?
Another question, if I boot this kernel, and then reboot, will I be back in Moto's kernel with radio?
Nice work, btw :good:
OK, I tried this 3 times, with no success, everytime the screen remained turned on but completely black, for about 10-15 seconds, then rebooted to Moto logo.
After the second try, my status bar and navigation buttons were gone, had to wipe dalvik cache to solve it.
Hope it helps you :good:
Lean946 said:
OK, I tried this 3 times, with no success, everytime the screen remained turned on but completely black, for about 10-15 seconds, then rebooted to Moto logo.
After the second try, my status bar and navigation buttons were gone, had to wipe dalvik cache to solve it.
Hope it helps you :good:
Click to expand...
Click to collapse
Did you turn off the screen before invoking the script? Without this the new kernel spends a lot of time tryinig to reinitialize it, and eventually watchdog will reboot the phone.
Have you got to the place where blue and green leds turn on?
czechop said:
Here is a port of 2ndboot to milestone2. It successfully boots new kernel, radio(as expected) is not working... but who uses smartphone as a phone anyway?
If you wish to try it:
1) extract attachment onto your sdcard
2) copy /sdcard/2ndboot_gb/hbootuser to /system/bin
3) chmod +x /system/bin/hbootuser
4) turn off lcd panel(otherwise the new kernel will not initialize display correctly)
5) in one console invoke adb shell cat /proc/kmsg (so that the processor does not sleep to deep... otherwise it can take time before it starts to boot )
5) from another console invoke adb shell /sdcard/2ndboot_gb/2ndboot_gb.sh... and cross your fingers(as it sometimes crashes)
NOTE1: it is compiled against froyo kernel, so probably wont work with gb. I've tested it with froyo kernel(MILS2_U6_2.4.24) and tezet's CM10 system(btw really nice rom... and very handy that the same system image can work with both froyo and gb kernels ).
NOTE2: it takes quite a lot of time to boot(if it boots at all), so be patient
NOTE3: it's my first post here, so... hello to everyone
Click to expand...
Click to collapse
Welcome to XDA and thanks for sharing this! Could you also please share the sources?
It would be cool to have working kexec, Droid 3 guys managed to have it working with radio. Maybe you could look at this and try to port it to our M2?
tezet said:
Welcome to XDA and thanks for sharing this! Could you also please share the sources?
It would be cool to have working kexec, Droid 3 guys managed to have it working with radio. Maybe you could look at this and try to port it to our M2?
Click to expand...
Click to collapse
Just added link to source code(should have done that straightaway)
As far as I know D3 has a different radio, so the chances are not so high it will work with M2... but probably it's worth to try anyway
Hey, nice work you have done! Maybe you should take a look at this repository: http://git.zerfleddert.de/cgi-bin/gitweb.cgi/ms2-kexec
From the same guy who made the MS2Debounce app, he tried some hacking with kexec but he failed, maybe you can find a way out in the code?
dangpzanco said:
Hey, nice work you have done! Maybe you should take a look at this repository: hxxp://git.zerfleddert.de/cgi-bin/gitweb.cgi/ms2-kexec
From the same guy who made the MS2Debounce app, he tried some hacking with kexec but he failed, maybe you can find a way out in the code?
Click to expand...
Click to collapse
Thanks
I've seen this repository. I've send the author PM with info regarding enabling console output(he gave up his work as without debugging info he was not able to progress), so I hope that he will get back to it
In the meantime I've tried 2ndboot to start mbm(milestone1 devs have tried it without success, but I hoped that maybe our mbm is better then the one milestone1 has), but mbm stucks at resetting BP Will try to dig this out(for some time)... and if this does not work(which is almost sure), will try(if my phone survive constant reboots) to look at possibility of passing usb context from the old kernel to the new one, so that to skip enumeration in the new kernel.
czechop said:
Thanks
I've seen this repository. I've send the author PM with info regarding enabling console output(he gave up his work as without debugging info he was not able to progress), so I hope that he will get back to it
In the meantime I've tried 2ndboot to start mbm(milestone1 devs have tried it without success, but I hoped that maybe our mbm is better then the one milestone1 has), but mbm stucks at resetting BP Will try to dig this out(for some time)... and if this does not work(which is almost sure), will try(if my phone survive constant reboots) to look at possibility of passing usb context from the old kernel to the new one, so that to skip enumeration in the new kernel.
Click to expand...
Click to collapse
Great to see someone (else) working on that and making some progress (even small ones is better than none).
Hope you'll reach something working someday.
czechop said:
Here is a port of 2ndboot to milestone2. It successfully boots new kernel, radio(as expected) is not working... but who uses smartphone as a phone anyway?
...
Click to expand...
Click to collapse
i have successfully test this on CM10 with GB kernel. one issue is the adb lost link after the new kernel launched, and un-recognized USB device found.
GREAT jobs! thanks
would you please post a kernel with swap support? it's a good reason for a custom kernel.
mimitech said:
i have successfully test this on CM10 with GB kernel. one issue is the adb lost link after the new kernel launched, and un-recognized USB device found.
GREAT jobs! thanks
would you please post a kernel with swap support? it's a good reason for a custom kernel.
Click to expand...
Click to collapse
Good to know that it works for someone else
Regarding adb, you lost link because micro-usb port is switched to serve as an UART to get console output. If you wish micro-usb to preserve its functionality, replace 2ndboot.ko with the one from the attachement, and in the 2ndboot.sh script add "emu_uart=0" parameter at the end of insmod command. Another option is to use adb over wifi.
Regarding swap support... I attach kernel version compiled with CONFIG_SWAP flag... this should I guess enable swap support(haven't tested that). Please let me know if it works
test progress
I have tested this. both the ADB over USB and swap work OK, thank you very much.
another minor issue is, after reboot into the new kernel, the CPU load is 100% high, all occurred in kernel. the process "khubd" has very high CPU time, and the dmesg show repeated messages:
"
<3>[ 2388.578765] hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
<3>[ 2388.584167] hub 1-0:1.0: unable to enumerate USB device on port 3
<4>[ 2388.588867] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.593536] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.598144] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.602752] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.607391] czecho: hub_port_reset: skipping reset of port 3
"
i have tried switch the 2ndboot.ko to original one, the issue still exists.
this issue should be related with OMPA3 usb hub? please help fix this, after then i guess this custom kernel should be very useful. thanks.
---------- Post added at 03:38 AM ---------- Previous post was at 03:28 AM ----------
post some more information for debug:
vmstat =>
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
1 0 8600 120912 246264 13260 211 431 0 1 0 93 0 0 7
1 0 8600 120916 246264 13260 166 143 0 1 0 96 0 0 3
1 0 8600 120916 246264 13260 222 463 0 2 0 87 0 0 9
2 1 11204 120916 243632 13260 195 104 0 0 0 97 0 0 3
============================================
ps =>
R 0 289 2 0 0 0:0 09:55 00:34:00 [khubd]
============================================
in official kernel, there is a hub with 3 port:
<6>[ 7.889923] usbcore: registered new interface driver hub
<6>[ 8.063293] hub 1-0:1.0: USB hub found
<6>[ 8.063415] hub 1-0:1.0: 3 ports detected
czechop said:
Good to know that it works for someone else
Regarding adb, you lost link because micro-usb port is switched to serve as an UART to get console output. If you wish micro-usb to preserve its functionality, replace 2ndboot.ko with the one from the attachement, and in the 2ndboot.sh script add "emu_uart=0" parameter at the end of insmod command. Another option is to use adb over wifi.
Regarding swap support... I attach kernel version compiled with CONFIG_SWAP flag... this should I guess enable swap support(haven't tested that). Please let me know if it works
Click to expand...
Click to collapse
mimitech said:
I have tested this. both the ADB over USB and swap work OK, thank you very much.
another minor issue is, after reboot into the new kernel, the CPU load is 100% high, all occurred in kernel. the process "khubd" has very high CPU time, and the dmesg show repeated messages:
"
<3>[ 2388.578765] hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
<3>[ 2388.584167] hub 1-0:1.0: unable to enumerate USB device on port 3
<4>[ 2388.588867] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.593536] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.598144] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.602752] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.607391] czecho: hub_port_reset: skipping reset of port 3
"
i have tried switch the 2ndboot.ko to original one, the issue still exists.
this issue should be related with OMPA3 usb hub? please help fix this, after then i guess this custom kernel should be very useful. thanks.
---------- Post added at 03:38 AM ---------- Previous post was at 03:28 AM ----------
post some more information for debug:
vmstat =>
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
1 0 8600 120912 246264 13260 211 431 0 1 0 93 0 0 7
1 0 8600 120916 246264 13260 166 143 0 1 0 96 0 0 3
1 0 8600 120916 246264 13260 222 463 0 2 0 87 0 0 9
2 1 11204 120916 243632 13260 195 104 0 0 0 97 0 0 3
============================================
ps =>
R 0 289 2 0 0 0:0 09:55 00:34:00 [khubd]
============================================
in official kernel, there is a hub with 3 port:
<6>[ 7.889923] usbcore: registered new interface driver hub
<6>[ 8.063293] hub 1-0:1.0: USB hub found
<6>[ 8.063415] hub 1-0:1.0: 3 ports detected
Click to expand...
Click to collapse
The CPU load is probably due to my recent modifications to disable usb reset in new kernel(so that to preserver link with BP)... which of course does not work as expected
Anyway, I guess I could prepare a "clean" kernel with swap support, but maybe it would be better if you do it yourself(so that in the future you could enable other features in the kernel)?
You would need(probably there is many other ways to do it):
1. ubuntu. I personally use 10.04 x64. In my system it cowork with windows xp(actually ubuntu is installed on the windows partition, so it could be easly deleted if space is required)
2. prepare a cross compiler(I use one made with crosstool-ng, but it took me realy loooong time to make it). I guess that the easiest option would be to use cross compiler from android ndk(it should work just fine). So that download ndk
3. find the path to the crosscompiler in extracted ndk(it would be something like android-ndk-r8b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin; should contain gcc and other tools) and add it to PATH
4. download motorola kernel source for milestone 2 from hxxp://sourceforge.net/projects/milestone.motorola/files/. I use version MILS2_U6_4.1-22(kernel is in file kernel_omap3.tgz)
5. extract kernel
6. cd to kernel root
7.edit configuration file(arch/arm/configs/mapphone_defconfig)... enable SWAP etc...
8. being in kernel root dir, invoke: make CROSS_COMPILE='prefix of your crosscompiler, e.g. arm-linux-androideabi-' ARCH=arm mapphone_defconfig
9. being in kernel root dir, invoke: make CROSS_COMPILE='prefix of your crosscompiler, e.g. arm-linux-androideabi-' ARCH=arm bzImage
10. if everything goes fine, your kernel should reside in arch/arm/boot/zImage... copy it over kern in 2ndboot
Let me know how do you feel about building your own custom kernel
Thanks for very detailed instruction. it should not be a problem for me, i have some experience with Linux kernel compiling, i need some time for environment setup and getting familiar with android SDK and cross-compiling tools.
thanks again. I'll let you know if any progress.
czechop said:
Let me know how do you feel about building your own custom kernel
Click to expand...
Click to collapse
I think you could have more luck with radio when starting new kernel from bootmenu, just like 2nd-init.
You may bind it to bootmenu's 2nd-boot option, however I suggest to use all init scripts from 2nd-init as a base, 2nd-boot is not mantained at all.
tezet said:
I think you could have more luck with radio when starting new kernel from bootmenu, just like 2nd-init.
You may bind it to bootmenu's 2nd-boot option, however I suggest to use all init scripts from 2nd-init as a base, 2nd-boot is not mantained at all.
Click to expand...
Click to collapse
Thanks for this tip
BTW, do you know if there is some way to restart then into 2nd-boot via bootmenu automatically(so that I don't need to choose 2nd-boot from the bootmenu list... this would speed booting up a little bit), but preserving 2nd-init as the default bootmenu option?
i have successfully compiled a kernel following your instruction, it's easy i think. but the kernel can't boot, about 10 second after i issue the "2ndboot_gb.sh", the red moto logo appeared, and the phone rebooted.
i use the stock config file, with one modification: 'config_swap=y'.
the kernel i compiled is larger than you provide, size is 3,130,008 bytes. the compiler is arm-linux-androideabi-4.4.3.
do you have any idea about this? maybe you can provide me a clean kernel with swap enabled to test? thanks
czechop said:
Let me know how do you feel about building your own custom kernel
Click to expand...
Click to collapse
---------- Post added at 08:23 AM ---------- Previous post was at 08:18 AM ----------
i post the kernel message before the new kernel reboot, please help me verify the process is ok. thakns
==================================================
<4>[ 221.475616] czecho: hboot_init
<4>[ 221.475708] dev[power.0], driver[power]
<4>[ 221.475799] dev[ram_console.0], driver[ram_console]
<4>[ 221.475982] dev[omap-panel], driver[omap-panel]
<4>[ 221.476074] dev[omapdss], driver[omapdss]
<4>[ 221.476165] dev[sfh7743], driver[sfh7743]
<4>[ 221.476562] dev[bu52014hfv], driver[bu52014hfv]
<4>[ 221.476654] dev[vib-gpio], driver[vib-gpio]
<4>[ 221.476745] dev[musb_hdrc], driver[musb_hdrc]
<4>[ 221.476928] dev[ehci-omap.0], driver[ehci-omap]
<4>[ 221.477020] dev[mapphone_bpwake], driver[mapphone_bpwake]
<4>[ 221.477172] dev[omap_hdq.0], driver[omap_hdq]
<4>[ 221.477264] dev[wl127x-rfkill.0], driver[wl127x-rfkill]
<4>[ 221.477691] dev[wl127x-test.0], driver[UNKNOWN]
<4>[ 221.477783] dev[mmci-omap-hs.0], driver[mmci-omap-hs]
<4>[ 221.477874] dev[mmci-omap-hs.1], driver[mmci-omap-hs]
<4>[ 221.478057] dev[TIWLAN_SDIO.2], driver[TIWLAN_SDIO]
<4>[ 221.478149] dev[omapvout], driver[omapvout]
<4>[ 221.478302] dev[omaplfb], driver[UNKNOWN]
<4>[ 221.478424] dev[usb_mass_storage], driver[usb_mass_storage]
<4>[ 221.478698] dev[rndis], driver[rndis]
<4>[ 221.478881] dev[android_usb], driver[android_usb]
<4>[ 221.478942] dev[sim.1], driver[sim]
<4>[ 221.479125] dev[omap3isp], driver[omap3isp]
<4>[ 221.479217] dev[omap2_mcspi.1], driver[omap2_mcspi]
<4>[ 221.479309] dev[omap2_mcspi.2], driver[omap2_mcspi]
<4>[ 221.479461] dev[omap2_mcspi.3], driver[omap2_mcspi]
<4>[ 221.479553] dev[omap2_mcspi.4], driver[omap2_mcspi]
<4>[ 221.479736] dev[omap-uart.1], driver[omap-uart]
<4>[ 221.479827] dev[omap-uart.2], driver[omap-uart]
<4>[ 221.479919] dev[omap-uart.3], driver[UNKNOWN]
<4>[ 221.480102] dev[omap-mcbsp.1], driver[omap-mcbsp]
<4>[ 221.480194] dev[omap-mcbsp.2], driver[omap-mcbsp]
<4>[ 221.480346] dev[omap-mcbsp.3], driver[omap-mcbsp]
<4>[ 221.480438] dev[omap-mcbsp.4], driver[omap-mcbsp]
<4>[ 221.480560] dev[omap-mcbsp.5], driver[omap-mcbsp]
<4>[ 221.480712] dev[i2c_omap.1], driver[i2c_omap]
<4>[ 221.480804] dev[i2c_omap.2], driver[i2c_omap]
<4>[ 221.480987] dev[i2c_omap.3], driver[i2c_omap]
<4>[ 221.481079] dev[omap_wdt], driver[omap_wdt]
<4>[ 221.481170] dev[omapfb], driver[omapfb]
<4>[ 221.484344] dev[cpcap_uc], driver[cpcap_uc]
<4>[ 221.484466] dev[cpcap_adc], driver[cpcap_adc]
<4>[ 221.484558] dev[cpcap_key], driver[cpcap_key]
<4>[ 221.484710] dev[cpcap_battery], driver[cpcap_battery]
<4>[ 221.484802] dev[cpcap_rtc], driver[cpcap_rtc]
<4>[ 221.484954] dev[cpcap_usb], driver[cpcap_usb]
<4>[ 221.485046] dev[cpcap_usb_det], driver[cpcap_usb_det]
<4>[ 221.485229] dev[cpcap_audio], driver[cpcap_audio]
<4>[ 221.485321] dev[cpcap_3mm5], driver[cpcap_3mm5]
<4>[ 221.485382] dev[bd7885], driver[bd7885]
<4>[ 221.485565] dev[leds-cpcap-kpb], driver[leds-cpcap-kpb]
<4>[ 221.485656] dev[leds-cpcap-gpio], driver[leds-cpcap-gpio]
<4>[ 221.485809] dev[leds-cpcap-rgb], driver[leds-cpcap-rgb]
<4>[ 221.485900] dev[flash-torch], driver[flash-torch]
<4>[ 221.485992] dev[wakeup_timer.0], driver[wakeup_timer]
<4>[ 221.486145] dev[omap-iommu.0], driver[omap-iommu]
<4>[ 221.486236] dev[C6410], driver[C6410]
<4>[ 221.486419] dev[adp5588-backlight], driver[UNKNOWN]
<4>[ 221.486511] dev[keyreset.0], driver[keyreset]
<4>[ 221.486572] dev[gpio-event.0], driver[gpio-event]
<4>[ 221.486755] dev[device_wifi.1], driver[device_wifi]
<4>[ 221.486846] dev[gpio-device.0], driver[gpio-device]
<4>[ 221.486999] dev[clock_32k], driver[clock_32k]
<4>[ 221.487091] dev[alarm], driver[alarm]
<4>[ 221.487182] dev[hp3a], driver[hp3a]
<4>[ 221.487365] dev[hplens-i2c], driver[UNKNOWN]
<4>[ 221.487426] dev[cpcap_usb_charger], driver[cpcap_usb_charger]
<4>[ 221.487609] dev[cpcap_usb_connected], driver[cpcap_usb_connected]
<4>[ 221.487701] dev[ondemand], driver[ondemand]
<4>[ 221.487854] dev[pvrsrvkm], driver[pvrsrvkm]
<4>[ 221.487945] dev[cpcap_usbled], driver[cpcap_usbled]
<4>[ 221.488037] hboot_init
<6>[ 221.488220] hbootctrl: Successfully registered dev
<6>[ 221.548248] hbootctrl: `open' stub called
<4>[ 221.549468] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.549652] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[0], type[0], attrs[0], size[9556], rest[0]
<4>[ 221.549743] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[0]
<4>[ 221.549926] hbootctrl: ioctl. cmd[4], arg[0]
<4>[ 221.550018] hbootctrl: HBOOT_SELECT_BUFFER. handle[0], ret[0]
<4>[ 221.551422] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.551513] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[1], type[1], attrs[1], size[3130008], rest[0]
<4>[ 221.597412] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[1]
<4>[ 221.597534] hbootctrl: ioctl. cmd[4], arg[1]
<4>[ 221.597686] hbootctrl: HBOOT_SELECT_BUFFER. handle[1], ret[0]
<4>[ 221.899444] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.899627] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[2], type[1], attrs[1], size[150558], rest[0]
<4>[ 221.899810] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[2]
<4>[ 221.899993] hbootctrl: ioctl. cmd[4], arg[2]
<4>[ 221.900085] hbootctrl: HBOOT_SELECT_BUFFER. handle[2], ret[0]
<4>[ 221.911102] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.911193] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[3], type[0], attrs[1], size[6220], rest[0]
<4>[ 222.208953] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[3]
<4>[ 222.209075] hbootctrl: ioctl. cmd[4], arg[3]
<4>[ 222.209228] hbootctrl: HBOOT_SELECT_BUFFER. handle[3], ret[0]
<4>[ 222.210693] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 222.210876] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[4], type[0], attrs[1], size[294], rest[0]
<4>[ 222.210968] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[4]
<4>[ 222.211120] hbootctrl: ioctl. cmd[4], arg[4]
<4>[ 222.211212] hbootctrl: HBOOT_SELECT_BUFFER. handle[4], ret[0]
<4>[ 222.212097] hbootctrl: ioctl. cmd[3], arg[0]
<4>[ 222.212188] hbootctrl: HBOOT_BOOT1. handle[0]
<4>[ 222.212432] hboot_boot
mimitech said:
i have successfully compiled a kernel following your instruction, it's easy i think. but the kernel can't boot, about 10 second after i issue the "2ndboot_gb.sh", the red moto logo appeared, and the phone rebooted.
i use the stock config file, with one modification: 'config_swap=y'.
the kernel i compiled is larger than you provide, size is 3,130,008 bytes. the compiler is arm-linux-androideabi-4.4.3.
do you have any idea about this? maybe you can provide me a clean kernel with swap enabled to test? thanks
---------- Post added at 08:23 AM ---------- Previous post was at 08:18 AM ----------
i post the kernel message before the new kernel reboot, please help me verify the process is ok. thakns
==================================================
<4>[ 221.475616] czecho: hboot_init
<4>[ 221.475708] dev[power.0], driver[power]
<4>[ 221.475799] dev[ram_console.0], driver[ram_console]
<4>[ 221.475982] dev[omap-panel], driver[omap-panel]
<4>[ 221.476074] dev[omapdss], driver[omapdss]
<4>[ 221.476165] dev[sfh7743], driver[sfh7743]
<4>[ 221.476562] dev[bu52014hfv], driver[bu52014hfv]
<4>[ 221.476654] dev[vib-gpio], driver[vib-gpio]
<4>[ 221.476745] dev[musb_hdrc], driver[musb_hdrc]
<4>[ 221.476928] dev[ehci-omap.0], driver[ehci-omap]
<4>[ 221.477020] dev[mapphone_bpwake], driver[mapphone_bpwake]
<4>[ 221.477172] dev[omap_hdq.0], driver[omap_hdq]
<4>[ 221.477264] dev[wl127x-rfkill.0], driver[wl127x-rfkill]
<4>[ 221.477691] dev[wl127x-test.0], driver[UNKNOWN]
<4>[ 221.477783] dev[mmci-omap-hs.0], driver[mmci-omap-hs]
<4>[ 221.477874] dev[mmci-omap-hs.1], driver[mmci-omap-hs]
<4>[ 221.478057] dev[TIWLAN_SDIO.2], driver[TIWLAN_SDIO]
<4>[ 221.478149] dev[omapvout], driver[omapvout]
<4>[ 221.478302] dev[omaplfb], driver[UNKNOWN]
<4>[ 221.478424] dev[usb_mass_storage], driver[usb_mass_storage]
<4>[ 221.478698] dev[rndis], driver[rndis]
<4>[ 221.478881] dev[android_usb], driver[android_usb]
<4>[ 221.478942] dev[sim.1], driver[sim]
<4>[ 221.479125] dev[omap3isp], driver[omap3isp]
<4>[ 221.479217] dev[omap2_mcspi.1], driver[omap2_mcspi]
<4>[ 221.479309] dev[omap2_mcspi.2], driver[omap2_mcspi]
<4>[ 221.479461] dev[omap2_mcspi.3], driver[omap2_mcspi]
<4>[ 221.479553] dev[omap2_mcspi.4], driver[omap2_mcspi]
<4>[ 221.479736] dev[omap-uart.1], driver[omap-uart]
<4>[ 221.479827] dev[omap-uart.2], driver[omap-uart]
<4>[ 221.479919] dev[omap-uart.3], driver[UNKNOWN]
<4>[ 221.480102] dev[omap-mcbsp.1], driver[omap-mcbsp]
<4>[ 221.480194] dev[omap-mcbsp.2], driver[omap-mcbsp]
<4>[ 221.480346] dev[omap-mcbsp.3], driver[omap-mcbsp]
<4>[ 221.480438] dev[omap-mcbsp.4], driver[omap-mcbsp]
<4>[ 221.480560] dev[omap-mcbsp.5], driver[omap-mcbsp]
<4>[ 221.480712] dev[i2c_omap.1], driver[i2c_omap]
<4>[ 221.480804] dev[i2c_omap.2], driver[i2c_omap]
<4>[ 221.480987] dev[i2c_omap.3], driver[i2c_omap]
<4>[ 221.481079] dev[omap_wdt], driver[omap_wdt]
<4>[ 221.481170] dev[omapfb], driver[omapfb]
<4>[ 221.484344] dev[cpcap_uc], driver[cpcap_uc]
<4>[ 221.484466] dev[cpcap_adc], driver[cpcap_adc]
<4>[ 221.484558] dev[cpcap_key], driver[cpcap_key]
<4>[ 221.484710] dev[cpcap_battery], driver[cpcap_battery]
<4>[ 221.484802] dev[cpcap_rtc], driver[cpcap_rtc]
<4>[ 221.484954] dev[cpcap_usb], driver[cpcap_usb]
<4>[ 221.485046] dev[cpcap_usb_det], driver[cpcap_usb_det]
<4>[ 221.485229] dev[cpcap_audio], driver[cpcap_audio]
<4>[ 221.485321] dev[cpcap_3mm5], driver[cpcap_3mm5]
<4>[ 221.485382] dev[bd7885], driver[bd7885]
<4>[ 221.485565] dev[leds-cpcap-kpb], driver[leds-cpcap-kpb]
<4>[ 221.485656] dev[leds-cpcap-gpio], driver[leds-cpcap-gpio]
<4>[ 221.485809] dev[leds-cpcap-rgb], driver[leds-cpcap-rgb]
<4>[ 221.485900] dev[flash-torch], driver[flash-torch]
<4>[ 221.485992] dev[wakeup_timer.0], driver[wakeup_timer]
<4>[ 221.486145] dev[omap-iommu.0], driver[omap-iommu]
<4>[ 221.486236] dev[C6410], driver[C6410]
<4>[ 221.486419] dev[adp5588-backlight], driver[UNKNOWN]
<4>[ 221.486511] dev[keyreset.0], driver[keyreset]
<4>[ 221.486572] dev[gpio-event.0], driver[gpio-event]
<4>[ 221.486755] dev[device_wifi.1], driver[device_wifi]
<4>[ 221.486846] dev[gpio-device.0], driver[gpio-device]
<4>[ 221.486999] dev[clock_32k], driver[clock_32k]
<4>[ 221.487091] dev[alarm], driver[alarm]
<4>[ 221.487182] dev[hp3a], driver[hp3a]
<4>[ 221.487365] dev[hplens-i2c], driver[UNKNOWN]
<4>[ 221.487426] dev[cpcap_usb_charger], driver[cpcap_usb_charger]
<4>[ 221.487609] dev[cpcap_usb_connected], driver[cpcap_usb_connected]
<4>[ 221.487701] dev[ondemand], driver[ondemand]
<4>[ 221.487854] dev[pvrsrvkm], driver[pvrsrvkm]
<4>[ 221.487945] dev[cpcap_usbled], driver[cpcap_usbled]
<4>[ 221.488037] hboot_init
<6>[ 221.488220] hbootctrl: Successfully registered dev
<6>[ 221.548248] hbootctrl: `open' stub called
<4>[ 221.549468] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.549652] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[0], type[0], attrs[0], size[9556], rest[0]
<4>[ 221.549743] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[0]
<4>[ 221.549926] hbootctrl: ioctl. cmd[4], arg[0]
<4>[ 221.550018] hbootctrl: HBOOT_SELECT_BUFFER. handle[0], ret[0]
<4>[ 221.551422] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.551513] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[1], type[1], attrs[1], size[3130008], rest[0]
<4>[ 221.597412] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[1]
<4>[ 221.597534] hbootctrl: ioctl. cmd[4], arg[1]
<4>[ 221.597686] hbootctrl: HBOOT_SELECT_BUFFER. handle[1], ret[0]
<4>[ 221.899444] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.899627] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[2], type[1], attrs[1], size[150558], rest[0]
<4>[ 221.899810] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[2]
<4>[ 221.899993] hbootctrl: ioctl. cmd[4], arg[2]
<4>[ 221.900085] hbootctrl: HBOOT_SELECT_BUFFER. handle[2], ret[0]
<4>[ 221.911102] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.911193] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[3], type[0], attrs[1], size[6220], rest[0]
<4>[ 222.208953] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[3]
<4>[ 222.209075] hbootctrl: ioctl. cmd[4], arg[3]
<4>[ 222.209228] hbootctrl: HBOOT_SELECT_BUFFER. handle[3], ret[0]
<4>[ 222.210693] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 222.210876] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[4], type[0], attrs[1], size[294], rest[0]
<4>[ 222.210968] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[4]
<4>[ 222.211120] hbootctrl: ioctl. cmd[4], arg[4]
<4>[ 222.211212] hbootctrl: HBOOT_SELECT_BUFFER. handle[4], ret[0]
<4>[ 222.212097] hbootctrl: ioctl. cmd[3], arg[0]
<4>[ 222.212188] hbootctrl: HBOOT_BOOT1. handle[0]
<4>[ 222.212432] hboot_boot
Click to expand...
Click to collapse
That was really quick.... I've spend almost a week configuring environment
The logs from the org kernel are ok. And the kernel is larger then mine probably due to a fact that I use slightly different compiler. But I guess that should not be a problem. Could you post your kernel? I would check if there is "uncompressing linux..." console output from the new kernel over micro-usb.
i have trouble with upload attachment in this forum. please download my kernel from here: "www . mimitech . net / zImage1" (please delete all space in it)
thanks
czechop said:
That was really quick.... I've spend almost a week configuring environment
The logs from the org kernel are ok. And the kernel is larger then mine probably due to a fact that I use slightly different compiler. But I guess that should not be a problem. Could you post your kernel? I would check if there is "uncompressing linux..." console output from the new kernel over micro-usb.
Click to expand...
Click to collapse
czechop said:
Thanks for this tip
BTW, do you know if there is some way to restart then into 2nd-boot via bootmenu automatically(so that I don't need to choose 2nd-boot from the bootmenu list... this would speed booting up a little bit), but preserving 2nd-init as the default bootmenu option?
Click to expand...
Click to collapse
No, there's no such feature. But simple modification of init scripts will do the job. You could just create file before restart and check it's presence in one of init scripts, e.g. 2nd-init.sh. Depending on file presence proceed with regular 2nd-init contents or run 2nd-boot.
That's the quickest I can think of.
Related
HELP [ROM]Lightspeed_1.0.2 USB ERROR
I got this error from dmesg on a freshly installed Lightspeed ROM Code: <4>[ 11.582224] ------------[ cut here ]------------ <4>[ 11.582333] WARNING: at /home/simba/autobuild/a501/mdrr_mr2/android/kernel/arch/arm/mach-tegra/usb_phy.c:515 tegra_usb_phy_power_on+0xd3c/0xd8c() <4>[ 11.582490] Modules linked in: <4>[ 11.582748] [<c003864c>] (unwind_backtrace+0x0/0xf0) from [<c00694d0>] (warn_slowpath_common+0x4c/0x64) <4>[ 11.582929] [<c00694d0>] (warn_slowpath_common+0x4c/0x64) from [<c0069500>] (warn_slowpath_null+0x18/0x1c) <4>[ 11.583027] [<c0069500>] (warn_slowpath_null+0x18/0x1c) from [<c00487f4>] (tegra_usb_phy_power_on+0xd3c/0xd8c) <4>[ 11.583207] [<c00487f4>] (tegra_usb_phy_power_on+0xd3c/0xd8c) from [<c025973c>] (tegra_ehci_probe+0x22c/0x398) <4>[ 11.583384] [<c025973c>] (tegra_ehci_probe+0x22c/0x398) from [<c01f6c8c>] (platform_drv_probe+0x18/0x1c) <4>[ 11.583552] [<c01f6c8c>] (platform_drv_probe+0x18/0x1c) from [<c01f5dfc>] (driver_probe_device+0xc8/0x184) <4>[ 11.583715] [<c01f5dfc>] (driver_probe_device+0xc8/0x184) from [<c01f5f18>] (__driver_attach+0x60/0x84) <4>[ 11.583880] [<c01f5f18>] (__driver_attach+0x60/0x84) from [<c01f5630>] (bus_for_each_dev+0x48/0x84) <4>[ 11.584045] [<c01f5630>] (bus_for_each_dev+0x48/0x84) from [<c01f4f84>] (bus_add_driver+0x9c/0x20c) <4>[ 11.584140] [<c01f4f84>] (bus_add_driver+0x9c/0x20c) from [<c01f6204>] (driver_register+0xa8/0x134) <4>[ 11.584310] [<c01f6204>] (driver_register+0xa8/0x134) from [<c001d84c>] (ehci_hcd_init+0x58/0x88) <4>[ 11.584480] [<c001d84c>] (ehci_hcd_init+0x58/0x88) from [<c0032584>] (do_one_initcall+0xd0/0x1a4) <4>[ 11.584646] [<c0032584>] (do_one_initcall+0xd0/0x1a4) from [<c0008588>] (kernel_init+0x14c/0x210) <4>[ 11.584809] [<c0008588>] (kernel_init+0x14c/0x210) from [<c0033bc4>] (kernel_thread_exit+0x0/0x8) <4>[ 11.584905] ---[ end trace 2f44094fb41243fe ]---
Unstable Wifi on EOS 30 and 32?
I've been playing about with the EOS build of ICS for the Xoom MZ604, and seem to have a unique problem. The wireless constantly drops, every few minutes or so. It was installed after a full wipe of stock (factory reset and cache format with CWM), firstly with revision 30 which dropped every 5 mins or so, and then with 32 (again, full wipe prior to install), which drops every minute or so. I noticed this when running dmesg: Code: <4>[ 3937.928526] ------------[ cut here ]------------ <4>[ 3937.928716] WARNING: at net/wireless/scan.c:403 cfg80211_bss_update+0x24/0x384() <4>[ 3937.928805] Modules linked in: <4>[ 3937.929063] [<c0042e64>] (unwind_backtrace+0x0/0xf0) from [<c007070c>] (warn_slowpath_common+0x4c/0x64) <4>[ 3937.929231] [<c007070c>] (warn_slowpath_common+0x4c/0x64) from [<c007073c>] (warn_slowpath_null+0x18/0x1c) <4>[ 3937.929329] [<c007073c>] (warn_slowpath_null+0x18/0x1c) from [<c0460a78>] (cfg80211_bss_update+0x24/0x384) <4>[ 3937.929499] [<c0460a78>] (cfg80211_bss_update+0x24/0x384) from [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) <4>[ 3937.929673] [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) from [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) <4>[ 3937.929844] [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) from [<c0285520>] (wl_inform_bss+0x44/0xa8) <4>[ 3937.930011] [<c0285520>] (wl_inform_bss+0x44/0xa8) from [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) <4>[ 3937.930176] [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) from [<c0284b48>] (wl_event_handler+0xac/0x17c) <4>[ 3937.930350] [<c0284b48>] (wl_event_handler+0xac/0x17c) from [<c003e5d8>] (kernel_thread_exit+0x0/0x8) <4>[ 3937.930442] ---[ end trace 1b75b31a2719eeee ]--- <3>[ 3937.930602] CFG80211-ERROR) wl_inform_single_bss : cfg80211_inform_bss_frame error <4>[ 3943.236683] ------------[ cut here ]------------ <4>[ 3943.237118] WARNING: at net/wireless/scan.c:403 cfg80211_bss_update+0x24/0x384() <4>[ 3943.237760] Modules linked in: <4>[ 3943.238488] [<c0042e64>] (unwind_backtrace+0x0/0xf0) from [<c007070c>] (warn_slowpath_common+0x4c/0x64) <4>[ 3943.239169] [<c007070c>] (warn_slowpath_common+0x4c/0x64) from [<c007073c>] (warn_slowpath_null+0x18/0x1c) <4>[ 3943.239853] [<c007073c>] (warn_slowpath_null+0x18/0x1c) from [<c0460a78>] (cfg80211_bss_update+0x24/0x384) <4>[ 3943.240252] [<c0460a78>] (cfg80211_bss_update+0x24/0x384) from [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) <4>[ 3943.240940] [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) from [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) <4>[ 3943.241621] [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) from [<c0285520>] (wl_inform_bss+0x44/0xa8) <4>[ 3943.242304] [<c0285520>] (wl_inform_bss+0x44/0xa8) from [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) <4>[ 3943.242975] [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) from [<c0284b48>] (wl_event_handler+0xac/0x17c) <4>[ 3943.243670] [<c0284b48>] (wl_event_handler+0xac/0x17c) from [<c003e5d8>] (kernel_thread_exit+0x0/0x8) <4>[ 3943.244326] ---[ end trace 1b75b31a2719eeef ]--- <3>[ 3943.244684] CFG80211-ERROR) wl_inform_single_bss : cfg80211_inform_bss_frame error <4>[ 3943.278521] wl_bss_connect_done succeeded status=(0x9) <6>[ 3943.328742] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready <4>[ 3943.336519] wlan0: set promisc 0 failed <4>[ 3943.348994] wlan0: set promisc 0 failed <4>[ 3943.354353] wl_bss_connect_done succeeded status=(0x11) Not sure if this is what is needed to debug it, if not tell me what is needed. Any ideas why I'm getting this? I've had a bit of a search, but I can't see anything relevant on XDA or via Google. Under stock, never had an issue with wireless. And I do appreciate that EOS is very much beta at the moment.
VaKo said: I've been playing about with the EOS build of ICS for the Xoom MZ604, and seem to have a unique problem. The wireless constantly drops, every few minutes or so. It was installed after a full wipe of stock (factory reset and cache format with CWM), firstly with revision 30 which dropped every 5 mins or so, and then with 32 (again, full wipe prior to install), which drops every minute or so. I noticed this when running dmesg: Code: <4>[ 3937.928526] ------------[ cut here ]------------ <4>[ 3937.928716] WARNING: at net/wireless/scan.c:403 cfg80211_bss_update+0x24/0x384() <4>[ 3937.928805] Modules linked in: <4>[ 3937.929063] [<c0042e64>] (unwind_backtrace+0x0/0xf0) from [<c007070c>] (warn_slowpath_common+0x4c/0x64) <4>[ 3937.929231] [<c007070c>] (warn_slowpath_common+0x4c/0x64) from [<c007073c>] (warn_slowpath_null+0x18/0x1c) <4>[ 3937.929329] [<c007073c>] (warn_slowpath_null+0x18/0x1c) from [<c0460a78>] (cfg80211_bss_update+0x24/0x384) <4>[ 3937.929499] [<c0460a78>] (cfg80211_bss_update+0x24/0x384) from [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) <4>[ 3937.929673] [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) from [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) <4>[ 3937.929844] [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) from [<c0285520>] (wl_inform_bss+0x44/0xa8) <4>[ 3937.930011] [<c0285520>] (wl_inform_bss+0x44/0xa8) from [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) <4>[ 3937.930176] [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) from [<c0284b48>] (wl_event_handler+0xac/0x17c) <4>[ 3937.930350] [<c0284b48>] (wl_event_handler+0xac/0x17c) from [<c003e5d8>] (kernel_thread_exit+0x0/0x8) <4>[ 3937.930442] ---[ end trace 1b75b31a2719eeee ]--- <3>[ 3937.930602] CFG80211-ERROR) wl_inform_single_bss : cfg80211_inform_bss_frame error <4>[ 3943.236683] ------------[ cut here ]------------ <4>[ 3943.237118] WARNING: at net/wireless/scan.c:403 cfg80211_bss_update+0x24/0x384() <4>[ 3943.237760] Modules linked in: <4>[ 3943.238488] [<c0042e64>] (unwind_backtrace+0x0/0xf0) from [<c007070c>] (warn_slowpath_common+0x4c/0x64) <4>[ 3943.239169] [<c007070c>] (warn_slowpath_common+0x4c/0x64) from [<c007073c>] (warn_slowpath_null+0x18/0x1c) <4>[ 3943.239853] [<c007073c>] (warn_slowpath_null+0x18/0x1c) from [<c0460a78>] (cfg80211_bss_update+0x24/0x384) <4>[ 3943.240252] [<c0460a78>] (cfg80211_bss_update+0x24/0x384) from [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) <4>[ 3943.240940] [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) from [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) <4>[ 3943.241621] [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) from [<c0285520>] (wl_inform_bss+0x44/0xa8) <4>[ 3943.242304] [<c0285520>] (wl_inform_bss+0x44/0xa8) from [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) <4>[ 3943.242975] [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) from [<c0284b48>] (wl_event_handler+0xac/0x17c) <4>[ 3943.243670] [<c0284b48>] (wl_event_handler+0xac/0x17c) from [<c003e5d8>] (kernel_thread_exit+0x0/0x8) <4>[ 3943.244326] ---[ end trace 1b75b31a2719eeef ]--- <3>[ 3943.244684] CFG80211-ERROR) wl_inform_single_bss : cfg80211_inform_bss_frame error <4>[ 3943.278521] wl_bss_connect_done succeeded status=(0x9) <6>[ 3943.328742] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready <4>[ 3943.336519] wlan0: set promisc 0 failed <4>[ 3943.348994] wlan0: set promisc 0 failed <4>[ 3943.354353] wl_bss_connect_done succeeded status=(0x11) Not sure if this is what is needed to debug it, if not tell me what is needed. Any ideas why I'm getting this? I've had a bit of a search, but I can't see anything relevant on XDA or via Google. Under stock, never had an issue with wireless. And I do appreciate that EOS is very much beta at the moment. Click to expand... Click to collapse You have more than enough posts, why not post this on EOS dev thread? Or on the bug reporting site?
My MZ604 running the EOS 32 ROM refused to connect to a wifi network earlier. I went into the wifi settings to select the network and it said something about it avoiding the low signal or whatever (I don't remember exactly what it said) even though that network's signal was excellent. It was when it tried to connect to it that it showed the signal as being poor to nonexistent. I'm connected to my home network fine but I hope that issue doesn't repeat itself on a regular basis. |Sent with XDA Premium via my X°°M ΔKΔ the antithesis to the iPad|
I haven't had any issues with wifi on 29, 30, 31, or 32. Did you by chance try a different access point or reset router? Just wondering sometimes the simple things cause the issues.
okantomi said: You have more than enough posts, why not post this on EOS dev thread? Or on the bug reporting site? Click to expand... Click to collapse Because I'm not entirely sure it is a bug with EOS. I'm running the same hardware and software build as many other people, yet seem to be the only one with this problem. And I don't think "my wireless is unstable" is good enough to log a bug report without additional details, which I don't know how to obtain. jaekidd1012 said: My MZ604 running the EOS 32 ROM refused to connect to a wifi network earlier. I went into the wifi settings to select the network and it said something about it avoiding the low signal or whatever (I don't remember exactly what it said) even though that network's signal was excellent. It was when it tried to connect to it that it showed the signal as being poor to nonexistent. I'm connected to my home network fine but I hope that issue doesn't repeat itself on a regular basis. Click to expand... Click to collapse chasehq11 said: I haven't had any issues with wifi on 29, 30, 31, or 32. Did you by chance try a different access point or reset router? Just wondering sometimes the simple things cause the issues. Click to expand... Click to collapse I get the same issue with different AP's, and the when it drops the scan can't pickup any of the AP's near me.
VaKo said: Because I'm not entirely sure it is a bug with EOS. I'm running the same hardware and software build as many other people, yet seem to be the only one with this problem. And I don't think "my wireless is unstable" is good enough to log a bug report without additional details, which I don't know how to obtain. I get the same issue with different AP's, and the when it drops the scan can't pickup any of the AP's near me. Click to expand... Click to collapse Create a bug report for it. It looks like the wifi driver is crashing for some reason. If you could log the issue at https://bugs.teameos.org and provide a description of what security your access point has, if it has any special characters in the name etc. Please also attach outputs from dmesg and logcat.
http://bugs.teameos.org/show_bug.cgi?id=37 Thanks mate. If you need any more details then tell me.
[Q] Nexus7 cant connect to wifi hotspots
Hey, so I am having issues getting my nexus 7 to connect to: 1) A WiFi hit spot sold by sprint 2) WiFi tether for root users on my epic 4g touch Every time I try to connect, it just sits there saying Saved, when it attempts to connect, it does the following. <6>[ 1731.085143] gpio_keys: Pressed KEY_VOLUMEUP <6>[ 1732.075103] gpio_keys: Released KEY_VOLUMEUP <4>[ 1742.238678] connect failed event=0 e->status 1 e->reason 0 <3>[ 1742.239261] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed <6>[ 1742.905188] gpio_keys: Pressed KEY_VOLUMEUP <4>[ 1743.796567] cpu_up(1)+ <7>[ 1743.819992] tegra CPU: force EDP limit 1200000 kHz <4>[ 1743.820228] CPU1: Booted secondary processor <4>[ 1743.820922] cpu_up(1)- <6>[ 1743.825092] Switched to NOHz mode on CPU #1 <6>[ 1745.355185] gpio_keys: Released KEY_VOLUMEUP <4>[ 1747.495190] cpu_down(1)+ <4>[ 1747.497796] stop_machine_cpu_stop smp=0 <4>[ 1747.497819] stop_machine_cpu_stop smp=1 <5>[ 1747.501350] CPU1: shutdown <4>[ 1747.505652] cpu_down(1)- <4>[ 1754.209707] connect failed event=0 e->status 1 e->reason 0 <3>[ 1754.210075] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed <4>[ 1766.179474] connect failed event=0 e->status 1 e->reason 0 <3>[ 1766.179604] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed <4>[ 1768.175110] cpu_up(1)+ <7>[ 1768.197452] tegra CPU: force EDP limit 1200000 kHz <4>[ 1768.197685] CPU1: Booted secondary processor <4>[ 1768.198278] cpu_up(1)- <6>[ 1768.205065] Switched to NOHz mode on CPU #1 <4>[ 1770.675130] cpu_down(1)+ <4>[ 1770.676925] stop_machine_cpu_stop smp=0 <4>[ 1770.676948] stop_machine_cpu_stop smp=1 <5>[ 1770.679400] CPU1: shutdown <4>[ 1770.682323] cpu_down(1)- <4>[ 1772.935077] cpu_up(1)+ <4>[ 1772.956078] CPU1: Booted secondary processor <4>[ 1772.956804] cpu_up(1)- <6>[ 1772.965070] Switched to NOHz mode on CPU #1 <5>[ 1773.297550] bq27541_get_psp status: Discharging ret= 0x0101 <5>[ 1773.298205] bq27541_get_psp voltage_now= 3737000 uV <5>[ 1773.298844] bq27541_get_capacity = 31% ret= 35 <5>[ 1773.299535] bq27541_get_psp temperature= 290 (0.1¢XC) <5>[ 1773.301018] bq27541_get_capacity = 31% ret= 35 <5>[ 1773.301791] bq27541_get_psp voltage_now= 3737000 uV <5>[ 1773.302505] bq27541_get_psp temperature= 290 (0.1¢XC) <5>[ 1773.303274] bq27541_get_psp status: Discharging ret= 0x0101 <4>[ 1775.236203] cpu_down(1)+ <4>[ 1775.238012] stop_machine_cpu_stop smp=0 <4>[ 1775.238033] stop_machine_cpu_stop smp=1 <5>[ 1775.240341] CPU1: shutdown <4>[ 1775.243291] cpu_down(1)- <4>[ 1779.005135] cpu_up(1)+ <7>[ 1779.044705] tegra CPU: force EDP limit 1200000 kHz <4>[ 1779.044947] CPU1: Booted secondary processor <6>[ 1779.045076] Switched to NOHz mode on CPU #1 <4>[ 1779.055396] cpu_up(1)- <4>[ 1779.105085] cpu_up(2)+ <4>[ 1779.105756] CPU2: Booted secondary processor <4>[ 1779.106395] cpu_up(2)- <6>[ 1779.115065] Switched to NOHz mode on CPU #2 <4>[ 1779.156698] connect failed event=0 e->status 1 e->reason 0 <3>[ 1779.156862] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed <4>[ 1781.205190] cpu_down(1)+ <4>[ 1781.208001] stop_machine_cpu_stop smp=0 <4>[ 1781.208026] stop_machine_cpu_stop smp=1 <4>[ 1781.208047] stop_machine_cpu_stop smp=2 <5>[ 1781.211678] CPU1: shutdown <4>[ 1781.215786] cpu_down(1)- <4>[ 1783.205273] cpu_down(2)+ <4>[ 1783.207760] stop_machine_cpu_stop smp=0 <4>[ 1783.207785] stop_machine_cpu_stop smp=2 <5>[ 1783.211411] CPU2: shutdown <4>[ 1783.214996] cpu_down(2)- <4>[ 1790.855129] cpu_up(1)+ <7>[ 1790.885773] tegra CPU: force EDP limit 1200000 kHz <4>[ 1790.886013] CPU1: Booted secondary processor <6>[ 1790.895086] Switched to NOHz mode on CPU #1 <4>[ 1790.896718] cpu_up(1)- <4>[ 1791.131409] connect failed event=0 e->status 1 e->reason 0 <3>[ 1791.131768] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed <4>[ 1793.055193] cpu_down(1)+ <4>[ 1793.057518] stop_machine_cpu_stop smp=0 <4>[ 1793.057541] stop_machine_cpu_stop smp=1 <5>[ 1793.061289] CPU1: shutdown <4>[ 1793.065042] cpu_down(1)- <4>[ 1795.855139] cpu_up(1)+ <7>[ 1795.885792] tegra CPU: force EDP limit 1200000 kHz <4>[ 1795.886027] CPU1: Booted secondary processor <6>[ 1795.895092] Switched to NOHz mode on CPU #1 <4>[ 1795.896734] cpu_up(1)- <4>[ 1798.255168] cpu_down(1)+ <4>[ 1798.267013] stop_machine_cpu_stop smp=0 <4>[ 1798.267033] stop_machine_cpu_stop smp=1 <5>[ 1798.269651] CPU1: shutdown <4>[ 1798.272700] cpu_down(1)- <4>[ 1800.255080] cpu_up(1)+ <4>[ 1800.256713] connect failed event=0 e->status 1 e->reason 0 <3>[ 1800.256787] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed <4>[ 1800.276129] CPU1: Booted secondary processor <4>[ 1800.276841] cpu_up(1)- <6>[ 1800.285069] Switched to NOHz mode on CPU #1 <4>[ 1802.355169] cpu_down(1)+ <4>[ 1802.357613] stop_machine_cpu_stop smp=0 <4>[ 1802.357636] stop_machine_cpu_stop smp=1 <5>[ 1802.361199] CPU1: shutdown <4>[ 1802.364700] cpu_down(1)- <4>[ 1807.235110] cpu_up(1)+ <4>[ 1807.256269] CPU1: Booted secondary processor <4>[ 1807.257405] cpu_up(1)- <6>[ 1807.265082] Switched to NOHz mode on CPU #1 <4>[ 1809.335168] cpu_down(1)+ <4>[ 1809.337691] stop_machine_cpu_stop smp=0 <4>[ 1809.337716] stop_machine_cpu_stop smp=1 <5>[ 1809.341149] CPU1: shutdown <4>[ 1809.346352] cpu_down(1)- <4>[ 1812.195150] cpu_up(1)+ <4>[ 1812.216592] connect failed event=0 e->status 1 e->reason 0 <3>[ 1812.216675] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed <7>[ 1812.235578] tegra CPU: force EDP limit 1200000 kHz <4>[ 1812.235817] CPU1: Booted secondary processor <4>[ 1812.241341] cpu_up(1)- <6>[ 1812.245097] Switched to NOHz mode on CPU #1 <4>[ 1814.395180] cpu_down(1)+ <4>[ 1814.398667] stop_machine_cpu_stop smp=0 <4>[ 1814.398690] stop_machine_cpu_stop smp=1 <5>[ 1814.400749] CPU1: shutdown <4>[ 1814.404283] cpu_down(1)- <4>[ 1816.142361] wl_bss_connect_done succeeded with 00:22:75:99:39:f9 <6>[ 1816.145835] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready <4>[ 1816.300417] wl_bss_connect_done succeeded with 00:22:75:99:39:f9 <4>[ 1816.595097] cpu_up(1)+ <7>[ 1816.636158] tegra CPU: force EDP limit 1200000 kHz <4>[ 1816.636391] CPU1: Booted secondary processor <6>[ 1816.645084] Switched to NOHz mode on CPU #1 <4>[ 1816.647752] cpu_up(1)- Click to expand... Click to collapse The last bit when it connects is me connecting to a random billing router. I tried resetting all the devices, forgetting the pass code on the nexus and retyping it again. So far nothing has worked. Has anyone has a similar issue.
does your home wifi work? what channel/frequency are your modems? r u running an custom rom with custom kernel? more info would be helpful
Access point at home works fine. The nexus is currently stock minus being rooted. I believe the APs were on channel 1 or 2. It seems to have connected fine to the hotspot that sprint gives out. When I tried to connect to WiFi tether on my epic touch 4g , the same problem happened, and then I was unable to connect to the hotspot device from sprint.
[Question] I build my our mba files but cannot be loaded successful.
I build my our modem files following as: https://forum.xda-developers.com/android/software-hacking/dev-building-qualcomm-modem-sources-t3489833 I have a Moto G X1032 that already unlocked. and also replace the NON-HLOS partition by my our mba.b00/mba.mdt. but when starting, it logs: 4>[ 4427.564452,0] ------------[ cut here ]------------ <4>[ 4427.564673,0] WARNING: at ../../../../../../kernel/kernel/irq/manage.c:428 enable_irq+0x3c/0x74() <4>[ 4427.564786,0] Unbalanced enable for IRQ 404 <4>[ 4427.564980,0] Modules linked in: <4>[ 4427.565210,0] [<c010bb78>] (unwind_backtrace+0x0/0xec) from [<c0182278>] (warn_slowpath_common+0x54/0x64) <4>[ 4427.565422,0] [<c0182278>] (warn_slowpath_common+0x54/0x64) from [<c01822b8>] (warn_slowpath_fmt+0x30/0x40) <4>[ 4427.565633,0] [<c01822b8>] (warn_slowpath_fmt+0x30/0x40) from [<c01e8f3c>] (enable_irq+0x3c/0x74) <4>[ 4427.565845,0] [<c01e8f3c>] (enable_irq+0x3c/0x74) from [<c0130a48>] (pil_boot+0x80c/0xbf0) <4>[ 4427.565970,0] [<c0130a48>] (pil_boot+0x80c/0xbf0) from [<c01327a0>] (mss_start+0x2c/0x60) <4>[ 4427.566183,0] [<c01327a0>] (mss_start+0x2c/0x60) from [<c015c7f0>] (subsystem_get+0x9c/0x178) <4>[ 4427.566397,0] [<c015c7f0>] (subsystem_get+0x9c/0x178) from [<c014573c>] (msm_ipc_load_default_node+0x34/0x6c) <4>[ 4427.566611,0] [<c014573c>] (msm_ipc_load_default_node+0x34/0x6c) from [<c014b27c>] (msm_ipc_router_ioctl+0x124/0x2dc) <4>[ 4427.566827,0] [<c014b27c>] (msm_ipc_router_ioctl+0x124/0x2dc) from [<c0779a08>] (sock_ioctl+0x1c8/0x294) <4>[ 4427.567043,0] [<c0779a08>] (sock_ioctl+0x1c8/0x294) from [<c026c4e8>] (do_vfs_ioctl+0x3f4/0x5a8) <4>[ 4427.567166,0] [<c026c4e8>] (do_vfs_ioctl+0x3f4/0x5a8) from [<c026c708>] (sys_ioctl+0x6c/0x7c) <4>[ 4427.567376,0] [<c026c708>] (sys_ioctl+0x6c/0x7c) from [<c0105ae0>] (ret_fast_syscall+0x0/0x30) <4>[ 4427.567576,0] ---[ end trace 3373d290566a10f8 ]--- <3>[ 4427.593954,0] pil-q6v5-mss fc880000.qcom,mss: PBL returned unexpected status -274725888 <3>[ 4427.594121,0] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to bring out of reset <3>[ 4427.594382,0] modem_notifier_cb: sysmon_send_event error -19 <3>[ 4427.594469,0] M-Notify: General: 5 <3>[ 4427.594743,0] msm_ipc_load_default_node: Failed to load modem <6>[ 4427.599158,0] pil-q6v5-mss fc880000.qcom,mss: mba: loading from 0x0c300000 to 0x0c349000 <4>[ 4427.604425,0] ------------[ cut here ]------------ any one know what cause this? <3>[ 4427.593954,0] pil-q6v5-mss fc880000.qcom,mss: PBL returned unexpected status -274725888
after my investigation, i think it caused by my mba is blocked by PBL. i read the <<Qualcomm-Secure-Boot>> (you can google it, because i cannot attach a link for newbie) and use the tools in attachments to compared the mba with the official mba. I got the Certification Store and analysis it. the tool is great that i can verify the mba.b00. but any one know how to generate the certification by reversing way?
[DEV] [KERNEL 3.10] [Sony Unified(Z1 to Z5)& maybe LG Nexus 5 - msm8974/8994] with latest branch merged from CAF (2021-10-14) on the horizon! (I hope)
NB: This is a development thread! A few days ago I embarked on merging the latest release from CAF (https://source.codeaurora.org/quic/la/kernel/msm-3.10/?h=LA.BR.1.3.7.c25 - 2021-01-28) with the SonyXperiadev unified kernel (https://github.com/sonyxperiadev/kernel/tree/aosp/LA.BR.1.3.3_rb2.14) which I've come to know quite well these last few years. I've sorted out most merging assumption errors (I think) and seem to have kept all important changes by Sony. It first started showing signs of life yesterday (I initially used 'fastboot boot boot.img' to test and didn't receive logs from /sys/fs/pstore/ in TWRP Currently it's configured towards Aosp 7.1/8.01, the default branch I wish not to deviate too far from SonyXperiadev with CAF merged. 3.10.108 and booting Aosp 9/10/11 will come later. Right now there's a NULL pointer deference... Somewhere... Causing a fatal crash. For anyone with motivation to help, it lives here: https://github.com/threader/kernel/tree/xperiadev/aosp/LA.BR.1.3.7.c26 - First signes of life - log: Code: <6>[ 6.967271] vidc: disabling clock-voltage handling <6>[ 6.974584] platform fdc00000.qcom,vidc: Driver msm_vidc_v4l2 requests probe deferral <4>[ 6.987934] ------------[ cut here ]------------ <4>[ 6.991554] WARNING: at /xperiadev/xperiadev/threader/LA.BR.1.3.3_rb2.14-LA.BR.1.3.7_c25/kernel/mm/page_alloc.c:2583 __alloc_pages_nodemask+0x2e8/0x904() <4>[ 7.005301] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 3.10.84-g68623d4646022-03022-gb4272132d257b-dirty #42 <4>[ 7.014977] Call trace: <4>[ 7.017404] [<ffffffc000206a4c>] dump_backtrace+0x0/0x130 <4>[ 7.022773] [<ffffffc000206b8c>] show_stack+0x10/0x1c <4>[ 7.027840] [<ffffffc000cf525c>] dump_stack+0x1c/0x28 <4>[ 7.032845] [<ffffffc00021b120>] warn_slowpath_common+0x70/0xa0 <4>[ 7.038757] [<ffffffc00021b380>] warn_slowpath_null+0x14/0x20 <4>[ 7.044473] [<ffffffc0002ca4a8>] __alloc_pages_nodemask+0x2e4/0x904 <4>[ 7.050741] [<ffffffc0002caadc>] __get_free_pages+0x14/0x60 <4>[ 7.056300] [<ffffffc0002fb5a0>] kmalloc_order_trace+0x3c/0xf0 <4>[ 7.062092] [<ffffffc0002fc7c0>] __kmalloc_track_caller+0x40/0x1e8 <4>[ 7.068282] [<ffffffc0005f8e9c>] devm_kmalloc+0x20/0x60 <4>[ 7.073476] [<ffffffc000849d44>] cam_ahb_clk_init+0xe4/0x488 <4>[ 7.079123] [<ffffffc00084ce48>] msm_probe+0x334/0x3ac <4>[ 7.084230] [<ffffffc0005f7198>] platform_drv_probe+0x14/0x20 <4>[ 7.089980] [<ffffffc0005f5cd0>] driver_probe_device+0x158/0x340 <4>[ 7.095961] [<ffffffc0005f5f64>] __driver_attach+0x60/0x90 <4>[ 7.101417] [<ffffffc0005f41a0>] bus_for_each_dev+0x64/0x98 <4>[ 7.106987] [<ffffffc0005f5b0c>] driver_attach+0x1c/0x28 <4>[ 7.112267] [<ffffffc0005f4a1c>] bus_add_driver+0x114/0x240 <4>[ 7.117837] [<ffffffc0005f6760>] driver_register+0x8c/0x10c <4>[ 7.123381] [<ffffffc0005f7b20>] platform_driver_register+0x58/0x64 <4>[ 7.129657] [<ffffffc0014364bc>] msm_init+0x10/0x1c <4>[ 7.134498] [<ffffffc0014008a0>] do_one_initcall+0xb0/0x158 <4>[ 7.140057] [<ffffffc001400ae0>] kernel_init_freeable+0x198/0x23c <4>[ 7.146138] [<ffffffc000ceab94>] kernel_init+0x14/0xcc <4>[ 7.151264] ---[ end trace 7bd08e91a20d3935 ]--- <3>[ 7.155856] msm_probe: failed to register ahb clocks <4>[ 7.161013] msm: probe of fd8c0000.qcom,msm-cam failed with error -12 <4>[ 7.169157] ------------[ cut here ]------------ <4>[ 7.172756] WARNING: at /xperiadev/xperiadev/threader/LA.BR.1.3.3_rb2.14-LA.BR.1.3.7_c25/kernel/drivers/media/platform/msm/camera_v2/msm.c:406 msm_sd_register+0x50/0x1ec() <4>[ 7.188072] CPU: 5 PID: 1 Comm: swapper/0 Tainted: G W 3.10.84-g68623d4646022-03022-gb4272132d257b-dirty #42 <4>[ 7.198744] Call trace: <4>[ 7.201137] [<ffffffc000206a4c>] dump_backtrace+0x0/0x130 <4>[ 7.206554] [<ffffffc000206b8c>] show_stack+0x10/0x1c <4>[ 7.211544] [<ffffffc000cf525c>] dump_stack+0x1c/0x28 <4>[ 7.216595] [<ffffffc00021b120>] warn_slowpath_common+0x70/0xa0 <4>[ 7.222478] [<ffffffc00021b380>] warn_slowpath_null+0x14/0x20 <4>[ 7.228243] [<ffffffc00084da18>] msm_sd_register+0x4c/0x1ec <4>[ 7.233769] [<ffffffc000851c2c>] msm_cci_probe+0x274/0xc68 <4>[ 7.239253] [<ffffffc0005f7198>] platform_drv_probe+0x14/0x20 <4>[ 7.244974] [<ffffffc0005f5cd0>] driver_probe_device+0x158/0x340 <4>[ 7.250951] [<ffffffc0005f5f64>] __driver_attach+0x60/0x90 <4>[ 7.256430] [<ffffffc0005f41a0>] bus_for_each_dev+0x64/0x98 <4>[ 7.261975] [<ffffffc0005f5b0c>] driver_attach+0x1c/0x28 <4>[ 7.267286] [<ffffffc0005f4a1c>] bus_add_driver+0x114/0x240 <4>[ 7.272825] [<ffffffc0005f6760>] driver_register+0x8c/0x10c <4>[ 7.278392] [<ffffffc0005f7b20>] platform_driver_register+0x58/0x64 <4>[ 7.284633] [<ffffffc0014364d8>] msm_cci_init_module+0x10/0x1c <3>[ 7.285451] i2c-msm-v2 f9928000.i2c: msm_bus_scale_register_client(mstr-id:86):0x11 (ok) <4>[ 7.298547] [<ffffffc0014008a0>] do_one_initcall+0xb0/0x158 <6>[ 7.301509] clearpad clearpad: device mid 1, prop 224, family 0xa1, rev 0x09.00, extra 0x03 <6>[ 7.301516] clearpad clearpad: bl 2000-00-00, tester 0, s/n 20556, id 'G0498-C1' <6>[ 7.304011] clearpad clearpad: x_max=1079, y_max=1919, n_fingers=10, n_bytes_per_object=8 <6>[ 7.304541] clearpad clearpad: result: G0498-C1, family 0xa1, fw rev 0x09.00, extra 0x03, (no fw update) <6>[ 7.304672] clearpad clearpad: funcarea 'pointer' [0, 0, 1079, 1919] [0, 0, 1079, 1919] <6>[ 7.304678] clearpad clearpad: Touch area [0, 0, 1079, 1919] <6>[ 7.304902] input: clearpad as /devices/virtual/input/input2 <6>[ 7.305135] evdt_initialize: LOG [=== DOUBLE TAP ===] <6>[ 7.305146] evdt_initialize: KEY [143, DOWN] <6>[ 7.305154] evdt_initialize: KEY [143, UP] <6>[ 7.305164] clearpad clearpad: Touch Wakeup Feature OK <6>[ 7.305948] clearpad clearpad: clearpad_set_power: state=running <6>[ 7.305990] clearpad clearpad: clearpad_vreg_suspend: vdd: set mode (HPM) ok, new mode=2 <6>[ 7.328607] clearpad clearpad: normal mode OK <6>[ 7.337308] clearpad clearpad: Touch irq busy <6>[ 7.349856] clearpad-i2c 6-002c: clearpad_i2c_probe: sucess <6>[ 7.350167] clearpad clearpad: status = 0x81 <6>[ 7.350171] clearpad clearpad: device reset <6>[ 7.368106] clearpad clearpad: x_max=1079, y_max=1919, n_fingers=10, n_bytes_per_object=8 <6>[ 7.368628] clearpad clearpad: result: G0498-C1, family 0xa1, fw rev 0x09.00, extra 0x03, (no fw update) <6>[ 7.368638] clearpad clearpad: clearpad_vreg_suspend: vdd: set mode (HPM) ok, new mode=2 <6>[ 7.391199] clearpad clearpad: normal mode OK <6>[ 7.391206] clearpad clearpad: Touch irq pending <6>[ 7.391415] clearpad clearpad: no work, interrupt=[0x00] <4>[ 7.451850] [<ffffffc001400ae0>] kernel_init_freeable+0x198/0x23c <4>[ 7.457907] [<ffffffc000ceab94>] kernel_init+0x14/0xcc <4>[ 7.463018] ---[ end trace 7bd08e91a20d3936 ]--- <3>[ 7.467992] msm_camera_get_dt_vreg_data:1119 number of entries is 0 or not present in dts <4>[ 7.477770] ------------[ cut here ]------------ <4>[ 7.481359] WARNING: at /xperiadev/xperiadev/threader/LA.BR.1.3.3_rb2.14-LA.BR.1.3.7_c25/kernel/drivers/media/platform/msm/camera_v2/msm.c:406 msm_sd_register+0x50/0x1ec() <4>[ 7.496667] CPU: 4 PID: 1 Comm: swapper/0 Tainted: G W 3.10.84-g68623d4646022-03022-gb4272132d257b-dirty #42 <4>[ 7.507319] Call trace: <4>[ 7.509742] [<ffffffc000206a4c>] dump_backtrace+0x0/0x130 <4>[ 7.515131] [<ffffffc000206b8c>] show_stack+0x10/0x1c <4>[ 7.520156] [<ffffffc000cf525c>] dump_stack+0x1c/0x28 <4>[ 7.525204] [<ffffffc00021b120>] warn_slowpath_common+0x70/0xa0 <4>[ 7.531091] [<ffffffc00021b380>] warn_slowpath_null+0x14/0x20 <4>[ 7.536833] [<ffffffc00084da18>] msm_sd_register+0x4c/0x1ec <4>[ 7.542380] [<ffffffc00085cc90>] csiphy_probe+0x17c/0x758 <4>[ 7.547775] [<ffffffc0005f7198>] platform_drv_probe+0x14/0x20 <4>[ 7.553487] [<ffffffc0005f5cd0>] driver_probe_device+0x158/0x340 <4>[ 7.559487] [<ffffffc0005f5f64>] __driver_attach+0x60/0x90 <4>[ 7.564958] [<ffffffc0005f41a0>] bus_for_each_dev+0x64/0x98 <4>[ 7.570499] [<ffffffc0005f5b0c>] driver_attach+0x1c/0x28 <4>[ 7.575804] [<ffffffc0005f4a1c>] bus_add_driver+0x114/0x240 <4>[ 7.581349] [<ffffffc0005f6760>] driver_register+0x8c/0x10c <4>[ 7.586921] [<ffffffc0005f7b20>] platform_driver_register+0x58/0x64 <4>[ 7.593159] [<ffffffc0014364f4>] msm_csiphy_init_module+0x10/0x1c <4>[ 7.599242] [<ffffffc0014008a0>] do_one_initcall+0xb0/0x158 <4>[ 7.604788] [<ffffffc001400ae0>] kernel_init_freeable+0x198/0x23c <4>[ 7.610880] [<ffffffc000ceab94>] kernel_init+0x14/0xcc <4>[ 7.615998] ---[ end trace 7bd08e91a20d3937 ]--- <1>[ 7.621062] Unable to handle kernel NULL pointer dereference at virtual address 00000080 <1>[ 7.628677] pgd = ffffffc00007d000 <1>[ 7.632044] [00000080] *pgd=000000001020b003, *pmd=000000001020c003, *pte=00e00000f9000407 <0>[ 7.640301] Internal error: Oops: 96000045 [#1] PREEMPT SMP <4>[ 7.645850] CPU: 4 PID: 1 Comm: swapper/0 Tainted: G W 3.10.84-g68623d4646022-03022-gb4272132d257b-dirty #42 <4>[ 7.656524] task: ffffffc0c0170000 ti: ffffffc0c0178000 task.ti: ffffffc0c0178000 <4>[ 7.663992] PC is at csiphy_probe+0x6b4/0x758 <4>[ 7.668329] LR is at csiphy_probe+0x6a4/0x758 <4>[ 7.672671] pc : [<ffffffc00085d1c8>] lr : [<ffffffc00085d1b8>] pstate: 80000005 <4>[ 7.680045] sp : ffffffc0c017bc20 <4>[ 7.683344] x29: ffffffc0c017bc20 x28: ffffffc0019398c8 <4>[ 7.688642] x27: 0000000000000007 x26: ffffffc00508e238 <4>[ 7.693936] x25: ffffffc001e3c926 x24: ffffffc001249f70 <4>[ 7.699231] x23: ffffffc001249000 x22: ffffffc0052c8ee8 <4>[ 7.704526] x21: ffffffc0bf55bc00 x20: ffffffc001c27260 <4>[ 7.709821] x19: ffffffc00508e000 x18: 0000000000000002 <4>[ 7.715116] x17: 0000000000000001 x16: 0000000000000007 <4>[ 7.720410] x15: ffffffc0c10c82e0 x14: 0000000000000000 <4>[ 7.725705] x13: 0000000000000000 x12: 0000000000000000 <4>[ 7.731001] x11: ffffffc0007f59cc x10: 0000000000000000 <4>[ 7.736297] x9 : ffffffc0007f60e0 x8 : ffffffc0007f6324 <4>[ 7.741592] x7 : ffffffc0007f6204 x6 : ffffffc001c272b8 <4>[ 7.746886] x5 : 0000000000000000 x4 : 0000000000000008 <4>[ 7.752182] x3 : 0000000000000010 x2 : ffffffffffffffd0 <4>[ 7.757478] x1 : ffffffc000ea1d20 x0 : 0000000000000000 <4>[ 7.762774] <4>[ 7.762774] PC: 0xffffffc00085d0c8: <4>[ 7.767721] d0c8 9102a021d0004f40 12800254910ac000 1400004e94125ba1 71003c1fb9428660 90004f61540001e9 91317421aa1503e0 97ffbae152800022 b5000100f9011a60 <4>[ 7.781434] d108 d0004f4091036281 910ac0009102a021 94125b9012800254 913dc2f814000038 aa1803e1aa1503e0 f901126097ffb9ef 91036281b5000100 9102a021d0004f40 <4>[ 7.795151] d148 12800254910b2000 1400002294125b83 aa0003e190000002 aa1803e4aa1303e5 aa1503e0910da042 97ffba03d2800023 9103628136f80100 9102a021d0004f40 <4>[ 7.808865] d188 128001f4910c1000 1400001294125b73 52800001f9411260 f9403fa097ffba69 9100829491090014 97ffc12faa1403e0 9116b000d0ffffe0 f9408260f9001a80 <4>[ 7.822580] d1c8 52800020f9004014 52800000b9028a60 b94286601400001e 540000e971003c1f f9411a6190004f62 aa1503e091317442 97ffbb5152800023 913dc2e2f9411661 <4>[ 7.836296] d208 52800023aa1503e0 aa1a03e097ffbb4c f9414a6097e82c13 aa1303e097ea7a70 2a1403e097ea7a6e 9103628114000008 9102a021b0004f60 128001b49102d800 <4>[ 7.850011] d248 17fffff294125b45 a9425bf5a94153f3 a9446bf9a94363f7 a8c87bfda94573fb a9be7bfdd65f03c0 a90153f3910003fd f9411414aa0003f3 b9419001f9414800 <4>[ 7.863728] d288 8b01028152800000 f9414a6097ffa1c4 52800000b9419801 97ffa1bf8b010281 b941a001f9414a60 8b01028152800000 f9414a6097ffa1ba 52800000b941a801 <4>[ 7.877442] <4>[ 7.877442] LR: 0xffffffc00085d0b8: <4>[ 7.882389] d0b8 f901166097ffbaf2 91036281b5000100 9102a021d0004f40 12800254910ac000 1400004e94125ba1 71003c1fb9428660 90004f61540001e9 91317421aa1503e0 <4>[ 7.896105] d0f8 97ffbae152800022 b5000100f9011a60 d0004f4091036281 910ac0009102a021 94125b9012800254 913dc2f814000038 aa1803e1aa1503e0 f901126097ffb9ef <4>[ 7.909821] d138 91036281b5000100 9102a021d0004f40 12800254910b2000 1400002294125b83 aa0003e190000002 aa1803e4aa1303e5 aa1503e0910da042 97ffba03d2800023 <4>[ 7.923537] d178 9103628136f80100 9102a021d0004f40 128001f4910c1000 1400001294125b73 52800001f9411260 f9403fa097ffba69 9100829491090014 97ffc12faa1403e0 <4>[ 7.937252] d1b8 9116b000d0ffffe0 f9408260f9001a80 52800020f9004014 52800000b9028a60 b94286601400001e 540000e971003c1f f9411a6190004f62 aa1503e091317442 <4>[ 7.950967] d1f8 97ffbb5152800023 913dc2e2f9411661 52800023aa1503e0 aa1a03e097ffbb4c f9414a6097e82c13 aa1303e097ea7a70 2a1403e097ea7a6e 9103628114000008 <4>[ 7.964681] d238 9102a021b0004f60 128001b49102d800 17fffff294125b45 a9425bf5a94153f3 a9446bf9a94363f7 a8c87bfda94573fb a9be7bfdd65f03c0 a90153f3910003fd <4>[ 7.978397] d278 f9411414aa0003f3 b9419001f9414800 8b01028152800000 f9414a6097ffa1c4 52800000b9419801 97ffa1bf8b010281 b941a001f9414a60 8b01028152800000 <4>[ 7.992113] <4>[ 7.992113] SP: 0xffffffc0c017bb20: <4>[ 7.997061] bb20 0000000000000008 0000000000000000 ffffffc001c272b8 ffffffc0007f6204 ffffffc0007f6324 ffffffc0007f60e0 0000000000000000 ffffffc0007f59cc <4>[ 8.010775] bb60 0000000000000000 0000000000000000 0000000000000000 ffffffc0c10c82e0 0000000000000007 0000000000000001 0000000000000002 ffffffc00508e000 <4>[ 8.024491] bba0 ffffffc001c27260 ffffffc0bf55bc00 ffffffc0052c8ee8 ffffffc001249000 ffffffc001249f70 ffffffc001e3c926 ffffffc00508e238 0000000000000007 <4>[ 8.038207] bbe0 ffffffc0019398c8 ffffffc0c017bc20 ffffffc00085d1b8 ffffffc0c017bc20 ffffffc00085d1c8 0000000080000005 ffffffc0c017bc20 ffffffc00085d1b8 <4>[ 8.051920] bc20 ffffffc0c017bca0 ffffffc0005f719c ffffffc0bf55bc10 ffffffc00191c000 ffffffc001830c38 0000000000000000 ffffffc0017cd000 ffffffc001c17000 <4>[ 8.065637] bc60 0000000000000069 ffffffc001601088 ffffffc0016b31c8 0000000000000000 ffffffc0c017bcb0 ffffffc00124a05c ffffffc0019395f8 ffffffc001c27000 <4>[ 8.079353] bca0 ffffffc0c017bcb0 ffffffc0005f5cd4 ffffffc0c017bd00 ffffffc0005f5f68 ffffffc0bf55bc10 ffffffc0bf55bc70 ffffffc001830c38 ffffffc0017ce368 <4>[ 8.093066] bce0 ffffffc0052c8d80 ffffffc001400194 ffffffc00198b000 ffffffc001830c38 ffffffc0c017bd30 ffffffc0005f41a4 0000000000000000 ffffffc001830c38 <4>[ 8.106783] <0>[ 8.108259] Process swapper/0 (pid: 1, stack limit = 0xffffffc0c0178058) <4>[ 8.114942] Call trace: <4>[ 8.117374] [<ffffffc00085d1c8>] csiphy_probe+0x6b4/0x758 <4>[ 8.122758] [<ffffffc0005f7198>] platform_drv_probe+0x14/0x20 <4>[ 8.128486] [<ffffffc0005f5cd0>] driver_probe_device+0x158/0x340 <4>[ 8.134475] [<ffffffc0005f5f64>] __driver_attach+0x60/0x90 <4>[ 8.139943] [<ffffffc0005f41a0>] bus_for_each_dev+0x64/0x98 <4>[ 8.145498] [<ffffffc0005f5b0c>] driver_attach+0x1c/0x28 <4>[ 8.150793] [<ffffffc0005f4a1c>] bus_add_driver+0x114/0x240 <4>[ 8.156349] [<ffffffc0005f6760>] driver_register+0x8c/0x10c <4>[ 8.161906] [<ffffffc0005f7b20>] platform_driver_register+0x58/0x64 <4>[ 8.168155] [<ffffffc0014364f4>] msm_csiphy_init_module+0x10/0x1c <4>[ 8.174232] [<ffffffc0014008a0>] do_one_initcall+0xb0/0x158 <4>[ 8.179786] [<ffffffc001400ae0>] kernel_init_freeable+0x198/0x23c <4>[ 8.185864] [<ffffffc000ceab94>] kernel_init+0x14/0xcc <0>[ 8.190990] Code: d0ffffe0 9116b000 f9001a80 f9408260 (f9004014) <4>[ 8.197275] ---[ end trace 7bd08e91a20d3938 ====9.215583 Edit 1: Compiling without camera and media - short log: Code: <6>[ 10.479964] init[1]: undefined instruction: pc=0000007fa4d704c8 <6>[ 10.485266] Code: 2947b0cb d50339bf b94038c9 d5033fdf (d53be04f) <4>[ 10.509764] init (1) used greatest stack depth: 11624 bytes left <0>[ 10.514754] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 <0>[ 10.514754] <2>[ 10.523855] CPU5: stopping <4>[ 10.526542] <4>[ 10.528019] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 3.10.84-g68623d4646022-03025-g95c2ecaa95022-dirty #4 <4>[ 10.537654] task: ffffffc0c0333e80 ti: ffffffc0c034c000 task.ti: ffffffc0c034c000 <4>[ 10.545125] PC is at lpm_cpuidle_enter+0xb4c/0xbc0 <4>[ 10.549895] LR is at lpm_cpuidle_enter+0xac4/0xbc0 <4>[ 10.554667] pc : [<ffffffc0008564c4>] lr : [<ffffffc00085643c>] pstate: 80000145 Fixed compiling and booting for KVM, included ranchu_defconfig for build targeting emulator - 'qemu-system-aarch64 -machine virt -cpu cortex-a57 -machine type=virt -nographic -smp 2 -kernel arch/arm64/boot/Image' - (interestingly does not happen if you remove "-smp 2") Edit 2 : I just built a KVM/ranchu_defconfig version of Sony's LA.BR.1.3.3_rb2.14 (almost) without changes - it outputs the same as the merged CAF-LA.BR.1.3.7_c25 with -smp 2: Code: [ 1.107402] Please append a correct "root=" boot option; here are the available partitions: [ 1.107902] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 1.108471] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.84+ #5 [ 1.108854] Call trace: [ 1.109421] [<ffffffc000087098>] dump_backtrace+0x0/0x140 [ 1.109646] [<ffffffc0000871e8>] show_stack+0x10/0x20 [ 1.109832] [<ffffffc000453b64>] dump_stack+0x1c/0x28 [ 1.110008] [<ffffffc000452c04>] panic+0xdc/0x228 [ 1.110181] [<ffffffc0005cece4>] mount_block_root+0x1c4/0x264 [ 1.110379] [<ffffffc0005cee8c>] mount_root+0x108/0x128 [ 1.110565] [<ffffffc0005cefe0>] prepare_namespace+0x134/0x174 [ 1.110763] [<ffffffc0005ce96c>] kernel_init_freeable+0x1b4/0x1d8 [ 1.110965] [<ffffffc00044cf28>] kernel_init+0x18/0x140 [ 1.111353] CPU1: stopping [ 1.111689] [ 1.111950] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.10.84+ #5 [ 1.112530] task: ffffffc005d48000 ti: ffffffc005d50000 task.ti: ffffffc005d50000 [ 1.113340] PC is at arch_cpu_idle+0x18/0x20 [ 1.113745] LR is at arch_cpu_idle+0x14/0x20 [ 1.114080] pc : [<ffffffc000084d80>] lr : [<ffffffc000084d7c>] pstate: 40000045
Hi, I'm work on port k3.10 for nexus 5, but still won't boot... I will ask you, if I can use this base, and I wanted to know, if to boot, do build rom+kernel
I've not looked at this for a while, I'm a bit perplexed as to where the problem lies, I have some ideas i would like to try soom but I can't quite understand why devices do not initializing, it's not a very obvious fault, I've not tried it for 8974, yet, i've worked with 8994, but this will not work with nexus 4, you would need a 3.10 kernel from google then merge the difference and pray, as far as i can tell only 3.4 kernels are available.
Commit 505510e59c86ff283a2eb743f679debc6698d1ed 'clocksource: arch_timer: make virtual counter access configurable' and a problem with arch/arm64/include/hw_breakpoints.h were the reason behind the issues. The logs tell of some problems, and i don't like a few of the compiler warnings. Code: ---- [ 10.541250] msm8994-asoc-snd fe034000.sound: msm8994_asoc_machine_probe: hdmi audio support present [ 10.542886] msm8994-asoc-snd fe034000.sound: ASoC: CODEC tomtom_codec not registered [ 10.542953] platform fe034000.sound: Driver msm8994-asoc-snd requests probe deferral [ 10.144994] ALSA device list: [ 10.144995] No soundcards found.
Very interesting https://source.codeaurora.org/quic/la/kernel/msm-3.10/log/?h=LA.BR.1.3.7.c26 - I spent some time on the arm32 end of LA.BR.1.3.7.c25 today, as aarch64 worked to an extent on the device and seemed quite happy in qemu I wouldn't not have thought 32bit at least to some degree shouldn't , that degree being qemu and the ranchu_defconfig. But the fact that c26 is out here is quite motivating.
2021-10-13Merge "msm: adsprpc: allocated all remote memory in kernel"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Linux Build Service Account3-67/+3472021-10-12Merge "asoc : msm: Fix zero size pointer issue"
Linux Build Service Account1-0/+62021-10-12asoc : msm: Fix zero size pointer issue
Soumya Managoli1-0/+6
https://github.com/threader/kernel/tree/xperiadev/aosp/LA.BR.1.3.7.c26 is alive on ARM64 but ARM32 does not output anything in qemu, and doesn't get further then the logo on the device(which is an improvement).
So this is the status of ARM32:
Code:
(gdb) stepi
restart () at arch/arm/boot/compressed/head.S:371
371 bl __hyp_set_vectors
=> 0x40010138 <restart+136>: 28 00 8f e2 add r0, pc, #40 ; 0x28
(gdb) stepi
375 sub r9, r6, r5 @ size to copy
=> 0x4001013c <restart+140>: b8 00 90 e8 ldm r0, {r3, r4, r5, r7}
(gdb) stepi
376 add r9, r9, #31 @ rounded up to a multiple
=> 0x40010140 <restart+144>: 03 30 40 e0 sub r3, r0, r3
(gdb) stepi
377 bic r9, r9, #31 @ ... of 32 bytes
=> 0x40010144 <restart+148>: 03 40 84 e0 add r4, r4, r3
(gdb) stepi
378 add r6, r9, r5
=> 0x40010148 <restart+152>: 03 50 85 e0 add r5, r5, r3
(gdb) stepi
379 add r9, r9, r10
=> 0x4001014c <restart+156>: 03 70 87 e0 add r7, r7, r3
(gdb) stepi
381 1: ldmdb r6!, {r0 - r3, r10 - r12, lr}
=> 0x40010150 <restart+160>: 00 80 87 e5 str r8, [r7]
(gdb) stepi
382 cmp r6, r5
=> 0x40010154 <restart+164>: 23 6c a0 e1 lsr r6, r3, #24
(gdb) stepi
383 stmdb r9!, {r0 - r3, r10 - r12, lr}
=> 0x40010158 <restart+168>: 06 0c 33 e1 teq r3, r6, lsl #24
(gdb) stepi
384 bhi 1b
=> 0x4001015c <restart+172>: 70 b9 0e 1a bne 0x403be724
(gdb) stepi
0x403be724 in ?? ()
=> 0x403be724: 00 00 a0 e1 nop ; (mov r0, r0)
(gdb) stepi
0x403be728 in ?? ()
=> 0x403be728: fd ff ff ea b 0x403be724
(gdb)
Code:
/* Relocate the hyp vector base if necessary */
#ifdef CONFIG_ARM_VIRT_EXT
mrs r0, spsr
and r0, r0, #MODE_MASK
cmp r0, #HYP_MODE
bne 1f
bl __hyp_get_vectors
sub r0, r0, r5
add r0, r0, r10
bl __hyp_set_vectors
1:
#endif
sub r9, r6, r5 @ size to copy
add r9, r9, #31 @ rounded up to a multiple
bic r9, r9, #31 @ ... of 32 bytes
add r6, r9, r5
add r9, r9, r10
1: ldmdb r6!, {r0 - r3, r10 - r12, lr}
cmp r6, r5
stmdb r9!, {r0 - r3, r10 - r12, lr}
bhi 1b
/* Preserve offset to relocated code. */
sub r6, r9, r6
Placeholder until recovered from injury
Why aren't you participating to the other mainline trees? postmarketOS / linux-postmarketos-archive · GitLab Archive of the issues in linux-postmarketos.git gitlab.com Qualcomm Snapdragon 820 Mainline / linux · GitLab Staging area for Device Tree support and drivers for various Qualcomm Snapdragon 820/821 mobile devices gitlab.com GitHub - SoMainline/linux: Linux kernel source tree Linux kernel source tree. Contribute to SoMainline/linux development by creating an account on GitHub. github.com
mirhl said: Why aren't you participating to the other mainline trees? Click to expand... Click to collapse I read about somainline but last I checked it had little activity, I might have been abit quick there though, reading and poking a bit about. Very much interesting, thank you for the heads up.
mirhl said: Why aren't you participating to the other mainline trees? postmarketOS / linux-postmarketos-archive · GitLab Archive of the issues in linux-postmarketos.git gitlab.com Qualcomm Snapdragon 820 Mainline / linux · GitLab Staging area for Device Tree support and drivers for various Qualcomm Snapdragon 820/821 mobile devices gitlab.com GitHub - SoMainline/linux: Linux kernel source tree Linux kernel source tree. Contribute to SoMainline/linux development by creating an account on GitHub. github.com Click to expand... Click to collapse Ok, so I'm taking a look at SoMainline atm, and gathering some info, I remember Rob Clark in regards to the Freedreno project did a panel driver for the Sony Z3 (https://patchwork.kernel.org/[email protected]/) - Started reading the documentation and found this gem (https://github.com/freedreno/freedreno/wiki/DSI-Panel-Driver-Porting) mentioning this gem https://github.com/msm8916-mainline/linux-mdss-dsi-panel-driver-generator .
hey! how's it going? i haven't seen any work done in a while...
IGor2Orel said: hey! how's it going? i haven't seen any work done in a while... Click to expand... Click to collapse Hey, thanks for asking, I've had to recover from all sorts of ****, got Covid around february 2022, i was in a good flow, but alas, it took it's toll and my lungs were wrecked after, took at least 6 months before i didn't need a break or two going to the store to buy stuff. I worked on an old huawei kernel trying to pull of a similar thing i did in 2011 or so where i stuffed the drivers in a mainline kernel and such, just doing so with the knowledge i have now, i worked for a month flat out on that until migraines and tinnitus beat the **** out of me, turns out i have a chronic sinus infection which leads to tinnitus, I've gotten some nasal-spray for that and the condition is improving. I'm slowly getting into a flow again, but i wont dare work 24h+ again and let it become too much of an obsession to get **** working as earlier, the body is complaining in all sorts of ways, i had to let everything go for months after the Huawei stuff. I got recovery booting on the MSM .c25 kernel here though, i got stuck on getting arm32 working, now I've got a similar problem with the Huawei kernel where i need to debug an early boot problem and boot in qemu to get any useful output, I'm hunting for my notes at the time and cursing myself for not posting everything in this forum so i could just go back and copy paste. I know, i think that CAF now Code Linaro has a new branch of this MSM kernel I could try to merge and see if arm32 boots, It stumps me that aarch64 worked, this was supposed to be a continuation of Sony's efforts to unify the kernel having the Z1 and z5 in the same place, I also got sidetracked with https://github.com/SoMainline , and a merge with of a Copyleft kernel to a Z3+, z4 and Z5 kernel, i guess too many balls in the air? I'll see in the coming weeks if i can manage to get around to merging newer branches and see if this work properly, or even boot los 14.1/15 which requires more diligence than just a recovery. As far as i could tell or remember audio wasn't initializing properly though, for reasons unknown, I know of a patch which i applied that fixed audio for the said Copyleft kernel, but that didn't seem to work reading the 'dmesg'. Question is though, is it worth the effort or should i focus on So-mainline, or both,I got to the point of having a generated display driver and was trying to figure out the regulator stuff on So-mainline before Covid screwed me hard. . . I'll get around to trying again, it's just taken me forever, and the years are flying these days, I could use a helping hand. Cheers.
threader said: Hey, thanks for asking... Click to expand... Click to collapse by the time you answered i already managed to sell the thing... can't help much at this point, my knowledge is near 0 too
IGor2Orel said: by the time you answered i already managed to sell the thing... can't help much at this point, my knowledge is near 0 too Click to expand... Click to collapse hehe, that makes sense knowing now all the nasty bugs that lurk everywhere in firmware and TZ and such, I can't recommend using old phones for anything serious. I got another z5 to play with but also bought a new phone last year, I'm discovering some rather annoying bugs in this kernel, I don't remember it being this way, or stubborn, i always tested with 'fastboot boot recovery.img' and it worked, now it work's the first time and fail to boot itself if i flash recovery to boot and select reboot, or 'fastboot boot recovery.img' twice without a full power circle. Same goes for getting into TWRP recovery to get the logs, TWRP sometimes fails to boot, i think it's left over NVRAM variables from the previous kernel. ugh. At least i got all the way back around to this in 1.4 years ?