Bricked Phone USB not recognized by PC - General Questions and Answers

Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.

vnandwana said:
Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.
Click to expand...
Click to collapse
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. Yes, USB debugging was enabled before it got bricked. I was able to successfully see my device when I ran adb -devices command. I was also able to run fastboot commands. Now its completely dead.

Related

[Q] ADP not working

I wanted to use nvflash to bring back to clean slate. Could not get the USB driver issue resolved in Windos 7 or XP, Read the threads, just did not work. Also noticed that the USB connect to the GTablet stopped working, it woriked fine for before trying adp. Tried Linux and the device is not seen using LSUSB did see the device is I tried via USB debugging mode. I power on and hold the vol- button see boot screen then unit goes black. No usb connect to PC either after trying.
Reset the device to stock with CWM and PC USB comes back. Is there a utility or something to check the ADP functionality at boot level, has anyone had USB issues that can help? Is it a possible hardware issue?
mrmpo said:
I wanted to use nvflash to bring back to clean slate. Could not get the USB driver issue resolved in Windos 7 or XP, Read the threads, just did not work. Also noticed that the USB connect to the GTablet stopped working, it woriked fine for before trying adp. Tried Linux and the device is not seen using LSUSB did see the device is I tried via USB debugging mode. I power on and hold the vol- button see boot screen then unit goes black. No usb connect to PC either after trying.
Reset the device to stock with CWM and PC USB comes back. Is there a utility or something to check the ADP functionality at boot level, has anyone had USB issues that can help? Is it a possible hardware issue?
Click to expand...
Click to collapse
Try USBDeview: http://www.nirsoft.net/utils/usb_devices_view.html
Disconnect the G Tablet from your PC. Then run USBDeview as administrator (i.e. right click and Run as Administrator in Windows 7). Then uninstall any drivers related to the G Tablet.
Now plug in G Tablet and it should be detected again and you can point it at a properly working ADB driver on your PC.
Have done that, but it seems that it is something on the GTablet that is causing the error. When is is malfunctioning no USB connections work and driver issues pop up, after set to factory the USB works and driver issue for storage go away.
So far I can tell that adp mode from power and vol - unroots my tab and I can not connect to pc. After re-rooting I can connect. Linux can not see device in adp mode.
Update. Returned the unit to sears for a new one and problem solved. I must of had a clinker.

Root without PC/USB

Hi,
Have a TF101 tablet here stock rom, stock recovery...
However it seems the USB will not detect on a windows PC tried multiple cables multiple PC's tried from recovery nothing is detected in device manager at all. Tablet doesn't even detect that its connected to PC either.
Is there anyway to root this thing without USB??? I need to root it so I can install recovery and flash another rom.
Thanks,
Which Windows version are you running?
If you use Win 7 and prior you should be able to connect with the universal naked drivers manually installed from device manager
Win 8 and above need driver signing disabled or they wont install the driver and the PC wont see the TF
If you have already tried the above, you might need a new cable
http://forum.xda-developers.com/showthread.php?t=1688012
*Detection* said:
Which Windows version are you running?
If you use Win 7 and prior you should be able to connect with the universal naked drivers manually installed from device manager
Win 8 and above need driver signing disabled or they wont install the driver and the PC wont see the TF
If you have already tried the above, you might need a new cable
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Thanks. Well i tried windows 7 x64 and windows 8 x64, neither showed any device or unknown device in device manager... Tried multiple cables as wel, no dice...
Shouldn't MTP work regardless of drivers installed in windows 7/8 ?
Are you putting the TF into APX mode?
Connect TF to PC USB > Power Off TF > Hold Power & Volume Up until the PC recognises it (Only takes a couple seconds, nothing appears on the TF screen) then install drivers
You need APX mode for Easyflasher
For normal media transfer, it will still need to install at least some USB type driver, as do all USB devices to function, possibly not the APX drivers
Check in Developer Options > USB Debugging mode
Try it enabled and disabled with the TF plugged in
But really the MTP drivers are not what you need if you want to root. you need APX mode to work (As above)
*Detection* said:
Are you putting the TF into APX mode?
Connect TF to PC USB > Power Off TF > Hold Power & Volume Up until the PC recognises it (Only takes a couple seconds, nothing appears on the TF screen) then install drivers
You need APX mode for Easyflasher
For normal media transfer, it will still need to install at least some USB type driver, as do all USB devices to function, possibly not the APX drivers
Check in Developer Options > USB Debugging mode
Try it enabled and disabled with the TF plugged in
But really the MTP drivers are not what you need if you want to root. you need APX mode to work (As above)
Click to expand...
Click to collapse
Doesn't seem to do anything when I hold power vol+, the screen of the tablet (blank/off) and on the pc nothing is being detected.
I can get to the bootloader/recovery via holding power vol- though. Also tried USB debugging mode... nothing is detected whatsoever... ordering another cable on ebay will see if that works but I doubt it since it seems to be a common issue with this tablet (port not working with pc)
I edited my post
Nothing will appear on the TF screen in APX mode until data transfer begins
The cheap non genuine cables are renowned for data connection failing, genuine cables are recommended
I still have my original cable and it still works 100%
*Detection* said:
I edited my post
Nothing will appear on the TF screen in APX mode until data transfer begins
The cheap non genuine cables are renowned for data connection failing, genuine cables are recommended
I still have my original cable and it still works 100%
Click to expand...
Click to collapse
Using the original cable, I still can't tell if its in APX mode, installed all the drivers provided by asus, nothing is detected in windows device manager. I'm 100% its not being detected ie. no connection. I ran easyflasher anyway both sbk1 and sbk2 says it flashed recovery but it never did still the stock recovery is on the tablet.
Will try again once the new cable comes in, thanks.
Forget the ASUS drivers, use the Universal ones from the Easyflasher thread
Here's what will happen when its working as intended
When you plug the TF into the PC, no matter what mode it is in, the PC should sound the USB connect sound
When you power off the TF, then put it in APX mode, the PC will again sound the USB connect noise, then it will fail to install the correct drivers
That's when you open Device Manager, find the ! missing driver ! exclamation mark, and update drivers manually pointing it to the extracted Universal drivers
Once you have installed them, then Easyflasher should work as normal
So unless you actually have a hardware fault on the TF, or the USB ports of the PC, Id hedge my bets on the cable
Have you tried a different PC?
*Detection* said:
Forget the ASUS drivers, use the Universal ones from the Easyflasher thread
Here's what will happen when its working as intended
When you plug the TF into the PC, no matter what mode it is in, the PC should sound the USB connect sound
When you power off the TF, then put it in APX mode, the PC will again sound the USB connect noise, then it will fail to install the correct drivers
That's when you open Device Manager, find the ! missing driver ! exclamation mark, and update drivers manually pointing it to the extracted Universal drivers
Once you have installed them, then Easyflasher should work as normal
So unless you actually have a hardware fault on the TF, or the USB ports of the PC, Id hedge my bets on the cable
Have you tried a different PC?
Click to expand...
Click to collapse
Ok, well ya thats the thing no sound or detection of anything when plugging it in, or going into apx mode, rebooting etc...
I tried 2 cables and 2 different PCs. Will try a new cable but I betting that is won't work either... we'll see.
Thanks again
No need to bother with cables and drivers, just download Baidu Root: https://app.box.com/s/pyehf9fh4xem3hy50dot
EDIT: The app has built-in su access management, but I'd recommend installing SuperSU from the Play Store.
Duchman said:
No need to bother with cables and drivers, just download Baidu Root: https://app.box.com/s/pyehf9fh4xem3hy50dot
EDIT: The app has built-in su access management, but I'd recommend installing SuperSU from the Play Store.
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!! Worked to let me get TWRP installed and flashed a new rom with SU etc...
Thanks again!!!!!!!!!

Help needed! ADB issues(detected on phone but not in fastboot)

Dear all,
Please Help me. My One plus one is on CM12 official rom (rooted). Problem is when I connect my phone to computer and use ADB it is detected (adb devices: number & devices detected) but when in fastboot (fastboot devices : nothing is detected) I check in my device manager (yellow triangle on android ) My problem is why CAN it be detected when my phone is on but NOT during fastboot.
Necessary checks done : USB debugging, Universal driver, SDK installed, USB driver reinstalled again, tried changing usb ports on computer, tried on 2 laptops)
I am helpless, tried checking on forums can not find the answer.
CalvinVeez said:
Dear all,
Please Help me. My One plus one is on CM12 official rom (rooted). Problem is when I connect my phone to computer and use ADB it is detected (adb devices: number & devices detected) but when in fastboot (fastboot devices : nothing is detected) I check in my device manager (yellow triangle on android ) My problem is why CAN it be detected when my phone is on but NOT during fastboot.
Necessary checks done : USB debugging, Universal driver, SDK installed, USB driver reinstalled again, tried changing usb ports on computer, tried on 2 laptops)
I am helpless, tried checking on forums can not find the answer.
Click to expand...
Click to collapse
Have test to fastboot commands?
In fastboot be unplugged
Write
fastboot reboot
for test
Will answer wait for device
Plug device to test
My pc also does not recognise but work fine
with commands
geowolf1000 said:
Have test to fastboot commands?
In fastboot be unplugged
Write
fastboot reboot
for test
Will answer wait for device
Plug device to test
My pc also does not recognise but work fine
with commands
Click to expand...
Click to collapse
Tried adb reboot bootloader then phone boots into fastboot mode but from here..
is total no connection. Tried checking fastboot devices (nothing), fastboot reboot (waiting)
then i tried as u said unplug & plug in (not recognize) from here adb cannot be written anymore. (no more commands can be typed). Tried others like down loading Pdanet ,force install driver..Nothing works. Thinking ,did I corupt the bootloader while I was rooting it last time.?
I think if something was wrong with bootloader you could not either boot .
Do you use antivirus to pc?
Try without antivirus
What happening the false is from computer
Mine is reverse issue. When in fastboot mode, pc recognizes OPO, but when OPO is normally connected to pc, adb is not working. Its charging and can transfer data through USB, but OPO is not recognized through adb commands. Device Manager too recognizes my OPO only when it is in fastboot mode and not when normally connected via USB for data transfer.
I have a software, through which I can REVERSE TETHER my PC's internet to my mobile via USB. Because my OPO is not recognized via USB in normal mode, I can't do that. Any idea, what's wrong with my OPO.
(I have installed Android SDK and google usb drivers, for my OPO to work in fastboot. I have rooted. My pc runs on win7)
mrsureshisha said:
Mine is reverse issue. When in fastboot mode, pc recognizes OPO, but when OPO is normally connected to pc, adb is not working. Its charging and can transfer data through USB, but OPO is not recognized through adb commands. Device Manager too recognizes my OPO only when it is in fastboot mode and not when normally connected via USB for data transfer.
I have a software, through which I can REVERSE TETHER my PC's internet to my mobile via USB. Because my OPO is not recognized via USB in normal mode, I can't do that. Any idea, what's wrong with my OPO.
(I have installed Android SDK and google usb drivers, for my OPO to work in fastboot. I have rooted. My pc runs on win7)
Click to expand...
Click to collapse
Install pdanet+ for win

Custom Binary Blocked by FRP Lock Error

İ use custom rom and i disabled OEM unlocking and restart my phone. Phone cant boot. My USB port isnt work and i cant use odin. Cant open twrp. Actually isnt broken but my PC cant recognize my phone i try different cable, pc and driver but Windows says unkown device.
nereloyka13 said:
İ use custom rom and i disabled OEM unlocking and restart my phone. Phone cant boot. My USB port isnt work and i cant use odin. Cant open twrp. Actually isnt broken but my PC cant recognize my phone i try different cable, pc and driver but Windows says unkown device.
Click to expand...
Click to collapse
How did you flash TWRP and custom if your USB port isn't working?
Download Mode is independent of ROM so unless your hardware got damaged since flashing custom, there's no reason it shouldn't work
Try installing Samsung S7 driver again, remove old drivers from device manager first while phone is connected / enabled "Show hidden devices" from device manager while phone is disconnected and remove old drivers
Windows should install the correct driver itself
*Detection* said:
How did you flash TWRP and custom if your USB port isn't working?
Download Mode is independent of ROM so unless your hardware got damaged since flashing custom, there's no reason it shouldn't work
Try installing Samsung S7 driver again, remove old drivers from device manager first while phone is connected / enabled "Show hidden devices" from device manager while phone is disconnected and remove old drivers
Windows should install the correct driver itself
Click to expand...
Click to collapse
İ try 4 different PC. İ charge my phone with wall charher but phone see USB charging. İ install twrp with odin but i cant use odin now. Windows says unkown device and odin cant recognize. https://forum.xda-developers.com/galaxy-s7/help/usb-device-recognized-fast-charge-t357118/ its my problem
That link redirects me to here
https://forum.xda-developers.com/showthread.php?t=357118
If you have tried 4 PCs, and different USB cables then you need to get your USB port on the phone replaced / repaired
*Detection* said:
That link redirects me to here
https://forum.xda-developers.com/showthread.php?t=357118
If you have tried 4 PCs, and different USB cables then you need to get your USB port on the phone replaced / repaired
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s7/help/usb-device-recognized-fast-charge-t3571184/page2 you can see my comment page 2

Device not recognized in fastboot on Mac and not recognized at all on PC

I'm hoping someone can help me out here. I've rooted phones before and didn't have any trouble previously. I just bought a used Pixel 3 on eBay with the plan to root using Magisk. The only problem is I can't get the device to be recognized at all on my PC. I've tried all the usual things like different USB ports, different cables, cleaning out the port, etc. I have the latest drivers installed and I have a Pixel XL that is recognized by my PC immediately so I know I have the correct drivers installed. Pixel 3 does not show up in Device Manager at all. I have USB debugging enabled on the device, but it never prompts me to Allow USB debugging when I connect the Pixel 3 to my PC.
Now, here's the weird part. I know the cable is working fine because I use the same cable and plug it into my Mac. The Pixel 3 is recognized immediately and I'm prompted to enable USB debugging. ADB then works just fine on my Mac. 'adb devices' shows my phone. But I then try to use 'adb reboot bootloader' and my phone reboots to the bootloader as it should. At this point my phone says it's in FastBoot Mode, but the device isn't recognized using 'sudo fastboot devices' and if I try 'sudo fastboot flashing unlock' it just sits there saying 'waiting for any device'. I've also tried putting it into FastBoot mode manually by using the Power and Volume Down key, but run into the same issue with it not being recognized while in FastBoot mode.
Could the previous owner have done something to the bootloader to cause the device to not be recognized in FastBoot mode? And is there any way to fix it? Why would the phone be recognized on my Mac without issue, but using the same cable and multiple different ports on my PC, it never gets recognized?
Any help would be very much appreciated here as I'm at a loss as to what I can do and fear I just spent money on an expensive paperweight.
I tested the cable I'm using with my Pixel XL and it's immediately recognized by my PC and the notification for USB debugging shows on the phone, so I know the cable is working out. No device ever shows in the device manager when I have my Pixel 3 connected though. I've even uninstalled the drivers while my Pixel XL is connected to hopefully put Windows into a driverless state hoping my Pixel 3 would then show up as an unrecognized device, but no device. I can't get it to show up at all in Windows for some reason and it's not recognized while in fastboot mode on my Mac. Fastboot mode information all seems to match what a Pixel 3 should look like as well, so I don't think the previous owner installed the wrong software causing device id mismatch. Anyone have any other suggestions for what I can try?

Categories

Resources