how to fix WIFI for MIUI V4 with 3.0kernel - myTouch 4G General

I have ported official MIUI V4 for Incredible S to glacier, but WIFI doesn't work, how to fix it ? thanks
FIX,thX

logcat?

You didn't couple a Sense Kernel with an AOSP ROM did you?

log
I/rmt_storage( 4248): rmt_storage user app start
I/rmt_storage( 4248): rmt_storage open success
I/rmt_storage( 4248): rmt_storage shared memory ioctl success
I/rmt_storage( 4248): rmt_storage mmap addr = 400b5000
E/rmt_storage( 4248): rmt_storage wait event ioctl failed
D/WifiService( 224): setWifiEnabledPersist enable=true, persist=true, getCallingPid()=1516
I/WifiHW ( 224): wifi_load_driver load module
I/WifiHW ( 224): is_wifi_driver_loaded
I/WifiHW ( 224): wifi_load_driver end error 2
E/WifiStateMachine( 224): Failed to load driver!
E/WifiStateMachine( 224): DriverFailedState
I/rmt_storage( 4253): rmt_storage user app start
I/rmt_storage( 4253): rmt_storage open success
I/rmt_storage( 4253): rmt_storage shared memory ioctl success
I/rmt_storage( 4253): rmt_storage mmap addr = 40174000
E/rmt_storage( 4253): rmt_storage wait event ioctl failed

A. You shouldn't use a Sense kernel with MIUI.
B. Try porting from a device closer to ours, like Desire S, Desire HD or G2.

MIUI V4 has the 2.8.3 build for the MyTouch, everything works great except for WiFi calling.

trikar21b said:
MIUI V4 has the 2.8.3 build for the MyTouch, everything works great except for WiFi calling.
Click to expand...
Click to collapse
ummm..wifi calling has been working for awhile on miui v4.......

estallings15 said:
A. You shouldn't use a Sense kernel with MIUI.
B. Try porting from a device closer to ours, like Desire S, Desire HD or G2.
Click to expand...
Click to collapse
Totally agree

zeng3545 said:
I have ported official MIUI V4 for Incredible S to glacier, but WIFI doesn't work, how to fix it ? thanks
Click to expand...
Click to collapse
hi.. ive had this problem before on a few different roms.. one thing i usually do is go into settings and disable all of my network and broadcasting options,, then boot the phone into recovery.. after i reboot,, everything is usually ok.. same for my mobile network..

MIUIv4 WIFI ERROR FIXED WITH S-ON
Im too stucked for 2 weeks to get WIFI on MIUIv4... (Worked for my Incredible S, try on your OWN risk)
Incredible S
HBOOT 2.02 S-ON
Bootloader UNLOCKED (htcdev.com)
Cause of error :- MIUI v4 wont works fully on HTC Stock Kernel. MIUIv4.xx.xx.zip contain a BOOT.img that contain the suppported kernel for MIUIv4. When you have S-ON , boot.img can't be updated via Recovery (zip). All errors can be fixed by updating the kernel (boot.img) provided in ROM zip
How to Update Kernel with S-ON : S-OFF-ing is a difficult tasks. So you can update kernel without S-OFF. It is done via 'fastboot'
1.Extract the boot.img from the MIUI-v4-xx-xx.zip. Copy boot.img to C:\Android\
2.Reboot your phone in Bootloader (Power-off -> Vol-Down + Pwr)
3.Goto Fastboot
4.Install HTC Sync (for drivers)
5.Connect USB
6.Open cmd
7.Navigate to 'fastboot.exe' folder
8 Type fastboot flash boot c:\android\boot.img
9.Format system,data,dalvik
10.Reflash MIUI from recovery
Good luck!!
Hit thanks if works, let help others

what is your overall experience on the miui version of android

Related

who wants a sony arc rom ???

Im starting to port the sony ericsson arc rom to our desire s and i just wanted to know who would be intrested in my rom ????? let me know what u think of the sony ericsson arc and what new things you would like to see in this port. like timescape and other things. its going to be good porting and i hope your all intrested and i aint doing this for nothing lol
paul.robo said:
Im starting to port the sony ericsson arc rom to our desire s and i just wanted to know who would be intrested in my rom ????? let me know what u think of the sony ericsson arc and what new things you would like to see in this port. like timescape and other things. its going to be good porting and i hope your all intrested and i aint doing this for nothing lol
Click to expand...
Click to collapse
Yup. More choice is always a good thing!!
I vote for a port. Do your thing!
LOG CAT
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Users\paul\Desktop\DOWNGRADE.SAGA.AND.GUIDE
C:\Users\paul\Desktop\DOWNGRADE.SAGA.AND.GUIDE>adb logcat
* daemon not running. starting it now *
* daemon started successfully *
--------- beginning of /dev/log/main
I/DEBUG ( 1175): debuggerd: Nov 29 2011 12:52:30
--------- beginning of /dev/log/system
I/Vold ( 1173): Vold 2.1 (the revenge) firing up
D/AK8975 ( 1182): AK8975 daemon 1.0.8 Start
D/AK8975 ( 1182): (Library version : 1.2.1.1125)
I/rmt_storage( 1183): rmt_storage user app start
I/rmt_storage( 1183): rmt_storage open success
I/rmt_storage( 1183): rmt_storage shared memory ioctl success
I/rmt_storage( 1183): rmt_storage mmap addr = 40009000
D/Vold ( 1173): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1173): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 1173): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted
)
THIS SHOWS ERRORS SO NOW IM GOING TO CHANGE MY APPROACH AND GET A DIFF SONY ROM AND FROM THE X10 NOW THAT WAS FROM ARC S WHICH IS GOING TO BE MUCH MUCH HARDER SO ILL STICK WITH THE X10 FOR NOW.

[Q] EBR missing in T699

Some of you may be familiar with my trials with my T699. To make a long story short, (see that story here http://forum.xda-developers.com/showthread.php?t=2528444) (thanks gee one!)
I was attempting to put CM on my Relay and I ended up hard bricking it.
I can now boot but I need a SD card installed to do it.
Recently I was playing around with adb and was running logcat which dumped a whole mess of wonderful information.
The line I thought was important was the following -
I/rmt_storage( 125): No EBR found
It is my guess that I messed up (corrupted) the EBR and that is why I am dependent on the external SD card.
My question is, does anyone know how to restore the EBR to working condition? I have tried to use odin to put the stock
image on but I think it is just over-writing the image on the SD card. If it can be done using adb that would be very great too since
it appears to be working well.
Oh, and the other thing I noticed, if I do not put the SD card, with image, into the slot I just boot into QHSUSB-DLOAD mode.
Which means much but is not useful at this time.
Thanks all,
Lou
I have added the first 25 lines of the logcat -
--------- beginning of /dev/log/main
I/rmt_storage( 125): Target is APQ8064: 1074445686
I/rmt_storage( 125): No EBR found
I/rmt_storage( 125): Error (-1) parsing MBR partitions
I/rmt_storage( 125): Registering modemst1: 0x4a /boot/modem_fs1
I/rmt_storage( 125): Registering modemst2: 0x4b /boot/modem_fs2
I/rmt_storage( 125): Registering fsg: 0x58 /boot/modem_fsg
I/rmt_storage( 125): Registering ssd: 0x5d ssd
I/rmt_storage( 125): 4 GPT partitions found
D/ICD ( 183): icd .02 runs
E/DataRouter( 186): Main entered
E/DataRouter( 186): switchUser
E/DataRouter( 186): monitor_usb_thread
E/DataRouter( 186): server_init
E/DataRouter( 186): Opening of the usb select file failed fd is -1 & errno is 2
E/DataRouter( 186): Opening of the usb select file failed fd is -1 & errno is 2
E/DataRouter( 186): Initialise USB and start the thread
E/DataRouter( 186): dr_usb_init
E/DataRouter( 186): USB Interface is open with 0x9
E/DataRouter( 186): USB interface is now configured for usb_fd = 0x9
E/DataRouter( 186): THREAD LAUNCH
E/DataRouter( 186): monitor_data_of_usb
E/DataRouter( 186): USB monitor thread launched, usb_fd= 0x9
E/DataRouter( 186): init_cur_sock
E/DataRouter( 186): Before the usb select
I/DEBUG ( 182): debuggerd: Mar 16 2013 22:15:51
*** UPDATE ***
I found another interesting line in line in the logcat ...
W/PackageManager( 674): Library not found: /system/framework/com.qualcomm.location.quipslib.jar
More on de-bricking
I have been continuing my hunt on how to permanently de-brick my T699. The following thread does not leave me with
much hope . I know it is for Evita on the HTC One but I see similar behaviour when I hook my T699 to linux.
http://forum.xda-developers.com/showthread.php?t=1966850&page=40
If anyone can comment on this it is greatly appreciated.

Android L Discussion (CM12/AOSP/all other builds...)

Hi,
First of all looks like there isn't anyone started building Android Lollipop for i9500
So lets make this thread for discussing about all Lollipop ROMS
I wanted to say, i built for i9500 already
There are bugs
If i can see anything on screen, probably it will be the lockscreen.
AOSP Lollipop Recovery (recovery.img) - OK!
AOSP Lollipop Kernel+ramdisk (boot.img) - OK!
AOSP Lollipop System - [PVRSRV PROBLEM : PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address)]
Probably something related about including vendor files on build(because of AOSP)
doesn't load graphics/display driver
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: Couldn't connect to services
E/dex2oat ( 2811): Failed to open writable oat file /data/dalvik-cache/arm/[email protected]@boot.oat for /data/dalvik-cache/arm/[email protected]@boot.oat: File size of 0 bytes not large enough to contain ELF header of 52 bytes: '/data/dalvik-cache/arm/[email protected]@boot.oat'
E/dex2oat ( 2811): Failed to create image file /data/dalvik-cache/arm/[email protected]@boot.art
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 3929): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/hwcomposer( 3929): failed to open gralloc
E/SurfaceFlinger( 3929): composer device failed to initialize (Invalid argument)
E/SurfaceFlinger( 3929): ERROR: failed to open framebuffer (Not a typewriter), aborting
F/libc ( 3929): Fatal signal 6 (SIGABRT), code -6 in tid 3929 (surfaceflinger)
@intervigilium @Alberto96 @alvin14
doga.ozkaraca said:
Hi,
First of all looks like there isn't anyone started building Android Lollipop for i9500
So lets make this thread for discussing about all Lollipop ROMS
I wanted to say, i built for i9500 already
There are bugs
If i can see anything on screen, probably it will be the lockscreen.
AOSP Lollipop Recovery (recovery.img) - OK!
AOSP Lollipop Kernel+ramdisk (boot.img) - OK!
AOSP Lollipop System - [PVRSRV PROBLEM : PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address)]
Probably something related about including vendor files on build(because of AOSP)
doesn't load graphics/display driver
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: Couldn't connect to services
E/dex2oat ( 2811): Failed to open writable oat file /data/dalvik-cache/arm/[email protected]@boot.oat for /data/dalvik-cache/arm/[email protected]@boot.oat: File size of 0 bytes not large enough to contain ELF header of 52 bytes: '/data/dalvik-cache/arm/[email protected]@boot.oat'
E/dex2oat ( 2811): Failed to create image file /data/dalvik-cache/arm/[email protected]@boot.art
E/IMGSRV ( 3929): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086848 (Bad address).
E/IMGSRV ( 3929): :0: PVRSRVEnumerateDevices: BridgeCall failed
E/IMGSRV ( 3929): :0: PVRSRVConnect: Unable to enumerate devices.
E/IMGSRV ( 3929): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 3929): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/IMGSRV ( 3929): :0: hal_open: Graphics HAL not initialized
E/hwcomposer( 3929): failed to open gralloc
E/SurfaceFlinger( 3929): composer device failed to initialize (Invalid argument)
E/SurfaceFlinger( 3929): ERROR: failed to open framebuffer (Not a typewriter), aborting
F/libc ( 3929): Fatal signal 6 (SIGABRT), code -6 in tid 3929 (surfaceflinger)
Click to expand...
Click to collapse
Maybe Alberto96 can help u?
I don't have time to work on a whole new android version. School is killing me.
Alberto96 said:
I don't have time to work on a whole new android version. School is killing me.
Click to expand...
Click to collapse
same.. :highfive:
i was sick and stayed home today, and that was my only free-time for building Android L
there should be a way to solve that :crying:
Thanks for all the effort that somehow have contributed or are contributing.
Does the issue at hand will be resolved only get if Samsung release the source code with the Lollipop? Or some work of developers already can fix (no need to be based on source code from Samsung)?
Too bad it's not 9505
Ill keep tabs on this tho. I'm mainly looking for a kernel+ramdisk for 5.0 on 9505 or similar S4s.
Maybe we can get some help from here or here ?
and it seems @BlaqueDroid is also trying to boot lollipop on i9500
@doga.ozkaraca long time man! You had disappeared from our forum for a very long time! Good to see you man!
As @Arch9 said, @BlaqueDroid needed help building it too! Maybe y'all can figure it out together!
Happy compiling ?
Sent from my GT-I9500 using Tapatalk
Hey man which kernel are u using to compile coz the CM one is throwing errors for
---------- Post added at 06:33 AM ---------- Previous post was at 06:31 AM ----------
rgshah3 said:
@doga.ozkaraca long time man! You had disappeared from our forum for a very long time! Good to see you man!
As @Arch9 said, @BlaqueDroid needed help building it too! Maybe y'all can figure it out together!
Happy compiling ?
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Hey man which Kernel are u using coz i tried the CM 11 one and the damn thing keeps throwing errors. Plz link me with the github Url
https://twitter.com/Antares__One this guy is doing some great stuff for our phone! Follow him for more updates #ThumbsUp
tkruijer said:
https://twitter.com/Antares__One this guy is doing some great stuff for our phone! Follow him for more updates #ThumbsUp
Click to expand...
Click to collapse
unfortunately it is for the I9505, I think the problem we have is different to boot
Even @gekkehenkie11 can help! He has done a lot of stuff recently to improve CM on our device! Maybe he can help boot CM12 on our device
Sent from my GT-I9500 using Tapatalk
@doga.ozkaraca
Welcome back buddy
Check this post
http://forum.xda-developers.com/showthread.php?p=56752819
Sent from my GT-I9500 using Tapatalk
I'm just found someone already build 5.0 for odroidxu in here, does we can do something with that? i'm trying to port it to i9500 but the result is nothing (stuck at boot)
Re-port a port is not a gold way ...
feraay said:
Re-port a port is not a gold way ...
Click to expand...
Click to collapse
Wut? re-port a port? what do you mean?
When can we expect fully working Android 5.0 based ROM?
ncenter said:
When can we expect fully working Android 5.0 based ROM?
Click to expand...
Click to collapse
31st Feb 2015
Sent from my GT-I9500 using Tapatalk
Yep, but unoficcial clean Lollipop ROM I mean.
ncenter said:
When can we expect fully working Android 5.0 based ROM?
Click to expand...
Click to collapse
How about you build it. And let us know? I heard its easy.

[5.1.x] [SM-T325] CyanogenMod 12.1 UNOFFICIAL Nightlies for the Tab Pro 8.4 LTE

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Download Links
CyanogenMod: download.crpalmer.org
Google apps addon:
Download: http://d-h.st/users/dhacker29/?fld_id=27426 (use latest lpmr1 gapps)
XDA:DevDB Information
CyanogenMod 12.1 for MondrianLTE (Unofficial), ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
ROM OS Version: 5.1.x Lollipop
Version Information
Status: No Longer Updated
Created 2015-04-18
Last Updated 2016-02-13
Reserved
Works fine
ROM works fine, made a dirty flash from CM12.
No problems at all.
http://review.cyanogenmod.org/#/c/95004/2
hopefully merged soon (already in cm12 since late march..just noticed recently in cm12 builds in mms.apk...should have known by looking at the history for the cm12 version)
EDIt
One thing though
Email exchange (hotmail etc) app has a repeated error popup during sync..this is from 4/17 build and also today's 4/18...was not the case till 4/16..noticed the apk file size has changed (not sure what..but it starts giving error popups during sync...pretty irritating as have to somehow get it to stop the sync to stop the popup...using the cm12.1 email apk 5.82mb from 4/16 or earlier fixes the issue)
cm12 not having such issues,.at least from 4.16 to 4/18 no email.apk file size changes..no sync issues
Edit attached mixer file to address earpiece echo for other caller not speakerphone echo for other caller.. change zip in extension to xml.. not a zip file..put in system etc folder permissions 644
Does miracast work with this build? I know CM started enabling the feature, but it didn't work when I last tried it with my SM-T315. Thank you for your answer.
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
TWRP 2.8.5.0 here. Any later version will work as well.
Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP
vrl13 said:
Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP
Click to expand...
Click to collapse
Thanks!
There's a donate link in my profile but I prefer not to clutter up useful information with extra donate links...
My PayPal is [email protected].
Beer uploaded: 7UG08116JF1461945
Thanks again!
Sent from my SM-T325 using Tapatalk
Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app
mackenzie121 said:
Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Hello,
I'm having no issue with both 2.4 and 5ghz wifi in my home.
Sounds like a router problem though.. can your other devices pick your wifi without a hitch?
Maybe it would help using a fixed IP, in case you are using DHCP now.
Regards.
Sent from my SM-T325 using Tapatalk
RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
I used TWRP 2.8.6.0. I already flashed several nightlies on this tablet, no issues.
---------- Post added at 10:41 PM ---------- Previous post was at 10:26 PM ----------
Is the changelog the same of the nightlies for "MONDRIANWIFI"? Thanks
Is it support cifs ?
Device encryption doesn't work. Build 20150507
Log:
Code:
D/Cryptfs ( 247): unmounting /data succeeded
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 247): Loading keymaster app failed
E/Cryptfs ( 247): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 247): Failed to init keymaster
F/libc ( 247): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 316 (vold)
F/libc ( 247): Unable to open connection to debuggerd: Connection refused
W/vold ( 316): type=1400 audit(0.0:190): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:190): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:190): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:190): item=0 name="/vendor/firmware/keymaster/keymaster.mdt"
W/auditd ( 314): type=1320 audit(0.0:190):
W/vold ( 316): type=1400 audit(0.0:191): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:191): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:191): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:191): item=0 name="/firmware/image/keymaste.mdt"
W/auditd ( 314): type=1320 audit(0.0:191):
W/vold ( 316): type=1701 audit(0.0:192): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=u:r:vold:s0 reason="memory violation" sig=11
I/Vold ( 8391): Vold 2.1 (the revenge) firing up
D/Vold ( 8391): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 8391): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 8391): Check if PFE is activated on Boot
E/Cryptfs ( 8391): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 8391): Error getting crypt footer and key
I see, that file /vendor/firmware/keymaster/keymaster.mdt exists:
# ls -la /system/vendor/firmware/keymaster/keymaster.mdt
lrw-r--r-- root root 2015-05-07 07:04 keymaster.mdt -> /firmware/image/keymaste.mdt
# ls -la /firmware/image/keymaste.mdt <
-r--r----- system drmrpc 12892 2014-11-13 05:32 keymaste.mdt
Any ideas how to fix it? Thanks.
crpalmer said:
CyanogenMod
Click to expand...
Click to collapse
f2fs support?
I am waiting for 10 minutes, hanging on the logo
Alexey71 said:
f2fs support?
I am waiting for 10 minutes, hanging on the logo
Click to expand...
Click to collapse
Try again with today's build and let me know.
crpalmer said:
Try again with today's build and let me know.
Click to expand...
Click to collapse
For me :
cm-12.1-20150523-UNOFFICIAL-mondrianlte.zip work fine but
cm-12.1-20150527-UNOFFICIAL-mondrianlte.zip and cm-12.1-20150528-UNOFFICIAL-mondrianlte.zip don't work : hanging on the logo
27-28 build not work (ext4-f2fs)
26 build work ext4
Builds 0527 and 0528 does not boot; instead, causes shutdown of the tab.

[Question]WiFi Problem in Lollipop ROMs

I have recently upgrade my hboot to hboot 2.15 and tried to flash new rom, but I'm facing a problem with wifi. I can't turn on the wifi, when I click on it just stick on "turning wifi on" and nothing happens.
I have tried these rom xenonHD,candy, LP but same issue, I have also installed a custom kernel "Mark kernel" but no luck.
while installing the rom I have followed every step required and mentioned by the developers "wipe cash, system...."
the wifi errors taken from logcat file are here:
Code:
[ 05-06 23:10:21.717 669: 1110 E/WifiHW ]
Supplicant not running, cannot connect
[ 05-06 23:10:21.818 669: 1110 E/WifiHW ]
Supplicant not running, cannot connect
[ 05-06 23:10:21.818 669: 1110 E/WifiMonitor ]
startMonitoring(wlan0) failed!
[ 05-06 23:10:21.823 669: 1110 E/WifiStateMachine ]
Failed to setup control channel, restart supplicant
[ 05-06 23:10:21.823 669: 1110 E/WifiMonitor ]
killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
[ 05-06 23:10:31.885 185: 601 E/WifiHW ]
Failed to write wlan fw path param (No such device)
[ 05-06 23:10:31.885 185: 601 E/SoftapController ]
Softap fwReload failed
[ 05-06 23:10:31.887 669: 1110 E/NetdConnector ]
NDC Command {148 softap fwreload wlan0 STA} took too long (5056ms)
[ 05-06 23:10:31.888 669: 1110 E/WifiStateMachine ]
Failed to reload STA firmware java.lang.IllegalStateException: command '148 softap fwreload wlan0 STA' failed with '400 148 SoftAP command has failed'
[ 05-06 23:10:31.893 185: 601 W/CommandListener ]
Failed to retrieve HW addr for wlan0 (No such device)
[ 05-06 23:10:31.898 185: 601 D/CommandListener ]
Setting iface cfg
[ 05-06 23:10:31.902 669: 1110 E/WifiStateMachine ]
Unable to change interface settings: java.lang.IllegalStateException: command '150 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 150 Failed to set address (No such device)'
[ 05-06 23:10:31.902 669: 1110 E/WifiMonitor ]
killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
[ 05-06 23:10:31.912 3822: 3822 D/BluetoothAdapter ]
760752152: getState() : mService = null. Returning STATE_OFF
[ 05-06 23:10:31.914 669: 1110 D/WifiMonitor ]
startMonitoring(wlan0) with mConnected = false
[ 05-06 23:10:31.914 669: 1110 E/WifiHW ]
Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
[ 05-06 23:10:31.945 6595: 6595 I/wpa_supplicant ]
Successfully initialized wpa_supplicant
[ 05-06 23:10:31.947 6595: 6595 E/wpa_supplicant ]
Could not read interface wlan0 flags: No such device
[ 05-06 23:10:31.947 6595: 6595 E/wpa_supplicant ]
wlan0: Failed to initialize driver interface
[ 05-06 23:10:32.015 669: 1110 E/WifiHW ]
VLE PVT SHIP S-off RL
HBOOT-1.14.0002
CID-ORANG202
RADIO-1.08ES.50.02.16
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
Please let me know what steps I should take to fix this problem.
no one has any suggestion?
First I am wondering how you ever thought you've upgraded your firmware to 2.15 as your boot info says hboot 1.14.0002...
Sent from nowhere over the air...
Rapier said:
First I am wondering how you ever thought you've upgraded your firmware to 2.15 as your boot info says hboot 1.14.0002...
Sent from nowhere over the air...
Click to expand...
Click to collapse
Sorry for wrong information. Im using hboot 2.5 (modded)
I guess you wanted to say 2.15 cause there's no 2.5 hboot.
Ok...have you flashed only the hboot or the entire firmware? Could be that you didn't flashed wcnss which is responsible for wifi. There are some threads where it is only the hboot posted and that's why I'm asking.
There is a thread that contains the full firmware with the partitions for wifi and audio included. You should have flashed this one then, if you want to get rid of the red warning, flash just the modded hboot you talked about (I guess that's why you flashed that one) .
Sent from nowhere over the air...
Rapier said:
I guess you wanted to say 2.15 cause there's no 2.5 hboot.
Ok...have you flashed only the hboot or the entire firmware? Could be that you didn't flashed wcnss which is responsible for wifi. There are some threads where it is only the hboot posted and that's why I'm asking.
There is a thread that contains the full firmware with the partitions for wifi and audio included. You should have flashed this one then, if you want to get rid of the red warning, flash just the modded hboot you talked about (I guess that's why you flashed that one) .
Sent from nowhere over the air...
Click to expand...
Click to collapse
yea I wanted to say 2.15 silly:
your guess is quiet right I have flashed only hboot.
now Im trying to flash the whole firmware as you said . should I download one of the RUU available here or I need to download different specific firmware?!
No, it is not a RUU. I'm on mobile so I can't search so easy but there's a thread that contained the whole firmware not only hboot. The firmware has a bigger size than the hboot only
Sent from nowhere over the air...
Rapier said:
No, it is not a RUU. I'm on mobile so I can't search so easy but there's a thread that contained the whole firmware not only hboot. The firmware has a bigger size than the hboot only
Sent from nowhere over the air...
Click to expand...
Click to collapse
I have found these threads:
http://forum.xda-developers.com/showthread.php?t=2570112
http://forum.xda-developers.com/showthread.php?t=2322755
Am I on the right path?
mraabs said:
I have found these threads:
http://forum.xda-developers.com/showthread.php?t=2570112
http://forum.xda-developers.com/showthread.php?t=2322755
Am I on the right path?
Click to expand...
Click to collapse
Yesss... That's the one I was talking about. Use that firmware. There is another thread about changing just the splash screen and that has only the moded hboot with red warning gone. I guess you have flashed that one in the past
Sent from nowhere over the air...
Rapier said:
Yesss... That's the one I was talking about. Use that firmware. There is another thread about changing just the splash screen and that has only the moded hboot with red warning gone. I guess you have flashed that one in the past
Sent from nowhere over the air...
Click to expand...
Click to collapse
Much appriciated Rapier, I have flashed the official firmware and now the wifi is working :good:

Categories

Resources