My wife's phone has never been able to get an OTA update (2 that I know of) on her Infuse. Do we need to check with AT&T on this? (searched for a forum post and couldn't find one)
I also have never been able to get OTA updates. That doesn't bother me cause i run custom roms which usually comes with the updates.
Sent from my Infused 1.6.0
Related
Excuse my complete noobishness, but I have to know.
If I root, but keep the stock ROM (basically, I just want root to get MarketEnabler at this stage) will I still be able to get OTA updates from Google?
The way I understand it, the answer is yes, but I'd like some confirmation from someone who definitely knows more than me.
no.....no.....no.....
Why ? There is any limitation for unlocked devices ? I think problems with ota only for custom rom.
I think so long as your on stock rom you get updates despite su and root. However if it is a major update you will lose root.
Once you root, you won't WANT the OTA update because you will get it from the forums long before it hits your device from Google.
This is a common question asked but its really irrelevant. Just root, the instant the update is released everyone gets it long before Google pushes it to you. Sure you could load a stock ROM and sit there waiting for a week till it pushes meanwhile everyone else just manually grabs it
Hello guys,
I have a stock Nexus One that received two updates, the first one was 2.2 which updated since the first boot, and the second one is the 2.2.1 (FRG83D). Now Google started the 2.3 OTA roll out (see http://bit.ly/hUlpUy) but I didn't get yet the 2.2.2 update yet. Will my phone accept the 2.3 one even if I didn't update to 2.2.2 yet?
Thanks in advance!
Was your phone bought directly from Google or through a carrier? The only phones that i know of that haven't received 2.2.2 yet are the ones tied to carriers like Vodafone, and if that is the case you'd have a long wait to receive 2.3.3 anyway.
Well yes. I bought it from Vodafone Italy. I understand, but it would update anyways right? Even if I would wait a little longer I mean? And will it have to update first to 2.2.2 or it just can jump to 2.3.3?
Thanks for your response.
And by the way it is not locked to vodafone (branded). It's unlocked.
Type *#*#checkin#*#* into the dialer. Your phone will then force check for the update.
More info here
Yeah I do this every now and then
I also have the Nexus One which in the end came from Vodafone! (However much i regret this now) So I am also still on 2.2.1 waiting for Vodafone to still push 2.2.2!
I have attempted to flash 2.2.2 to my phone using ClockWorkMod etc but that didn't work out and it ended up just looping the Nexus logo on startup so had to recover it all, I attempted that a few times as well but with no luck! So in the end I still have the carrier version of stock android!
I'm hoping that someone on here manages to source the Nexus One 2.3.3 OTA file from the Google servers and can whack up some instructions on how we can flash that over because I'm sick of waiting on Vodafone! Will it be possible for me to go from 2.2.1 straight to 2.3.3? Or do I have to get 2.2.2?
I don't think anyone has received the Nexus One 2.3.3 OTA yet so whether Google have actually put it up for release yet is another thing!
The OTA is not pushed by Vodafone. I've bought my N1 from Italy (vodafone) and I use it in Egypt, and I could receive all the previous OTAs without any issue. Now my question was simple. Do I have to update to the versions before 2.3.3 or it can just update from 2.2.1 to 2.3.3? (note there are 3 versions in the middle).
Thanks.
You guys have lots of options and should really come post in the Nexus One section of the forum.
If you are on Vodafone firmware phones, and hitting up *#*#checkin#*#* daily, then you are going to wear out your device before Voda actually gets around to releasing the OTA!
I imagine that Voda will either OTA 2.2.2 sometime and then 2.3.3 later, or will skip 2.2.2 and find a way to roll it into the 2.3.3 update later. There's also the possibility that they never intend to update the Nexus One again. After all there's not much profit in it for them as Nexus users make up a tiny percentage of their customers. My advice would be to go custom.
Options include Rooting and flashing a stock, non-voda firmware, which fails for a lot of people (including me), or flashing a custom/stock 2.2.2 (which worked for me) which will then allow future OTA direct from Google, or go the custom route and flash a CM7 ROM so that you never have to worry about OTA again
Thanks DirkGently1 for the info. I would like to do the same thing you did with your phone (flashing a stock 2.2.2) so I could get OTAs directly from google?
Thanks in advance!
I would also like to receive my OTA's from Google, I have attempted the flashing of a stock 2.2.2 ROM which is what failed for me, maybe this is the same non vodafone firmware you've just mentioned which didn't work for you?
Any instructions and files as to how you managed to flash yours to 2.2.2 to get updates from Google?
tomrobbo26 said:
I would also like to receive my OTA's from Google, I have attempted the flashing of a stock 2.2.2 ROM which is what failed for me, maybe this is the same non vodafone firmware you've just mentioned which didn't work for you?
Any instructions and files as to how you managed to flash yours to 2.2.2 to get updates from Google?
Click to expand...
Click to collapse
All the usual stock ROM/passimg.zip methods failed for me. Either installing the OTA to get updated to the most recent build, or updating manually, would fail. So i used THIS ROM which is a stock, rooted, 2.2.2 that will be able to receive OTA direct from Google.
If you can't install that for some reason then you probably can't install any ROM using the normal methods. In that case your only option would be to unlock your Bootloader and use Fastboot. HTC always seems to honour warranties regardless so i wouldn't let that worry you.
I guess I'll have to root my 2.2.1 Rom before being able to flash it with the rom you suggested...
I can't root it!!
omarfouad said:
I can't root it!!
Click to expand...
Click to collapse
What method did you try? For me SuperOneClick works like a champ as long as 1) Your device drivers are installed properly on your pc* and 2) You enable USB Debugging and then turn off the phone/plug in to pc/start SOC and select 'Root'/Turn phone back on when you see the 'waiting for device..' prompt/wait until completed.
*Nexus one driver pack can be found around here somewhere. I believe they came from the SDK.
The wiki is a great source of N1 info... http://forum.xda-developers.com/showthread.php?t=746544
My version is 2.2.1. Is there something that can root it yet?
omarfouad said:
My version is 2.2.1. Is there something that can root it yet?
Click to expand...
Click to collapse
Yes, SOC as mentioned above.
http://forum.xda-developers.com/showthread.php?t=803682
Hi everibody,
tried searching for the result but couldn't find any answer... Also, I'm guessin it would wipe off all my data, rite?
- Software Version: 1.28.707.2
- Android Version: 2.3.3
- Baseband Version: 10.43.9007.00U_10.11.9007.19_M
Note: I tried to do the update once but my phone showed an "error" screen (yellow exclamation mark inside a triangle) and hung.
Any help is appreciated.
As far as i am led to believe you cannot update if you are rooted,(more advance users feel free to correct me!). I think you have to restore using the ruu.exe back to stock 2.3.3 unrooted to do the update!
yes this is correct, I do believe there is a way to accept the update while rooted and get it to work but once its applied it will break root anyway... if you want to stay rooted then might as well flash one of the stock rooted 2.3.4 roms available in the dev forum... the ones for the US aren't out yet. hope this helps
You might want to check this out:
http://forum.xda-developers.com/showpost.php?p=16734103&postcount=342
I haven't tried it myself.
If you do try it, I would love to hear back from you after as to how it went.
When I had my g2x I was running eaglesblood and when the T-Mobile update finally got released it gave me the notification to update but I didn't. It may work both ways
Sent from my HTC Sensation Z710e using XDA Premium App
The only way I have received ay updates is if I was running the stock ROM. If you are running a custom ROM you will have to wait until the Dev makes the update. I have accepted some updates holding my breath to not lose root and I have been lucky so far.
I've tried and done successfully without RUU, just with OTA package, Buck767 pointed to my post with guide how to do it
Most of the devs edit out the update option in the build.prop as it is not necessary if you are hoping to stay rooted and s-off. You may simply edit it back in but I certainly wouldn't take that chance of accepting an update accidentally.
thanks for all the replies guys... was bz the past few days... will be trying poduy's method soon... btw, i'm running on stock...
update: just tried poduy's method... but my fone can't seem to update... all versions still remain... tried it twice... after updating, it says update successful... anybody has any clue?
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00046726&fm_seq=49755
So finally the blaze has been confirmed along with others to get ICS which I knew would and am glad I haven't messed around with root or anything else so the update works and makes this phone even better!
Rooting shouldn't affect the process of updating or the update itself.
Anyway, I'm glad to see that this is happening.
appu1232 said:
Rooting shouldn't affect the process of updating or the update itself.
Anyway, I'm glad to see that this is happening.
Click to expand...
Click to collapse
I was under the impression if you changed the kernel you wouldn't receive OTA updates. The process is reversible, but just saying.
That being said, I'll continue my streak, and bet you $10 we don't see ICS from Samsung within the next 3 months.
Oh yeah, I forgot..... this may not be the case anymore, but I remember back in the 2.1-2.2 days that people were always looking for someone that had a phone on 2.1 that received the OTA update to 2.2 to not install it until they had a log thingamajiggie running, as it helped people do their magic with the official rom.
I'm no wizard but if this is desirable to anyone who wants to work on roms for this phone whenever they decide to push ICS to us, lemme know, and lemme know how to do it.
I had to unroot and restore everything to get the ota 2.2 update to work back when I had my Motorola...
Ok, so I got a message for the OTA update today (ver 67.21.125.en.US). Now, I see all these threads that say don't apply the OTA because you can't flash back. But they seem to be talking about if you are already IN ICS. I am running a custom mod version of the supercharged 2.3.6 rom.
Is this the official ICS update? Should I flash all the way back to stock and then just do the OTA's? Will that process make it so I will not be able to FXZ back?
Or Should I follow the instructions in this thread? --> http://forum.xda-developers.com/showthread.php?t=1779968
The only question I have about the above linked thread is I am not sure if that info is out of date regarding this update I just saw today. If the OTA that came up today is nothing new (and it just took forever for me to see it for whatever reason) and everything in that thread still applies, then I will probably go that route. However if this is a new/different update, then I dont know what to do.
Bump
Look here, it has everything you need to know, to make your own decision.
http://forum.xda-developers.com/showthread.php?t=1882335
extide said:
Bump
Click to expand...
Click to collapse
All of your questions have been answered numerous times in numerous threads over the past week.
I suggest to read - A LOT - then, make the choice whether to go on the official ICS (your phone must be in stock 2.3.6 GB condition), or non-official leak#1 which you linked (which yes, we are still able to downgrade with leak#1 ONLY).
If you are going to go on custom roms in the end, then it really doesn't matter... and in my opinion, I'd prefer to have the option to FXZ if I'm in trouble - so I'm personally sticking with leak#1 as a base firmware - at least until we get an FXZ package for the official at&t 4.0.4 ICS.
Ok, I suppose I should have phrased it better, but my main question/concern was whether I was seeing a newer update than what all those threads were talking about. It seems as though I am not.