Hello, I have an xt1771 that does not come out of the motorola logo even if it passes several roms with sp flash tool(i tried "download only", "firmware upgrade" and "format all + download") it only turns on, vibrates, gets some seconds on the motorola logo and stays in that loop, I can not access the recovery and the bootloader is blocked, not allowing me to use any command. Any idea what to do?
Sorry for my bad English .
Unlock the bootloader and install twrp and then flash no-verity-opt-encrypt zip file to disable dm-verity.
AnonyWorld said:
Hello, I have an xt1771 that does not come out of the motorola logo even if it passes several roms with sp flash tool(i tried "download only", "firmware upgrade" and "format all + download") it only turns on, vibrates, gets some seconds on the motorola logo and stays in that loop, I can not access the recovery and the bootloader is blocked, not allowing me to use any command. Any idea what to do?
Sorry for my bad English .
Click to expand...
Click to collapse
Just curious how long are you waiting on the Moto Logo screen? I've seen it take upwards of 20 minutes on some ROMs.
TheHitMan said:
Unlock the bootloader and install twrp and then flash no-verity-opt-encrypt zip file to disable dm-verity.
Click to expand...
Click to collapse
I can't unlock bootloader, i open the prompet and write "fastboot oem unlock", in the device i see an message (img1) if i press vol + i see in the prompt "operation not allowed" and if i press vol - the phone back to bootloader screen and in prompt i look the message "OK" but the bootloader was not unlocked. I believe that be because i not flag the "oem unlock" in developer options.
bobbyphoenix said:
Just curious how long are you waiting on the Moto Logo screen? I've seen it take upwards of 20 minutes on some ROMs.
Click to expand...
Click to collapse
I think 5 or 10 minutes, but the phone not make the "hello moto" just stay in loop on the "motorola powered by android" per more or less 50 seconds, i can't acess recovery and can't unlock bootloader, believe that be because i not flag the "oem unlock" in te developer options.
AnonyWorld said:
I can't unlock bootloader, i open the prompet and write "fastboot oem unlock", in the device i see an message (img1) if i press vol + i see in the prompt "operation not allowed" and if i press vol - the phone back to bootloader screen and in prompt i look the message "OK" but the bootloader was not unlocked. I believe that be because i not flag the "oem unlock" in developer options.
Click to expand...
Click to collapse
Yes.
You are right. OEM unlock should be enabled in developer options.
TheHitMan said:
Yes.
You are right. OEM unlock should be enabled in developer options.
Click to expand...
Click to collapse
Unless it's different on the Mediatek variant, he needs an unlock code from Motorola, yes? https://forum.xda-developers.com/moto-e4-plus/how-to/bootloader-unlock-custom-recovery-t3738683
Sizzlechest said:
Unless it's different on the Mediatek variant, he needs an unlock code from Motorola, yes? https://forum.xda-developers.com/moto-e4-plus/how-to/bootloader-unlock-custom-recovery-t3738683
Click to expand...
Click to collapse
Probably NO. Only Qualcomm variant of E4 and E4 Plus requires an unlock key from motorola. Mediatek variant doesn't need it at all.
"Allow oem unlock" should be enable in developer option else if it isn't enable by default, one should enable this in custom recovery through some setprop conditions.
Sizzlechest said:
Unless it's different on the Mediatek variant, he needs an unlock code from Motorola, yes? https://forum.xda-developers.com/moto-e4-plus/how-to/bootloader-unlock-custom-recovery-t3738683
Click to expand...
Click to collapse
Qualcomm variant is different from the mediatek variant.
TheHitMan said:
Probably NO. Only Qualcomm variant of E4 and E4 Plus requires an unlock key from motorola. Mediatek variant doesn't need it at all.
"Allow oem unlock" should be enable in developer option else if it isn't enable by default, one should enable this in custom recovery through some setprop conditions.
Click to expand...
Click to collapse
I can't write unsigned softwares with flash tool. Any idea?
AnonyWorld said:
I can't write unsigned softwares with flash tool. Any idea?
Click to expand...
Click to collapse
Did you have any working recovery in your device ?
TheHitMan said:
Did you have any working recovery in your device ?
Click to expand...
Click to collapse
I do not know, because this phone is not my. The owner said that out of nowhere the phone was in this state. I do not believe the owner knows what a custom recovery is.
Related
Hello,
Is it possible to unlock the Nexus One without having a working power button?
The step before entering "fastboot oem unlock" in your adb shell, you have to select "fastboot" in the default stock bootloader on your N1. But you've to select "fastboot" with the power button.
Without unlocking the device, I'm not able to flash custom bootloaders (like Black Rose), am I?
Any ideas how to manage this problem?
Thanks in advance!
Domskibus said:
Hello,
Is it possible to unlock the Nexus One without having a working power button?
The step before entering "fastboot oem unlock" in your adb shell, you have to select "fastboot" in the default stock bootloader on your N1. But you've to select "fastboot" with the power button.
Without unlocking the device, I'm not able to flash custom bootloaders (like Black Rose), am I?
Any ideas how to manage this problem?
Thanks in advance!
Click to expand...
Click to collapse
I think you can but you have to root your phone first with the bootloader locked and install custom ROM with the option to boot the phone to bootloader and then do the oem unlock via fastboot without shutting the phone off. And I am sure you know how to do the battery trick to recharge your phone, right?
It won't help you. Command "adb reboot bootloader" will take you straight to fastboot from absolutely any ROM, including stock, but you'll have to press Power button to confirm your choice to unlock bootloader - and voila, you have no power button.
I´m in same problem.
I also had this problem once, this is what I found:
Common Instructions
If you need to restart the phone, its impossible to do so, since the power button is broken.In such a scenario, follow this
a)Connect the phone to a charger/USB.
b)Remove the battery from the phone once you see the charging light on the phone
c)Insert the battery and keep it there until you see the charging light again.
Continue doing steps b) and c) until the phone boots (Phone normally boots in 4 attempts).
[Update]
It is required that the phone be fully charged in order to complete the steps correctly.A phone shutting off in between an upgrade/flashing due to low battery is sure to brick.
Click to expand...
Click to collapse
Please, before posting more or less useless posts, consider re-reading the title of the thread, and then re-reading this:
Jack_R1 said:
It won't help you. Command "adb reboot bootloader" will take you straight to fastboot from absolutely any ROM, including stock, but you'll have to press Power button to confirm your choice to unlock bootloader - and voila, you have no power button.
Click to expand...
Click to collapse
Hi Domskibus,
you don't need to unlock your device to flash BlackRose! I didn't unlock mine, too!
yxcv99 said:
Hi Domskibus,
you don't need to unlock your device to flash BlackRose! I didn't unlock mine, too!
Click to expand...
Click to collapse
This is correct. For flashing BlackRose only root is required, AFAIK. Possibly not even that. The exact requirements are stated in BlackRose thread.
forget to "unlock oem" in developer option. now moto x2 is stuck in boot, any help??
I didn't switch the "unlock oem" in developer option. mine is moto 2nd Gen 2014, now it is stuck in boot. Tried flashing recovery but keeps telling me unlock oem in developer option as phone is not booting i cant do that
devan448 said:
I didn't switch the "unlock oem" in developer option. mine is moto 2nd Gen 2014, now it is stuck in boot. Tried flashing recovery but keeps telling me unlock oem in developer option as phone is not booting i cant do that
Click to expand...
Click to collapse
Why don't you try to wipe your Dalvik Cache and Cache in the Recovery .........
devan448 said:
I didn't switch the "unlock oem" in developer option. mine is moto 2nd Gen 2014, now it is stuck in boot. Tried flashing recovery but keeps telling me unlock oem in developer option as phone is not booting i cant do that
Click to expand...
Click to collapse
You need to factory reset your device...hard reset you device using any recover...if you dont have any custom recovery use stock recovery!!
Thank you....
devan448 said:
I didn't switch the "unlock oem" in developer option. mine is moto 2nd Gen 2014, now it is stuck in boot. Tried flashing recovery but keeps telling me unlock oem in developer option as phone is not booting i cant do that
Click to expand...
Click to collapse
You can temporarily run by Fastboot Method and get into recovery to fix your issues.
Get ADB and Fastboot Files from the web and Download TWRP Recovery for your device .
Now enter into bootloader mode ( Power + Volume Down )
type fastboot devices to check whether your device recognizes it . If so
type fastboot boot {drag your recovery into the CMD window } and click enter
Your phone will boot the image and run the TWRP Recovery . Now fix your problem with ease...
http://forum.xda-developers.com/showthread.php?t=2588979&page=1
Try using this thread for fastboot and abd install...simple nd small!!:good:
Hope that helps you !! Hit the Thanks if its so
Hey guys, i have MI A2 cellphone, and after auto update programmed to three hours the smartphone show "AndroidONE" logo and then shutdown, i tried "Fastboot oem unlock", but it is my output:
PHP:
C:\Users\Lucas Daniel>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.000s
. I'm desperate, I do not know what to try anymore, I believe I do not have unlock OEM activated, someone can help me?
Sorry for bad english, i'm from brazilian.
@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.
sas.mar said:
@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.
Click to expand...
Click to collapse
Thanks, looks that, unfortunately, my unique solution is test-point for activate EBL Mode... I will leave the topic open for the case of i get other solutions... after 3 days, if not get, i will close and the unique solution will really test-point.
Try rebooting it a couple of times and see if it boots. Or plug it to a charger and try booting it once it starts to charge successfully. If all fails, flashing via EDL might be your only option.
Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).
Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?
Tianhe said:
Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?
Click to expand...
Click to collapse
What is it command?
Aerobatic said:
Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).
Click to expand...
Click to collapse
How can I do it? I leave the phone in the charger for a long time? Or do you need the power button for a long time?
I tried to press the power button for 2 minutes and nothing happened.
When i leave the smartphone on the charge, after 50 minutes, show for me 100% percent, so, i pressed power button and the screen stayed lock in "AndroidONE", nothing happened, until try again press power button.
The problem original comebacked to me
LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
I tried, the same ploblem happenned... don't work, unfortunely... :/
LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)
Phil_Smith said:
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)
Click to expand...
Click to collapse
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.
LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
Do as tabun1994 said.
This will hopefully get the system up again.
The commands I wrote would unlock the bootloader. What else could I have meant?
If you succeeded with tabun's method, then you probably would only need to enable "USB debugging" and "OEM unlocking" in the ROM's developer options (which you'll enable by hitting "build number" in settings like 10 times or so).
Then you would connect the device and accept the 'trust this device' warning.
After booting to fastboot now, the commands I wrote should work and unlock the bootloader (if you even want that when your system is running again).
tabun1994 said:
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.
Click to expand...
Click to collapse
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl
The test point method is actually easy , you have to dissasemble the display , easy procedure , remove the battery and short the two test points with tweezerz or something ,and in the meantime you plug the usb cable into the computer. It should install the Qusb_Hub drivers , and with miFlash you should be able to reflash the firmware . I bought a phone that was in this state and fixed it using these steps.
No more solutions, I will do the test point method, thanks to everyone who tried to help otherwise.
LukeSkyPTBR said:
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl
Click to expand...
Click to collapse
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!
LukeSkyPTBR said:
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!
Click to expand...
Click to collapse
I execute bat archive but nothing happens in Mi A2 .-
tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
What is your smartphone?
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
sprays said:
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
Click to expand...
Click to collapse
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
sprays said:
You should be able to reflash the firmware
Use
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
Click to expand...
Click to collapse
have you tried unlocking your bootloader again?
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
kewlzter said:
have you tried unlocking your bootloader again?
Click to expand...
Click to collapse
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
sprays said:
You should be able to reflash the firmware
Use
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
Click to expand...
Click to collapse
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
kewlzter said:
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
Click to expand...
Click to collapse
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
sprays said:
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
Click to expand...
Click to collapse
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
?
kewlzter said:
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
Click to expand...
Click to collapse
Ty for the advice... I will do that.
Yea, i can wipe data/factory reset, but its the same. Bootloop until stuck to "fastboot reason: fall-through from normal boot mode."
I've read about this scenario for months on several different model forums and I imagine my best chance is to use the blankflash in edl mode but i can't boot into edl mode. Wherever I connect it is always recognized as a Motorola PCS or Motorola ADB device. I'm thinking of buying the deep flash cable and see if it works ...
$ fastboot getvar current-slot
//Getting and setting the slot should not cause any harm, but you never know.
$ fastboot --set-active=<a/b - whichever "current-slot" isn't.>
$ fastboot reboot
EDIT0:
In addition, you should plan ahead if you do get in. Like doing everything it takes to allow you to unlock/flash (adb).
You don't want to miss anything critical and screw up that other slot too.
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Hazardous2u said:
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Click to expand...
Click to collapse
Aún no hay solución
To everyone who is having this problem, just run the command multiple times in a row and it works! I don't know why, but just running it a few times in a row (I had to do like 9 times) gave me the unlock code.
Same thing for applying the code after getting it from Moto. Had to do it like 9 times in a row again, but it worked.
I tried unlocking the bootloader of my phone, Realme C25s (Sorry, i know wrong forums, there's no realme c25s)
but whenever I tap the "Start in-depth test"
and it will reboot on the bootloader, showing the errors below:
oplus verify fail
need to verify signature of another brand
oplus verify pass
fastboot verify success
fastboot_unlock_verify ok
Click to expand...
Click to collapse
but the fastboot/my pc cannot detect the phone whenever i try to "fastboot devices", so i won't be able to do the "fastboot flashing unlock"
please help me, i want to unlock the bootloader of my phone
CloudChase said:
I tried unlocking the bootloader of my phone, Realme C25s (Sorry, i know wrong forums, there's no realme c25s)
but whenever I tap the "Start in-depth test"
and it will reboot on the bootloader, showing the errors below:
but the fastboot/my pc cannot detect the phone whenever i try to "fastboot devices", so i won't be able to do the "fastboot flashing unlock"
please help me, i want to unlock the bootloader of my phone
Click to expand...
Click to collapse
it's already unlocked now hold power button and volume up for 20 seconds
Glenmar Dev said:
it's already unlocked now hold power button and volume up for 20 seconds
Click to expand...
Click to collapse
It's not, if it is i should be able go flash patched boot.img from magisk, but the fastboot keeps telling me that flashing is not allowed on locked devices
CloudChase said:
It's not, if it is i should be able go flash patched boot.img from magisk, but the fastboot keeps telling me that flashing is not allowed on locked devices
Click to expand...
Click to collapse
May I know the link for the unlock app that you used? All of the deep testing app that I tried are not working