hey, my motorola one vision got this message displaying " your device has failed verification and may not work properly" that i rescued it and replaced firmware with motorola assistant software then after a while it dead again and now hardbricked it is not not even recognized by my pc before it showed at least exynos driver in ports now it displays not recognized, I tried giving it to service center but they returned it and told they can't fix it connsider going come other center...., so is there anything i could do to get it recognized by my pc..?
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
jwoegerbauer said:
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
Click to expand...
Click to collapse
if it is soft bricked at least it should show the processor connected.., bt in my case it just connects and not turning fastboot or cant even do blank flash
jwoegerbauer said:
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
Click to expand...
Click to collapse
And i tried that ADB-FASTBOOT-INSTALLER, still it shows not recoganized
Re-flashing phone's Stock ROM never is done
Ammar595 said:
And i tried that ADB-FASTBOOT-INSTALLER, still it shows not recoganized by Fastboot.
Click to expand...
Click to collapse
To successfully run Fastboot you additionally have to install on Windows computer the "Android USB Driver" that is suitable to your phone.
See also here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
jwoegerbauer said:
Re-flashing phone's Stock ROM never is done
To successfully run Fastboot you additionally have to install on Windows computer the "Android USB Driver" that is suitable to your phone.
See also here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
Click to expand...
Click to collapse
yes tried this too still not recoganized..
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
jwoegerbauer said:
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
Click to expand...
Click to collapse
so what should i do now..?
jwoegerbauer said:
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
Click to expand...
Click to collapse
this is what its showing and phone is completly dead like a brick..
Delete this USB device from within Windows' Device Manager. Re-install the "Android USB Driver".
jwoegerbauer said:
Delete this USB device from within Windows' Device Manager.
Click to expand...
Click to collapse
yes i did that too, stilll not working....
Ammar595 said:
so what should i do now..?
Click to expand...
Click to collapse
Does this work?
Code:
adb devices
jwoegerbauer said:
Does this work?
Code:
adb devices
Click to expand...
Click to collapse
no..... the only thing working is that it shows not recoganized
We could have saved ourselves all this back and forth if this had been known from the start.
jwoegerbauer said:
We could have saved ourselves all this back and forth if this had been known from the start.
Click to expand...
Click to collapse
so there's nothing i could do now...?
Ammar595 said:
so there's nothing i could do now...?
Click to expand...
Click to collapse
my sdcard reader also show that i think thats normal
ineedroot69 said:
my sdcard reader also show that i think thats normal
Click to expand...
Click to collapse
what is normal....? my phone is entirely dead, it isn't responding al it does is shows not recognized
when i connects it to my pc, ya maybe that's normal, bt am asking for solution not a compliment
Related
Hey
A couple of days ago i tried to install the latest CM12 nightly. After updating it my phone crashed everytime it booted up. I did a factory reset and tried to flash older versions but nothing seemed to work so i went into CWM recovery 6.0.4.5 and pretty much formatted everything.
I still have access to the bootloader and recovery but my Windows 8.1 PC doesn't recognize my phone ("Unknown usb device" "Windows has stopped this device because it has reported problems. (Code 43)") I can't access my phone with adb or fastboot now. This looks like a driver problem but i tried a lot of different drivers on multiple PC's.
What can i do now?
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Darth said:
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
zagorteney said:
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
Click to expand...
Click to collapse
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer. ?
Darth said:
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer.
Click to expand...
Click to collapse
And in future: please, stay on stock.
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
dermaxe said:
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
Click to expand...
Click to collapse
Try this: http://nirsoft.net/utils/usb_devices_view.html
It helped me a few times.
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
Did you use USBDeview or you just manually removed all drivers that you saw?
I went into USBDeview and uninstalled everything that was android related
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
How do i enable usb debugging without any os?
dermaxe said:
How do i enable usb debugging without any os?
Click to expand...
Click to collapse
chaco81 said:
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
Click to expand...
Click to collapse
USB debugging enabled is only needed when using Adb from within the Android OS. It's not needed for adb use in recovery mode, and never needed for fastboot.
??
good to know
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
For me this sounds more like computer realted problem rather than device. If you can try all of those steps ( installign drivers, etc ) on another pc maybe this will solve your issue
Just tried it on a fresh installation of W7 but my device wasn't recognized and i couldn't install any drivers for it. How can it be a PC related problem if it doesn't work on so many different configurations?
If you run it on VirtualBox, see this answer (prepend http, I can't post links): superuser.com/a/887249/239087
To make it short, you need VirtualBox Extension Pack, and you need to configure the USB port to use USB 2.0 at least.
Hi
My phone is international NXT-L29
I was on Ephemeral B180 rom but i decided to upgrade it to get emui 4.1
I flashed back stock b180 rom, and after I flashed stock b321 rom
ROM works great but i would like to get root and twrp back again, but everytime I try to go through fastboot i get this screen on picture.
I logged into my dc unlocker again and followed the procedures (manufacture mode, unlocking,...) and dc unloccker tool informs that the phone was unlocked...but no, when I do adb reboot bootloader i still get the same message on the picture.
I saw other suggestions here on XDA, i confirm oem unlock is activated on developer options...i made factory reset and then "vol+- power" (with or without phone connected to PC) but i dont't get any option to unlock bootloader. I always arrive to a menu saying that the phone is looking for upgrade and tries until 5% is reached... (if I keep waiting it does not fisplat error message, only waits and waits and after a while it reboots normally (i don't have any dload folder either on phone or sd card)
Any suggestion to solve this is highly appreciated
many thanks
Try to get ur unlock code from huawei website maybe this can help.
Did you run the bootloader unlock command with your unlock code again?
Ephemera said:
Did you run the bootloader unlock command with your unlock code again?
Click to expand...
Click to collapse
the only command my phone accept is adb reboot bootloader
Then i get the screen of picture that I posted, which says that it is a cold reboot (?)
Whem I reach this point it doens not respond to anything else taht I type on Command line (I type fastboot oem unlock (and the code) but on pc screen i read 'ewaiting device' and nothing happens on phone
gm007 said:
Try to get ur unlock code from huawei website maybe this can help.
Click to expand...
Click to collapse
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Can I replace the stock boot.img that comes inside the UPDATE.APP file byone decrypted boot image of same rom?
If that would be possible then flashing this "modified" UPDATE.APP would solve the problem?
Many Thanks
pasil.pt said:
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Click to expand...
Click to collapse
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
grofock said:
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
Click to expand...
Click to collapse
I don't see any kedacom usb device folder...
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Ephemera said:
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Click to expand...
Click to collapse
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
pasil.pt said:
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
Click to expand...
Click to collapse
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
grofock said:
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
Click to expand...
Click to collapse
YES!!!!!!
many thanks to you. grofock, and to ephemera, and XDA
At last i got it done. (Huawei are so tricky compared to samsung...but at least they do not explode
gm007 said:
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
Click to expand...
Click to collapse
You were probably right because i recently changed PC and aeverytime w10 upgrades I pray...
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
timasan said:
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
Click to expand...
Click to collapse
try grofock's hints about control panel and Device manager on windows....
pasil.pt said:
try grofock's hints about control panel and Device manager on windows....
Click to expand...
Click to collapse
I try it on four different PCs and still error 43 "wrong descriptor".
timasan said:
I try it on four different PCs and still error 43 "wrong descriptor".
Click to expand...
Click to collapse
Maybe explain more what you did,what are you trying to do and which tools you used.
gm007 said:
Maybe explain more what you did,what are you trying to do and which tools you used.
Click to expand...
Click to collapse
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
timasan said:
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
Click to expand...
Click to collapse
Did you install hisuite it has all the drivers and make sure to enable allow hisuite to use hdb in phone settings under security.
I have a problem with my nexus 5, I try to install the recovery and it stays black screen does not enter the bootloader or anything, my pc recognizes it as android adb interface some help.
me to having same problem dont know what to do
pc not recognising my device
Follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
I hope you have an efs backup somewhere if you don't keep trying..
also how did you try to install recovery? there is a multitude of ways and knowing what you did could help a lot.
Jo_Jo_2000 said:
Follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
I hope you have an efs backup somewhere if you don't keep trying..
also how did you try to install recovery? there is a multitude of ways and knowing what you did could help a lot.
Click to expand...
Click to collapse
Hello thanks for your help I will try, I did the procedure with the tool nexus root toolkit I followed the steps my phone stayed so now it vibrates and reboots constantly my pc only recognizes it as mtp usb or android device.
soujirock said:
Hello thanks for your help I will try, I did the procedure with the tool nexus root toolkit I followed the steps my phone stayed so now it vibrates and reboots constantly my pc only recognizes it as mtp usb or android device.
Click to expand...
Click to collapse
Follow the thread and stop using toolkits since they might do obscure things and people cannot help you if you just say "i did it with the toolkit"
Jo_Jo_2000 said:
Follow the thread and stop using toolkits since they might do obscure things and people cannot help you if you just say "i did it with the toolkit"
Click to expand...
Click to collapse
Hello try to perform the steps but in the device manager I do not get any of that I only recognize the phone as android device.
soujirock said:
Hello try to perform the steps but in the device manager I do not get any of that I only recognize the phone as android device.
Click to expand...
Click to collapse
Thanks for your help, download one that said repair nexus 5 dead and now I get this I think I should do something more because now the pc recognizes me so if you could guide me I would thank you very much.
what happens when you try to open the mtp device?
if not try uninstalling all drivers with google..
you should always be able to reach the dload mode even if it's fully working as long as you follow the steps.
Jo_Jo_2000 said:
what happens when you try to open the mtp device?
if not try uninstalling all drivers with google..
you should always be able to reach the dload mode even if it's fully working as long as you follow the steps.
Click to expand...
Click to collapse
Hello what happens if it opens like a usb but on the screen of my cell you can not see anything even I recognize it in fastboot mode but on the screen I see nothing.
How can i get into dload mode
I try to flash it with the method you gave me but I get a message from device was not found in dload mode trying flash programmer.
maybe your screen is just broken?
also citing the thread linked: "If you dont see Qualcomm HS-USB QDLoader 9008 click on the CLICK TO SHOW CONTENT button bellow, otherwise don't and follow the guide."
Jo_Jo_2000 said:
maybe your screen is just broken?
also citing the thread linked: "If you dont see Qualcomm HS-USB QDLoader 9008 click on the CLICK TO SHOW CONTENT button bellow, otherwise don't and follow the guide."
Click to expand...
Click to collapse
Hello my screen is not broken or anything I already recognized the pc driver qualcom 9008 and perform the procedure of the post now my cell recognizes the pc as nexus 5 in usb mode but I do not have the system.
soujirock said:
but I do not have the system.
Click to expand...
Click to collapse
Aka no reaction or no fastboot or a missing partition?
is recovery working?
is bootloader working?
what has appeared on your screen to show you that it isnt broken?
Jo_Jo_2000 said:
Aka no reaction or no fastboot or a missing partition?
is recovery working?
is bootloader working?
what has appeared on your screen to show you that it isnt broken?
Click to expand...
Click to collapse
Hello, it seems that the fastboot mode works because in the pc it recognizes me as android device and I download a program that is called dead nexus 5.bat and this recognizes me and writes the system and performs other operations more but still nothing appears I do not know if the system can be flashed by this method.
i try with this method https://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 but nothing
can you execute fastboot commands?
what does that script tell you, where is it from?
Please stop using toolkits, they perform obscure unpredictable things.
Also what makes you so certain your screen isn't broken given that everything works except the screen?
Jo_Jo_2000 said:
can you execute fastboot commands?
what does that script tell you, where is it from?
Please stop using toolkits, they perform obscure unpredictable things.
Also what makes you so certain your screen isn't broken given that everything works except the screen?
Click to expand...
Click to collapse
thanks man i solved my problem
i installed corvus os on Xiaomi Mi A3. After the process is completed i rebooted my phone and its not starting. no power on (my battery was 100% when i installed corvus os)
cant just turn on the phone
is the phone hard bricked.
or how can i fix it
Hardbricked means a hardware component no longer is working ( e.g. power button is broken ).
My guess is that the operating system you flashed or the installed software is corrupted, what means the phone got softbricked.
jwoegerbauer said:
Hardbricked means a hardware component no longer is working ( e.g. power button is broken ).
My guess is that the operating system you flashed or the installed software is corrupted, what means the phone got softbricked.
Click to expand...
Click to collapse
Ok thank you for the info
How do you think if its soft bricked could be started again atleast on fastboot
and i dont think its ard bricked because when i hold my power button after 5-8 seconds i can see my phone connected in the pc but only in device manager
i think this could maybe help me for something to fix it
When in Windows's Device Manager under tab Portable Devices phone is listed that simply means phone is connected in USB-MTP mode.
You can check whether phone is accessible by means of Fastboot running these commands - one by one - in Windows CMD prompt
Code:
fastboot devices
fastboot getvar all
jwoegerbauer said:
When in Windows's Device Manager under tab Portable Devices phone is listed that simply means phone is connected in USB-MTP mode.
You can check whether phone is accessible by means of Fastboot running these commands - one by one - in Windows CMD prompt
Code:
fastboot devices
fastboot getvar all
Click to expand...
Click to collapse
i checked but its not showing the device also i can see that my phone is connected by the icon at there but still the problem persists
it maybe a unsupported rom that i installed.
i tried for adb as well but no devices found
As I can see you're proud owner of a softbricked phone, what is neither accessible via Fastboot nor ADB.
My recommendation: Take phone to authorized service center and let them try to fix it.
jwoegerbauer said:
As I can see you're proud owner of a softbricked phone, what is neither accessible via Fastboot nor ADB.
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
ok Thank you for your suggestions
Hi All
I have ROG 5s tencent edition. it was modified by seller to global. I have been using it for more than 1 year now. Last night something happened and it went off. I tried turn it on but it kept bootlooping at logo. It is not detetedable by computer because bootloader was locked by seller before selling. I had no idea about that at that time.
MY device is now in bootloop. I can open bootloader but it won't take me to recovery mode. Fastboot commands are also not working . Phone not found by computer in any state. Can any one provide me with some pointers on how an i flash firware,
Recoery is not opening. When I select it from bootloader it keeps bootlooping
Fastboot is not seen by computer. Tried many cables, both ports.
If anyone can guide me that be a huge favor as this is my daily driver
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Andrologic said:
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Click to expand...
Click to collapse
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
dksoni411 said:
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
Click to expand...
Click to collapse
If there isn't a hardware issue with the device, you should be able to.
Try to delete the driver and re-install it. Use the official Android USB driver from the SDK as opposed to Qualcomm drivers from random places on the net. Plug it in from the side port and try to turn it on while connected. Have Device Manager in Windows open and notice changes. Read out what it is recognized as. If absolutely nothing, then it's the cable, Windows or the device may really have a motherboard defect.
I believe it's more likely motherboard. Is there any fix for it?