Related
is i possible to keep my thunderbolt rooted after any future updates? can i disable updating all together? i don't want to loose my wifi tether option.
thanks
kings322 said:
is i possible to keep my thunderbolt rooted after any future updates? can i disable updating all together? i don't want to loose my wifi tether option.
thanks
Click to expand...
Click to collapse
Once you're rooted you shouldn't be getting any OTA updates (especially if you're running a custom ROM...most devs remove that menu or disable the auto check anyways.) If you do get prompted for an OTA update decline it as you can brick/unroot your phone if you install an OTA on top of a rooted phone.
Cubs2008 said:
Once you're rooted you shouldn't be getting any OTA updates (especially if you're running a custom ROM...most devs remove that menu or disable the auto check anyways.) If you do get prompted for an OTA update decline it as you can brick/unroot your phone if you install an OTA on top of a rooted phone.
Click to expand...
Click to collapse
If you are rooted on stock ROM, it will still let you know there is an update available, still decline inorder to keep root. evertyhing else is correct
Updated....ok Now What
I was Rooted, But returned to stock because of an issue with my screen.
Is Rooting Possible, since the June,2011 Update? if so do the same rules apply because you are downgrading at that point, and assuming my thoughts are clear...will there be a patch for the new radios the update installed?
After you root what you want to do is wait for a developer to release a rooted version of that build. Check the developer section for it. I would post you a link but I'm on my Thunderbolt.
Edit: http://forum.xda-developers.com/showthread.php?t=1160374
Shawn haz root said:
After you root what you want to do is wait for a developer to release a rooted version of that build. Check the developer section for it. I would post you a link but I'm on my Thunderbolt.
Edit: http://forum.xda-developers.com/showthread.php?t=1160374
Click to expand...
Click to collapse
Thanks Much, man I appreciate it. I will try the link, now the fun part Rooting all over again, ughhh...lol thank you again
Congrats to all those looking forward to the 4.1 OTA. I'm happy for you. However, I just got my Razr Maxx HD and I'm happy with it as it is.
If I root using these instructions: http://forum.xda-developers.com/showthread.php?t=1943851 will that stop my Maxx from getting the pending OTA?
If not, what else will I need to do?
Thanks in advance to all willing to help.
ThanksToXDA said:
Congrats to all those looking forward to the 4.1 OTA. I'm happy for you. However, I just got my Razr Maxx HD and I'm happy with it as it is.
If I root using these instructions: http://forum.xda-developers.com/showthread.php?t=1943851 will that stop my Maxx from getting the pending OTA?
If not, what else will I need to do?
Thanks in advance to all willing to help.
Click to expand...
Click to collapse
OTA aren't automatic... You have to accept the download. So just don't accept it. Easy enough.
EdwardN said:
OTA aren't automatic... You have to accept the download. So just don't accept it. Easy enough.
Click to expand...
Click to collapse
Thanks for the response, but I've been told OTAs can't be continually refused (like after the 5th decline, they will update automatically). You seem to be stating that if I decline the OTA, it will not update ever.
If I'm understanding you correctly and I decline the OTA, will it continually prompt me to do it?
ThanksToXDA said:
Thanks for the response, but I've been told OTAs can't be continually refused (like after the 5th decline, they will update automatically). You seem to be stating that if I decline the OTA, it will not update ever.
If I'm understanding you correctly and I decline the OTA, will it continually prompt me to do it?
Click to expand...
Click to collapse
Looks like there's a few ways to block OTA updates. Installing a custom rom does, but you want to keep it stock, obviously.
You can edit your build.prop file to "spoof" the current version so it doesn't try to update you. Do a search for editing build.prop, I don't have the exact details on hand.
The specific line is ro.build.fingerprint= but you'll have to wait until someone has the update installed to find out what the new information after the = is.
EdwardN said:
Looks like there's a few ways to block OTA updates. Installing a custom rom does, but you want to keep it stock, obviously.
You can edit your build.prop file to "spoof" the current version so it doesn't try to update you. Do a search for editing build.prop, I don't have the exact details on hand.
The specific line is ro.build.fingerprint= but you'll have to wait until someone has the update installed to find out what the new information after the = is.
Click to expand...
Click to collapse
Those running the leak, would they have the correct "after the =" ?
ThanksToXDA said:
Those running the leak, would they have the correct "after the =" ?
Click to expand...
Click to collapse
The leak might not, but the soaktest should. I would imagine it'll be on some phones in the next few days. Just make sure you get the line from someone with the same provider.
Having said all this, I have my older Defy running JB and it's an improvement over ICS. I personally am looking forward to the update. I feel a little like they didn't do as much optimization on ICS as they could have just because they knew JB was coming soon after launch.
EdwardN said:
The leak might not, but the soaktest should. I would imagine it'll be on some phones in the next few days. Just make sure you get the line from someone with the same provider.
Having said all this, I have my older Defy running JB and it's an improvement over ICS. I personally am looking forward to the update. I feel a little like they didn't do as much optimization on ICS as they could have just because they knew JB was coming soon after launch.
Click to expand...
Click to collapse
Thanks for the help.
I decided to wait over night to see if I recieved any other options here. This morning I found an "An update has been downloaded..." message.
EdwardN said:
OTA aren't automatic... You have to accept the download. So just don't accept it. Easy enough.
Click to expand...
Click to collapse
Wrong! Wrong! Wrong!
I still had the option to install now or later. I chose later.
Edit for better info: The download, "Update (0.7.2.en.US) has been downloaded and is ready to install."
Can I still root using the prev mentioned method if I install this?
Any other options to prevent the JB OTA?
ThanksToXDA said:
I decided to wait over night to see if I recieved any other options here. This morning I found an "An update has been downloaded..." message.
Wrong! Wrong! Wrong!
I still had the option to install now or later. I chose later.
Edit for better info: The download, "Update (0.7.2.en.US) has been downloaded and is ready to install."
Can I still root using the prev mentioned method if I install this?
Any other options to prevent the JB OTA?
Click to expand...
Click to collapse
My error, I meant to say "You have to accept *to install* the download." I did read that it'd download anyway, unless you already had the version spoof in place. If you intend to root, root first, then use VooDoo OTA Rootkeeper (from market) to backup your root before update, and restore after update.
ThanksToXDA said:
Congrats to all those looking forward to the 4.1 OTA. I'm happy for you. However, I just got my Razr Maxx HD and I'm happy with it as it is.
If I root using these instructions: http://forum.xda-developers.com/showthread.php?t=1943851 will that stop my Maxx from getting the pending OTA?
If not, what else will I need to do?
Thanks in advance to all willing to help.
Click to expand...
Click to collapse
Not sure the reluctance to dl jb. It's faster than Ics, and you can keep root.
Sent from my DROID RAZR HD using Tapatalk 2
JB is nothing but pure improvement. Absolutely no downsides. That's why people are foaming at the mouth for it. And 0.7.2.en.US is just an ICS update.
BinarySauce said:
0.7.2.en.US is just an ICS update.
Click to expand...
Click to collapse
I appreciate the info on (0.7.2.en.US)
From another forum, I found this advice:
"I renamed my OTACERTS.ZIP file to otacerts.zip.bak ... and this stopped updating on my DI2.
The OTACERTS.ZIP file can only be modified by ROOT users, and it's located in: system/etc/security/otacerts.zip"
Would this work?
ThanksToXDA said:
From another forum, I found this advice:
"I renamed my OTACERTS.ZIP file to otacerts.zip.bak ... and this stopped updating on my DI2.
The OTACERTS.ZIP file can only be modified by ROOT users, and it's located in: system/etc/security/otacerts.zip"
Would this work?
Click to expand...
Click to collapse
yes, but the problem with that solution is that it will keep downloading the update over and over, it'll just fail the certification process prior to install, and it'll eat your battery doing all the repeated downloads. You are welcome to try it though, and report back your results please.
EdwardN said:
yes, but the problem with that solution is that it will keep downloading the update over and over, it'll just fail the certification process prior to install, and it'll eat your battery doing all the repeated downloads. You are welcome to try it though, and report back your results please.
Click to expand...
Click to collapse
LOL, I'll take your word on this one (thanks again).
OK, next idea: Use Tit Backup to freeze updater.apk
or
FOTA Kill
What do you think???
I By now everyone must be aware that Lollipop has a new way of checking for system mods that will prevent rooted devices from taking OTAs. Has anyone thought through what the easiest and best procedure will be for updating the firmware going forward? I've applied the lollipop OTA but have been holding back on root until I have a firm hold on how updates will work. I feel there must be many less technical people out there with the same concerns.
From Android Police:
With Lollipop, this has all been turned on its head because now, the OTA script no longer patches individual files. Instead, it patches the system block directly and treats it as one enormous blob. Here's a look at the update script in a recent Nexus 9 OTA:
image
From a technical standpoint, the reason behind the change has to do with verified boot, which was first introduced in KitKat. Even though Google has yet to enable this feature on a Nexus device, this move seems to indicate that the company could be preparing to go that route in the future.
Even outside of verified boot, though, it makes all the sense in the world to do OTAs this way. Patching the system block directly is far faster than trying to patch a lot of individual files. That said, if you're one of those who like to tinker with your devices, you'll have to flash a completely stock system image before applying an update because changing anything by so much as one byte will throw off the signature and make it so the OTA will fail.
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
Also here's chain fire....
http://forum.xda-developers.com/showthread.php?p=36316945
Does it matter when we have access to the factory images?
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
EddyOS said:
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
Click to expand...
Click to collapse
That's not at all what I'm reading. I'll post links later when I get home
Edit: see updated OP
/facepalm
I wrote a thread about other ways to update. Its in my signature
[Deleted]
DamnItLukasz said:
I don't know what that link says but thats not true lolz
Rooted and I got the OTA 3 days ago, just flashed stock 4.4.4 kernel over ElementalX et voilá.
Click to expand...
Click to collapse
The OTA you got was lollipop but it was applied to kitkat. This is about post kitkat. Or maybe it wasn't lollipop but to my knowledge there hasn't been an OTA yet released that updates lollipop
NCguy said:
The OTA you got was lollipop but it was applied to kitkat. This is about post kitkat.
Click to expand...
Click to collapse
Ups, forgive me then
Altrezia said:
Does it matter when we have access to the factory images?
Click to expand...
Click to collapse
For the less skilled hacker who doesn't want to wipe it requires more knowledge, more risk and more reliance on modified OTAs, and 3rd party stock builds. Otherwise they're into dirty flashing and that requires more skill and knowledge.
rootSU said:
I wrote a thread about other ways to update. Its in my signature
Click to expand...
Click to collapse
I'll have a look, thanks. That's really what I was hoping this thread would be about since it looks like plain OTAs may be out.
EddyOS said:
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
Click to expand...
Click to collapse
please read updated OP
NCguy said:
please read updated OP
Click to expand...
Click to collapse
That article is for the Nexus 9. People on here have successfully updated to 5.0 from 4.4.4, with root, by just sideloading the OTA in the stock recovery. If not, just flash the factory image but leave out the userdata partition
EddyOS said:
That article is for the Nexus 9. People on here have successfully updated to 5.0 from 4.4.4, with root, by just sideloading the OTA in the stock recovery. If not, just flash the factory image but leave out the userdata partition
Click to expand...
Click to collapse
It mentions the N9 only because it was the first 5.0 device that was officially released.
I mentioned before this problem is going to exist for updates to devices that already have lollipop, not for those updating from kitkat to lollipop.
rootSU said:
I wrote a thread about other ways to update. Its in my signature
Click to expand...
Click to collapse
Excellent post. With your level of experience you must be familiar with the problems stated in the Android police article regarding the new way google will be checking for system mods before processing the OTA?
NCguy said:
Excellent post. With your level of experience you must be familiar with the problems stated in the Android police article regarding the new way google will be checking for system mods before processing the OTA?
Click to expand...
Click to collapse
I haven't read it yet to be honest. I'm not an OTA fan, so I don't spend much time reading up on it. I will though, at some point and update the thread. There is also an OTA help-desk thread but I haven't read that yet. Apparently latest OTA doesn't work with custom recovery either
Am i not getting OTA of 6.0 cause my bootloader is unlocked or is 6.0 not out yet for OTA? I know the images are i just want the OTA and ill wait for it or is unlocked BL keeping me from getting the OTA?
cell2011 said:
Am i not getting OTA of 6.0 cause my bootloader is unlocked or is 6.0 not out yet for OTA? I know the images are i just want the OTA and ill wait for it or is unlocked BL keeping me from getting the OTA?
Click to expand...
Click to collapse
No, it's not because the bootloader is unlocked.OTA are sent in "waves" so the servers won't get overwhelmed.So it's just a matter of time until you will gey it too.
Pretoriano80 said:
No, it's not because the bootloader is unlocked.OTA are sent in "waves" so the servers won't get overwhelmed.So it's just a matter of time until you will gey it too.
Click to expand...
Click to collapse
Great ty what if phone was rooted would that stop OTA`s? Just curious im not rooted. Is the OTA suppose to be released with Gapps included do you know? There are an awful lot of people not being able to recieve gapps the right way. I hear location doesnt work and some other stuff but maybe thats a handful of people
I don't think the root prevent a device receiving the OTA,but it might cause the OTA installation to fail,so it's always best to disable root before updating.
I didn't used the OTA to update my device,so I can't say if there's any issue with it,but I know people that updated via OTA and it was all fine.
I have a rooted device with twrp recovery. Despite of what people think, I get this update. I just replace twrp recovery to stock and flash . This is amaze me. In general, my location also doesn't work also. There is solution?
The Joke(r) said:
I have a rooted device with twrp recovery. Despite of what people think, I get this update. I just replace twrp recovery to stock and flash . This is amaze me. In general, my location also doesn't work also. There is solution?
Click to expand...
Click to collapse
That seems to be a major bug there are so many talking about location not working or its in another place in settings. Not sure where cause i dont have my phone right now. Im sure there will be a workaround soon
So i am running 8.0 with the R16NW.N950USQU3CRAF Update, and i am having a hard time getting the OTA update that was recently launched. (changed dates to check for software updates and rebooted with no luck).
Will i need to downgrade back to Nougat in order to get the Official 8.0 update?
You won't get yesterday's OTA unless you are running the previously released AT&T OTA which is BRA8 I believe (someone correct me if I'm wrong). So yes, flashing back to what people here are calling "stock" would allow you to get recent OTA.
jack man said:
You won't get yesterday's OTA unless you are running the previously released AT&T OTA which is BRA8 I believe (someone correct me if I'm wrong). So yes, flashing back to what people here are calling "stock" would allow you to get recent OTA.
Click to expand...
Click to collapse
Happen to know if there is a way to do it other than using Odin?
mcnairp86 said:
Happen to know if there is a way to do it other than using Odin?
Click to expand...
Click to collapse
I'm not the really the person to ask about that. I haven't flashed my note 8. I just waited and took the OTA. I've just been following the threads out of habit from flashing phones since the beginning of the galaxy line. Sorry I can't be of more help for you.
jack man said:
You won't get yesterday's OTA unless you are running the previously released AT&T OTA which is BRA8 I believe (someone correct me if I'm wrong). So yes, flashing back to what people here are calling "stock" would allow you to get recent OTA.
Click to expand...
Click to collapse
mcnairp86 said:
Happen to know if there is a way to do it other than using Odin?
Click to expand...
Click to collapse
Jackman is correct (Although being on the newer 3BRB2 would be best)
Odin is going to be the ONLY way to get back to stock.
You can go HERE for links and such.
Even when the 3CRC1 Odin files become available, Odin will still be the only option to get back to stock