Database Info

Sony Xperia Z3 D6616 possibly hard bricked?

Hi all! I have a Sony Xperia Z3 I recently acquired, it seems to be bricked, possibly hard bricked I'm not sure, but the phone refuses to boot into fastboot or flashmode. Here's what I've noticed so far:
EDIT: The bootloader on the device was never actually unlocked! After getting in contact with the previous owner, all he did was use KingRoot to gain root access on the phone, then installed SuperSU and Clockworkmod recovery respectively. After installing the custom recovery the previous owner had then attempted to flash a variant of Cyanogenmod but the flash failed, since the bootloader wasn't unlocked, resulting in the bricked state the phone is currently in.
The phone shows a red LED when left plugged in to charge overnight
If power button + volume up buttons are held, the red led turns off and the phone vibrates 3 times, but nothing else happens
When connected to the computer via USB, the red led will appear again for a couple seconds, then disappear, then appear, and repeats this process until unplugged. While this is happening you can hear the computer recognizing the phone being constantly plugged in and unplugged.
When plugged into the PC, flashtool recognizes the phone as "Device Connected with USB debugging OFF"
Booting into fastboot or flashmode doesn't work, no matter what button combinations I've tried none of them worked to put the phone in either of these modes.
Is there any way I can unbrick the phone? I don't think this is a driver issue as the computer is recognizing the device in device manager and flashtool sees it, however shows "Device Connected with USB debugging OFF". Is there anyway to somehow enable USB debugging in this state?
I've also tried using adb commands to reboot into fastboot, however this is pointless as the phone is not recognized as an ADB device, when you type "adb devices" there is no devices listed.
HUGE thanks to anyone who has any input on my situation, any help is gladly appreciated! Thank you everyone!

I'm not sure you can do anything about it being hard bricked but I did want to ask you a question how was you able to unlock the bootloader on your tmobile z3, that might be why it's acting up cause I heard tmobile z3 bootloader couldn't be unlocked

lavin40 said:
I'm not sure you can do anything about it being hard bricked but I did want to ask you a question how was you able to unlock the bootloader on your tmobile z3, that might be why it's acting up cause I heard tmobile z3 bootloader couldn't be unlocked
Click to expand...
Click to collapse
EDIT: I just got in contact with the previous owner, the bootloader was actually not unlocked, the phone was simply rooted via KingRoot, after that SuperSU was installed, then Clockworkmod recovery. After that the previous owner had attempted to flash a new custom rom from clockworkmod but it failed, resulting in the brick. So as it turns out the most probably reason for the brick was because the bootloader was never unlocked, causing the flash to fail, putting the phone in this bricked state. Does anyone have any suggestions on what I can do at this point to unbrick it, now knowing the bootloader was never unlocked? Thanks!

If there's no way for you to plug it into the PC without the constant unplugging by itself it's very difficult to do anything. If you try to get into flash mode/fastboot is the phone just not recognized or is it in the "red led" mode?
Usually if you flash a custom without the bootloader unlocked, the bootloader corrupts the system and shows an error while trying to boot. A full brick is very uncommon. You may just try to plug it in and see if EMMA or Flash Tool recognizes the device in any possible way.
I guess the last thing you could do is get in contact with a repair service and ask them if there's a chance that they unbrick it.

Omario-242 said:
If there's no way for you to plug it into the PC without the constant unplugging by itself it's very difficult to do anything. If you try to get into flash mode/fastboot is the phone just not recognized or is it in the "red led" mode?
Usually if you flash a custom without the bootloader unlocked, the bootloader corrupts the system and shows an error while trying to boot. A full brick is very uncommon. You may just try to plug it in and see if EMMA or Flash Tool recognizes the device in any possible way.
I guess the last thing you could do is get in contact with a repair service and ask them if there's a chance that they unbrick it.
Click to expand...
Click to collapse
When I try to go into flash mode or fastboot, nothing happens except for the phone vibrating 3 times and getting the red LED. I've also tried plugging it in and running EMMA however it's not recognized at all by it.
Flash tool recognizes the phone, but throws this message everytime its connected
"Device Connected with USB debugging off"
Is there anything I can do with Flash Tool with the phone being recognized in this state?
I guess as a last option I could try to get in contact with a repair service and ask if they'd be able to unbrick it, however I do not know of any as I've never been to one, hopefully theres another way to unbrick it without having to go here.
Thank you everyone so far who has replied to my thread so far! Please let me know if anyone has the same issue or has an idea for helping unbrick my phone, I appreciate all the tips I've gotten so far.

I searched a little bit and most of the people which got the same problem said that they weren't able to unbrick it it just because the device wasn't recognized at all. Maybe try the Sony Update Service (program) and see if it recognizes it in any way.
If you start adb and type "adb devices" with plugged in phone is adb giving out anything?
Maybe try to hold down the volume down/up while plugging it in but don't release it at all.

Use this tool ( Pc companion by Sony). Install driver and repair phone.. It will fix hard brick d6616. You can find intrustion about this tool on google
Sr . Bad english
http://support.sonymobile.com/global-en/tools/pc-companion/
---------- Post added at 05:57 AM ---------- Previous post was at 05:55 AM ----------
D6616 dont have any custom from now. Dont flash any rom or kernel custom, it will lose boot, and hard brick

Omario-242 said:
I searched a little bit and most of the people which got the same problem said that they weren't able to unbrick it it just because the device wasn't recognized at all. Maybe try the Sony Update Service (program) and see if it recognizes it in any way.
If you start adb and type "adb devices" with plugged in phone is adb giving out anything?
Maybe try to hold down the volume down/up while plugging it in but don't release it at all.
Click to expand...
Click to collapse
Hi, thanks for the tips, I just tried downloading and installing the Sony Update Service program however it terminates immediately after opening and checking for updates as Sony has discontinued the program since Sony PC Companion replaces this program.
If I type "ADB devices", the phone does not appear on the list, as for some reason ADB is not finding the phone in the state that it's in. I've tried repeatedly typing in this command numerous times when its plugged with no luck.
I've also even tried holding down the volume down/up buttons with a rubber band as i plug the device into the computer however no change, I still get the same result.
Thanks for the tips though!
tz16 said:
Use this tool ( Pc companion by Sony). Install driver and repair phone.. It will fix hard brick d6616. You can find intrustion about this tool on google
Sr . Bad english
http://support.sonymobile.com/global-en/tools/pc-companion/
---------- Post added at 05:57 AM ---------- Previous post was at 05:55 AM ----------
D6616 dont have any custom from now. Dont flash any rom or kernel custom, it will lose boot, and hard brick
Click to expand...
Click to collapse
I've already tried using Sony PC Companion however it does not detect my phone at all in the current state for some reason. I've tried everything the program told me to do, pressing and holding numerous button combinations however the program will not recognize the phone. Thanks for the tip though.

when my d6616 get bricked.. I follow that way n it unbrick my phone. you should try again.
http://imgur.com/a/pyFcs

tz16 said:
when my d6616 get bricked.. I follow that way n it unbrick my phone. you should try again.
http://imgur.com/a/pyFcs
Click to expand...
Click to collapse
I've tried this exactly as you showed above, however this is the screen I get stuck on, since Sony PC Companion does not recognize my phone. Look at the picture below. Please let me know if you know how to get past this/get Sony PC Companion to recognize my phone, thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ

tz16 said:
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
Click to expand...
Click to collapse
Hi, thanks for the link and instructions, I just installed the drivers successfully, however Sony PC Companion still isn't recognizing my Xperia Z3.
Anything else I can try? Please let me know, thanks

Unplug your device
Hold Volume+ ....and plug in back till your pc load device " flashmod"
I remember this way, when i do it my pc reconized my device with other name

tz16 said:
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
Click to expand...
Click to collapse
I'd guess the problem isn't anything related to drivers on the PC.
The state the OP's device is in is the problem. You can only install/flash/update a device if it is in the correct state for the process (flash mode for updates/installations, fastboot for flash via adb etc.). I for myself never had a brick where the device wasn't recognized in any functioning way.
Usually if a custom rom is flashed onto locked device the bootloader can't process the system as it compares signature keys which aren't present in the custom ROM. The bootloader then exits the loading of the system and gives out an error message, but the device can still boot into flash mode and fastboot.
Since the OP's device doesn't boot into anything (even with various button combinations and/or hard reset) I'd say that it's now a quite nice looking paperweight.
Like I said before I think the only option is to contact the official Sony repair service.
EDIT: One last question, did you plug your device into a USB3.0 in your PC? Because I remember having problems with it while trying to flash something onto my Z3 once. Maybe try a different USB plug if you haven't already.

Omario-242 said:
I'd guess the problem isn't anything related to drivers on the PC.
The state the OP's device is in is the problem. You can only install/flash/update a device if it is in the correct state for the process (flash mode for updates/installations, fastboot for flash via adb etc.). I for myself never had a brick where the device wasn't recognized in any functioning way.
Usually if a custom rom is flashed onto locked device the bootloader can't process the system as it compares signature keys which aren't present in the custom ROM. The bootloader then exits the loading of the system and gives out an error message, but the device can still boot into flash mode and fastboot.
Since the OP's device doesn't boot into anything (even with various button combinations and/or hard reset) I'd say that it's now a quite nice looking paperweight.
Like I said before I think the only option is to contact the official Sony repair service.
EDIT: One last question, did you plug your device into a USB3.0 in your PC? Because I remember having problems with it while trying to flash something onto my Z3 once. Maybe try a different USB plug if you haven't already.
Click to expand...
Click to collapse
Hi, my computer doesn't even have USB 3 ports, I've tried every single USB port on my computer all give the same result..
Do you know how to get in contact with the official sony repair service and would they be willing to unbrick it for free (or for a reasonable price that won't exceed the price the phone is worth) I've tried calling Sony already telling them my Z3 was bricked however they told me that since the phone ran out of warranty 4 months ago, they wouldn't repair it, even if they charged, since apparently Sony doesn't do out of warranty repairs.
If getting the phone repaired via the official sony repair service, I may have found a last option below, however this will require me to take apart the phone.
After doing much more research, I've heard with S1tool, if you take apart the phone and find the testpoint, you can then flash the phone from there in order to get fastboot and flashmode back, then after successful flashing from testpoint, the phone will boot into fastboot/flashmode and allow you to restore the phone normally. Is this possible with the Z3? A quick google search gives you a bunch of threads started for finding the testpoints and recovering those devices for the Xperia Z1, ultra, etc. but I haven't found a specific guide for the Z3. Is this still possible? I've attached pictures below of what I believe is the testpoint for the Xperia Z3, I found these looking them up on the internet.
Thank you everyone who's replied so far, please let me know what I should do at this point. Thanks

sebzter said:
Hi, my computer doesn't even have USB 3 ports, I've tried every single USB port on my computer all give the same result..
Do you know how to get in contact with the official sony repair service and would they be willing to unbrick it for free (or for a reasonable price that won't exceed the price the phone is worth) I've tried calling Sony already telling them my Z3 was bricked however they told me that since the phone ran out of warranty 4 months ago, they wouldn't repair it, even if they charged, since apparently Sony doesn't do out of warranty repairs.
If getting the phone repaired via the official sony repair service, I may have found a last option below, however this will require me to take apart the phone.
After doing much more research, I've heard with S1tool, if you take apart the phone and find the testpoint, you can then flash the phone from there in order to get fastboot and flashmode back, then after successful flashing from testpoint, the phone will boot into fastboot/flashmode and allow you to restore the phone normally. Is this possible with the Z3? A quick google search gives you a bunch of threads started for finding the testpoints and recovering those devices for the Xperia Z1, ultra, etc. but I haven't found a specific guide for the Z3. Is this still possible? I've attached pictures below of what I believe is the testpoint for the Xperia Z3, I found these looking them up on the internet.
Thank you everyone who's replied so far, please let me know what I should do at this point. Thanks
Click to expand...
Click to collapse
Ok I think I'm out on this point as I honestly have no idea about the whole test point procedure. About repair service though, I guess they don't repair it because they may have to give warranty on their repaired products. Maybe try a mobile repair service in your neighborhood if there's one, but like you said I don't know if the price for a repair exceeds the devices worth.
I guess if you can find this test point it would be a reasonable option for you and I really wish you good luck with that and your phone.

Here's some more screenshots of where I'm at right now as far as the phone being recognized by the computer. The phone shows up as 2 devices, HID-compliant device, and USB input device. I've attached pictures of this in device manager below as well as the list of Connected Devices I see in flashtool when I go to Devices > Check Drivers

sebzter said:
Here's some more screenshots of where I'm at right now as far as the phone being recognized by the computer. The phone shows up as 2 devices, HID-compliant device, and USB input device. I've attached pictures of this in device manager below as well as the list of Connected Devices I see in flashtool when I go to Devices > Check Drivers
Click to expand...
Click to collapse
is your device recognize in fastboot....instead of 'adb devices' try 'fastboot devices' in cmd,
if it does try to use fastboot to reboot into recovery.

ndmuni said:
is your device recognize in fastboot....instead of 'adb devices' try 'fastboot devices' in cmd,
if it does try to use fastboot to reboot into recovery.
Click to expand...
Click to collapse
Hi, thanks for the tip, however the phone doesn't seem to be recognized in fastboot devices either. Heres a screenshot of what I get when I type in adb devices and fastboot devices. Thanks

Try installing Minimal adb with fastboot from here http://forum.xda-developers.com/showthread.php?t=2317790
If youconnect your device in fastboot mode....power off, hold vol up ..does your pc sees it?

Hard bricked my OnePlus One by just rebooting it, help! [5$ REWARD]

I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.

Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.

First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English

sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are saying.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)

Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.

sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers

MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.

I have same thing did it work
I am just wondering if u managed to fix it.

I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/

Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.

install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers

[Hisense A5] How to Enter Hardware EDL mode

Hisense A6, A6L, A5 ... can not unlock bootloader
you can enter A5 hardware edlmode
teardown your phone
jump this point with clip(?)
and connect usb cable
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if can not enter
you need take off power cable ( right bottom corner)
and retry
you can enter EDL mode
you need A5's QFIL firmware

joygram said:
Hisense A6, A6L, A5 ... can not unlock bootloader
you can enter A5 hardware edlmode
teardown your phone
jump this point with clip(?)
and connect usb cable
if can not enter
you need take off power cable ( right bottom corner)
and retry
you can enter EDL mode
you need A5's QFIL firmware
Click to expand...
Click to collapse
Hi, thanks for the useful information.
Previously I bricked my A5 and was able to re-flash with 6.09.06.
I thought I would be able to issue the "adb reboot edl" command. But it didn't seem to work for me.
If I issue the "adb devices" command, I get the response "List of devices attached" with a number and the word "device".
I can do an "adb shell" command ... works well ... can go in there and put in some linux commands.
But when I issue the "adb reboot edl" command, it appears to work. The phone becomes unresponsive. If I issue the command "adb devices", it says that nothing is there.
But when I go into the QFIL program ... there is "No Port Available".
Any ideas ?

try step.
no adb required.
just jump point and connect power cable.
you should retry until catch QFIL catch port.
CrotteDeChien said:
Hi, thanks for the useful information.
Previously I bricked my A5 and was able to re-flash with 6.09.06.
I thought I would be able to issue the "adb reboot edl" command. But it didn't seem to work for me.
If I issue the "adb devices" command, I get the response "List of devices attached" with a number and the word "device".
I can do an "adb shell" command ... works well ... can go in there and put in some linux commands.
But when I issue the "adb reboot edl" command, it appears to work. The phone becomes unresponsive. If I issue the command "adb devices", it says that nothing is there.
But when I go into the QFIL program ... there is "No Port Available".
Any ideas ?
Click to expand...
Click to collapse

Anybody who knows:
How do you open the device without breaking it?
Ehere to begin to open it?
What tools (i.e. screwdrivers T5?) you need?
Does an Edl-Hardware USB-Cable works with the Hisense to enter Edl-Mode? How?

Yeah, how to open the Hisense A5?

Use something like a guitar pic (plastic plectrum) on the edge of the cover and open the cover carefully i.e. upper front.

lillo9546 said:
Yeah, how to open the Hisense A5?
Click to expand...
Click to collapse
I used just my fingernail. You can start opening from the weakest point which is near the sim card port.

Hi Everyone, thanks you your tips.
I went to a phone repair place and paid them 20 AUD to open the phone.
I am having trouble getting the phone into edl mode, (which I found means Extended Download Mode BTW).
Reading more there is information regarding PCB (printed Circuit Boards) and the test points. These are the points we are mean to be "jumping".
What is the sequence of events ? Do I turn off the phone first ? Do I turn on the phone while having the points jumped ?
Do I connect the phone to the computer via USB first, and then allow debugging ... and THEN jump the points with tweezers or a paperclip ?
Any ideas would be greatly appreciated.

CrotteDeChien said:
I am having trouble getting the phone into edl mode, (which I found means Extended Download Mode BTW).
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
See after Step 6., but really be careful. Good luck
https://in.c.mi.com/thread-387857-1-0.html

Entered EDL mode after tearing down my phone. Flashed the "prog_emmc_.... .mbn" and "rawprogram_000b....." files with QFil successfully. But my phone just lights up, shows Hisense logo when try to start the device. Same bricked device.
Any idea?

Mehedi34 said:
Entered EDL mode after tearing down my phone. Flashed the "prog_emmc_.... .mbn" and "rawprogram_000b....." files with QFil successfully. But my phone just lights up, shows Hisense logo when try to start the device. Same bricked device.
Any idea?
Click to expand...
Click to collapse
Dear Mehedi,
use the base firmware 6.03.02 for edl-mode flashing in Qfil provided from gowin132
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Then flash this in Qfil see here some general infos
https://forum.xda-developers.com/showpost.php?p=82654769&postcount=79
use "prog_emmc_firehose_8937_ddr_000bf0e1.mbn"
from the package of joygram
Flash each partition in Qfil Partition Manager (Menu Tools)
After that reboot the device and it should work.
Then upgrade to latest 6.09.06 with TFMode (microSD)
https://forum.xda-developers.com/showpost.php?p=82583733&postcount=28

see also here
https://forum.xda-developers.com/an...nfo-thread-t4101945/post82794951#post82794951

JLowe said:
see also here
https://forum.xda-developers.com/an...nfo-thread-t4101945/post82794951#post82794951
Click to expand...
Click to collapse
Successfully unbricked my phone. Thanks everyone [email protected] @joygram @gowin132

Mehedi34 said:
Successfully unbricked my phone. Thanks everyone [email protected] @joygram @gowin132
Click to expand...
Click to collapse
Good to hear that you're successful! You can't soft brick these China Qualcomm Smartphones
Have fun with this great device!

5 Methods to enter EDL mode on any Xiaomi smartphones [Qualcomm]
5 Methods to enter EDL mode on any Xiaomi smartphones [Qualcomm]
1. Boot EDL Mode via ADB Commands
2. Use Fastboot to Boot EDL mode on any Xiaomi smartphones
3. Use Hardware Buttons
===> Turn off your device.
===> Press and hold the Power + Volume Down buttons together and immediately connect the device to the PC.
===> It will automatically boot into EDL mode and LED lights may blink.
4. Use Deep Flash Cable
5. Use PCB Test Points

Well I guess I bricked my phone. I had it rooted with google play services but wanted to reset it. After a factory reset it seems like I'm stuck in a boot loop or something and also can't get into TF mode to flash the original firmware again.
I had many services disabled but nothing uninstalled before the factory reset.
Does anyone know what I can do to unbrick it or get into TF mode?

hammelgammler said:
Well I guess I bricked my phone. I had it rooted with google play services but wanted to reset it. After a factory reset it seems like I'm stuck in a boot loop or something and also can't get into TF mode to flash the original firmware again.
I had many services disabled but nothing uninstalled before the factory reset.
Does anyone know what I can do to unbrick it or get into TF mode?
Click to expand...
Click to collapse
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!

JLowe said:
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!
Click to expand...
Click to collapse
I made a deep flash cable myself but sadly that doesn't seem to work either. Maybe I did something wrong with the cable but it seems all good to me. I can connect another phone with it and it functions normally, so the only thing that can be defect is the switch/button itself which shorts/connects the green and black wire together.
When I plug the Hisense in my computer with the button pressed it "starts normally" into the boot loop or something and when I let go off the button nothing happens.
As far as I read, you press the button, plug the phone into the computer and after about 8 seconds or so you let go off the button and it will boot into edl mode. But it doesn't seem to work for me.
Thank you. Any help would be very appreciated.
Edit: Okay I got it. For some reason I had to press the button on the cable, volume up/down and power button together for a few seconds until it showed up i QFIL.

JLowe said:
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!
Click to expand...
Click to collapse
Same me. I had rooted it but i tried to reflash stock firmware and now has bootloop. How imcan fix? If i flash root it will boot, but i want to go back to stock

Mehedi34 said:
I used just my fingernail. You can start opening from the weakest point which is near the sim card port.
Click to expand...
Click to collapse
I also used my fingernail too, its easy to handle,

How To Guide Repair your ASUS ROG Phone 5 with EDL mode

If your phone can only enter EDL mode (9008 mode)
this firmware is glad to help you. It can be flashed in through the miflash tool.
The firmware is made through the official package
WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
CN_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.62_Phone-user.raw
without any modification, Suitable for repairing phones that can only enter edl mode (9008 mode).
What should we do?
1. First, the computer must install Qualcomm's driver and ASUS fastboot driver,
otherwise the computer will not recognize the connected mobile phone
cannot recognize the connected mobile phone.
2.Then open the MiFlash2020-3-14 folder, open XiaoMiFlash.exe
3. Select the unzipped images folder, It prompts that flash script cannot be found,
just click on, it doesn't matter.
4. Before flashing this file, please re-enter the edl mode,
use the USB port on the left side of the phone to connect to the computer,
and then press and hold the power button, volume + and volume-at the same time,
and wait until the phone re-enters the edl mode.
5. Then click "load device", see COMx, it means your phone is connected,
then click flash, just wait a few minutes. The prompt is success, flash done,
indicating that the flashing is complete, and now you can start your phone
by pressing and holding the power button.
If you are worried that there is a problem with this firmware,
you can re-enter the fastboot mode and flash the official raw file again.
NOTE :
If You don't understand see the Video tutorial.
and if you have knowledge about EDL then try it.​
All Files Link :
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw.zip​
​
CN_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.62_Phone-user.raw​
​
MiFlash2020-3-14-0​
QD_Loader Driver
CN_Edl-Images
WW_Edl-Images
prog_firehose_ddr.elf
ALL IN ONE
Share with Credit :
johnny & HunterTik.​

HunterTik said:
If your phone can only enter EDL mode (9008 mode)
this firmware is glad to help you. It can be flashed in through the miflash tool.
The firmware is made through the official package
WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
CN_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.62_Phone-user.raw
without any modification, Suitable for repairing phones that can only enter edl mode (9008 mode).
What should we do?
1. First, the computer must install Qualcomm's driver and ASUS fastboot driver,
otherwise the computer will not recognize the connected mobile phone
cannot recognize the connected mobile phone.
2.Then open the MiFlash2020-3-14 folder, open XiaoMiFlash.exe
3. Select the unzipped images folder, It prompts that flash script cannot be found,
just click on, it doesn't matter.
4. Before flashing this file, please re-enter the edl mode,
use the USB port on the left side of the phone to connect to the computer,
and then press and hold the power button, volume + and volume-at the same time,
and wait until the phone re-enters the edl mode.
5. Then click "load device", see COMx, it means your phone is connected,
then click flash, just wait a few minutes. The prompt is success, flash done,
indicating that the flashing is complete, and now you can start your phone
by pressing and holding the power button.
If you are worried that there is a problem with this firmware,
you can re-enter the fastboot mode and flash the official raw file again.
NOTE :
If You don't understand see the Video tutorial.
and if you have knowledge about EDL then try it.​
All Files Link :
WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw​
​
CN_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.62_Phone-user.raw​
​
MiFlash2020-3-14-0​
QD_Loader Driver
CN_Edl-Images
WW_Edl-Images
Share with Credit :
johnny & HunterTik.​
Click to expand...
Click to collapse
Thanks bro, But could you please upload the images file on a different website or provide a new like.
Thanks in advance.

Any ways to get this to work? https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/

File Updated to mega.nz server successfully

HunterTik said:
File Updated to mega.nz server successfully
Click to expand...
Click to collapse
Miflash reports object reference not set to an instance of an object error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

FlareMaster said:
Miflash reports object reference not set to an instance of an object error View attachment 5298947
Click to expand...
Click to collapse
see the Video tutorial

HunterTik said:
see the Video tutorial
Click to expand...
Click to collapse
CN_images does not have files such as instructional videos

how to enter edl mode?

FlareMaster said:
CN_images does not have files such as instructional videos
Click to expand...
Click to collapse
On video it's showing only ww ROM

HunterTik said:
On video it's showing only ww ROM
Click to expand...
Click to collapse
both are missing prog_ufs_firehose_*.elf file

alan_greece said:
both are missing prog_ufs_firehose_*.elf file
Click to expand...
Click to collapse
Yes, both lack the files needed for flash rom

It is seems something missing or wrong for both CN and WW.
tried many times but no chance to flash.
Please provide a full images file, thanks in advance

Object reference does not point to an instance of an object ((

goodfoxes said:
Object reference does not point to an instance of an object ((View attachment 5300593
Click to expand...
Click to collapse
elf files is missing wait until he upload it.

Has anyone tried this and made it work?

monoxian said:
Has anyone tried this and made it work?
Click to expand...
Click to collapse
Not worked for me.

Why my device manager cant read qdloader 9008 driver?

I bought my phone from Aliexpress and is tencent version flashed with global. After opening and setting it up, it was working fine until after I plugged it into my PC to transfer files
I plugged it out, installed my apps, then it just died. No warning or anything, just ploof.
When I plug it into its charger, it does a boot loop.
When charging on the side, it boots up the android logo then the ROG logo but dies right after.
When charging on the bottom, it flashes the android logo and dies.
While it does that I held the volume up button, I can access fastboot and it stays on with the options:
- Start
- Restart bootloader
- Recovery mode
- Power off
I tried every option to no avail.
When I plug out the charger while in fastboot, it dies.
I think the battery connection is fried.

asim KHadka said:
I bought my phone from Aliexpress and is tencent version flashed with global. After opening and setting it up, it was working fine until after I plugged it into my PC to transfer files
I plugged it out, installed my apps, then it just died. No warning or anything, just ploof.
When I plug it into its charger, it does a boot loop.
When charging on the side, it boots up the android logo then the ROG logo but dies right after.
When charging on the bottom, it flashes the android logo and dies.
While it does that I held the volume up button, I can access fastboot and it stays on with the options:
- Start
- Restart bootloader
- Recovery mode
- Power off
I tried every option to no avail.
When I plug out the charger while in fastboot, it dies.
I think the battery connection is fried.
Click to expand...
Click to collapse
Can anyone please tell me if its software problem or hardware?

I have the same issue. I have just returned the phone

My moto g XT1032 is bricked.

I forgot to charge it and then the battery went completely dead. I tried to charge it but it took forever. Then it would start. I did several things and got into the fast boot mode tried other things and thus it is now unable to start. I think I found a thread that pretty much fits my problem. I show it below
.
[IMG alt="neozen21"]https://forum.xda-developers.com/data/avatars/s/3041/3041348.jpg?1600603258[/IMG]
neozen21​Senior Member​
Mar 28, 2014 at 11:28 PM
#2
NexusHaggis said:
hi everyone,
i accidentally deleted all of my data from my sd card when i got stuck in a bootloop and now my moto g has no OS installed. I've tried using adb to push the stock ROM onto it but because I cant access usb debugging through TWRP it doesn't even recognise my device is plugged in. any advice would be help full thanks.
Click to expand...
Click to collapse
Hmmm.. You basically have 2 options here.
1. Get ADB working (it's not hard, try the Koush's Universal ADB driver)
2. Restore back to stock ROM, but you will need Fastboot working.
The thing is, if you can get Fastboot working, ADB should work too.. so...
If you need help with ADB, just ask..
------------------------------------------------------------------------------------------------
I need help. The phone is not recognized by my laptop when it is connected via USB. However, it does connect to the Motorola Rescue and Smart Assistant software. The Rescue program askes for my phone's MEI number. When entered
it ask for the phone version number and shows 2 choices XT1032 and XT1033. I select XT1032 and the program responds that my firmware is not the same as XT1032. I cannot go any further to get fixed.
I tried to follow your instructions but since my phone will not connect to my laptop I can't do anything.
I know this is lengthy and may sound immature but I need your help. Please help if you can.
Thanks in advance.
tvlover

tvlover said:
I forgot to charge it and then the battery went completely dead. I tried to charge it but it took forever. Then it would start. I did several things and got into the fast boot mode tried other things and thus it is now unable to start. I think I found a thread that pretty much fits my problem. I show it below
.
[IMG alt="neozen21"]https://forum.xda-developers.com/data/avatars/s/3041/3041348.jpg?1600603258[/IMG]
neozen21​Senior Member​
Mar 28, 2014 at 11:28 PM
#2
Hmmm.. You basically have 2 options here.
1. Get ADB working (it's not hard, try the Koush's Universal ADB driver)
2. Restore back to stock ROM, but you will need Fastboot working.
The thing is, if you can get Fastboot working, ADB should work too.. so...
If you need help with ADB, just ask..
------------------------------------------------------------------------------------------------
I need help. The phone is not recognized by my laptop when it is connected via USB. However, it does connect to the Motorola Rescue and Smart Assistant software. The Rescue program askes for my phone's MEI number. When entered
it ask for the phone version number and shows 2 choices XT1032 and XT1033. I select XT1032 and the program responds that my firmware is not the same as XT1032. I cannot go any further to get fixed.
I tried to follow your instructions but since my phone will not connect to my laptop I can't do anything.
I know this is lengthy and may sound immature but I need your help. Please help if you can.
Thanks in advance.
tvlover
Click to expand...
Click to collapse
So, you device is in Fastboot mode?
You should be able to skip the imei and let LMSA choose the firmware.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

sd_shadow said:
So, you device is in Fastboot mode?
You should be able to skip the imei and let LMSA choose the firmware.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
I found that LMSA responds with "doesn't match the appropriate firmware", "you can select a firmware manually". I select Moto g, then select XT1032 and I get "information you input does not match the connected device". Obviously the phone is communicating with the LMSA and dose not have XT1032 firmware installed. The phone is locked and it's a Telus phone. What do you think>

tvlover said:
I found that LMSA responds with "doesn't match the appropriate firmware", "you can select a firmware manually". I select Moto g, then select XT1032 and I get "information you input does not match the connected device". Obviously the phone is communicating with the LMSA and dose not have XT1032 firmware installed. The phone is locked and it's a Telus phone. What do you think>
Click to expand...
Click to collapse
That you will need to flash manually with fastboot.exe
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Tom

I have gone through the posts and have come to the conclusion that my phone's Fastboot flashmode is not working properly and I cannot communicate with my laptop. I guess there is no way to get the phone working. I think it is unusable.
I would like to thank those who have tried to help me and those who have written all of the procedures I have encountered. I give up.

tvlover said:
I have gone through the posts and have come to the conclusion that my phone's Fastboot flashmode is not working properly and I cannot communicate with my laptop. I guess there is no way to get the phone working. I think it is unusable.
I would like to thank those who have tried to help me and those who have written all of the procedures I have encountered. I give up.
Click to expand...
Click to collapse
How does it show in device manager?

sd_shadow said:
How does it show in device manager?
Click to expand...
Click to collapse
I have checked the device manager several times while investigating the issue and it does recognize when the phone is connected. It shows "Android Device" and "Mot Composite ADB Interface". It also shows "Portable Devices" and " Moto E(4)" + " Moto E(4)". The phone I connected with is a Moto G. I do have a working Moto E 4 and it has been connected to both of my laptop's USB ports in the past. Also when I right click on the 2 Moto E4's it displays Moto E 4 properties and shows the Device status "Currently the hardware device is not connected to the computer (code 45)", " To fix the problem reconnect this hardware to the computer". This does not correct the problem.
Please note: This happens when I connect the Moto G with it in the Fastboot Flash Mode. An audible computer tone happens at this time too. When the phone is unplugged the audible sounds and a refreshed Device manager no longer shows the "Android Device". This is why I concluded the phone is unusable.
Let me know what you think.

tvlover said:
I have checked the device manager several times while investigating the issue and it does recognize when the phone is connected. It shows "Android Device" and "Mot Composite ADB Interface". It also shows "Portable Devices" and " Moto E(4)" + " Moto E(4)". The phone I connected with is a Moto G. I do have a working Moto E 4 and it has been connected to both of my laptop's USB ports in the past. Also when I right click on the 2 Moto E4's it displays Moto E 4 properties and shows the Device status "Currently the hardware device is not connected to the computer (code 45)", " To fix the problem reconnect this hardware to the computer". This does not correct the problem.
Please note: This happens when I connect the Moto G with it in the Fastboot Flash Mode. An audible computer tone happens at this time too. When the phone is unplugged the audible sounds and a refreshed Device manager no longer shows the "Android Device". This is why I concluded the phone is unusable.
Let me know what you think.
Click to expand...
Click to collapse
I would Uninstall the driver it is using
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and reinstall Moto drivers
When it's in fastboot/bootloader mode it shouldn't say anything other than "Motorola ADB Interface"
You don't want to see Composite, Portable, or Model

sd_shadow said:
I would Uninstall the driver it is using
View attachment 5412979
and reinstall Moto drivers
When it's in fastboot/bootloader mode it shouldn't say anything other than "Motorola ADB Interface"
You don't want to see Composite, Portable, or Model
View attachment 5412975
Click to expand...
Click to collapse
I did what you suggested and installed the 64 bit drivers successfully. When I right click on Motorola ADB interface Properties - Events tab it says "
Device USB\VID_22B8&PID_2E80\TA92919RWS requires further installation." How do I do that?

tvlover said:
I did what you suggested and installed the 64 bit drivers successfully. When I right click on Motorola ADB interface Properties - Events tab it says "
Device USB\VID_22B8&PID_2E80\TA92919RWS requires further installation." How do I do that?
Click to expand...
Click to collapse
Can you take a screenshot with the snipping tool?

What is a snipping tool. How do I use it?

I think I have found out how. I will try,

Man have I learned a lot from you. Now I can snip.

I hope you didn't misinterpret what I meant in the above reply. So sorry for the way I presented my enthusiasm. I really wanted to tell you how impressed I am with your knowledge. I was wondering before you asked for the screen shot how you got the screen shots into your replies. When you asked I honestly did not know about Snipping. I did some searching on Google and found out that it was part of Windows 10. I tried it and was very impressed. Your help and knowledge has impressed me all along and I was sincere when I made my last post. If it offended you I apologise profusely and hope that you continue to help me with my problem.
Sincerely Eric (tvlover).

tvlover said:
I think I have found out how. I will try,
Click to expand...
Click to collapse
I suspect a bad usb port on the phone.
You have tried other usb ports on the pc? other usb cables?

I have tried both USB ports on my pc with my working device MotoE E4 and they both work ok. Using the same cable and my bricked phone on both ports it does not work.
However when the working phone is connected to the pc the screen lites up on the phone and no audible from the pc is heard. If I sign in to access the phone an audible is heard and I can use the feature of the phone. For example developer options.
When the bricked phone is connected to the pc the screen on the phone lites up with the Motorola "M" and "Android" and a momentary vibration can be felt. It then goes dark and a few seconds later the Android picture with "no command" comes on then goes off the the screen is black again, A few seconds later the Android picture with "no command" comes on then goes off the the screen is black again this happens over and over again. I think the phone tries to start up and it fails due to "no command".
If I then hold the power and volume down buttons for 15 seconds and release them the phone displays the Fastboot Flash Mode screen. The connect audible from the pc is heard and commands are scrolling down the screen and ends with the command "cmd: getvar:all". From this point on nothing works on the phone. The button Volume down will perform the scroll function. The Volume up button causes the Motorola "M" and "Android" display to come on and stay on permanently. I think that the firmware is corrupted so the phone won't start
therefore I cannot access "settings" to access "Developer Options" to change the "USB Configuration" settings.
I think I should give up it is bricked. What do you think?

tvlover said:
I have tried both USB ports on my pc with my working device MotoE E4 and they both work ok. Using the same cable and my bricked phone on both ports it does not work.
However when the working phone is connected to the pc the screen lites up on the phone and no audible from the pc is heard. If I sign in to access the phone an audible is heard and I can use the feature of the phone. For example developer options.
When the bricked phone is connected to the pc the screen on the phone lites up with the Motorola "M" and "Android" and a momentary vibration can be felt. It then goes dark and a few seconds later the Android picture with "no command" comes on then goes off the the screen is black again, A few seconds later the Android picture with "no command" comes on then goes off the the screen is black again this happens over and over again. I think the phone tries to start up and it fails due to "no command".
Click to expand...
Click to collapse
The no command screen is just the stock recovery, you must hold the Power and tap the volume up button to access recovery options.
tvlover said:
If I then hold the power and volume down buttons for 15 seconds and release them the phone displays the Fastboot Flash Mode screen. The connect audible from the pc is heard and commands are scrolling down the screen and ends with the command "cmd: getvar:all". From this point on nothing works on the phone. The button Volume down will perform the scroll function. The Volume up button causes the Motorola "M" and "Android" display to come on and stay on permanently. I think that the firmware is corrupted so the phone won't start
therefore I cannot access "settings" to access "Developer Options" to change the "USB Configuration" settings.
I think I should give up it is bricked. What do you think?
Click to expand...
Click to collapse
fastboot/bootloader mode isn't affected by usb settings in Dev options

I did not know either of these facts. When I was in the "no command" state I held the power key down and tapped the up volume key. This is what appeared at the bottom of a black phone screen:
E: can't mount/cache/recovery/last log
E: can't open cache/recovery/last log
They disappear in a second or two leaving a black screen.