Related
Edit... Nevermind. I unlocked and then used LineageOS. Visualvoicemail app from AT&T working perfectly.
I was given a turbo last week and didn't take the moto update (it already had marshmallow) so I am looking at unlocking it and rooting. My main problem with the phone right now is since I am using AT&T, my visualvoicemail doesn't work. I think this may be due to call forwarding being disabled outside Verizon. Is there a way for me to enable it on AT&T? I figured if there was, it would require root.
I'm getting nagged to update my software even though I've disabled updates for the Motorola updates service, and disabled automatic updates in developer options. I'm currently running stock Oreo, and have been getting these every 24 hours or so, sometimes more.
I'm fine with taking the security updates, but I really don't want to upgrade to Pie. So much so that I exchanged the first X4 I had just so I could stay on the older update with a locked bootloader. My main concern is that I accidentally updated already, because they eventually take away the option to be reminded later instead. At this point I think I know how to avoid consenting to the update, but it would be nice if this annoyance was gone for good.
nguinn said:
I'm getting nagged to update my software even though I've disabled updates for the Motorola updates service, and disabled automatic updates in developer options. I'm currently running stock Oreo, and have been getting these every 24 hours or so, sometimes more.
I'm fine with taking the security updates, but I really don't want to upgrade to Pie. So much so that I exchanged the first X4 I had just so I could stay on the older update with a locked bootloader. My main concern is that I accidentally updated already, because they eventually take away the option to be reminded later instead. At this point I think I know how to avoid consenting to the update, but it would be nice if this annoyance was gone for good.
Click to expand...
Click to collapse
I had the exact same problem with the three moto x4 Amazon Prime versions. I contacted Amazon and Motorola - both told me there was no way to stop the update notices. I even explored app lockers hoping to find one that would let me lock the update notice app - no luck.
I finally gave up, purchased three moto x4 Android one versions (they are rootable) on sale at Best Buy, rooted them, then disabled the Motorola update service. No more update notices.
nogods said:
I had the exact same problem with the three moto x4 Amazon Prime versions. I contacted Amazon and Motorola - both told me there was no way to stop the update notices. I even explored app lockers hoping to find one that would let me lock the update notice app - no luck.
I finally gave up, purchased three moto x4 Android one versions (they are rootable) on sale at Best Buy, rooted them, then disabled the Motorola update service. No more update notices.
Click to expand...
Click to collapse
I see, I was afraid of that. I should have mentioned that I have the Android one version, but I was hoping not to have to root it. I play Pokemon GO sometimes, and it doesn't like it when your device is rooted, even using the method that's supposed to hide it.
Has anyone had any luck breaking OTA updates, possibly by flashing a slightly modified version of stock software? I was hoping to stay stock because that's usually best for the camera, but Gcam should get around that, right?
nguinn, just use magisk. i play PoGo also. use the X4 to GPS spoof for regional exclusives. works great. reddit.com/r/pokemongospoofing has a great tutorial on how to root your phone to make pokemon go not be able to see it.
Moto G5S Plus with "ID: bad key" problem and won't see updates (stuck on 7.1.1)
Hello, y'all. I have a Moto G5S Plus (XT1806) with an unlocked bootloader that is showing "ID: bad key" whenever I restart the phone and I have no idea what to even try to do, being that I have not ever even unlocked the bootloader on a phone, as I am having this problem with a phone I bought from eBay that had this issue when I received it.
The full message that displays on my phone is this: "Your device has been unlocked and can't be trusted. - To learn more, visit: motorola.com/unlockbootloader - ID: bad key - Your device will boot in 5 seconds."
For the record, I'm not really concerned with this message being displayed after I restart the phone, as the message goes away after about 5 seconds and the phone starts up properly and is able to be used (*for the most part, with two issues, which I will describe below this paragraph*), it's that the phone will not see any Android updates and is still stuck on these outdated settings: Android version: 7.1.1 - Current version: NPSS26.116-61-8 - Security patch level: April 1, 2018. And I have tried to search for updates with my T-Mobile SIM card in the phone, and also when connected to my home WiFi, but it will not see a new update available.
* The two issues that I referred to earlier have to do with actually making calls on the phone, with outgoing calls taking like 20-30 seconds to actually start dialing and incoming calls not even ringing through to my phone and sending callers straight to voicemail (the phone shows no notification of someone having tried to call me). Text messaging works properly, and I am able to connect to a strong LTE signal with my T-Mobile SIM card in the phone and I can use apps and websites without any issues. However, outgoing calls take much longer to dial out than they should take, and incoming calls will not work at all.
So, I am hoping that flashing a different ROM on to the phone will fix these calling issues and also allow the phone to update to a more-recent Android version. However, as I mentioned, I have not ever even unlocked a bootloader, much less, actually flashed a ROM on a phone, so I have no idea what I'm doing when it comes to things this. Also, for the record, I have tried multiple different APN settings on this phone, I have used my T-Mobile SIM card in another phone without any calling issues, and I have done multiple Factory Resets, but nothing has fixed the calling issues or allowed the phone to see any Android updates.
By the way, if flashing a different ROM might be worth trying on this device, being that I would be a first timer doing something like this, how difficult would this be? And about how long should the process likely take?
If anyone has any helpful advice, information or suggestions that they could offer me that might help to fix this issue with my Moto G5S Plus, I would appreciate any and all help that I could get!
Could anyone at least let me know if flashing a new/different ROM on this phone might help to fix the calling issue and allow it to see new Android updates? And if so, could someone recommend a ROM for me to try to flash?
I would really appreciate a reply.
Lol - you bought a device in which someone already unlocked the bl. Only way to get rid of the message is to lock the bl. But, an unlocked bl isn't causing you to not get updates.
Phazmos said:
Lol - you bought a device in which someone already unlocked the bl. Only way to get rid of the message is to lock the bl. But, an unlocked bl isn't causing you to not get updates.
Click to expand...
Click to collapse
I'm not sure why you find it funny that I bought a phone that already had the bootloader unlocked, but, yes, that's what I did. Also, as I specifically mentioned, I was not really concerned with the message that displays after restarting the phone; I was just hoping to get some information and/or advice about which ROM might be worth trying to flash and some suggestions about a simple way to try to flash a ROM for the first time, as I'm trying to figure out a way to fix the phone call issue and get the phone to see a new Android update.
If anyone sees this thread and is willing to offer a reply that might actually help me try to fix this issue with my Moto G5S Plus, I would really appreciate some help with this!
Bump. I have the same problem on a new phone on which I unlocked the bootloader -- Yes AZAssassin, neither am I sure why anybody would think it's funny to have an unlocked bootloader on a phone that's sold by Moto as easily bootloader-unlockable.
All I've done so far is unlock the bootloader and disable a few useless apps. No TWRP yet, no root, nada. But I keep getting the message that my phone is up to date. Model XT1806, Build number NPS26.116-45. I just want the security updates, not Oreo, but I can't get any updates at all.
I got the S10 recently, and when I went into developer options, the "OEM Unlock" option is missing. This confuses me since I ordered a Hong Kong model (SM-G9730) that supposedly allows for an unlockable bootloader according to people here and elsewhere. Would appreciate it if someone could help shed some light on this. If it matters, in Settings > About Phone, it definitely says SM-G9730 is the model, and under Software Information, the build number is G9730ZHU1ASBA, which is apparently the February 2019 build date.
Same issue
I'm getting the same problem. I am 100% certain without a shred of doubt that I have the exynos version but OEM unlocking does not appear in developer options immediately after developer options is turned on. From what I have noticed in my recent struggle to put this piece of ---- to good use, the OEM unlock option decides to appear after a certain amount of time after developer mode is enabled. Idk whose bright idea this was but if pissing off the customer was their goal then they did a stellar job.
I have this vague memory of reading that the oem unlock option is timed. So I went ahead and set the phone's system time to a month into the future (also checked 24 hour time but im not sure if that had an impact) to 7/9/19 while the phone was connected to wifi and now the OEM unlock option has appeared again. Hope this helps.
I have tried resetting the time trick a dozen times and OEM unlock does not appear. What is really frustrating is that it was there when I first got the phone and I had it turned on. Of course back in March, there was nothing you could do with the phone. Then bright people started to figure out how to root but by then, a firmware update had come along and OEM unlock disappeared. I tried to install Magisk but it failed badly. Now I'm stuck with the first phone/tablet I can't clean up all the unwanted crap I will never use or want. Very frustrating.
you need to wipe data, and when you set up your phone have wifi connected. Then it should appear in the options, if it does not change the time into the future
bengtc said:
you need to wipe data, and when you set up your phone have wifi connected. Then it should appear in the options, if it does not change the time into the future
Click to expand...
Click to collapse
I have reset the phone back to a previous firmware version, which should have wiped the data completely. I enabled Developers Options right away but OEM Unlock was not there. I tried the time thing again, but to no avail.
Of course my carrier promptly wanted to install the last update which I accepted. Strangely enough, the phone is behaving better since I did this but I still would prefer to have it rooted so I could get rid of a bunch of junk apps.
khocking said:
I have reset the phone back to a previous firmware version, which should have wiped the data completely. I enabled Developers Options right away but OEM Unlock was not there. I tried the time thing again, but to no avail.
Of course my carrier promptly wanted to install the last update which I accepted. Strangely enough, the phone is behaving better since I did this but I still would prefer to have it rooted so I could get rid of a bunch of junk apps.
Click to expand...
Click to collapse
So wait 7 days and it will be available ..
dynospectrum said:
So wait 7 days and it will be available ..
Click to expand...
Click to collapse
khocking...did this work for you?
I bought my device direct from Samsung, S10+, Snapdragon variant and I, too, am not seeing the OEM unlock, even after the time change and after 7 days.
Radio2006 said:
khocking...did this work for you?
I bought my device direct from Samsung, S10+, Snapdragon variant and I, too, am not seeing the OEM unlock, even after the time change and after 7 days.
Click to expand...
Click to collapse
Nope. I believe my carrier must have blocked it from appearing. I've given up all hope of rooting this phone and I'm learning to live with it the way it is. But this may very well be the last Samsung phone I have.
Why did you get the exynos verison?
Player04 said:
Why did you get the exynos verison?
Click to expand...
Click to collapse
It's the only version available in Canada
khocking said:
It's the only version available in Canada
Click to expand...
Click to collapse
This is unbelievably unreal. All these versions and only two are unlockable? I have always bought my phones direct from the manufacturer to prevent a carrier from telling me what I could and could not do with my phone, now the manufacturer is getting in on it. A waste of $1000. However, I refuse to accept this mode of operation. I will perform better research and find a phone that gives me the freedom I feel I am paying for.
Thanks for the information guys!
Solution:
https://www.youtube.com/watch?v=mF2Nxck4FtM
Note: You have Internet to be activated. But first i would do all other steps. and then restart, do time sync, deactivate set 7+ days back in time (25-7-2019 > 17-7-2019)
DONE! UNLOCK OEM appers (at least in aprils version)
||||| said:
Solution:
https://www.youtube.com/watch?v=mF2Nxck4FtM
Note: You have Internet to be activated. But first i would do all other steps. and then restart, do time sync, deactivate set 7+ days back in time (25-7-2019 > 17-7-2019)
DONE! UNLOCK OEM appers (at least in aprils version)
Click to expand...
Click to collapse
You might have noticed that I have said I've tried this a number of times to no avail.
This method does not work
JewsRshady said:
This method does not work
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=zqbu7jCmeMY
My OEM is grayed out off disabled will not let me go to download mode from recovery or by pressing the buttons phone will not register to odin at all it's not Verizon or TMobile either
khocking said:
It's the only version available in Canada
Click to expand...
Click to collapse
No it's not.
I just got off of the phone literally less than 5 mins ago with a Telus rep and we were discussing rooting (I'm in this forum wondering if there is a root method for the SD S10 version yet ~ I don't own one). He has the S10 and is waiting for a method to root it. We joked about how the Exynos version is inferior to the SnapDragon one. "Thank god we live in North America" he said.
So I don't know how you got the Exynos S10 from Telus. In Canada you should only be able to get the SnapDragon S10,
xunholyx said:
No it's not.
I just got off of the phone literally less than 5 mins ago with a Telus rep and we were discussing rooting (I'm in this forum wondering if there is a root method for the SD S10 version yet ~ I don't own one). He has the S10 and is waiting for a method to root it. We joked about how the Exynos version is inferior to the SnapDragon one. "Thank god we live in North America" he said.
So I don't know how you got the Exynos S10 from Telus. In Canada you should only be able to get the SnapDragon S10,
Click to expand...
Click to collapse
You're correct, I was mistaken in thinking the Qualcomm processor was the Exynos version. My apologies for that. Nevertheless, the OEM unlock switch is not available and has not been since the first updated firmware I got from Telus.
When I called Telus to ask about it, I got the run-around and essentially a non-answer. I have to believe it is Telus that is blocking this function although I've not read about anybody having this trouble who is with any of the other carriers. If you are looking to buy, you might explore this theory.
khocking said:
You're correct, I was mistaken in thinking the Qualcomm processor was the Exynos version. My apologies for that. Nevertheless, the OEM unlock switch is not available and has not been since the first updated firmware I got from Telus.
When I called Telus to ask about it, I got the run-around and essentially a non-answer. I have to believe it is Telus that is blocking this function although I've not read about anybody having this trouble who is with any of the other carriers. If you are looking to buy, you might explore this theory.
Click to expand...
Click to collapse
There is no root method yet for the SD S10.
It's not Telus, It's Samsung.
If you want root, don't buy a Samsung device. There will be a method eventually probably, but there has been a problem with root on the S line for quite some time now.
I would recommend a Pixel myself (monthly updates for 3yrs+), but there are other options out there.
I have recently purchased a Pixel 4 XL, in order to root it I have enabled USB debugging however the option of OEM unlock is greyed out, that means I won't be able to unlock the bootloader.
I want to root my phone in order to install Substratum themes, Please help me and let me know how I can enable OEM unlock option on my phone.
I have updated my Pixel 4 XL with latest MAY20 system update.
Purav786 said:
I have recently purchased a Pixel 4 XL, in order to root it I have enabled USB debugging however the option of OEM unlock is greyed out, that means I won't be able to unlock the bootloader.
I want to root my phone in order to install Substratum themes, Please help me and let me know how I can enable OEM unlock option on my phone.
I have updated my Pixel 4 XL with latest MAY20 system update.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-4-xl/help/how-to-sim-unlock-pixel-4xl-t-mobile-t4081235
My phone is not network locked phone, I have a Sim unlocked phone.... Only issue is Developer option is greyed out and I want to enable it.
It really depends on your carrier. If you bought it directly from Google (unlocked or Google Fi), it should be available without contacting anyone. I've heard that it might not be available until it has been activated for a few days with service. Otherwise, I've heard that you may need to fully wipe all user data before it becomes available. The process of OEM unlocking will wipe all user data as well, so you must be prepared for that eventuality.
If you did not get it from Google, the waters become murky and your success will vary.
Purav786 said:
I have recently purchased a Pixel 4 XL, in order to root it I have enabled USB debugging however the option of OEM unlock is greyed out, that means I won't be able to unlock the bootloader.
I want to root my phone in order to install Substratum themes, Please help me and let me know how I can enable OEM unlock option on my phone.
I have updated my Pixel 4 XL with latest MAY20 system update.
Click to expand...
Click to collapse
If you bought a Pixel 4 XL with a unlockable bootloader, use this Guide to root.
Most Pixel 4 XL that are purchased from Carriers with the exception of Google Fi are not bootloader unlockable.
Purav786 said:
My phone is not network locked phone, I have a Sim unlocked phone.... Only issue is Developer option is greyed out and I want to enable it.
Click to expand...
Click to collapse
You aren't providing much useful information to solve your problem in your OP. Post a screenshot of your bootloader page, and what are the first two digits of your IMEI's. If you have already 100% WIPED your phone, skipped through setup and gone straight to dev settings with an active Wi-FI signal and get a greyed out OEM unlock , you will likely never succeed because you inadvertently purchased a bootloader locked phone. SIM unlocked definitely does not equal BL unlockable.
v12xke said:
You aren't providing much useful information to solve your problem in your OP. Post a screenshot of your bootloader page, and what are the first two digits of your IMEI's. If you have already 100% WIPED your phone, skipped through setup and gone straight to dev settings with an active Wi-FI signal and get a greyed out OEM unlock , you will likely never succeed because you inadvertently purchased a bootloader locked phone. SIM unlocked definitely does not equal BL unlockable.
Click to expand...
Click to collapse
So that means my phone is bootloader locked phone and there is no way to unlock it...
Purav786 said:
So that means my phone is bootloader locked phone and there is no way to unlock it...
Click to expand...
Click to collapse
Remove SIM, factory reset from recovery, initiate setup enabling Wi-Fi, proceed to dev settings and check "Allow OEM unlocking". If you have completely wiped the phone and OEM unlocking is still greyed out, then your phone is bootloader locked and there is no workaround.
I downgraded my p40 lite to lowest version of emui...
which is 10.0.1.108 and oem unlock option appeared but its grayed out and I took advice from the guy in this thread that said call them and tell them you are developer and you need it to install android 11 and they were like oh ok then will figure this out and give you a call hahahahhaahahahhahah awesome dude it worked
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
I saw there is a tool created by skyemie on github that uses bruteforce method to retrieve the unlock code so if they fix my oem grayed option then I will try that and give you all update if everything worked.
Just a FWIW: I bought two phones from Google directly and returned both since OEM was greyed out on both. Third try I purchased one off Swappa and it worked. Something to do with the IMEI... Search for posts started by me.. It's a looooong thread.
If you got your pixel from Verizon, just call them and say that you're a developer and you need OEM unlocking. They'll need your IMEI and Verizon account number tho to check that you're the owner. If you got it second hand you may have to contact the person you bought it from.
CoNsTaR said:
If you got your pixel from Verizon, just call them and say that you're a developer and you need OEM unlocking. They'll need your IMEI and Verizon account number tho to check that you're the owner. If you got it second hand you may have to contact the person you bought it from.
Click to expand...
Click to collapse
Do you have a source for this? The only official answer I've seen is that Verizon has no process in place to enable OEM unlocking. It's actually baked into the ROM.
V0latyle said:
Do you have a source for this? The only official answer I've seen is that Verizon has no process in place to enable OEM unlocking. It's actually baked into the ROM.
Click to expand...
Click to collapse
I did it. I saw someone saying that calling T-Mobile does the job so I just decided to call Verizon too and it worked.
CoNsTaR said:
I did it. I saw someone saying that calling T-Mobile does the job so I just decided to call Verizon too and it worked.
Click to expand...
Click to collapse
Well, that's interesting. What exactly were the circumstances, and how did you get unlocked? Such as, were you using the phone on the VZW network? Did they push a software update or something?
V0latyle said:
Well, that's interesting. What exactly were the circumstances, and how did you get unlocked? Such as, were you using the phone on the VZW network? Did they push a software update or something?
Click to expand...
Click to collapse
From what I know, by the moment you install a Verizon SIM on your pixel, it becomes a Verizon phone. How they do this is that they'll add your phone's IMEI to their database, and until it's deleted from their database your phone will be a Verizon phone. You can check that by trying adding an eSIM, if it says anything about Verizon at the QR code step, you know it's still bound to Verizon.
I think the mechanism of checking if the phone is bound to any carrier is baked in the ROM, but not the information itself. I do see people saying that it needs time for the records to be propagated after they've removed you from their database, but YMMV.
Edit:
No, I wasn't on the VZW network.
CoNsTaR said:
From what I know, by the moment you install a Verizon SIM on your pixel, it becomes a Verizon phone. How they do this is that they'll add your phone's IMEI to their database, and until it's deleted from their database your phone will be a Verizon phone. You can check that by trying adding an eSIM, if it says anything about Verizon at the QR code step, you know it's still bound to Verizon.
I think the mechanism of checking if the phone is bound to any carrier is baked in the ROM, but not the information itself. I do see people saying that it needs time for the records to be propagated after they've removed you from their database, but YMMV.
Edit:
No, I wasn't on the VZW network.
Click to expand...
Click to collapse
Right, and I'm asking exactly how you did it.
V0latyle said:
Right, and I'm asking exactly how you did it.
Click to expand...
Click to collapse
The ONLY thing I did is to call them, tell them I am a developer and I need OEM unlocking, and provide the information they needed. Hope this answers your question.
I've called Verizon 6 times and talked to several reps and no idea what I'm talking about. I was even sent to 2nd tier and nothing. The 2nd tier rep said he's worked at vzw for 8 years and has never seen or heard of this happening. So I find this whole thing hard to believe.
I am just providing my experience, and maybe someone will benefit from it. I came across this thread when I did my research so I thought I should share it here too.
If more details may help, I called them with the number 800-922-0204, on Oct 27 9:48 AM, the time I spent on the call was 36m4s (30m or so was waiting on the line), and I was on Fido network (Canadian).
When the system asked me about my area code or something like that before they connect me with a human, I both entered # key, and also chose something like I want to be a Verizon customer.
That's really all what I did, and I got it done on the first try. This was my first time calling Verizon, so I don't know much about 2nd tier or what not, but that's all I wanted to share here.
hey guys I know I'm not in the right group but I've been looking at Any Pixel related posts to try to get OEM unlock and came across some options using dialer code *#*#0702#*#* which is ims setting, sim provisioning and a lot more in which are editable. could we find something to do with network unlock in those settings? I'm attaching screen shots of this find. I'm very limited in knowledge as this is my first pixel. oh and Btw I have the spectrum mobile variant of the Google pixel 7 pro. I have always been under the assumption that pixels were able to be flashed with official firmware without bootloader unlocked, but apparently pixel 7s have to have network unlock at least to enable OEM unlock toggle to flash official firmware even with the Android flash tool. if anybody could shine some light on this for me I would greatly appreciate it as I have never been able to come across this type of information before on any other device