Unlocked my phone and everything was fine. Then tried installing the 5.1 update and something got messed up there...
My phone is stuck on the "Google logo unlocked icon screen" and will not boot.
I've tried the factory reset, installing a stock image via Flash-All, clearing cache, etc. Nothing fixes it.
Any ideas here?
leesfer said:
Unlocked my phone and everything was fine. Then tried installing the 5.1 update and something got messed up there...
My phone is stuck on the "Google logo unlocked icon screen" and will not boot.
I've tried the factory reset, installing a stock image via Flash-All, clearing cache, etc. Nothing fixes it.
Any ideas here?
Click to expand...
Click to collapse
Try flashing stock image the old fashioned way, and do check that your bootloader and radio version match with the android version you're using
Yasharkhan said:
Try flashing stock image the old fashioned way, and do check that your bootloader and radio version match with the android version you're using
Click to expand...
Click to collapse
If I do a flash-all using the stock LRX22C then it should include the correct bootloader and radio, right?
leesfer said:
If I do a flash-all using the stock LRX22C then it should include the correct bootloader and radio, right?
Click to expand...
Click to collapse
No, do not downgrade your bootloader.
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
And do not relock your bootloader.
---------- Post added at 07:47 PM ---------- Previous post was at 07:45 PM ----------
From fastboot:
fastboot format cache
fastboot format userdata
Okay, I've reinstalled stock 5.1 step-by-step via fastboot rather than flash-all and everything seems to be working okay now.
I see now that flash-all was giving some missing file errors that I missed
Related
So I just got a AT&T black HTC One, unlocked bootloader, installed TWRP (first time, always used CWM in the past) rooted, s-off. Nandroid backup. I am no stranger to flashing ROMs with past devices but I CANNOT get a custom rom to install on this thing! I have tried a couple different 4.4 ROMs and each one always gives me some sort of error or failure when installing. Each time I do the standard TWRP wipe, then immediately try and flash, and they never successfully install. When I reboot it shows the HTC screen then crashes, and automatically reboots into recovery. Any ideas on what am I doing wrong? Is it something with TWRP I'm unaware of? Do the rom files have to be placed somewhere specific in TWRP?
This is what I see everytime after trying to flash a ROM:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcar(the screen cuts off whatever comes after this)
Updating partition details...
Failed
Thanks in advance!
What version of twrp? Firmware version?
SaHiLzZ said:
What version of twrp? Firmware version?
Click to expand...
Click to collapse
TWRP = 2.6.3.0
I think firmware means build number, which is = 1.26.502.10 CL166754 release-keys
Is that what you mean? I don't remember ever changing anything relating to "firmware", not on this new phone today nor on any old devices. Just like that I feel super noobish again.
You probably need 2.6.3.4 or whatever is latest.
Also post an output of fastboot getvar all (remove sn/imei)
sent from my mobile device
---------- Post added at 12:15 AM ---------- Previous post was at 12:15 AM ----------
Absolutely S-off before you go any further
sent from my mobile device
SaHiLzZ said:
You probably need 2.6.3.4 or whatever is latest.
Also post an output of fastboot getvar all (remove sn/imei)
sent from my mobile device
---------- Post added at 12:15 AM ---------- Previous post was at 12:15 AM ----------
Absolutely S-off before you go any further
sent from my mobile device
Click to expand...
Click to collapse
Welp, updating to the latest 2.6.3.3 seemed to fix it. Just flashed a ROM without errors. I'm just booting into the new ROM now and while it's going through the "Android is upgrading..." screen all indications are that it was a successful flash. Thank you and thanked!
Help plsssssssss
lin453889100 said:
Help plsssssssss
Click to expand...
Click to collapse
I have a motor x developer ed, but after flashed a rom, i tried to reboot the system, it gets stuck at white warning page
lin453889100 said:
I have a motor x developer ed, but after flashed a rom, i tried to reboot the system, it gets stuck at white warning page
Click to expand...
Click to collapse
Reboot into recovery by turning phone off and holding down the power button and volume down for about 5 sec. Choose recovery and install backup. If you didn't make a backup (shame on you). You will have to fxz the firmware and you will have a fresh new phone but will lose ALL data including pics and music etc.
bigv5150 said:
Reboot into recovery by turning phone off and holding down the power button and volume down for about 5 sec. Choose recovery and install backup. If you didn't make a backup (shame on you). You will have to fxz the firmware and you will have a fresh new phone but will lose ALL data including pics and music etc.
Click to expand...
Click to collapse
thx for your help, can you tell me more details about fxz the firmware?
Help plsssssssssssss
HELP!!!!
http://forum.xda-developers.com/showpost.php?p=46327689&postcount=1
Or
http://forum.xda-developers.com/moto-x/development/kit-restore-moto-x-to-stock-rsd-lite-t2560571
Or
Get RSD from http://ted.servepics.com/razrm/ & the XML from http://sbf.droid-developers.org/
---------- Post added at 01:32 AM ---------- Previous post was at 01:21 AM ----------
More on RSD lite
http://forum.xda-developers.com/showthread.php?t=2176753
Did you try wiping cache and factory reset in recovery
Sent from my XT1053 using XDA Free mobile app
Follow the links suggested above. Return to stock. The same version you are on now. Don't flash a different version.
Then I suggest respectfully that you read the stickies at the top of general section and learn a bit more before attempting more flashing.
The more you learn and understand.... The easier things will be and the less trouble you will have. Also might save you from bricking your phone doing something you shouldn't.
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
Also you can use fastboot to return to stock. Read this guide, and there's a return to stock section for you.
http://forum.xda-developers.com/showthread.php?t=2603358
kj2112 said:
Follow the links suggested above. Return to stock. The same version you are on now. Don't flash a different version.
Then I suggest respectfully that you read the stickies at the top of general section and learn a bit more before attempting more flashing.
The more you learn and understand.... The easier things will be and the less trouble you will have. Also might save you from bricking your phone doing something you shouldn't.
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
Also you can use fastboot to return to stock. Read this guide, and there's a return to stock section for you.
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
+1 I always say it's great having an unlocked phone but learn how to fix it before you screw it up. Read everything you can trust me it will make it so much easier in the long run.
Hey,
I have a Moto X Play running stock 6.0.1, no root, no twrp and with the bootloader locked. So I have unlocked it, installed twrp and super su. So when I've finished installing super su, i've rebooted the phone and it's stuck at WARNING BOOTLOADER LOCKED. OK, I guess this may be a soft brick. I can get into twrp.
Shall I for example download cyanogenmod through the pc and flash it with twrp?
Thank you
_mikelanda said:
Hey,
I have a Moto X Play running stock 6.0.1, no root, no twrp and with the bootloader locked. So I have unlocked it, installed twrp and super su. So when I've finished installing super su, i've rebooted the phone and it's stuck at WARNING BOOTLOADER LOCKED. OK, I guess this may be a soft brick. I can get into twrp.
Shall I for example download cyanogenmod through the pc and flash it with twrp?
Thank you
Click to expand...
Click to collapse
flash UPDATE-SuperSU-v2.65-20151226141550.
had the same problem and the supersu 2.65 solved it.
kamalshetty90 said:
flash UPDATE-SuperSU-v2.65-20151226141550.
had the same problem and the supersu 2.65 solved it.
Click to expand...
Click to collapse
Thanks Sir
kamalshetty90 said:
flash UPDATE-SuperSU-v2.65-20151226141550.
had the same problem and the supersu 2.65 solved it.
Click to expand...
Click to collapse
Any other ideas? I tried it but my phone still at bootloader logo.
edwart said:
Any other ideas? I tried it but my phone still at bootloader logo.
Click to expand...
Click to collapse
Last i tried the latest super user worked for me.
But now i am using moto g5s plus. Sorry if this didn't help.
So a friend of mine has an LG D415, which apparently is the same as the Optimus L90. He asked me to install a ROM for him (CM 11) which requires an unlocked bootloader. He already had root (through "KingRoot") and I managed to successfully install TWRP custom recovery.
I then followed this post's instructions on how to unlock the bootloader, that's where everything went wrong.
The phone can still boot into android and recovery without any problems, but I keep getting this error when issuing commands through fastboot "failed (remote: unknown command)"
I have a backup copy of laf.img, but I'm not sure how exactly to flash it with fastboot down for the count.
I have that phone and found the bootloader was already unlocked, thus causing that failure message. Try just installing the ROM.
---------- Post added at 02:08 PM ---------- Previous post was at 02:06 PM ----------
Also, if you find that it doesn't recognize the sim card, make sure you flash the KitKat bootstack.
sandworm said:
I have that phone and found the bootloader was already unlocked, thus causing that failure message. Try just installing the ROM.
---------- Post added at 02:08 PM ---------- Previous post was at 02:06 PM ----------
Also, if you find that it doesn't recognize the sim card, make sure you flash the KitKat bootstack.
Click to expand...
Click to collapse
if is allready unlocked why rommanager cant install twrp?
Don't use rom manager. Flash TWRP manually using fastboot or use flashify.
Help
"Forgive me maybe I ask for help in the wrong place"
Hello!
I have a D415 T-MOBILE
According to this procedure I act
.According to the restart guide
And again the wire stays in "LG"
Thanks.........
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.
you mean magisk not working with this build?
mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs
avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!
Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV
avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.
jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems
gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?
jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again
I need stock firmware for my Moto G6 XT1925-5 OPSS27.82-87-6
And compatible working and tested TWRP.
I want to reflash this Phone, and get rid bootloader unlock warning.
Any help with that?
Morricorne said:
I need stock firmware for my Moto G6 XT1925-5 OPSS27.82-87-6
And compatible working and tested TWRP.
I want to reflash this Phone, and get rid bootloader unlock warning.
Any help with that?
Click to expand...
Click to collapse
This is the signed firmware you are looking for:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Official TWRP is available on https://eu.dl.twrp.me/ali/.
You should start with version 3.2.3-0 for your old Oreo build.
---------- Post added at 10:29 PM ---------- Previous post was at 10:22 PM ----------
Morricorne said:
I want to reflash this Phone, and get rid bootloader unlock warning.
Any help with that?
Click to expand...
Click to collapse
Try this tool for Windows
https://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667/
In case of any problems with the tool I could repack a logo.bin with the images that you prefer.
WoKoschekk said:
This is the signed firmware you are looking for:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Official TWRP is available on https://eu.dl.twrp.me/ali/.
You should start with version 3.2.3-0 for your old Oreo build.
Click to expand...
Click to collapse
Thanks for answear. I test this fw in next week.
Now im on official newest 9.0 for moto g6.
I find place with stock moto g6 firmware. Tried flash oldest 8.0 rom. But fastboot give me cannot downgrade message. Thats why i decided flash newest avaible fw.
I flashed official TWRP recovery for g6 too.
And try flash zip file. But i cant decrypt storage. And i have error with format data. I Just give up with remove Bootloader warning. And use stock 9.0
I dont have enough data package to download this fw. But i try this fw in future. Thanks for helpi just wanted only remove this Bootloader warning. Cause im buy this moto with already unlocked Bootloader. I have moto g5 too. With unlocked Bootloader. I replaced this warning with black moto logo. And its work. But i cant do the same thing with moto g6
Morricorne said:
Thanks for answear. I test this fw in next week.
Now im on official newest 9.0 for moto g6.
I find place with stock moto g6 firmware. Tried flash oldest 8.0 rom. But fastboot give me cannot downgrade message. Thats why i decided flash newest avaible fw.
I flashed official TWRP recovery for g6 too.
And try flash zip file. But i cant decrypt storage. And i have error with format data. I Just give up with remove Bootloader warning. And use stock 9.0
I dont have enough data package to download this fw. But i try this fw in future. Thanks for help
Click to expand...
Click to collapse
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
WoKoschekk said:
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
Click to expand...
Click to collapse
OK thanks i try this in next week
WoKoschekk said:
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
Click to expand...
Click to collapse
Where i can find this disable forceencrypt zip?
Morricorne said:
Where i can find this disable forceencrypt zip?
Click to expand...
Click to collapse
https://github.com/Zackptg5/Disable...Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
WoKoschekk said:
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
Click to expand...
Click to collapse
Cant format data TWRP 3.3.1-0
Flashed decryption zip, magisk system start.
Can enter TWRP again.
Imei work but no Service.
Wtf?
Morricorne said:
Flashed decryption zip, magisk system start.
Can enter TWRP again.
Imei work but no Service.
Wtf?
Click to expand...
Click to collapse
It's not a decryption.zip, it's a forceencryption-disabler.
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
I guess you don't reboot to system after flashing the stock ROM, do you?
One of the last fastboot commands was "fastboot erase userdata". The missing reboot command is the reason for your problem!
WoKoschekk said:
It's not a decryption.zip, it's a forceencryption-disabler.
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
I guess you don't reboot to system after flashing the stock ROM, do you?
One of the last fastboot commands was "fastboot erase userdata". The missing reboot command is the reason for your problem!
Click to expand...
Click to collapse
Nope its a not compatible with android 9 version. I found this on xda
https://forum.xda-developers.com/moto-g6/help/service-root-t4004467
**** that. I reflash everything to Stock cause i dont need magisk and root. I only need get rid Bootloader Unlock warning. What i almost finished. Now i look for modified logo.bin
Morricorne said:
Nope its a not compatible with android 9 version. I found this on xda
https://forum.xda-developers.com/moto-g6/help/service-root-t4004467
**** that. I reflash everything to Stock cause i dont need magisk and root. I only need get rid Bootloader Unlock warning. What i almost finished. Now i look for modified logo.bin
Click to expand...
Click to collapse
Post a picture and I will convert it for you to a logo.bin
WoKoschekk said:
Post a picture and I will convert it for you to a logo.bin
Click to expand...
Click to collapse
I may send you original logo bin
I have this now
A resolution of 1080x2160 would be perfect.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Morricorne said:
I may send you original logo bin
I have this now
Click to expand...
Click to collapse
Send it
WoKoschekk said:
A resolution of 1080x2160 would be perfect.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Send it
Click to expand...
Click to collapse
Finished everything flashed. Bootlogo too. And i get ride unknown password when Phone boot too. I dont use any password. Then i dont know whats wrong. Phone ask me everytime when i reboot my device. Now this is gone. No more modding moto g6. Better is stay on stable working stock. Then cant use phone. Man what a day. Time to relax i almost throw this damn phone on the floor.