Related
Quick question,
I'm rooted w/latest Starburst and ICS theme, and I accidentally allowed the most recent Sprint system update to go forward (12/12/2011 @ 8am [EST]). I did so without asking (here) if this was safe. So is it? I searched other threads and it appears that some recommend going back to stock prior to updating, while other swear that "re-stocking" is unnecessary.
So far (after 10 mins) I still have an exclamation mark triangle with a blue andriod guy. Not sure if this is normal. Thanks!
-Aaron
Aairman23 said:
Quick question,
I'm rooted w/latest Starburst and ICS theme, and I accidentally allowed the most recent Sprint system update to go forward (12/12/2011 @ 8am [EST]). I did so without asking (here) if this was safe. So is it? I searched other threads and it appears that some recommend going back to stock prior to updating, while other swear that "re-stocking" is unnecessary.
So far (after 10 mins) I still have an exclamation mark triangle with a blue andriod guy. Not sure if this is normal. Thanks!
-Aaron
Click to expand...
Click to collapse
If you aren't on the "factory" ODIN odexed ROM with EG30 modem, the update will fail. The update from Sprint relies on the system files being in a particular condition and the update will fail if they are not in that condition.
I have heard that some people have perfectly working phones after rebooting (but not updated). If you want EK02 ROMs, they're available in the development sub-forum and would be easier to manage than returning to stock and accepting this update.
EDIT: You may need to pull the battery to get out of the update. Supposedly once you put the battery in, you'll get to CWM, and then should be able to boot back into Starburst. I haven't done this, so I can't confirm.
Go back to stock.
The update will fail.
Why not flash the update from here? Android 2.3.6 + root is in the development section.
Sources? Personal experience.
Sent from the future.
nivron said:
If you aren't on the "factory" ODIN odexed ROM with EG30 modem, the update will fail. The update from Sprint relies on the system files being in a particular condition and the update will fail if they are not in that condition.
I have heard that some people have perfectly working phones after rebooting (but not updated). If you want EK02 ROMs, they're available in the development sub-forum and would be easier to manage than returning to stock and accepting this update.
EDIT: You may need to pull the battery to get out of the update. Supposedly once you put the battery in, you'll get to CWM, and then should be able to boot back into Starburst. I haven't done this, so I can't confirm.
Click to expand...
Click to collapse
You are correct, I pulled battery, was directed to CWM and rebooted system...all is fine (as it was before).
I saw QBKINGs videos on updating the Modem, but am not sure I want to go through with that until i figure out if the update is worth it. I am still not sure if this was an android version update, or an update that fixes LOS...or both. If I see a majority of members recommending this update, then I guess I'll jump through the hoops.
I tend to not have very much luck with tinkering with my phone. Something always goes wrong and then I loose 2 hrs of my day trying to figure out how to fix it. but I guess that's the name of the game...
SocialReject said:
Go back to stock.
The update will fail.
Why not flash the update from here? Android 2.3.6 + root is in the development section.
Sources? Personal experience.
Sent from the future.
Click to expand...
Click to collapse
I'll check this out.
I know I SHOULD know this, but... what would the process be for getting 2.3.6+ root along with starburst Rom. Would I flash the above recommendation then flash starburst over it, then load my ICS them last?
P.S. please forgive my incorrect use of the technical terms flash and load. As you can see from my questions, I only have a cursory understanding how rooting/flashing/loading.....just enough to get my phone to the customized state that it is currently in.
If it ain't broke.... that's my motto and if you are not savvy with the phone I definitely suggest you leave your setup alone. Using Odin has got to be one of the easiest things to do though but once again if it ain't broke....
Aairman23 said:
I'll check this out.
I know I SHOULD know this, but... what would the process be for getting 2.3.6+ root along with starburst Rom. Would I flash the above recommendation then flash starburst over it, then load my ICS them last?
P.S. please forgive my incorrect use of the technical terms flash and load. As you can see from my questions, I only have a cursory understanding how rooting/flashing/loading.....just enough to get my phone to the customized state that it is currently in.
Click to expand...
Click to collapse
Wasn't aware you were hoping to continue using starburst. I don't think starburst supports EK02 yet.
Sent from the future.
SocialReject said:
Wasn't aware you were hoping to continue using starburst. I don't think starburst supports EK02 yet.
Sent from the future.
Click to expand...
Click to collapse
That was all I really needed to know...I am very happy with starburst... thank you!
Edit: last question For some reason I have a little "arrow loop" or "arrows in a circle" (in grey) in the middle of my top menu bar, and it is partially blocking the time. Did I induce this somehow, how do I make it go away (reboot didn't work)?
playya said:
If it ain't broke.... that's my motto and if you are not savvy with the phone I definitely suggest you leave your setup alone. Using Odin has got to be one of the easiest things to do though but once again if it ain't broke....
Click to expand...
Click to collapse
Indeed. You wouldn't believe how many people make one tiny mistake in Odin and BAM it's all over.
Sent from the future.
Aairman23 said:
That was all I really needed to know...I am very happy with starburst... thank you!
Click to expand...
Click to collapse
No problem
Sent from the future.
Aairman23 said:
That was all I really needed to know...I am very happy with starburst... thank you!
Edit: last question For some reason I have a little "arrow loop" or "arrows in a circle" (in grey) in the middle of my top menu bar, and it is partially blocking the time. Did I induce this somehow, how do I make it go away (reboot didn't work)?
Click to expand...
Click to collapse
The arrows are the sync indicator (for any "pull" accounts or contact/calendar sync). You can check under Settings->Accounts & sync to see if any of your accounts are spinning. You can cancel the sync from there and restart it if you like. Sometimes they get stuck.
Aairman23 said:
Quick question,
I'm rooted w/latest Starburst and ICS theme, and I accidentally allowed the most recent Sprint system update to go forward (12/12/2011 @ 8am [EST]). I did so without asking (here) if this was safe. So is it? I searched other threads and it appears that some recommend going back to stock prior to updating, while other swear that "re-stocking" is unnecessary.
So far (after 10 mins) I still have an exclamation mark triangle with a blue andriod guy. Not sure if this is normal. Thanks!
-Aaron
Click to expand...
Click to collapse
More to the point...I am rooted with stock EG30. Received update and failed so I assume I need to un-root in order to get this to install correct?
jeffvb9 said:
More to the point...I am rooted with stock EG30. Received update and failed so I assume I need to un-root in order to get this to install correct?
Click to expand...
Click to collapse
You can do that, or Calkulin has a Stock EK02 ROM in the dev section, which would be easier.
I've been running my phone stock with the EG30 ROM and radio(s) since the day I got it. I originally rooted it using ODIN just to download su (my applications / data were not effected); I do not recall what this method was called. I have not messed with it since due to lack of time.
Today I got a notice about a new OTA firmware update. I let it try to update but it failed with the following error:
Code:
E: Error in /cache/182a027d4e63.SPH-D710_update_EG30_to_EK02.zip (Status 7)
I could be wrong but this error doesn't seem indicative of a failure to update due to the fact that I have root.
I rebooted the phone and it's still at stock EG30 and it states that there is no update available. The only thing I've tried since was to flash (using stock recovery still) a pre-rooted version of this update but it failed to "signature verification".
Can someone give me a pointer on what I need to do to get this phone updated preferably WITHOUT having to reload my apps/settings?
Thanks!
Followed this thread here and was able to update perfectly without having to wipe my data:
http://forum.xda-developers.com/showpost.php?p=20233048&postcount=376
I think the issue may have been that I previously "integrated into ROM" some software via TB. Now have to figure out how to re-root.
Wayno-san said:
Now have to figure out how to re-root.
Click to expand...
Click to collapse
Very simple, just look at the first post in that thread and choose Option A.
Can someone help me with this? I found that if you remove sprintandroidextension.apk it goes away but it didnt. I also found that by removing SprintOMADMConnMOPlugin.apk it goes away, but i cant find it on my Galaxy note 2. Any ideas? Thanks in advance.
If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
digitallogik said:
If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.
Click to expand...
Click to collapse
I tried doing that many times but it never worked, it just gave me an error.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
Thank you! it worked
interesting. found this thread buried, and there still seem to be many people with this issue... seemingly related to the chameleon FCs some are getting, somehow possibly related to the LK8 update and/or a return to an earlier stock version...
digitallogik said:
If you let it go all the way through HFA once it won't return.
Click to expand...
Click to collapse
I've let it complete (personally) aprox 20+ times, so no go.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
could the "fix" really be this simple? (at work, can't test this right now.)
kingdazy said:
could the "fix" really be this simple? (at work, can't test this right now.)
Click to expand...
Click to collapse
yes, and you can delete the activation.apk as well to stop it
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
thanks, stopped the HFA, still have the chameleon errors to deal with...
t3project said:
yes, and you can delete the activation.apk as well to stop it
Click to expand...
Click to collapse
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.
kingdazy said:
thanks, stopped the HFA, still have the chameleon errors to deal with...
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.
Click to expand...
Click to collapse
your solution is to thoroughly wipe and reflash whatever rom you are running.
t3project said:
your solution is to thoroughly wipe and reflash whatever rom you are running.
Click to expand...
Click to collapse
I would have thought so too. As I've been advised by other as well. But...
I have, at least five times, run a return to stock, both through ODIN and OneClicks.
I still have the issue. Baffles the mind. Makes little sense. But there it is. And I'm not the only one.
(Just so it's noted, and before you accuse me otherwise, I am not new at this, and I follow directions fastidiously. I've never once had a problem that I didn't cause myself, and I've always been able to fix them by further reading/researching.)
Just for SnG's I'll quote myself and others from a few other posts in other threads:
kingdazy said:
well, this is annoying. I seem to be stuck with the "hands free activation" and chameleon fc.
i'm assuming a nice total stock one click should fix it?
Click to expand...
Click to collapse
garwynn said:
Sure should! Please try the stock restore or rooted restore.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
kingdazy said:
interestingly, it didn't fix it... "preparing network", "hands free" and chameleon FC on every reboot. this is after the rooted full restore OC. what am I missing? weird.
(history: I was rooted stock w/ twrp from the mskip toolkit method of rooting, got rid of twrp using the mrRobinson stock w/ root, and flashed the sxtp update to lk8, got a wifi failbug and tried to get back to stock rooted using mrRobinson and started getting this issue. lol. ok. so... one-clicked your rooted full restore, still there. is that even possible?)
well, my phone seems to work, as long as I don't reboot.
but I find it worrisome.
have to sleep for work now, but if you had any advice for things to try when I wake up, let me know? thanks dood.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
kingdazy said:
Just my 2 cents, my experience with this error.
I'm getting the Chameleon FC, and the persistent HandsFree Activation on every reboot. All started when I lost wifi on the LK8 update zip (I was rooted, thanks to Voodoo OTA rootkeep), and tried to get back to LJC...
And this morning, I tried the following:
Installed TWRP with GooManage, restored a nandroid from my orig rooting using the toolkit, no luck, same two errors.
So then I OneClicked the Full Restore (SPH-L900_LJC_Stock_Restore.exe), and wtf, still there.
As I mentioned in my quote, it (the Note2) works, not broken, but I find the persistent error worrisome.
I am open to criticism, suggestions, whatever. What am I missing?
Click to expand...
Click to collapse
Itchiee said:
I'm having similar issues, I was on the release before LK8, then updated to LK8 but wanted to start over again.
Once i downgraded to LJ1? the hands free bug kept popping up every reboot, until I moved onto to LJC then LK8 update file which is fine.
I'm trying to figure out myself how to go back to the original firmware (pre any updates) without the issues... /subscribed.
Wonder if this is tied into it somehow...
I dunno, my head is exploding reading all these posts, replies.... 5 different versions of restore.
Click to expand...
Click to collapse
evilgenyus said:
I have tried the one click restores back to ljc and the original tar, and I still have the hands free activation issue and the chameleon error. And when I update to lk8 I get no wifi. I have tried returning to stock about 4 times and then updated to lk8 with the same results. I always go back to ljc bc I need wifi.
Click to expand...
Click to collapse
kingdazy said:
interestingly, even using a stock oneclick full restore (and even using a TAR in Odin), still have the handsfree repetition and chameleon FCs. (lol, I'm not complaining really, it's early in the dev life for this device I suppose. )
Also, I've been reading that re-flashing the LK8 update.zip (via sxtp?) while it seems to fix the HFA and ChameleonFC, it kills the wifi? (it killed my wifi after aprox 2 days use, when I orig updated...)
Click to expand...
Click to collapse
garwynn said:
I'm starting to wonder if the move to 4.1.2 changed something that isn't handled properly by older versions. Without a gn2 will be hard to confirm... but I may be resolving that soon as well!
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It would apear that something in the LK8 changes ... something. Permanently?
So, any new advice would be welcome...?
Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app
smooth703 said:
Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
fine question, but without knowing what the chameleon apk does, i'm reluctant to f**k with it.
anyone know? (a goog search gave me nothing...except this XDA rom w/ a fix...? I'm going to try n PM him...)
and again, my concern is the issue seems to be more significant, seeing as a Full Wipe to Stock doesn't fix it.
has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
sxtp site said:
If you need to clear NVRAM/Sprint data login info, perform a ##72786# reset from the Dialer and enter MSL.
Type getprop ril.MSL in adb shell or terminal to retrieve your MSL.
Click to expand...
Click to collapse
kingdazy said:
has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
Click to expand...
Click to collapse
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile
shiftr182 said:
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile
Click to expand...
Click to collapse
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium
So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
kingdazy said:
it would seem that the factors that all of us with this issue have in common are: a) rooting w/ ToolKit ver2 b) flashing LK8 update zip c) trying to return to stock LJC/LJ1 because of a wifi problem... please chime in if you have the issue, but not one of those factors?
After everything, I just returned to stock LJC w/ Flash Counter @ 0 (no) w/ the errors still present, took it into Sprint store said, 'hey guys, this is weird, i've got a persistent error, won't go away after resetting my phone." (IE, acted dumb enough to not have rooted/flashed unofficial shtuff/etc, but smart enough to know that it's a real issue), they looked at it, asked a few obvious questions, replaced it, because obviously something was wrong in a permanent way. I want to a corp store, not a "repair center". I think it was a good thing that these guys were not super techie.
I told them as little as possible, that I had a "wifi issue after an update, tried full reset (through the android settings menu, of course), and the problem didn't go away, no matter what". Once they heard that I had done a full factory reset, and saw the problem/error happen, it was a no-brainer to swap out.
I'll be avoiding the LK8 leak for now, and frankly gun-shy about the toolkit.
Click to expand...
Click to collapse
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
kingdazy said:
ok, to get back to stock, first use this OneClick to get to Stock+Root, it will wipe ALL internal memory except SD card:
http://rwilco12.androidfilehost.com...sung Galaxy Note II (SPH-L900)/LJC/ROM/Rooted
Instructions are here:
http://www.sxtpdevelopers.com/showt...-TAR-SPH-L900-LJC-(LJC-Modem-Kernel-ROM-Stock)
then use TriangleAway, this will set your counter at 0 (reads as "no" in download mode). it should also say "Official" And "Samsung Official"
Then, if you want to get Total Stock unrooted, for returns to Sprint, or any other reason, use Odin (not mobile) to flash this:
http://www.androidfilehost.com/?fid=9390214368362234120
Instructions for flashing that are here:
http://www.sxtpdevelopers.com/showthread.php?76-TAR-STOCK-Full-L900VPALJC-quot-Back-to-Stock-quot
After I did those things, I was stock unrooted, no flash count.
Click to expand...
Click to collapse
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.
Yeah, I have to give it up to garwynn, he hooked me up with the pit file for our phone. Good people.
ProjectROM 2.1
Did a clean install and I get this as well =/
RussellAlan said:
Did a clean install and I get this as well =/
Click to expand...
Click to collapse
a clean install, coming from what? And what did you use to get back to stock? (Just asking so people will have a clear history of what is causing this. In case a dev wants to look closer at the problem, have clear ideas where to start)
Sent from my SPH-L900 using xda premium
ceabbott2 said:
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
+1
Sent from my galaxy note 2....
kingdazy said:
So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.
Click to expand...
Click to collapse
I try that method but mine still show 1 on the counter. Is there a way to get rid of that?
Long story short, with above average ROM knowledge, and two previous successful flashes under my belt, I flashed Slimbean JB 4.2.1 Beta1 for my Sprint GS3 SPH-L710, and all was quite fine until I messed with menu/security/SIM PIN. Though I thought I was setting it for extra phone security, I actually implemented an unknownst-to-me feature that upon the following reboot, the phone requested a PUK code for a now-locked SIM card (my phone doesn't have a SIM card by the way).
After a long CS call to Sprint, including International Sprint, I was told to go to a local store. The short part of this story is that no one has been able to help. You see, since I DON'T have a SIM card, I have no ID to provide to Int Sprint for them to find a PUK code for me to enter. Although, I've had many troubles in doing so, I have since been able to reset the phone to stock factory settings; HOWEVER, this has NOT removed the PUK code screen, which prevents me from using the phone at all.
I am out of ideas of things to change, alter or fix to get rid of this issue. I have tried CWM and TWRP solutions with no success. In a sense, although I can do anything with the phone - recovery, download, flashing - except actually use the OS, I would consider this phone as useless as if it were bricked at this point. Any ideas from out there would be appreciated. Thanks.
Have you tried Odin
Sent from my SPH-L710 using xda premium
I would try flashing an odin stock tar, then re-rooting.
Nothing in recovery, such as a full wipe, factory and system reset fixed the problem?
This is good info to know. Please let us know of a solution if you find one - good luck!
Have you tried Odin
Click to expand...
Click to collapse
I can use and have used Odin - no problem. I have full access to the device, just none to the OS.
I would try flashing an odin stock tar, then re-rooting.
Click to expand...
Click to collapse
I have successfully returned boot, system and recovery to stock, but this has not resolved the overriding issue. I don't believe I have tried to re-root since doing so. Perhaps that is worth a try.
EDIT: rerooting after Odin stock flash did not help the issue.
Nothing in recovery, such as a full wipe, factory and system reset fixed the problem?
Click to expand...
Click to collapse
I am afraid none of these tasks worked. This issue must reside somewhere recovery can't get to, and only the OS can. The software is likely built so that a regularly performed task can't override a security issue - even if it is a false issue.
GRazor71 said:
I can use and have used Odin - no problem. I have full access to the device, just none to the OS.
I have successfully returned boot, system and recovery to stock, but this has not resolved the overriding issue. I don't believe I have tried to re-root since doing so. Perhaps that is worth a try.
EDIT: rerooting after Odin stock flash did not help the issue.
I am afraid none of these tasks worked. This issue must reside somewhere recovery can't get to, and only the OS can. The software is likely built so that a regularly performed task can't override a security issue - even if it is a false issue.
Click to expand...
Click to collapse
Have you tried wiping internal storage through twrp? I saw a solution for wiping encryption by wiping internal storage through twrp,
Mcluvin
Sent from my SCH-I800 using Tapatalk 2
Have you tried wiping internal storage through twrp?
Click to expand...
Click to collapse
Tried it last night. Though promising, this too failed.
GRazor71 said:
Tried it last night. Though promising, this too failed.
Click to expand...
Click to collapse
Do you have insurance on your phone?
Sent from my SCH-I800 using Tapatalk 2
Do you have insurance on your phone?
Click to expand...
Click to collapse
Nope.
This happened on my nexus and I had to get a new phone because your phone is basically locked at that point and I did try random codes and one of them worked but my lte didn't work after that neither did MMS so I just kept calling sprint non stop for a replacement and they finally gave in and gave me an exchange for free
Sent from my SPH-L710
jazz995756 said:
This happened on my nexus and I had to get a new phone because your phone is basically locked at that point and I did try random codes and one of them forked but my lte didn't work after that neither did MMS so I just kept calling sprint non stop for a replacement and they finally gave in and gave me an exchange for free
Click to expand...
Click to collapse
Did you have to contact International Sprint CS or just regular? How long exactly did you badger them? Had you flashed the phone, increasing your Binary count? If so, did Sprint not hit you with a bill after replacement? Just curious, as I have really upped my count due to recovery flashes to try to fix the phone. I think I can still get a Samsung E-ticket through Sprint store for about $37.00. But again, I am concerned about the flash count, and being unable to reset it. Perhaps I should do what I can to really brick it once and for all before I turn it over.
Flash http://forum.xda-developers.com/showthread.php?t=1904099 to go to stock unrooted with stock recovery and a reset flash count.
ChaseBroyles said:
Flash http://forum.xda-developers.com/showthread.php?t=1904099 to go to stock unrooted with stock recovery and a reset flash count.
Click to expand...
Click to collapse
Awesome! Thanks, will give it a go.
ChaseBroyles said:
Flash http://forum.xda-developers.com/showthread.php?t=1904099 to go to stock unrooted with stock recovery and a reset flash count.
Click to expand...
Click to collapse
I don't think this will work seeing as he's already flashed an odin stock tar which brought the phone back to stock everything. :/
mstrmscn said:
I don't think this will work seeing as he's already flashed an odin stock tar which brought the phone back to stock everything. :/
Click to expand...
Click to collapse
He wanted to reset the flash counter and go to pure stock so he could take it to the Sprint store.
He wanted to reset the flash counter and go to pure stock so he could take it to the Sprint store.
Click to expand...
Click to collapse
Correct, and it worked like a charm. Thanks again!!!!!
Handsfree Activation?
I don't think Sprint even implements that rule anymore so he should definitely be fine. Have you tried handsfree activation ------>
http://forum.xda-developers.com/showthread.php?t=1670131
Maybe give that a whirl. I believe you must be on stock tw for this to work effectively which it sounds like you should now be on.
On second thought, your phone may not even allow you get as far as being able to dial the activation number, but just thought I'd throw it out there.
RS7JR said:
I don't think Sprint even implements that rule anymore so he should definitely be fine. Have you tried handsfree activation ------>
http://forum.xda-developers.com/showthread.php?t=1670131
Maybe give that a whirl. I believe you must be on stock tw for this to work effectively which it sounds like you should now be on.
On second thought, your phone may not even allow you get as far as being able to dial the activation number, but just thought I'd throw it out there.
Click to expand...
Click to collapse
Yeah, I don't have any access to the phone OS whatsoever. Sprint tech has it now; doing some kind of process which includes a 40-minute file extraction and a 30+minute flash. Perhaps that will finally reset everything. If not, Sprint has already said it will then replace the phone.
Received a new GS3 today and I'm back in the game. Thank you to everyone who tried to assist me. In the end, no one on any forum, not Sprint, and not even Samsung could correct the original phone problem. The moral - be very cognizant and careful when flashing any CMDA variant of a native GSM ROM, as there could be settings within them regarding the SIM cards that GSM's do have, but CMDA's do not, or perhaps other harmful settings if messed with or changed. This warning is really nothing new to anyone flashing custom ROM's; it's simply another hard-learned lesson by one person whose adding more truth to the usefulness of such warnings.
I feel like a moron because mine hasn't updated automatically from 4.4.4. Any way to force the Lollipop update? I already checked and have the 24 wait period in effect. Thanks!
Happened to me as well. Go into settings, time and date, uncheck the automatic date/time function and move the date 1 day ahead. I would reboot the phone just in case, and check it again.
efishta said:
Happened to me as well. Go into settings, time and date, uncheck the automatic date/time function and move the date 1 day ahead. I would reboot the phone just in case, and check it again.
Click to expand...
Click to collapse
Weird - just did all that and it still says software is up to date. Any other suggestions?
Called AT&T to see if they could push Lollipop to my device. No dice. Tried the "move ahead one calendar day" trick, but it didn't work. Now it shows that I can't check again for 702 hours. Ha! Any other suggestions? Maybe it just hadn't rolled out to everyone yet. I'm in Chicago, if that matters.
If you don't have an issue wiping your data then you can use the stock Odin file in the general sub to flash it back to stock and update again.
I had my wife's phone updated with a push from AT&T. She had the same issue. They have to file a ti let and tech department did it but took a few days.
Hoshneer said:
I had my wife's phone updated with a push from AT&T. She had the same issue. They have to file a ti let and tech department did it but took a few days.
Click to expand...
Click to collapse
Thanks for the help! Did you do it over support chat on their site or the phone?
nunyabiziz said:
If you don't have an issue wiping your data then you can use the stock Odin file in the general sub to flash it back to stock and update again.
Click to expand...
Click to collapse
Thanks! Yeah, I might just do this.
Also if you factory restore your phone it will go back to the default 24hr wait.
I haven't really messed around with root stuff in a while, but I know even without root we used to be able to download the update, put it in the root or the SD card and rename it update.zip . Does this not work anymore? I really thought there would be a way to force the update somehow..
evilsock said:
I haven't really messed around with root stuff in a while, but I know even without root we used to be able to download the update, put it in the root or the SD card and rename it update.zip . Does this not work anymore? I really thought there would be a way to force the update somehow..
Click to expand...
Click to collapse
That would work if someone has captured the zip file or the download URL, which no one has done. Virtually every 5.0.1 related thread has someone asking for this, with the same response. No one has it, and if they did, it would be available in a stickied post.
Oh the woes of waiting for updates lol.
I remember with my OG moto droid waiting for 2.1 lol.
And how 2.2 blew my mind. Now look at it.
i had to flash oem kitkat to my att note 4, which right after the flash immediately got lollipop.
if you do got to the Samsung kiosk have them re-flash kitkat. then the download for lollipop will update after setup.
Force update to marshmallow?
Hi, absolute idiot when it comes to stuff like this.
So, i was searching through my apps list when i noticed AT&T software update.
I dont need any AT&T applications as i am in Australia and do not have AT&T.
i have tried to force an update by following the clearing data and force stopping the Google services frame work.
tried it multiple times, nothing.
Then i thought i could disable the app of the AT&T software update, and then i fell deeper into the rabbit hole of how OSPolice got in trouble and how there is 2 versions of package disabler pro.
So here i am, stuck with 5.1.1 and i have no idea what to do.
No, i am not going to root it. This is an AT&T phone, with a bootlocker on it. If anyone, *ANYONE*, can help me solve this small issue that would be much appreciated.
UPDATED VIDEO
NOW USE SAMSUNG SMART SWITCH FOUND BY CLICKING THIS TEXT​Use the method at this link instead, and ignore the info below: http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
I've been messing heavily with my new S6 Edge (Rooting, Removing System Apps, etc), and have caused myself some issues. I wanted to restore the Firmware, but Kies would not do it last night. But now, this afternoon, it is allowing it. I'm installing right now and it appears to be going smoothly.
Just a heads up for anyone that was trying before and could not get it to go.
I'll report back if I have any issues.
DOWNLOAD KIES
UPDATE: It went perfectly smooth. Now I'm back to Stock Firmware with Stock Recovery.
Video Tutorial
SuperSport said:
I've been messing heavily with my new S6 Edge (Rooting, Removing System Apps, etc), and have caused myself some issues. I wanted to restore the Firmware, but Kies would not do it last night. But now, this afternoon, it is allowing it. I'm installing right now and it appears to be going smoothly.
Just a heads up for anyone that was trying before and could not get it to go.
I'll report back if I have any issues.
UPDATE: It went perfectly smooth. Now back to Stock Firmware with Stock Recovery.
Click to expand...
Click to collapse
It doesn't work for me yet. did you enter download mode before connecting to Kies? what version of Kies do you have? mine is 3.2.15041_2
I entered download mode when it asked me to. Also Kies 3.2
I also got that message, but it will go through anyways. At least it did for me. I left that message in the background till it finished.
Initial Update when you Open Box is Included in this method
I just noticed that the update you get when you first turn on your phone is pre-built into this update method. I wonder if that has anything to do with the fact that my phone feels blazing fast now as opposed to when I first got it. And, it's not near as HOT as it was.
Here is my current version for comparison. Not sure if it's the same as that updated file we got when first turned on as I didn't make a note of the version numbers.
Just curious, was the phone staying awake at all times after you rooted it? Mine is, and I noticed today after my second Edge came in that rooting appears to be the cause.
joshnichols189 said:
Just curious, was the phone staying awake at all times after you rooted it? Mine is, and I noticed today after my second Edge came in that rooting appears to be the cause.
Click to expand...
Click to collapse
No, but I did find the battery life to be HORRIBLE! Now, with this Firmware Recovery, the battery is lasting longer than it has since I got it. I'm finally really enjoying the phone. When it was new, battery life was very dismal and it got really hot regularly. Now it feels like a normal phone, but FAST.
Yep, my battery life was horrible after rooting as well - I found out and now I'm almost 100% positive that when you root it the system doesn't deep sleep properly. I was able to confirm on a second phone that it does deep sleep at all times up until rooting. Afterwards it just refuses to enter deep sleep.
good to see a restore works, but I don't think I will root until TWRP comes out for this guy.
phone is running just fine now..
My device won't boot even with the 920 root method. And kids says my serial n is no good?
Tell your kids to mind their own business.
Hehe, just kidding.
What serial are you using? It needs to be the one from Settings/About/Status near the bottom of that screen. Try again, making sure you've got model and serial exact. I had it complain on me a couple times. Was a mistype on my part. Not sure if case matters, but maybe try all upper case.
NOTICE: I've posted a new video showing how to use Samsung Smart Switch to do this process. You can ignore this thread and go to the new thread here:
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
SuperSport said:
NOTICE: I've posted a new video showing how to use Samsung Smart Switch to do this process. You can ignore this thread and go to the new thread here:
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
Click to expand...
Click to collapse
nice work :good:
Hi there,
I finished the process "Software Update and Initialization" via SS but my it looks like my phone has the same settings and apps as before and was not "wiped" or initialised to factory.
Does this mean it actually was not successful or did the process actually automatically restore my backup while I looked away?
The phone definitely seems snappier though ...
Thx
Ken
kenwchan said:
Hi there,
I finished the process "Software Update and Initialization" via SS but my it looks like my phone has the same settings and apps as before and was not "wiped" or initialised to factory.
Does this mean it actually was not successful or did the process actually automatically restore my backup while I looked away?
The phone definitely seems snappier though ...
Thx
Ken
Click to expand...
Click to collapse
I saw your post in the other thread and replied there: http://forum.xda-developers.com/tmo...re-using-samsung-t3079176/page29#post61541063