Database Users

Android M help

Hello! I have just upgraded to Android M and I have two quick questions: 1 is , is it a problem if my system did not have any problems updating , even though I am S-OFF and my boot-loader is unlocked, this system being installed from a zip? 2 is, I do not have the brightness bar in the notification area, and that is a feature I used to use a lot, yet it isn't there, and I can't find it anywhere in settings. Please help on the second one and tell me if this is supposed to happen or not, also BTW in the boot loader it says System status: official, but it is S-OFF and the boot loader is unlocked.

1-Did you unlock the bootloader or it was unlocked when you got the phone? maybe you have the developer edition phone.
2-I think this option is not available for the M9+ you need to use an app like Brightness slider control or any other app from google play

Reply
About your first question: I was the one who unlocked the boot loader because I had the clean slate ROM installed and just reverted to stock, yet the stock ROM was a very old version and because it was S-OFF and the boot loader was unlocked I feared that I might not get the marshmallow update, yet I decided to try and install the update anyways, and to my surprise it worked flawlessly. Is this normal lol

Unable to update Google apps on 6.0.1 after trying 7.1.1?

So yesterday I tried Resurrection Remix on my phone. Then I decided to go back to stock (I like trying ROMs).
I did several clean flashes to try to get rid of this new problem (as in I wiped every partition including system and then flashed and relocked my bootloader). When the updates start, Google Play Services crash. This is new but fair enough. But then, Google Maps can't update, I get an error (Error retrieving information RPC:S-13:AEC-13 5 JOK-MVMB-5QA). Then same with Google itself, Google Drive, Translation, Clock and Chrome all fail.
Once the original update process is done, I can retry those and they end up updating. But the, when I get to install my apps, the same problem happens!
This is a new problem I've never had before. Could it be related to me trying Resurrection Remix? Like my account is now linked to more recent google services or something?
Thanks

So I've put TWRP back and not only wiped but repaired all the filesystems (data, system, etc.) then flashed again. Everything went smootly except one app that gave me an error but I just pressed "Install" again and it went right through!
Guess that was the problem!

Still getting the Google Play Services has stopped error after first boot and before it starts updating (so after the Google Play Store has updated itself). If I reboot it's OK. I feel like there's something on the server side of things.

Prosis said:
Still getting the Google Play Services has stopped error after first boot and before it starts updating (so after the Google Play Store has updated itself). If I reboot it's OK. I feel like there's something on the server side of things.
Click to expand...
Click to collapse
Hello,
One question: how you relock the bootloader? me i install also 7.1.1 after reflash the stock rom with fastboot procedure but at the end when i type: fastboot oem lock say ok. Restart phone but message bootloader unlock stay.

pots22 said:
Hello,
One question: how you relock the bootloader? me i install also 7.1.1 after reflash the stock rom with fastboot procedure but at the end when i type: fastboot oem lock say ok. Restart phone but message bootloader unlock stay.
Click to expand...
Click to collapse
You'll always get that message, it's by design. The bootloader is locked but its status is 2 which means it has been unlocked. They added this message so people wouldn't try to send back the phone if they have a problem after flashing something on it (officially it's to protect buyers who would buy used phones but, you know, come on... ).
There's a logo.bin file on this forum that you have to flash in order to get rid of the message. If you want to make your own, you can also search for MotoBootLogoMaker.zip and use the logo.bin that comes with your stock ROM. If you search for this on the forum you'll find several threads about it.

Prosis said:
You'll always get that message, it's by design. The bootloader is locked but its status is 2 which means it has been unlocked. They added this message so people wouldn't try to send back the phone if they have a problem after flashing something on it (officially it's to protect buyers who would buy used phones but, you know, come on... ).
There's a logo.bin file on this forum that you have to flash in order to get rid of the message. If you want to make your own, you can also search for MotoBootLogoMaker.zip and use the logo.bin that comes with your stock ROM. If you search for this on the forum you'll find several threads about it.
Click to expand...
Click to collapse
Ok thank's, i flash first: 'fastboot oem lock begin' after the stock Rom and 'fastboot oem lock' and finaly logo.bin

pots22 said:
Ok thank's, i flash first: 'fastboot oem lock begin' after the stock Rom and 'fastboot oem lock' and finaly logo.bin
Click to expand...
Click to collapse
Yes and then if you decide to try another ROM before going back to stock, you can skip logo.bin file in the process so you don't have to flash the one without the warning again.

Question about wiping with twrp, dont know lock code

Hi, I'm trying to get my phone back. I lost my phones password that is used to unlock the phone.
I dont know my google account im using on the phone either. Yes this is my phone.
I dont want to get locked out with google frp either
If i put twrp on and do a factory wipe, will i still need the pin?
Also, my phone doesn't need the pin to boot. thanks in advance

nebula37 said:
Hi, I'm trying to get my phone back. I lost my phones password that is used to unlock the phone.
I dont know my google account im using on the phone either. Yes this is my phone.
I dont want to get locked out with google frp either
If i put twrp on and do a factory wipe, will i still need the pin?
Also, my phone doesn't need the pin to boot. thanks in advance
Click to expand...
Click to collapse
No you won't need a pin in twrp if you have not encrypted the device..no you won't need pin to boot, but frp might get you..not sure how that works, I also feel like there are files you can delete through twrp to remove lock code, someone else will have to confirm this though, just something I heard

thanks but its not a concern now. I was on latest official ota update, flashed twrp but cant get lineage, or any custom rom to fully boot. It just gets to the logo screen and wont go any further. I have not used my moto a while.

nebula37 said:
Hi, I'm trying to get my phone back. I lost my phones password that is used to unlock the phone.
I dont know my google account im using on the phone either. Yes this is my phone.
I dont want to get locked out with google frp either
If i put twrp on and do a factory wipe, will i still need the pin?
Click to expand...
Click to collapse
FRP is disabled on unlocked bootloader.
PIN can be deleted with twrp's file manager.
LOS - you flashed wrong build. You need custom rom for N Modem. LOS by Hashbang works on N modem.

Help: My LG H990 DS only enters Fastboot and now the device changes to US996

Hi, I get a notification to update magisk. then I update it and use the recommended action to update it. After that it asks me to reboot the device. After rebooting the device it goes to fastboot only. And I see the device now changes to US996 while what I have is H990DS.
Can someone explain to me what's wrong and how to fix it without losing all my data?
thanks...

Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope

aliks00 said:
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
Click to expand...
Click to collapse
It's common knowledge that if you root your phone you never apply an OTA
Sent from my LG-H910 using XDA Labs

cnjax said:
It's common knowledge that if you root your phone you never apply an OTA
Click to expand...
Click to collapse
Thanks, but who said I ever applied an OTA? It was magisk that wanted to update itself, I've been performing magisk updates regularly for quite some time and never had a problem, in fact I can't even perform an OTA phone update as I have AT&T variant but with a different sim...
Other times, when updating magisk, I lost root but never lost the ability to boot...
I was running alpha-omega oreo with mk2000 kernel and updating rom, kernel and magisk regularly through TWRP (or direct install in case of magisk though magisk app) and never had this problem before... at least I can manage to boot from recovery/TWRP so hopefully I will soon manage to get things working again... that is, if I can copy some images to my SD card that windows insists that is corrupted but that's another story...

I ended up flashing whole rom again and everything is back to normal

bootloader says official?

does anyone know why the bootloader says the software is still official even though I am running havoc os a custom rom?

itcanbdone said:
does anyone know why the bootloader says the software is still official even though I am running havoc os a custom rom?
Click to expand...
Click to collapse
Maybe a glitch.

so, does yours say unofficial?
I ask cause when I unlocked my booloader and flashed twrp 3.1. something the stock rom wouldn't boot after I backed it up. its never seemingly behaved properly..
also, no matter what rom I put on the contacts up and delete themselves (i do not use cloud sync or gapps) and tge other issue accompanying is calls will drop on 1st second & 3rd rings when full signal present.
Did I miss a step?
I did developer options oem unlocking adb etc.
adb unlocked oem, then flashed twrp via adb/fastboot
then not working?