Hey all.
I've had my atrix since before we got our BL unlocked. I've been following the scene and flashing with no problems for a long time.
After flashing "insert rom name here", a CM7 based rom, my wifi has stopped working. It is a known serious issue where the atrix wifi says "error" when you try to even turn it on. It doesn't activate at all. As soon as you tap it, it says error, and unchecks the wifi box. Paired with that is the fact that it reboots once every five minutes. I've tried everything to fix it(other roms, lots of different flashing methods and whatnot), and nothing has worked.
****ty part is, this is actually the first time I flashed without a backup. I wasn't planning on flashing another rom for a very long time.
What I'm asking from you guys is some help. It is a bell atrix, BL unlocked, custom recovery, all that jazz.
I don't know where to go from here. Is there any way one of you guys could send me a nandroid backup of your own? I don't want to resort to flashing .sbf as I will then lose my unlocked BL. I suspect that it is a software issue as it reboots every god damn 5 minutes. If you guys have a better suggestion I'm all ears.
Magnetox said:
Hey all.
I've had my atrix since before we got our BL unlocked. I've been following the scene and flashing with no problems for a long time.
After flashing "insert rom name here", a CM7 based rom, my wifi has stopped working. It is a known serious issue where the atrix wifi says "error" when you try to even turn it on. It doesn't activate at all. As soon as you tap it, it says error, and unchecks the wifi box. Paired with that is the fact that it reboots once every five minutes. I've tried everything to fix it(other roms, lots of different flashing methods and whatnot), and nothing has worked.
****ty part is, this is actually the first time I flashed without a backup. I wasn't planning on flashing another rom for a very long time.
What I'm asking from you guys is some help. It is a bell atrix, BL unlocked, custom recovery, all that jazz.
I don't know where to go from here. Is there any way one of you guys could send me a nandroid backup of your own? I don't want to resort to flashing .sbf as I will then lose my unlocked BL. I suspect that it is a software issue as it reboots every god damn 5 minutes. If you guys have a better suggestion I'm all ears.
Click to expand...
Click to collapse
As you're having lots of reboots have you tried a factory reset/dalvik wipe first? If that fails then a fresh install of the Rom (either fastboot or CM recovery methods) that you're having issues with. Also, another thing I would try is to 'forget' your wifi settings, turn wifi on/off at the mains and then try again.
I know you've tried lots of different flashing methods (and not forgetting the 'whatnots' as well!) but I'm just wondering what you'd think about installing another rom (either go for CM 7.2 or a CM9/10 one) with a full system wipe (format data,system.osh.preinstall and cache before flashing) and see where you go from there.
Magnetox said:
Hey all.
I've had my atrix since before we got our BL unlocked. I've been following the scene and flashing with no problems for a long time.
After flashing "insert rom name here", a CM7 based rom, my wifi has stopped working. It is a known serious issue where the atrix wifi says "error" when you try to even turn it on. It doesn't activate at all. As soon as you tap it, it says error, and unchecks the wifi box. Paired with that is the fact that it reboots once every five minutes. I've tried everything to fix it(other roms, lots of different flashing methods and whatnot), and nothing has worked.
****ty part is, this is actually the first time I flashed without a backup. I wasn't planning on flashing another rom for a very long time.
What I'm asking from you guys is some help. It is a bell atrix, BL unlocked, custom recovery, all that jazz.
I don't know where to go from here. Is there any way one of you guys could send me a nandroid backup of your own? I don't want to resort to flashing .sbf as I will then lose my unlocked BL. I suspect that it is a software issue as it reboots every god damn 5 minutes. If you guys have a better suggestion I'm all ears.
Click to expand...
Click to collapse
Remove the /system/lib/modules/dhd.ko. This is the wifi kernel module, if your reboots are related to wifi, your phone will not reboot anymore. Try to look logcat and dmesg.
Unfortunately, I think your wifi/BT module may have died.
http://forum.xda-developers.com/showthread.php?t=1946667
barry_ said:
As you're having lots of reboots have you tried a factory reset/dalvik wipe first? If that fails then a fresh install of the Rom (either fastboot or CM recovery methods) that you're having issues with. Also, another thing I would try is to 'forget' your wifi settings, turn wifi on/off at the mains and then try again.
I know you've tried lots of different flashing methods (and not forgetting the 'whatnots' as well!) but I'm just wondering what you'd think about installing another rom (either go for CM 7.2 or a CM9/10 one) with a full system wipe (format data,system.osh.preinstall and cache before flashing) and see where you go from there.
Click to expand...
Click to collapse
Yes of course, i've tried all of these things. I will try a full fastboot wipe if the other suggestions don't work, but I have tried all of those steps.
epinter said:
Remove the /system/lib/modules/dhd.ko. This is the wifi kernel module, if your reboots are related to wifi, your phone will not reboot anymore. Try to look logcat and dmesg.
Click to expand...
Click to collapse
Cheers, will try this and will update. Will post logcat later if it still is not working. Do you know what the BT kernel module is too?
upndwn4par said:
Unfortunately, I think your wifi/BT module may have died.
http://forum.xda-developers.com/showthread.php?t=1946667
Click to expand...
Click to collapse
Yep, I looked at this already. I do think this might be the case, but what I'm trying to fix right now is the reboots every 5 minutes. I'm ok without my wifi as long as everything else works properly.
Edit: did not find the tool page before, nvm and thanks!
Ok here is logcat AFTER deleting wifi driver dhd.ko(during logcat I tried turning wifi and BT on). Seems like reboots are fixed (for now).
I will try a full fastboot wipe (preinstall , boot, radio, system, etc.) and then reflash and post a new logcat BEFORE deleting wifi driver. I will then delete the driver to keep my phone from rebooting.
Here is a portion from it:
02-20 14:00:27.995 1599 1849 I WifiService: setWifiEnabled enable=true, persist=true, pid=2307, uid=1000
02-20 14:00:28.005 1599 1688 E WifiService: Failed to load Wi-Fi driver.
02-20 14:00:28.015 1719 1719 E WifiSettingButton: onReceive()-S:2
02-20 14:00:28.045 1719 1719 E WifiSettingButton: onReceive()-S:4
02-20 14:00:28.075 5708 5708 I WifiToggle: OnReceive
02-20 14:00:28.075 5708 5708 I WifiToggle: getServiceState.INTERMEDIATE_STATE
02-20 14:00:28.075 5708 5708 I WifiToggle: UpdateWidget - currentState=INTERMEDIATE_STATE
02-20 14:00:28.075 5708 5708 I WifiToggle: updateButtons
02-20 14:00:28.085 5717 5717 I HomeSyncReceiver: onReceive. WifiState= 2
02-20 14:00:28.115 5708 5708 I WifiToggle: OnReceive
02-20 14:00:28.125 1599 2306 W libgps : recv_command_nmea_gsa() : missing GSV command(s) since last GSA
02-20 14:00:28.125 5708 5708 I WifiToggle: getServiceState.INTERMEDIATE_STATE
02-20 14:00:28.125 5708 5708 I WifiToggle: UpdateWidget - currentState=INTERMEDIATE_STATE
02-20 14:00:28.125 5708 5708 I WifiToggle: updateButtons
02-20 14:00:28.125 5717 5717 I HomeSyncReceiver: onReceive. WifiState= 4
02-20 14:00:28.395 1599 2306 E libgps : recv_command_status() : fix returned error code 15
02-20 14:00:28.395 1599 2306 E libgps : numsats histogram: 0,1,57,95,73,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
02-20 14:00:28.395 1599 2306 E libgps : sats histogram: 0,0,0,0,0,0,0,0,0,0,0,0,0,225,131,0,0,110,0,0,0,226,0,0,0,0,0,0,0,0,0,0
02-20 14:00:29.715 1599 1816 D BluetoothService: Bootcompleted so turning on Bluetooth
02-20 14:00:29.715 1599 1816 D BluetoothService: Bluetooth state 10 -> 11
02-20 14:00:29.735 1719 1719 E BluetoothSettingButton: onReceive()-S:11
02-20 14:00:29.805 2307 2307 V BluetoothEventRedirector: Received android.bluetooth.adapter.action.STATE_CHANGED
02-20 14:00:29.875 1599 1849 I ActivityManager: Start proc com.android.bluetooth for broadcast com.android.bluetooth/.opp.BluetoothOppReceiver: pid=5815 uid=10027 gids={3003, 3002, 3001, 1015}
02-20 14:00:29.945 1440 1440 D dalvikvm: GC_EXPLICIT freed 11K, 50% free 2599K/5123K, external 2357K/2773K, paused 63ms
02-20 14:00:30.015 1440 1440 D dalvikvm: GC_EXPLICIT freed <1K, 50% free 2599K/5123K, external 2357K/2773K, paused 41ms
02-20 14:00:30.055 1440 1440 D dalvikvm: GC_EXPLICIT freed <1K, 50% free 2599K/5123K, external 2357K/2773K, paused 41ms
02-20 14:00:30.185 5815 5815 I ActivityThread: Pub com.android.bluetooth.opp: com.android.bluetooth.opp.BluetoothOppProvider
02-20 14:00:30.205 5708 5708 I BluetoothToggle: OnReceive
02-20 14:00:30.205 5708 5708 I BluetoothToggle: getServiceState
02-20 14:00:30.205 5708 5708 I BluetoothToggle: getServiceState.INTERMEDIATE_STATE
02-20 14:00:30.205 5708 5708 I BluetoothToggle: UpdateWidget - currentState=INTERMEDIATE_STATE
02-20 14:00:30.205 5708 5708 I BluetoothToggle: updateButtons
02-20 14:00:30.215 1599 1941 I ActivityManager: Start proc com.motorola.bluetooth for broadcast com.motorola.bluetooth/.map.BluetoothMapReceiver: pid=5825 uid=10074 gids={3002, 3001, 1015}
02-20 14:00:30.215 1599 1941 I ActivityManager: No longer want com.android.calendar (pid 2803): hidden #21
02-20 14:00:30.225 1599 5814 I bluedroid: Starting bt_start
02-20 14:00:30.445 5825 5825 V BluetoothMapReceiver: MapReceiver onReceive: android.bluetooth.adapter.action.STATE_CHANGED
02-20 14:00:31.355 1424 1458 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-20 14:00:31.355 1426 1493 E NetlinkListener: ignoring non-kernel netlink multicast message
02-20 14:00:31.355 1424 1458 E NetlinkListener: ignoring non-kernel netlink multicast message
02-20 14:00:32.765 1424 1458 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-20 14:00:32.775 1426 1493 E NetlinkListener: ignoring non-kernel netlink multicast message
02-20 14:00:32.775 1424 1458 E NetlinkListener: ignoring non-kernel netlink multicast message
Here is the log from before I deleted wifi and bluetooth driver. Once again, it didn't work. There are a few modules with dhd.ko, namely aev.ko, evfwd.ko, scsi_wait_scan.ko, vpnclient.ko. Would deleting any of those along with dhd.ko help?
Here is logcat, can we confirm my wifi is truly kaput? I think so(neither BT or wifi driver were deleted yet):
02-20 14:27:47.018 1776 2275 D WifiService: setWifiEnabled: true pid=2149, uid=1000
02-20 14:27:47.018 2051 2051 D BluetoothAdapter: 1088533408: getState() : mService = null. Returning STATE_OFF
02-20 14:27:47.018 2149 2149 D BluetoothAdapter: 1087624032: getState() : mService = null. Returning STATE_OFF
02-20 14:27:47.018 1776 4965 E WifiStateMachine: Failed to load driver!
02-20 14:27:47.018 1776 1944 E WifiStateMachine: DriverFailedState
02-20 14:27:47.018 2051 2051 D BluetoothAdapter: 1088533408: getState() : mService = null. Returning STATE_OFF
02-20 14:27:47.018 2149 2149 D BluetoothAdapter: 1087624032: getState() : mService = null. Returning STATE_OFF
02-20 14:27:49.018 1776 1776 D dalvikvm: GC_FOR_ALLOC freed 300K, 25% free 7929K/10572K, paused 60ms, total 60ms
02-20 14:27:49.018 1776 1776 I dalvikvm-heap: Grow heap (frag case) to 8.122MB for 214528-byte allocation
02-20 14:27:49.018 1776 1776 D dalvikvm: GC_FOR_ALLOC freed 0K, 25% free 8139K/10784K, paused 44ms, total 44ms
02-20 14:27:49.018 2149 2149 D BluetoothAdapter: 1087624032: getState() : mService = null. Returning STATE_OFF
02-20 14:27:49.018 2149 2149 W System.err: Removed 2131231229
02-20 14:27:49.018 2149 2149 W System.err: Removed 2131231243
02-20 14:27:49.018 2149 2149 D BluetoothAdapter: 1087624032: getState() : mService = null. Returning STATE_OFF
Magnetox said:
There are a few modules with dhd.ko, namely aev.ko, evfwd.ko, scsi_wait_scan.ko, vpnclient.ko. Would deleting any of those along with dhd.ko help?
Click to expand...
Click to collapse
No. Don't touch them.
ravilov said:
No. Don't touch them.
Click to expand...
Click to collapse
Great, I didn't :angel:
The same problem exactly is a frequent guest of Galaxy Note 2. The only cure is the hard reset.
In Note 2 you have to remove the battery, press power button and hold it for 30+ seconds. Without the battery!
The Q is how to do hard reset to the Atrix.
Sent from my Atrix which I bought drunk. Kill nVidia!
Hello!
I have available device, vendor end kernel source for my device so I tried port Omnirom. I have never done this before or similar ports but I want to learn. I managed to do a working kernel and recovery but stuck with the ROM. It just stuck at the manufacturer logo not even the boot animation comes in. Of course no adb and no logcat. Managed to get the last kernel message from recovery: http://pastebin.com/wBshmx8J
Can someone help or give idea what did I done wrong?
Here is the device tree: https://github.com/Gaboros/android_device_vernee_thor_k506
I have managed to step forward, now I have adb on boot but I got this:
Code:
01-14 17:12:12.893 275 275 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: cannot locate symbol "__xlog_buf_printf" referenced by "/system/lib64/libdpframework.so"...
01-14 17:12:12.893 275 275 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
01-14 17:12:12.893 275 275 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 275 (surfaceflinger)
The problem is "__xlog_buf_printf" in the "libmtk_symbols.so" which is compiled and installed in the ROM and also preloaded on boot. It's seems impossible to get this error after this but still can't get through it. Any idea please?
Gaboros said:
I have managed to step forward, now I have adb on boot but I got this:
Code:
01-14 17:12:12.893 275 275 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: cannot locate symbol "__xlog_buf_printf" referenced by "/system/lib64/libdpframework.so"...
01-14 17:12:12.893 275 275 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
01-14 17:12:12.893 275 275 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 275 (surfaceflinger)
The problem is "__xlog_buf_printf" in the "libmtk_symbols.so" which is compiled and installed in the ROM and also preloaded on boot. It's seems impossible to get this error after this but still can't get through it. Any idea please?
Click to expand...
Click to collapse
Fixed it by patching liblog. If anyone interested in the fix: https://github.com/Gaboros/android_...mmit/44ac2f707c0a12af038f4a4911e8eca47f9a7aff
Hi guys,
First time posting on XDA so hope I have the right section etc...
I am trying to compile and boot the kernel for the Xiaomi Mi Note 2 and have had some success, but the image created causes the phone to boot into recover. Can I check my build procedure with your please?
The Xiaomi GitHub wiki page has an guide for another phone, which I have followed as far as possible.
Anyway, here are the steps I have taken. Have I missed anything out in terms of configuration?
Step 1: Clone the Xiaomi git repo using:
git clone [email protected]:MiCode/Xiaomi_Kernel_OpenSource.git
Step 2: Checkout the Scorpio branch:
git checkout scorpio-m-oss
Step 3: Get the release tag for the QualComm suported Android Enablement Project: For the Mi Note 2 it I have used LA.UM.5.5.r1-04600-8x96.0.
Step 4: Download the QAEP:
repo init -u git://codeaurora.org/platform/manifest.git -b release -m LA.UM.5.5.r1-04600-8x96.0.xml –-repo-url=git://codeaurora.org/tools/repo.git --repo-branch=caf-stable --depth=1
repo sync -j8
Step 7: Merge Xioami Linux Kernel into QAEP: From the QAEP repo dir...
rm -rf kernel/*
mkdir kernel
cp -rf ~/Mi_Kernel/Xiaomi_Kernel_OpenSource/* kernel/
Step 8: Build Kernel
source build/envsetup.sh
lunch msm8996-userdebug
make bootimage BOARD_USES_LIBC_WRAPPER=true
I found that I had to specify BOARD_USES_LIBC_WRAPPER=true as otherwise there would be a link error in the build as the symbol __propClientDispatchWrite would not be defined. Searching for this symbol I found that it is defined in ./bionic/libc/codeaurora/PropClientDispatchWrite.cpp:48. Looking at the Makefile ./bionic/libc/Android.mk one can see that this file is only compiled if ifeq ($(BOARD_USES_LIBC_WRAPPER),true), hence the need for the extra define in the command line for make.
Step 9: Put kernel image into original
Download the original image and unpack:
adb pull /dev/block/sde36 boot_minote2_original.img
./mkboot boot_minote2_original.img boot_minote2_original
Do that same with mkboot for the image I built and unpack that. Then copy the file kernel from the newly build version into boot_minote2_original and repackage:
./mkboot boot_minote2_original boot_minote2_new.img
Step 9: Attempt to boot new image
adb reboot bootloader
fastboot boot boot_minote2_new.img
And, almost there. The new image boots to a state where I can at least ADB shell into the device. The logcat shows the following significant errors when compared to the logcat of the original xiaomi image:
W SystemServer: ***********************************************
E SystemServer: BOOT FAILURE making display ready
E SystemServer: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.server.wm.WindowManagerService.displayReady()' on a null object reference
E SystemServer: at com.android.server.SystemServer.startOtherServices(SystemServer.java:594)
E SystemServer: at com.android.server.SystemServer.run(SystemServer.java:281)
E SystemServer: at com.android.server.SystemServer.main(SystemServer.java:179)
E SystemServer: at java.lang.reflect.Method.invoke(Native Method)
E SystemServer: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:738)
E SystemServer: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)
E System : ******************************************
E System : ************ Failure starting system services
E System : java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.server.wm.WindowManagerService.showBootMessage(java.lang.CharSequence, boolean)' on a null object reference
E System : at com.android.server.am.ActivityManagerService.showBootMessage(ActivityManagerService.java:6474)
E System : at com.android.server.SystemServer.startOtherServices(SystemServer.java:627)
E System : at com.android.server.SystemServer.run(SystemServer.java:281)
E System : at com.android.server.SystemServer.main(SystemServer.java:179)
E System : at java.lang.reflect.Method.invoke(Native Method)
E System : at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:738)
E System : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)
D AndroidRuntime: Shutting down VM
E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.server.wm.WindowManagerService.showBootMessage(java.lang.CharSequence, boolean)' on a null object reference
E AndroidRuntime: at com.android.server.am.ActivityManagerService.showBootMessage(ActivityManagerService.java:6474)
E AndroidRuntime: at com.android.server.SystemServer.startOtherServices(SystemServer.java:627)
E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:281)
E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:179)
E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:738)
E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)
So, onwards with my investigations but if any one has tips and clues to share, please lemme know
Trying to ask help from StoneTrapper !! He is the only one developer in this forum until now ...
Hey did you ever figure this out? Struggling with my Blu Life One X2 kernel. Compiling it without the QAEP tree boots, but the display goes all glitchy and just shows black. I can adb and everything else works.
Trying your method of QAEP now. Please let me know if you found anything new!
Hey, sorry I hadn't been keeping an eye on this thread.
I don't really use MIUI so haven't tried to compile the kernel for it. The current kernels that are around for these devices are based on generic similar devices with source code taken and adjusted from MiCode where needed.
Since this kernel base is also marshmallow for the more recent MIUI releases it'll need updating for that too.
For building a MIUI kernel your best bet is to take a look at other devices in the same family that currently have third party MIUI kernels. A good example is the DragonXia Kernel which is MIUI compatible. You'll need to add the missing features required for scorpio and add msm8996pro support but between MiCode and various sources it's do-able.
If you're successful and happy with the result then the author may be happy for you to release with permission.