I was trying to upgrade from A9 to A10 and phone booted into bootloader. probably because i didn't clear internal memory. but it didn't even let me boot back into twrp recovery, which i upgraded to be compatible with android 10.
i have done all that before and never had problems that my pc didn't recognise the phone. tried on linux, not just windows - same story. tried on different windows machine - again the same. doesn't even show it as unrecognised device under device manager. tried cleaning usb ports, still no difference. even cahnged the battery as i've read somewhere that low battery can cause phone not being recognised.
now i don't know what else to try. could be loose data pins at side usb c port that would cause this?
any help is appreciated
edit: i disassembled the phone and checked all the pins from side port. now i can't say for sure, but it seems like few pins are be shorted to ground. i'm not sure if i accidentally poked with multimeter shielding instead of pin, but i tested few times on continuity and last three pins all beeped on ground. can't really see inside the port that good, but it looks all untouched. could it be that damage is already done when they shorted for the first time or is there any hope?
Did you use side usb when trying to access fastboot? Also in my opinion its a simple matter of switching active slot, like from A to B or viceversa. Also, did you update with an ota file, thru TWRP or how?
VarDes said:
Did you use side usb when trying to access fastboot? Also in my opinion its a simple matter of switching active slot, like from A to B or viceversa. Also, did you update with an ota file, thru TWRP or how?
Click to expand...
Click to collapse
ofcourse i used side port. how to switch active slot if i can't access recovery nor connect phone to the pc to boot up twrp?
i updated through twrp with full android 10 zip downloaded from asus
Related
I have a USB BRICK and wishing that someone could help me fix it
[STORY]
My phone was working perfectly until a few days ago when I noticed that USB connection to PC stopped working. I was running imilkas CM9 v2. USB used to work perfectly and then randomly, it just stopped working, I don't have a clue what caused it because I did not flash anything on the phone.
When I connect my Phone to the Computer via USB cable, my phone start charging and nothing else happens. My computer does not even show that I connected a USB device.
I've tried 3 other computers with the drivers and the same issue (1 comp with xp and the others with win 7). Also, not to mention, I've tried multiple USB cables, including the original. I've tried USB Debugging on and off, doesn't make a difference.
I've tried ADB and it does not recognize the device either.
In CWM when I mount USB storage, it does not work.
In download mode, when I plug in the cable, nothing happens, odin does not detect any connection.
USB connection to the computer is Dead and it does nothing but charge my phone. I've searched this issue and I believe its called a USB BRICK
[THINGS I'VE TRIED THAT DID NOT FIX THE ISSUE]
1. Factory Reset.
2. Used Mobile Odin, reverted to my Phone's Stock GB ROM (KK2). On stock GB, I tried Kies Air and that worked fine, but USB connection had the same issue. Also tried Stock ICS via Mobile Odin
3. Formatted the Internal Storage
4. Removed the SIM Card and Micro SD card, still no luck.
5. re-installed CWM manually (without pc)
6. Tried various different roms in the development section
7. Called Samsung... They said they wont service my phone because I'm located in Canada and I have the International Note. They told me I'd have to take it to the country I bought it from.
8. Replaced the micro USB hardware component inside the phone (bought it from ebay)
9. Tried a Jig to see if it recognizes that and it booted me into download mode but doesn't recognize the USB connection to PC.
I've been struggling with this issue for the past 2 months and have gotten sick of this issue.:crying: I've tried all that was possible based on my knowledge and now I need some serious help. I've posted this issue in the Q&A before and about 3 people responded with suggestions that I had already mentioned in thread. I believe this issue might be caused by a file that has gotten corrupted on the phone because i've even replaced the hardware (usb port) and it didn't change anything. If anyone can offer any help/suggestions that would be great. Sorry for making this such a long post but I really need some help and wanted to give as much info as possible.
Thanks in advance.
I had that same problem before, it's really frustrating having tried so many stuff before finally I gave up and went to service center to replace the usb hardware module, which solves the problem. When I asked them why it happened and how to prevent that same thing to happen again, they didn't answer.
kopitalk said:
I had that same problem before, it's really frustrating having tried so many stuff before finally I gave up and went to service center to replace the usb hardware module, which solves the problem. When I asked them why it happened and how to prevent that same thing to happen again, they didn't answer.
Click to expand...
Click to collapse
I've already replaced the usb hardware module myself. I bought it from ebay. It didnt change anything.
ssyed said:
I've already replaced the usb hardware module myself. I bought it from ebay. It didnt change anything.
Click to expand...
Click to collapse
1. You bought it from ebay
2. You changed it personally
Send it in for proper repair.
Sent from my GT-N7000 using xda app-developers app
praetorius said:
1. You bought it from ebay
2. You changed it personally
Send it in for proper repair.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I am well versed in replacing hardware components myself. The usb module I bought from ebay does exactly the same thing as the original one. It too charges but does not recognize PC connectivity which means it wasnt the usb module which was defective, its something else!
I would love to send it in for repair, but Samsung WON'T service my phone because I live in Canada and they do not sell the international Note here. When I called them they told me to take it to where I bought it from (which was in UAE). Since I am not going there and have no plans to go there, I am stuck with a phone that can't be warrantied!
Any one know how to fix this issue?
Maybe what you need is just to replace the usb cable... Who knows? (trying-to-help mode).
kopitalk said:
Maybe what you need is just to replace the usb cable... Who knows? (trying-to-help mode).
Click to expand...
Click to collapse
I've tried multiple different cables, including the original, in multiple different usb ports! nothing works.
I appreciate the suggestions tho
Try another set of driver from Samsung.
The set in the file from link below works perfectly for me:
http://www.mediafire.com/?ager59qlwy35q50
If it does not work then, maybe, try to change rom. Load a custom rom.zip to external sdcard and flash using CWM.
cheers.
I had the somewhat similar problem, few days back and started a thread.
http://forum.xda-developers.com/showthread.php?t=1732686
Ok here is the solution. It worked for me. Hope it helps someone
1. download latest version of kies for PC
2. uninstall previous kies (if any) and install new one.
3. On the cell phone, dial the following number: *#7284#
Once the last # is hit, the PhoneUtil application is launched. Choose USB -> Modem and then USB -> PDA mode. (Even if the mode is PDA, switch to Modem and then back to PDA.)
4. Plug the USB cable.
darthvedor said:
I had the same problem, few days back and started a thread.
http://forum.xda-developers.com/showthread.php?t=1732686
Ok here is the solution. It worked for me. Hope it helps someone
1. download latest version of kies for PC
2. uninstall previous kies (if any) and install new one.
3. On the cell phone, dial the following number: *#7284#
Once the last # is hit, the PhoneUtil application is launched. Choose USB -> Modem and then USB -> PDA mode. (Even if the mode is PDA, switch to Modem and then back to PDA.)
4. Plug the USB cable.
Click to expand...
Click to collapse
Hmm it looks like your issue was different.. at least you were getting some sort of message that you connected your phone. When I connect it to the computer, its as if nothing happened. I've even tried linux and its just that the phone isnt recognizing its connected to a computer, it thinks its connected to a charger.
I tried your suggested solution, still no avail!
ssyed said:
it thinks its connected to a charger.
Click to expand...
Click to collapse
if you have CWM installed, just boot into CWM Recovry >
advance > wipe battery status
turn off the phone, remove battery for 3 mins and than reboot normally. Let us know, if it works.
darthvedor said:
if you have CWM installed, just boot into CWM Recovry >
advance > wipe battery status
turn off the phone, remove battery for 3 mins and than reboot normally. Let us know, if it works.
Click to expand...
Click to collapse
Just tried that... didnt work
I faced a similar problem a few days ago. Here's what I did :
Try cleaning micro usb port by rubbing alcohol using paper strips. They should be thin enough so that you can clean both top and bottom part of the port.Then let it dry under the sun or by itself.Make sure that you don't blow any air into the port else condensation may occur.
By the way, is it monsoon season there in Canada ?
abhijit038 said:
I faced a similar problem a few days ago. Here's what I did :
Try cleaning micro usb port by rubbing alcohol using paper strips. They should be thin enough so that you can clean both top and bottom part of the port.Then let it dry under the sun or by itself.Make sure that you don't blow any air into the port else condensation may occur.
By the way, is it monsoon season there in Canada ?
Click to expand...
Click to collapse
I bought a whole new micro usb module and replaced it. Still didnt change anything.
lol our weatherman is messed up, and where I live, its just been hot and dry for the most part.
i had the same problem before...try changing the rom ...that worked for me
ssyed said:
I have a USB BRICK and wishing that someone could help me fix it
[STORY]
My phone was working perfectly until a few days ago when I noticed that USB connection to PC stopped working. I was running imilkas CM9 v2. USB used to work perfectly and then randomly, it just stopped working, I don't have a clue what caused it because I did not flash anything on the phone.
When I connect my Phone to the Computer via USB cable, my phone start charging and nothing else happens. My computer does not even show that I connected a USB device.
I've tried 3 other computers with the drivers and the same issue (1 comp with xp and the others with win 7). Also, not to mention, I've tried multiple USB cables, including the original. I've tried USB Debugging on and off, doesn't make a difference.
I've tried ADB and it does not recognize the device either.
In CWM when I mount USB storage, it does not work.
In download mode, when I plug in the cable, nothing happens, odin does not detect any connection.
USB connection to the computer is Dead and it does nothing but charge my phone. I've searched this issue and I believe its called a USB BRICK
Click to expand...
Click to collapse
Almost same situation here from the highlighted above. when I plug my charger in the usb it just charge the phone and PC cannot detect it. Also, it only charge the phone when i reboot it. If I unplug the charger while the phone is on, and plug the charger back, it will not charge. However, when I insert the usb cable in my phone, there is a notification in my phone which says "usb connector connected" but the PC cannot detect my phone for mass storage, as well as for Kies and Odin.
My usb port was already replaced by Samsung but same problem still occurs. It could be a software/configuration related issue. Or could it be a usb brick? Pls help.
have you tried to put the phone in download mode and checked if odin is able to detect the phone.. what rom are you on.. have you tried to flash a stock rom ?
I have the same problem ... :crying:
nokiamodeln91 said:
have you tried to put the phone in download mode and checked if odin is able to detect the phone.. what rom are you on.. have you tried to flash a stock rom ?
Click to expand...
Click to collapse
Yes, tried on download mode but odin cannot detect it.
Joined the group of USB Brick ....
I recently tried to install PureNexus 7.1.2 along with the latest version of GApps 20170610. There seems to be some sort of conflict with that version of Google Play Services that prevents my device from completing setup. Without completing setup, I'm not able to do anything with the phone.
In an attempt to save myself, I want to go back to the older version of the ROM and GApps that worked, but first they need downloaded. In the past, I could go into TWRP and mount my device to my PC and transfer the files I needed to install. Now, Windows is showing my device as Unknown USB Device (Device Descriptor Request Failed). Going through every thread I could find about updating drivers, etc, it still does not work. This used to work just fine in the past on the same PC (Windows 10).
Both adb and fastboot don't seem to work either. There is no device found. When I boot the phone into Bootloader mode and plug in the USB cable, it shows Transfer Mode: USB Connected but running fastboot on the PC still can't find anything.
I am not sure how else to go about getting the necessary files on the device to flash them.
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
tristanlee85 said:
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
Click to expand...
Click to collapse
It could be just a dirty usb port.
Where's answers
ktmom said:
It could be just a dirty usb port.
Click to expand...
Click to collapse
Unfortunately I do not think that is the case. I have used a number of different means to clean the connection with rubbing alcohol and electrical terminal cleaner, small utensils to get in there and clean the contacts, but no luck. I am to the point now where the phone won't boot up the OS. I can get into TWRP and the Bootloader, but from there I have no way to transfer files to the device.
Bluetooth was my option before, but that is when the device would boot. There's no way to enable BT from recovery right? I am trying to reset the phone back to stock to trade it in to Google, but I am afraid I am going to be out $100 since it seems to be as good as dead now.
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
No big deal right? I mean sure, I didn't make a back up first (Mistake #2) but it shouldn't matter because I can just go into twrp and factory reset and reflash everything.
So off I went to copy over the zips to my phone -- went ahead and wiped everything (mistake #3) and then opened up windows explorer to copy over the zips. Turned out my computer couldn't see my phone.
I tried mounting and unmounting and installing and uninstalling drivers. Moving over to my other computer (linux mint) messing around with adb sideloads, and lastly tried using OTG. Turned out my computer just couldn't register my phone at all with adb.
So then I switched to fastboot -- at the very least I should be able to reflash stock and then root and then install custom stuf, right? But I couldn't get my phone to even register on windows or linux with driver changes using fastboot!
I was pretty upset at this point (still am, admittedly).
In fastboot mode whenever I plug in my phone my computer doesn't even bat an eye, and my phone just says it's waiting for a data cable connection. Windows will register it after a while as a "code 43: Windows has stopped this device because it has reported problems" after a while but I still wasn't able to get the right drivers to register the device. Doesn't even show up in lsusb in linux.
Wondering now if maybe when the device was alive I forgot to enable adb debugging first or maybe it doesn't register because it was set to charge only in the usb mode setting. Is there a way to change those settings in recovery like through the terminal? I would love to hear any possible solutions, I've been googling and search xda all over the place so any insight would be really appreciated.
Fortunately I had an extra shamu (with a very cracked screen) left over that I switched to in the mean time, but I'd like to get my old phone back in working order if possible! Any help or insight is appreciated!
gunha said:
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
Click to expand...
Click to collapse
You even made more errors. You don't seem to read properly. Franco does only support shamu up to nougat.
- Did you install the latest USB drivers and latest platform tools (adb, fastboot ...)
- Did you boot you phone into bootloader when you tried to connect?
Yup! I installed drivers from Google when I downloaded the platform-tools. I put my phone in bootloader mode when using fastboot, and my phone never indicated 'USB transfer cable connected' it just said 'connect usb.' also fastboot just said waiting for devices when I tried doing a getvar all....
try it on another laptop, try a new usb cable...you seem to have done everything right
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
gunha said:
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
Click to expand...
Click to collapse
Could be the cable. But the USB port could also be the cause. The simplest solution could be that the port is just full of dust. In that case, cleaning will help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
IF you still have access to TWRP, you can move your zips on an usb drive and connect it via otg and mount in TWRP and flash from the USB drive. Might help.
I've unlocked successfully my Mi 9 Lite and installed TWRP and then Lineage 16.0. It worked well for some weeks, but now I cannot get any connection via USB to a computer. I've tried Windows and Linux machines, tried different cables and connected the phone directly to the PC without any USB-Hub. The phone only shows that it is charging, but doesn't display the message to select the connection-type.
First I thought it was only a setting, which I changed, but one thing worries me. Even when booted into fastboot, "fastboot devices" didn't show anything.
did you try a different cable?
Did USB work at any time after you flashed TWRP? It's possible you somehow did something wrong and messed up the USB driver.
As a last resort, you can try flashing stock ROM and start over fresh.
I don't know what I did, but USB is working again.
I think that the problem was the silicone-case. It prevents that some USB-C-plugs will not have full contact. The original USB-plug is small enough to fit in the cutout of the silicone case.
Hello Everyone, so 2 days ago i hard bricked my MI 8 with flashing an eu rom over global mi 8 rom with twrp then when i rebooted the phone it stuck at mi logo so i tried to goto recovery mode again but nothing happens when i press power + volume up its just mi logo and i tried to go to fastboot mode but not luck i get a black screen....................so i decided to connect it to a computer but no signs of anything(not detected).....so i searched google a little and i found a solution wich envolved disassembling the phone the method called EDL method with test point,,,,,,,so i opened my phone with my friends and tried to do the test points,,,when i joined the testpoints and then connecting the phone to pc.....nothing happened.....it should detect the phone but nothing happens.....please help guys!!!
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone ?
mi_guel said:
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone
Click to expand...
Click to collapse
I have been trying....but no luck till now:crying::crying::crying:
alandxaled said:
I have been trying....but no luck till now:crying::crying::crying:
Click to expand...
Click to collapse
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
tsongming said:
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
Click to expand...
Click to collapse
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
alandxaled said:
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
Click to expand...
Click to collapse
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
tsongming said:
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
Click to expand...
Click to collapse
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
alandxaled said:
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
Click to expand...
Click to collapse
The EU rom does not lock the bootloader, the developers actually removed the bit of code that will allow MiFlash to lock the bootloader. Whenever leaving or returning to Miui, storage must be formatted.
The problem with these custom roms for the Mi8 is that These mi8 developers do not work together ( like most do, on other threads) These developers are always fighting and arguing and accusing each other of stealing their code, while they do it themselves and they all have their own way of doing things. Ideally every rom should use the same device tree, firmware and vendor...The basics! But no, everyone does things differently.
I would suspect that your phone bricked due to firmware encryption or just corruption. Even though it seems that it can't be fixed, you will surely be able to fix it eventually.
Many people were eventually able to solve this exact issue in the past with success. so start with the basics., and dont give up when or if it fails, just try again on a different device, and be sure to disable Windows defender. Because it's possible you could have your computer setup in a way that it will make this process harder to resolve, temporarily disable the antivirus and firewall etc.
Download the All in One tool: https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807 If it gets flagged, and completely disabled. then your computer is helping contribute to this issue.
If you can successfully install and open the tool, use it to update adb and android drivers and to apply system wide adb access. Next manually setup the phone , even if it claims to not see a fastboot device. and attempted to remove encryption. if this fails find a Linux machine to complete these tasks.
See if you can leave EDL, by pressing and holding the power and volume down. >>>>> Even if you dont see the fastboot screen the computer may see the phone in fastboot.
I definitely believe that you will have a easier path to getting this issue resolved sooner by using linux. If you can "format" ( not wipe) user data, install TWRP and root the rest will obviously be easy.
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
Boiisxu said:
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
Click to expand...
Click to collapse
He didn't format user data, or the file was somehow corrupted