Getting late notifications after KK - Sprint Samsung Galaxy S III

I installed the OTA 4.4.2 stock rom from the forums and ever since my notifications come sometimes hours later. I don't have cell service and haven't for awhile. I leave the phone on airplane mode but with wifi turned on. It's the same way I used it under Jellybean. However now I have to often open up Hangouts and Google Voice to check manually for messages. If I don't I'll sometimes get notifications of new messages 1 to 6 hours after the message was sent.
Even opening up the app and checking sometimes won't force me to get new messages. If I hit the refresh button on Google voice about 3 times then sometimes it'll force it to finally receive the message.
Wifi works fine though, I can surf the web, stream music, watch youtube, update apps perfectly. Never have a hiccup or stutter and never had this issue until I updated to KK. Before I flashed KK, I did a backup of my apps with Helium and restored them. I wondered if that could be the problem. Not sure why it would effect the messages I receive on Hangouts or Google Voice and nothing else though.
This is the rom and procedure I used, going from stock 4.3 rooted to KK.
http://forum.xda-developers.com/showthread.php?t=2738533

Just to be 100% sure nothing else is causing weird issues, I would backup everything from your internal storage and external SD card, reformat your SD card, Odin the stock ND8 tar and the latest Philz Touch Recovery, then try to reproduce your problem.
If you can't reproduce it, root the phone (Philz Touch Recovery / Settings /Re-Root), then breakup the apps with data you restore into half. Restore only that half and try to reproduce the problem. Each time the problem doesn't occur, do a nandroid backup and restore another half of what's not restored yet. Once you can reproduce the problem, you'll have narrowed it down.
Once you can reproduce the problem, restore the last nandroid and restore half of what you had previously tried, etc. Keep going until you narrow the problem down to one, or narrow it down enough to make an educated guess from what's left and try just that one and verify that it's the issue.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

roirraW "edor" ehT said:
Just to be 100% sure nothing else is causing weird issues, I would backup everything from your internal storage and external SD card, reformat your SD card, Odin the stock ND8 tar and the latest Philz Touch Recovery, then try to reproduce your problem.
If you can't reproduce it, root the phone (Philz Touch Recovery / Settings /Re-Root), then breakup the apps with data you restore into half. Restore only that half and try to reproduce the problem. Each time the problem doesn't occur, do a nandroid backup and restore another half of what's not restored yet. Once you can reproduce the problem, you'll have narrowed it down.
Once you can reproduce the problem, restore the last nandroid and restore half of what you had previously tried, etc. Keep going until you narrow the problem down to one, or narrow it down enough to make an educated guess from what's left and try just that one and verify that it's the issue.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Thanks for the reply, I thought I had notifications setup for this thread, but I guess not. Anyways in the past 4 days I've flashed 2 different KK roms and still having the same issue. I've used Philz wipe and install option both times. I used a stock rooted rom first, and after a day of using it I still am not getting my notifications for Hangouts. I used another custom KK rom from the forum and flashed it as well using Philz wipe and install.
I've left the roms stock on both installs, except for signing into my Google account and letting the apps update. I'll send myself test messages and wait sometimes even an hour and not get any notification until I manually open the app and even then sometimes I cannot get it to load the message. Yet the internet connection is working and I can check email and browse websites without issue. The only way I can get it to load up any new messages is to reboot.
I want to try going back to Jellybean just to see if I'll have the same issue. Now that I've gone to KK though, is it possible for me to downgrade back to Jellybean? I know I've seen threads in the past saying downgrading will brick the device.

You can flash any ROM made for our SPH-L710 that you want without bricking. You just can't ever Odin anything older than ND8 or NDC.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Related

S3 crashes after lockingn screen for longer than 5 seconds.

I recently sent in my S3 for repairs via samsung because my usb port had gone bad. The usb port issue has been solved but now, roughly 1 hour into any factory reset i preform, the phone will lock up/crash when i lock the phone for any longer than 5 seconds. PLEASE help!
I just want to make sure I understand. Are you factory resetting from the stock recovery or a custom recovery?
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
roirraW "edor" ehT said:
I just want to make sure I understand. Are you factory resetting from the stock recovery or a custom recovery?
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
everything is stock; ive recently had to send this in for repairs and this is all happening right out of the box since ive gotten it back. was hoping i could fix this on my own rather than having to be without my phone for another 2 weeks.
doodlebird said:
everything is stock; ive recently had to send this in for repairs and this is all happening right out of the box since ive gotten it back. was hoping i could fix this on my own rather than having to be without my phone for another 2 weeks.
Click to expand...
Click to collapse
What version of stock TouchWiz is on your phone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
it's nd8 all the way. i've also tried different nd8 roms, different recoveries, different launchers etc etc etc. i can't seem to replicate the crashes from any one action but one thing that is consistent seems to be that if i reload the ROM onto the phone, the crashes go away for roughly an hour. after a while though it will randomly start doing it again. i've even reloaded the rom and let my phone just sit there completely fresh from being reset while occasionally locking/unlocking the phone to see if it has crashed, just for the phone to eventually give way to crashing every time i lock it after roughly an hour of use. the phone is not getting overheated either.
doodlebird said:
it's nd8 all the way. i've also tried different nd8 roms, different recoveries, different launchers etc etc etc. i can't seem to replicate the crashes from any one action but one thing that is consistent seems to be that if i reload the ROM onto the phone, the crashes go away for roughly an hour. after a while though it will randomly start doing it again. i've even reloaded the rom and let my phone just sit there completely fresh from being reset while occasionally locking/unlocking the phone to see if it has crashed, just for the phone to eventually give way to crashing every time i lock it after roughly an hour of use. the phone is not getting overheated either.
Click to expand...
Click to collapse
Argh. I sympathize with what must be very frustrating. I hate it when stuff like that happens and I know it doesn't help but at least it's consistent. I take it that the Knox counter has been tripped (go into Download mode and check the line that says Warranty = ??) and that you wouldn't be able to send it in for repairs again because of it? It seems they either missed or caused a second problem with your phone when they fixed the first.
roirraW "edor" ehT said:
Argh. I sympathize with what must be very frustrating. I hate it when stuff like that happens and I know it doesn't help but at least it's consistent. I take it that the Knox counter has been tripped (go into Download mode and check the line that says Warranty = ??) and that you wouldn't be able to send it in for repairs again because of it? It seems they either missed or caused a second problem with your phone when they fixed the first.
Click to expand...
Click to collapse
mine says warranty bit: 1, is that mean it has been tripped?
doodlebird said:
mine says warranty bit: 1, is that mean it has been tripped?
Click to expand...
Click to collapse
Yes, it's tripped and there's absolutely no way to un-trip it, so Samsung wouldn't repair it under warranty unless you just get lucky.
It got tripped when you put a custom recovery on.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

[Q] Time to update ROM with Knox bit tripped, how to avoid a brick

So back in December while updating to the newest version of MOAR, I made this mistake of taking the OTA update and getting Knox. I managed not to brick my phone at the time, but ended up with the Knox bit tripped and a lot of concern that further experimenting would result in a dead phone and a forced replacement. Anyway, fast forward to now and its time to update again (some apps are starting to get unstable because they have been updated but my ROM hasn't), but I want to make sure I don't risk bricking the phone thanks to Knox.
If I remember correctly, the fact that I'd contracted Knox and tripped the bit already meant that I was stuck with the same bootloader, but I could update everything else. Is this still the case, or has someone figured a way around the issue in the past six months so that I can get rid of Knox once and for all? Also, since I haven't looked at any of this in the last 7 months, what exactly would the process be to update to the newest version of MOAR without updating the bootloader (if that's still what needs to happen)?
Thanks
You can downgrade everything but bootloader and modem. You can upgrade everything.
Flashing custom ROMs don't include bootloaders or modems, so have no fear. Only Odining the stock ROM, taking an OTA, or specifically finding a way to flash those upgrade them.
Just flash the latest MOAR or whatever other ROM you want to, as always.
The only exception to this is to flash ND8 (TouchWiz 4.4.2) based ROMs you need to have taken the ND8 OTA or Odined the stock ND8 tar first, otherwise you may brick your phone.
You're welcome!
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
roirraW "edor" ehT said:
You can downgrade everything but bootloader and modem. You can upgrade everything.
Flashing custom ROMs don't include bootloaders or modems, so have no fear. Only Odining the stock ROM, taking an OTA, or specifically finding a way to flash those upgrade them.
Just flash the latest MOAR or whatever other ROM you want to, as always.
The only exception to this is to flash ND8 (TouchWiz 4.4.2) based ROMs you need to have taken the ND8 OTA or Odined the stock ND8 tar first, otherwise you may brick your phone.
You're welcome!
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Ok, with all of that said, the ND8 is an upgrade, so if I Odin it in, I should still be fine? I really hate that this is even an issue... I am thinking of jumping ship from the company's products when I upgrade next specifically as a result of this
treblesum81 said:
Ok, with all of that said, the ND8 is an upgrade, so if I Odin it in, I should still be fine? I really hate that this is even an issue... I am thinking of jumping ship from the company's products when I upgrade next specifically as a result of this
Click to expand...
Click to collapse
Yes, you can upgrade everything.
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
treblesum81 said:
Ok, with all of that said, the ND8 is an upgrade, so if I Odin it in, I should still be fine? I really hate that this is even an issue... I am thinking of jumping ship from the company's products when I upgrade next specifically as a result of this
Click to expand...
Click to collapse
The only valid arguments against Knox (IMHO) are:
1. Once the warranty counter is tripped there is no way to reset it.
2. You do not have the ability to downgrade modems/bootloaders.
Myself, rode warrior and many others have had no issues directly related to Knox....
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
The only valid arguments against Knox (IMHO) are:
1. Once the warranty counter is tripped there is no way to reset it.
2. You do not have the ability to downgrade modems/bootloaders.
Myself, rode warrior and many others have had no issues directly related to Knox....
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
The problem is the way in which those issues manifested. Samsung essentially slipped Knox into the update almost without warning and with virtually no documentation. As a result many of those who were affected found out about it as a result of a bricked phone which was now permanently marked as ineligible for warranty work. Had Samsung made it clear what Knox was capable of and provided proper documentation of its function then I don't think many people would have had any problems with it.
Sent from my SPH-L710 using XDA Free mobile app

[Q] Status of freedom to install ROMs?

I'm considering picking up a S3 off eBay, since they seem to be rather cheap nowadays ( under $100), and was thinking of it as an upgrade from my Galaxy Nexus.
I've seen people with Verizon S3s and S4s get stuck after updating so they couldn't install any ROMs anymore.
Of course I haven't really heard much about the Sprint phones being locked down so much, but could anyone tell me if (even with the newest update) if you can install CWM and CyanogenMod?
Thanks
GTRsdk said:
I'm considering picking up a S3 off eBay, since they seem to be rather cheap nowadays ( under $100), and was thinking of it as an upgrade from my Galaxy Nexus.
I've seen people with Verizon S3s and S4s get stuck after updating so they couldn't install any ROMs anymore.
Of course I haven't really heard much about the Sprint phones being locked down so much, but could anyone tell me if (even with the newest update) if you can install CWM and CyanogenMod?
Thanks
Click to expand...
Click to collapse
it would be better to install Philz Touch CWM advanced recovery from Odin and you can back up your stock rom when in the recovery then do the second option under wipe data to wipe everything but first make sure you have the Touchwiz rom and or AOSP rom + Gapps to flash in your internal storage then wipe cache and dalvik cache and your done so yes you can still install a custom recovery and custom rom like CyanogenMod
6th_Hokage said:
it would be better to install Philz Touch CWM advanced recovery from Odin and you can back up your stock rom when in the recovery then do the second option under wipe data to wipe everything but first make sure you have the Touchwiz rom and or AOSP rom + Gapps to flash in your internal storage then wipe cache and dalvik cache and your done so yes you can still install a custom recovery and custom rom like CyanogenMod
Click to expand...
Click to collapse
I don't think you read through my whole post, since I wasn't asking how to do it, since I'm already familiar with Heimdall flashing (have been flashing on early Verizon S3/S4, before updates blocked it).
But the big question is... If you were to go to 100% stock (or a 100% stock phone to begin with), and have the newest updates applied(I think it is 4.3 or 4.4), you can still flash stuff, and not have it brick, right?
I know if I were to try the same on a Verizon S3, it would almost certainly brick.
GTRsdk said:
I don't think you read through my whole post, since I wasn't asking how to do it, since I'm already familiar with Heimdall flashing (have been flashing on early Verizon S3/S4, before updates blocked it).
But the big question is... If you were to go to 100% stock (or a 100% stock phone to begin with), and have the newest updates applied(I think it is 4.3 or 4.4), you can still flash stuff, and not have it brick, right?
I know if I were to try the same on a Verizon S3, it would almost certainly brick.
Click to expand...
Click to collapse
but i did read through it i just answered the last part about CWM and CyanogenMod since that's what i know for sure
but you see for the rest of your words i have flashed on full stock 4.4.2 NDC since mine is the Boost variant with root and philz touch recovery....but only stuff made for touchwiz like the S5 ported apps just the worst i got after flashing is constant force closing of one or more apps for then i would have to boot back into recovery with the button method and flash a backup but i have done so and my s3 started with 4.4.2 stock update for the sprint variant even tho its the same model number i would wait to see if anyone else with it chimes in....but since it is the same basic model everything basically works the same way for them
Yes, you can still flash whatever you want besides modem. You just can't ever Odin anything older than ND8 (Sprint TouchWiz 4.4.2) or NDC (Boost / Virgin Mobile TouchWiz 4.4.2).
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v4.4, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Network Unavailable ND8

Hi all, I flashed the stock tar via ODIN then Philz recovery, everything loads and installs fine it seems. My wifi works as well as everything else however, I have not had any cell phone service at all. when I go to setting->self activate it says network unavailable. I've tried to do a reset and all to get the phone to turn on the network but I am not sure what it blocking my phone from gaining any type of network access. I'm not sure where to go from here, the Stock ROM unrooted as well as Custom ROMs have provided the same no service results. I hope someone is able to help me I know I didn't provide a lot of information but I've followed all of the ND8 and Restore guides that I could find down to every last detail and cannot seem to get this to work, After 5 days of trying I feel it is worth asking you all seperately because any searchs have only shown users with both wifi and network connectivity problems.
Thank you all so much!
Kennan Miller
Sprint, Boost or Virgin Mobile? Did you check the MD5 hash of the zip or tar? Did you try the Odin multiple times and without changing anything, not even custom recovery? By reset you mean ##72786# from the stock dialer? After the reset did you try update profile and PRL? Try the NDC tar instead of ND8, especially if you're on Boost or Virgin Mobile.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
I havent tried the reset with the numbers, i kept looking for the code and could not find the proper one for my carrier, but that is the sprint one. I have a Sprint phone, I'll do some searching on what the NDC is, I have not heard of that before.
Edit: yes, I checked the md5 before anything i flashes through odin or recovery etc. . i've done the update for PRL and profile
Thank you for the response! Kennan
kcmiller82 said:
I havent tried the reset with the numbers, i kept looking for the code and could not find the proper one for my carrier, but that is the sprint one. I have a Sprint phone, I'll do some searching on what the NDC is, I have not heard of that before.
Edit: yes, I checked the md5 before anything i flashes through odin or recovery etc. . i've done the update for PRL and profile
Thank you for the response! Kennan
Click to expand...
Click to collapse
You're welcome! Try the data reset first. After that it's normal to do an update PRL and Profile. NDC is TouchWiz 4.4.2 for Boost and Virgin Mobile, ND8 is the same for Sprint, which should be what you Odined.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Hey! I'm sorry it took so long to respond back , I don't live in an area where I have service I had to drive into town so I could test it out! The code worked and I received service! however, I did not have any data/3g . I'm fairly confident when I have been to that town previously I had 3G, Does anyone have recommendations for that issue if it doesn't come back? sorry for seeming so needy, I would just like a few things to possibly try because unfortunately I have to make a trip into town everytime I need to see if I have service
Thank you all so much!!
Kennan
You didn't mention if you updated your PRL and Profile after the data reset. Try that if you didn't.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

[Q] Can't receive sms after flashing stock

Hello everyone,
So ill start out telling you my long journey through the numerous roms I've flashed.
First flashed cm11 4.4.2, then to 4.4.3. Nothing out of the ordinary.
Next flashed liquid smooth 4.4.4, nothing else was wrong until I noticed my calls took
a while to connect. Then I got multiple and duplicate sms messages all at once that were usually late.
So I tried to restore my first cm11 backup, then I started to lose all texting ability. So I tried to revert back to
stock and unroot. Success
Now everything works fine (calls, data, sending sms etc.) But I still can't receive any text messages.
I am running the stock 4.4.2 Rom from Seminole with no root access. I've contacted sprint and gone
through all of those hoops to no avail. Is there a way to fix this? I would greatly appreciate any help..
Thanks
derder764 said:
Hello everyone,
So ill start out telling you my long journey through the numerous roms I've flashed.
First flashed cm11 4.4.2, then to 4.4.3. Nothing out of the ordinary.
Next flashed liquid smooth 4.4.4, nothing else was wrong until I noticed my calls took
a while to connect. Then I got multiple and duplicate sms messages all at once that were usually late.
So I tried to restore my first cm11 backup, then I started to lose all texting ability. So I tried to revert back to
stock and unroot. Success
Now everything works fine (calls, data, sending sms etc.) But I still can't receive any text messages.
I am running the stock 4.4.2 Rom from Seminole with no root access. I've contacted sprint and gone
through all of those hoops to no avail. Is there a way to fix this? I would greatly appreciate any help..
Thanks
Click to expand...
Click to collapse
did you flash the ND8 stock tar via Odin??
6th_Hokage said:
did you flash the ND8 stock tar via Odin??
Click to expand...
Click to collapse
I flashed the stick 4.4.2 from the Sam mobile site for the sph-l710. Ill see
how the nd 8 does.
6th_Hokage said:
did you flash the ND8 stock tar via Odin??
Click to expand...
Click to collapse
I flashed nd8 and the problem still persists. The thing is when I swapped phones with somone else on my plan I could text and I was able to get rel lies. Then I put my number back on the galaxy s3 and AGAIN no replies..
Any idea?
I don't know if this would help this particular problem, but did you try on a stock ROM in the stock dialer:
##72786#
Then when it finishes, update PRL and Profile from Settings / More /About Device
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
roirraW "edor" ehT said:
I don't know if this would help this particular problem, but did you try on a stock ROM in the stock dialer:
##72786#
Then when it finishes, update PRL and Profile from Settings / More /About Device
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Thanks, I did that a couple times with sprint. Each time I ask for help they transfer me to another tech...
Ill try again though. Is it possible that flashing one of my previous roms caused the Id on my phone to change?

Categories

Resources