Database Develop

Problem Custom Roms with some wifi in some phones like Velocity 4G x710s

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

[Q] Help - Droid 3 information "unknown"

All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.

dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
It may have been flashed to the 883 radio. I would do a complete SBF.

dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.

I have sbf'ed the phone, but it hasn't fixed the problem. I have installed the 833 radio previously and made sure I have pushed the build.prop into the system folder still without luck of fixing the problem. After a little more research, could the EFS folder be corrupt/deleted causing the problem?

Skreelink said:
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
Click to expand...
Click to collapse
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?

dinosaur swagg said:
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
Click to expand...
Click to collapse
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.

htsebar meafure
Skreelink said:
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
Click to expand...
Click to collapse
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too

dinosaur swagg said:
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
Click to expand...
Click to collapse
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.

Skreelink said:
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Click to expand...
Click to collapse
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?

dinosaur swagg said:
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
Click to expand...
Click to collapse
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.

Skreelink said:
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Click to expand...
Click to collapse
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.

dinosaur swagg said:
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
Click to expand...
Click to collapse
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.

Skreelink said:
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Click to expand...
Click to collapse
Okay so I have the 883 modified build.prop. Do you happen to have or know where/how I can get the stock build.prop?

[Q] Flashing a custom rom with phone already flashed to cricket

Good afternoon all,
I have an HTC One PN072. I've flashed the phone from Sprint to Cricket. They were very adamant about me not "resetting" the phone as it will remove the information, or flash they've added.
I've done several searches and can't seem to find a thread indicating 1) if this is possible and 2) a guide to doing so. The phone already is rooted and has TWRP on it as well.
If anyone knows of a thread I would love a link to a guide.

heartspains88 said:
Good afternoon all,
I have an HTC One PN072. I've flashed the phone from Sprint to Cricket. They were very adamant about me not "resetting" the phone as it will remove the information, or flash they've added.
I've done several searches and can't seem to find a thread indicating 1) if this is possible and 2) a guide to doing so. The phone already is rooted and has TWRP on it as well.
If anyone knows of a thread I would love a link to a guide.
Click to expand...
Click to collapse
I have a Sprint One fully flashed to Verizon and I flash custom ROMs all the time without any problems. I have never lost any settings and I don't even have to re-activate my phone. I would think that as long as you dont use Bootloader to flash a complete RUU image you should be fine. Goin s-off if your not already might cause issues here as well. (If someone knows for sure please correct me) I would say just download a ROM and install it with TWRP. I have updated firmware as well with no issues as well, however the firmware I upgraded with did not contain a radio update, which I am hesitant to do since I imagine that will effect my flash. I did my flash myself but it seems like a headache re-doing it.

electroblood said:
I have a Sprint One fully flashed to Verizon and I flash custom ROMs all the time without any problems. I have never lost any settings and I don't even have to re-activate my phone. I would think that as long as you dont use Bootloader to flash a complete RUU image you should be fine. Goin s-off if your not already might cause issues here as well. (If someone knows for sure please correct me) I would say just download a ROM and install it with TWRP. I have updated firmware as well with no issues as well, however the firmware I upgraded with did not contain a radio update, which I am hesitant to do since I imagine that will effect my flash. I did my flash myself but it seems like a headache re-doing it.
Click to expand...
Click to collapse
The wipes in TWRP usually recommended before flashing a custom rom don't remove their flashed data?

heartspains88 said:
The wipes in TWRP usually recommended before flashing a custom rom don't remove their flashed data?
Click to expand...
Click to collapse
Not that I have ever experienced. That was true on my EVO LTE and has so far been true on my One. I have the newest TWRP and in the past two days I have flashed EclipticOne, Elegencia and Insert Coin. On my old Droids Clockwork recoveries reset worked fine as well. DONT do a factory reset from inside the ROM. I have not tried it on my One, but on my EVO and my Droid 1/2/3 phones that would undo parts of a flash and I would have to reactivate. If I were you I would just work within my current firmware and flash what was available.
It is possible for you to flash your phone back to Cricket for free but its requires a lot of setup and can be a real pain in the ass. Getting 3G on Verizon was particularly painful and I have many screen shots and pages of notes on the actual procedure. When I upgraded from my EVO to the One I managed to get it right the first time by following my notes but it was still a serious hassle.

electroblood said:
Not that I have ever experienced. That was true on my EVO LTE and has so far been true on my One. I have the newest TWRP and in the past two days I have flashed EclipticOne, Elegencia and Insert Coin. On my old Droids Clockwork recoveries reset worked fine as well. DONT do a factory reset from inside the ROM. I have not tried it on my One, but on my EVO and my Droid 1/2/3 phones that would undo parts of a flash and I would have to reactivate. If I were you I would just work within my current firmware and flash what was available.
It is possible for you to flash your phone back to Cricket for free but its requires a lot of setup and can be a real pain in the ass. Getting 3G on Verizon was particularly painful and I have many screen shots and pages of notes on the actual procedure. When I upgraded from my EVO to the One I managed to get it right the first time by following my notes but it was still a serious hassle.
Click to expand...
Click to collapse
i was thinking about getting my one flashed to verizon but how does it work?? say i get my phone flashed.. is it verizon pre paid?? does that come with unlimited data?? text & talk?? how much would my bill be a month? sorry for all the questions

I apologize, so just to be as clear as possible, if you follow all of the wipes that roms usually ask you to perform in TWRP then you should be fine? However, do not perform a factory reset in the rom itself once loaded?

Doing a wipe through TWRP's wipe feature is fine as long as you dont go into 'Advanced' and mess with settings. Do not do the factory reset within the ROM once the ROM is loaded. If, while installing a ROM, the installer wants to do a wipe, that is fine as well.

VZW KK APN Settings

Somehow during my update to the 24A baseband, I lost my APN settings (there are no entries), and therefore have no mobile data ("Mobile Network State: Disconnected"). Where can I find the APN settings for my vzw g2? I found a site that claimed to have the correct VZW apn settings (can't post links yet, just google "buzzmobile verizon apn" and it's the top result) but for some reason, whenever I try and set the MNC to 012, the entire APN entry disappears from the menu. Entering all the other settings and leaving the MNC at its default (I think it was 004) didn't resolve my internet connection. Any ideas? I was thinking I could probably revert to stock KK using the kdz method, but since that'd be rather time consuming, if there's any way I could just flash a quick fix or something I'd prefer that.
I'm running Mahdi 6-28 build, V6 patch, 4.4.4 PA mini gapps, 24A baseband

After several hours of searching and troubleshooting I found a fix. Trying to make APN entries didn't lead anywhere, and editing the apn-conf.xml also did nothing. I had flashed 4 or 5 different 4.4.4 roms (some stock, some AOSP) and still nothing, but for whatever reason, doing a wipe and flashing XDABBEB's VS98024A v1.2.1 ROM (can't post link sorry) fixed my mobile data. I then did a system/cache/dalvik/data wipe and reinstalled Mahdi 6-28 and boom I have Mahdi with working LTE. Sorry for the spam I guess, but maybe this will help anyone having similar issues.

takethecake said:
After several hours of searching and troubleshooting I found a fix. Trying to make APN entries didn't lead anywhere, and editing the apn-conf.xml also did nothing. I had flashed 4 or 5 different 4.4.4 roms (some stock, some AOSP) and still nothing, but for whatever reason, doing a wipe and flashing XDABBEB's VS98024A v1.2.1 ROM (can't post link sorry) fixed my mobile data. I then did a system/cache/dalvik/data wipe and reinstalled Mahdi 6-28 and boom I have Mahdi with working LTE. Sorry for the spam I guess, but maybe this will help anyone having similar issues.
Click to expand...
Click to collapse
Ran into the same exact issue on a friend's phone. Going to try this out. Regardless if it works, thanks for the post!
UPDATE: It worked. The 24a bootstack includes the new modem and properly formats relevant partitions. I flashed XDABBEB's ROM just to replicate your exact procedure but this shouldn't be necessary. The bootstack is all that is needed when coming from a 12b rom.

topdawg7793 said:
Ran into the same exact issue on a friend's phone. Going to try this out. Regardless if it works, thanks for the post!
UPDATE: It worked. The 24a bootstack includes the new modem and properly formats relevant partitions. I flashed XDABBEB's ROM just to replicate your exact procedure but this shouldn't be necessary. The bootstack is all that is needed when coming from a 12b rom.
Click to expand...
Click to collapse
Having the same issue and flashing the 24a bootstack without the ROM does nothing. About to return this phone, it seems like nothing works correctly unless you are on the POS bloated stock ROM. What a shame, such potential on this device. Oh well.

remicks said:
Having the same issue and flashing the 24a bootstack without the ROM does nothing. About to return this phone, it seems like nothing works correctly unless you are on the POS bloated stock ROM. What a shame, such potential on this device. Oh well.
Click to expand...
Click to collapse
Return it to stock, let it take the KK OTA, root it, autorec for recovery, flash your 24A based rom of choice, that always works for me.
I had Carbon running fine on mine til I got bit by the black line issue. I haven't put AOSP on the replacement, probably will soon..

mjones73 said:
Return it to stock, let it take the KK OTA, root it, autorec for recovery, flash your 24A based rom of choice, that always works for me.
I had Carbon running fine on mine til I got bit by the black line issue. I haven't put AOSP on the replacement, probably will soon..
Click to expand...
Click to collapse
Trying this now, returning to 11a robbed me of my LTE for some reason though... doesn't even show up in the network info screen that shows the 3g/1x/LTE signal strength... weird...

remicks said:
Having the same issue and flashing the 24a bootstack without the ROM does nothing. About to return this phone, it seems like nothing works correctly unless you are on the POS bloated stock ROM. What a shame, such potential on this device. Oh well.
Click to expand...
Click to collapse
Haha I should have clarified. I meant that flashing the 24a bootstack and THEN flashing a 24a-based rom should do the trick. Flashing the 24a bootstack, XDABBEB's rom, and then (clean) flashing another 24a-based rom is redundant.

Thanks, doesn't matter now. Phone fell 1 foot and cracked to hell and touchscreen no longer works.

connection problem

i had a bootloop problem in my xt1254, fixed it with Computerfreek's ROM, flashed modems and everything but now i've got no connections and cannot setup my phone, no wi-fi or mobile data
mac address is marked as 02:00:00:00
even flashing stock 6.0.1 with RSD Lite doesn't work
help plz

joshua7727 said:
i had a bootloop problem in my xt1254, fixed it with Computerfreek's ROM, flashed modems and everything but now i've got no connections and cannot setup my phone, no wi-fi or mobile data
mac address is marked as 02:00:00:00
even flashing stock 6.0.1 with RSD Lite doesn't work
help plz
Click to expand...
Click to collapse
Which modems did you flash?
Sent via open market LG US998 V30/V30+

ChazzMatt said:
Which modems did you flash?
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
the ones Computerfreek posted in the rom thread (''MCG24.251-5+Radios+BL'')

joshua7727 said:
the ones Computerfreek posted in the rom thread (''MCG24.251-5+Radios+BL'')
Click to expand...
Click to collapse
just realized my mistake, i was flashing de wrong ones
now i flashed ''MCG24.251-5-5+Radios+BL-New'', then flashed Computerfreek 1.0.8 but still got no wifi or mobile data :/

Did you get this fixed?

no :'(

joshua7727 said:
just realized my mistake, i was flashing de wrong ones
now i flashed ''MCG24.251-5-5+Radios+BL-New'', then flashed Computerfreek 1.0.8 but still got no wifi or mobile data :/
Click to expand...
Click to collapse
One, you're sure you have a Droid Turbo and not another Quark like Moto Turbo/Moto Maxx XT1225? Sorry, I have to ask. Because while you can install this ROM on an XT1225 you won't get any mobile signal or Wi-Fi. Which is exactly your symptoms...
If you do have Droid Turbo XT1254, boot into TWRP and flash this Clean Modem file.
Clean_modem_status.zip
https://androidfilehost.com/?fid=24531035584725320
Then, flash THIS modem. It's ONLY the TWRP-flashable MCG24.251-5-5 modem -- not + bootloader like you flashed before. I want you to flash this AFTER you flash the clean modem file.
TheSt33v said:
[ROM] MCG24.251-5-5 100% Stock
By popular demand, here are just the modems: https://mega.nz/#!m9xnwDjD!jvvLXbGpCN9QVzRY1hph6JOyZv8kiBcLs2bsCdIgv8w
Click to expand...
Click to collapse
If that doesn't solve your problems, just as an experiment, flash this Quark custom kernel. It will work with all stock firmware, including this stock-based Computerfreek ROM. Kernel especially controls Wi-Fi, besides modem.
BHB27 custom kernel for Quark
https://androidfilehost.com/?w=files&flid=135512
Check your APN also. I don't know which carrier you have, it's possible the wrong APN settings are preventing connection. That shouldn't affect your Wi-Fi, but I'm looking for solutions.

ChazzMatt said:
One, you're sure you have a Droid Turbo and not another Quark like Moto Turbo/Moto Maxx XT1225? Sorry, I have to ask. Because while you can install this ROM on an XT1225 you won't get any mobile signal or Wi-Fi. Which is exactly your symptoms...
If you do have Droid Turbo XT1254, boot into TWRP and flash this Clean Modem file.
Clean_modem_status.zip
https://androidfilehost.com/?fid=24531035584725320
Then, flash THIS modem. It's ONLY the TWRP-flashable MCG24.251-5-5 modem -- not + bootloader like you flashed before. I want you to flash this AFTER you flash the clean modem file.
If that doesn't solve your problems, just as an experiment, flash this Quark custom kernel. It will work with all stock firmware, including this stock-based Computerfreek ROM. Kernel especially controls Wi-Fi, besides modem.
BHB27 custom kernel for Quark
https://androidfilehost.com/?w=files&flid=135512
Check your APN also. I don't know which carrier you have, it's possible the wrong APN settings are preventing connection. That shouldn't affect your Wi-Fi, but I'm looking for solutions.
Click to expand...
Click to collapse
Well, yes i do have a XT1254.
I wiped the phone for clean installing, flashed both files in order, then flashed Computerfreek 1.0.8
Still got no Wi-Fi, so i tried flashing BHB27's kernel, same result...
Now i remember a similar issue but in a brazilian rom, it boots but you have to flash your own modems, and i think this ones should work
ill keep u updated
(thx btw)

joshua7727 said:
Well, yes i do have a XT1254.
I wiped the phone for clean installing, flashed both files in order, then flashed Computerfreek 1.0.8
Still got no Wi-Fi, so i tried flashing BHB27's kernel, same result...
Now i remember a similar issue but in a brazilian rom, it boots but you have to flash your own modems, and i think this ones should work
ill keep u updated
(thx btw)
Click to expand...
Click to collapse
Tried that, didn't work either
The proccess i'm following is:
- Flash both modem files
- Flash ROM
- Flash Kernel
I dont know if i'm doing somthing wrong or what but plz, i need help

Did you have another ROM other than the stock cf274 before you started flashing? Are you on Verizon?

Well i had RR, then Stock, then Computerfreek
In RR and Stock it worked pretty well
And nope, i ain't in Verizon

joshua7727 said:
Well i had RR, then Stock, then Computerfreek
In RR and Stock it worked pretty well
And nope, i ain't in Verizon
Click to expand...
Click to collapse
OK I think this will work, you will need to clean everything including internal memory, then through twrp file mgr and your PC copy the latest bootloader and radio and cf274 ROM to internal. Be sure to use the ones for the country you are in. Sometimes there are files left over from RR that interfere with going to Cf274 ROM. I had that problem back sometime and by wiping everything a few times and following his instructions for your area it should work. Good luck
Been thinking, what version of twrp are you using? Latest bhb27 one?

newbe1droidx said:
OK I think this will work, you will need to clean everything including internal memory, then through twrp file mgr and your PC copy the latest bootloader and radio and cf274 ROM to internal. Be sure to use the ones for the country you are in. Sometimes there are files left over from RR that interfere with going to Cf274 ROM. I had that problem back sometime and by wiping everything a few times and following his instructions for your area it should work. Good luck
Been thinking, what version of twrp are you using? Latest bhb27 one?
Click to expand...
Click to collapse
i use twrp 3.1.1-mod_2
i've done this a lot of times
but i was playing around with TWRP's terminal and found this out
{
"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"
}
i don't know if its useful but seems interesting

Good correct twrp, regretfully I don't write code yet so it doesn't help me, hopefully someone who does can chime in on that.

joshua7727 said:
Well, yes i do have a XT1254.
I wiped the phone for clean installing, flashed both files in order, then flashed Computerfreek 1.0.8
Still got no Wi-Fi, so i tried flashing BHB27's kernel, same result...
Now i remember a similar issue but in a brazilian rom, it boots but you have to flash your own modems, and i think this ones should work
ill keep u updated
(thx btw)
Click to expand...
Click to collapse
Yes, on that Brazilian ROM posted over here you have to flash your own modem, like the one I linked to. BUT on that ROM you can only use the kernel listed in that thread. It's an older BHB27 kernel but it's compatible with that ROM. You cannot update the kernel without issues.
newbe1droidx said:
OK I think this will work, you will need to clean everything including internal memory, then through twrp file mgr and your PC copy the latest bootloader and radio and cf274 ROM to internal. Be sure to use the ones for the country you are in. Sometimes there are files left over from RR that interfere with going to Cf274 ROM. I had that problem back sometime and by wiping everything a few times and following his instructions for your area it should work. Good luck
Been thinking, what version of twrp are you using? Latest bhb27 one?
Click to expand...
Click to collapse
Yeah, wiping everything in TWRP never hurts, for a really clean install. Just make sure you have all your materials (stored on PC) handy to drag over from PC to TWRP to install again. You don't want to be searching for stuff with a dead phone on your hands that you can't reboot. Test your PC-to-TWRP connection before wiping.
One more suggestion. Flash back to stock completely, see if it works. Then try to flash to the ComputerFreak ROM?

ChazzMatt said:
Yes, on that Brazilian ROM posted over here you have to flash your own modem, like the one I linked to. BUT on that ROM you can only use the kernel listed in that thread. It's an older BHB27 kernel but it's compatible with that ROM. You cannot update the kernel without issues.
Yeah, wiping everything in TWRP never hurts, for a really clean install. Just make sure you have all your materials (stored on PC) handy to drag over from PC to TWRP to install again. You don't want to be searching for stuff with a dead phone on your hands that you can't reboot. Test your PC-to-TWRP connection before wiping.
One more suggestion. Flash back to stock completely, see if it works. Then try to flash to the ComputerFreak ROM?
Click to expand...
Click to collapse
i have done that many times, none of them successful

joshua7727 said:
i have done that many times, none of them successful
Click to expand...
Click to collapse
Maybe you have a hardware issue . I don't know.

ChazzMatt said:
One, you're sure you have a Droid Turbo and not another Quark like Moto Turbo/Moto Maxx XT1225? Sorry, I have to ask. Because while you can install this ROM on an XT1225 you won't get any mobile signal or Wi-Fi. Which is exactly your symptoms...
If you do have Droid Turbo XT1254, boot into TWRP and flash this Clean Modem file.
Clean_modem_status.zip
https://androidfilehost.com/?fid=24531035584725320
Then, flash THIS modem. It's ONLY the TWRP-flashable MCG24.251-5-5 modem -- not + bootloader like you flashed before. I want you to flash this AFTER you flash the clean modem file.
If that doesn't solve your problems, just as an experiment, flash this Quark custom kernel. It will work with all stock firmware, including this stock-based Computerfreek ROM. Kernel especially controls Wi-Fi, besides modem.
BHB27 custom kernel for Quark
https://androidfilehost.com/?w=files&flid=135512
Check your APN also. I don't know which carrier you have, it's possible the wrong APN settings are preventing connection. That shouldn't affect your Wi-Fi, but I'm looking for solutions.
Click to expand...
Click to collapse
Good day friend, I have that same problem, just that I have the bootloader blocked, is it solvable ?, I've already tried flashing with different radio fastboot, but it does not work. XT1254 , Not have BASEBAND.
---------- Post added at 03:02 PM ---------- Previous post was at 02:13 PM ----------
joshua7727 said:
Tried that, didn't work either
The proccess i'm following is:
- Flash both modem files
- Flash ROM
- Flash Kernel
I dont know if i'm doing somthing wrong or what but plz, i need help
Click to expand...
Click to collapse
Did you solve it?