New user with hopefully a simple question. Currently my phone is stock everything. As I have very little experience with Android I do not feel comfortable rooting and installing new ROMs on my phone yet.
I am running Android 2.3.1 according to settings however I am fairly sure that 2.3.3 is out. I was told by a few peeps that my phone would auto update (and that was the beauty of Nexus phones) but for some reason I am still running 2.3.1.
Do I have to do anything to update? I bought the phone outright from the U.S but I am in Australia on the Optus 3G Network. Everything else on the phone runs smoothly, I was just wondering if my service provider has to actually do something.. which if so, I'm kinda stuffed as the Nexus S isn't even out in Australia yet.
Thanks
You can manually update the phone to 2.3.3.
Use this tutorial, but with this file.
or type this in the dialer *#*#2432546#*#*
It does seem as if Google stopped pushing out the update, but nobody knows why.
The checkin method described above worked for people at the beginning, but now it doesn't seem to make any difference. I'm on stock 2.3.2, and haven't gotten the update to 2.3.3 either.
At this point, peoples' suggestion of manually updating seems to be the way to go.
Related
Well, I think I'm deep poo.
I'll save the introduction, being a new member, for later, and focus on an urgent problem that needs help.
Basically, being stuck on 2.1, I tried to find the easier way to upgrade my Captivate to 2.2. My Kies didn't work (even though I tried many solutions), so I had to find new ways to update my phone to Froyo. Take note that my Captivate is locked on Rogers (meaning I have a SIM card inside already). Also, my phone isn't rooted.
I stumbled upon this; "considering I can't post links, I'll give the directions for you, so you find the page I'm talking about; it's on techpetals.net and the article name is "How to Install Froyo on Captivate – Android 2.2 Froyo for Samsung Captivate Leaked"
I completed all the steps and this is where the problem shows its ugly face.
The HUGE problem comes from the fact that my phone is now like a stock, locked AT&T phone. What I mean by that is that the boot screen shows the AT&T logo. Everything is stock, such as in the early AT&T Captivate YouTube review. All my contacts are probably lost (I hope there's a way to retrieve them back). I can blame myself, as much as I can blame the author of the article who didn't mention that the solution only applied to US phones (likely). At least the menu shows that the firmware's 2.2.
I'm in limbo and I don't know what to do. There are so many things to fix here. I don't know what to do and I urgently need your help. What should I do, people?
Any kind of help would be appreciated.
What seems to be the problem? Do you want to go back to stock or do you just want to remove the ATT boot screen?
carboncopy01 said:
What seems to be the problem? Do you want to go back to stock or do you just want to remove the ATT boot screen?
Click to expand...
Click to collapse
Thanks for the reply. A little update on my situation: I've followed the steps mentioned on the mmacleod.ca - updating the rogers samsung galaxy s to android froyo 2 2 froyo article, which helped me set my APN. 2.2. is working great, but my issue now is the fact that I lost my contacts (which were stored on the internal memory) and the AT&T boot screen.
Are these solvable issues?
As far as getting OTA updates, is there any difference between being on T-Mobile's phone network or on random wi-fi link? Does it make any difference if the sim card is in the phone or not?
I don't have reception at all at home so the phones are just on wifi and I often only spend a few hours a week on T-Mobile's network. So at that rate I may never get the OTA update. And lately my SIM card is in my spare rooted G2x which I've been using to try out ROMs.
Does anyone have any idea how phones are selected for updating? Random based on IMEI number? Phone number? SIM card? Date phone was purchased? Date the phone was manufactured? Does account type matter? Prepaid vs contract etc.?? The lack of info about this is infuriating. Same as the new market, weeks later, still no new market on my stock phone (not side loading anything on that phone).
The fact that Google has no direct support for Android at all and they are leaving support completely to grossly incompetent companies like LG and T-Mobile bodes very poorly in my estimation. Will this have me go to a locked down phone like iPhone or WM7 phones? No. But it leads me hoping they might open up WebOS more and get it on some better hardware.
Basically, is there anything I can do to influence the situation, or is it completely random? Does checking more often help, or will my phone only get the update once Google/LG/T-Mobile determine my phone will get it???
No one has any idea? Not even wild, inaccurate speculation??
I am interrested in knowing this as well! I spend most of the day on wifi calling either at work or at home...
I recently spoke to tech support he told me he would recommend updating thru the lg update tool because its a secure connection.
Sent from my LG-P999 using XDA App
I heard they use IMEIs, but I don't think the IMEIs are necessarily in order of oldest to newest. One of my buddies who bought his nexus one from google a couple months after I did would always get OTAs before I did.
And we both got OTAs over wifi. I wouldn't know if your sim card needs to be in there, but I would definitely leave it in and just run the *#*#checkin#*#* command just in case.
But nonetheless, to anybody:
Please use alogcat while downloading the OTA.
Once done, just upload the whole logcat so that we can find the URL for the OTA.
Ha! Strangely, I got my OTA GB today. While on cellular, not wifi. Go figure.
Still waitin' on the new market......
Sorry, I wish I had known about the logcat thing. I may flash stock 2.2 onto my spare rooted g2x and wait to see when it gets the OTA, I want nothing to do with the LG updater app, but I might loose patience, we'll see....
Oh, and the *#*#checkin#*#* command??? Has this been tested to work on the G2x? Is that regarded as useful on Android phones in general? Or certain brands, like just HTCs? Search isn't showing too much info on that.
Ha! Strangely, I got my OTA GB today. While on cellular, not wifi. Go figure.
Still waitin' on the new market......
Sorry, I wish I had known about the logcat thing. I may flash stock 2.2 onto my spare rooted g2x and wait to see when it gets the OTA, I want nothing to do with the LG updater app, but I might loose patience, we'll see....
Oh, and the *#*#checkin#*#* command??? Has this been tested to work on the G2x? Is that regarded as useful on Android phones in general? Or certain brands, like just HTCs? Search isn't showing too much info on that.
Ok, so my girlfriend currently has a G2.. She got it about a month or so ago, I know her version was 4.2.2. So I looked into rooting and saw that it was possible. I'm coming from a Gnex, so root and rom is important to me. Anyway.. Now I hear that the new AT&T G2's are shipping with 4.4.2? And loki is not working currently with that so there is no way to downgrade and root? Is that the correct understanding? Also, are they shipping with 4.4.2 or is it still just an OTA update they do while in store at AT&T buying one? Because my buddy works at AT&T and if it is just the OTA, I will just have him leave it at 4.2.2 for me and root and rom it from there, since that seems much easier.
Also I saw something about a 838 firmware that currently doesn't support root?
Any help would be much appreciated. Thanks, Chris.
If it comes with 4.4 you can go back to 4.2 through download mode using this, http://forum.xda-developers.com/showthread.php?t=2663369 . Then root and install recovery. Check out http://forum.xda-developers.com/showthread.php?t=2520419 for some videos on that. Then you can flash a modified stock 4.4 that keeps the 4.2 bootloader and root/recovery intact here http://forum.xda-developers.com/showthread.php?t=2672931. Or flash any of the many 4.2 4.4 custom roms available. There are other ways to go about this but it works for me. Just takes quite a while to download the files the first time to do it! :laugh: Also, if you decide to do this and go with the stock 4.4 firmware AT&T has a small patch they're pushing now that you'll want to block. You can just freeze the software update using TiBu.
I have been liking my G2 but I would (and will soon) jump to another phone, like the M8 or N6, the dev support is decent but there are some far outstanding issues with this phone and kitkat, seems like something always not working right i.e. hotspot, auto-rotate, volume, process com,gapps errors, etc,
Not necessarily
ossito2012 said:
I have been liking my G2 but I would (and will soon) jump to another phone, like the M8 or N6, the dev support is decent but there are some far outstanding issues with this phone and kitkat, seems like something always not working right i.e. hotspot, auto-rotate, volume, process com,gapps errors, etc,
Click to expand...
Click to collapse
I got my LG G2 a week ago and I'll tell you I didn't have any problems with it, however I did downgrade and put an older version of CM 10 for the D80010d on my phone, not knowing that you can upgrade while maintaining the bootloader, as described above. I did notice that my gps didn't work after that, my tethering didn't work and while using wifi hotspot I was unable to load google or facebook, meaning I can't access my e-mail from my computer. I get SSL error's on https:// sites and sometimes I can proceed anyway, while other times I can't load it at all. however these sites load fine on my phone.
Stable
My LG G2 is completely stable on latest stock ROM and CM nightly. Honestly, I haven't run into any trouble.
Remember, when you are flashing - try clearing cache.
J0hnC0nn3r said:
I got my LG G2 a week ago and I'll tell you I didn't have any problems with it, however I did downgrade and put an older version of CM 10 for the D80010d on my phone, not knowing that you can upgrade while maintaining the bootloader, as described above. I did notice that my gps didn't work after that, my tethering didn't work and while using wifi hotspot I was unable to load google or facebook, meaning I can't access my e-mail from my computer. I get SSL error's on https:// sites and sometimes I can proceed anyway, while other times I can't load it at all. however these sites load fine on my phone.
Click to expand...
Click to collapse
ainstushar said:
My LG G2 is completely stable on latest stock ROM and CM nightly. Honestly, I haven't run into any trouble.
Remember, when you are flashing - try clearing cache.
Click to expand...
Click to collapse
I agree with you guys for most part phone is 95% good, don't really think it is devs fault but LG is making this phone a pain in the ass to play with, I would think with Samsung allowing the Htc One and G2 to sneak in beat their S4, LG would seize the moment to open up the phone to be truly customized. Looking at HTC One M8 forums it seems HTC is not putting up stupid barriers to rooting and stuff. Imagine a HTC Nexus 6
Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc
I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc
Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.
And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc
the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....
I just bought a new unlocked Verizon G920V phone from eBay to use with my Verizon prepaid account. (Well actually the hardware version under About Phone lists it as G920V.07). I can't say for sure if Marshmallow or Nougat shipped on this phone but it's currently running Nougat. As soon as I got it and it connected to my home wifi it wanted to update so I decided (maybe like an idiot) to let it. It appeared to download a giant file and flash itself a new firmware. This leads me to believe that it maybe shipped with Marshmallow but it obviously now has Nougat on it.
FWIW, I've rooted my own phones and a couple of my wife's phones in the past, but I'm by no means an expert. I'm fairly technically inclined in other areas of technology, but when it came to rooting various phones it amounted to carefully researching (usually through this site) and simply following a set of steps. I've always been successful. Long story short, I'm kind-of confused as to whether or not I can root. Like I said, I'm a bit confused, but it would appear that not only is there no root for the S6 running Nougat, but I believe I read where someone mentioned that Verizon released a security patch that prevents any sort of downgrading. Right after getting cellular service transferred the phone wanted to do a security patch so I assume that I've now got that patch installed as well.
So, can I downgrade this phone and root? I don't care about marshmallow I'll go to version 5 (whatever wonky name that one is called) if I have to. I would really just like to get root on this phone. Mainly so I can block ads more effectively and try to milk more battery life out of this thing because the battery life is horrible in my opinion.
Also FWIW, the software build/baseband number is G920VVRS4DQE1 if that helps or matters.
Anyway, this long-time lurker but first-time poster thanks you in advance for any replies.
It's been a few days and no replies, but from the additional information I've found since posting, I'm thinking that root ain't gonna happen. At this point I don't think it's even possible to roll back to an earlier version. Oh well I'll just live with this phone for awhile. I really like the phone despite not being able to get root. I suppose I'll just live with ads.
You can go to Samsung apps, if you have a Samsung account and download there ad block app. That is what I am using. It under Galaxy apps that came with phone
Sent from my Verizon Samsung Galaxy S6 using XDA Labs
You actually can downgrade your firmware should you so desire. The following two threads have links to firmwares flashable via odin.
https://forum.xda-developers.com/ve...20vvrs4dqd1-odin-nougat-7-0-firmware-t3597007
https://forum.xda-developers.com/verizon-galaxy-s6/general/downgrade-6-0-1-to-5-1-1-t3489816
At this point I don't think you can downgrade any lower than the OK7 firmware.