Related
i downloaded and have been running asops 2.2 rom but i just changed my phone number with sprint and I cant figure out how to update the msid. obviously sprint cant help me since im not using stock rom. anyone know where to look or an app i can download, because under settings: about phone: phone status: shows my old phone number, and i cant make calls or send msgs because of it.
they kept giving me ## codes but they wont work it just tries to dial the number.
Sorry woulda responded sooner, been busy. You need to flash a sense rom to use dialer codes our have sprint modify the phone or account info tied to it.
ugh... ok can you recommend a quick and simple rom so i can do that real quick
hate flashing it takes forever without a highspeed usb. anyways, downloading a sense rom now. thanks
arrg! ok i downloaded and flashed over to herocs 2.2 sense rom, tried doing the ## codes and nothing happens.
anyone??? im kinda screwed here.. cant use my phone until i get the prl updated
If all you need to do is update prl, and you have a sense rom flashed, you can do that from phone settings. I believe it is under "about phone".
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
user7618 said:
If all you need to do is update prl, and you have a sense rom flashed, you can do that from phone settings. I believe it is under "about phone".
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
Click to expand...
Click to collapse
it should be, but its not. under about phone, this is what i have :
network
phone identity (no update option)
battery
hardware information
software information
legal information
MyHerox25 said:
it should be, but its not. under about phone, this is what i have :
network
phone identity (no update option)
battery
hardware information
software information
legal information
Click to expand...
Click to collapse
Just use LiquidSense to update it.
what is liquidsense?
this is the rom i flashed to for temporary purposes
It is a 2.1 Sense ROM that can be found in the Development section.
well i guess no need to worry about this anymore, the charging dock on my phone is now broken or something because nothing will charge my phone.
Try a different battery. Or a different usb cable.
Root/Hack-Mod_Always*
ok i was in panic mode earlier being without my phone and all...
got liquidsense, updated all info. all good there. however when i flashed back to aosp rom its suddenly really glitchy, i cant get passed the "touch the android" set up screen!
attempting to reflash and see if that helps any...
nope....man this is a nightmare. btw gave thanks to everyone who replied in this post.
well... i flashed back to LS and even that one glitches out at the set up menu. so im still nowhere with my phone.
**UPDATE**
i found a backup copy of aosp rom that i originally downloaded in another folder on my sd. everything is working just fine now couldn't have done this without your help (all of you)
MyHerox25 said:
well... i flashed back to LS and even that one glitches out at the set up menu. so im still nowhere with my phone.
**UPDATE**
i found a backup copy of aosp rom that i originally downloaded in another folder on my sd. everything is working just fine now couldn't have done this without your help (all of you)
Click to expand...
Click to collapse
Glad you got it up and running.
First Just for your future reference so your not crappin all over yourself.lol (Been there) If you haven't already make a nadroid of the LS Rom or sense Rom that you used.
Second,I believe alot of the people around here that flash between sense and CM and AOSP do a factory rest or wipe from fastboot(look in this guide for instructions on this http://forum.xda-developers.com/showthread.php?t=1063843 by forum memeber il Duce )the reason being is that (from what I've read) is that sense roms leave bits and pieces of files behind that can corrupt a flash,or make you phone wonky after it boots up.
P.S. If you ever have to RUU or unroot when you re-root makea nandroid of that after you root and keep it some where safe so you can go back to it.
Yes, wipe data, cache, and dalvik every time you change roms. Especially between sense and aosp. The only exception us when flashing an update to the rom you're currently running. Even then, it may require a cache and dalvik wipe. Wipes are not necessary when restoring a nand. Also, keeping a sense nand is a good idea, as out makes it quicker when prl updates are needed.
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
Hey boys & girls
I've got a problem:
Every time when i flash a Sense Rom on my Nexus One everything is fine when i start it up. Network is fine and also Mobile Data is fine, but when press the sleep/wake button to lock the screen the mobile data dissapears
Then when i enter settings to turn it on again, it's not getting on
That happens to me on every Sense Rom (Kingdom v0.2, evil's NXSense, Modacos r24,..)
The APN Settings are correct.
I'm really pissed of because the Roms are great but they are useless for me without Mobile Data
My Phone:
Radio Update - 5.12.00.08
RA-passion-v2.2.1
HBoot 0.35.0017
Any suggestions?
What recovery are you using if your using clockwork 3.x I would change to either a previous version of clockwork (i.e. 2.5.1.4). And if your on Amon RA then I would try doing a temasek system wipe before flashing your ROM.
I'm using Amon RA-passion-v2.2.1.
What is a "temasek system wipe"?
When I flash a CM7 onto my nexus one there is no mobile data problem, only with these sense roms.
temasek wrote a script to do a more thorough wipe than the one normally performed through recovery...
Heres a copy of the script:
http://db.tt/fH1vZNM
Temasek system wipe is a .zip file that will wipe the system partition of the phone this will sometimes solve problems when flashing ROMs. Here is a link to the zip just flash it like any other zip http://www.mediafire.com/?7l9nadd9ekkp7ae
EDIT: You beat me to it danger
thanks guys! I will test it and let's see if it solves the problem
Edit: Does this also wipe battery stats, so that i have to calibrate my battery?
Ok i flashed the extremewipe.zip and then flashed a rom onto my nexus one. Now the phone reboots into the fastboot mode everytime a press "reboot phone" in the recovery menue. How can i fix that?
Sounds like it might be missing the boot partition. What firmware did you flash?
eViL's NXSense HD
Unfortunately, I am not familiar with Sense-based firmwares. Have you tried an alternate to see if it is limited to that particular one? Maybe try and flash CyanogenMod as I know that will work fine after using the Extreme Wipe.
Okay now I'm on CM7 and everything works! Is it possible that i need a froyo radio when i use this sense based roms?
Gingerbread works best with the 5.08 radio (found under Settings -> About phone -> Baseband (we take the two sets of numbers after the underscore "_"). I don't think Sense has any additional requirements with it.
I think the the ROM you flashed didn't contain anything for the /boot partition (or it just screwed up with the flash)... but that is just a guess.
So, I have to roll this thread up again.
Now I'm back on CM7 Nightly, everything works also data
And I think I tested all Sense Roms out there for the Nexus One and for me only KingX's Sense Rom and NexDesire were working.
But with these two, Bluetooth isn't working
On every other Sense Rom it is the same
I start the Rom and Data is there and after i press the sleep button to turn the display off, my mobile data dissapears, I have no clou what is wrong with my N1.
On all the Gingerbread Roms my mobile data works but the Sense Roms are killing it.
I just want to use a Sense Rom
Sorry for waking up the dead but I have the same issue. It seems to be an incompatibility between libhtc_ril.so in the rom with the radio that nexus one is running. Now, Im not sure how that could be generalized because many users have installed same roms that we tried and as well same radios and no issues with radio/data disconnecting when screen goes to sleep.
So, again, any bright mind cares to give a spoon of wisdom?
What are we missing?
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&A] [ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | Sense 6 | Deodexed | BB Updater | Upd
Q&A for [ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | Sense 6 | Deodexed | BB Updater | Updated 6/19/14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | Sense 6 | Deodexed | BB Updater | Updated 6/19/14 . If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I'm having the same issue with the ringtones. I could never add a custom ringtone even in the previous versions of this ROM.
Using ES File Explorer, when I try to copy my ringtones to system/media/audio/ringtone, ES File Explorer gives me an error, which is "EROFS - Read Only File System". When I checked the properties of that folder, both "Readable" and "Writeable" are "Yes".
I also moved my ringtones to the sdcard/ringtone folder. When I select one of my custom ringtones from the menu ("Select music track"), it reverts back to the Ringtone menu without making any selection.
wfa22 said:
I'm having the same issue with the ringtones. I could never add a custom ringtone even in the previous versions of this ROM.
Using ES File Explorer, when I try to copy my ringtones to system/media/audio/ringtone, ES File Explorer gives me an error, which is "EROFS - Read Only File System". When I checked the properties of that folder, both "Readable" and "Writeable" are "Yes".
I also moved my ringtones to the sdcard/ringtone folder. When I select one of my custom ringtones from the menu ("Select music track"), it reverts back to the Ringtone menu without making any selection.
Click to expand...
Click to collapse
Have you tried flashing this fix? I had a problem where it couldn't find my custom ringtones in the ringtone folder, but after flashing this, it was there.
http://forum.xda-developers.com/showpost.php?p=53557269&postcount=1195
That did it! You're a life saver! Thank you very much!
Wifi Issue for Bad Boyz 4.4.4 update
After booting up my updated HTC One M8 into Bad Boyz 4.4.4 Rom, I wasn't able to turn wifi on. Also I can't get the regular system update to see that I have 4.4.4 and to stop prompting me to download it.
The ability to download certain mods for the phone is amazing though props to the Devs! Thank you!
If anyone knows how to fix the wifi issue please let me know. I wiped Cache before and after the install of the Rom. Not sure what could have gone wrong.
If anyone can help with this I would be grateful I use wifi a lot to download larger files or stream because my LTE Connection isn't that great in my apt.
Fairly major issues, Seems really outdated.
I just flashed the rom and kernal included in the download list. Google Play won't connect, and Blink Feed literally crashes constantly. I am unable to get the phone to do anything. I would clear the BlinkFeed crash message and immediately another would pop up. I flashed this rom back when it was first published and everything worked great. I then had to return my phone to stock so I could get screen replacement, now this rom appears to have gone from the best, to useless.
Reagarding the Post
Yes Really I have done this and works well even in PC and also in Android mobiles.
Quick question, the only roms I have used have been stock and CM11 on my M7,
With CM11, HTC Synch would not see the phone, I have tried other programs for backing up, HTC Synch has been the only one that works for me.
Will HTC Synch see my phone with this rom???
EDIT:
Never mind, I'm an idiot
I am thinking TWRP 2.8.0.2 isnt the recovery to use......
Been sitting for about 5 minutes with no movement trying to flash..
Any ideas??
HTC Synch doesn't see it, but that doesn't matter.
I been searching the Rom thread for battery issues, my battery is getting sucked dry super fast, other then this, the Rom flies, I love it....
Slagathor01 said:
HTC Synch doesn't see it, but that doesn't matter.
I been searching the Rom thread for battery issues, my battery is getting sucked dry super fast, other then this, the Rom flies, I love it....
Click to expand...
Click to collapse
Amplify may be your best friend. Btwn that and apps like Greenify and something other than the stock kernel may make your battery life wonderful.
In my use of this rom (my standby DD when I'm not trying something new), my biggest knock in battery life was when I was using ElementalX kernel with wake gestures enabled. It was awesome, but it gobbled on my battery like nothing else. Ifound myself charging my phone almost twice a day. With the apps mentioned and Kangaroo kernel (for 4.4.2)? I got crazy life.
MFOsaka said:
Amplify may be your best friend. Btwn that and apps like Greenify and something other than the stock kernel may make your battery life wonderful.
In my use of this rom (my standby DD when I'm not trying something new), my biggest knock in battery life was when I was using ElementalX kernel with wake gestures enabled. It was awesome, but it gobbled on my battery like nothing else. Ifound myself charging my phone almost twice a day. With the apps mentioned and Kangaroo kernel (for 4.4.2)? I got crazy life.
Click to expand...
Click to collapse
Not sure which one to snag??? Or if I am even on the right track....
https://www.androidfilehost.com/?w=files&flid=15248
Go for v138 and you should be golden.
MFOsaka said:
Go for v138 and you should be golden.
Click to expand...
Click to collapse
Sweet, thank you sir, snagging it now...
I apologize if this has already been covered, but whenever I try to search a thread through the xda app I get all kinds of garbled results, and trying to read through this whole thread would take months... For some reason, neither "modifications" in settings nor the HUB app will work for me. They always give a pop-up that says "myHUB has quit working." No other issues with the ROM. Any ideas? Is there a link to reinstall myHUB without having to re-flash the entire ROM?
sim
i am using bad boyz one sense 5.5 v1.4 [4.3] right now and my sim is working fine
my question is am i able to use my sim on this version or my sim wont work on it ?
Waiting for Reply
Regards
New Version of the software.
Hi Sir,
I have rooted my HTC One M8 and currently having the Bad Boyz Sprint ONE M8 Harman v1.5 ART
Andorid Version 4.4.3
HTC sense version 6.0
Currently I am in US and running my phone on Sprint as It didn't work on T-mobile and Lyca Sim.When I used in India, it worked with GSM carriers. I have the MSL also for this.
I wanted to know if there is any software UPDATE from your end for my device. I keep getting a System Update from HTC which I obviously can't install.
Can you please help and guide me sir.
Regards
Firmware Confusion - Updating to the 5.0.2 BB ROM from 4.4.2 BB ROM
Hi all,
Could you guys please advise me on how to go about updating from the 4.4.2 BB ROM to this new Lollipop BB ROM? Previously, when upgrading, I just downloaded the ROM directly to my device and flashed from TWRP. I never dealt with an accompanying firmware update or reflashing TWRP. I never had to mess with fastboot on the computer after the original unlocking/rooting. I recently tried running the Lollipop RUU.exe directly from Sprint to return to stock and get the OTA update, but it would not work because presumably my firmware was old. It said I had 1.31.652.1 when I did getvar all in fastboot mode because I had done an OTA update a long time ago. Apparently there is no 1.31....RUU readily available (5 hours of googling and scouring forums). I read people used 1.29... so I relocked my bootloader and tried the 1.29....RUU.exe, but that did not work. That got my device stuck in the bootloader. Could not access TWRP or boot to the OS. I was able to unlock the bootloader, wipe it, and somehow wound up with a fresh 4.4.2 BB ROM. I successfully flashed the latest TWRP 2.8.4.0 just to have it.
Currently my device is running the 4.4.2 Bad Boyz Sense 6 ROM and the latest 2.8.4.0 TWRP. Main goal - to get Lollipop (don't care if it's custom or stock). If I have the BB 4.4.2 ROM, does that mean I have the firmware version 5.03.651.3? If so, would running the 5.03.651.3 RUU.exe revert me to stock and thus able to receive the 5.02 Lollipop OTA update? Can I just download the Bad Boyz Lollipop ROM and flash that from within TWRP and be done? Or will I need to worry about flashing an additional firmware file, and can that be done from TWRP?
Currently S-On, but I have Hboot 1.44 so I should be able to revone and S-Off if necessary for whichever way is easier, right?
Unlocked bootloader.
Can't find the firmware version. Where can I find it?
Please advise me on the steps necessary to get this Lollipop update.
Also, thanks Bad Boyz for bringing it to everybody!
allison1derland said:
Hi all,
Could you guys please advise me on how to go about updating from the 4.4.2 BB ROM to this new Lollipop BB ROM? Previously, when upgrading, I just downloaded the ROM directly to my device and flashed from TWRP. I never dealt with an accompanying firmware update or reflashing TWRP. I never had to mess with fastboot on the computer after the original unlocking/rooting. I recently tried running the Lollipop RUU.exe directly from Sprint to return to stock and get the OTA update, but it would not work because presumably my firmware was old. It said I had 1.31.652.1 when I did getvar all in fastboot mode because I had done an OTA update a long time ago. Apparently there is no 1.31....RUU readily available (5 hours of googling and scouring forums). I read people used 1.29... so I relocked my bootloader and tried the 1.29....RUU.exe, but that did not work. That got my device stuck in the bootloader. Could not access TWRP or boot to the OS. I was able to unlock the bootloader, wipe it, and somehow wound up with a fresh 4.4.2 BB ROM. I successfully flashed the latest TWRP 2.8.4.0 just to have it.
Currently my device is running the 4.4.2 Bad Boyz Sense 6 ROM and the latest 2.8.4.0 TWRP. Main goal - to get Lollipop (don't care if it's custom or stock). If I have the BB 4.4.2 ROM, does that mean I have the firmware version 5.03.651.3? If so, would running the 5.03.651.3 RUU.exe revert me to stock and thus able to receive the 5.02 Lollipop OTA update? Can I just download the Bad Boyz Lollipop ROM and flash that from within TWRP and be done? Or will I need to worry about flashing an additional firmware file, and can that be done from TWRP?
Currently S-On, but I have Hboot 1.44 so I should be able to revone and S-Off if necessary for whichever way is easier, right?
Unlocked bootloader.
Can't find the firmware version. Where can I find it?
Please advise me on the steps necessary to get this Lollipop update.
Also, thanks Bad Boyz for bringing it to everybody!
Click to expand...
Click to collapse
My understanding (limited as it may be) is that you only need S-OFF to flash custom kernels. I've never found a real need to do so but I was able to S-OFF with REVONE back in the day. For now if you are S-ON but unlocked, you'll need to flash the full firmware (link in the Bad Boyz thread and there's a firmware thread as well). My suggestion is you go to this post by @O.M.J http://forum.xda-developers.com/showpost.php?p=58766627&postcount=1694 and follow the instructions for S-ON users before flashing the new BB Lollipop.
Good luck
P_M_G said:
My understanding (limited as it may be) is that you only need S-OFF to flash custom kernels. I've never found a real need to do so but I was able to S-OFF with REVONE back in the day. For now if you are S-ON but unlocked, you'll need to flash the full firmware (link in the Bad Boyz thread and there's a firmware thread as well). My suggestion is you go to this post by @O.M.J http://forum.xda-developers.com/showpost.php?p=58766627&postcount=1694 and follow the instructions for S-ON users before flashing the new BB Lollipop.
Good luck
Click to expand...
Click to collapse
Unfortunately that doesn't address any of my specific questions. I've read that forum post already. Thats how I know the new ROM exists. I've read this http://forum.xda-developers.com/showthread.php?t=2694171&page=170 and this http://forum.xda-developers.com/showthread.php?t=2795856 and do not see directions pertaining to flashing from within TWRP. The requirements section only says fast boot flashable in parentheses for some things.
Thanks for trying, but here are my question again:
Can I just download the Bad Boyz Lollipop ROM directly to my phone and flash that from within TWRP and be done? Or will I need to worry about flashing an additional firmware file, and can that be done from TWRP? As I said, I've just used TWRP in the past, not fast boot on the computer. Also, updating only required flashing 1 ROM in the past, so why does he bring up additional files, and can those be flashed from TWRP?
If I have the BB 4.4.2 ROM, does that mean I have the firmware version 5.03.651.3? If so, would running the 5.03.651.3 RUU.exe revert me to stock and thus able to receive the 5.02 Lollipop OTA update? Can't find the firmware version. Where can I find it? Software Info in About section just says Bad Boyz Sense 6. Thats not a firmware #.
Please advise me on the steps necessary to get this Lollipop update.
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: