I am new to the Dream, I just got mine on Friday. I have now got root access. I want to know when the RC31 comes out, if I update via t-mobile will it kill root access, or will I need to hold off until a modded FW comes from JesusFreke.
Thanks
Tim
Yes,if you update via t-mobile,it will remove root. Its best if you wait for a modded FW if you want root.
Thats what I figured. thanks for the info.
otto888 said:
Yes,if you update via t-mobile,it will remove root. Its best if you wait for a modded FW if you want root.
Click to expand...
Click to collapse
While I agree that it would probably be best to not upgrade right away, we don't know anything about RC31 yet. The only thing I think that has been officially announce is that it would contain elements of cupcake. I'm not even sure how official that was either. Let's try not to speculate.
Echoing what's been said above, being that we know NOTHING about the next OTA update, it will likely (at the very least) remove root access from a JF RC30 device. It might even prevent you from backflashing to RC29 to get back to the modified JF RC30. So whatever you do, DON'T let your phone update until the new version is examined and tested by others, or you might find yourself with a permanently locked down G1.
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
Correct, or the update will fail, can't remember which one.
So I guess it would be safe to say....
STAY TUNED!!! Same XDA time, Same XDA channel
Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
I love when modders do that, keeps me from doing something stupid
Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
I am not entirely convinced of this.
I had a chat with a co-worker about this and he said "well no, between the engineering bootloader and the test keys, there is no way the modded rc30 can be OTA'd".
I tossed this at him.
What if tmo decided to setup something like this...
check what you are running.
check what keys you are running.
send an update that does something along the lines of...
if your image is equal to or less than rc30 and your keys are either ota or test then update.
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
I imagine that anyone with ADP1 or ADP1.1 will be left alone as it would be a bad move to screw with your developer audience; but I could be wrong. They could go after anyone who doesn't have an official ADP image (non JF kernel)...
I have no idea what they are really planning but it does seem that this could be a "check mate" pivotal move if they wanted to play that card this early in the game.
Of course, it could be as simple as "let's leave everyone where they are and only focus on security moving forward" which is most likely going to be the case....
deprecate said:
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
Click to expand...
Click to collapse
The running theory is that T-Mo will not do this because all devices with the standard ota-keys installed will also get the "targeted" test-key rc31, reboot, and then freak out because the update is signed with a mismatched key.
The way the update service works is the device periodically sends its Android build fingerprint to Google servers. If the fingerprint is of a supported device (in this case Dream) and the build number is lower than the most recent, then the server may push an update back to the device. Since JF modified builds report an official fingerprint, there is no way for the server to distinguish between a modified and unmodified RC30.
However, i've seen enough in information technology to know that very little is truly "impossible". Based on what is currently known though, it is highly unlikely that Google/T-Mo/HTC could forcibly reroot a modified RC30 G1 at this time.
I really don't see T-mobile doing this. Why would they? At this point people with root don't have any real advantage over normal phones other than techie stuff. We are not pirating software or getting free minutes. Unless it becomes an issue I think T-mobile will leave us alone.
speoples20 said:
I really don't see T-mobile doing this. Why would they? At this point people with root don't have any real advantage over normal phones other than techie stuff. We are not pirating software or getting free minutes. Unless it becomes an issue I think T-mobile will leave us alone.
Click to expand...
Click to collapse
There is no piracy because apps are free. Once support for paid apps arrives, piracy will start. (Someone in this forum started a thread wondering how to do that). It happens in all software platforms, and it's going to happen with Android also. Note that I don't endorse piracy (for some weird reason people think that developers are the only guys who should work for free), less in these environments where there are lots of applications than are made by individuals, not big companies, but this won't prevent piracy to come to Android.
Anyway, if I were TMob I would try to remove root from as many devices as I can (which obviusly does NOT include ADP1, as it has nothing to do with TMob),
not just for the piracy, but to keep users from breaking their devices due to doing stupid thing with a rooted phone.
T-Mobile motivation to wipe devices using test keys
T-Mobile could have a motivation to wipe devices by providing an update using test keys. Tethering is against the terms of service and can only be done if you have root. They could take the *IAA approach and say that any one who has root wants to be able to tether and break their TOS (since tethering is the biggest advantage to root right now). If enough people tethered it could cause a problem as they may not have the bandwidth to accommodate what people want to do when tethered. BTW, for all who tether use this addon for firefox and change your user string to match the android's browser (https://addons.mozilla.org/en-US/firefox/addon/59) so they can not tell.
Is there a way to make new keys that are different from the dev keys, or is google the only ones who can do that?
Doing an update using test-keys sounds a bit desperate to me.
Moreover, as jashsu said, it seems that there is no way that currently TMob could know if you were using a G1 with an stock R30 or JF's one, so if they offered the update with testing keys, stock R30 phones would reject it.
They could try some tricks as offering the update with test keys for a while, then switch to another with official keys, then came back to test keys, etc...
But as I said, this sounds desperate and sloppy.
Mi bet is that they would try to fix the downgrade issue, and will use the official keys, so anyone with JF will be safe.
Anyway (I have an ADP1, so I've not receive any update from now), I though that, when an update was available, the user was asked whether to update or not.
clarke.hackworth said:
If enough people tethered it could cause a problem as they may not have the bandwidth to accommodate what people want to do when tethered.
Click to expand...
Click to collapse
This is not a problem. They will simply throttle you down to EDGE if they consider you are using up too much bandwidth (tethering or otherwise).
Is there a way to make new keys that are different from the dev keys, or is google the only ones who can do that?
Click to expand...
Click to collapse
Anyone can create signing keys. Not sure what you're getting at though.
clarke.hackworth said:
Tethering is against the terms of service and can only be done if you have root.
Click to expand...
Click to collapse
It is? Where? Last I remember I saw the CEO say it wasn't and it is allowed. And that they wouldn't stop it or prevent it in anyway.
deprecate said:
I tossed this at him.
What if tmo decided to setup something like this...
check what you are running.
check what keys you are running.
send an update that does something along the lines of...
if your image is equal to or less than rc30 and your keys are either ota or test then update.
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
Click to expand...
Click to collapse
It still wouldn't apply the update, even if they sent out an OTA signed with test keys. The OTAs are verified against the certificate present in /system/etc/security/otacerts.zip.
Since that file has been deleted, it wouldn't be able to verify the OTA, no matter how it was signed.
JesusFreke said:
It still wouldn't apply the update, even if they sent out an OTA signed with test keys. The OTAs are verified against the certificate present in /system/etc/security/otacerts.zip.
Since that file has been deleted, it wouldn't be able to verify the OTA, no matter how it was signed.
Click to expand...
Click to collapse
Good point. That completely escaped me. But wouldn't it be entertaining to see an official rc31 sent out with your certs as the target
deprecate said:
Good point. That completely escaped me. But wouldn't it be entertaining to see an official rc31 sent out with your certs as the target
Click to expand...
Click to collapse
Very entertaining
Related
Hi,
Firstly, I have read many of the threads on here, so I've done my searching but want a bit of advice:
Can anybody give any real reasons why I'd want to go custom? From what I can see there is no advantage at the moment (Considering that all new features, eg, Cupcake) will be released officially at some point. Also worth considering is that if something good on the custom scene arrives in the future by then I'm sure many devs/hackers will know how to root the phone again.
For the moment, is there any advantage for a casual user to make the switch to custom?
My new G1 arrives soon, and after taking part in the PSP custom scene I'm keen to see any reasons why I should go custom on the G1... I don't want to do it for the sake of it (If it offers little to no advantage, but risk) but likewise I want to make sure I'm not misunderstood and perhaps there really is some reason?
Thanks.
Big reason I went with a custom image was to allow tethering on my phone using iptables.
That and the fact I get a little glow deep down knowing my phone is free!
Thanks for the reply.
With those in mind, any other reasons I should grab custom rather than the OTA update?
Cheers.
freedom, plain and simple. There is a lot of stuff that cannot be done without a modded system. For example, the themes. If you are happy with what you have, there is no problem in keeping it.
I wouldn't customize my new phone right away. It's always a good idea to wait it out and get familiar with the phone and all it's capable of doing first. Perhaps later you can get into customizing it and all the other mods.
Imyman said:
I wouldn't customize my new phone right away. It's always a good idea to wait it out and get familiar with the phone and all it's capable of doing first. Perhaps later you can get into customizing it and all the other mods.
Click to expand...
Click to collapse
I would - who knows when T-Mobile will issue an OTA update to block downgrading?
didnt think about that...
thats true, I'll bet dimes to dollars the next update stops downgrading
if history is a predictor of the future, the Tmob will not allow the this fun to continue unchecked.
I say do it while you can, it wont last forever.
They said an update would come out "after the american holidays" and I say the downgrading will stop then, look how fast the lockdown came, the first update(RC28) was slow to come out, but once the exploit was in the wild, RC30 was out in a few days...
look on the brightside it may just get us an update sooner
bhang
...and since both tmo and google know the keys that the "rooters" around here are using, what's to stop them from sending out separate, test-key-signed OTAs to stop what's already been going on?
I wouldn't expect it from Google (if they did, I'd call Android "tango uniform") but from tmo, I'd expect anything.
Ok rooting gives you freedom. To do what you want with your property??
beartard said:
...and since both tmo and google know the keys that the "rooters" around here are using, what's to stop them from sending out separate, test-key-signed OTAs to stop what's already been going on?
I wouldn't expect it from Google (if they did, I'd call Android "tango uniform") but from tmo, I'd expect anything.
Click to expand...
Click to collapse
your a negative person i feel. I dont think Tmo can force an update on my phone when the keys are renamed as told????
beartard said:
...and since both tmo and google know the keys that the "rooters" around here are using, what's to stop them from sending out separate, test-key-signed OTAs to stop what's already been going on?
I wouldn't expect it from Google (if they did, I'd call Android "tango uniform") but from tmo, I'd expect anything.
Click to expand...
Click to collapse
the lack of otacerts.zip prevents it. no otacerts.zip -> no ota will pass sig check.
note: the ADP1 version still has otacerts.zip. it contains the test-key. I didn't delete it from ADP1 because it might still be useful to receive OTAs from google for the ADP1.
JesusFreke said:
the lack of otacerts.zip prevents it. no otacerts.zip -> no ota will pass sig check.
Click to expand...
Click to collapse
Hence once android source is completely public you wont need you could in theory have JFoid but that would be a lot of work. I could sit on rc30 with overlay mods until someone beside google by tmobiles hand forces what we want on our Devices. Contract or not they are ours to do with what we want. especially if you paid full price for your device...
Thanks for so many replies.
I'm sorry if I'm being stupid here, but alot of people say to go custom just because I should be able to have full access to my own device. Sounds great and I can understand that viewpoint... I'm just curious though - Say I "have" full access... At this time what exactly does that let me do? This is the thing, I'm surely not understanding everything correctly for all that I can see (Mainly) that it allows you to do is put your own firmware on, add a new boot image and tether. I can see people are fond of doing this "because they can do" but to the average user is there anything that I cannot do with the original that custom can do?
Cheers!
Installing themes for one thing. That seems to be quite popular with average users
You can also use droidsans to get the autorotate feature. And soon, who knows what will happen in a mo or 2.
802.1X support via wpa_supplicant is one reason to get root. Some of us are on university campuses where the only wifi is WPA Enterprise. Though G1 hardware supports this, there is no UI for it and root is needed.
My favorites so far (and I've only had root for a day)...
1. Tethering.
2. Installing the new autorotate browser, if you don't feel like waiting for an update.
3. Busybox (thanks to Jesus Freke.)
4. You might want to theme it, I like it the way it is though with the Ibex background to match my computer.
Well, I just realized that I jumped into flashing my G1 and getting root access before I was ready/before it was necessary. So now I want to go back to RC33 official firmware, but now since i'm rooted, the official RC33 update.zip file won't work. So i now have a rooted RC29 official firmware, how do I unroot and get back up to RC33?
ogwilson said:
Well, I just realized that I jumped into flashing my G1 and getting root access before I was ready/before it was necessary. So now I want to go back to RC33 official firmware, but now since i'm rooted, the official RC33 update.zip file won't work. So i now have a rooted RC29 official firmware, how do I unroot and get back up to RC33?
Click to expand...
Click to collapse
Have you heard of the word search?Do some work then being lazy.
Funny. I searched google, came across 2 threads of this very same nature filled with people telling us "lazy folks" to google and search. I also searched the forums directly, same threads and no other threads I could find related to this. And on google, I tried multiple search terms and phrases and noone had a definitive answer, if at all.
So please stop saying "search and stop being lazy" and just help, because you don't know if we all have tried to search or not. Perhaps if you help someone, we can actually come up fruitful in our search results.
http://lmgtfy.com/?q=g1+android+unroot
first entry
here are those threads in question:
http://forum.xda-developers.com/showthread.php?t=478856
http://forum.xda-developers.com/showthread.php?t=478873
and i couldn't simply reply to the threads because the mods were so quick to close them. Seems like everyone here has something against helping people restore to factory than upgrade to custom.
sputnik99 said:
http://lmgtfy.com/?q=g1+android+unroot
first entry
Click to expand...
Click to collapse
Well, seeing as how I already stated that I did indeed try to google using multiple search terms and phrases, then you might assume I already came across that result. I did indeed come across that result and I've already tried that method. If you would actually read instead of being so quick to judge my ability to find information, upon trying to reinstall paid apps and manually updating to RC33, it failed, meaning that the phone is somehow still rooted and that I'm not sure what to do at this point. I'm stuck at what looks to be like the official RC29 with no way to manually update and I cannot get my paid apps off of the market still (nor are they showing up).
Hell, I'm not even sure if this pertains to the fact that the phone was rooted or not, but it certainly isn't what happened before I rooted (where I was able to successfully update to RC33 and download paid apps from the market as well as view them)
Now please, read that and see that I have tried all that I can from the little information that is out there. Don't think that I don't appreciate the dev community here, but you tend to only care and only help when it comes to flashing phones, not restoring them.
why bother
it doesnt make a darn bit of difference, it just taking out crap that may in the future stop you from doing somthing you want to do, the phone doesn't work any differently, rooted or un rooted, I just can't think of a reason why somebody would WANT to go back, this is probably the cause of the resistance you feel, not a conspiracy to keep rooted phones, just that way...ROOTED
I'd say just don't bother and don't go typing in commands like a madman, and everything will be OK.
it seems that JF is dedicated to continue his work on the test signed updates, why do somthing that makes no difference? Just be lazy, or spend that time reading up on common linux commands.
bhang
bhang said:
it doesnt make a darn bit of difference, it just taking out crap that may in the future stop you from doing somthing you want to do, the phone doesn't work any differently, rooted or un rooted, I just can't think of a reason why somebody would WANT to go back, this is probably the cause of the resistance you feel, not a conspiracy to keep rooted phones, just that way...ROOTED
I'd say just don't bother and don't go typing in commands like a madman, and everything will be OK.
it seems that JF is dedicated to continue his work on the test signed updates, why do somthing that makes no difference? Just be lazy, or spend that time reading up on common linux commands.
bhang
Click to expand...
Click to collapse
its not that at all man. i cant even get my paid apps back. i bought the apps because i really liked them and used them on a daily basis, so i dont want to just give them up just so i can say my phone is rooted. Thanks for the reassurance though,but until i can do soemthing really useful with root access (installing other OSs) thenim sticking to official unmodified and updated firmware
paid apps and rom flashes/upgrades
im not sure you will get your paid apps back, but little is known about how the paid apps work.
they may be keyed to imei, but it doesn't seem so or you wouldn't have had a problem, my theory is that there is no security ie: 1 guy pays and anybody can use the copy of the app he paid for, I dunno and I AM NOT TALKING ABOUT PIRACY.
I am just theorizing on how your paid apps will or will not follow your phone after flashes.
it should just keep a list of what you d/l'd attached to your gmail login, I like to see more talk about how the apps are secured, NOT ABOUT HOW TO CIRCUMVENT the security, but how the apps are tied to the buyer/phone/rom installed.
I swapped apps from one g1 to another via astro and the sd card but they were all free, it just so happened to be the day the paid apps debut.
no piracy talk, just any facts you may have as to the above questions
bhang
Side loading
Apparently there is an update that has to be pushed to your phone from AT&T, but hardly anyone has received it yet. People in this thread are working on adding this feature without the update. This method will allow you to install non android market apps, but so far it disables your mms capability.
http://forum.xda-developers.com/showthread.php?t=1111278
Free tethering/wifi hotspot
http://forum.xda-developers.com/showthread.php?t=980591
By changing a few settings, you can have tethering/use wifi hotspot without adding a tethering plan from AT&T.
Maybe we could add future developments to this thread as they become available. I like the idea of leaving my phone stock so that it will automatically update.
Are you talking about the "silent" OTA that enables side-loading?
If so, and if by hardly anyone, you mean "hardly anyone here on XDA," it may be because they are rooted or otherwise running a custom ROM that will prevent them from getting OTA updates.
If you mean hardly anyone here on XDA that is bone stock, well, that might be true. And it also might be true that the recently discovered method of enabling sideloading will help some people, who don't mind their mms broken until some workaround fixes it.
Or they can root, and be done with it. There's nothing that will ever be OTA that I would want to get OTA anyway -- it will be available here shortly after.
The only excuse people have to not root is that it *appears* to be difficult. It really isn't. You can enjoy the same exact phone with a stock ROM, but with the added perks that rooting brings. Yes, that includes sideloading. And SIM unlock. And no more bloatware.
However, if this sideloading trick can be perfected, and it will keep people who otherwise don't have the patience to root their phones and as a result would just screw them up, causing them to further not spend the time to read and search, instead firing off 1000's of redundant "Halp Me!" posts, then that's a good thing.
ehh I would just rather use adb.... (if I was stock)
mudknot2005 said:
ehh I would just rather use adb.... (if I was stock)
Click to expand...
Click to collapse
Or that. My friggin' rant post from hell was long winded enough for me to forgo mentioning much more.
mudknot2005 said:
ehh I would just rather use adb.... (if I was stock)
Click to expand...
Click to collapse
Yeah, OP, you should definitely include a link to the adb method, or the Sideload Wonder Machine method.
I used SWM to install Swype weeks before I got the AT&T non market option (which was a week before I rooted).
ST3ALTHPSYCH0 said:
Yeah, OP, you should definitely include a link to the adb method, or the Sideload Wonder Machine method.
I used SWM to install Swype weeks before I got the AT&T non market option (which was a week before I rooted).
Click to expand...
Click to collapse
The adb method for sideloading an app is already discussed in mudknot's stickied guide.
Supposedly there is still an update floating around for unknown sources. If I happen to get my hands on it I will post it.
That's the only reason I haven't updated the side loading part of the guide. If the update gets pushed to every phone with in the month then it would be obsolete quick. I might add it just to have the most information possible... Though I will not put this method on there, because there is no reason you should have to give something up to gain something (captivate anyone?)..
Still stock here, without the non-market update.
No issues at all using the SWM. I didn't like that whole stupid "dropbox" method mentioned. It's easier and faster to just to use "disk drive" mode to copy the apk files onto the PC.
mudknot2005 said:
Supposedly there is still an update floating around for unknown sources. If I happen to get my hands on it I will post it.
That's the only reason I haven't updated the side loading part of the guide. If the update gets pushed to every phone with in the month then it would be obsolete quick. I might add it just to have the most information possible... Though I will not put this method on there, because there is no reason you should have to give something up to gain something (captivate anyone?)..
Click to expand...
Click to collapse
Absolutely agreed. Your guide should be reserved for known methods that provide the desired result without sacrificing other functionality.
I really don't see what all the excitement is about, regarding this new method. I mean, side loading has been a non-issue for rooted devices from the start, now it's *officially* a non-issue, even for bone stock devices.
This new method might have been a useful workaround for stock phones before ATT changed course on sideloading, now not so much.
Searched and looked around in a few threads, but couldn't find a definitive/clear answer.
Recently bought an HTC Radar. Phone prompted that an update was available (I believe it's an OS update).
My question is should I be updating my phone at all if I'm hoping for an interop unlock?
From reading, am I right to assume OS updates should not affect future abilities to interop, but firmware/baseband updates would? Is there an easy way to figure that out?
I'm coming from an iPhone, so I still have this mindset of "to update or not to update..." when it comes to homebrew.
Thanks all!
Usually HTC updates disable the unlock but beware that it is also possible for updates to disable hacks and mods too. Do some research first. What update is it, does it say?
OS updates shouldn't affect the ability to unlock, correct. On the other hand, we can't currently interop-unlock HTC gen2 phones anyhow, so at this point it doesn't matter much. I suppose firmware updates might make it harder to do so in the future, but if nothing else we can always tell people to roll back too. I suggest you keep your backups around (move or copy them to a folder with a different name so they don't get overwritten; they're stored in "%localappdata%\Microsoft\Windows Phone Update").
sinister1 said:
Usually HTC updates disable the unlock but beware that it is also possible for updates to disable hacks and mods too. Do some research first. What update is it, does it say?
Click to expand...
Click to collapse
Thanks. The phone came with stock 7.5, and the update prompted is 7.10.8107.79. I went ahead and updated regardless because the keyboard issue was driving me nuts.
GoodDayToDie said:
OS updates shouldn't affect the ability to unlock, correct. On the other hand, we can't currently interop-unlock HTC gen2 phones anyhow, so at this point it doesn't matter much. I suppose firmware updates might make it harder to do so in the future, but if nothing else we can always tell people to roll back too. I suggest you keep your backups around (move or copy them to a folder with a different name so they don't get overwritten; they're stored in "%localappdata%\Microsoft\Windows Phone Update").
Click to expand...
Click to collapse
Thanks. Done and done.
I read on cnet last night that Verizon would be sending an update for all GS3 users and, sure enough, I was prompted for the update for an update morning. (5/30/2013)
I am running stock 4.1.2 rooted.
Does anyone know if this is safe for me to apply? Will I lose root?
Thanks!
yep
You will lose root and if you have a custom recovery (twrp for instance) it will be overwritten. You will also get a "update failed" message. However, the update actually will succeed. You can reroot the same way you did before (unlock bootloader, root, install custom recovery if desired). I was surprised that the OTA was even available for rooted/custom folks. There will be a couple new apps installed, one dealing with CallerID which will force your 4G and WiFi to both be on - freezing that new app will fix that issue too, search the forums for details.
Goddrick said:
I read on cnet last night that Verizon would be sending an update for all GS3 users and, sure enough, I was prompted for the update for an update morning. (5/30/2013)
I am running stock 4.1.2 rooted.
Does anyone know if this is safe for me to apply? Will I lose root?
Thanks!
Click to expand...
Click to collapse
gozirra said:
You will lose root and if you have a custom recovery (twrp for instance) it will be overwritten. You will also get a "update failed" message. However, the update actually will succeed. You can reroot the same way you did before (unlock bootloader, root, install custom recovery if desired). I was surprised that the OTA was even available for rooted/custom folks. There will be a couple new apps installed, one dealing with CallerID which will force your 4G and WiFi to both be on - freezing that new app will fix that issue too, search the forums for details.
Click to expand...
Click to collapse
How are you surprised about the OTA being available for rooted phones? You don't make any sense with that comment as the update is just that an update. Verizon doesn't know which customers have rooted their device just that you have a device that needed to be updated.
Because thats the way it always was back when I had my original Incredible? A lot of people were surprised that the update was available to them, I'm not a minority here. No reason to be rude.
jmxc23 said:
How are you surprised about the OTA being available for rooted phones? You don't make any sense with that comment as the update is just that an update. Verizon doesn't know which customers have rooted their device just that you have a device that needed to be updated.
Click to expand...
Click to collapse
gozirra said:
Because thats the way it always was back when I had my original Incredible? A lot of people were surprised that the update was available to them, I'm not a minority here. No reason to be rude.
Click to expand...
Click to collapse
I am not being rude just stating the fact that Verizon doesn't know your phone is rooted in fact all companies don't know what you did to your phones until something bad happens to it. I will also add that the update will be pushed regardless if you're rooted or not the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.
jmxc23 said:
I am not being rude just stating the fact that Verizon doesn't know your phone is rooted in fact all companies don't know what you did to your phones until something bad happens to it. I will also add that the update will be pushed regardless if you're rooted or not the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.
Click to expand...
Click to collapse
Funny I did not see him mention anywhere that Verizon knew anything. His experience with a previous phone was that for some reason after rooting etc. his phone did not receive OTA updates. Whatever the reason, instead of being rude, you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
ghostboa said:
Funny I did not see him mention anywhere that Verizon knew anything. His experience with a previous phone was that for some reason after rooting etc. his phone did not receive OTA updates. Whatever the reason, instead of being rude, you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
Click to expand...
Click to collapse
Okay I have corrected myself like you have so eloquently posted I don't see the need to defend him if I already like you stated told him finally the reason. I already know that I should have done it sooner and like I normally do correctly fall back and respond in a normal tone. I unlike others am self aware of what I do and make an effort to correct any wrongs that I have caused. I don't filter myself when I post my thoughts so they can come across
as rude depending on your sensitivity level the difference is that I don't insult people nor belittle them in any way. I can only imagine how you or anyone will react if I was a total jackass.
ok then
Thanks for the explanation. follow-up question - if Verizon doesn't "know" then what is with the "unauthorized software discovered, call Verizon" popup that so many people have reported? Or the infamous yellow triangle? I assumed (yeah I know the cliche) that Verizon in fact DID "know" otherwise that wouldn't have happened. Simple mistake based on past experience, sorry.
As a side note.. If you have Titanium you can freeze SDM 1.0 and you won't get those updates
gozirra said:
Thanks for the explanation. follow-up question - if Verizon doesn't "know" then what is with the "unauthorized software discovered, call Verizon" popup that so many people have reported? Or the infamous yellow triangle? I assumed (yeah I know the cliche) that Verizon in fact DID "know" otherwise that wouldn't have happened. Simple mistake based on past experience, sorry.
Click to expand...
Click to collapse
This is completely unrelated to OTAs though. That warning is solely because of the secure bootloader on the Verizon GSIII. That warning is built into the system to pop up whenever you try installing software to the phone without having the prerelease bootloader in place. Verizon and Samsung intentionally made this model GSIII more difficult to install custom software onto or to make it a more secure device, depending on how you look at it. It's a business decision at the end of the day.
Sent from my SCH-I535 using Tapatalk 4 Beta
Probably business related as they don't want to be the first company to have an worldwide malware problem on their devices.
ghostboa said:
...you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
Click to expand...
Click to collapse
That's the key (at least in my experience with HTC phones). I can't remember the name of the file, but it was one file that you could rename and the phone would not check or ignore OTA updates that were pushed by the carrier.
i downloaded the update the other day by mistake as it bricked my phone. im rooted only and stock. i know its going to keep forcing the update thru, is there anyway i can get the update to go thru successfully without bricking my phone again?
You didn't brick your phone at least not a hardware brick.