Related
So I had 4.1.2 on my phone and rooted with no problems, but now that I updated to 4.4.2 and lost my root... I cannot for the life of me figure out how to get root back again. Anyone help me please?
Well I got impatient and found something called towelroot and root checker now says I am rooted, but I cannot get CWM installed. Using both Odin 307 and 309 I boot into downloading mode and odin fails and I see red error saying "secure check fail: recovery"
Any help?
MortTheBeast said:
Well I got impatient and found something called towelroot and root checker now says I am rooted, but I cannot get CWM installed. Using both Odin 307 and 309 I boot into downloading mode and odin fails and I see red error saying "secure check fail: recovery"
Any help?
Click to expand...
Click to collapse
If you go to settings > about phone build and based band ending in ML1 NC1 NE1 have looked bootloader a meaning you can't install custom rims .. You will have to root / install safestrap and boot custom tw Roms since you are on 4.4.2 you have to wait for a 4.4.2 tw rom I don't think any are out yet
Sent from my iPod touch using Tapatalk
MortTheBeast said:
Well I got impatient and found something called towelroot and root checker now says I am rooted, but I cannot get CWM installed. Using both Odin 307 and 309 I boot into downloading mode and odin fails and I see red error saying "secure check fail: recovery"
Any help?
Click to expand...
Click to collapse
Since we can't install custom roms, I found this xposed module called Wanam Xposed. I'm not even rooted yet but I was going to with towelroot. Anyway, it lets you customize certain looks of the stock rom without modifying anything. You need the Xposed Framework first and then you can get Wanam Xposed.
Mon431 said:
Since we can't install custom roms, I found this xposed module called Wanam Xposed. I'm not even rooted yet but I was going to with towelroot. Anyway, it lets you customize certain looks of the stock rom without modifying anything. You need the Xposed Framework first and then you can get Wanam Xposed.
Click to expand...
Click to collapse
Yea I am just going to be as patient as possible till I can unlock the bootloader. How long does it usually take for the tech geniuses to figure this kind of stuff out? I'm wishing I hadn't updated 4.4.2 now... (slaps forehead)
MortTheBeast said:
Yea I am just going to be as patient as possible till I can unlock the bootloader. How long does it usually take for the tech geniuses to figure this kind of stuff out? I'm wishing I hadn't updated 4.4.2 now... (slaps forehead)
Click to expand...
Click to collapse
Unless if the file leaks from Samsung like it did on 4.1.2, it won't ever get unlocked
Mon431 said:
Unless if the file leaks from Samsung like it did on 4.1.2, it won't ever get unlocked
Click to expand...
Click to collapse
EEEEeeeeek! Don't say things like that! LOL
Anyway... I guess if worse comes to worse, shouldn't a Factory Reset take me back to 4.1.2? And then I would be able to try out one of the 4.4.3 CM Nightly builds
MortTheBeast said:
EEEEeeeeek! Don't say things like that! LOL
Anyway... I guess if worse comes to worse, shouldn't a Factory Reset take me back to 4.1.2? And then I would be able to try out one of the 4.4.3 CM Nightly builds
Click to expand...
Click to collapse
A factory reset will reset your phone like it's new but it'll stay on the same version. For example, if you updated to 4.3 and then did a factory reset, you be on 4.3 but your phone would be reset.
Son of a biscuit lol.... maybe if I dunk in the toilet it will revert back to 4.1.2? LMAO! Man... being impatient really put the screws to myself.
MortTheBeast said:
Son of a biscuit lol.... maybe if I dunk in the toilet it will revert back to 4.1.2? LMAO! Man... being impatient really put the screws to myself.
Click to expand...
Click to collapse
1st rule of rooting...NEVER OTA! Bricks, locked bootloaders, and facepalms will be imminent.
Sent from my SCH-I535 using XDA Premium 4 mobile app
MortTheBeast said:
Son of a biscuit lol.... maybe if I dunk in the toilet it will revert back to 4.1.2? LMAO! Man... being impatient really put the screws to myself.
Click to expand...
Click to collapse
Yeah, once you update to 4.4.2 you're stuck. You will NEVER be able to go back and you'll never be able to flash a custom recovery. It's Touchwiz from here on out for you.
I feel for you, but it's pretty universally known that you don't take OTA's from Verizon OR Samsung because they usually close up loop holes.
sbenson1226 said:
Yeah, once you update to 4.4.2 you're stuck. You will NEVER be able to go back and you'll never be able to flash a custom recovery. It's Touchwiz from here on out for you.
I feel for you, but it's pretty universally known that you don't take OTA's from Verizon OR Samsung because they usually close up loop holes.
Click to expand...
Click to collapse
That seems to be a little presumptuous saying "never". Software is software... which to me means "if there is a will, there is a way", in regards to hacking/cracking it. And if I get that hard pressed to want the ability to tinker with roms I can always just sell the phone and buy one thats not been updated to 4.4.2. All I can say right now being a newb to all this stuff is "lesson learned and stored in memory for future use". :good:
MortTheBeast said:
That seems to be a little presumptuous saying "never". Software is software... which to me means "if there is a will, there is a way", in regards to hacking/cracking it. And if I get that hard pressed to want the ability to tinker with roms I can always just sell the phone and buy one thats not been updated to 4.4.2. All I can say right now being a newb to all this stuff is "lesson learned and stored in memory for future use". :good:
Click to expand...
Click to collapse
It's not really presumptuous, it's the truth. Samsung and Verizon are hell bent on keeping their bootloaders locked down. The S5 hasn't been cracked. The S4 cannot be cracked, after MDK. The S3 cannot be cracked after 4.2.1. The S3 was pure luck because somebody inside of Samsung leaked what we needed. The only way it will ever be cracked is if Samsung themselves hand us the code. Never going to happen again. Sorry, it's the hard truth. If you want to tinker, don't buy a Verizon phone and don't buy a Samsung.
What exactly is even the reasoning behind locking the bootloader? I mean, I know they don't want people messing with their software.. but WHY? Are they not already making their profits by selling the phone? Just can't wrap my head around companies that want to limit a consumers options. That would be like buy a computer with for example Windows 8 on it and being told there is no way to remove it and install Windows 7. If I can have whatever OS I want on my computer... then how is that any different then a phone which nowadays is pretty much a handheld computer.
sbenson1226 said:
It's not really presumptuous, it's the truth. Samsung and Verizon are hell bent on keeping their bootloaders locked down. The S5 hasn't been cracked. The S4 cannot be cracked, after MDK. The S3 cannot be cracked after 4.2.1. The S3 was pure luck because somebody inside of Samsung leaked what we needed. The only way it will ever be cracked is if Samsung themselves hand us the code. Never going to happen again. Sorry, it's the hard truth. If you want to tinker, don't buy a Verizon phone and don't buy a Samsung.
Click to expand...
Click to collapse
Maybe you (or someone else) can explain to me what options if any I have for unlocked bootloader capability for S3 and S4? Like whats the final software version number that still allows unlocking the bootloader, what if any carrier specific options have it unlocked or able to be. Like you mentioned the S5 not being cracked but I read through a thread on here dating back to just this past May and confirming unlocked bootloader for S5 T-Mobile. S5 is out of my price range, but the S3 and S4 I can pick up at a reasonable price... just need the proper information so I can be sure Im not getting something thats going to stick me with a locked boot. Thanks
MortTheBeast said:
What exactly is even the reasoning behind locking the bootloader? I mean, I know they don't want people messing with their software.. but WHY? Are they not already making their profits by selling the phone? Just can't wrap my head around companies that want to limit a consumers options. That would be like buy a computer with for example Windows 8 on it and being told there is no way to remove it and install Windows 7. If I can have whatever OS I want on my computer... then how is that any different then a phone which nowadays is pretty much a handheld computer.
Click to expand...
Click to collapse
Locking the bootloader means added profit on verizons end. You have less access to features that get baked into a custom rom that we bypass, such as free tethering and simply making a device better than stock. Verizon wants this.
The less debloating and access to modified firmware available means they make more money on services people have to pay for.
Verizon will tell you it's better for consumers because it adds to your customer service experience. If you have a problem, and need help, then they are more likely to be able to help you knowing you are not running modified firmware that could give you a less than par experience. They will also add that using unapproved software could negatively impact their network (ie: tethering) and cause problems for other consumers.
There may be some truth in that, but without the ability to flash a new rom you essentially limit your software abilities and limit the life of the phone. It forces people to buy their services and extend their plan more often.
---------- Post added at 01:19 AM ---------- Previous post was at 01:13 AM ----------
The t-mobile variant for both the s3 and s4 have unlocked bootloaders on every device. None of them will work on verizons network. Every Verizon Samsung phone is completely locked down.
The last available firmware that can be unlocked on the S3 is mf1. The s4's is MDK or something but that's way harder to find. There is no unlock method for the s5.
MortTheBeast said:
Maybe you (or someone else) can explain to me what options if any I have for unlocked bootloader capability for S3 and S4? Like whats the final software version number that still allows unlocking the bootloader, what if any carrier specific options have it unlocked or able to be. Like you mentioned the S5 not being cracked but I read through a thread on here dating back to just this past May and confirming unlocked bootloader for S5 T-Mobile. S5 is out of my price range, but the S3 and S4 I can pick up at a reasonable price... just need the proper information so I can be sure Im not getting something thats going to stick me with a locked boot. Thanks
Click to expand...
Click to collapse
MortTheBeast said:
Maybe you (or someone else) can explain to me what options if any I have for unlocked bootloader capability for S3 and S4? Like whats the final software version number that still allows unlocking the bootloader, what if any carrier specific options have it unlocked or able to be. Like you mentioned the S5 not being cracked but I read through a thread on here dating back to just this past May and confirming unlocked bootloader for S5 T-Mobile. S5 is out of my price range, but the S3 and S4 I can pick up at a reasonable price... just need the proper information so I can be sure Im not getting something thats going to stick me with a locked boot. Thanks
Click to expand...
Click to collapse
If you're looking to stay with Verizon, I would keep an eye out for a GS4 with the MDK firmware. I see them pop up from time to time on Swappa, but never in the condition I'm looking for (looking to upgrade my wife). Other than that, your best bet is to leave Verizon and buy unlocked phones because at least they don't have additional carrier restrictions.
BadUsername said:
Locking the bootloader means added profit on verizons end. You have less access to features that get baked into a custom rom that we bypass, such as free tethering and simply making a device better than stock. Verizon wants this.
The less debloating and access to modified firmware available means they make more money on services people have to pay for.
Verizon will tell you it's better for consumers because it adds to your customer service experience. If you have a problem, and need help, then they are more likely to be able to help you knowing you are not running modified firmware that could give you a less than par experience. They will also add that using unapproved software could negatively impact their network (ie: tethering) and cause problems for other consumers.
There may be some truth in that, but without the ability to flash a new rom you essentially limit your software abilities and limit the life of the phone. It forces people to buy their services and extend their plan more often.
---------- Post added at 01:19 AM ---------- Previous post was at 01:13 AM ----------
The t-mobile variant for both the s3 and s4 have unlocked bootloaders on every device. None of them will work on verizons network. Every Verizon Samsung phone is completely locked down.
The last available firmware that can be unlocked on the S3 is mf1. The s4's is MDK or something but that's way harder to find. There is no unlock method for the s5.
Click to expand...
Click to collapse
Appreciate the response... but now you also mention the S5 having "no unlock"... what about this thread... http://forum.xda-developers.com/showthread.php?t=2711730
sbenson1226 said:
If you're looking to stay with Verizon, I would keep an eye out for a GS4 with the MDK firmware. I see them pop up from time to time on Swappa, but never in the condition I'm looking for (looking to upgrade my wife). Other than that, your best bet is to leave Verizon and buy unlocked phones because at least they don't have additional carrier restrictions.
Click to expand...
Click to collapse
What exactly id MDK? 4.2.2? And yea I really don't care what carrier I am with, I just want a phone I can tinker with and I been getting "tinker withdrawal" since upgrading to 4.4.2
Out of curiosity, what other phones are worth looking into that are comparable to the S3 and S4? It sucks when I am a diehard Samsung lover.
MortTheBeast said:
Appreciate the response... but now you also mention the S5 having "no unlock"... what about this thread... http://forum.xda-developers.com/showthread.php?t=2711730
Click to expand...
Click to collapse
That's T-Mobile. The Verizon version is locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app
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
I talked to Samsung for about an hour about why the bootloader is locked for the US versions of the S7.( I have a SM-G930R4) Most of the time they gave me the run around but I was able to find out that with the Oreo update ,it may be possible to lock/unlock the bootloader. They didn't come right out and say it but that's what it sounded like to me. They were saying something about a "security issue" that is supposed to be fixed in Oreo,and that it's within the realm of possibilities. Let's hope they weren't trying to make me feel better,lol. I haven't had a nice phone since 2013,and I was pretty nonplussed to find out we got shafted. I have been using Samsung phones since the original Google Nexus,and have flashed/rooted/customized every single one of them. Customization is important to a lot of people,and Samsung understands this. Why'd they have to give in this time? ><
Highly unlikely
Samsung talk out of their rears when you contact them, usually just to get you to go away I find
Well that's corporations in general right? Lol. I don't want to get another phone if I don't have to. I rather like this one. I guess we'll find out in the coming weeks ,eh?
I have a screenshot of part of the conversation,but it seems like I can't post the link or embed it. Basically it was them feeding me a line of garbage about none of their USA model phones having unlockable bootloaders,and I corrected them. They also said that it was Qualcomm's fault but I can't see how. Don't they use their own bootloaders?
I guess I could always try to trade my S7 for a S6 lol.
I don't know the details of why they are locked or who's fault it is, but they're right that none of the USA S7s have unlocked bootloaders (Snapdragon Models)
It's the Exynos International S7s that are unlocked (G930F, G930W8)
Samsung will have the bootloader encryption key, so they could have added a feature to unlock it like they did with the Exynos versions, no idea why they haven't
If you want an unlocked S7 I'd sell that one and get the G930F
They didn't say it would never be unlocked. What I got from the exchange was that it may happen during the next OTA,which I assume is Oreo,or a patch of sorts thereafter. The particular lady I was speaking to implied it was Qualcomm's fault,but I find that hard to believe. I brought up the fact that we're being singled out (for whatever reason) and that customization is quite important to a lot of us.She said "Yes I agree,if you buy a phone it should be yours" So hopefully they do the right thing. I can't very well just sell this phone ,however. It holds sentimental value and was a gift from someone very dear to me.So my only option is ,A) Pray Sammie does right by us,or B) wait until someone hacks it(if it's even possible)
Also from what I've been told and what I've read on multiple forums(XDADev included) our phone carriers pressured Samsung to do it,to cut down on people bricking their phones. From my experience it's pretty hard to completely brick a Samsung. As long as you can get into download mode and flash something via Odin or backup from recovery,it's all good.
I'm running oreo. But soon all carriers will now lock bootloaders latest sprint and Verizon starting , to make it it so no one can change carriers
Not to stir up an old thread, but oreo just rolled out for the sm-g930p yesterday and I noticed that there is the option for OEM unlock. Good news for finally unlocking the bootloader?
whbisondtr said:
Not to stir up an old thread, but oreo just rolled out for the sm-g930p yesterday and I noticed that there is the option for OEM unlock. Good news for finally unlocking the bootloader?
Click to expand...
Click to collapse
No.. That's not what that feature is for. It's in Nougat as well under development options
InsanePostman said:
No.. That's not what that feature is for. It's in Nougat as well under development options
Click to expand...
Click to collapse
Gotcha. I didn't have it on here with nougat though, it didn't show up until I got the oreo update. From what I've read around, that's what it was for.
whbisondtr said:
From what I've read around, that's what it was for.
Click to expand...
Click to collapse
Random thought...Maybe when the Oreo U firmware comes out flashing the BL will work?
SprintBama said:
Random thought...Maybe when the Oreo U firmware comes out flashing the BL will work?
Click to expand...
Click to collapse
When I talked to Samsung about it they hinted that would be the case. They didn't confirm or deny it directly,but the way they put it sure alluded to something of the sort.
lets pray ))
Yea so anyway still locked and I honestly don't even need root. I'll just use the unlocked firmware and disable bloat. Rooting the s7 seems arbitrary at this point. If I wanted to I would just trade my s7 USA varient for an international varient if I was really that adamant. S7's are pretty cheap now with the s8 and s9 out on the market.
I have an unlocked phone and the only thing unlocked is the carrier or sim, nothing to do with the bootloader unless you all are suggesting that after the full release of Oreo on all the s7 devices that they may rethink locked bootloader. By then I'll probably just get a new phone. I've lost interest in rooting the s7 but that's probably because there's only three ways around it. Rooting Android 6, rooting earlier versions of Android 7 or getting the xynos s7. I love Oreo more than root on this phone.
I've been going through many pages and tried a few different ways of rooting my SM-N920V, but every page I go to tells me something a little different and it doesn't work. I've had to recover my phone a few times, but still can't get it rooted.
Specs:
SM-N920V
6.0.1
Originally I wanted to install Copperhead OS or Lineage, but from what I read, there's no way of installing either on my Verizon Note 5.
If anyone here has a way of installing Copperhead or any other privacy centric android build, please let me know.
Thanks! :highfive:
There isn't one...
Icetech3 said:
There isn't one...
Click to expand...
Click to collapse
as in its not possible?
curious as to why.
also, any suggestions you can give me to get my phone more private/un-googly?
Lakeesheontray said:
as in its not possible?
curious as to why.
also, any suggestions you can give me to get my phone more private/un-googly?
Click to expand...
Click to collapse
Verizon locked the bootloader so well that no one has been able to crack it on this phone and i don't believe anyone is even working on it anymore. Which means no real roms, no root...
Don't care if it works as a phone.
Icetech3 said:
Verizon locked the bootloader so well that no one has been able to crack it on this phone and i don't believe anyone is even working on it anymore. Which means no real roms, no root...
Click to expand...
Click to collapse
I have retired my Note 5 and currently have a Note 8. Since the device can be used for a whole lot more than a phone, is it possible to modify (root...whatever) the device considering that I don't care about tripping Knox (spelling?) or ever plan using it as a phone on VZW (or any other carrier, for that matter)? Right now it is sitting in a drawer and it isn't worth enough for me to sell it.
Thanks, Jack
jaxmaxinc said:
I have retired my Note 5 and currently have a Note 8. Since the device can be used for a whole lot more than a phone, is it possible to modify (root...whatever) the device considering that I don't care about tripping Knox (spelling?) or ever plan using it as a phone on VZW (or any other carrier, for that matter)? Right now it is sitting in a drawer and it isn't worth enough for me to sell it.
Thanks, Jack
Click to expand...
Click to collapse
Yeah, i'm too cheap to buy a new phone.. i use ting as my carrier, in my area i can use Sprint or T-Mobile towers.. my house gets ZERO signal from t-mobile and the verizon phone won't connect to sprint towers.. i hate it.. just *****ing, i'm gonna have to break down and get a different phone
Is anyone else still waiting for the December update to be available for OTA download? Google Pixel 3, unlocked, not rooted, not happy. Never waited this long before.
Is it a Verizon phone? Verizon updates are supposed to roll out this week. The update for non-Verizon phones was available last Monday.
I don't get OTA updates on my rooted phone because of root. I don't know if just being unlocked prevents OTA. You can always download the factory image and manually update. The images are at https://developers.google.com/android/images.
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Fat fingers! 1st sentence intended to be "Thank you for the response".
BlackKeys said:
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Click to expand...
Click to collapse
In that case, you will have to apply the update manually. The factory image is at the URL I gave previously. Edit flash-all.bat/sh to remove the -w from the last line in the file so the phone is not wiped.
You could also apply just the OTA manually. The OTA images are at https://developers.google.com/android/ota. I have not done that - I use the factory image method.
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
BlackKeys said:
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
Click to expand...
Click to collapse
You can search for update errors in logcat. See https://forum.xda-developers.com/t/tutorial-how-to-logcat.1726238/ on how to get a logcat. If you did the manual "Check for update" look in the log at the time you did the check. Logs are kept for quite a while, so the info should still be available.
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
dcarvil said:
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
Click to expand...
Click to collapse
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
TonikJDK said:
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
Click to expand...
Click to collapse
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
dcarvil said:
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
Click to expand...
Click to collapse
That has always been there, very sure of that. A lot of us went done that rabbit hole with the Pixel 1 or 2. We never new for sure what it did, but I remember freezing it and had all kinds of connection problems.
Other carriers have those types of things too. They are built into the image and go live when the phone sees what carrier it is on.