Related
How would they know this?
I had to chat with their online CS about replacing my phone that seems to have a defective digitizer (sometimes it registers inputs when I'm not touching it and inputs in places other than where I touch it). They asked me what software number I'm running, which is 1.55.605.2. I'm guessing that number somehow denotes if my bootloader is unlocked?
They didn't seem to care though and told me to just re-lock my bootloader before I send the phone back to them. I'm just curious as to how they knew since that's the only info I gave them about the phone.
No just that number alone doesn't tell them that your bootloader is unlocked. You must have told them other information as well like say you radio versions, etc. If say you flashed a 1.55.605.2 based stock rom but DIDN'T flash the most current radios then you would have mismatching versions. If they by chance asked what radio version number you had then that could give it away. Cause the only way you could have mismatching radio/software versions is if your bootloader was unlocked and you were flashing stuff. But there are other indictators too. You might have unwittingly told them other stuff that could give it away. I wouldn't worry about it though. HTC is generally pretty cool about it. They know for example that a dead pixel in a screen has absolutely nothing to do with an unlocked bootloader or SOFF so they still honor the warranty. Unlike companies like Verizon.
I had a similar conversation with Motorola when I had the Droid RAZR MAXX HD. After trying to do a factory reset to sell the phone it got hung up in the cache wipe. I contacted Moto, explained the problem and told them that the phone was not rooted. The csr told me that she could see that the phone was not rooted, and set up the rma to get it fixed. I too was surprised by this info from Moto. Moto had built in a root checker into their software and apparently it sent back info to Moto without my knowing. So I wouldn't be too surprised if other oems have followed suit.
Sent from my HTC One M8.
nicholi2789 said:
No just that number alone doesn't tell them that your bootloader is unlocked. You must have told them other information as well like say you radio versions, etc. If say you flashed a 1.55.605.2 based stock rom but DIDN'T flash the most current radios then you would have mismatching versions. If they by chance asked what radio version number you had then that could give it away. Cause the only way you could have mismatching radio/software versions is if your bootloader was unlocked and you were flashing stuff. But there are other indictators too. You might have unwittingly told them other stuff that could give it away. I wouldn't worry about it though. HTC is generally pretty cool about it. They know for example that a dead pixel in a screen has absolutely nothing to do with an unlocked bootloader or SOFF so they still honor the warranty. Unlike companies like Verizon.
Click to expand...
Click to collapse
No, I'll post the transcript later (at work right now) if you want. It was literally the only thing she asked me about the software before she confirmed with me that the bootloader was unlocked. Maybe it was social engineering..? Lol
Yeah, I'm not worried about it, as she didn't even hesitate to warranty the phone for me still. I was just curious as to how she knew that.
NSA I tell ya. Oh and HTC knew you met that hooker on your lunch break too so watch those texts.
T4rd said:
No, I'll post the transcript later (at work right now) if you want. It was literally the only thing she asked me about the software before she confirmed with me that the bootloader was unlocked. Maybe it was social engineering..? Lol
Yeah, I'm not worried about it, as she didn't even hesitate to warranty the phone for me still. I was just curious as to how she knew that.
Click to expand...
Click to collapse
Well for all we know HTC apps could be logging information about our phones. There's no way we could know except for reading days and days worth of logcats. It is interesting though.
Yeah I recently had the worst customer service experience with HTC ever. They confirmed my bootloader was unlocked and i sent it in for a screen repair since it was cracked. They made me pay full price for the repair because they said it voided the warranty.
Then when I asked the customer support person if i paid for the repair out of pocket would they send me the phone still unlocked and S-off'd. The support person said specifically that if i didn't escelate the problem then they would just repair the screen. So i didn't escalate the problem and when i got the phone back i found out i was no longer unlocked or S-Off'd.
Then when i spoke to customer support again they quoted the previous tech and said that if i escalated the problem they would have likely done the repair for free and left my phone unlocked. I also found out what i paid for was a new board and the screen repair. They refused to help me in any way. I even asked if i could escalate the problem and if there was a way i could be refunded for the main board replacement since i only requested the screen be repaired. They said nope your SOL.
Litterally don't understand how anyone has had a good experience with HTC support :/
TLDR: Bootloader unlocked, sent phone for repair. Was lied to by customer support and offered no help from HTC.
T4rd said:
Yeah, I'm not worried about it, as she didn't even hesitate to warranty the phone for me still. I was just curious as to how she knew that.
Click to expand...
Click to collapse
I think it was social engineering
Or
HTC allows most every phone to be unlocked EXCEPT Verizon does not. So they are probably working with the rest of the world and thinking Remember to lock your bootloader!
scrosler said:
I think it was social engineering
Or
HTC allows most every phone to be unlocked EXCEPT Verizon does not. So they are probably working with the rest of the world and thinking Remember to lock your bootloader!
Click to expand...
Click to collapse
They are saying they knew it was unlocked from the phone call, does this mean make sure it is relocked before making the call? This kinda scares me, I have never had issues with warranty replacements but I am new to Verizon. Will Verizon know I am unlocked and reject me or can I simply relock if needed? Hopefully I will never have to use warranty but this does not sound good lol.
While I am here I have a quick question without opening a new thread, why does this Verizon M8 forum's phone description show us having the 2.5ghz processor? I thought we had the 2.3Ghz version from Verizon? Thanks
LibertyMonger said:
They are saying they knew it was unlocked from the phone call, does this mean make sure it is relocked before making the call? This kinda scares me, I have never had issues with warranty replacements but I am new to Verizon. Will Verizon know I am unlocked and reject me or can I simply relock if needed? Hopefully I will never have to use warranty but this does not sound good lol.
While I am here I have a quick question without opening a new thread, why does this Verizon M8 forum's phone description show us having the 2.5ghz processor? I thought we had the 2.3Ghz version from Verizon? Thanks
Click to expand...
Click to collapse
Well do have the 2.3 ghz version. And you can re-lock your bootloader with a fastboot command. Verizon is not that strict on their phones. Noone even looks. I've sent 2 M8s back to Verizon for warranty replacements. One still said s-off, the other said unlocked and s-off. Noone every said a word to me. Not to mention all the warranty replacements in the past I've done with other devices.
Just do everything you can to lock it back up and get it as close to stock as possible since it doesn't take that much effort. But I wouldn't sweat it too hard. I don't think they even look aside from powering it on and making sure it isn't water damaged.
They can tell because of the HTC DM and the HTC Checkin Services
These apps occasionally check in with HTC servers and send log files
Sent from my HTC6525LVW using XDA Free mobile app
my HTC story:
well here goes.... I bricked my my M8...BAD, to the point of no boot, no hope. So i worked with HTC tech support via chat, and told them i had rooted & SOFF'd my phone, and i was willing to pay to get the phone fixed and back. So they sent me an email explaining the mail in procedure. I sent the phone, the tech conversation transcript, and a letter stating the specific problem with the phone, also explaining root & SOFF. And i got a refurb phone from them a week later, free of charge. But this one had terrible scratches all over the camera lense. So i sent it back, and i got sent another refurb, this time with a good lense. By that time, i had paid my edge contract buyout, and gotten a new M8, so now i have 2 M8's. Customer service wasn't bad for me.
FragmentedLogik said:
They can tell because of the HTC DM and the HTC Checkin Services
These apps occasionally check in with HTC servers and send log files
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
Maybe time to see what happens if they are renamed,removed, or froze with TB.
I recently cracked the screen on my VZW M8. I chose the $19 option with HTC Advantage. I first sent my unlocked, s-off device to HTC. They received the device in 2 days, and shipped out a replacement device the same day, free of charge. I guess I'll call it "luck".
sfobrien said:
Maybe time to see what happens if they are renamed,removed, or froze with TB.
Click to expand...
Click to collapse
HTC DM you can disable in the app mgr.
Do you have the HTC Quick Guide app installed from the market?
It does not change ver. from 4.1.2
what does this updatedo?
What does this update do? Does it affect my root? Thanks!
It is notifying me too. Since I have twrp and root on stock jelly bean, how can I update if helpful, or turn off update notification?
Chad
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
AFwarbird said:
It is notifying me too. Since I have twrp and root on stock jelly bean, how can I update if helpful, or turn off update notification?
Chad
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Started getting the notification yesterday, but I'm also on stock Jelly Bean 4.1.2 and TWRP. I was able to stop the notifications by freezing "AT&T Sofware Update" with Titanium Backup, but I'd also like to know if there's anything here worth the trouble of trying to get it installed.
I just had a chat session with a Samsung official, and she said it's news to them. I told her that I am on I727UCMC1, and she said that my device is up to date. The small update AT&T is pushing must be something to do with AT&T.
Unless it updates my camera features, I'm not even bothering with it, and will keep AT&T Update frozen.
I'm pretty sure I'd have to backup everything, revert to stock UCMC1, cross my fingers and toes that it still doesn't brick my phone, and hope it still can be rooted the way I did before.
It sure would be nice if there was some sort of explanation as to what is being updated. I have looked all over and not found anything anywhere else that mentions this update to I727UCNJ1. I got the number from this an at&t website I would post the link but can't. It is only 12mb so probably not worth a bunch of trouble but I wish I knew what it is trying to update.
Paranoid?
Me too. Mine is original stock, but I upgraded the Android OS last year to 4.1.2 via Samsung Kies. However, mine is unlocked, and I can't help but be suspicious that AT&T is "updating" to do something that is to their benefit and not ours (i.e. relocking the phone?, spyware, etc.?), so it would be nice to have some details of what/why this unexpected update, before blindly agreeing to it. So, if anyone know what this update is all about, please share with us. Thanks very much!
My money's on an update that locks the phone down. What else would AT&T possibly do with a three-year-old platform that isn't making them any new money at this point?
I chatted with an AT&T representative yesterday, and all I could get out of her was that the update had to do with new features to the O/S. That's all the information that she could find, and couldn't tell me any specifics about what features were being updated.
I am about to go to an S5 or S5 Active soon, and I might just revert to stock to check it out.
It's pretty fishy though that neither Samsung, or AT&T has, or wants to divulge in any, information on exactly what it's going to do.
---------- Post added at 07:29 PM ---------- Previous post was at 07:26 PM ----------
As far as it locking your device back down, I have yet to flash, or install anything that has re-locked my phone. I guess it's possible. The only thing I'm worried about is losing root, and not being able to get it back with the last way that's available.
I see it's now listed on the AT&T eSupport website No details, just "Android OS Enhancements".
I don't have enough posts on this forum to be permitted to publish a link, but you can find it by Googling "AT&T Update to Skyrocket", and the eSupport link should be near the top of the results.
AT&T is taking the same tack as Verizon, and locking everything down. Even the mid to low end phones. So, I wouldn't be surprised if this is a way to lock older phones.
On the other hand, it really may be final bug fixes - a sort of final service pack. I wish I trusted them to give it a try.
I reverted back to stock I727UCMC1 using Odin v1.85, updated OTA to I727UCNJ1, flashed TWRP custom recovery, got root back, but I am not sure if I am still unlocked or not. I tried *#7465625# on the dialer, but the code does nothing.
Anyone know of another code to check the unlock status?
Thanks very much for your feedback. I've always just put a SIM card from another carrier into my phone. Even if it is not an active SIM, your phone should still tell you whether or not it is locked.
24fan4life said:
I reverted back to stock I727UCMC1 using Odin v1.85, updated OTA to I727UCNJ1, flashed TWRP custom recovery, got root back, but I am not sure if I am still unlocked or not. I tried *#7465625# on the dialer, but the code does nothing.
Anyone know of another code to check the unlock status?
Click to expand...
Click to collapse
unless u restored a previous efs partition that was locked to a carrier then u will remain unlocked, afaik no one lost their unlocked sim by restoring or flashing any firmwares, to read more about the sim lock or to unlock the sim read this http://forum.xda-developers.com/showthread.php?t=2638037
as for firmwares locking down the phone its referring to the way root is acheived not to the sim carrier lock
T.J. Bender said:
My money's on an update that locks the phone down. What else would AT&T possibly do with a three-year-old platform that isn't making them any new money at this point?
Click to expand...
Click to collapse
i hope you are joking, because if not then then you're insane. no offense intended.
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices. Several devices started out unlocked, like the S2, and became locked by OTA updates. The S3, Note 2, etc.
IOW, I wouldn't put it past them, especially if Samsung wasn't aware of the update. On the flip side, the S2 is no longer even for sale, and I have to wonder how many are left in active service.
Clarification?
lingowistico said:
i hope you are joking, because if not then then you're insane. no offense intended.
Click to expand...
Click to collapse
Thanks, that was very helpful! Seriously though, as a senior member of this forum, perhaps you might have some constructive comments on this subject? After all, we're sitting here with phones (the I-727 SII Skyrocket is an oldie, but goodie!) that are trying to push an unanticipated OTA update on us, in a very suspicious manner. We hope it's just a bug fix, but don't trust the carrier (AT&T) to be doing this, unless they have some ulterior motive. The benefit of your substantial experience would be appreciated. Thanks in advance for any insight you can offer us.
Regards,
Ron M.
jshamlet said:
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices. Several devices started out unlocked, like the S2, and became locked by OTA updates. The S3, Note 2, etc.
IOW, I wouldn't put it past them, especially if Samsung wasn't aware of the update. On the flip side, the S2 is no longer even for sale, and I have to wonder how many are left in active service.
Click to expand...
Click to collapse
Thank you for your insight, it was TRULY helpful! As a relative newbie, I just want to clarify our terms. When you use the term "unlocked", I deduce you are referring to a phone that has been rooted and is running a different platform - is that correct? In my case, I am NOT rooted and simply running the original crappy stock platform, but my phone is "unlocked" in the traditional sense, in that I can use it with different sims from different carriers throughout the world, rather than being "locked" to AT&T. So, for those of us who are not as technically advanced, could you please clarify? For me, if this OTA update doesn't prevent me from continuing to use other sims from other carriers, then I don't know what the downside would be, unless they're just adding more spyware and bloatware to their already intrusive system? I look forward to your comments.
Regards,
Ron M.
jshamlet said:
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices.
Click to expand...
Click to collapse
I thought T.J. Bender was talking about simlock since he didn't mention the bootloader. :silly:
At&t sure isn't making life easy for you.. I'd still be proudly rocking a skyrocket too if I didn't lose it :angel:
I only messed with my Skyrocket for an hour or so after accepting the OTA update, before starting up my new S 5 Active.
The only thing that I really noticed, was they took the AT&T phone setup app off of it, since it is no longer in use by AT&T. There may have been more that I didn't notice, but only running it a couple hours, I couldn't tell. I even checked the camera thinking they might have finally snuck some new features into it, but no dice.
lingowistico said:
i hope you are joking, because if not then then you're insane. no offense intended.
Click to expand...
Click to collapse
How does suggesting that AT&T would lock a bootloader make me insane?
Sent from my totally badass HTC One m8 using Tapatalk
After giving the V10 a month, I decided to swap it out (why is for another thread, I suppose). I had rooted and installed TWRP, so I used the stock files provided in the dev threads to go back to stock and relock the bootloader. I did a factory reset to make sure everything was working properly.
When I went to turn in the device, the guy at the store ran a phone code and got a code back from the network. Apparently, it does a check to make sure the device is the same one that I originally purchased and that it hasn't been rooted (in a Samsung phone's case, it checks Knox status as well). If it comes back as rooted or having ever been rooted, he said the system will deny the exchange. Mine passed (since thankfully LG's stuff can be completely reset), and I didn't volunteer that I had rooted it.
Just be aware that you need to go completely to stock in order to return the phone to swap out for a new one. I'll assume if your phone get's flagged in the system once, you can't ever return it, even if you try to flash back to stock again.
I love Jump on Demand, but I think it's going to keep me stuck unrooted for the most part - can't risk blowing $700.
Thanks for the heads up! With JUMP it shouldn't matter, but a device exchange may flag.
Sent from my LG-H901 using Tapatalk
I rooted my Note 4 and 5 with twrp aswell.... Did jump from both with no problem! My last jump was Nov. 15th for the V10 and the promo and had no problem, must be a new policy!!! But yes, always go back to stock before upgrade lol
That's good you passed the network check, I wonder how that works? When you rooted, did you freeze that weird pr.adapt app that kept requesting root access?
YrrchSebor said:
That's good you passed the network check, I wonder how that works? When you rooted, did you freeze that weird pr.adapt app that kept requesting root access?
Click to expand...
Click to collapse
I did freeze it, but the T-mobile app (which I use to check my data usage) still saw that my device was rooted, even though I never gave that app root access. However, when I start the app, I told it I didn't want it to share any info with T-mobile, so it shouldn't have had permission to report my root status to T-mobile (and apparently it didn't).
daveeckert said:
I did freeze it, but the T-mobile app (which I use to check my data usage) still saw that my device was rooted, even though I never gave that app root access. However, when I start the app, I told it I didn't want it to share any info with T-mobile, so it shouldn't have had permission to report my root status to T-mobile (and apparently it didn't).
Click to expand...
Click to collapse
Ahh OK, I guess that could be an important point then! I always disallow sending the diagnostics and such in the my T-Mobile app... Thank god. Hopefully it'll be OK. Thanks for the heads up!
I just jumped from a Note 5 to the V10. I reset the Note 5 using Kies, but knox was still tripped. No issue at the store. The G4 that I jumped from to go to the Note 5 also had been rooted/bootloader unlock, no issue when I did that either.
That's weird. I called a store and asked them this exact question before turning in my G3. She said it didn't matter and they were gonna wipe the phone. It's possible she didn't understand the question, but I turned it in with no issues and haven't received any calls over the few days I've had the V10. I'm on the basis Jump plan too.
No issues trading in my Knox-tripped Note 4 a couples months ago. Maybe just that one store is getting a little wacky with the checking lol
Unheard said:
I just jumped from a Note 5 to the V10. I reset the Note 5 using Kies, but knox was still tripped. No issue at the store. The G4 that I jumped from to go to the Note 5 also had been rooted/bootloader unlock, no issue when I did that either.
Click to expand...
Click to collapse
Just curious how you like the V10 vs. the Note 5? I kinda like the V10 hardware, but it seems there will be very little development done on this phone (I'm dying for CM in particular). Doesn't seem as popular as I had hoped it would be with the dev community. I'm considering the Note 5 as a JoD exchange (and thanks to OP for the heads up here), since there seems to be a lot of dev activity for it. Just don't know if I'll be able to deal with that hardware home button. Guess I'm picky.
I can't tell the number of rooted phones I've sent back to Verizon and T-mobile, never a word.
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
Ahh OK, I guess that could be an important point then! I always disallow sending the diagnostics and such in the my T-Mobile app... Thank god. Hopefully it'll be OK. Thanks for the heads up!
Click to expand...
Click to collapse
Okay you could also block it with root cloak...
Sent from my LG-H901 using Tapatalk
Been on Verizon, Alltel, Sprint, and Ma'Bell. always rooted, never had e Problem. Just make shure you return to stock. I even exchanged a couple of Samsungs with Knox trip, Lucky I guess. I've heard Stories but never met anyone that has been returned or charged a device.
spg900ny said:
Just curious how you like the V10 vs. the Note 5? I kinda like the V10 hardware, but it seems there will be very little development done on this phone (I'm dying for CM in particular). Doesn't seem as popular as I had hoped it would be with the dev community. I'm considering the Note 5 as a JoD exchange (and thanks to OP for the heads up here), since there seems to be a lot of dev activity for it. Just don't know if I'll be able to deal with that hardware home button. Guess I'm picky.
Click to expand...
Click to collapse
Currently have the Note 5. I wouldn't say there is a lot of dev activity. Then again, I came from a Nexus 6. [emoji2]
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Cool, so no more Jump for me. Looks like a steady stream of Priv's, 950XL's, Moto's, or Nexuses.
xxdjvalexx said:
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Click to expand...
Click to collapse
I just got the V10 and traded in my rooted and ROM'd Galaxy S6 for it. She did the code thing, didn't bat an eye.
Sent from my LG-H901 using Tapatalk
xxdjvalexx said:
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Click to expand...
Click to collapse
What ## code do you enter?
I would imagine that code is more of a quick IMEI/"is the phone stolen" verification rather than checking for root.
daveeckert said:
After giving the V10 a month, I decided to swap it out (why is for another thread, I suppose). I had rooted and installed TWRP, so I used the stock files provided in the dev threads to go back to stock and relock the bootloader. I did a factory reset to make sure everything was working properly.
When I went to turn in the device, the guy at the store ran a phone code and got a code back from the network. Apparently, it does a check to make sure the device is the same one that I originally purchased and that it hasn't been rooted (in a Samsung phone's case, it checks Knox status as well). If it comes back as rooted or having ever been rooted, he said the system will deny the exchange. Mine passed (since thankfully LG's stuff can be completely reset), and I didn't volunteer that I had rooted it.
Just be aware that you need to go completely to stock in order to return the phone to swap out for a new one. I'll assume if your phone get's flagged in the system once, you can't ever return it, even if you try to flash back to stock again.
I love Jump on Demand, but I think it's going to keep me stuck unrooted for the most part - can't risk blowing $700.
Click to expand...
Click to collapse
No, he was pulling your leg. I turned in my note 4 with twrp and a custom rom in October and I had to do the same check, it's just a service code check to make sure it's the same one you bought from tmo, if it checked for root I would never be able to get a phone again because I flashed that phone so much. I talk to the guys at the store and told them I rooted do they.
I don't know how this'll go.......
So all my past android phones I have rooted + installed recoveries and what not. Originally I did this because I heard of a way to increase the battery life of my HTC Incredible via rooting. Afterwards I found myself rooting my Inc2, DNA, Inc4G, and my One M8. This time I did it so I can get the latest versions of Android/HTC Sense (until Google finally made a good looking UI w. 5.0).
Today (technically yesterday at this point) I bought the Pixel in hopes of finally being able to receive consistent android updates. That being said, the idea of being able to get consistent and relatively quick android updates was the whole point of me unlocking + rooting my phone.
I guess the question remains: Should I continue running unlocked with the Pixel, or will the updates from Google be enough?
dkris2020 said:
I guess the question remains: Should I continue running unlocked with the Pixel, or will the updates from Google be enough?
Click to expand...
Click to collapse
I like custom recoveries like TWRP because you can make nandroid backups. The downside of unlocking your bootloader is that Android Pay won't work and if someone gets ahold of your phone, like a thief, if the phone is unlocked then they can flash it and it will circumvent any protection on the device.
I like root because you can use apps that require root, like some Ad blockers and Titanium Backup, and because I can remove system apps I don't want on my phone.
It all depends on what you want to do with your phone.
Unless someone has a reason for unlocking the device, generally I don't see the point. There are some things that I want to do with my phone, which are easier to do unlocked, so personally I specifically wanted an unlockable phone. Depending on how much you've read about the Pixel, here are some things you may or may not know.
- Unlocking the device will wipe it, so if you decide later that you want to unlock it will wipe the phone.
- An unlocked stock device can still use the standard OTA updates.
- Some SuperSU users may be able to unroot and then use the standard OTA updates, and some rooted users have reported their phones automatically updating.
- After I started using root my phone fails to install the OTA updates, so I'd guess one of the checked areas on my phone has changed due to the root apps I've used.
- If the OTA notification shows up and the update will not install, with the stock ROM it's possible to burn through a lot of cellular data. When I didn't update my phone this month, it used about 1 GB before I shut off cellular data.
- Items like a computer, TWRP, or FlashFire are the sorts of alternate update routes for the stock ROM if a rooted phone cannot use the standard OTA.
alluringreality said:
some rooted users have reported their phones automatically updating..
Click to expand...
Click to collapse
Isn't there a way to disable the automatic updates?
LoliSmith said:
Isn't there a way to disable the automatic updates?
Click to expand...
Click to collapse
You can disable them in developer options. I've had my phone since early November (turned off system updates the day I got it) and have never been notified that an update is available. However, some have reported that they had system updates disabled in developer options and they still get notified an update is available. It seems to be hit and miss so I can't say for sure it would work for you or not.
Just addressing OPs concerns, unlocking your phone shouldn't have any impact on updates from Google. You can still get them, OTA or otherwise.
The only downside I'd say, are warranty related (unlocking the bootloader will void the warranty on Verizon models), and security. Google has pretty much decided that having an unlocked bootloader is not secure enough for Android pay, so you'll be without that (However, you can still use loaded gift cards/loyalty program cards. It's just credit/debit cards that won't work).
robocuff said:
You can disable them in developer options. I've had my phone since early November (turned off system updates the day I got it) and have never been notified that an update is available. However, some have reported that they had system updates disabled in developer options and they still get notified an update is available. It seems to be hit and miss so I can't say for sure it would work for you or not.
Click to expand...
Click to collapse
On my motorola phones, there was an app that you could freeze using titanium back up. I wonder if there is anything like that with the pixel?
---------- Post added at 12:28 PM ---------- Previous post was at 12:23 PM ----------
Soccerdude588 said:
The only downside I'd say, are warranty related (unlocking the bootloader will void the warranty on Verizon models),
Click to expand...
Click to collapse
First, that assumes that Google has a record of you unlocking your bootloader, which they may since jcase is saying that the phones have to communicate with the Google servers to unlock the bootloader.
Second, there is a federal law on this and the way it works in this situation is that if unlocking your bootloader is not related to the warranty claim, Google can't deny your claim. For instance, if the charging port fails that is entirely a hardware issue unrelated to unlocking your bootloader. Google must honor the warranty for that.
If you were to brick your device flashing, that would be different but Google would have to have some proof that you not only unlocked your bootloader but that it was the unlocked bootloader that resulted in a bricked phone.
robocuff said:
I've had my phone since early November (turned off system updates the day I got it) and have never been notified that an update is available.
Click to expand...
Click to collapse
Are you manually updating your device, or are you running months behind the current release? The reason I ask is that the OTA notices on my phone have been delayed my days or weeks from the initial release, but I think they have showed up eventually when I've stayed on a prior version and the developer option has been shut off.
LoliSmith said:
On my motorola phones, there was an app that you could freeze using titanium back up. I wonder if there is anything like that with the pixel?
Click to expand...
Click to collapse
I was hoping the following link might work similar to the Razr updater, but unfortunately the change kept my phone awake and didn't allow deep sleep both times I tried it. The update notification can be shut off by long pressing it, which I think shows up as a notification block. Due to the cellular data drain, my current plan is to try FlashFire for updates, and if that doesn't work well I'll probably try a ROM to avoid OTA updates.
https://www.androidexplained.com/pixel-hide-ota-notification/
alluringreality said:
Are you manually updating your device, or are you running months behind the current release? The reason I ask is that the OTA notices on my phone have been delayed my days or weeks from the initial release, but I think they have showed up eventually when I've stayed on a prior version and the developer option has been shut off.
Click to expand...
Click to collapse
I've been manually updating it. Usually within a week or so of the release. However, I skipped the January update all together and never got a notification about it. Maybe I got lucky. Don't know.
Thanks for the input guys.
So a lot of the stuff you guys are saying are things that I have had prior experience with so the actual process of unlocking I have no issues with. If unlocking the Pixel is anything like the Moto X Pure (which it should cause Google) it shouldn't be too much of a hassle.
That said I am with Verizon and I can say that in all of my years of owning rooted/unlocked HTC phones I only ever needed to use my warranty for hardware based claims. Like I said the main reason I unlocked/rooted was to get updated ROMs that Verizon/HTC wouldn't push out to the phone. I think I'll more than likely unlock it but I probably won't root unless I need to.
That's pretty much where I am. I did root, but a recent OTA update that I accidentally took unrooted me. Keeping the bootloader unlocked at least leaves that option available.
Long story short, I got a brain tumor (that's not going to kill me) but it's messed up my eyesight... which is great... so I decided to finally get rid of my beloved Pixel2 and get something with a larger screen so I could see the thing. Hence the S21+ and... it works for that. The screen is way bigger so it's great.
The problem is, one other thing that really worked well for my eye problem is VR. I have the Google Daydream headset and my eye problem means my left eye kind of moves around on its own. It's super fun... lol... but somehow, the VR tracks that and I can actually see in VR, use the browser, etc... It's not perfect but it gives my eyes a rest. But, apparently this phone doesn't work with Daydream unless I have root and edit some files. So ok, I need root.
My carrier is Google FI and I was under the impression that all of their phones came with OEM unlock, but I have no "OEM Unlock" option in developer tools. I am very confused by all the different information I'm finding out there.
So, here are my questions:
1. Is my phone already OEM unlocked because this is GoogleFI or am I screwed?
2. Is there some other way to get the OEM unlock?
3. I'm assuming there's no way to get root without OEM unlock?
4. Barring all of the above, does anyone know of any way to trick Google Daydream into working on this phone?
5. If I can't get Daydream to work, I can just pop out the daydream RFID thingy and use the headset as if it weren't daydream, but the controller doesn't seem to do anything. Is there a way to set that up? or is it possible to get a "Wand style" controller like this outside of daydream?
1 no
2 pay 150, look for a paid service on 1st page, I personally don't like that, I went with g9960 route
3 correct
4
https://www.reddit.com/r/daydream/comments/5jg33j
5 see pt 4
Thanks! That's a bummer... I'll wait until there's a community unlock somewhere.
The Daydream link you offered doesn't really help me. If you switch to the cardboard headset, it doesn't support the controller anymore. But I did find a post that helped me get it working:
Trying to get Daydream working on the MZP without root.
Can some one please help me edit the Daydream related APK's to automatically pass the checks in /system/etc/permissions/handheld_core_hardware.xml for and
forum.xda-developers.com
Basically you modify and recompile the daydream app.
I still want root, it's unfortunate Samsung sucks.
If your phone's model number is SM-G996U1 then it is unlocked. I'm thinking about getting one. Did you get it directly from Fi?
Lancez said:
If your phone's model number is SM-G996U1 then it is unlocked. I'm thinking about getting one. Did you get it directly from Fi?
Click to expand...
Click to collapse
Yes, I got it directly from FI.
So the problem is, I'm not up on the current lingo, but there are multiple kinds of unlocks. In this case, my phone is definitely carrier unlocked. Google FI requires that because it hopps carriers. But is it bootloader unlocked? I'm trying to figure that out, but none of the dialer codes work on this phone. I tried to get to fastboot, but Samsung phones are weird. It's almost like they have their own set of rules. lol
Any idea how I can check the bootloader?
It's been a loooong time since my last Samsung phone. But if my memory serves me well, you can turn off the phone then press and hold vol up or down and power button simultaneously (or even 3 buttons at same time). It'll take you to bootloader or recovery mode. You can try all possible combinations until you get what you want, it won't hurt your phone.
Oh, one more thing. If you are using third party dialer app instead of built-in. All codes are not gonna work.
Fi is offering $300 discount for existing customers, That's a pretty good deal. I'm ordering one right now.
Lancez said:
Oh, one more thing. If you are using third party dialer app instead of built-in. All codes are not gonna work.
Click to expand...
Click to collapse
I've tried both the default google dialer and the samsung dialer that came with it. Neither will do anything when I enter a dialer code. :-/
Lancez said:
Fi is offering $300 discount for existing customers, That's a pretty good deal. I'm ordering one right now.
Click to expand...
Click to collapse
I've tried a dozen different ways to get this to work. I do not think the bootloader is unlocked, and I do not think its unlockable without that paid services which is $150
OEM unlocking does not exist, even after waiting the 7 days.
I can boot into download mode, but the volume up thing does nothing
If I chose "Reboot to bootloader" it just boots the phone into safemode.
I've read that if you try and flash TWRP with the bootloader locked, it can brick your phone.
I've found no way to check if a samsung phone is bootloader unlocked.
I don't want to flash it, trip knox, and then end up having it bricked. lol
I'll take a look when I have the phone handy next week and keep you updated
Samsung's Galaxy S21 series can now be rooted with Magisk
You can now root your Galaxy S21, Galaxy S21 Plus, and Galaxy S21 Ultra using Magisk. Follow the link in the post for instructions.
www.xda-developers.com
As topjohnwu notes ... as of now, only the Exynos and Hong Kong Snapdragon Galaxy S21 devices can be bootloader unlocked,...
Click to expand...
Click to collapse
if that's not true I would be slightly annoyed cuz I spent extra 100$ to get the Hk version
fenvy said:
Samsung's Galaxy S21 series can now be rooted with Magisk
You can now root your Galaxy S21, Galaxy S21 Plus, and Galaxy S21 Ultra using Magisk. Follow the link in the post for instructions.
www.xda-developers.com
if that's not true I would be slightly annoyed cuz I spent extra 100$ to get the Hk version
Click to expand...
Click to collapse
It is true. You can root the phone, but you have to unlock the bootloader before you can root it. Currently the only way to unlock the bootloader in the US versions is to pay $150 to the dude that came up with the exploit. If you have the non us version, you can unlock it yourself.
charliemopps said:
I've tried a dozen different ways to get this to work. I do not think the bootloader is unlocked, and I do not think its unlockable without that paid services which is $150
OEM unlocking does not exist, even after waiting the 7 days.
I can boot into download mode, but the volume up thing does nothing
If I chose "Reboot to bootloader" it just boots the phone into safemode.
I've read that if you try and flash TWRP with the bootloader locked, it can brick your phone.
I've found no way to check if a samsung phone is bootloader unlocked.
I don't want to flash it, trip knox, and then end up having it bricked. lol
Click to expand...
Click to collapse
Just got my S21+ today and you were right. Bootloader is indeed unlockable by average users at least. I did get into recovery mode by using Vol up+power and I can see there's reboot to bootloader option. But it does nothing other then restarting the phone. I don't know how did you get into safe mode tho. (attached a pic of recovery mode from my phone)
Anyway, I'm pretty happy with the way it is and I personally would not pay anything over 50 bucks to get bootloader unlocked.
Lancez said:
If your phone's model number is SM-G996U1 then it is unlocked. I'm thinking about getting one. Did you get it directly from Fi?
Click to expand...
Click to collapse
Unlock means ?
My model is g996u . Will i get ota update ?