Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.
Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?
lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...
The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...
I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.
BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...
I wonder if it found one of those radios and did something with it?
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.
lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.
I want to send a HUGE thanks to all the developers and users on the site. I have had nothing but problems over the past week, with my EVO being stuck in some inbetween root and unroot world... I couldn't load the PC36IMG file to re-root, I couldn't get toasts part 2 running to run so i could get those files to run, couldn't get files to flash that needed flashing, etc.... I was stuck only able to use one or 2 different roms, which, while allowing me to have a phone, frustrated me to no end, knowing that it wasn't right. Through piecing bits of info I read in various different threads, i was finally able to do everything that I needed to do to get back to a good rooted state. I can now run any Rom, and have control over my phone again. I am starting to understand ADB a little better, and am no longer intimidated by it.
Only problem I still am having, is the 4g issue... I had a bad Mac address, which I was finally able to run the fix (I couldn't get in before because of the state of the phone), but I still get the (Turning on, scanning, connecting to sprint, turning off, repeat). I know it is only a matter of time till that gets fixed as well.
I decided to thank everyone in a single thread, because it was no one persons help or advice that helped me get through this. It was a collective effort by everyone. I don't want to even TRY to thank individuals, for fear of leaving someone out.
Thanks again....
I was having the 4g issue.. i just reverted back to the DC ROM 3.1.2.. works like a charm for me. I'll wait until the stable Froyo ROMs before i upgrade again.
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.
Hello,
Im having a most frustrating problem. Im not sure if its a modem issue or a hardware issue. What I am experiencing is this:
The phone shows no bars, but sees a carrier. This happened after flashing back to a stock GB rom after using a CM9 rom. I can receive texts and calls sometimes, but its not consistant. If it shows no bars I can get a call, if it shows one or two bars i cant, but get the missed call notification. I have done factory resets, cache clears. Its really making my phone unusable. I went back to using my 3 yr old Ericsson till I can get this figured out. Im hoping that someone has some advice for me as Im out of ideas. Ive tried to flash just the modem but no luck. Went from CyanTablet to xxjvt 2.3.5, rooted it so I could get the modded recovery. The pins for the where the sim card make contact are damaged but it has worked for the last 2 months that way. I really love this phone and dont want to replace it yet.
rivman05 said:
I really love this phone and dont want to replace it yet.
Click to expand...
Click to collapse
test with a network booster to increase signal strength, free from google but if you bring phone to another location, do you get a better signal? meaning location matters, if you far from your network cell site, its more difficult
Ill try the network booster. All of my old phones pick up 5 bars, I live about 1/4 mile from the cell tower. I have tried another flash with 2.3.3, repartitioned this time. Once its back up and running Ill get back to you. Is there anything else Im missing? Well I think its dead. Ive tried all my coworkers sims in it, nothing came up. It says no service permanently now, guess its a 4" tablet.
Try another radio, i had the same problem wit JW4 radio,flashed JVT and problem solved.
Some radios are better than others in different locations, it also depends on rom used.
I tried a completely new build, flashed a new modem, then flashed xxjvu. Still nothing, going to call Samsung and see if I can get the warranty to fix it. 2.3.6 tho has 364 megs of ram and has almost 200 free, thats cool. zsjw4 has a new look to it.
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