Related
Hello,
I've been flashing for a long time and currently I'm running Bionix 1.2. I've got 2 major problems and I have a workaround for each; however I thought the community might know better than me.
The first one is about the signal bars and dropped calls. I live in an area (Maine) where you never experience a dropped call since there aren't many people living. At least with my old MyTouch and stock Vibrant, I never had one. So almost once a day I drop call and see the all the signals gone. Sometimes, I see signals but there is no data or GSM connection since I cannot login to GTalk and other services (FB, twitter, etc.). I read in the development section that turning flight mode on/off can help. Well for me, it sometimes helps, sometimes doesn't. I find myself rebooting to solve the problem at least. I am a little concerned since I might need my cell in case of an emergency and I definitely would not want to wait for a reboot to call 911.
The second one is about the GPS. If I open navigation and ask for turn-by-turn directions, almost every time, it gets stuck searching for GPS. The workaround for me is to launch Maps, wait a few minutes to locate my location; then ask for directions. Although, this might not work from time to time. Again, in the middle of nowhere, you are driving and need a quick and dirty turn-by-turn directions and your smart Vibrant makes you go thru a lot of hassle to accomplish your task.
Any advice from our community?
Thank you!
Flash to stock, call t mobile and tell them your gps is non functional even after the froyo update, and get an exchange. My gps works INSTANTLY. Cold. I type my destination in Navigation and when I press enter my navigation is already talking. No maps, no 10 minutes, no downloads, we all know these are often placebos and we are still waiting and waiting for a signal which can still go off road randomly, etc. none of that with a new phone.
I did not try the physical gps fix in the forums but that could work too. Your gps still not be fixed by software, its a hardware problem. It seems phones manufactured after October (?) do not have the gps issue. Worth the hassle for me, at no cost if you do it for the gps issues and there is no physical damage to your phone. Just make sure you flash back to stock before you call because they will ask you to go through your system information on the line. Back up EVERYTHING and put it on a computer, get your exchange and flash back to your favorite rom and enjoy your now fully functional Vibrant that works in every way you bought it to work. And make sure you not only factory reset before you send the old one in, but also delete anything incriminating on your internal sd because a factory reset won't do it.
Sent from my SGH-T959 using XDA App
Don't blame the rom...Your hardware sucks.
Been running TW roms since the Bionix 1.0 days and NEVER had any issues.
Those problems are not inherent to TW roms, it's a problem with the phone.
@TheSneakerWhore, @deadpass:
OK - it might the hardware, but how do you explain no dropping calls on stock 2.1? I've used on stock for at least couple months and never had to reboot my phone because it did not have signals (or had signals but no connection).
I also flash Axura roms and never have a similar issue but they are too customized for me.
PS: I am not trying to blame the TW roms specifically nor am I defending another rom. Actually, if you open the latest Development thread, you will see my post thanking those guys because of an excellent job they've done. I am just not happy with the data and GPS - which I never had an issue before starting flashing TW and thinking others might be experiencing the same.
Strangely my GPS and cell signals seem stronger on TW ROMs than most others... It might be just slightly different hardware (not all units are created 100% equal after all) reacting differently to the software?
Have you perhaps tried Trigger v1.5? I thought the theming was very tasteful, you may like it, and it seemed pretty solid on GPS and signals.
Thanks, @Oxirane. I will give it a try.
I would try out different modems. For instance jl5 and kb1 great with gps in my case. jfd, ji6, ka5-7 all were teh suck when it came to gps. It all depends on your phone and location too. So flash away and find whats right for you.
http://forum.xda-developers.com/showthread.php?t=868774
I lol'd @ this "I live in an area (Maine) where you never experience a dropped call since there aren't many people living."
I'm with the OP on the drop call and inconsistent data issue. By all means, I have flashed almost every ROM out there. Every single ROM on here is awesome and all respects to the devs. I'm currently on Bionix 1.2 now for the third time and what I have and still noticed is the inconsistent data drop 2-3 times a day. No biggie since I managed to turn airplane off and back on and everything's back to normal. At first I thought it was KB1 that's causing this so I decided to try out different modems/kernals. After playing around a bit, I decided to stay with KA6 for a few days and noticed data improvement but still inconsistent (loss data connection). I also flashed the ROMs (Axura and Einherjar) and I don't have the data loss. I also flashed all the way back to Nero 5 just to check it out. I do not have any data problems with Nero 5. Anyways, I don't really mind every now and then switching air plane mode off/on. However, the issue as mentioned by OP does exist on some phones.
I'm running Bionix V 1.2, and the last 4 ROM's before this were all also TW ROMs.
I have not experienced a single one of your issues. My phone is fast, smooth, and have excellent signal and data everywhere around my area.
I doubt it is the ROM, but I'm no expert and cant say that for a definite.
But if myself along as many others , including a few buddies of mine, don't see those issues it just seems unlikely to be the ROM.
But who knows....
Well im guessing its the change of modems that's causing your issues... im sure it has nothing to do with the rom espeically since you never had issues supposedly when using Axura (since axura is based on bionix). Almost all the roms on here are based on TW roms, just change modems, theme, add a few random options, from what i've seen in the code. Like other suggested tryin flashing different modems and find the one that works best for your area. I've been running Bionix V 1.2 since day one and have not experienced any of the issues you have describbed...
2sh0rt said:
Well im guessing its the change of modems that's causing your issues... im sure it has nothing to do with the rom espeically since you never had issues supposedly when using Axura (since axura is based on bionix). Almost all the roms on here are based on TW roms, just change modems, theme, add a few random options, from what i've seen in the code. Like other suggested tryin flashing different modems and find the one that works best for your area. I've been running Bionix V 1.2 since day one and have not experienced any of the issues you have describbed...
Click to expand...
Click to collapse
I know your not trying to act up or anything, but thats kind of just mean.
I mean these devs are helping us by giving us more options.
Most of them aren't based on TW.
some are, most aren't.
but your saying "almost all the rom on here are based on TW Roms, just change modems, theme, add a few random options"
I'd like to see YOU edit the modem and theme and add a few random options and make a ROM. go ahead.
I can say that TW is also just editing a few codes and theming on a ROM that Samsung made, and that they aren't developers.
TW set a standard, a precedent, and people will follow it, but they aren't copying it.
not complaining at all to any ROMs. just throwing out my input to let the OP knows that he's not alone in this world. To me, if there's a way around the problem, the problem is minor. Besides, I flashed and used different ROMs like changing diapers. LOL. I like to keep my Vibrant looked different every 2-3 wks. Pretty soon, we'll see a flow of new ROMs and I be all over every single one of them like "flies on sh!t". Dang, haven't used that expression in a long time. LOL
xriderx66 said:
I know your not trying to act up or anything, but thats kind of just mean.
I mean these devs are helping us by giving us more options.
Most of them aren't based on TW.
some are, most aren't.
but your saying "almost all the rom on here are based on TW Roms, just change modems, theme, add a few random options"
I'd like to see YOU edit the modem and theme and add a few random options and make a ROM. go ahead.
I can say that TW is also just editing a few codes and theming on a ROM that Samsung made, and that they aren't developers.
TW set a standard, a precedent, and people will follow it, but they aren't copying it.
Click to expand...
Click to collapse
there is not "editing of modems" its changing modems... and theming is nothing more then changing pngs and .9s and edit xmls... its not very difficult... time consuming but not difficult. as far as what TW does to their roms in decompiling smalis and editing the Java, i've personally only seen a handful tru developers here actually doing it to what samsung has leaked. MOST of these so called roms have taken the edits that TW has done and just dropped their own changes on top of them. This has been proven time and time again! but regardless you are entitled to youre own opinions.
My point is that Axura IS based on TW's edit so if the issues persist in TW rom but not in Axura, one of the causes would most likely be due to the modem cuz im 99% sure that several Axura roms use different modems.... that is all i was trying to say.
One thing I have not seen in any of the posts that are having the issue is what modem you are using.
I will say it now, KB1 modem sucks monkey balls. I haven't had any dropped calls on it, but have stale connections all the time. What I mean by that is, my phone is sending data packets, but isn't receiving any for a good 30 seconds.
So, try a different modem. KA5 seems to be the best modem for signal and battery life.
krylon360 said:
One thing I have not seen in any of the posts that are having the issue is what modem you are using.
I will say it now, KB1 modem sucks monkey balls. I haven't had any dropped calls on it, but have stale connections all the time. What I mean by that is, my phone is sending data packets, but isn't receiving any for a good 30 seconds.
So, try a different modem. KA5 seems to be the best modem for signal and battery life.
Click to expand...
Click to collapse
THX Krylon360. To be perfectly honest, I tried different ROMs and modems and noticed some significant improvements. I totally agree that KA5 and KA6 are better for me in terms of signal hence KA6 is what I stick with as mentioned in my previous response.
surprisingly, these problems can come up from odd combos of apps or some configuration that is unique........ Lucky you
I had some phone disconnects on my phone when it was on a TW and Eugene kernel, but it was a custom mms I installed that caused the issue..... so you might look at what you got on your phone as well. Remember, some of the app developers did not or do not update their apps and this may cause an issue especially running a 2.2 platform (especially a ported 2.2 platform) if they are older apps. Food for thought
I was having the same issues with 1.2. dropped calls, no data, constantly switching from edge to 3g, etc. had no issues with nero. As everyone said, try a different modem. Worked for me.
Sent from my SGH-T959 using XDA App
Thanks everyone! krylon360, I should have mentioned the modem I've been using: KA5. So, it's weird how you and some others find KA5 and KA6 to work best and I had all these problems with it. Maybe it really is a unique combination of apps, configuration etc.
Last night I flashed KB1 and will give it a try for a few days. I tried GPS on my way to home; opened Navigation and entered directions, and I got instant lock. I see that as an improvement. Will follow closely. Thanks again!
Sent from my SGH-T959 using XDA App
There's nothing wrong with the roms i been flashing since i got my vibrant once flashing do you wait the initial 10 mins and then reboot before you start using your phone? if not you may want to try that. TW roms are pretty much flawless.
I have to change my signature (look below). Sprint just really impressed me. My phone, for reasons idk, dropped my mobile connection. I tried all the ## fixes to no avail. I called Sprint and the guy tried to walk me through it only to really mess my phone up, by the end of the conversation I couldn't even make calls, in fact somehow I had gotten a completely different phone number! It was a mess!
So by this time I was like screw it, I'm taking it in. I have a years worth of titanium back up's, countless nandroids, and pretty much every ROM under the sun on my SD card. I was so frustrated though, I told the guy I don't care if you kill my root and have to reflash factory, just fix my phone.
I came back an hour and a half later to pick up my phone. To my surprise the phone was not only fixed (mobile network reconnected, my phone number restored), but still was on Mik 2.60! The guy told me that when they fixed my phone, not only did they try to fix it, but did everything they could to maintain my root and not reflash the factory!
Big Up to Sprint.
That's pretty sweet, the store I go to has the same type of employees. Very helpful and do whatever they can without making me unroot.
We're comin from a pure power source.
Similar experience here, the employees were actually running Cyanogenmod and know what they were doing.
So for a while now I have not been able to update my PRL or Profile. It hasn't bothered me because for the most part the phone has worked fine until recently. A friend texted me and said he was going to call me. He text back a few minutes later and ask why I didnt answer. Phone was next to me the whole time and it didnt ring or so any kind of notification that he had tried to call. Took him 3 calls before my phone rang and he got through.
I have applied for a few jobs within the past few weeks and have heard nothing from anyone which I am surprised because I was referred to one company by and friend who put in a good word for me and said that his supervisors were really impressed with my resume. So now I feel like this issue could possibly be costing me job opportunities and I want to get it figured out.
The errors are 6602 and 407. I've tried to do it over 4G and put my phone just in CDMA mode for 3G only and get the 407 code for 3G and the 6602 over 4G.
I am running Stock rooted/odexed MK2 and I just did a clean flash of the rom again clearing data/cache and dalvik seeing if that would help which it didn't. I have reflashed the modem seperately also with no help.
I have seen many threads of others having this issue but no answers on a fix. Has anyone experienced this and actually done something that has resolved the issue?
If you feel it may be costing you a job, why not flash a nand of a stock rom, assuming you have one
Sent from my SPH-L720 using XDA Free mobile app
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
tenaciousj said:
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
Click to expand...
Click to collapse
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
rsngfrce said:
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
Click to expand...
Click to collapse
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
tenaciousj said:
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
Click to expand...
Click to collapse
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
rsngfrce said:
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
Click to expand...
Click to collapse
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
rsngfrce said:
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
Click to expand...
Click to collapse
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
rsngfrce said:
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
Click to expand...
Click to collapse
Bootloader and software version both show up as NG2 on Device Info.
tenaciousj said:
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Click to expand...
Click to collapse
I'm not an EXPERT on this subject, but if you are on NG2 stock unrooted right now, I believe you can use: CF-Auto-Root to root it. Or, here is a stock rooted version of the NG2 ROM:
[ROM][NG2] Stock Rooted NG2 (which mentions that it has Knox removed).
As far as tripping stuff, I'm somewhat unsure about that to be honest. I have always used Triangle Away on my phone, but it has a warning now not to use it with a custom kernel (which I use). My counter is at 3, but I am out of warranty anyway.
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
rsngfrce said:
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
Click to expand...
Click to collapse
I got the phone I have now about a month after the GS4 came out so its non sparks. I stayed on MK2 for so long because I couldn't find a newer rom that looked to be stable and not have to jump through a bunch of hoops to install it. The Odin screen shows everything being zero and offical software so I should be good. I am going to sign out of all of my accounts before I bring it in being I have a lot of apps bought through the store that only work on rooted phones. I hope I can get a tri band to replace it. My friend has a triband GS4 and it gets much better data speeds than mine.
Yeah, I mentioned elsewhere here before that I actually didn't know of the existence of the "Sparks" version of the G4. I screwed up the USB port on my G4 before upgrade time, so I had to buy another G4 on Amazon. Upgrade time has come up, so I was just looking and saw my phone listed as "Non-Sprint Sparks", which I thought meant that they called it the "Sparks" model because I hadn't bought it from Sprint... took me a while to figure out what that actually meant... :laugh:
Sprint online nor the store could fix it so I got a new one.
No rooting but error 407
As titled, I've not rooted the phone. I'm getting error code 407 on attempts to update PRL and Update profile. Download updates manually does nothing. Note I'm on a Samsung Note 4, Sprint. Had updated to Marshmallow 6.0.1 late March but then above actions persist since then. I'm using Wi-Fi only, Sprint service disconnected as I couldn't pay bill when I lost job during a disabling illness.
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
00Lee said:
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
Click to expand...
Click to collapse
Have you done a factory reset via recovery? Or you might want to flash latest full stock
Im a long time reader first time poster... i first want to thank everyone here for finding the time and patience to help others by sharing your knowledge ideas and expertise, This is by far the best resource for trustworthy information for Android on the Web. I've been able to help my loved ones and myself by using information i found here through the years and so for that I sincerely thank all of you.
Now onto the issue at hand. .
I have a cricket wireless Samsung sgh-i337z 4.4.2 i337ztuuboa3 I first
Soft rooted with kingoroot, but later i was able to full root using towel root.
No issues until about maybe a month ago when messages i was sending sometimes wouldn't go through until 3 or 4 tries. Its getting progressively worse, to where now have trouble sending emails occasionally also. Keeping the messaging cache cleared is the only way I've found to send them, still not until the 2nd or 3rd or 4th try. . Installed a different messaging app, same thing. It's not a weak signal thing, I've deleted all unneeded stored messages, and I'm not sure what to do next. it's starting to make me crazy. I send a text it goes thru, send another then go about my business, wonder why I never got a response till I pick up my phone an hour later and see that damn failed notification again. It's maddening i tell you! Could it be a network problem because I haven't updated past kitkat? Or is there something else I'm not seeing? I wanted to ask before jumping in trying to update to lollipop, as I am still unable to connect and use adb and I'm guessing updating and keeping root probably won't be like a click 1 and done thing on top of it also wiping my phone, seems like fun all around. I'm open to any feedback and appreciate any help/ advice given....
Thanks so much for all you do and I hope you have a great day!
Well mate, I don't think its a problem to do with you not being on Kitkat, but have you considered factory resetting or talking to your carrier?
I had that problem regularly on my i337 running Hyperdrive RLS 19 which was Android KitKat 4.4.2 but created from a ROM that was originally on Verizon's CDMA network. I found that when I was on Wi-Fi, most of the time my MMS would send about 50% of the time and regular texts would send about 90% of the time. When I shut off wi-fi and used AT&T's network exclusively they sent with a much greater reliability, MMS closer to 90% and normal texts around 100%. My guess is that, since Cricket is switching to AT&T's GSM infrastructure from years of being on a CDMA (Verizon) there is some issue in the hand-off from a CDMA rom that doesn't translate right to the GSM network. What that might be, I couldn't say because I just don't have the background or knowledge (and good luck explaining that to a Cricket rep), but I think I'm right as the the cause at least. That being said, if there is a newer ROM that can be flashed on your phone, or even the same one over with the modems, I'd do it to see if it would fix the issue. I finally flashed my i337 to a stock GSM ROM and it resolved the problem.
So I've had my OP6T for several months now and I've really enjoyed it and been impressed with it.
For the majority of the time I've used AEX as my custom rom. I always pick a rom with signature spoofing support so I can use microg. Also, my service provider is Verizon.
I finally decided after several months with AEX as my daily driver, I wanted a rom that is more up to date but I'm not really ready to update from 9 to 10. So I decided to flash The Skydragon rom. I flashed it super easy but could not make calls nor send texts. The entire time I used AEX, it made calls and sent SMS/MMS just fine. After I installed Skydragon I called Verizon and spent 2 hours on the phone with various tech specialists and in the end they said from their end everything looked like it should be working. They never got it making calls and sending/receiving texts.
It said out of service in the settings. I ended up switching back to AEX and as soon as I did, it began working properly again. I even tried to make calls and texts on my OP6T when it was 100% stock and it will not work
I wonder if it's because I was on AEX when I originally called Verizon last year and set it up? Am I correct in assuming that, each time I flash a different rom, my phone will appear to Verizon as a brand new phone? I couldn't get it to work on stock nor Skydragon but when I switch back to AEX it works as it's supposed to.
TRexombo said:
AEX it works as it's supposed to.
Click to expand...
Click to collapse
When you tried the other ROMs, were they unmodified?
OP6T works only with Verizon's LTE network, from what I saw online.
It may matter if your phone is international/unbranded, etc., and if the ROMs are for the appropriate version of phone.
pbergonzi said:
When you tried the other ROMs, were they unmodified?
OP6T works only with Verizon's LTE network, from what I saw online.
It may matter if your phone is international/unbranded, etc., and if the ROMs are for the appropriate version of phone.
Click to expand...
Click to collapse
My phone is international/unbranded. I'm not sure if the Roms were unmodified. I know AEX works and when I tried Skydragon I worked on it for close to 2 days trying to make it work. One of the options within the Skydragon settings was that I can choose the exact network to use. I chose LTE. After choosing LTE, in the settings it shows my phone number and my provider as Verizon but it says out of service under service state. The Verizon representatives told me on their end it shows that I am CDMAless and they did not have a solution.
I noticed in the Skydragon thread that some people were successful in getting their OP6T to work with Verizon but at least one other XDA member said he had no service.
Also, as I was in the process of switching back to AEX, I first went back to stock and booted up in stock and tried to make calls /send texts and it would not allow me to until I reflashed AEX.
What a nuisance. Since you're so familiar with flashing ROMs, maybe try some others, but I would first go back to stock again--completely back to stock, even if it means lowering your android version.
But follow the instructions very carefully--you may be in brick territory going back. I'd download the MSMTool just in case.
Good luck with whatever you do, if you don't stay on AEX.