Related
LG D801 (T-Mobile) Bricked[/U][/B]
The device has been bricked and is in this condition:
Download mode shows as dots and is not recognized by Windows (only occasionally as "Unknown Device")
No custom recovery (it has been wiped in fastboot)
No ROM (system was wiped)
It makes a nice paperweight
Click to expand...
Click to collapse
This device does not allow fastboot, unless there is a software issue (which I cannot purposely cause without ADB in a custom recovery).
I have tried every set of drivers on Windows 7 Ultimate (64 bit) and am unable to change the COM port to 41 because the device isn't recognized at all (it was being recognized last night, but the version of Windows I have didn't have ANY options to change the COM serial port).
No, a rooting method will not work (I'm a Recognized Developer, so trust me).
I have Linux and Windows 7 dual-booting.
I have used everything [URL="http://storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2F"]HERE
Click to expand...
Click to collapse
.
I have also tried THIS driver method (when the device was actually visible on Windows, but the driver never successfully installed).
I manually repartitioned the device using this method on Ubuntu, but accidentally used the stock recovery image.
I am trying to use this method, for Windows, with no luck (because of the phone not being recognized on Windows).
I have tried a friend's desktop with no luck. I have used different USB ports and cables, as well.
Any help at all would be greatly appreciated. Especially if I could somehow trigger fastboot.
Click to expand...
Click to collapse
Thanks in advance,
Mike Criggs
So you flashed LG's stock recovery, can you actually boot into that?
savoca said:
So you flashed LG's stock recovery, can you actually boot into that?
Click to expand...
Click to collapse
It just sticks at the "Processing factory reset..." message.
I need a miracle here, haha.
Your download mode works if there are no blue circles when you start it.
Try installing ubuntu, knoppix etc under vmware and see if it gives you any errors.
also under windows watch the devices under device manager.
bender_007 said:
Your download mode works if there are no blue circles when you start it.
Try installing ubuntu, knoppix etc under vmware and see if it gives you any errors.
also under windows watch the devices under device manager.
Click to expand...
Click to collapse
Oh if his download mode is just hanging at the loading screen but never gets to the loading circle it's most definitely a goner, considering his recovery hangs that probably confirms he dd'ed the wrong bootstack.
@MikeCriggs Check if you have fastboot mode when you try loading recovery or download mode (as the bootloader's fallback) - if not you need to RMA. No big deal I've killed 2 so far via bootloadery mischief.
Is there a JTAG like device out there that can fix this phone's hard bricks?
tiguy99 said:
Is there a JTAG like device out there that can fix this phone's hard bricks?
Click to expand...
Click to collapse
JTAG is disabled for G2.
savoca said:
JTAG is disabled for G2.
Click to expand...
Click to collapse
Has the op tried this method?
MikeCriggs said:
LG D801 (T-Mobile) Bricked
Thanks in advance,
Mike Criggs[/SIZE]
Click to expand...
Click to collapse
Did you make sure that when you put your device in download mode that you changed the port to COM41 in device manager?
tiguy99 said:
Has the op tried this method?
Click to expand...
Click to collapse
Thank god I'm good with hardware! I'll give this a try tomorrow, thank you!!!
Updated!
Thank you all for your help so far!
Updated!
Thank you all for your help so far!
MikeCriggs said:
Thank god I'm good with hardware! I'll give this a try tomorrow, thank you!!!
Click to expand...
Click to collapse
No worries!
Keep us posted on how it goes.
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.
rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...
I held the power and vol down and now it shows up under com ports so this is a good sign.
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...
5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?
Hi guys,i was looking for guide how to unlock Axon 7 with latest update 1.2.0B05 but can't find anything. Can someone please help? I want to flash resurrection remix rom and not to brick phone...or is there better roms?
I cannot believe you're asking this question.
YOU HAVEN'T READ ANYTHING.
This board is full with uncountable guides.
https://forum.xda-developers.com/showthread.php?t=3573108
Not working....error: Length cannot be less than zero. Parameter name: length
salle25 said:
Not working....error: Length cannot be less than zero. Parameter name: length
Click to expand...
Click to collapse
Really, the last thing this forum needs is people unable to find guides on their own...
Ask @bkores about the error
WTF is wrong with you ppl?? I came to ask for help and you told me i'm retarded and stupid in nice way! If you don't wan't to help anyone then don't post reply or help and don't QQ about that! Thanx a lot!
salle25 said:
WTF is wrong with you ppl?? I came to ask for help and you told me i'm retarded and stupid in nice way! If you don't wan't to help anyone then don't post reply or help and don't QQ about that! Thanx a lot!
Click to expand...
Click to collapse
I'm sry but there's nobody here who will tell you're stupid,
People here are willing to help, but if you are too lazy to search for the guides (yes more then one is available) people will tell you that you are lazy.
Now I link a working guide for you
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
If you want it easier, search for the toolkit, it will make the most work for you.
Nope....not working. axon7tool.exe keeps crashing: "This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Toolkit is useless too,MiFlash doesn't see phone when in EDL mode,reinstaled every possible driver i found and not even Zadig helped. I had custom roms on every singe phone i had,but this one is pain in the ...
Got it sorted....renaming to .bin was problem,thanx
question
me too
salle25 said:
Got it sorted....renaming to .bin was problem,thanx
Click to expand...
Click to collapse
Yes it's a bit harder to unlock and flash, good you managed that, I forgot to tell you that there are two toolkits win32 and win64.
Help cant repair my Axon 7 G latest B05
coremania said:
Yes it's a bit harder to unlock and flash, good you managed that, I forgot to tell you that there are two toolkits win32 and win64.
Click to expand...
Click to collapse
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Bizon86 said:
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Click to expand...
Click to collapse
So what don't you understand on this message? It tells you that your bootloader is already unlocked [emoji779] [emoji779]
marcus.linkenbach said:
So what don't you understand on this message? It tells you that your bootloader is already unlocked [emoji779] [emoji779]
Click to expand...
Click to collapse
No is not unlocked Axontooolkit says something oposit. I try both guides from this topic and:
- twrp dosent instal
- cant allow oem unllock
- when use UNLOCK BOOTLOADER Miflash dosent see my devices
Bizon86 said:
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Click to expand...
Click to collapse
Your bootloader is unlocked, you only got to managed the rest, read this thread here, you will see it's familiar to your situation, read to the end.
https://forum.xda-developers.com/axon-7/help/to-date-guide-rooting-a2017g-b04-t3666808
I try this and still. nothing
Bizon86 said:
I try this and still. nothing
Click to expand...
Click to collapse
This is a bit thin.
A bit more details, you don't manage to go to edl mode ?
Did you try zadig to to get the right drivers working ?
What do see in device manager ?
Can you boot to stock recovery?
Did you tried to start from scratch with the guide, not the toolkit ?
No detail, no help
Edit: if you use only the toolkit, may ask in the toolkit thread for help ???
coremania said:
This is a bit thin.
A bit more details, you don't manage to go to edl mode ?
Did you try zadig to to get the right drivers working ?
What do see in device manager ?
Can you boot to stock recovery?
Did you tried to start from scratch with the guide, not the toolkit ?
No detail, no help
Edit: if you use only the toolkit, may ask in the toolkit thread for help ???
Click to expand...
Click to collapse
Zadig works for axon7tool only, MiFlash uses COM while axon7tool uses usb protocol
- The edl is dont working because phone go blank after use command and computer dosent see it.
- i try zading and try another driver effect is the same.
- in device menager i see android device but only when smartfon is running
- i start from the scratch the effect is the same
- i cant turn allow oem
the problem is with phone if i use adb reboot computer dont see phone
Bizon86 said:
Then what i must do any idea?
Click to expand...
Click to collapse
First of all, understand what you just did. If you don't explain it in an understandable way, we won't get any of it...
So:
-You unlocked the bootloader.
-axon7toolkit failed somewhere, and you didn't tell us exactly where
-you didn't try to use any guide to retake from where it ended up failing
-you didn't try to enter any mode
So just try to get to recovery or fastboot, using the 5 sec screen. After that we'll see
Bizon86 said:
- The edl is dont working because phone go blank after use command and computer dosent see it.
- i try zading and try another driver effect is the same.
- in device menager i see android device but only when smartfon is running
- i start from the scratch the effect is the same
- i cant turn allow oem
the problem is with phone if i use adb reboot computer dont see phone
Click to expand...
Click to collapse
If you go to edl, by adb command or by pressing both volume buttons while connecting usb the screen goes blank, that's ok, it has to be this way.
Why you want to turn on allow oem, you are already unlocked.
Your issue seems to be the driver, I guess.
Edit: try this maybe, from the toolkit FAQ
The toolkit says my device is connected through ADB but adb commands don't work?
Your device may be unauthorized. Unlock your device, open a cmd window, type in "adb devices" and then accept the "Allow USB debugging" prompt on your phone. Make sure to check the "Always allow from this computer" box as well. If you don't get the prompt, try retoggling USB debugging, replugging your device in, and revoking all USB debugging authorizations in developer options.
hello ,
I had installed rescurssion remix rom on my phone and i had decided to change to stock rom. So I give my mobile to a mobile shop and they repaired and changed to stock rom.!!!!actually the problem is......after the repair of my mobile in the mobile shop when I switch power on it directly go to boot loader instead of showing boot logo..After that when it shows the update I updated . It suddenly HARD BRICKED.Only the white light near fingerprint sensor worked while charging. please help meee...:crying::crying::crying::crying:
please help me to make my mobile in good condition ........by solving the boot loader issue which shows as the start up...
If I've read your post correctly, you used an OTA update and that's when you had the white light blinking? When you connect your device to your computer, what is your device recognised as? Is it recognised as Qualcomm HS-USB 9008 or similar?
If so, you may wish to look at this guide to try to get your device fixed: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Do you know what the shop did for the repair, what stock ROM did they flash to your device?
echo92 said:
If I've read your post correctly, you used an OTA update and that's when you had the white light blinking? When you connect your device to your computer, what is your device recognised as? Is it recognised as Qualcomm HS-USB 9008 or similar?
If so, you may wish to look at this guide to try to get your device fixed: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Do you know what the shop did for the repair, what stock ROM did they flash to your device?
Click to expand...
Click to collapse
yes it recognize as Qualcomm HS-USB 9008 something like that
the shop has installed rom with build number NPJS25.93-14-18.....I think its april 2018 update
charuvilapauljohn said:
yes it recognize as Qualcomm HS-USB 9008 something like that
the shop has installed rom with build number NPJS25.93-14-18.....I think its april 2018 update
Click to expand...
Click to collapse
actually i did not know what did hey doo
what to do for the start up problem ith always starts with the boot loader
charuvilapauljohn said:
actually i did not know what did hey doo
what to do for the start up problem ith always starts with the boot loader
Click to expand...
Click to collapse
I'm confused by what help you're asking for, as you appear to be asking for help on how to fix a hard bricked device, and yet also asking for help on your device starting with the bootloader. If your device is fully hard bricked, then you wouldn't have a bootloader to boot to... Can I thus ask please is your device still in a blinking light state or are you now booting to the bootloader?
I asked you also in your other post if using fastboot oem fb_mode_clear would work in clearing the bootloader start: https://forum.xda-developers.com/showpost.php?p=76927663&postcount=421 However, if your device is truly hard bricked (and is in the Qualcomm HS-USB 9008 mode), then you need to try the blankflash as linked above, then re-flash the stock ROM - the NPJS25.93-14-18 April 2018 fastboot ROM and guide is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
thanks..it worked
It worked...thanks a lot...I installed NPJS25.93-14-18 rom....
Now there is another problem..both the sim and the finger print is not working
charuvilapauljohn said:
It worked...thanks a lot...I installed NPJS25.93-14-18 rom....
Now there is another problem..both the sim and the finger print is not working
Click to expand...
Click to collapse
That's because you phone model is changed to G4 only (not plus,) and lost 2nd IMEI... (Check in about section)
If it's changed to G4, follow,
Follow linked thread to solve: post #139, and better to read all posts to get correct information. (Turn pages to Download correct HW.img that's meant for your device model)
https://forum.xda-developers.com/mo...luss-model-changed-to-g4-lost-t3496912/page14
the hw.img file not working
____Mdd said:
That's because you phone model is changed to G4 only (not plus,) and lost 2nd IMEI... (Check in about section)
If it's changed to G4, follow,
Follow linked thread to solve: post #139, and better to read all posts to get correct information. (Turn pages to Download correct HW.img that's meant for your device model)
https://forum.xda-developers.com/mo...luss-model-changed-to-g4-lost-t3496912/page14
Click to expand...
Click to collapse
As I found a hw.img file for my xt1643.and i tried to install.The TWRP RECOVERY got struck.And the adb command prompt is not showing anything
So, i flashed a stock android 7 rom on my moto g4 plus. It was working fine, until, i updated it for a new security update(the rom had security version of December,2017) and it restarted. The update started to install but after sometime minutes, it switched off. I tried charging it up, but only the LED at the bottom is blinking but i can't start it up. I tried going into bootloader mode but i can't go in the bootloader mode. Any possible way i can get this phone working? Even going into bootloader will be okay for me as i will then factory reset my device. Please help me. The service centre people are taking like $155 but the phone itself is slightly more than it.
Fantastic Lord said:
So, i flashed a stock android 7 rom on my moto g4 plus. It was working fine, until, i updated it for a new security update(the rom had security version of December,2017) and it restarted. The update started to install but after sometime minutes, it switched off. I tried charging it up, but only the LED at the bottom is blinking but i can't start it up. I tried going into bootloader mode but i can't go in the bootloader mode. Any possible way i can get this phone working? Even going into bootloader will be okay for me as i will then factory reset my device. Please help me. The service centre people are taking like $155 but the phone itself is slightly more than it.
Click to expand...
Click to collapse
It got hard bricked because you downgraded ROM and then tried to update..
Now try blank-flash,
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Download latest firmware from here :
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Try using the blankflash here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 for GPT or bootloader files, have a look here https://drive.google.com/folderview?id=0B-GUyOfb8OgzcUl1NUtHYWNIR2M
What device do you have and what firmware did you have? In future, please avoid using ota updates if you flashed an old stock firmware.
echo92 said:
Try using the blankflash here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 for GPT or bootloader files, have a look here https://drive.google.com/folderview?id=0B-GUyOfb8OgzcUl1NUtHYWNIR2M
What device do you have and what firmware did you have? In future, please avoid using ota updates if you flashed an old stock firmware.
Click to expand...
Click to collapse
i can't blank flash as the phone is not getting detected by the PC.
____Mdd said:
It got hard bricked because you downgraded ROM and then tried to update..
Now try blank-flash,
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Download latest firmware from here :
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
i can't blank flash as the phone is not getting detected by the PC.
Fantastic Lord said:
i can't blank flash as the phone is not getting detected by the PC.
Click to expand...
Click to collapse
Hmm, do you have the Motorola drivers installed https://support.motorola.com/us/en/drivers and do you have driver signature enforcement disabled if running Windows 10 or 8.1? https://www.google.co.uk/amp/s/www....so-that-you-can-install-unsigned-drivers/amp/
Are you also using the original USB cable or a high quality USB data cable?
echo92 said:
Hmm, do you have the Motorola drivers installed https://support.motorola.com/us/en/drivers and do you have driver signature enforcement disabled if running Windows 10 or 8.1? https://www.google.co.uk/amp/s/www....so-that-you-can-install-unsigned-drivers/amp/
Are you also using the original USB cable or a high quality USB data cable?
Click to expand...
Click to collapse
currently i am using an original data cable, also, i have the moto usb drivers installed.
Fantastic Lord said:
currently i am using an original data cable, also, i have the moto usb drivers installed.
Click to expand...
Click to collapse
From your description, you said: you have already flashed firmware, is it same PC ?
If it's same PC, and Cable then i see no problem with PC, drivers, and Cable.. all fine..
Just make sure charging your phone for couple of minutes,
In addition, have service center guys made any changes in device ?
____Mdd said:
From your description, you said: you have already flashed firmware, is it same PC ?
If it's same PC, and Cable then i see no problem with PC, drivers, and Cable.. all fine..
Just make sure charging your phone for couple of minutes,
In addition, have service center guys made any changes in device ?
Click to expand...
Click to collapse
i don't think the service center people did anything to it, but yeah they tested it and said that the phone was having 86% battery. Any ideas?btw thanks for replying