Hey guys, I haven't looked in the source yet but with this new option can we check and see where it's looking for updates? Just an idea there that might facilitate our getting of updates when they come out.
If I'm not mistaken, you "could" check for updates, but the downloaded updates would not install because the versions would not match the hacked versions.
Can anyone confirm?
I just assumed you would be able to install, but it would wipe out root access and revert it to stock... i'm probably wrong though
but it would theoretically download? maybe a quick battery pull and we're good to go...idk never been through the ota update process
Related
I recently purchased my Nexus S.
About a week ago from Best Buy.
It was on 2.3.1, and its been a week and I haven't received OTA, yet.
I have been searching and reading regarding about OTA, and I know
it goes by the IMEI #, and we just have to wait for it.
I do know there is a manual upgrade and it's easy, but I just want to
know if this phone can receive OTA or not.
I have checked in several times and no response of OTA or any sort
of notification, yet.
When I googled regarding about this, there are several, well, more than
several people out there who are in same situation as me, (2.3.1 & no OTA),
Considering that we're on 2.3.3 already, I was expecting to receive
OTA for 2.3.2 already (at least), but now this is starting to make me worry.
Anyone else can ease my mind?
Manual update will be my last solution to this problem, I just want to know
whether I will receive OTA anytime soon..
Also, just one more question I want to add.
Even after if I manually update to 2.3.3, and in the future 2.3.4 comes out,
I will still be able to receive OTA from Google, correct?
Because when I was searching for any case of..
2.3.1 -> 2.3.2 manually, then 2.3.2 -> 2.3.3 OTA, I didn't find any case of that.
If you guys can confirm anything regarding of this matter, it'd help me to just
upgrade my firmware via manual method.
Did you try using the 'checkin' function?
Yes, on my first post, I mentioned that I have checked in several times.
In fact, I checked in at least 2 times a day.
;(
I guess you will have to wait then, though I would recommend you to update manually. Even if you update manually, you still can receive OTAs in future.
Thank you very much for the fast response.
I already had the update file waiting.
Just booted into recovery and updated to 2.3.3
Things are looking good so far.
Glad I could help
Enjoy your new update.
Hello all,
I've read that there is a 2.3.6 update for the AT&T Skyrocket. I don't have this latest update and still have Android version 2.3.5. I also hate the check for update on this phone. Unlike other phones I've had like HTC and on other carriers, I can check for updates anytime I want. Here, I can only check once and it will tell me to check again in 24hrs. WTF???
I keep running it every day but it does not find the OTA update.
My phone is rooted...
Thanks,
--mike
have you read around on the forums? the update was pulled and/or only available to select IMEIs...
there is no OTA update as of this moment. if you want to move to 2.3.6, flash a rom. otherwise, sit tight
Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
ExcludedDroid said:
Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
Click to expand...
Click to collapse
Best way to check is to go into Settings/About Phone/Software Update. If it force closes then you're all set. Renaming or uninstalling "smd 1.0" causes the phone to not actively poll for future OTAs from that moment on. Using a file explorer, check in /cache and delete the update.zip for VRBMF1 cuz you deferred the OTA which means it saved to your phone already.
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
ExcludedDroid said:
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
Click to expand...
Click to collapse
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
xavierxxx2p said:
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
Click to expand...
Click to collapse
There is a touchwiz version, it just wasn't updated in awhile and it's pretty buried in the development section.
Sent from my SCH-I535 using Tapatalk 4 Beta
Just wondering if I'll be able to take an OTA update from 6.0 to 6.0.1 whenever it is available? I received a message saying a software update was available and when I told it to install it, it rebooted into TWRP, checked the current software for about 3 minutes, then rebooted? Upon looking, I am still on 6.0? I had the system check to see if there was still an update available, but it said there was nothing. Maybe it was just a radio update? I am anxiously awaiting the update so that I may install Xposed. Any input would be greatly appreciated :good:
AT+T US Unlocked
Rooted/S-off
6.0
1.10.502.3
You can't take OTAs with rooted phones and twrp. The OTA looks at the system partition and if anything is changed...it will not install.
You have to either take a backup somebody made with the OTA/stock basically. Flash it via TWRP. Or RUU back to the lastest for your phone. Then, take all OTA updates, then TWRP, Format Data, then SuperSU again, reboot...start/restore phone.
There is no easy way without Dev support/Custom Roms to get latest bases/OTAs right now without wiping/starting over somehow.
This is why having devs creating Roms is really a luxury. Because they already have the proven installer/Rom customized. They will then take OTAs/new bases, roll that into their Rom, and you just do an update/flash, like Viper, and not lose anything, and no need to wipe.
Likely never to happen with this phone since Devs really only work on the Mainline/Flagship M models, like M8/M9/M10 etc...
So now that I am rooted a can no longer receive OTA updates. Also, being a Sprint\Tmo device, I don't have "Local Upgrade" option.
Can someone tell me how I would now go about updating my device?
Do I simply wait for A11-based rom?
Do I need to remove magisk\modules in order to re-enable OTA?
Any help is appreciated.
I was actually about to ask this very question myself, the local update is missing on mine too, so that didn't change when you rooted? Maybe you can flash one of the stable releases they came out with recently? My question was would the global version work for our tmobile branded devices.
Also wondering wtf is up with tmobile cutting features out of the updates like shelf that dropped in July.
There is a guide to switch to global firmware.
It seems straight forward.
I would rather not.
If there was a stock rom image that we could simply flash via magisk or twrp, the process would be far simpler.
My guess is that for the method above to work, we will need to wait for A11 source code to drop.
Afterwards, we will likely see full A11 roms that we can use.
Ideally we would wipe system, data, cache. Flash rom. Wipe data again. Reboot.