Related
I just tried to restore stock image with fastboot mode, but somethings wrong and now my phone is dead.
No boot, no vibrate, no bootloader, only the black screen and nothing appears.
And qhsusb_bulk device is detected when I connected phone to my computer.
I tried fastboot and adb sideload but it didn't work. How can I restore my phone?
Please help me fix this! :crying::crying:
pi.zero said:
I just tried to restore stock image with fastboot mode, but somethings wrong and now my phone is dead.
No boot, no vibrate, no bootloader, only the black screen and nothing appears.
And qhsusb_bulk device is detected when I connected phone to my computer.
I tried fastboot and adb sideload but it didn't work. How can I restore my phone?
Please help me fix this! :crying::crying:
Click to expand...
Click to collapse
No known way except JTAG service, although I can't recall a Moto X Pure/Style being done successfully... Otherwise contact Moto Customer Care or take it to a service center.
Unfortunately, on these devices a hard-brick is exactly that, bricked.
i have a unit same problem hard bricked
No solution yet
pi.zero said:
I just tried to restore stock image with fastboot mode, but somethings wrong and now my phone is dead.
No boot, no vibrate, no bootloader, only the black screen and nothing appears.
And qhsusb_bulk device is detected when I connected phone to my computer.
I tried fastboot and adb sideload but it didn't work. How can I restore my phone?
Please help me fix this! :crying::crying:
Click to expand...
Click to collapse
were you able to resolve your issue?
Welp... looks like I joined this club. I downgraded to sept security patch without an issue but when upgrading to december.... I get this.
@gokart2 I know this is a long shot but I'll ask anyway haha. Seeing that you've done a ton of help and support on this device and mind you, I will be the guinea pig in this whole process whether it borks the phone even more or not. Do you think you can attempt to modify this process with Moto X Pure's bootloader and I will attempt to run it? If not, no biggie.
https://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Ended up going through moto repair and had them send me a new XT1575 for 75 bucks. Thanks anyway... no more messing with downgrading boot loaders anytime soon.
Doubt I could have done much good. New phone for $75 isn't too bad though.
Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !
Dr_Raider said:
Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !
Click to expand...
Click to collapse
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode
Choose an username... said:
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode
Click to expand...
Click to collapse
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.
Kantastisch said:
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.
Click to expand...
Click to collapse
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)
Choose an username... said:
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)
Click to expand...
Click to collapse
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.
Kantastisch said:
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.
Click to expand...
Click to collapse
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Choose an username... said:
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?
Click to expand...
Click to collapse
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Kantastisch said:
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Click to expand...
Click to collapse
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash
Choose an username... said:
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash
Click to expand...
Click to collapse
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...
Kantastisch said:
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...
Click to expand...
Click to collapse
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).
Choose an username... said:
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).
Click to expand...
Click to collapse
THANKS SO MUCH , you saved my ass, it flashed without a problem and sorry for bothering you. Bootloader is locked now and it works fine. Thanks again!
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Same problem
Same thing happened to me. Same day as you. I can get fastboot but not adb but since the device is locked I can't flash. I've only had the phone about 6 months so I contacted customer support and they offered to replace the phone.
It might be a known issue because they didn't even try to address the fact that I could get fastboot connected but not adb. They just offered to replace.
Thanks for the info! I am -at least in this case- unfortunately an early adopter. I bought two essentials at the beginning of the pre-release.
Essential support checked my serial number and said the phone was out of warranty.
Has anyone been able to force the Essential into EDL mode to recover that way? It looks like you have to latch one of the USB pins to ground, or 5V, but I haven't found any detailed instructions on how to make this work on the essential...
Thanks again
Justin
I'm sure things have changed and I'm wrong, but if you can get into the fastboot menu can't you just cycle through the options until you get to recovery and then flash an official release from Essential?
I may be thinking of LG or something but this should be possible as long as it's newer than the current software installed because it will see it as an official update and allow the flash.
Thanks but unfortunately, when I try and do that, the phone just does the same thing, it hangs forever on the initial boot screen white Android text with the circle/square logo...
That's why I've been looking into the more direct hardware version of forcing the phone into EDL mode, which is supposed to be possible with all Qualcomm based phones.
I've just not found the time yet to find a USB-C cable I'd be happy to cut in half and short the pins on! Which is why I was hoping someone might have tried this with an essential before to know if it was successful before I start trashing good cables
Thanks again for your reply!
JB
justinbaird said:
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Click to expand...
Click to collapse
I have the exact same problem,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cannot flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you
So, basically I will make this short as possible
Due to some problems I had to sell my G6 Plus (Brazilian -8 model) but it was on a custom rom, and did the most dumb thing that I could do: Reflashing pure stock and locking it, I've used the LMSA tool then relocked in Fastboot, the thing is some files were corrupt and when locked, it doesn't boot up anymore, as i still had hope for it, I tried to LSMA again, but it doesnt recognize anymore, as the lock flag is now "Flashing_Locked", flashing manually via Fastboot gives a error related to the lock flag (also LSMA resets the device, so using my unlock key asks to enable OEM Unlock at settings, a impossible thing when OS is broken) , then searched for some solutions, first it was booting a Boot.img file from the last stock, which was the flashed one, it bootloops, then tried something on the recovery that works, but is the stock one and pretty limited, so the logical thing to do is flashing a OTA file, but only works for old versions that requires one version before the target one, so its a no go. The last thing i tried to do is booting TWRP, but it gets stuck on a red warning that indicates that system is corrupt. Then the last hope was EDL Mode, and thats the point where i want to go, i've bought a EDL Cable that's basically a green and black wire thing used on most Qualcomm based Redmi/Xiaomi devices, but it automatically boots to fastboot, so I need help to get EDL Test Points for this device, im with access to the board, i just need the right Pads to short-circuit it and blankflash it, so i can finally get it to work like normal again.
Schematics (for people who understands): https://androidfilehost.com/?fid=4349826312261726244
Any help is important, I'm sorry for some typos, english isnt my main language considering i didnt use translate
and please don't come with instructions like "have you tried LSMA?, try booting up the device and select oem unlock" because its clear that it doesnt work.
I bought a Motorola Moto C Plus a while ago so I can root it and play around with it. I tried to unlock the bootloader for a while on this phone but I just can't. Every guide I tried didn't work. From mfastboot to MTKClient.
mfastboot just gave "unknown command" when trying to get unlock data, and MTKClient couldn't detect a partition or something when trying to wipe.
Then I tried searching my serial number: ZW2224XFWW, but that gave no results. Not on Google nor on here. Can anybody help. I'm very new to the rooting scene.
EDIT: I have a Moto C Plus with 1GB RAM and 16GB internal storage
MTKClient works, download the live .iso file from https://github.com/bkerler/mtkclient
Boot from it, open a console and type:
pip3 install -r requirements.txt
First just follow the readme to unlock the bootloader and after that root with latest magisk. I just tested all that on a moto C, I don't have the exact model but it was the 8gb/1gb variant.
Something's going terribly wrong because now it hangs at 43.8% while flashing boot partition and i dont know why
(I'm scared...)
MarkPCExpert said:
Something's going terribly wrong because now it hangs at 43.8% while flashing boot partition and i dont know why
(I'm scared...)
Click to expand...
Click to collapse
After further investigation, this happens also at recovery and maybe also other partitions so now it is soft bricked
EDIT: it seems that the connection stops or something because after it fails flashing, i also cant do other operations. I NEED HELP!!!
EDIT 2: after trying the console instead of the gui, i discovered that it was never unlocked in the first place. It said "unknown seccfg partition header, aborting unlock"
You are going to know you have your bootloader unlocked if you see a white letters on black background message saying that the phone will boot in 5 seconds after turning it on. You can't flash anything with a locked bootlader.
THATS EXACTLY WHAT I'M GETTING!!! But still, i can't flash a single thing. and I dont know why. I tried to flash TWRP recovery to install a lineageos build but TWRP hangs at 88%. And the patched magisk thingy hung at 43.8%
Now the phone is kind of bricked.
EDIT: Maybe the hang is because i use USB 2 or the Live ISO on a not so good USB. I do use an upgraded Dell OptiPlex 3010 as my main machine. Or the hang is bcuz it failed to flash.
Reflash the original firmware and try again. If you did a backup just flash the original boot.bin
Welp. I am screwed. I forgot i was running a live USB so the entire backup is gone.
And the userdata was also empty for the most part.
Try this: https://www.motorola.com/us/rescue-and-smart-assistant/p
If that doesn't work see if you can find a stock firmware and flash with flash tool. https://androidfilehost.com/?fid=889964283620774903
I already tried that one, but when i plug it in, it doesnt do anything and I DONT KNOW WHY!
also im on vacation
UPDATE: im back from vacation and no replies, great...
BUT, ive chosen a mostly aosp based rom for the phone.