Does anyone know where the uart is located on this device and how I can tap into it?
I need to do some kernel debugging and from the CM kernel commit log I can tell they enabled it in the kernel, but I simply can't find any documentation on where the physical connectors are located.
MrColdbird said:
Does anyone know where the uart is located on this device and how I can tap into it?
I need to do some kernel debugging and from the CM kernel commit log I can tell they enabled it in the kernel, but I simply can't find any documentation on where the physical connectors are located.
Click to expand...
Click to collapse
You get a serial port when you are flashing with qpst if thats of any help. When phone is turned off, you hold vol + and then insert usb cable and the phone will be in a modem diag flash mode something for like 5sec and if there hasnt been any activity from the connected pc then it will continue booting. Was quite a hassle to flash original zui through qpst I tell you but thats the only time ive seen a serial comport from the phone in device manager.
You might already know this and im sry if its a dumb answer.
While the Qualcomm Loader mode is technically a USB serial port, this is not what I'm searching for.
I talk about the kernel debugging serial port used for outputting kernel messages.
Related
Just ran into a problem which took me some time to solve. Thought I would share it to save other people some frustration.
After an adb reboot the i5800 got stuck in "modem" mode. i.e. android booted fine but gave a modem and a serial port over usb rather than adb. Reboots did not solve the problem.
The solution is to enter recovery screen:
reboot recovery
OR
press proper buttons to get into recovery mode
And then perform a reboot from there
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
miki.antena said:
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
Click to expand...
Click to collapse
Thanks so much for this!!!! After helping hack a friends build.prop to enable Apparatus compatibility in the Market, I found USB wasn't working properly anymore. Resetting changes in the phone didn't help (I had to do this via the phone terminal) although I at least managed to buy Apparatus before the sale ended.
After initially getting confused due to a lack of drivers and the occasional 'nH' showing up devices without drivers which made me think something was borked, I worked out from the VID & PID it was just the lack of drivers making (well I'm not sure why it did the 'nH' sometimes it got serial something instead), once I installed the drivers all was fine.
Except still mass storage wasn't showing and the Samsung connect manager didn't show up on my phone when I connected USB, nor did ADB work at all. In fact, it didn't even show up in the phone menu as debugging mode if I didn't start phone with it connected (or something like that). Funnily enough when I did get it the debugging to show up I did get the USB mass storage to show up in the phone, but it didn't help (it just unmounted the card which I think is all it ever does).
Anyway after a bit more fooling around I eventuall came across http://forum.xda-developers.com/showthread.php?t=1215103 and the stuff about modem and mkasick's post which sounded a lot like it could be my problem. The code for that Samsung phone didn't work so I searched for the 5800 and came across this giving me the right code. Sure enough UART (but not USB) was set to modem instead of PDA. I was unsure whether that was wrong but changed it anyway and yep that fixed it!
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times. In fact most of the stuff except install a superuser update has been more or less repeated. I guess it was just some strange rare occurence that it somehow got changed. I did have to reconnect the USB while working the first time, not sure why but ADB lost connection then I found couldn't connect. Perhaps that's somehow related. Now that I know what to do, it's trivial but very annoying when I didn't. I still don't get why Samsung decided to make the connect manager (my phone doesn't have that) only to have some hidden option where it can be set to modem or USB.
Partially because of this, I never got to get Tilestorm HD become compatible in time for the sale although my friend wasn't so interested in that. (Eventually I worked out using the THC Tattoo modded market which reports a fake resolution enables it. Well, I also modified the build.prop but I don't know if that was necessary. I wasn't able to do it solely by the build.prop. But it was way too late by then to buy Tilestorm HD cheap.)
Nil Einne said:
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times.
Click to expand...
Click to collapse
This may sound like crazy idea, but is your USB port/connector clean?
(The USB port allows for dozens of different phone functions when using very specific resistance between data pins.)
i bought a LG D802 32gb last night as i was using a 16 gb before i wanted to flash cloudy g3.. so i tried to install custome recovery twrp...
now i am in fast boot mode..
it says :
[880]fastboot mode started
[910]udc_start()
when i attach usb cable
[1100]-reset-
[1110]-portchange-
[1120]-reset-
[1130]-portchange-
[1140]-fastboot: processing commands
i tried holding volume + and and attaching the usb cable but no luck ... so now i have NO RECOVERY, NO DOWNLOAD MODE, AND MY WINDOWS PICKING UP MY PHONE AS "USB MODEM PHONE ADB PORT"
please help
I'm trying to connect to my device using QPST, but the device is not showing up in the COM ports. I've tried to delete all the usb devices related to the device in device manager but all to no avail. And none of the dial codes I'm using seem to be working. Only ones that work are those that start with "*#*#" and end with "#*#*". Only com port I get is the default COM1, to which there is no phone connected. The other problem is that the drivers I have doesnt seem to be working, I even had to install them by disabling hardware signing. Device is not detected in download or recovery mode either.
Processor is a MSM8212 and the mainboard is MSM8610.
I'm on windows 8.1
Your device is in regular mode... to access DM you HAVE to have it in DM mode.... so try EFSpro to switch your phone into DM mode or you will have to keep looking for a dial pad code. Some handsets allow sysfs to enable DM mode too. Have a look and do some research. Your QPST drivers should come from the manufacturer... ie I am using samsung drivers to use the DM port, not drivers from QPST.
s5 usb connect - device not recognized cant access secret menu *#0808#
can anyone give advice how to access menu *#0808# when I dial it trys to call the number not open menu
my usb is not work on s5
always says device not recognized but it charges perfect on connect
no one has advice?
Look for Samsung usb driver, it will open a Samsung Dev website, download and install the drivers. Of it's not working either, try on another USB port, another computer, another cable, another phone with the same steps above, of it's not recognizing it on all computers, it's a faulty USB port, it may charge but no data transfer.
midi_1996 said:
Look for Samsung usb driver, it will open a Samsung Dev website, download and install the drivers. Of it's not working either, try on another USB port, another computer, another cable, another phone with the same steps above, of it's not recognizing it on all computers, it's a faulty USB port, it may charge but no data transfer.
Click to expand...
Click to collapse
i have a g900v s5 here
the usb port is a new one, says g9008v on the usb hardware. is there a way to check the usb driver on the phone? maybe the usb driver needs reset or update
I'm trying to do a QCN back up but one of the required steps is to enter the Diag Mode (via starting the phone under BP Tools).
I am using the Qfil desktop app to do this but the phone won't remain on long enough for the backup.
The Qualcomm drivers are installed and the device is being detected by the PC, it just reboots once the USB cable is connected. (stays on for 5-10 seconds max) It stays on indefinitely once no cable is connected.
I've tried different PCs, different drivers, and even radio version 2.10L with no success.
Haven't seen this same problem in other threads and would appreciate any help.
d_originaldappa said:
I'm trying to do a QCN back up but one of the required steps is to enter the Diag Mode (via starting the phone under BP Tools).
I am using the Qfil desktop app to do this but the phone won't remain on long enough for the backup.
The Qualcomm drivers are installed and the device is being detected by the PC, it just reboots once the USB cable is connected. (stays on for 5-10 seconds max) It stays on indefinitely once no cable is connected.
I've tried different PCs, different drivers, and even radio version 2.10L with no success.
Haven't seen this same problem in other threads and would appreciate any help.
Click to expand...
Click to collapse
Go to developer option and Enable USB Debugging. (I know it's a late reply but it will help for others )
Thanks, but this was enabled. Still isn't resolved. Can't put a sim in the phone.
d_originaldappa said:
Thanks, but this was enabled. Still isn't resolved. Can't put a sim in the phone.
Click to expand...
Click to collapse
mine fixed by enabling usb debugging. did you allow the pc to usb debugging ? I also can't also put the sim. no imei and baseband unknown. I'm still looking for someone to share their qcn backup
Hello friends.
I have spent 2 days reading the forums and finally decided to post after not being able to get my XT1687 to switch into DIAG mod so that I can use QPST.
The device is boot loader unlocked, flashed with TWRP, running Arrow OS Pie.
No trick such as using setprop sys.usb.DM or Diag, or anything seems to work. Also, no dialer codes seems to work.
All I can manage to do with Shell is reset the USB connection.
No combination of Vol + UP or 3 finger "saluting"... while in bootloader on BP Tools, QCOM, Tools Mode (Switch to Enable) seems to work. I have tried with every setting of USB Configuration combined with debugging on, or debugging off. Nothing will prompt my Windows 10 machine to call for several of the version of the Qualcomm driver's that I have installed - and the only remotely close to a COM Port is when I set it to USB Tether and sets up as a network adapter but I have not been able to manually update that or any other driver so that it establishes a COM port.
Like, am I just stupid and this doesn't have Qualcomm hardware in it or something?
Very much appreciate any guidance.