I tried to use the November 4th build but kept getting the setup wizard crashing. Do you know the reason for this? I haven’t tried the newest build because I didn’t know it was out but I think I might give it a try
When I edited the unlock code I did not include the # synbol I thought it was a line return. I used the Motorola scrub tool and I got the correct code and was sent unlock key.
Only problem no is in the developer options the “allow OEM unlocking” switch is greyed out.
Anyone know a way to fix this? Actually it “say connect to the internet or contact your carrier”. I do not have WiFi turn on or have a SIM in the phone. I was hesitant to connect to internet as Android or Moto wants to update the phone.
Any thought on this?
Edit: I had to login to the WiFi and then the unlock option became available.
When I reboot the phone running this build I security warning “this build was signed with public keys”. Do I have to be concerned about this and if so can I change the keys? There is also another warning SELinux is not enforcing… and SELinux is disabled. I think the second warning may be by design by e OS.
Hi, this download link appears to be down. Can you reupload?
EDIT: Nevermind, I see that you have to go through the unofficial builds list to get to the list of builds for this device rather than that specific November download. Thanks!
I have to agree that the build is, so far, so good; thank you guys, although I have posted some issues (primarily screen stops working during calls) elsewhere just in case it helps.