I am still on ICS 4.04
I rooted phone using GNex ToolKit 7.9 (thanks Mark, ToolKit is great for newbies) mainly to add widgets to Apex Launcher. Since I am still using stock ICS, can I still just sit back and wait for 4.1 JellyBeans to OTA from Sprint?
I am new to Android, about 3 months now. I am a little anxious about flashing a ROM at this point.
Yep, you should still be able to get OTAs IIRC. It's only if you've put on a new rom, kernel or recovery that your ability to get OTAs is stopped (not sure about radio but I would assume that it would stop OTAs too).
Unlawful said:
Yep, you should still be able to get OTAs IIRC. It's only if you've put on a new rom, kernel or recovery that your ability to get OTAs is stopped (not sure about radio but I would assume that it would stop OTAs too).
Click to expand...
Click to collapse
if you modify any system files, the OTA will be available, but you wont be able to install it.
Related
If and when the Gingerbread update gets pushed out, how will us custom ROMmers be notified? Will we receive notifications asking us to download the update and then have to deny it? Will we have to unroot then upgrade? I wasn't around for the 2.2 update so I am a little curious as to how this all works on the Evo. Feel like such a noob right now but I really don't feel liking bricking my Evo due to an act of stupidity.
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
You aren't going to need to do anything, other than NOT take the OTA. The only thing you will need to do is wait from 2-10 hours after the update is out in the wild for the devs to get their hands on it and give us a fully rooted build to flash. It does not take long around here. There is absolutely no need to unroot and take the OTA. Who knows, if you did that you may not even be able to root again. So basically all you're going to need to do for the update is wait for the devs, and then flash a rom as usual. Maybe some new radios or something too, who knows.
I'm more concerned about when they will push the damn update. *Supposedly* it's Q2, but I'd bet if that's true, it will be late Q2.
r916 said:
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
Click to expand...
Click to collapse
Sure, lots of people say "wait for a rooted version of the update," but all I want to know is, is it POSSIBLE to safely upgrade even if you are rooted? Would flashing the stock update remove ClockWork recovery?
yes i was rooted before 2.2 and i was having a crazy day, long story short i accepted the OTA not paying attention and it got me a weird reboot then i was unrooted and on 2.2 i had to wait for a root method for it. but i heard of some people having their phone glitch in crazy ways, also that first OTA sprint rolled out had a bug that was bricking some phones
RileyGrant said:
If and when the Gingerbread update gets pushed out, how will us custom ROMmers be notified? Will we receive notifications asking us to download the update and then have to deny it? Will we have to unroot then upgrade? I wasn't around for the 2.2 update so I am a little curious as to how this all works on the Evo. Feel like such a noob right now but I really don't feel liking bricking my Evo due to an act of stupidity.
Click to expand...
Click to collapse
Developers will simply make new roms, and then you can flash the "update" of that rom. it'd be the same way of flashing CM7 nightlies.
Or just make sure you are s-off, take the update, install it. Then install SU from recovery and you are good to go. Thats the whole point of s-off (other than flashing PRI, NV, and Radios of course)
rugedraw said:
If you rooted with Unrevoked and have Unrevoked Forever, then theoretically you should be able to flash the update and still be s-off to flash a rooted rom over the update. You'd have to push the custom recovery back onto the phone, though. However, I wouldn't be the guinea pig for the theory myself. I'd keep 2.2 until a rooted 2.3 rom is available and then flash that. No one knows what will happen if you flash the OTA update as no one has is or knows what's inside of it.
Once it starts being pushed out, it will just be a matter of time before some posts a thread either:
a) crying because the update broke their root.
b) gloating because the update did NOT break their root.
Basically, don't accept it. Play it safe and wait. We've been on 2.2 for well over half a year, so 1 more day isn't going to kill anyone.
Click to expand...
Click to collapse
To make it simple, the result of accepting the OTA would either:
A- luckily do nothing
B- "Break" your phone and not be able to re-root
r916 said:
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
Click to expand...
Click to collapse
You are correct!
Theoretical question... If you're on a custom non-stock ROM (Myn or CM or whatever) and you accept the OTA, what would happen to the ROM? I don't think it would revert you back to the stock ROM because that ROM isn't on your phone anymore. I can't imagine CM would continue to work since it's not Sense. Would a Sense-based ROM (assuming you reinstalled all the Sprint bloatware) continue working with all the customizations even though you don't have root any more? Or does the OTA rewrite the entire ROM? Or would you just screw up your phone unpredictably?
I'm certainly not going to try this myself, but I'm curious as to what would happen.
phsteve said:
Theoretical question... If you're on a custom non-stock ROM (Myn or CM or whatever) and you accept the OTA, what would happen to the ROM? I don't think it would revert you back to the stock ROM because that ROM isn't on your phone anymore. I can't imagine CM would continue to work since it's not Sense. Would a Sense-based ROM (assuming you reinstalled all the Sprint bloatware) continue working with all the customizations even though you don't have root any more? Or does the OTA rewrite the entire ROM? Or would you just screw up your phone unpredictably?
I'm certainly not going to try this myself, but I'm curious as to what would happen.
Click to expand...
Click to collapse
The OTA update would include the new stock 2.3 rom in it. It would wipe whatever you have on your phone (regardless of whether it is Sense or not) and install the OEM Sprint 2.3-based rom that all will eventually be on all new Evos when HTC ships them out.
Even though I'll probably be on to a new phone by the time the Inc 2 receives its OTA ICS update, I nevertheless want to be able to upgrade to it when it arrives. My question is, will the nandroid backup I have (Android version 2.3.3 with superuser but none of the bloat removed) be able to receive it? Or will I need to go through the whole process of unrooting and restoring 2.3.4 first?
Sent from my Incredible 2 using XDA
tattedupboy said:
Even though I'll probably be on to a new phone by the time the Inc 2 receives its OTA ICS update, I nevertheless want to be able to upgrade to it when it arrives. My question is, will the nandroid backup I have (Android version 2.3.3 with superuser but none of the bloat removed) be able to receive it? Or will I need to go through the whole process of unrooting and restoring 2.3.4 first?
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
you wouldnt want to take the ota regardless as it will likely block root and might bring an hboot that cannot be reverted from
id imagine we d get a leak of the ota ahead of time or just wait for a dev to make an update.zip version of it once its pulled from the servers or a phone
I also had a question about the OTA update. I HTC unlocked and rooted with SU and CWM recovery. I do have some of the bloated apps uninstalled with Titanium Backup. As soon as I heard that the upgrade for ICS was coming out, I flashed the stock recovery from the most recent RUU. Does anyone forsee any problems recieving the ICS OTA with this setup?
Well, not sure I would have done it that way... with the stock recovery you lose CWM's capabilities waiting for Vzw to release the ICS upgrade, and that could take months and months. Additionally, if you accept the ICS OTA my guess is that you'll lose root as well, and be stuck with Vzw's typical bloatware until you re-root. And we don't know if the new OTA will be immediately re-rootable. Some of the previous upgrades have required reverting to earlier versions.
As nitsuj17 remarks a few posts earlier, I would imagine that once the ICS upgrade for the Dinc2 is released, somebody will quickly get hold of it and post up a version for us rooted folks and we can just flash it from CWM. And use TB or AntTek App manager or whatever tool is your favorite to freeze or delete the Vzw crap. That's what I'm planning to do...
Hi guys,
I used the GNEX toolkit to unlock my bootloader and then flash to 4.0.2 yakju. I'm just wondering why I'm not getting an OTA for 4.0.4 or 4.0.3. I've tried clearing the data in GoogleFrameWorkServices. I've also flashed stock recovery.
Did I do something wrong, or is there actually no update?. P.S I'm in Australia.
Any help would be greatly appreciated.
Im in the same boat.
I have flashed the completely stock 4.0.4 ROM from Google Code. I have not received the IMM76I update yet.
I have cleared the framework cache too and still nothing.
I live in Melbourne (australia) and I am assuming that the update to yakju devices works on a country-by-country basis.
IF I don't receive it soon, I am just going to hope Google Code gets updated and I will just reflash a the newer version.
I do not want to root the phone or using work-around methods to install an update. I like having a completely stock phone with a locked bootloader.
(Marshallaw.. Why not just download the 4.0.4 update from Google Code and flash using Fastboot? Atleast that way, you know your on the latest Android version and have a better chance of receiving the IMM76I update, or if worst comes to worst, just wait until Google Code is updated to the latest version and flash that?)
The way Google updates their devices is pretty pathetic. You would think they would push the update to every stock YAKJU device everywhere and not be so selective. My old Nexus S received 4.0.4 update and my stock Galaxy Nexus never received it, so I had to manually flash. Very stupid.
Simmo3D said:
[snip]
IF I don't receive it soon, I am just going to hope Google Code gets updated and I will just reflash a the newer version.
I do not want to root the phone or using work-around methods to install an update. I like having a completely stock phone with a locked bootloader.
Click to expand...
Click to collapse
I think you are confusing a few things:
1) What is posted on Google Code (as you put it), are NOT updates -- they are complete, full ROMs.
2) What is posted here are incremental update that UPDATE your existing ROM.
There is a difference between the two, despite the end result being the same.
3) Having an unlocked bootloader or a locked bootloader does not mean you are stock or are not stock -- it has nothing to do with it at all. You are not adding or taking away anything from the firmware on the device...
4) You say you do not want to use a work around to flash the update, but you are using a work around to flash a full ROM? Something there doesn't compute for me.
5) Flashing a stock update file does not make you any less/more stock than flashing a full ROM.
I don't think you understand what I meant.. Im hoping Google updated their full ROM with the IMM76I kernel and bug fixes...
hence, I am waiting for an updated full ROM that 'includes' the latest kernel update.
e.g. Google Code features :
4.0.1 (ITL41D) and 4.0.1 (ITL41F). I am waiting for
4.0.4 (IMM76D) and 4.0.4 (IMM76I) to be posted on their site.
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Simmo3D said:
I don't think you understand what I meant.. Im hoping Google updated their full ROM with the IMM76I kernel and bug fixes...
hence, I am waiting for an updated full ROM that 'includes' the latest kernel update.
e.g. Google Code features :
4.0.1 (ITL41D) and 4.0.1 (ITL41F). I am waiting for
4.0.4 (IMM76D) and 4.0.4 (IMM76I) to be posted on their site.
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Click to expand...
Click to collapse
Well, I'm not sure if this is it but here's the OTA package for IMM76I from IMM76D. It might just be a test build which was only pushed to small portion of users to test it which would explain not everyone getting it.
And Marshalllaw, you've already begun to flash things and mess around, why not just flash the stock build of 4.0.4 straight away rather than relying on an OTA?
Simmo3D said:
[snip]
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Click to expand...
Click to collapse
Ok, but you do realize that manually installing the IMM76I update (which you can do right now, although requires an unlocked bootloader) ends you up at the exact same place the flashing the IMM76I image when it comes out (and it will still require an unlocked bootloader). So whether you install the update, or what for the full image, you will still wipe, and you will end up at the same place -- you will just get there sooner with the update.
OK but how do you flash this with fastboot once I unlock my boot loader. I need to boot with CWM don't I?
Sent from my Galaxy Nexus using xda premium
Simmo3D said:
OK but how do you flash this with fastboot once I unlock my boot loader. I need to boot with CWM don't I?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Correct, you do. But booting CWM is different from flashing CWM. When you boot it, you are not "writing" anything to your device - you are only loading the kernel and ramdisk into your device's RAM. It only boots CWM one time - as soon as you reboot, it is no longer there, as it was never flashed - it just existed in RAM.
Additionally, even if you did flash it, it still wouldn't be there when you rebooted, because EVERY OTA update adds two files to your device that automatically re-flash the stock recovery on EVERY boot of your device.
Unlawful said:
Well, I'm not sure if this is it but here's the OTA package for IMM76I from IMM76D. It might just be a test build which was only pushed to small portion of users to test it which would explain not everyone getting it.
And Marshalllaw, you've already begun to flash things and mess around, why not just flash the stock build of 4.0.4 straight away rather than relying on an OTA?
Click to expand...
Click to collapse
Hi Unlawful. Yeah I can always flash it directly to 4.0.4, its more that this is my first Android phone / first experience messing with bootloaders and roms. I was more so just wondering if the lack of OTA update to either 4.0.3 or 4.0.4 was that i've screwed something up or that the update has not been pushed to all devices.
My device info is: 19250XXKK6, ICL35F. Its basically the same as when I first bought it but not Yakjuwx. I more or less flashed to Yakju because people were saying that you could get OTA updates faster or something.
Thanks for the help, sorry if this is a noob question.
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Unlawful said:
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Click to expand...
Click to collapse
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
marshalllaw said:
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
Click to expand...
Click to collapse
4.0.3 was never released in OTA form.
Unlawful said:
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Click to expand...
Click to collapse
That does not work. You will have to wait until Google decides it's time for your IMEI to receive it...
marshalllaw said:
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
Click to expand...
Click to collapse
You did not mess anything up. As martonikaj said, there was never any 4.0.3 update.
Updates are not rolled out to everyone all at once. It could take seconds or MONTHS before you get the OTA, after the first person gets it.
Awesome . Thanks for the help guys.
Having an Android is great for all the exploring you can do, finding out how it works though can be a bit daunting.
Sorry for the noob question!.
So been while since I've done much rom flashing. Had an EVO for 2+ years and tried lots of ROMS, but then got the sprint GNEX because I just wanted vanilla android without having to mess with ROMS as much. As such, I'm just running stock 4.1.1, with it rooted for a few apps and wifi tethering which I flashed after rooting. Looking to update to the new stock Sprint 4.2.1 firmware, keeping root and wifi tethering. Back on the EVO, every time there was a new firmare update, someone would post a "stock rooted" ROM (not that I used them), that didn't have anything done to it, but can't seem to find that with the latest Sprint GNEX update, only one that seems to come close has been fiddled with, deodexed, causing some issues. I'm also not used to flashing without my data being on a removable SD card. So I'm wondering, is there a way to just flash a rooted version of the Sprint firmware, keeping my data and wifi tethering (or by just flashing a new 4.2.1 wifi tethering patch), or can I use OTA rootkeeper, flash the OTA update, and restore root? I've got latest TWRP recovery btw, which it seems I would have to change back to stock recovery to flash the OTA update correct? Thanks for any direction anyone can provide
First off, im not sure about wifi tethering, but it is an option on gsm android settings. I would use OTA rootkeeper, but you need the stock recovery first to accept the ota. Did you check this thread? http://forum.xda-developers.com/showthread.php?t=1419170
bodh said:
First off, im not sure about wifi tethering, but it is an option on gsm android settings. I would use OTA rootkeeper, but you need the stock recovery first to accept the ota. Did you check this thread? http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
Thanks so much for pointing me in the right direction. Swear I tried to search other threads before asking but somehow missed that one, looks like it should tell me what I need. Think I was looking too much in the development forum for a full ROM to flash, and missed that thread in the general forum about just applying the update. Thanks again!!
i followed the unroot galaxy s3 thread because i accidentally pressed update when OTA update popped up on my rooted phone.
downloaded the latest android zip and updated with ODIN.
but it doesnt show 4.2 it still shows 4.1.1 android.
im a bit confused.
theres just too much **** available and i lost track of all these build numbers and updates and different programs.
i dont spend much time here anymore after i got rid of the HD2 and now im completely lost.
got other stuff to do cant afford spending 3 hours a day to stay on top of latest repackaged rom release
fuzzysig said:
i followed the unroot galaxy s3 thread because i accidentally pressed update when OTA update popped up on my rooted phone.
downloaded the latest android zip and updated with ODIN.
but it doesnt show 4.2 it still shows 4.1.1 android.
im a bit confused.
theres just too much **** available and i lost track of all these build numbers and updates and different programs.
i dont spend much time here anymore after i got rid of the HD2 and now im completely lost.
got other stuff to do cant afford spending 3 hours a day to stay on top of latest repackaged rom release
Click to expand...
Click to collapse
4.1.1 UVDLJC is the latest official firmware.
oh ok then i thought it was 4.2 for some reason
one more question that i could not understand clearly
once i root the phone again. what specific services do i need to disable to prevent the automatic OTA updates?
i disabled one service related to update but didnt see any others.
and once rooted. do i have to unroot it in order to use odin and manually install OTA update that i downloaded?
im not planning to use custom roms( spent toomuch time making them wrk on HD2 and done with that for good)
jsut stock tmobile roms work fine for me.
thanks for quick reply i was about to try flashing again since i thought that it was supposed to be 4.2 version
fuzzysig said:
one more question that i could not understand clearly
once i root the phone again. what specific services do i need to disable to prevent the automatic OTA updates?
i disabled one service related to update but didnt see any others.
and once rooted. do i have to unroot it in order to use odin and manually install OTA update that i downloaded?
im not planning to use custom roms( spent toomuch time making them wrk on HD2 and done with that for good)
jsut stock tmobile roms work fine for me.
thanks for quick reply i was about to try flashing again since i thought that it was supposed to be 4.2 version
Click to expand...
Click to collapse
You don't have to do anything with ota. When next one comes out you can unroot and install the ota as long as you hav stock recovery. If you have custom recivery you can always update with Samsung kies but you would need to reroot the new ROM. Or just flash a ROM through Odin.
Sent from my SGH-T999 using xda app-developers app