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.
Hey gang. Wondering if you can help me with a strange issue I've got. I can't seem to connect my phone to my computer via USB. Wondering if anyone could help determine if there's a possibility of repair or not.
==Possibly relevant info==
Samsung Vibrant
Android 2.2 Froyo
Kernel version: 2.6.32.9
Build number: FROYO.UVKB5
==End relevant info==
So, my USB is acting up. Has been for the last few months, where although it charges when I plug into a computer, it's not connecting to allow data transfer. I haven't been too terribly worried, this happened before then cured itself when I did a factory reset. The thing that usually triggered it was when I tried connecting to my linux box in media player mode. The phone would just kinda lock up, I'd have to restart it and then USB wouldn't connect. But after doing the factory reset it was fine the first time. THIS time however, since I'd just left it stock now I'm itching to flash a custom rom but even though I've wiped the whole stupid phone totally clean, it still won't connect. I'm trying to follow a method on an article on dkszone.net called "Bypass E - Signature Verification Fail Issue On Vibrant Android 2.2".
So it seems I need USB for the debug mode.
What I think my main problem is, and where I need some help, is that I had purchased a super cheapwad USB car charger off of amazon for like 35 cents. Every time I connected to it, my phone would ask me if I wanted to connect using kies, media player mode, or data storage mode. I thought it was annoying but didn't really think it would harm anything. But now that I'm thinking about it, it's probably been pumping 5v into each pin on the USB port, whereas the USB functionality uses probably 3.3v, and I'm afraid I cooked something.
The random part here though is that about 5% of the time it does (sortof) connect. It brings up the USB options when I want to connect, brings up the icon saying it's using debug mode, etc. But my machine just reports that it didn't recognize the USB device. So, I'm thinking it's on the fritz, but figured I'd check here to see if I could possibly find a ray of hope.
Scooterx3 said:
So it seems I need USB for the debug mode.
Click to expand...
Click to collapse
You can use ADB over tcpip. There's many a free widget to enable it on google play or Do it manually
Thanks for that, I had been wondering if there wasn't a way to do that over wifi. My issue is that sadly I haven't even rooted the phone. ADB over WiFi requires root, whether I do it manually or use one of those super sweet apps.
So anyways, guess what?
My brother in law has the same phone I do, and I grabbed his phone one day and plugged it into my computers and had the same problem as with my own, and I know he hadn't plugged into the same charger I had, hadn't tried the media mode on Linux like I had (which were what I thought were the big contributing factors). SO, I kept digging, found that I hadn't quite yet cleaned it properly. I'd tried my best to clean it but until I swabbed it well with some rubbing alcohol it wasn't as clean as it should've been.
Long story short, I'm backing everything up so I can start flashing roms.
Moral: just clean the dang thing really well
I have a TF101 that's seemingly dead after being dropped. Currently, it does not power on. When plugged in with the ac charger, it shows no sign of charging, i.e., no light of any kind - amber, green or otherwise. I assume the mainboard has gone south.
When I connect it to my laptop, however, Windows 7 gives a chime and recognizes it as an MTP device, and even lists it as a TF101 in device manager. Linux also acknowledges that much. I can pretty much browse and access the content of the internal SD card like an external HD. Holding the power button long enough will unmount the device in either OS, which suggests that the device has turned itself off, and thus still responding to physical commands, or functioning on some level.
So it appears dead but not really. Being totally unfamiliar with this model, I'm not sure what possibilities the current state of affairs might indicate insofar as the device's vitality. Any input as to what this means is greatly appreciated.
If is it determined that the mainboard is done for, can anyone point me to a source for a replacement? If this kind of info solicitation is proscribed by regulation, my apology. Thank you.
My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.
Lethe6 said:
My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.
Click to expand...
Click to collapse
On second thought, I'm not too keen on replacing the MB just yet. Cracking the thing open is no big deal. I am dexterous enough. However, I am more intrigued by what is possibly going on.
If you guessed right, and transferring PC knowledge to this, the board would have a video chip integrated, with the other part consisting of an inverter and the LCD. If the integrated video circuit is dead, then connecting the device via HDMI to a TV would show nothing. If the device shows up, for instance, it's just the display part from the inverter on and so forth.
But I'm hesitant to go down that route. If it's the video part, then I should be able to do everything else like putting it in APX Mode, or flashing as with a normal device. Unfortunately, my computer never registered such activities; the tablet does not respond beyond the symptoms I described above.
As a matter of fact, I'd entertain any mad proposal on what should be tried on the thing at this point, just for the fun of it. I stand to lose little. So you can use your imagination and shoot some crazy ideas my way, and we'll see what.
So you tried with HDMI and it didn't work? You're right about APX though unless you're missing the drivers.. so maybe there really is some damage to the board. Sadly I don't have any crazy/mad suggestions at this point
My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.
Mike_NZ said:
My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.
Click to expand...
Click to collapse
Hey I totally agree that killing it may be the only option right now. And I don't mind that, just that I'd prefer the scalpel to the cleaver, and doing it in such a way that I would learn something about it that may be of benefit to me and incidentally, to others. I did open the thing, and you're again right, people have run into this problem of the LCD cable being jarred loose on impact from Asia to the Western Hemisphere to Eastern Europe. But it's not that, as I did unseat and reseat the cable on both ends, for naught.
As to the APX drivers, I did try both Easy Flasher and PERI 0.4. They act as if they finish the job. However, the tablet remains consistently inert. Lethe6, am I missing something here? How do you tell if the APX drivers are missing? Normally Windows would show the USB device as in APX mode right? Mine did not do that. When I tried to update the driver in Device Manager, Windows refused to do it claiming it was not necessary. Is there a way to force-install the drivers just to see?
Oh well, I'd just let the issue hang at this point and see what else comes this way.
Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?
Lethe6 said:
Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?
Click to expand...
Click to collapse
I never had the chance to try the HDMI output. Still waiting for the adapter to arrive. Ebay can be a pain during holiday season. But I'd sure to report the result. When I plugged the thing in, Win recognized it as an MTP device and proceeded to install drivers automatically. After which it showed in Device Manager as TF-101. So apparently the drivers are correct, though they dated back to 2006!!?? However, with other devices like the Acer A500, the USB device symbol normally would appear at the right bottom bar with the designation "APX device." With this thing, nothing - not even the icon. What's your thought on this?
I don't have any other devices that I can boot into APX (HTC won't tell anyone and my other tablet is a craplet, have to ADB on the live FS, which is awesome lol) so I can't compare here, but have you tried these drivers for APX? It's been a while but I seem to remember needing special drivers for APX. The device had a weird name.. like a bunch of numbers and letters... haven't used it since easyflasher though.
When I plug it in APX the device is called "NVIDIA USB Boot-recovery driver for mobile devices" and it's dated 1/31/2011.
When I plug it in Rogue Recovery the device is called "Asus Android MTP Device" dated 7/17/2012.
When I plug it in booted to 4.0.3 the device is called "Transformer TF101" dated 7/17/2012.
So I'm guessing yours never enters APX or has the wrong drivers? Maybe try installing the ASUS Sync software? Not sure but it may bring newer drivers...
I assume you're doing all this undocked as well?
Hello people,
so a few days ago I dropped my Galaxy S5 and the screen is now black, I can't use it. I want to try to save the data, but it's not as easy as plug in and transfer, since I have a password that I can't unlock. Using a screen mirroring program is also out of question, because I had USB Debugging disabled before I dropped it.
My next thought was to enable USB debugging with the help of adb, but that didn't work, since adb sees my device as "unauthorized". It still shows up as "Samsung Android ADB Interface" up in the Windows Device Manager.
So my next thought was to flash a custom recovery such as CWM via Odin (my phone doesn't have to be rooted for that, right?). That way I could use the volume keys to navigate through recovery mode once I enter it. All I would have to do is look at screenshots online and count how many times I press the volume buttons to know when to hit enter since the sceen doesn't work.
Would that even be helpful? I really hope that someone can help me or at least tell me there is no possible way to recover the files so I can sleep in peace. I've been trying so much, but all I find is more problems. I even had to use the Samsung 300K tool to enter Download mode, since that didn't work at one point. And I did that to use Dr. Fone's Android Lock Screen Remover which didn't remove my password. So that was 50 dollars well spent.
Looking forward to any kind of help, really desperate right now!
i dont think you can enable usb debugging from outside of the GUI. Can you use one of those MHL devices to get the display output to something? Perhaps the digitizer will still recognize touch input and let you turn it on from there.
youdoofus said:
i dont think you can enable usb debugging from outside of the GUI. Can you use one of those MHL devices to get the display output to something? Perhaps the digitizer will still recognize touch input and let you turn it on from there.
Click to expand...
Click to collapse
That's a pretty good idea! Looks like I haven't tried everything after all. I'll take a look if I the local electric market has some sort of adapter or is there anything I have to take into consideration? I am not familiar with the term MHL...
zakuani said:
That's a pretty good idea! Looks like I haven't tried everything after all. I'll take a look if I the local electric market has some sort of adapter or is there anything I have to take into consideration? I am not familiar with the term MHL...
Click to expand...
Click to collapse
nothing else really to take into consideration, just hope it works for ya
https://images-na.ssl-images-amazon.com/images/I/413PWcLXQHL._SY300_.jpg
Phone fell out of my pocket and got run over. Screen is completely black and the digitizer is done as well. If I connect it to my PC, it comes right up, but I have no way to enable USB file transfer mode so I can't "see" the SD card or internal memory. I tried to use [email protected] with Android Control, but it appears USB Debugging is turned off on the phone as ADB tells me the device is "unauthorized" and [email protected] gives me a "Rejected" status when it connects with the phone. (Yes, I did remove the ADB keys from my PC's ./user/.android folder and tried again)
Recovery is stock so no ADB access to open a shell and tweak anything. I haven't run across an ADB enabled recovery that I can install on this unlocked bootloader. (I can get into download mode and Odin recognizes the phone.) so I thought I'd try the "simple" route.
I bought an MHL adapter and an OTG cable thinking I could use a spare monitor and a mouse to turn on USB debugging or, at a minimum, turn on USB file transfer so I can get my data off the phone. I connected everything up and I can see the display, but mouse movement isn't being passed through the MHL cable assembly. If I plug the OTG cable directly into the phone, the phone does react to mouse movement and clicks and I can get lucky and launch apps, but I can't see WTH I'm doing. The odds of me turning on USB debugging like this are slim.
Anyone know of an MHL adapter that will allow "piggybacking" a USB mouse or an ADB enabled recovery I can flash to the phone? Maybe some uber-secret method to turn on USB debugging without access via ADB?
(Skiddz) said:
Phone fell out of my pocket and got run over. Screen is completely black and the digitizer is done as well...
Click to expand...
Click to collapse
I don't have this device but, I believe that one or both of the following threads may be helpful for what you need and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=2786395
https://forum.xda-developers.com/showthread.php?t=3607259
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, I believe that one or both of the following threads may be helpful for what you need and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=2786395
Click to expand...
Click to collapse
Yep, have all this working. Replacement phone works so my config is correct. The issue is USB debugging got turned off somehow. If I can get in via ADB, I can tweak the files I need to turn it back on. Or, I can find a MHL/OTG combo that works and just turn it on via the screen. Hell, if I could view the ADB key on the phone, I'd modify that file on my PC and it'd probably work.
https://forum.xda-developers.com/showthread.php?t=3607259
Click to expand...
Click to collapse
Read this one as well. I'm not sure what all gets nuked in the process nor have I researched ADB enabled ROMs. I have 2 files I *need* to get off the phone before I send it back. If I had local copies, I wouldn't sweat it and I'd boot into recovery and since I'm familiar with the order of the menus in there, I can probably do a factory restore. Unfortunately, the 2 files I need were updated/created while I was doing the errands that resulted in the broken screen.
(Skiddz) said:
Yep, have all this working...
Click to expand...
Click to collapse
If you are unable to obtain any member guidance, within any of those threads, the only other thread, that I can point you to, is the following Q&A thread that's specific for all S5 Variants.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Looks like it should be a cable with 11-pin connector.
Something like this: https://www.ebay.com/itm/252931732046
bbsc said:
Looks like it should be a cable with 11-pin connector.
Something like this: https://www.ebay.com/itm/252931732046
Click to expand...
Click to collapse
Yeah, I've seen a bunch of those, but have read several reviews that state it does not work with the S5. I wish I could find one locally just to try it out and if it doesn't work, I can return it without too much hassle.
Just spent almost an hour on the phone with Verizon and Samsung. The 2nd tier person at Verizon said that if the phone was still activated, they *might* be able to get in remotely and tweak the USB Debugging setting for me. I would have to acknowledge the request on the screen, but that may have been doable via blind mouse clicks after seeing where the dialogue was located on the display. Unfortunately, the phone was already deactivated and without a working digitizer, I would not have been able to temporarily reactivate it.
Samsung was slightly better than useless. I had to explain several times, to two different people, the specifics of my situation and they couldn't seem to grasp the idea that both the display and the digitizer were dead and all I was looking for was a way to get MHL and OTG working at the same time. That concept seemed completely foreign to them and they couldn't tell me if the dock they manufactured for the S5 would do what I wanted. The capper was the last person I spoke to all of a sudden said, "Thank you. Have a nice day." and hung up while I was asking a question.
I called Asurion again to see if I could send the replacement phone back (Because the sound quality is so bad it's almost useless. Even the Samsung Advanced Support guy said the quality on his end was crappy.) and just get this screen replaced. They told me "That service is not available in your area (I'm in a city of approximately 1.3 million - surely they'd have a vendor here?) and "we don't replace the digitizer, only the glass." When I asked, "How is that possible when the glass, the LCD and the digitizer are all one unit (At least I've not seen the separate components in my searches) that you can replace the glass?" The response was a seemingly scripted, "We don't replace the digitizer." When I asked if I could just send this replacement back and replace the screen myself, they said the phone would no longer be insured. Same as if I had a "professional" swap it out.
At this point, it appears I'm dead in the water. I'm still going to research the feasibility of cobbling my own cable(s) together before I have to return this phone. This seems so simple to solve, but it's proving to be an exercise in frustration.
Having a little success in "driving" the phone now with the use of an MHL adapter and some swapping of MHL and OTG cables and a keyboard. I've verified USB debugging *IS* enabled, turned it off, revoked previous privs, turned developer options off, rebooted the phone, turned developer options and USB debugging back on.
I installed the Samsung USB drivers on my notebook and installed Android Control and [email protected] and tried again. Still getting an unauthorized response from ADB with a request to check the screen for messages. Unfortunately, as soon as I unplug the USB cable from the phone to plug in the MHL adapter, any message that may have been there disappears. I did this same thing on my replacement phone and after a couple tries, I got the Authorization message and was able to get that one "talking" again.
At some point I had installed a screen mirroring app on the old phone and managed to get WiFi working with some blind mouse clicks and got the mirroring working with a keyboard plugged in. It's VERY slow, but I was able to turn on BlueTooth as well. I ran out of time for the trial version of the mirroring app and can't seem to make it work again so....
I'm off to buy a BT keyboard and mouse. The plan is to try and sideload Samsung Smart Switch, use the BT KB/Mouse to "drive" and the MHL adapter to "see" and transfer data that way. Alternately, if I can get the screen mirroring working with BT KB for control, I could, in theory, reauthorize the USB stuff.
Alternately, what's the trick to making ADB work via TCPIP? I've been reading a few threads about it and actually got a brief response (Still unauthorized) early this morning (0230-ish) but have been unable to repeat that. Trying with my new phone ADB tells me it can't "see" any devices and "unable to connect to :5555"
Found a thread on Stack Overflow that mentions adbd insecure needing to be disabled, but I have no idea where that might be done.
Continuing from other thread...
(Skiddz) said:
If I could get an ADB shell up, I can turn on USB debugging *and* copy my key to the phone, but I've got no ADB ability in recovery mode..
Click to expand...
Click to collapse
And here is a chicken and egg. For you need USB debugging activated in order to provide you with an ADB shell. At least as I understand it.
Smart Switch is already installed, but I can't access the confirmation dialogue(s). If I can get the thing talking to the PC, I'm golden. I can pull my data and then do a factory reset.
Click to expand...
Click to collapse
That's strange. I managed to get it working on my Core Prime with a dead screen. Well broken enough. With no OTG support. And I wasn't aware of any dialogue on screen. I loaded up Switch in Windows and it communicated with Switch on the mobile fine AFAICT.
I can the phone recognized by ODIN and wouldn't mind attempting to flash something if it'll help. At this point, I'm considering this pretty much a lost cause so if something gets jacked, I don't care.
Click to expand...
Click to collapse
If your phone has a supported custom recovery then you have a chance.
Was able to recover an ADB key file pair from Saturday afternoon's initial attempt to get in to the phone. Still no joy. However! I *was* able to drive through the settings menus with a keyboard. USB debugging IS on and I was able to revoke USB debugging Authorizations
Click to expand...
Click to collapse
This started off well but if your phone had a list of keys already, even if you didn't know it is, then revoking the keys pulls rug from under your feet. So to speak. However, if you can satisfy the dialogue to authorise a new computer, then that's no problem and your in!
Am I on the right track with revoking authorizations? Any way to make the phone think I've never "touched" it with ADB? Again, the new phone connected right up with no input required from me.
Click to expand...
Click to collapse
I wouldn't have done that given it freshens the slate. But if you wanted to clear it to a near untouched state that is the way to do it. Strange the new phone was easy that way. In that case it would be a good idea to clear it if the old one acts the same.
Here is my story about trying to get USB debugging working:
https://forum.xda-developers.com/ga...how-recover-data-core-prime-sm-g360g-t3681433
Here is a guide I wrote from my story detailing how I hacked my adb key in to authorise my computer for USB debugging:
https://forum.xda-developers.com/android/help/guide-modfying-cf-autoroot-kit-to-t3725596
Now this details what's involved but my phone was fully unsupported by everything but the CFAR kit. Which I needed to hack. You shouldn't need to go to such measures. Just need a recovery with ADB enabled.
Hypexed said:
Continuing from other thread...
And here is a chicken and egg. For you need USB debugging activated in order to provide you with an ADB shell. At least as I understand it.
Click to expand...
Click to collapse
USB debugging *is* on. I was able to verify that once I figured out how to drive "blind" with a keyboard. I was able to turn it off, turn off debugging options, reboot, turn debugging options back on, then turn on USB debugging.
That's strange. I managed to get it working on my Core Prime with a dead screen. Well broken enough. With no OTG support. And I wasn't aware of any dialogue on screen. I loaded up Switch in Windows and it communicated with Switch on the mobile fine AFAICT.
Click to expand...
Click to collapse
I'll have to try again but when I used Switch to move my wife's data from her Droid Mini to an S5, there was a confirmation dialogue on the Mini.
If your phone has a supported custom recovery then you have a chance.
Click to expand...
Click to collapse
G900V. Locked bootloader (Thanks Verizon) and I haven't found a custom recovery I can install without rooting.
This started off well but if your phone had a list of keys already, even if you didn't know it is, then revoking the keys pulls rug from under your feet. So to speak. However, if you can satisfy the dialogue to authorise a new computer, then that's no problem and your in!
Click to expand...
Click to collapse
I was getting the "unauthorized" status of the device via ADB and had no way to compare keys. I revoked keys so I had a known starting point. Yes, if I can get to the dialogue to confirm the access, I'm golden. Going to try the BT keyboard/Mouse and screen mirroring this evening when I'm done for the day. Even if I get Switch to start talking and get my data moved over, I'm going to figure out the ADB thing - it's become personal.
(Skiddz) said:
USB debugging *is* on. I was able to verify that once I figured out how to drive "blind" with a keyboard. I was able to turn it off, turn off debugging options, reboot, turn debugging options back on, then turn on USB debugging.
Click to expand...
Click to collapse
Then you're half way there. Almost living on a prayer. And if you can do the above it should be a cinch to get over the line and get that computer authorised.
I'll have to try again but when I used Switch to move my wife's data from her Droid Mini to an S5, there was a confirmation dialogue on the Mini.
Click to expand...
Click to collapse
It may work different from a non-Samsung phone. I used Switch on Windows to back up data from my Samsung phone. It was able to do so without intervention on the phone. Well I didn't see any prompt on the phone. Since my screen was blank.
G900V. Locked bootloader (Thanks Verizon) and I haven't found a custom recovery I can install without rooting.
Click to expand...
Click to collapse
Aha. Well hopefully you can get it going without need of that. In my case my under supported phone wasn't locked.
I was getting the "unauthorized" status of the device via ADB and had no way to compare keys. I revoked keys so I had a known starting point. Yes, if I can get to the dialogue to confirm the access, I'm golden. Going to try the BT keyboard/Mouse and screen mirroring this evening when I'm done for the day. Even if I get Switch to start talking and get my data moved over, I'm going to figure out the ADB thing - it's become personal.
Click to expand...
Click to collapse
Haha. Yes I know what you mean. You can see by the links I posted how personal I got.
I managed to CF-AutoRoot my phone before I got USB debugging even close to on. Of course I still couldn't do much with a broken rooted phone since all actions needed acknowledgement on screen. Later when I finally broke in and got the authorisation I still didn't have root access from an adb shell since that needed the screen working.
I had AirDroid installed. So once USB debugging was working I could do screen mirroring right away. That was a reward in itself. But it was the darnedest thing. The time I got it up and working suddenly the screen started responding to touch which didn't work before. I could brush my finger across the screen and hear the waters. So I quickly backed up my data. The next day, the screen stopped detecting my touch again. As well as AirDroid being unable control input. It's stuck in the corner and I can't use the mirroring to echo any touch to the phone. Most bizarre! I backuped my data just in time.
I used Helium to do a non root backup even though it was rooted. Worked well. Needed the mirror to see on screen.
I'm in! I was able to use my MHL adapter and a mouse via OTG to get the trial version of Stream Screen Mirror going. Once I got that going, I was able to pair a BT mouse/keyboard and use an MHL adapter to "see". Out of "spite", I fired up Android Control and authorized ADB access and voila! Remote screen and control. Pretty slow, but it works.
Sideloaded Switch via SMB and got it transferring data. It's grinding along now but will likely be another hour or so.
Thanks to everyone for the help.
That's good you got it going. Well done, I knew you would get there. Now if only there was a better solution than all this fiddling around.
Hypexed said:
That's good you got it going. Well done, I knew you would get there. Now if only there was a better solution than all this fiddling around.
Click to expand...
Click to collapse
No kidding... I can't imagine someone without any technical knowledge being able to move their data over in this type of situation. Oh well, it was a nice learning experience. I got a BT keyboard and Mouse for use with my Rapsberry Pi and now have a solution for the next time.
Actually, I think I'm going to root this thing and avoid all the hassle in case this happens again.
I agree with you there!