Sorry bad english. I have a Motorola X Style XT1572 Brazil, I rooted it once and now I am back to stock rom and it always go to bootloader screen and I dont know how to get off it.
Plus it had update to software but when it tried to update it goes to 12% and reboot to bootloader, back to 0% again and repeating about 5x and got a error that cannot update. I downloaded here the 6.0 marshmallow Latin America DS stock rom, also have the warning back everytime of unlocked bootloader.
Thx for attention and helping =)
Run "fastboot oem fb_mode_clear" using Command Prompt (Windows) or Terminal (Linux/OS X) then reboot the phone.
Spasticdroid said:
Run "fastboot oem fb_mode_clear" using Command Prompt (Windows) or Terminal (Linux/OS X) then reboot the phone.
Click to expand...
Click to collapse
I will try that. That will remove the bootloader screen right?
How do I remove the warning of unlocked bootloader too?
Thx for the attention, =)
2006goto said:
I will try that. That will remove the bootloader screen right?
How do I remove the warning of unlocked bootloader too?
Thx for the attention, =)
Click to expand...
Click to collapse
fastboot oem fb_mode_clear takes the bootloader out of fastboot flashing mode, turning it on is the first step in flashing a stock ROM, but sometimes it seems to just happen... This will cause the bootloader NOT to pop-up on reboot/startup.
The bootloader unlocked screen will ALWAYS be there, forever, including the delay and vibration... You can hide it with a custom logo screen or the stock, patched logo image (look around, it's posted here)
Note you will never be able to hide the fact the bootloader was unlocked, if anyone who knows anything just starts the bootloader it will show a Status of 2, meaning relocked. That is NOT possible to be changed or hidden, and it cannot go back to a 0 (locked). Fastboot getvar all will always show the truth too.
acejavelin said:
fastboot oem fb_mode_clear takes the bootloader out of fastboot flashing mode, turning it on is the first step in flashing a stock ROM, but sometimes it seems to just happen... This will cause the bootloader NOT to pop-up on reboot/startup.
The bootloader unlocked screen will ALWAYS be there, forever, including the delay and vibration... You can hide it with a custom logo screen or the stock, patched logo image (look around, it's posted here)
Note you will never be able to hide the fact the bootloader was unlocked, if anyone who knows anything just starts the bootloader it will show a Status of 2, meaning relocked. That is NOT possible to be changed or hidden, and it cannot go back to a 0 (locked). Fastboot getvar all will always show the truth too.
Click to expand...
Click to collapse
Hum... But I know there is some way to hide, just to no show that horrible white screen at starting...
2006goto said:
Hum... But I know there is some way to hide, just to no show that horrible white screen at starting...
Click to expand...
Click to collapse
Read my post again... Flash the patched logo.
The unlock screen and status are still there, just hidden.
Related
Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this
Wife's phone got stuck in a bootloop last night, just stayed on the moto logo. Tried wiping cache and then data from recovery. phone now boots to moto then a black screen. I can see the device in fastboot, but not in recovery. I want to unlock the phone so that I can reflash the OS either from a custom recovery or from fastboot, but since I cant fully boot, I cant get to the developer options. This phone has never been unlocked/rooted or anything.
Is there a way to unlock the bootloader without going into the developer options and enabling it?
rokenford said:
Wife's phone got stuck in a bootloop last night, just stayed on the moto logo. Tried wiping cache and then data from recovery. phone now boots to moto then a black screen. I can see the device in fastboot, but not in recovery. I want to unlock the phone so that I can reflash the OS either from a custom recovery or from fastboot, but since I cant fully boot, I cant get to the developer options. This phone has never been unlocked/rooted or anything.
Is there a way to unlock the bootloader without going into the developer options and enabling it?
Click to expand...
Click to collapse
No there is no way to unlock bootloader without allowing OEM unlock, you're gonna wanna flash the latest version of stock available for your phone. Unfortunately I'm not very familiar with the commands so maybe another user can chime in here!
rokenford said:
Is there a way to unlock the bootloader without going into the developer options and enabling it?
Click to expand...
Click to collapse
You cannot unlock BL without "allow oem unlock" enabled.
Usb debugging you can't enable with fastboot.
You can try to erase with commands:
fastboot erase userdata
fastboot erase cache
fastboot erase customize
fastboot reboot
Give it some time.
How long are you waiting for it to boot after a factory reset? This can take 30 minutes... sometimes more.
acejavelin said:
How long are you waiting for it to boot after a factory reset? This can take 30 minutes... sometimes more.
Click to expand...
Click to collapse
I've waited at least 20 mins (not really timing it.) but with the black screen (screen on, not displaying anything) after the boot screen, how can I be sure its actually doing anything?
Honestly... Locked and stock there isn't much you can do. If we had the latest firmware image, maybe, but we are a release behind with no way knowing when, or if, we will ever get the current one.
There are two likely cases here for the cause of this problem... Actually, the cause is corruption of data on the internal emmc chip, the reason behind that corruption is the issue. It is either a faulty emmc chip or a fluke from cosmic radiation, static electricity, or who knows what. Either way, there since a factory reset isn't fixing it and we don't have a current firmware image your only option is send it in to Moto or replace it.
Hopefully someone can help me out here. I have been trying to root my phone, and everything goes fine but for some odd reason as soon as I relock the bootloader the phone wont boot anymore, I just get stuck at the boot screen indefinitely and have to revert to stock. I went through this process several times with the same issue, and unfortunately I got frustrated and started messing around. Not thinking I went into developer options and uncheck "allow OEM unlock," and forgot about it and rebooted. Now I can't get the phone to boot, but I can't flash unlock either. It will not boot into TWRP for some unknown reason as well, so at this point I don't see how I am going to fix this.
Even better, I just got the phone today...
Help!
sublimejhn said:
Hopefully someone can help me out here. I have been trying to root my phone, and everything goes fine but for some odd reason as soon as I relock the bootloader the phone wont boot anymore, I just get stuck at the boot screen indefinitely and have to revert to stock. I went through this process several times with the same issue, and unfortunately I got frustrated and started messing around. Not thinking I went into developer options and uncheck "allow OEM unlock," and forgot about it and rebooted. Now I can't get the phone to boot, but I can't flash unlock either. It will not boot into TWRP for some unknown reason as well, so at this point I don't see how I am going to fix this.
Even better, I just got the phone today...
Help!
Click to expand...
Click to collapse
Do not try to lock the BL if you are not completely stock.
If you have TWRP or anything like Magisk installed do not lock the BL.
If something goes wrong, you have a brick.
only lock the BL if you are completely stock.
sublimejhn said:
Hopefully someone can help me out here. I have been trying to root my phone, and everything goes fine but for some odd reason as soon as I relock the bootloader the phone wont boot anymore, I just get stuck at the boot screen indefinitely and have to revert to stock. I went through this process several times with the same issue, and unfortunately I got frustrated and started messing around. Not thinking I went into developer options and uncheck "allow OEM unlock," and forgot about it and rebooted. Now I can't get the phone to boot, but I can't flash unlock either. It will not boot into TWRP for some unknown reason as well, so at this point I don't see how I am going to fix this.
Even better, I just got the phone today...
Help!
Click to expand...
Click to collapse
Why would you relock bootloader? Not a good idea especially after modifying software
Sent from my PH-1 using Tapatalk
tech_head said:
Do not try to lock the BL if you are not completely stock.
If you have TWRP or anything like Magisk installed do not lock the BL.
If something goes wrong, you have a brick.
only lock the BL if you are completely stock.
Click to expand...
Click to collapse
Man, I could have sworn it was not recommended to leave the bootloader unlocked. Not exactly the answer I wanted to hear unfortunately. Any idea why it won't boot just because I relocked the bootloader? It just seems like an odd thing to cause a boot loop, and it did it 3 separate times
Can you go to bootloader?
Sent from my PH-1 using Tapatalk
TJSteveMX said:
Can you go to bootloader?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I can get into fastboot
sublimejhn said:
I can get into fastboot
Click to expand...
Click to collapse
If your PC can recognize adb fastboot then just get the stock zip file from "back to stock" section here
https://forum.xda-developers.com/showthread.php?t=3701681
I messed up too and back to stock was my only way.
Make sure under bootloader, if you type fastboot devices and is waiting for device, use
fastboot devices -i 0x2e17
If the PC recognize your device then, you can save from your bootloop
Sent from my PH-1 using Tapatalk
TJSteveMX said:
If your PC can recognize adb fastboot then just get the stock zip file from "back to stock" section here
https://forum.xda-developers.com/showthread.php?t=3701681
I messed up too and back to stock was my only way.
Make sure under bootloader, if you type fastboot devices and is waiting for device, use
fastboot devices -i 0x2e17
If the PC recognize your device then, you can save from your bootloop
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I would do this, but I had unchecked "allow OEM unlock" when I booted up earlier. I cannot unlock the bootloader now from fastboot, and I can't flash back to stock because my bootloader is locked. I am pretty sure I am screwed at this point
sublimejhn said:
I would do this, but I had unchecked "allow OEM unlock" when I booted up earlier. I cannot unlock the bootloader now from fastboot, and I can't flash back to stock because my bootloader is locked. I am pretty sure I am screwed at this point
Click to expand...
Click to collapse
Try holding volume up and down right after essential logo and see if you can get into safe mode. Worth a shot.
Skickat från min PH-1 via Tapatalk
do you see your device in fastboot at all? try switching the slot.. fastboot --set-active=x where x is either _a or _b.
superior8888 said:
Try holding volume up and down right after essential logo and see if you can get into safe mode. Worth a shot.
Skickat från min PH-1 via Tapatalk
Click to expand...
Click to collapse
Not sure if I'm doing something wrong, but holding both volume buttons does nothing for me.
And I can get into fastboot and it registers the phone, but when I try to change slots it tells me it failed and I cannot change slots while locked
sublimejhn said:
Not sure if I'm doing something wrong, but holding both volume buttons does nothing for me.
And I can get into fastboot and it registers the phone, but when I try to change slots it tells me it failed and I cannot change slots while locked
Click to expand...
Click to collapse
It just stays on lineage boot screen?
Skickat från min PH-1 via Tapatalk
try reinstalling TWRP and flash LOS again, I think once you flash a different software the OEM UNLOCKING switch are not highlighted anymore(what I mean is you can't turn it off), if you can do fastboot, try doing fastboot -w and wait till it reboots.
imna357 said:
try reinstalling TWRP and flash LOS again, I think once you flash a different software the OEM UNLOCKING switch are not highlighted anymore(what I mean is you can't turn it off), if you can do fastboot, try doing fastboot -w and wait till it reboots.
Click to expand...
Click to collapse
It's OEM locked. Not true, you can lock it, and so he did.
Skickat från min PH-1 via Tapatalk
See this thread on Reddit:
https://www.reddit.com/r/essential/comments/7hocrl/psa_if_youre_running_a_custom_rom_recovery_on/
sublimejhn said:
Man, I could have sworn it was not recommended to leave the bootloader unlocked. Not exactly the answer I wanted to hear unfortunately. Any idea why it won't boot just because I relocked the bootloader? It just seems like an odd thing to cause a boot loop, and it did it 3 separate times
Click to expand...
Click to collapse
Check any forum of a phone with an unlockable bootloader. You never ever relock the bootloader unless you are 100% completely stock. Once relocked with modified software there is nothing you can do to get it to boot.
Your only hope might be a deep flash cable and qpst if you can figure out how to use it.
superior8888 said:
It just stays on lineage boot screen?
Skickat från min PH-1 via Tapatalk
Click to expand...
Click to collapse
Yeah it just continues to boot as normal, and then of course goes into the boot loop.
I cannot reflash twrp or any other room. Attempting to flash anything fails with the error cannot flash while locked. Same with using -w
Did you try the fastboot unlock command?
varxx said:
See this thread on Reddit:
https://www.reddit.com/r/essential/comments/7hocrl/psa_if_youre_running_a_custom_rom_recovery_on/
Click to expand...
Click to collapse
Just saw your post. Wonderful. Might be a good sticky on xda, I didn't see this on Reddit. Anyone want to buy a really expensive shiny brick?!
Hi.
A few months ago I had a white screen with the usual bootloader unlocked warning.
Last week I screwed up things (no sim detection, no wifi, etc). Had to install Android 7 official and then go back to Oreo 8.1.
But after that, I get the same warning with black background.
How can I get back the white background again?
Thanks!
movelbit said:
Hi.
A few months ago I had a white screen with the usual bootloader unlocked warning.
Last week I screwed up things (no sim detection, no wifi, etc). Had to install Android 7 official and then go back to Oreo 8.1.
But after that, I get the same warning with black background.
How can I get back the white background again?
Thanks!
Click to expand...
Click to collapse
The Black background was for Android 7 Bootloader (TISSOT1.0), for 8.0/8.1 turned White (TISSOT2.0), no differences..
You can download the 8.1 fastboot image and flash the splash image manually:
Code:
fastboot flash splash splash.img
dgadelha said:
You can download the 8.1 fastboot image and flash the splash image manually:
Code:
fastboot flash splash splash.img
Click to expand...
Click to collapse
Thank you.
That was it.
Is it possible to remove the warning with unlocked bootloader?
Thanks!
movelbit said:
Thank you.
That was it.
Is it possible to remove the warning with unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
Hey,
In this case you can use the attached file to remove the unlocked bootloader warning.
Thanks!
dgadelha said:
Hey,
In this case you can use the attached file to remove the unlocked bootloader warning.
Thanks!
Click to expand...
Click to collapse
Again, thank you.
Worked perfect!
Hi all ....sure someone has asked this before but........
When I power on my phone it jumps directly into Start screen with a message "visit this link on another device g.co/ABH. Then it shuts down. If I press the volume key within 5 secs it will go to the next screen which has recovery, fastboot power off etc.....any option I select at that point it restarts and goes back to the first screen. I have tried ADB devices and it cannot find the phone. When I check device manager and select "show hidden devices" it shows android phone/android composite ADB Interface and under portable devices it show ZTE A2017U.
It makes no difference if the phone is plugged in or not as it does not recognize it.
Thoughts much appreciated. Chuck
@here2for: You're getting the "visit this link on another device" because your bootloader is unlocked. This is just a guess, but you're probably running the stock ROM, and the system partition has probably been modified by whatever means, so the phone shuts down after this screen as a result of failing the bootloader's dm-verity check. dm-verity can be disabled but it must be done manually. Am I correct in assuming that you are running a stock ROM?
ADB commands wont work on the bootloader screen, except when booted into FTM mode or recovery.
AnonVendetta said:
@here2for: You're getting the "visit this link on another device" because your bootloader is unlocked. This is just a guess, but you're probably running the stock ROM, and the system partition has probably been modified by whatever means, so the phone shuts down after this screen as a result of failing the bootloader's dm-verity check. dm-verity can be disabled but it must be done manually. Am I correct in assuming that you are running a stock ROM?
ADB commands wont work on the bootloader screen, except when booted into FTM mode or recovery.
Click to expand...
Click to collapse
Yes stock...
Nothing going on here,continue walking
here2for said:
Yes stock...
Click to expand...
Click to collapse
If you've lost recovery and lost boot, you're going to need to use EDL.