Related
If you are having problems getting to download mode, Use the Stock Captivate Cable Only when trying to access Download mode!
Story:
I have struggled with 2 captivates now to get into download mode. I have read tons of arguments back and forth from people that say it is easy to get into download mode, and people who say that it is impossible with their phones.
Well, for some history...On my first captivate, I bricked it and it refused to go into download mode...PERIOD. I proceeded to exchange it(I was within my 30 days), and didn't think much more about it. Well, I installed Cognition 2.2 recently and in the process realized that my new phone would go into download mode just fine by doing the standard process of:
1)remove battery, sim, microsim
2)reinserting battery only
3)holding down both volume buttons
4)inserting usb cable
No problems right? Well, I ended up "bricking" my phone by accidentally deleting my framework-res.apk file(don't ask) and lo and behold, I suddenly could not get it to go back into download mode. I was really pissed at this point and spent all night trying everything all over again.
Well, I decided to give up for the night and go to bed. As I was laying in bed a thought crossed my mind. I had purchased a second usb cable(from ATT) to use with the captivate, and the one time that download mode had worked, I was using the standard captivate cable that came in the box. However, every time it wasn't working I was using my second USB cable. So I got up out of bed to try the stock cable and, lo and behold, it works flawlessly every time.
I would venture to guess that this is what the problem is with most everyone else that can not get their captivates to go into download mode. So, if you haven't tried it give it a shot. And certainly tell everyone you know to use the stock cable only.
I just want to reiterate that the spare cable that would NOT work was purchased from ATT and is the cable that they recommend you purchase as a spare. It wasn't like I got it from ebay or something.
Using a usb cable I got from ebay, monoprice, htc, motorola, and stock samsung cable, I was able to get into download mode everytime...
... also, shouldn't this be in general and not in development?
No USB Hubs or Extenders
RECOMMENDED: Use your stock USB cable that came with the phone.
IMPORTANT: Plug the USB cable into your computers native motherboard USB port (the back of your computer). Plugging the cable into USB switches, extenders or external ports, does not allow the phone to enter download mode correctly.
Aerimus said:
I just want to reiterate that the spare cable that would NOT work was purchased from ATT and is the cable that they recommend you purchase as a spare. It wasn't like I got it from ebay or something.
Click to expand...
Click to collapse
I can confirm, although i found this out a whilllllle ago, just didnt think much of it lol
Just so you know. I found that in some cases certain USB cables just will not work with some devices. This has to do with the quality of the cable. I would avoid overly thin or flat cables because they tend to be cheaply made and won't be able to provide a stable power flow. The shorter the cable the better.
shinji257 said:
The shorter the cable the better.
Click to expand...
Click to collapse
The cable he/I bought from AT&T is shorter the the cable that comes in the box, and doesnt work, so im not sure if shorter is better
kkeo said:
Using a usb cable I got from ebay, monoprice, htc, motorola, and stock samsung cable, I was able to get into download mode everytime...
... also, shouldn't this be in general and not in development?
Click to expand...
Click to collapse
I can recreate this over and over again. The reason I put this here and not in general is because I, like many others, have struggled over and over with odin, and people had the attitude of "it works every time, you're just doing something wrong." The reality is that you're trying to prove that I'm just "doing something wrong" because all your cables work. I can recreate this over and over again. What do you want me to do, make a video of it in order for you to believe that there is an actual issue?
I think it's important for people to see this when trying all the roms and mods that are in the development section. In fact, I think it would be REALLY helpful if designgears would add this to the "how to get to download mode" section on the Odin thread. I can't tell you the amount of hours I have spent trying to get into download mode. It is incredibly frustrating to do everything right, and have others telling you that you are not doing it right.
I searched google endlessly looking for a solution to get into download mode, and no where did I see this as a possible solution. Also, as an FYI, when I plug in the other cable, it just goes straight to the battery screen no matter what I press. I can hold down the power and volume buttons to go into recovery mode, but it's impossible to get to download mode.
I have plugged mine into a usb port in the front of my computer as well as in my monitor. I have never had a problem with download mode or anything else.
Aerimus said:
I can recreate this over and over again. The reason I put this here and not in general is because I, like many others, have struggled over and over with odin, and people had the attitude of "it works every time, you're just doing something wrong." The reality is that you're trying to prove that I'm just "doing something wrong" because all your cables work. I can recreate this over and over again. What do you want me to do, make a video of it in order for you to believe that there is an actual issue?
I think it's important for people to see this when trying all the roms and mods that are in the development section. In fact, I think it would be REALLY helpful if designgears would add this to the "how to get to download mode" section on the Odin thread. I can't tell you the amount of hours I have spent trying to get into download mode. It is incredibly frustrating to do everything right, and have others telling you that you are not doing it right.
I searched google endlessly looking for a solution to get into download mode, and no where did I see this as a possible solution. Also, as an FYI, when I plug in the other cable, it just goes straight to the battery screen no matter what I press. I can hold down the power and volume buttons to go into recovery mode, but it's impossible to get to download mode.
Click to expand...
Click to collapse
While this is good to know...It is quite possible you got a faulty second cable, and some of the cables that do come in the box are faulty as well..
It's always a good reminder to try changing out cables if your having an issues. Same for downloading different things that work for a-lot of people and not for you/me..same too for hooking into the back of the computer and bypassing the external hub....Sometimes you get lucky and find the problem right away..sometimes you don't....It's called a process of elimination...
FWIW..I've never trusted cheap ass cables..in anything. Never have..Never will..but..JSYK..expensive cables go bad from time to time too
Thanks for the reminder
Mac
jromney said:
RECOMMENDED: Use your stock USB cable that came with the phone.
IMPORTANT: Plug the USB cable into your computers native motherboard USB port (the back of your computer). Plugging the cable into USB switches, extenders or external ports, does not allow the phone to enter download mode correctly.
Click to expand...
Click to collapse
I use the external ports on the front of my case without a problem...
jromney said:
RECOMMENDED: Use your stock USB cable that came with the phone.
IMPORTANT: Plug the USB cable into your computers native motherboard USB port (the back of your computer). Plugging the cable into USB switches, extenders or external ports, does not allow the phone to enter download mode correctly.
Click to expand...
Click to collapse
I've also noticed that, on my PC at least, my front case USB ports don't always reliably work with this procedure. I've been plugging the USB cable since into the USB ports on the motherboard.
Mac11700 said:
While this is good to know...It is quite possible you got a faulty second cable, and some of the cables that do come in the box are faulty as well..
It's always a good reminder to try changing out cables if your having an issues. Same for downloading different things that work for a-lot of people and not for you/me..same too for hooking into the back of the computer and bypassing the external hub....Sometimes you get lucky and find the problem right away..sometimes you don't....It's called a process of elimination...
FWIW..I've never trusted cheap ass cables..in anything. Never have..Never will..but..JSYK..expensive cables go bad from time to time too
Thanks for the reminder
Mac
Click to expand...
Click to collapse
The thing that throws me off is that this cable works for EVERYTHING else. Data transfer, media syncing, recovery mode, charging, etc... There was never anything that would indicate any issue with the cable. I just want to make sure everyone knows this, because when I was struggling to get into download mode, I didn't see anyone suggest that it could be the cable, even though the cable worked for everything else.
OP - thanks for posting this! It is at least another thing to keep in mind when troubleshooting. I was actually considering getting another cable to keep at work.....
P.S. would we get in trouble for quoting Michael Scott's favorite joke in response to post #6? Yea, I know. Little too obvious right. I'll restrain. Already made myself chuckle anyways
terrigan said:
I've also noticed that, on my PC at least, my front case USB ports don't always reliably work with this procedure. I've been plugging the USB cable since into the USB ports on the motherboard.
Click to expand...
Click to collapse
Um.. not true - Although I did use the stock USB Cable - I was flashing the night away (trying to recover my bricked phone) on my Win7 box using a USB hub that had a few other devices hooked into it.
Never had an issue getting to D/L mode.. and it found the phone again and again and again and again.... (go on for infinity).
I think it has more to do with the hardware your connecting it to and how the USB drivers loaded (i.e. XP=****e) and what type of OS your running more than anything. I had terrible luck with my work's XP rig... but my Win7 x64 rig found the device while in d/l mode - found the drivers?!?! and I was good to go.
Although - it is always a good rule of thumb IF you can't get the device to recognize on your computer to use the original cable and hook to the best source of power for your USB which is the back of your computer.
So.. this isn't a [FIX] - just a good tip. If you can't get into D/L mode by holding the volume button and jamming in the USB or using ADB -> Reboot Download command.. your pretty much fux0red.
I need original USB cable
I just wanted to throw in my $0.02 I needed to use the original USB cable and a port directly on my motherboard. The usb cable I bought from newegg does not work with my MSI X58 motherboard and my capitavate. The original cable does not work if I use a front usb port on my Antec P183 case. Strangly an identical usb cable from newegg that I ordered at the same time does work with my work computer, Dell X38 motherboard.
Ive had the same problem... only way i get it to download mode is via Terminal:
su
reboot download
I really cant get it to work no other way :s
jromney said:
RECOMMENDED: Use your stock USB cable that came with the phone.
IMPORTANT: Plug the USB cable into your computers native motherboard USB port (the back of your computer). Plugging the cable into USB switches, extenders or external ports, does not allow the phone to enter download mode correctly.
Click to expand...
Click to collapse
honestly, i have my phone cord that came into the box, connected to an extender cable, that's connected into a usb port hub so i don't agree with what you're saying here
mine works every single time
This method has been known for some time now, reading really helps...
http://forum.xda-developers.com/showthread.php?t=731989
designgears said:
This method has been known for some time now, reading really helps...
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
I appreciate all your hard work on everything. I read through that post and tried to search it several times... Believe me, I spent hours pouring through the pages looking for something that would work.
No where did I see anyone say to make sure you were using the stock cable because other cables might not work? Feel free to correct me if I'm wrong...there are a lot of pages after all.
Furthermore...I'm sorry to be new to Android and to flashing roms, but we are all new at some point. No one is born an expert.
edit: I'm guessing you misunderstood the post? I wasn't posting about the method...just about the fact that many usb cables, including the micro usb cable that ATT sells, do not work for getting to download mode. If I'm wrong about what you were posting, feel free to correct me. If i'm correct, your post is quite ironic
The first captivate I had WOULD NOT GO INTO DOWNLOAD mode regardless of cable or usb port. I tried every port and every cable including the stock one that came with the phone.
The replacement captivate ALWAYS goes into download mode regardless of cable or port.
It's a tip and thank you for the. But if your phone is one of those that does not have 3 button recovery then it will likely not work with the 2 button download trick either.
USB debugging no longer activates on my phone. Activating it in settings/applications/development brings up the "Allow USB debugging?" permission window. However, no usb notifications appear, and the phone appears to be a dead device to any PC it is connected to.
This started when I accidently got into the download screen from the phone options popup. The display showed the yellow sign, android guy with shovel, and message warning not to turn target off. Phone was not connected to anything at the time.
Searching found a couple of threads indicating that a battery pull was safe to get out of it. Did same.
Since then, usb debugging (or usb anything) has been dead on this phone. Other methods of usb access (thru usb settings) have no effect either.
Tried the following...
(1) restore to my last backup rom.
(2) numerous reboots and battery pulls.
(3) mount/unmount sd card in cwm recovery
(4) clear caches
(5) changed pc's and cables (all worked before)
(6) reinstalled usb drivers on pc (worked before, didn't expect it to help since issue is at phone end)
As you can see, I'm running out of sticks to poke the horse with. Does anyone have any ideas?
Update: new kernel didn't help, either
Update2:
(a) Can't do a restore via odin, which won't detect the phone.
(b) Updated my adb (which I don't use much). adb devices command will not detect the phone via usb.
(c) Installed adbWireless which allowed me to push a stock nandroid backup to the phone. Restored that, usb is still dead.
(d) Restored back to my superdark rom, usb is still dead.
Head scratch: I'd blame hardware except that it seems to be between the settings and execution. If it was purely hardware, I'd expect to see the usual usb notifications. Regardless, it looks like I'll have to revert back to stock and let Verizon figure it out.
Update3:
(a) switched to the new AOSP rom. Nice, but no usb.
(b) switched back to superdark since I like my speakerphone and the AOSP seems to be on hold. Still no usb.
Resolution:
My apologies for not posting a resolution. My bad. After the first few days the post kind of fell off the radar and I stopped checking.
Short version...dirty usb port.
Details...after a week or so, I saw the usb icon flash in the notification bar for a few seconds when I plugged it in for a recharge. Hadn't seen that in a week, hope springs eternal!
A thorough cleaning of the usb port using a paper swab dampened with alcohol restored usb functionality. Not much dirt came out on the paper, but it must have been enough to probably bridge the contacts somehow.
At present the phone is fully functional. The original Verizon cable seems to be a little wonky. I have an aftermarket cable that works fine. It may be that the aftermarket cable did some physical harm to the contacts in the port, or the original cable is going bad (I had something very similar happen on my Omnia). Not sure.
I now use the original verizon cable only for charging at work and use the aftermarket cable for usb connecting at home.
Bottom line...if your usb goes dead as described in the op, carefully clean the port.
My thanks to all who responded...
Download screen shouldn't have harmed you.
You probably are well aware of this, but sometimes it's the simplest solution: Is your usb cable unplugged when you are trying to turn on USB debugging? It will not let you if you are plugged into a pc or mounted for some other reason. Make sure your file manager and any other rogue app is closed. Again, it does sound like you have tried all of this, just giving my best shot ar an answer.
Other then that... Has anyone else had this problem? I haven't seen it in this forum before.
The most general solution to any issue on these fascinates is to undo whatever you did to break it, it's just difficult sometimes to isolate what that event was.
Swyped w/ XDA App. When in doubt, mumble.
Thanks for the reply.
USB is unplugged when turning on debugging. I've also tried turning the phone on with usb plugged in.
The last thing I had done (before accidently activating the download screen) was to install SiMi Folder Widget. Needless to say, it went away with the rom restore.
Also used ATK to kill running processes before turning on usb debugging. Also verified that I still have root.
I've buggered the phone up before but have always been able to figure out a way back (with help from forum searches). This one's got me stuck.
Tonight I'll try to figure out if it can be odin'd back to stock and rebuild from there.
Again, thanks. All suggestions/advice are appreciated.
See op for steps taken to (unsuccessfully) solve this.
Can anyone advise how I can flash back to stock DI01 without using odin, since it won't detect the phone? I can push files to the phone via adbWireless but that's about it.
thanx in advance...
I dont know if you fixed it or not, but here is a stupid question. Are you using the cable that came with your phone? I have several cables that will only charge my phone and only the stock one enables data transfer. Hope this helps. Good luck
Sent from my SCH-I500 using XDA App
Have you tried a factory data reset?
Sent from my SCH-I500 using XDA App
Did this ever get resolved? I hate to see an open issue die like this.
My apologies for not posting a resolution. My bad. After the first few days the post kind of fell off the radar and I stopped checking.
Short version...dirty usb port.
Details...after a week or so, I saw the usb icon flash in the notification bar for a few seconds when I plugged it in for a recharge. Hadn't seen that in a week, hope springs eternal!
A thorough cleaning of the usb port using a paper swab dampened with alcohol restored usb functionality. Not much dirt came out on the paper, but it must have been enough to probably bridge the contacts somehow.
At present the phone is fully functional. The original Verizon cable seems to be a little wonky. I have an aftermarket cable that works fine. It may be that the aftermarket cable did some physical harm to the contacts in the port, or the original cable is going bad (I had something very similar happen on my Omnia). Not sure.
I now use the original verizon cable only for charging at work and use the aftermarket cable for usb connecting at home.
Bottom line...if your usb goes dead as described in the op, carefully clean the port.
My thanks to all who responded...
This may be my problem! I'm having the same similar effects. Although mine randomly shows the symbol but also says my usb is connected when it does. I've been trying to solve this for 2 weeks now! I hope this is the solution.
Sent from my SCH-I500 using Tapatalk
common problem
This must be a common problem because I've had the same issue. switched cables and viola, all good.
My exact problem solved:
USB debugging activated on phone but computer did not detect it at all, nothing what so ever. Not even on dial-up mode, or download-Odin (yellow triangle).
Drivers installed (Fascinated and Nexus for the hell of it).
Tried to ADB my into it both from windows 7 and MAC OS-X.
Hell I even tried a different USB cord.
I would get the USB debug icon in the status bar only when on windows7 machine.
I cleaned the phones USB port with the alcohol damped paper towel/tooth pick and the **** worked, first time.
Man I gotta thanks God for this site. I been ****ing with for 2 days.
Then this lil SOB acted as if nothing ever happen. I wanted to beat the hell out the lil ****er. But we are back friends now.
Thanks dude. This **** needs publicized more. I went through a few links before I found this.
I would and tell people to use something non-metallic and removed the battery beforehand. I did just to be safe.
When I plug my wife's phone in, most of the time it does not even recognize that anything is plugged in at all, but the phone charges. Sometimes in device manager the phone comes up with a yellow exclamation point and the error
Windows has stopped this device because it has reported problems. (Code 43)
I installed the Android SDK and USB driver.
I installed the Samsung Driver from the site.
I thought possibly it was a software issue, so I was going to try to set the phone to factory settings. When I go into recovery, there is an Android logo with a red exclamation point, then eventually it boots back into Android with no change.
I manually added the driver into android_winusb.inf as I saw on another post here, but no matter what it is not picking it up.
I want to just be able to connect so I can root the phone and put a ROM on it. The phone is pretty hosed and slow. Any suggestions?
I had this at one point. It was the device, I had to get a replacement.
Sent from my SCH-I815 using Tapatalk 2
esoh said:
I had this at one point. It was the device, I had to get a replacement.
Sent from my SCH-I815 using Tapatalk 2
Click to expand...
Click to collapse
Well I do have insurance on it, and I agree that is the easy way, but I really don't think the hardware is broken.
I mean it charges, so the USB port works. I think if I was able to reload Android from scratch onto it, it would work. However, every solution I see requires rooting and you can't root without USB. It is a frustrating catch 22. Any other possible solutions? If not, I guess we are screwed.
The most frustrating part is factory reset not working.
I am currently having similar problems like you, I have one USB port from memory card reader and on that port phone isn't even charging but a flash drive works without problems. On other ports (back of case and front) there is charging but computer can't recognize the device. Try uninstalling all phone related drivers or cleaning them with some sort of driver cleaner. Then reinstall driver, or let Windows update it automatically. Mine worked for a while, and in device manager it was recognized as Acer ADB.
EDIT: Hi, just to report reason of my problems, my USB cables started failing for no apparent reason, my original Samsung USB cable and one other no name have both failed. I'm currently using my old LG USB cable, wrapped up in insulating tape, but everything is working good. So try some other micro USB cable, it maybe the source of your problems.
Hello all!
I'm just guna say, this might get long winded so, TLDR, Nexus 7 has no OS, I can get into the boot loader, the only thing I can actually do is get into TWRP v2.8.01, computer doesn't recognize it, can't get it to even see a flash drive that I've formatted to Fat32, now what?
For those who want some background. I got my N7 refurbished from ebay, if that matters at all. First thing I did was update it to Kitkat and root it. Installed some apps and was happy with it for a few months. About a month or so ago it stopped connecting to the Google Play Store. I wasn't bothered by it too much. But as time goes on, I find new apps and would like to use them. But obviously can not.
So, just to be safe, I wrote down all the apps I still had on it just in case they didn't want to load back up. Did a factory reset, still couldn't connect. Looked online and cleared caches and stopped services. Still didn't work. When I went onto the GPS, heh, on my computer it said that I had no devices so that was a clue of some sort. I could still go onto Youtube and log in and use it just fine. Just nothing in the store. So I decided to try something else.
What that was was to clear all my data with TWRP. Went to put in my email and password, couldn't connect, tried another wifi connection, still no go. I was able to use it, but the Play Store still didn't want to play nice. So in a bit of, "rage" we'll call it. I formatted it and now I'm where I am now. With a tablet that won't boot, just sit at the Google logo for up to 5 mins, as long as I've let it sit there for anyway. I have downloaded the Nexus Root Kit and tried to use that, but my computer won't even see my N7 now. In the bootloader or TWRP. So I can't even get anything onto it now.
So, what now? Do I have a bricked tablet that won't do anything or is there something an Android Guru out there can help me with? I'd like to keep it. I mainly used it to read and for various videos.
I have posted on forums.androidcentral but after a week and almost 300 views, no one has made any comments. I'm sorry for my ignorance if I'm missing something.
Thanks! I shall be hoping for good news.
So, does ADB recognize your tablet or not when you type "fastboot devices"?
I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.
Waslow said:
I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.
Click to expand...
Click to collapse
Can you go into the bootloader? Did you install the right drivers?
I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?
Waslow said:
I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?
Click to expand...
Click to collapse
That is correct. Use this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
And if doesn't work check in device manager.
If it works flash the latest factory image and then you will be good to go
I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.
Waslow said:
I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.
Click to expand...
Click to collapse
Then try the driver manual in nexus root toolkit
I can follow the instructions, but that doesn't resolve the fact that my computer can't see the Nexus .
go into device manager and delete every single entry that suggests anything to do with a phone, tablet, google device, nexus device, ETC. if you dont do that first, this will probably not work.
once you delete every single entry in there, go to the top command bar and somewhere in those menus is an option to show disconnected devices. delete everything again as above.
now, does your tablet still charge on the AC plugged into the wall? does it still charge when plugged into the computer usb? drivers are NOT required for usb to supply power. if so, the usb connector is probably OK. if not, your usb connector may be toast.
next, connect to the computer. does windows show any device connected? if not, try a different usb cable. report your findings back.
Sorry for the late reply.
There is nothing in the device manager related to my Nexus, which is odd, it had entries for flash drives, a camera, and my phone. All of which were in the disconnected devices. I got rid of just for the sake of it. Nexus charges just fine, either from the wall or any of my usb ports. If there is no way to make ANY computer see my Nexus, is it safe to say it's bricked?
I do have a cousin who's fluent in Linux if that means anything. I know that Android is a flavor of it. Might work better if both devices speak the same language. Grasping for straws I know.
Again, thanks for the help fwayfarer, GtrCraft, and Fobos531!
If I am reading right, you did NOT try a new USB CABLE yet, did you?
Try a known good USB cable, what I mean by that is try a cable you KNOW works for data transfer on another device and report back.
Connecting it to a Linux machine isn't going to make any difference in my opinion.
I have 2 cables and they transfer things just fine with my phone and my Kindle. I just downloaded everything off of both things, and transferred them back. No issue with the cables. I just popped open my Nexus and it looks like the usb connector and ribbon are fine. I did wiggle them a little but to no avail.
Pull the battery cable, smash the power button for a few minutes, reconnect and try again. It won't recognize a USB thumb drive in bootloader or recovery to my knowledge, BTW. I noticed you mentioned it not seeing one.
I unplugged the battery, hit the power switch for a while, plugged the battery back in, plugged the usb back in, nothing. Still nothing. I had read before that you can put the version of android you wanted on a flash drive. With an otg cable you could use that to update/install what you wanted.
You're probably right, I haven't tried using one in recovery for a long time. You didn't change the battery or anything recently did you?
Nope, haven't replaced anything in the Nexus. The only thing that I could think of that could be wrong is the usb connector. But for it to "fail" at the same time I formatted everything, too much of a coincidence.
Over a week bump
I ran into a similar problem about a year ago. Unless your tablet is connected to the computer you will not see it show up it the windows device manager. You should be able to connect your N7 to a work computer & it should go out for the drivers. If not, then you are Sol. You might have a blown main board.
The only thing my N7 does when I plug it in, is that it charges. That's the only thing I can get it to do. Well, this sucks. If I really have a bricked, or worse, tablet, it's still good for its screen and other bits.
Hey!
While I was calibrating my fingerprint, phone suddenly turned off and went to recovery with screen off.
I managed to reflash stock rom through fastboot and it boots to system fine, but the screen stays off and the front camera keeps trying to open while playing the MIUI camera sound (sometimes, while booting, the camera does manage to open once, kinda like it's calibrating). Some playing around with ADB and it seems that the SIM isn't recognized either.. antenna maybe?
I opened the phone up and checked everything, there's no visible issues with the electronics, however it could just be the inside of a cable that died?
Does anyone know what this could be? I noticed the screen, fingerprint reader and antenna are all connected to the same removable PCB, but the camera isn't so that's odd.
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
XDHx86 said:
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
Click to expand...
Click to collapse
It's a bit of a long one, so I didn't want to bother too much with the details if anyone knew what those specific issues could be caused by, here goes though:
I am on a Mi 9T bought on Amazon Italy in July 2019. I cannot comfortably send it to a repair center due to every authorized shop around here is just a drop-off point for Xiaomi RMA. I talked to them and, due to (>6 months old) glass damage to the screen and back of the phone, they intended to charge me way more than I can afford, as "solving issues covered by the warranty would require us to replace the accidentally damaged components"
As for what happened:
I was running LOS 17.1 with no issues for a few months. I went to unlock the phone and I heard the reboot vibration, which sent me to recovery (softbricked) but with no screen signal. I assumed it was just a software problem, so I flashed MIUI 12 (global, V12.0.7.0.QFJMIXM) to see what would happen.
As it completed, the phone rebooted itself, the MIUI logo popped up and it went to system (seemingly) without any issues.
I went through the initial wizard and played around with it. everything seemed fine and I even made sure the screen did work in recovery and fastboot. Later, when I went to setup the fingerprint reader, the screen went blank for half a second when I first touched it, and then the same screen death -> reboot to recovery.
The phone was softbricked again, though, this time, reinstalling MIUI didn't yield the same success. Now:
MIUI boots "normally" again
The screen isn't working at all
The front camera opens, as if it's calibrating, when system boots up
The front camera randomly tries to open again every now and then, failing to do so as if the motor is stuck, while MIUI plays the camera closing sound.
Meddling through ADB, the antenna doesn't seem to be working, but I can't be 100% sure due to the methods used
The power and volume buttons, speakers, and the charging light all work.
I have opened the phone up myself, thoroughly checked every cable, connection and PCB, but there is no sign of damage. I put it back together and the same issue continued.
My best guess is that something inside the fingerprint reader went bad and shorted something else.
What that something else is, I couldn't find out. Given the antenna, screen and FOD are all connected to the same little PCB which then runs a couple cables to the motherboard, I am now in the process of finding a couple replacement cables to see if that fixes anything.
As I mentioned before, repair centers are not an option due to the lack of anyone who's willing to help me for less than a good chunk of the price of the phone.
Interesting. So basically what happened is due to the initial soft brick and accordingly you flashed a global MIUI 12 ROM, which in return brought you to the second soft brick which caused some issues within the hardware of the device.
Now you're stuck with a faulty screen, a faulty camera and a faulty antenna.
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
I can't help you if you messed up your phone circuit since I have no knowledge about android hardware, however I can safely assume that what caused your issue isn't related to hardware.
I think the issue is caused by an incomplete flashing of a ROM (In this case MIUI 12 global) OR flashing a different variation from your device.
e.g. you flashed only the ROM, but didn't flash the other components of the ROM.
Needless to say, flashing a variation of the ROM that isn't meant for you device can be a disaster recipe.
I recommend flashing LOS again, since you can't go back on Xiaomi devices due to rollback protection.
XDHx86 said:
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
Click to expand...
Click to collapse
I understand why you'd think that and have seen people do similar stupid things, however I didn't watch any youtube video and know what I'm doing quite well.
I made sure I flashed the correct rom through fastboot to restore everything to stock. I did try to reflash LOS and whatever else (though it's kind of a pain with adb shell), but it doesn't fix the problem, sadly.
That's why I'm betting on a HW issue.
The fingerprint reader and everything else worked flawlessly in LOS for months, but it made the screen go blank and bricked the device in both LOS and fully functional, stock MIUI.
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
angometry said:
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
Click to expand...
Click to collapse
If the touch screen is dead then you can use mouse and OTG cable.
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one). Or you can use playstore on pc to download and install apps like (Screen stream over HTTP) on your device, just make sure your device is connected to the internet and you're signed in on your phone as well, you might have to type in the screen password if you have one.
angometry said:
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
Click to expand...
Click to collapse
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
All I can think of is:
Wiping dalvik cache, though you might have already done that.
Trying other custom ROMs from here.
You may try to get your device rollback index and installing a MIUI ROM that has index higher than it, and see if that works.
That is as far as I can help, unfortunately.
I have zero knowledge when it comes to hardware, so I can only help with software issues. If none of my solutions worked then sorry for wasting your time :/
XDHx86 said:
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one).
Click to expand...
Click to collapse
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
XDHx86 said:
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
Click to expand...
Click to collapse
Sorry, I didn't explain myself, I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
If I can get it on, I can then use things like scrcpy to get screen signal through USB.
Main problem with everything else is that the screen is 100% dead. Even with usb otg I don't know how I could possibly get through the setup wizard haha
angometry said:
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
Click to expand...
Click to collapse
I haven't tried it myself, however it should detect it as a second monitor. Give it a try the cable isn't costly at all anyway.
angometry said:
I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
Click to expand...
Click to collapse
TWRP has debugging mode on by default, however that strictly applies to recovery and fastboot modes only as debugging mode is pretty powerful and can cause security issues. So you better forget about it.
I saw one of my friends who owns an authorized service center use some cable connections to get the screen to display on another touch screen. If you have the capabilities and resources I recommed trying it, though don't mess too much with the motherboard.
Just a question though, can you confirm if the touch is working? If not then there's a chance - Although slight - that this is just a UI problem (Which is pretty common in MIUI ROMs for some reason). In that case deleting dalvik cache or completely reflashing the ROM might solve the issue.
I may not do much help but certainly someone there can help so it's better if you include "usb debugging" in the title and/or the tags. Like changing the title to "Enabling usb debugging without screen" or "Screen is dead, need help to flash ROM"
Using proper title and proper tags can get the right person to help.