Related
Hi everyone. So I rooted my captivate and enabled side loading. I used titanium backup to rid of the att bloatware. Im wondering what the easiest easy to unroot is. Also, does not having the bloatware after unrooting affect my ability to receive OTA updates? Thanks a lot!
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I don't think leaving it rooted will affect anything, not right now at least. Root can be seen as an admin account. If you had to intervene with the phone for some other reason, you'd have to root it again. When the updates start coming down the pipe and you weren't getting them, while everyone is, then I'd say there is something to be concerned about.
As far as unrooting goes, there are threads that touch on the subject and would be more helpful tham I on the subject.
So, I have heard that motorola looks for the bloatware that came on our phones when we look for updates. That being said, will this decrease our chances on cheesecake?
I for the longest time had much of the bloatware deleted off my phone. It's half the reason I root.
Until yesterday, when I had a little developer hiccup and had to flash the fxz.
This time I am keeping the bloatware on hoping to up my chances of finding that golden ticket in cheesecake.
All this to say, How "stock" should we really be while searching cheesecake to get the best chances?
Sent from my MB865 using xda premium
It should not affect cheesecake. Only when you go to install the update. Im on stock waiting for ics to drop. Im leaving my phone as is for now because i know as soon as ics is released ill be like a kid on Christmas day ready to install it.
Sent from my MB865 using xda premium
Ah, kid on Christmas is right.
The good news is that hopefully whoever gets it first will be smarty enough to post it here for the rest of us also.
Sent from my MB865 using xda premium
Bloated or not, it should have not affect the update process. In fact, I seem to remember FXZ'ing back to 2.3.5. and then rooting (jumping over the step to OTA to 2.3.6.) and checking for update after rooting. My phone found the 2.3.6. update, and I realized I had done this out-of-sequence. So, I FXZ'd again, OTA'd and then rooted. I have seen though that if you are rooted when an update appears, and after installing it, it will break root on your device. Just what I've seen/heard -for what it's worth...
Missing bloat will not have any impact on cheesecake, but it will prevent the update from actually installing once downloaded.
Motorola has checks in the OTAs to make sure that all of the bloatware is still on the phone, it does not give a crap about anything else, just that the bloatware is installed, and that you are listed as being on a stock ROM/build in the build.prop file.
Again all of this has noting to do with a cheesecake check since it is just logging into Motorola servers and doing a search for any update files for the edison phones (it gets that from your build.prop). If you have changed your phone to show as some other phone in the build.prop then change it back as that will make cheesecake not work properly.
Thanks guys. Just didn't want to hinder my constant search for the holy grail.
Sent from my MB865 using xda premium
It is apparent that verizon S3 enthusiasts will never be able to take an OTA, how do we disable them completely so there are no accidents?
Do you guys have root yet? Titanium backup> freeze everything Verizon (including kies) related. Especially the one that says "update".
Of course in ics you can disable a lot of bloatware w/o root. Go to apps long press on app of choice hit disable.
Make sure to hIt "stop" process first.
Freezing via TiBu is best .
freakboy13 said:
Do you guys have root yet? Titanium backup> freeze everything Verizon (including kies) related. Especially the one that says "update".
Of course in ics you can disable a lot of bloatware w/o root. Go to apps long press on app of choice hit disable.
Make sure to hIt "stop" process first.
Freezing via TiBu is best .
Click to expand...
Click to collapse
Root has been achieved but is probably 100% guaranteed to be broken by an OTA. Any enthusiast will depend solely on the dev community for updates for the life of the phone.
So, I have been hearing that a SGS3 OTA is on the way, and has begun rolling out on Sprint. I will be getting my vzw sgs3 tonight, should I be wary of installing this OTA? Do you think they already fixed the exploit even after less than 24 hours?
juntistik said:
So, I have been hearing that a SGS3 OTA is on the way, and has begun rolling out on Sprint. I will be getting my vzw sgs3 tonight, should I be wary of installing this OTA? Do you think they already fixed the exploit even after less than 24 hours?
Click to expand...
Click to collapse
I would err on the side of caution and not take any OTA's unless the devs approve. At the minimum right now we have root. Verizon OTA's on encrypted devices are notorious for breaking existing exploits. All OTA's will be repackaged by the devs into something we can use, so you gain nothing by taking an OTA. Fact of life with an encrypted device.
Not having a lot of luck finding the answer to this, anybody?
i happened to find this while just looking online although it seems like there are arguments against it and for it accross the table... im neutral as id much rather have an unlocked bootloader i am simply just posting this so everyone can see it and maybe share something to prove or disprove
http://www.gottabemobile.com/2012/07/16/verizon-wont-unlock-galaxy-s-iii-bootloader/
this says they wont release an update to unlock the s3
beeholtz said:
this says they wont release an update to unlock the s3
Click to expand...
Click to collapse
Verizon never made any sort of promise that they would unlock the bootloader. The rumor got started a month ago from transcripts of chats with ill-informed customer service reps who didn't know a bootloader from a barnacle. They chose to lock it, and they will not willingly reverse that decision. When our bootloader gets unlocked, it will be through the fine efforts of communities like this one. Depending on the type of exploit, I might not be surprised if Verizon then pushes an update to relock the bootloader, as has happened with some HTC phones in the past.
In general, never take the word of a CSR without a fair bit of skepticism, especially if it conflicts with VZW's official statements.
lazarus2405 said:
Verizon never made any sort of promise that they would unlock the bootloader. The rumor got started a month ago from transcripts of chats with ill-informed customer service reps who didn't know a bootloader from a barnacle. They chose to lock it, and they will not willingly reverse that decision. When our bootloader gets unlocked, it will be through the fine efforts of communities like this one. Depending on the type of exploit, I might not be surprised if Verizon then pushes an update to relock the bootloader, as has happened with some HTC phones in the past.
In general, never take the word of a CSR without a fair bit of skepticism, especially if it conflicts with VZW's official statements.
Click to expand...
Click to collapse
Correct me if I'm wrong but once and if the bootloader is unlocked we can just stay on that bootloader (unlocked) even if verizon does try to re-lock it correct? In a sense similar to s-off
Sent from my SCH-I535 using Tapatalk 2
niv3d said:
Correct me if I'm wrong but once and if the bootloader is unlocked we can just stay on that bootloader (unlocked) even if verizon does try to re-lock it correct? In a sense similar to s-off
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
IMO - Its just safe practace not to take any OTA updates until after the Devs got them fixed. Verizon could patch their own bootloader if they needed to - via an OTA. So, yes, you could stay unlocked (once it is unlocked anyway), so long as you stay away from OTAs .
i have a thunderbolt and in 9 days when i have an upgrade available on my account will be getting the s3. on my thunderbolt after i rooted i never even had to block updates i just straight up never got ota updates. is there a setting in the s3 that ill need to check or uncheck a box to not receive them after i root?
why are so many folks concerned about ota updates? The day one roots his/her phone OTA should be forgotten. The devs here will have all the updates we can possibly achieve and in alot more timely fashion.
droidstyle said:
why are so many folks concerned about ota updates? The day one roots his/her phone OTA should be forgotten. The devs here will have all the updates we can possibly achieve and in alot more timely fashion.
Click to expand...
Click to collapse
**** yeah!
Sent from my SCH-I535 using Tapatalk 2
if you actually took the time to read my post you would have noticed that i asked if there is a way to NOT RECEIVE OTA UPDATES as opposed to asking about receiving them. i will post that question in q and a when i get the phone thanks anyways
beeholtz said:
if you actually took the time to read my post you would have noticed that i asked if there is a way to NOT RECEIVE OTA UPDATES as opposed to asking about receiving them. i will post that question in q and a when i get the phone thanks anyways
Click to expand...
Click to collapse
I did read your post...my apologies since that post was not 100% directed towards you...I kind of hijacked your thread posting that for others to read lol. There has been 100 threads on here about "will I lose ota if I root".
A big cellphone company lied to us? It can't be. Haha sorry for the sarcasm but the way this phone has been going I think an unlock will come through the developers over the big companies. That means we'll have to pay up on that bounty.
Sent from my SCH-I535 using xda premium
ya my bad too i didnt mean to be a **** about it. i had some ahole customer i dont like helping come up today. fixing their computers and network just makes about anything else sound like more fun. im just stoked to get the phone soon but i also am getting it knowing about having a locked bootloader and the possibility of all those little quirks and issues that some people have and some dont. On my thunderbolt i rooted it not long after i got it and have flashed roms and kernels and radios etc until i find one i really like at the time. I'm figuring once the dev. edition comes out people will get it and verizon will then do the same thing on the next big deal phone that comes out in however many months.
I swear at this point, they're just sitting back in their chairs and cackling madly. Biggest trolls ever.
I think the "ota" talk only references people who are stock and take ota, get said-bootloader "fixed" by vzw, then want to mod afterwards. Then a new/different method will have to be used, whether it be Odin/rollback/whatever is come up with.
People already unlocked and rooted will be fine.
Sent from my Galaxy S3 using Tapatalk 2
I can't say i'm terribly surprised, Verizon seems content to violate whatever they want for their benefit. Just need to put the pressure to them.
I am not even concerned about the boot loader anymore. You can flash kernels with kexec cwm(6010), Odin new modems and the roms that synergy, bean and Nos are producing are just fantastic. Developers will find a way and there are some great ones on the SG3.
Sent from my SCH-I535 using xda premium
Rather doubt it
Doubt verizon will unlock the bootloader
anytime soon. For now we are left to
root use custom stock roms with some
themes or leave Verizon.
Cheers,
INC > TB > S3
azbobs said:
For now we are left to
root use custom stock roms with some
themes or leave Verizon.
Cheers,
INC > TB > S3
Click to expand...
Click to collapse
This is simply not true...there is plenty of aosp dev going on! we have 4 cm10 roms, 1 aokp jb rom, 1 paranoidandroid rom...the bugs these roms do have are not related to the locked bootloader. Its the same issues across multiple devices. 5min of research would of yielded these results...
Verizon is NEVER going to unlock the bootloader. Ever. You can quote me on that.
Sent from my SCH-I535 using xda premium
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
droidstyle said:
This is simply not true...there is plenty of aosp dev going on! we have 4 cm10 roms, 1 aokp jb rom, 1 paranoidandroid rom...the bugs these roms do have are not related to the locked bootloader. Its the same issues across multiple devices. 5min of research would of yielded these results...
Click to expand...
Click to collapse
Ya and they all break your phone and wipe out vital information like imei and/or permanently break data.
Sent from my SCH-I535 using xda premium
It's the Big Red SideShow starring Mr. Smoke & Mirror's Himself Lowell McAdams.
Verizon can burn in hell. I
Off topic, but is the volume really this quiet on this phone? I came from the OG like 2 weeks ago and it was literally double the decibels that this thing is putting out. I've heard about the volume+ app but is that the only way to increase volume? I'm still stock but plan on rooting n roming soon, perhaps one of them contains that dsp manager that cm7 base used to include?
Sent from my SCH-I535 using xda app-developers app
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.