had been trying roms for months now, and 2 weeks ago just starting bootlooping. was running carbon rom when the bootloop started. changed to padawan v2, bootloop went away for a few days and then came back. thought it was power button but when im in cwm it doesnt bootloop.
even all my backups they bootloop. today i went back to stock and using odin and reboots after the att logo.
is my phone done for? thanks
Try an emergency recovery with kies.
fixed it!
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
ufuknut said:
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
Click to expand...
Click to collapse
Hi, I wanted to know what radio version you flashed, because I'm getting the exact same error but none of the radios works for me, I'm also using padawan because of what you said.
Related
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I dont use ROM manager to flash it in, I flash everything in through recovery.
McLabia said:
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I flash everything in through recovery.
Click to expand...
Click to collapse
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
devindpotts said:
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
Click to expand...
Click to collapse
The ROM Ive been on hasnt mattered. Ive jumped through BAMF, the new Cubed Rom, the Deodexed stock debloat and Virus' Airborne(which is my daily driver). Ive done the different radios. I was on the v2 leaked for a while, then I switched to the new 3g and old 4g to see if its worked but it hasnt. I may have to try out the original one and see if that works, but I havent had wifi since before I flashed in the leaked radio when it came out.
isdnmatt said:
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Gotcha. Trying this now. I will make sure to make a nandroid this time if it works. lol.
@isdnmatt: Thanks, that got rid of my recovery problem
Still having wifi issue though. 100% out of the box stock and I get the "Unable to scan for networks
**** me, I should have read that before I did it. Now I have to reroot. Goddamnit.
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
ILMF said:
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thats a separate issue than what Im having. Im not having issues with it forgetting my networks. I cant scan for networks.
I am thinking of downgrading the radio.
EDIT: after LOTS of research here, I upgraded to MR2 and Gingervitis. All of my WiFi issues are gone.
Sent from my TBolt using XDA Premium App
I am coming from a Galaxy Nexus. I have flashed many roms in the past, but when I flash roms on the Note the phone portion seems to stop working. Data works fine, its just when I try to make a call it just sits there for a long time and then the call terminates. Happens every time a flash a new rom. With my old Droid 1 on Verizon you could dial up a number to reactivate the phone, on the Nexus this seems to not be an issue at all. Is there some trick to getting AT&T to reinitialize the cell phone after a new rom flash? I tried pulling the battery for like 5 minutes figuring that would force it to resync or something...
Any one else running into this?
Never heard of this problem. Which roms are you loading, I would suggest asking the dev of the ROM, including all of the steps you use to install it.
Sent from my SAMSUNG-SGH-I717 using XDA
I completely agree with you and same thing is happening to my note as well...I thought i was in bad signal area....now i am running into problems with google market....cant load apps...always showing error 492....i installed saurom rom rc7 and also i dont see what kernel i have on my phone....i also installed the kernel fix and flashed it....still nothing...i am myself trying to get some help here
busybeebusy said:
I completely agree with you and same thing is happening to my note as well...I thought i was in bad signal area....now i am running into problems with google market....cant load apps...always showing error 492....i installed saurom rom rc7 and also i dont see what kernel i have on my phone....i also installed the kernel fix and flashed it....still nothing...i am myself trying to get some help here
Click to expand...
Click to collapse
To fix the market you need to reboot to clockworkmod and clear the cache. The issue with the kernel is normal, it is the HoloKernel, it just has bad information in the about screen, that's normal too.
To fix the phone issue I usually pull the battery for like 5 minutes and then toggle the network from auto to manual a couple of times and then it seems to finally pick it up. Just seems odd...
omniphil said:
I am coming from a Galaxy Nexus. I have flashed many roms in the past, but when I flash roms on the Note the phone portion seems to stop working. Data works fine, its just when I try to make a call it just sits there for a long time and then the call terminates. Happens every time a flash a new rom. With my old Droid 1 on Verizon you could dial up a number to reactivate the phone, on the Nexus this seems to not be an issue at all. Is there some trick to getting AT&T to reinitialize the cell phone after a new rom flash? I tried pulling the battery for like 5 minutes figuring that would force it to resync or something...
Any one else running into this?
Click to expand...
Click to collapse
Did you flash the ATT fix after flashing RC7? If not, download ATT fix, flash Saurom RC7, wipe cache and d cache, flash ATT fix and then reboot system...
Update.....yesterday i opened the cwm and just cleared the wipe cache and then rebooted the phone and everything came back to normal...error code 492 disappeared and i was able to download all my apps.. I hope it will help somebody. Running saurom rc7. Everything looks fine so far....only data speed needs to go up some more but it could be the area....
Sent from my SGH-I717R using XDA
omniphil said:
To fix the market you need to reboot to clockworkmod and clear the cache. The issue with the kernel is normal, it is the HoloKernel, it just has bad information in the about screen, that's normal too.
To fix the phone issue I usually pull the battery for like 5 minutes and then toggle the network from auto to manual a couple of times and then it seems to finally pick it up. Just seems odd...
Click to expand...
Click to collapse
What is the problem with the kernel that you need to flash the kernel fix? Is that only if you use holo kernel?
When I flashed 7/18 version of tweaked vzw remix I stated getting random shutdowns not reboots ( i pull my phone out and screen won't turn on, hold down power and it boots up fine and I have no isseus). I was getting atleast 3-4 of those a day. The new release was on its way so I wasn't worried, figured might be a bad download or kernel issue. the next release came out and I flashed it along with pbj kernel and same thing. After a few days they decreased and then hadn't had any for a week or so.
Today I went back to clean rom 3.5 and I started getting them again.
Anyone have any ideas what could be causing this? The only new app I have downloaded recently is the game dots. Neither time have I restored any data from tibu (I have been to lazy to do it)
any help is appreciated.
Have you tried going back to stock with odin and starting from scratch?
droidstyle said:
Have you tried going back to stock with odin and starting from scratch?
Click to expand...
Click to collapse
No I have not tried that. I just got the phone back in July, samsung had to replace cdma radio so it was all stock then. During the times I've had issues,there was a day I was on beans build 21 and cant remember the shut down issues happening that day. If it doesn't get better the next few days may try using Odin then rooting and unlocking it again.
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
renegadeone8 said:
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
Click to expand...
Click to collapse
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Possibly
lemonoid said:
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Click to expand...
Click to collapse
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Did all that
Jaggar345 said:
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Click to expand...
Click to collapse
I have done all of that stuff multiple times
I haven't installed any apps at all on it. This phone is basically brand new, I got it right when they launched. I shattered the screen like 3 days after I got it, and tucked it in a drawer. It has been sitting there ever since.
I have another piece to add to the puzzle. While it has the stock ROM installed it seems to get service and work just fine, but when I install the custom ROMS it has absolutely zero cell connectivity (though WiFi works fine.)
Going into the settings reveals that on the custom roms it shows the IMEI and MEID as Unknown, and the ICCID is listed as Unknown as well. If I try to change the network mode (to LTE/CDMA or any one of the many available options) it says com.phone has crashed.
After the RUU process I have my proper MEID and ICCID showing in the settings panel, and service returns.
Can't flash radio?
After discovering the issues with the service while on custom ROMS I wondered if the radio had something wrong with it.
I tried to manually reflash the radio via fastboot (fastboot flash radio radio.img).
I tried this both in standard fastboot as well as in the rebootRUU mode, but both times I get an error that says remote not allowed. Could my bootloader somehow still be locked? The flag in bootloader mode says "Unlocked" but I unlocked manually after obtaining s-off rather than doing it officially via HTCdev. just trying to explore all options
My phone did that at one point. I had to re-lock and RUU back to 100% stock. I then unlocked my phone with Rumrunner S-Off tool. Flashed a Sense 6 ROM and has been working fine since.
Fixed!
So this problem is fixed!! I am not 100% sure what did the trick, so I will post my solution here in case anybody else experiences a similar issue. I won't go into too much detail with these instructions as all the tools are here: http://forum.xda-developers.com/showthread.php?t=2612740
I first downgraded to the 1.15 hboot and radio. I had to rebootRUU and flash them there as it can't be done directly in fastboot as far as I know.
Do them one at a time (flash the hboot, then reboot-bootloader, then rebootRUU then flash the radio, then reboot bootloader again.)
After doing this I tried to run the RUU exe but it came up with an error that it could not update my phone, so I did the manual Alt 3.06 RUU.
This seemed to work great, restarted the phone and saw the stock rom. I then changed from superCID 11111111 back to the stock CID, relocked my bootloader went back to s-on status. At this point I ran the RUU.exe again just to make sure everything was as stock as could be.
Got that all finished, ran RumRunner again, installed CM11 and no reboot for nearly 24 hours. Pretty sure all is well!
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
lemonoid said:
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
Click to expand...
Click to collapse
Good news and bad news. The good news is for you!!! I think I figured out what the problem was. It seems to be an issue either with using an older radio, or an older hboot on a newer ROM. I don't know why exactly, but the RUU process was not properly updating my radios. This may be because I ran an RUU while unlocked at one point (every guide I see is very adamant about relocking before the RUU process.)
The bad news is that I ordered a new LCD for my DNA, and I ruined my phone trying to do the repairs. It is by FAR the worst phone I have ever had to work on. I have replaced LCD's in Galaxy devices, Iphones/ipod touches, laptops, TV's, and one in a smartwatch and have never hurt a thing. Got my DNA back together and it flat out wont turn on I don't know what the problem is, but something is fried. Hope you have better luck than me!