Related
i search whole vivid forum about this problem
some guys (like me ) have problem with wifi on custom Roms
in some kernel wifi stuck on "wifi is turning on ..." and some kernel wifi could be on but it's crazy (like couldn't off) and couldn't find any wifi signal.
phone go to s-off but problem not solved
phone like Velocity 4G x710s
any body have a suggestion or help
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
mohamed_moscow said:
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
Click to expand...
Click to collapse
i found some "bcmdhd.ko" in some kernel
which is best for me
Cant wait for release!!
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
ideaLduK said:
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
yes, upload that for us
Every kernel has it's own specific modules.
Thats why if you're S-ON you have to flash a CWM Zip and fastboot the img.
If you're S-OFF both are done in CWM.
This thread should be moved.
ok i find working file
tested with kozmik RC1 kernel and work well
Nottach said:
Cant wait for release!!
Click to expand...
Click to collapse
Hehe awesome.
I experienced the issue you described as a separate error from the common issue solved by a manual adb push for the wireless module.
Even though my phone is S-Off, I'd receive the error consistently when installing certain ROMs (but not all ROMs).
After multiple wipes (including formatting all SD drives, data and system partitions), I finally fixed the issue on my phone by fastboot flashing the kernel for the specific ROM I'm installing after doing a re-format/wipe and before starting the ROM installer through CWM.
It's a strange error, especially because everything seemed to be installed properly (including proper kernel info in the system) and my phone is S-Off, but this is the method I've found that works.
If anyone experiences the issue, I'd recommend doing a back-up, full wipe and re-format (including internal and external SD, basically everything you can wipe); and then fastboot flash the boot.img pulled from your ROM zip before going into CWM and installing (always be careful when fastboot flashing; if you're new to it, you definitely need to familiarize yourself and read a tutorial or two; don't blame me if you're new to flashing, don't read tutorials and end up accidentally flashing a kernel to the wrong partition or some other problem).
Hope this helps out some of the people experiencing this issue.
I can relate
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
daspazz said:
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
Click to expand...
Click to collapse
How did you get it working
Sent from my ADR6410LVW using xda premium
Ok guys, i figured i've refrained from customizing my phone long enough.
I'm well aware of how to flash things onto the phone. I am currently running 4.2.2 on my C6606.
I have dualboot recovery flashed onto it, phone is rooted, and the only mod i have is pure audio.
I know i have to unlock my bootloader to be able to flash roms that require a custom kernel.
My question is, is there anything i should lookout for before flashing onto my phone?
I just want to know if these roms will also work on the t-mobile network. Haven't seen too much activity from C6606 users on here, so i'm a bit curious on that.
I don't believe you can unlock the bootloader on a C6606. If you could, you would need to back up your AT? partition; the one that has all your DRM keys and stuff. But you can still flash custom roms that are made for locked bootloaders, with stock kernels... I have flashed the stock roms from other regions and never had a problem with my C6606 working on the T-Mobile network.
Good luck!
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
shabbypenguin said:
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
Click to expand...
Click to collapse
Being able to get CM on the Z without unlocking the bootloader would be awesome.
iDroid8 said:
Being able to get CM on the Z without unlocking the bootloader would be awesome.
Click to expand...
Click to collapse
well i dont want peopel to get their hopes up about myself, its no easy feat and i applied for motorola financing last week, as i might end up going with a moto x. the bill with tmobile is a bit more than expected and going with a moto x would mean unlocked bootloader as well as lower monthly payments. you guys have some very talent people working on this device, it may end up happening on the z1 first and then get backported.
shabbypenguin said:
well i dont want peopel to get their hopes up about myself, its no easy feat and i applied for motorola financing last week, as i might end up going with a moto x. the bill with tmobile is a bit more than expected and going with a moto x would mean unlocked bootloader as well as lower monthly payments. you guys have some very talent people working on this device, it may end up happening on the z1 first and then get backported.
Click to expand...
Click to collapse
I'm just finding the process quite confusing. I haven't found any good videos detailing the entire process for a retard (myself).
iDroid8 said:
I'm just finding the process quite confusing. I haven't found any good videos detailing the entire process for a retard (myself).
Click to expand...
Click to collapse
videos on what?
shabbypenguin said:
videos on what?
Click to expand...
Click to collapse
Of flashing CM11. Most people aren't helpful and say if I can't unlock a bootloader then I shouldn't flash ROM's.
iDroid8 said:
Of flashing CM11.
Click to expand...
Click to collapse
its not possible with a locked bootloader at this time.
sbackus said:
I don't believe you can unlock the bootloader on a C6606. If you could, you would need to back up your AT? partition; the one that has all your DRM keys and stuff. But you can still flash custom roms that are made for locked bootloaders, with stock kernels... I have flashed the stock roms from other regions and never had a problem with my C6606 working on the T-Mobile network.
Good luck!
Click to expand...
Click to collapse
shabbypenguin said:
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
Click to expand...
Click to collapse
So say i tried to flash XperiaBlueLights, its a 4.2.2 rom, and it says its for a locked bootloader, it should work fine right?
Or the CriskeloRom, its 4.3 but it says it works on both locked and unlocked bootloaders. There shouldn't be an issue installing this on a C6606 should there?
Don't mean to ask so many questions, im usually the type to go and find out myself, but so far customizing my first sony phone isn't as fun, or easy as my past phones.
xDC23 said:
So say i tried to flash XperiaBlueLights, its a 4.2.2 rom, and it says its for a locked bootloader, it should work fine right?
Or the CriskeloRom, its 4.3 but it says it works on both locked and unlocked bootloaders. There shouldn't be an issue installing this on a C6606 should there?
Don't mean to ask so many questions, im usually the type to go and find out myself, but so far customizing my first sony phone isn't as fun, or easy as my past phones.
Click to expand...
Click to collapse
I think you would need to flash the C6606 kernel to be able to boot. I have written a C6606 tutorial for MIUI if you are interested in the Chinese version of Android. It is in the first post.
http://forum.xda-developers.com/showthread.php?p=46120012
C6606 user here. Currently running @niaboc79 4.3 Black Edition, and couldn't be happier.
I got my Z shortly after it became available, and have had a custom stock based ROM on it since day 1. I will admit there was a slight learning curve, but I knew I was switching to T-mobile and started reading up on the whole rooting/flashtool before I purchased and have stayed out of trouble (for the most part). Once you flash a ROM or two you will get the gist of it and it will become less confusing. The beauty of it is that we don't have to wait for T-Mobile to push out new Android versions. Once the Z gets it, so can we and no T-Mobile bloat. You will not have wifi calling if you haven't figured that out already.
Look for the "LB" (lockedbootloader) tag in the ROM title, and they should be good to go for us C6606 users.
Just follow the OP's instructions for installing and you will be fine. I haven't touched anything directly related to the C6606, other than APN's. I haven't had any luck doing the "download settings for internet and MMS" under wireless & networks settings.
I use these APN's every time I do a clean install and all network modes (3G, 4G, LTE) work just fine - http://forum.xda-developers.com/showthread.php?t=2236735
xDC23 said:
Ok guys, i figured i've refrained from customizing my phone long enough.
I'm well aware of how to flash things onto the phone. I am currently running 4.2.2 on my C6606.
I have dualboot recovery flashed onto it, phone is rooted, and the only mod i have is pure audio.
I know i have to unlock my bootloader to be able to flash roms that require a custom kernel.
My question is, is there anything i should lookout for before flashing onto my phone?
I just want to know if these roms will also work on the t-mobile network. Haven't seen too much activity from C6606 users on here, so i'm a bit curious on that.
Click to expand...
Click to collapse
yeah made sure you back your entire phone completely up! that way if something happens you can always go bck to the orginal state!
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
I have an unlocked bootloader and rooted Nexus 6. I usually run custom ROMs but I have had some issues when I install them for about the past week or so. I use Straight Talk CDMA which uses the Verizon towers. If I flash an official firmware such as LMY47I (5.1) or LMY47Z (5.1.1) then I have no issues with LTE connecting from the very beginning of the setup screen. Everything works fine including voice, data, and texting. When I install a custom ROM the signal will not connect and there is an exclamation point (!) next to the signal icon. I did have to exchange my phone and Motorola sent me a new one but I was able to use custom ROMs without issues on this phone until sometime earlier this week.
I know that people have been having some issues recently with connection problems and there are various threads on them. I have tried several of these workarounds but it just seems odd that I never had these issues before.
Any help or suggestions would be great. Don't mind running stock firmware but would prefer to be able to use custom ROMs again.
Thanks in advance.
emmittobie said:
I have an unlocked bootloader and rooted Nexus 6. I usually run custom ROMs but I have had some issues when I install them for about the past week or so. I use Straight Talk CDMA which uses the Verizon towers. If I flash an official firmware such as LMY47I (5.1) or LMY47Z (5.1.1) then I have no issues with LTE connecting from the very beginning of the setup screen. Everything works fine including voice, data, and texting. When I install a custom ROM the signal will not connect and there is an exclamation point (!) next to the signal icon. I did have to exchange my phone and Motorola sent me a new one but I was able to use custom ROMs without issues on this phone until sometime earlier this week.
I know that people have been having some issues recently with connection problems and there are various threads on them. I have tried several of these workarounds but it just seems odd that I never had these issues before.
Any help or suggestions would be great. Don't mind running stock firmware but would prefer to be able to use custom ROMs again.
Thanks in advance.
Click to expand...
Click to collapse
Try a different radio. I've read that the radio from the M test build is fixing some issues.
I've tried flashing a few of the newest radios but not the Android M version. Will give it a try.
Thanks for the reply.
Sent from my Nexus 6 using XDA Free mobile app
emmittobie said:
I've tried flashing a few of the newest radios but not the Android M version. Will give it a try.
Thanks for the reply.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
You can even flash an older radio if need be.
So I tried installing two different custom ROMs and both times I got the same signal icon with an (!) next to it. There is no working connection. I tried flashing the radio from the Android M preview and also installed the radio from LMY47D (Verizon 5.1.0) since I am on Straight Talk CDMA. Neither one seemed to help. After flashing these radios I went back to restoring a TWRP backup based on just a stock firmware. From what I understand the radio is separate from any particular ROM you flash and thus independent of each other. I am able to get an LTE signal when I revert back to the backup.
So now I'm stumped. It doesn't seem to be based on the radio. None of the custom ROMs that I was able to use less than a week ago are able to find an LTE signal after a clean install. I can only seem to use official firmware versions.
Any other possible ideas? Could the phone be defective? It was an RMA replacement and I think it was new and not refurbished.
Thanks in advance.
emmittobie said:
So I tried installing two different custom ROMs and both times I got the same signal icon with an (!) next to it. There is no working connection. I tried flashing the radio from the Android M preview and also installed the radio from LMY47D (Verizon 5.1.0) since I am on Straight Talk CDMA. Neither one seemed to help. After flashing these radios I went back to restoring a TWRP backup based on just a stock firmware. From what I understand the radio is separate from any particular ROM you flash and thus independent of each other. I am able to get an LTE signal when I revert back to the backup.
So now I'm stumped. It doesn't seem to be based on the radio. None of the custom ROMs that I was able to use less than a week ago are able to find an LTE signal after a clean install. I can only seem to use official firmware versions.
Any other possible ideas? Could the phone be defective? It was an RMA replacement and I think it was new and not refurbished.
Thanks in advance.
Click to expand...
Click to collapse
Really sounds like an APN issue. I have flashed a few ROMs and have had that problem. Most recently Exodus ROM. I changed the APN and all is well.
Evolution_Tech said:
Really sounds like an APN issue. I have flashed a few ROMs and have had that problem. Most recently Exodus ROM. I changed the APN and all is well.
Click to expand...
Click to collapse
Let me take a look at the APN settings on the stock firmware and then see how they compare when I use a custom ROM. In the past, I never had to set the APN settings as I thought they were set automatically on CDMA sim cards. I'll take a look.
Thanks.
emmittobie said:
Let me take a look at the APN settings on the stock firmware and then see how they compare when I use a custom ROM. In the past, I never had to set the APN settings as I thought they were set automatically on CDMA sim cards. I'll take a look.
Thanks.
Click to expand...
Click to collapse
Even if there's another APN with the same name as the one set by default, try switching to the other. That's what worked for me on Exodus.
Evolution_Tech said:
Even if there's another APN with the same name as the one set by default, try switching to the other. That's what worked for me on Exodus.
Click to expand...
Click to collapse
Thanks for the advice. I was able to compare the APN settings on a stock firmware and enter these settings into the APN settings of a custom ROM and able to get it to work. Just strange that I have to enter these settings manually when I never had to do it before. Thanks for all your help. Much appreciation.
emmittobie said:
Thanks for the advice. I was able to compare the APN settings on a stock firmware and enter these settings into the APN settings of a custom ROM and able to get it to work. Just strange that I have to enter these settings manually when I never had to do it before. Thanks for all your help. Much appreciation.
Click to expand...
Click to collapse
No problem, glad you got it straight. :good:
Hello everyone
I'm new to the HTC One M7 and what happens is that I have a problem with Wifi and Bluetooth, to activate nothing happens! Wireless does not show me the available networks, only stays in "Turning" and nothing happens more, same with the bluetooth but that does not worry me, what matters is the access, in settings can not put it off once I try to start wifi, just dead! I wonder if there is any Fix that can flash or something that makes the wifi working again because the only way that I connect it with LTE but again, the wifi did not work at all! please help
If you are rooted and running a custom ROM, I recommend updating the radios, firmware, etc to the latest. You may need to reflash the ROM as well.
I have a custom rom and root but the wifi problem began with the stock rom without root or modify anything, install the custom ROM and the root thinking wifi so the problem would end, but not so with other roms the problem continues why is that not what else to do, I even installed the rom several times with all the necessary wipes
Marcoant91 said:
I have a custom rom and root but the wifi problem began with the stock rom without root or modify anything, install the custom ROM and the root thinking wifi so the problem would end, but not so with other roms the problem continues why is that not what else to do, I even installed the rom several times with all the necessary wipes
Click to expand...
Click to collapse
My first step would be to update the firmwares, radios, etc. If you have a Sprint HTC One, you can find it here. If not, you're really in the wrong forum.
Marcoant91 said:
I have a custom rom and root but the wifi problem began with the stock rom without root or modify anything, install the custom ROM and the root thinking wifi so the problem would end, but not so with other roms the problem continues why is that not what else to do, I even installed the rom several times with all the necessary wipes
Click to expand...
Click to collapse
Maybe some hardware damages have been caused ask your phone seller first