can someone with a stock vibrant tell me if you were able to apply the update smoothly. either ota or odin.
and no rooting required please, there are lots of ways there but I can't see anyone posting for a stock phone and not rooted.
Yes, I was able to right now. (10:17pm PDT)
Stock, no root, no titanium backup, no roms. Worked perfect. From reading some of the threads reporting problems, 90% sounds like a specific combination of the above 3 things is what is causing issues.
Charged the battery to 100% before i did it.
OTA (was connected to home wifi when i clicked on the updated notification). Don't know if it used the wifi connection or switched over to 3g to download the update ...
Clicked on update. It said it was going to reboot phone, and rebooted.
Then it started download/install. Took about 5 minutes to download and install. It sat at 50% for a little bit longer than the other %'s. Also sat at 85% for a minute or so. Then it booted up. "Vibrant" screen displayed for about a minute. Then the GalaxyS screen displayed for about a minute or 2, then phone booted like normal.
Everything seems okay.
Stock vibrant (non rooted) should be fine. Its what the update was made for.
anthonys2r said:
Stock vibrant (non rooted) should be fine. Its what the update was made for.
Click to expand...
Click to collapse
I read in the t-mobile forums that most of them are running stock phones, but they weren't able to update their phones.
what do you mean by 'weren't able'? a majority of the people still have not received the t-mobile notification (me included). is that what you meant?
no. sorry i guess i didn't put much details to what i have said. some of them already received the notification from t-mobile. but they weren't successful with the processing of the updates on their phone. and i read that they are running stock vibrants.
i tried to update via odin, but i can't go to download mode. seems that i just have to use a stock vibrant.
First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.
I wasn't so luckly. I undid my lag fix and un rooted and still soft bricked mine and had to use odin to get it back
how long
HumanTarget said:
First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.
Click to expand...
Click to collapse
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...
jblade1000 said:
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...
Click to expand...
Click to collapse
took about 3-6 minutes for me.
I got very worried... but was patient.
Stock ROM
Rooted
All bloatware removed.
wasted mine with no lag fix rooted on stock kernel, stock build..had to odin back and update via odin...****ty
well damn, im kinda at a loss then about whether to go through with this. I want the update but I dont have the time to be messing with flashing and odin right now...
Weirdddddddd
I to bricked my phone with the ota. I was rooted, stock rom, lagfix with clockwork. I undid the lagfix but still bricked. My boy's running the same without clockwork (never had time to put it on). Unrooted, delaged and removed the update.zip that was on the phone from root and cleared the cache. Ota worked without a problem. Some believe it is the result of an update.zip left on the sd which causes the problem.
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.