Hi everyone, congratulations for the really great site. Now answer me if you already have the unlock / removal procedure of the google account of the Motorola Moto XT1640 Android 7.0 Nougat and security patch December 1, 2016 ???? Because I've tried everything, app test dpc, terminal, dirtycow, and nothing ... If you can not think nobody else, except for the technical assistance, Thanks and congratulations.
digaoartes said:
Hi everyone, congratulations for the really great site. Now answer me if you already have the unlock / removal procedure of the google account of the Motorola Moto XT1640 Android 7.0 Nougat and security patch December 1, 2016 ???? Because I've tried everything, app test dpc, terminal, dirtycow, and nothing ... If you can not think nobody else, except for the technical assistance, Thanks and congratulations.
Click to expand...
Click to collapse
You mean you are locked out of your Google account? If this is the case you need to wait for 72 hours.
any solution for 1st nov patch , m also stucked in frp ... although m able to access the phone through sidebar but oem is locked , dirtycow is not working showing "cannot execute binary file " plss help me out
cooldudekapz said:
any solution for 1st nov patch , m also stucked in frp ... although m able to access the phone through sidebar but oem is locked , dirtycow is not working showing "cannot execute binary file " plss help me out
Click to expand...
Click to collapse
You have to use your last synced google id, or if you had multiple ids then try with each one of those. I had frp too 2-3 times but it lets me proceed after entering the correct google id & password
Dirtycow, dpc etc..all these will probably fail because google fixes it by releasing monthly security updates.
Can't you boot into bootloader and make a factory reset?
Sent from my Motorola Moto G4 Plus using XDA Labs
djumie said:
Can't you boot into bootloader and make a factory reset?
Sent from my Motorola Moto G4 Plus using XDA Labs
Click to expand...
Click to collapse
Nope FRP still exists. It's something from google's end, you either remember your google id & password or else find a way to bypass FRP
lCrD512 said:
Nope FRP still exists. It's something from google's end, you either remember your google id & password or else find a way to bypass FRP
Click to expand...
Click to collapse
Oh, ok! Sorry if it sounds like a dumb question but may I ask what FRP means?
Sent from my Motorola Moto G4 Plus using XDA Labs
djumie said:
Oh, ok! Sorry if it sounds like a dumb question but may I ask what FRP means?
Sent from my Motorola Moto G4 Plus using XDA Labs
Click to expand...
Click to collapse
Full form is Factory reset protection. You can get detail info by google search
lCrD512 said:
Full form is Factory reset protection. You can get detail info by google search
Click to expand...
Click to collapse
Really? I never knew about this! I'll research for better understanding. Thank you!
Sent from my Motorola Moto G4 Plus using XDA Labs
Small tip that everyone forgets:
if you keep the setting 'OEM unlocking' in developer options enabled then you desable this FRP. (in this case it's too late of course).
Droidphilev said:
Small tip that everyone forgets:
if you keep the setting 'OEM unlocking' in developer options enabled then you desable this FRP. (in this case it's too late of course).
Click to expand...
Click to collapse
oem is also locked .. i tried to unlock oem by adb .. but its not working
cooldudekapz said:
oem is also locked .. i tried to unlock oem by adb .. but its not working
Click to expand...
Click to collapse
what do you mean?
What i mean is that if you keep te switch "OEM unlocking" in developer options is enabled you cannot get locked out for 72 hours IN THE FUTURE. it won't help WHILE being locked out of course.
Droidphilev said:
what do you mean?
What i mean is that if you keep te switch "OEM unlocking" in developer options is enabled you cannot get locked out for 72 hours IN THE FUTURE. it won't help WHILE being locked out of course.
Click to expand...
Click to collapse
unable to switch on developer mode , developer mode is locked in nov patch
cooldudekapz said:
unable to switch on developer mode , developer mode is locked in nov patch
Click to expand...
Click to collapse
Have you tried to contact Google, see if you can recover your credentials to log into the device? Seems you're running head long into Android's anti-theft security measures.
Related
For anyone who has just picked up a Moto G and plans to unlock their bootloader, unlock it before updating to 4.4.4. There is currently a bug with the unlock codes on the 4.4.4 bootloader and the workaround is a hassle. The issue isn't present on 4.4.2, you can update once your bootloader is unlocked.
Jdiesel87 said:
For anyone who has just picked up a Moto G and plans to unlock their bootloader, unlock it before updating to 4.4.4. There is currently a bug with the unlock codes on the 4.4.4 bootloader and the workaround is a hassle. The issue isn't present on 4.4.2, you can update once your bootloader is unlocked.
Click to expand...
Click to collapse
The bootloader is the culprit.
Mine came with 4.4.3 and it has thus problem already.
Sent from my Nexus 5 using XDA Free mobile app
Whats the issue.(you never said what it was)
.
Guicrith said:
Whats the issue.(you never said what it was)
Click to expand...
Click to collapse
The issue, when you receive the Motorola's code and enter it in the cmd get an error message. At least, that happened to me.
Hi! I bought the phone with the 4.4.2 update, and hurried him through the air to 4.4.4. And now I can not unlock the boot loader (incorrect password). Tried to go back to 4.4.2, and it does not work. When Motorola is the solution?
Jdiesel87 said:
the workaround is a hassle.
Click to expand...
Click to collapse
Thanks @Jdiesel87 for heads up. As you mentioned that there is a workaround , can you please point out or explain what it is , so that it will help the people who updated to 4.4.4 on first day itself..
Sure thing. In order to get the fix from Motorola you need to visit the thread on their forum at:
https://forums.motorola.com/posts/f2061da875?commentId=798955#798955
You will need to sign up for the Motorola Feedback Network under your account settings, register your device with your IMEI number, and opt in to receive emails from Motorola. Once you have done that post on the above thread alerting the moderators that you have completed those steps.
I can't comment on anything after that point as the Motorola beta program has a non-disclosure agreement but they will help you from there.
Jdiesel87 said:
Sure thing. In order to get the fix from Motorola you need to visit the thread on their forum at:
https://forums.motorola.com/posts/f2061da875?commentId=798955#798955
You will need to sign up for the Motorola Feedback Network under your account settings, register your device with your IMEI number, and opt in to receive emails from Motorola. Once you have done that post on the above thread alerting the moderators that you have completed those steps.
I can't comment on anything after that point as the Motorola beta program has a non-disclosure agreement but they will help you from there.
Click to expand...
Click to collapse
Thanks for a quick response. And I respect NDA with beta program.
This will definitely help people who would like to seek help.
thanks for the heads up.
fiddlestix!!
i stupidly upgraded before reading this. am i likely to get the error on moto g 8gb?
Jdiesel87 said:
For anyone who has just picked up a Moto G and plans to unlock their bootloader, unlock it before updating to 4.4.4. There is currently a bug with the unlock codes on the 4.4.4 bootloader and the workaround is a hassle. The issue isn't present on 4.4.2, you can update once your bootloader is unlocked.
Click to expand...
Click to collapse
killer23d said:
The bootloader is the culprit.
Mine came with 4.4.3 and it has thus problem already.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So moral of the story is,,unlock bootloader while 1 is still using 4.4.2,,right?
I got my moto g 2 days ago. model XT1033 dual sim india . When I got it the android version was 4.4.4 .. and I have just successfully unlocked the bootloader. ... bt.. im not able work any custom recoveries... I flashed many recoveries using fastboot commands, bt after selecting the recovery from fast boot list , the phone shows the bootlogo then a black screen with some random lines or something.. is this becoz of the bootloader issue ?
jayOOMjay said:
I got my moto g 2 days ago. model XT1033 dual sim india . When I got it the android version was 4.4.4 .. and I have just successfully unlocked the bootloader. ... bt.. im not able work any custom recoveries... I flashed many recoveries using fastboot commands, bt after selecting the recovery from fast boot list , the phone shows the bootlogo then a black screen with some random lines or something.. is this becoz of the bootloader issue ?
Click to expand...
Click to collapse
This recovery works on 4.4.4
http://forum.xda-developers.com/showthread.php?t=2639583
robin0800 said:
This recovery works on 4.4.4
http://forum.xda-developers.com/showthread.php?t=2639583
Click to expand...
Click to collapse
I tried that one first, it shows black blinking screen
jayOOMjay said:
I got my moto g 2 days ago. model XT1033 dual sim india . When I got it the android version was 4.4.4 .. and I have just successfully unlocked the bootloader. ... bt.. im not able work any custom recoveries... I flashed many recoveries using fastboot commands, bt after selecting the recovery from fast boot list , the phone shows the bootlogo then a black screen with some random lines or something.. is this becoz of the bootloader issue ?
Click to expand...
Click to collapse
Which recoveries you flashed?
rohitthe1 said:
Which recoveries you flashed?
Click to expand...
Click to collapse
philz, cmw( touch and non touch ), twrp
Thanks for the heads up. : D
So what is the procedure to unlock our device if we made the update? Because I'm a bit confused here
I aslo successfully root moto g 4.4.4 version with superbot.
when unlocking bootloader it says unlocking failed messege buy when i restar it says warning unlocked bootloader.
I have this problem and i posted in the Motorola forum on wednesday... still no response. No mail, no beta, no response in the thread itself. I've followed all the steps that they asked.
I have a bad feeling.
current account is not bound to this device. this error I get when I try to unlock bootloader of redmi 3S. what I do now??
update latest version of miui and check
same
same problem with me i am on beta global.. please tell me if u find any solution
varungajjarrock said:
same problem with me i am on beta global.. please tell me if u find any solution
Click to expand...
Click to collapse
After getting permission, you cannot unlock your bootloader immediately. You have to wait a bit, say, 1 week before you can unlock.
joe34 said:
after getting permission, you cannot unlock your bootloader immediately. You have to wait a bit, say, 1 week before you can unlock.
Click to expand...
Click to collapse
can i try in this one week or i should not try?
varungajjarrock said:
can i try in this one week or i should not try?
Click to expand...
Click to collapse
Read what I said again. I think it's clear.
joe34 said:
After getting permission, you cannot unlock your bootloader immediately. You have to wait a bit, say, 1 week before you can unlock.
Click to expand...
Click to collapse
Got permissions on the 15th, it's now the 23rd. Still can't unlock. Going to try on the 25th again.
ZETROzky said:
Got permissions on the 15th, it's now the 23rd. Still can't unlock. Going to try on the 25th again.
Click to expand...
Click to collapse
Are you logged in with that account on your phone? Is backup phone turned on? Is find device turned on? (Tinker with the settings of the miui account. I got permission after 3 days of submitting a request and immediately unlocked the bootloader)
bekcicandrej said:
Are you logged in with that account on your phone? Is backup phone turned on? Is find device turned on? (Tinker with the settings of the miui account. I got permission after 3 days of submitting a request and immediately unlocked the bootloader)
Click to expand...
Click to collapse
Yes, yes and yes. I tried yesterday, nothing.
joe34 said:
After getting permission, you cannot unlock your bootloader immediately. You have to wait a bit, say, 1 week before you can unlock.
Click to expand...
Click to collapse
bekcicandrej said:
Are you logged in with that account on your phone? Is backup phone turned on? Is find device turned on? (Tinker with the settings of the miui account. I got permission after 3 days of submitting a request and immediately unlocked the bootloader)
Click to expand...
Click to collapse
it seems that u didnt changed ur rom from a long time and ur account got bind with ur phone before getting permission so that u can unlock after getting req immediately.. am i correct?
Still. Not. Binding.
Still. Can't. Unlock.
Sent from my land using XDA Labs
varungajjarrock said:
it seems that u didnt changed ur rom from a long time and ur account got bind with ur phone before getting permission so that u can unlock after getting req immediately.. am i correct?
Click to expand...
Click to collapse
Nope. So I got the phone. Created the miui profile, saw the Chinese apps and decided to find a way to get ride of them. Found out 2 days later that I need to unlock, applied for unlocking. 3 days later got permission. 2h later unlocked via unlocking tool. This was 8 months ago
Now I've noticed that you need to enable oem unlocking in the dev options, before going into fastboot to unlock
But one more thing comes, that I did and that's fully entering all the info on my profile (security questions etc)
And yes my miui account is bound to this​ phone, when I install miui it doesn't even ask for a account just a password
Finally unlocked it today.
Sent from my land using XDA Labs
ZETROzky said:
Finally unlocked it today.
Click to expand...
Click to collapse
Did anything special? And how much days it take?? And u were trying daily?
Have been reading a lot about this and have tried every method explained. My conclusion is, it's based on luck. XIOMI screwed the b/l unlocking method like many things and you need to be lucky to smoothly unlock it.
I assume you have already followed every single rule like waiting for some days before trying and connecting the phone and unlocking tool with same account, disabling lock screens or that find device thing they say and many others with no luck.
I believe since redmi 3s is a dual sim so if you are using another simcard your best bet is to try making a new account with that number and try the whole process again. About waiting... well, many have been waiting for months, so don't much from waiting and retrying luck.
Hopefully we will get some unofficial unblocking method someday, like note 3 has.
---------- Post added at 09:23 PM ---------- Previous post was at 09:22 PM ----------
ZETROzky said:
Finally unlocked it today.
Sent from my land using XDA Labs
Click to expand...
Click to collapse
Please tell how you were able to unlock. Were you on global stable? Which trick worked for you?
I have a Special Edition (pro prime 152mm) with the Special Edition Dev ROM.
I got the unlock approval 8 days ago, I can locate my device using MI account but the binding doesn't work. (Settings>Additional settings>Developer Options>Mi Unlock Status>Add account and device) Please retry within 1 or 2 minutes again and again and again...
I tried the tool in version 1.0.1225.2, 1.1.03171.1 and last 2.2.406.5.
Still no binding possible.
I have got my permission 1 day before
it is still not unlocking
what to do now??
1+2=3 said:
I have got my permission 1 day before
it is still not unlocking
what to do now??
Click to expand...
Click to collapse
Enable Dev settings by clicking 5 times onto MIUI Version number in settings then go in other settings > des settings > lock status and try to bind
1+2=3 said:
I have got my permission 1 day before
it is still not unlocking
what to do now??
Click to expand...
Click to collapse
1 day before? Then wait a week before trying to bind device and unlock your bootloader.
My BL is not unlocking as the account is not binding in the dev setting>unlock status and therefore unlocking stops at 99%.
If anyone facing the error 86012 had later unlocked their BL later, please tell us clearly what did you do. "I just need to know that is there someone who had unlocked without binding their account."
Sent from my land using XDA Labs
Hey! Whats up bros! I am dRb & I successfully unlocked BL today. Before going to trick I should say some myths about unlocking BL. There are tons of YouTube as well as xda xiomi forum BL Unlocking methods posted by our beloved Developers .
I got permission just 4 days after submitting an application. Tried after two weeks but failed - Phone Can Not be verified blah bhah.... After four days I successfully unlocked BL.
Nothing you have to do just try after some days after getting permission. Make sure ENABLE DEVELOPER OPTION, OEM UNLOCKING, no need to bind your device with account, if you do, everytime you will get Chinese Sh!t Error, even fly vpn can do nothing!!! no need to flash developer ROM
Hope You understand. Try with latest unlocking tool
itsmedRb said:
Hey! Whats up bros! I am dRb & I successfully unlocked BL today. Before going to trick I should say some myths about unlocking BL. There are tons of YouTube as well as xda xiomi forum BL Unlocking methods posted by our beloved Developers .
I got permission just 4 days after submitting an application. Tried after two weeks but failed - Phone Can Not be verified blah bhah.... After four days I successfully unlocked BL.
Nothing you have to do just try after some days after getting permission. Make sure ENABLE DEVELOPER OPTION, OEM UNLOCKING, no need to bind your device with account, if you do, everytime you will get Chinese Sh!t Error, even fly vpn can do nothing!!! no need to flash developer ROM
Hope You understand. Try with latest unlocking tool
Click to expand...
Click to collapse
And what is latest unblocking tool ?
tharmor said:
And what is latest unblocking tool ?
Click to expand...
Click to collapse
2.2
itsmedRb said:
2.2
Click to expand...
Click to collapse
It does not work !!
tharmor said:
It does not work !!
Click to expand...
Click to collapse
bro again tell u ,, try after some days
Enable OEM Unlocking not found.
i have an mtk redmi note 4. but i dont have any "enable oem ulocking" in my developer option. i tried almost every rom for getting the option. but still i didnot find the option. please help me unlocking my device....
zimamahmed said:
i have an mtk redmi note 4. but i dont have any "enable oem ulocking" in my developer option. i tried almost every rom for getting the option. but still i didnot find the option. please help me unlocking my device....
Click to expand...
Click to collapse
mybe u device come with fake rom. try screenshot your MIUI version
[Deleted]
Is there a way to root the amazon ads version of this phone or are we stuck in the same boat as the verizon version?
Bump
I've been reading up on the Moto G4 Play forums and I am wondering if initroot is possible with the Moto E4. I've run the sunshine APK and it says the pretests have passed and that temproot is needed to continue. So would initroot + sunshine = unlock? Or are sunshine and initroot patched. Do I have this all wrong or??? Would love some input, thanks.
EDIT: Appears SunShine doesn't support the E line of devices, may still work though...
this tethered vulnerability was fixed back in June ...moto e4 comes out of the box with higher than June security patch .......
KevMetal said:
this tethered vulnerability was fixed back in June ...moto e4 comes out of the box with higher than June security patch .......
Click to expand...
Click to collapse
So are SOL then?
Sent from my Moto E4 using XDA Labs
TheJAYpoop said:
So are SOL then?
Click to expand...
Click to collapse
hard to say with finality but definitely SOL if uour security patch is higher than June in regards to the exploits you want to use
TheJAYpoop said:
Is there a way to root the amazon ads version of this phone or are we stuck in the same boat as the verizon version?
Click to expand...
Click to collapse
Have you entered your code on moto site to see if it can be unlocked? Just curious. I thought I saw someone with that amazon ads version unlock the bootloader. I could be wrong though.
madbat99 said:
Have you entered your code on moto site to see if it can be unlocked? Just curious. I thought I saw someone with that amazon ads version unlock the bootloader. I could be wrong though.
Click to expand...
Click to collapse
Yeah i've tried it a few times but unfortunately it doesn't work, for some people it works for some reason. Hopefully someone can find a temp root solution then sunshine MIGHT work.
madbat99 said:
Have you entered your code on moto site to see if it can be unlocked? Just curious. I thought I saw someone with that amazon ads version unlock the bootloader. I could be wrong though.
Click to expand...
Click to collapse
I think that was just a tutorial on how to disable ads/bloatware with fastboot.
volatile1 said:
I think that was just a tutorial on how to disable ads/bloatware with fastboot.
Click to expand...
Click to collapse
I've already removed the ads when I got it.
Sent from my Moto E4 using XDA Labs
It would be cool if someone created an unofficial Android 8 update for the e4's based on the stock kernel and everything so we could flash it without unlocked bootloader. Or is that not possible...
Sent from my Moto E4 using XDA Labs
TheJAYpoop said:
It would be cool if someone created an unofficial Android 8 update for the e4's based on the stock kernel and everything so we could flash it without unlocked bootloader. Or is that not possible...
Click to expand...
Click to collapse
without an unlocked bootloader you can',t flash files they don't get written unless signed by manufacturer so your Oreo would have to come from LenovoMoto
http://www.openwall.com/lists/oss-security/2017/11/30/1
root
I need root with this vulnerability, then I think you can change the firmware to another version
not an amazon
Well I dont feel like waiting for a bootloader unlock that will most likely never happen, I'm sending my Amazon e4 back and getting a normal version. Good luck to you all!
Sent from my Moto E4 using XDA Labs
madbat99 said:
Have you entered your code on moto site to see if it can be unlocked? Just curious. I thought I saw someone with that amazon ads version unlock the bootloader. I could be wrong though.
Click to expand...
Click to collapse
I just tried this with the bootloader unlock code from my Amazon Moto E4 on Motos website..."Your device does not qualify for bootloader unlocking"...F*ckers...lol...
amazon just canceled the ad program, all devices will have the ads removed...
http://www.zdnet.com/article/amazon-removing-lockscreen-offers-and-ads-from-prime-exclusive-phones/
wonder if it would affect the bootloader unlock policy
djdevin said:
amazon just canceled the ad program, all devices will have the ads removed...
http://www.zdnet.com/article/amazon-removing-lockscreen-offers-and-ads-from-prime-exclusive-phones/
wonder if it would affect the bootloader unlock policy
Click to expand...
Click to collapse
Not a chance. Zero incentive for Amazon to change the status quo.
its been a few months since ive tried to unlock my amazon e4's bootloader, so i tried it again... IT WORKED. I bought this phone on Aug. 26, 2017...so not quite a year old, but i was able to unlock it following the instructions on motos website.
It figures too...I just picked up a Pixel XL for $200 too...oh well. If you guys are still interested in unlocking, give it a try now before Amazon or Moto change their minds!
juggalofr33k said:
its been a few months since ive tried to unlock my amazon e4's bootloader, so i tried it again... IT WORKED. I bought this phone on Aug. 26, 2017...so not quite a year old, but i was able to unlock it following the instructions on motos website.
It figures too...I just picked up a Pixel XL for $200 too...oh well. If you guys are still interested in unlocking, give it a try now before Amazon or Moto change their minds!
Click to expand...
Click to collapse
I am truly shocked! The cost/effort to maintain an exclusion list of device identifiers must have outweighed the business benefit (Amazon ecosystem lockin) assuming it was not an inadvertent disclosure. That leaves Verizon (XT1767) as the only major that can't be bootloader unlocked.
I noticed the price gap between 'prime' and 'standard' variants has narrowed of late - perhaps in recognition of revenue loss due to lack of lock screen ads (Amazon policy change) and/or more freedom to root and remove Amazon exclusive content - aka 'bloat'.
got excited, but sad to report it didn't work for me.
LISTEN AND LISTEN WELL. i dont take responsibility for paper weights i just stumbled across this while trying to unlock my pixel xl 128 GB on verizon cid update to the latest OFFICIAL version of pie. then use this tool credit goes to this awesome guy for the tool. https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730227
ok then you remove COM.ANDROID.PHONE ONLY!!!!!!!!
then sign up for the android Q/10 beta and do the ota. NOTE THAT YOU MUST RESTART
BEFORE THE BETA OTA TO DO THIS SUCSESSFULLY. after you restart go to settings then activate dev options if you havent then allow oem unlock SHOULD BE THERE. good lock to you all!!!!!
Dlind said:
LISTEN AND LISTEN WELL. i dont take responsibility for paper weights i just stumbled across this while trying to unlock my pixel xl 128 GB on verizon cid update to the latest OFFICIAL version of pie. then use this tool credit goes to this awesome guy for the tool. https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730227
ok then you remove COM.ANDROID.PHONE ONLY!!!!!!!!
then sign up for the android Q/10 beta and do the ota. NOTE THAT YOU MUST RESTART
BEFORE THE BETA OTA TO DO THIS SUCSESSFULLY. after you restart go to settings then activate dev options if you havent then allow oem unlock SHOULD BE THERE. good lock to you all!!!!!
Click to expand...
Click to collapse
Hi, can you be more specific how do you do that? since seems like it Google patched OEM unlocking and after using normal method
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
that OEM unlocking still grayout under settings.
work today ?
RubenPCA said:
work today ?
Click to expand...
Click to collapse
No. It's been heavily discussed here. Google has patched the exploit that allowed this to work and as of right now there is no solution.
Hazard15301 said:
No. It's been heavily discussed here. Google has patched the exploit that allowed this to work and as of right now there is no solution.
Click to expand...
Click to collapse
Do>it now!
The bootloader unlock for the Verizon Pixel/Pixel XL is working. Go here to unlock it.