Anyway to view an Android phone remotely like with PicMe but without root?
hah2110 said:
Anyway to view an Android phone remotely like with PicMe but without root?
Click to expand...
Click to collapse
The ddms tool in the Android SDK will get screen captures over USB Debug of course.
Anything remotely?
I don't think it's possible without root because you need to take snapshots of your phone and taking snapshots needs root. (unless you use ddms)
Zeam launcher can take screenshots of your home screen (not tested by me). http://forum.xda-developers.com/showthread.php?t=664149
But I think you are talking about live watching your mobile screen on PC, aren't you?
Most of these live view server take pictures of your screen and send it over the internet. There is also the issue with port forwarding. The only service that has pulled off remote screen viewing server without port forwarding has been teamviewer.
Sent from my Droid using XDA App
andrew121 said:
Most of these live view server take pictures of your screen and send it over the internet. There is also the issue with port forwarding. The only service that has pulled off remote screen viewing server without port forwarding has been teamviewer.
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Teamviewer exists for Android? I'm fine with the picture taking...
This is fairly new to the forum if you haven't seen it.. but it does require root.
http://forum.xda-developers.com/showthread.php?p=7567932#post7567932
khaytsus said:
The ddms tool in the Android SDK will get screen captures over USB Debug of course.
Click to expand...
Click to collapse
Does not have to be over USB. ADB can connect via TCP.
Code:
- disconnect device from usb then tell it to listen on 4455
adb tcpip 4455
restarting in TCP mode port: 4455
- connect to the device using a specified ip:port. my device is using wifi
adb connect 192.168.1.103:4455
connected to 192.168.1.103:4455
- now do normal adb commands over tcp
adb shell
- when your done, you can put it back in USB mode
adb usb
restarting in USB mode
You can also set an environment variable called ADBHOST with the IP address and adb will attempt to connect to that ip.
Now I am not sure if DDMS can connect to the device over tcpip, but if adb can, and ddms uses adb to connect, it should be possible.
BUMP. Any success here?
Its been a while, was wondering if there have been any solutions to this.
Sent from my Nexus S 4G using XDA App
Android ScreenControl without root
Have a look at this ... Its something I have been working on ...
http://piglings.blogspot.com/2011/08/android-screen-control-without-root.html
Hope that helps !
Cheers,
Vikram.
I found this and thought it will be helpful as I ended up on this thread during my search.
NO ROOT REQUIRED!
Follow this link: it has everything.
http://www.mymobiler.com/
So far only PC is supported I think.
The app also gives you the ability to use your PC keyboard remotely over wifi, it also has shortcuts for home, menu, back, etc.
The one thing that you might need to figure out is the display option in the mobile app settings.
I chose to keep it #3 - others ... that's the only way I can see the screen on my razr maxx!!
Also, if you are having weird screen problems, the website has the FAQ section and other pages to tweak the settings so that it works fine!!
Now it is a bit slow ... but none the less very useful ... I use it to change music while my phone's connected to speakers and chatting with people on Viber/WeChat/WhatsApp ... comes in pretty handy!!
Hope this helps!! cheers!!
Anyway to view android screen remotely without root
Have you tried the App Airdroid it might be what you're looking for.
camalot said:
Does not have to be over USB. ADB can connect via TCP.
Code:
- disconnect device from usb then tell it to listen on 4455
It works. Except that device must be connected via USB while configuring this.
Click to expand...
Click to collapse
Hi , I have made an app that enables you to connect 2 your phone wirelessly, using ADB. The app opens port tcp port 4774 n showcasesthe command needed to connect the device, the app also showcases the devices IP so you don't have to look it up, root is required 4 the root method. There are also premium versions available which remove adds, two are obtainable UnLockKkAyyy which should also unlock any other apps w/ it in the description, if they ever might be released n Start ADB Over Wi-Fi Unlocker which should only unlock this app.
Google play LiNKs:
Start ADB Over Wi-Fi [Root]
Start ADB Over Wi-Fi Unlocker
UnLockKkAyyy
This should be about it for now .
Reserved...
Reserved...
What's great is the OP is helping people connect rooted Android to PC adb completely wirelessly (without the initial need for the USB cable), where I'd like to ask the kind-hearted developer if he knows of a Windows PC networking command that we can run from the PC which tells us which port is being used for that adb connection.
More details on WHY I ask that question are over here...
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
Bearing in mind I'm NOT ROOTED (and my phone can't be rooted); so that's why I ask for help in determining the random Developer options Wireless debugging port after the fact...
I think I am missing the point of this app. Isn't ADB over WiFI a standard feature of android, under developer options?
>>>>:>>
GalaxyA325G said:
What's great is the OP is helping people connect rooted Android to PC adb completely wirelessly (without the initial need for the USB cable), where I'd like to ask the kind-hearted developer if he knows of a Windows PC networking command that we can run from the PC which tells us which port is being used for that adb connection.
More details on WHY I ask that question are over here...
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
Bearing in mind I'm NOT ROOTED (and my phone can't be rooted); so that's why I ask for help in determining the random Developer options Wireless debugging port after the fact...
Click to expand...
Click to collapse
You could try brute forcing it in CMD.
DiamondJohn said:
I think I am missing the point of this app. Isn't ADB over WiFI a standard feature of android, under developer options?
View attachment 5676389>>>View attachment 5676391>:>>View attachment 5676393
Click to expand...
Click to collapse
I don't think it was out while I was making it, I think is random and I prefer a static port.
Dev.4.fuN said:
Basically I don't think it was out while I was making it, I think is random and I prefer a static port.
Click to expand...
Click to collapse
The first post is from 2021, I definitely basically have used it well before that. However I do use custom ROMs. And as I implied it’s already there. One of the big concepts of Android OS is to use what’s there, not add on , which is basically a duplication.
DiamondJohn said:
The first post is from 2021, I definitely basically have used it well before that. However I do use custom ROMs. And as I implied it’s already there. One of the big concepts of Android OS is to use what’s there, not add on , which is basically a duplication.
Click to expand...
Click to collapse
Static port, so it's not.
My Samsung A30 has a broken screen, I’m attempting to transfer all my files unfortunately the phone does not have the file transfer mode enabled so when I plug it in to my PC it’s recognised as a modem.
I’ve attempted to use https://github.com/Genymobile/scrcpy to display my phone so I can perform transfer operations unfortunately it requires USB debugging enabled which I don’t have.
I’ve also attempted connecting my phone to my TV via a USB hub though the phone model does not support HDMI output.
The phone is running as it is receiving calls with it vibrating.
Any thoughts on anything else I can attempt? I’ve already bought a new phone so not too keen on getting the screen replaced especially given there could be other issues.
AHuss123 said:
My Samsung A30 has a broken screen, I’m attempting to transfer all my files unfortunately the phone does not have the file transfer mode enabled so when I plug it in to my PC it’s recognised as a modem.
I’ve attempted to use https://github.com/Genymobile/scrcpy to display my phone so I can perform transfer operations unfortunately it requires USB debugging enabled which I don’t have.
I’ve also attempted connecting my phone to my TV via a USB hub though the phone model does not support HDMI output.
The phone is running as it is receiving calls with it vibrating.
Any thoughts on anything else I can attempt? I’ve already bought a new phone so not too keen on getting the screen replaced especially given there could be other issues.
Click to expand...
Click to collapse
If the screen is broken and you did not have USB debugging enabled before it was broken, there is nothing you can do to retrieve your data except repair the screen or find a tech shop that has the tools and the knowledge to pull your data directly from the hardware chip itself.
You will not solve this yourself using only software.
Use a USB Type C to HDMI cable to your TV.
The Samsung A30 apparently supports it.
HDMI Alt Mode doesn't go through a hub.
Enable ADB and download.
@Droidriven thanks, fair enough, I've ordered a screen and will attempt to replace it myself.
@Renate To enable ADB I need to enable USB debugging. Also doesn't seem like Samsung A30 supports HDMI output https://www.samsung.com/au/support/mobile-devices/connect-samsung-device-to-tv-via-hdmi/
Oh, sorry, my bad. The internet will give you an answer to any question, usually wrong.
Is there any chance that you can find the hardware serial console on internal test points?
Then you just need to:
Code:
# settings put global adb_enabled 1
If your ADB was previously enabled, then you won't have to deal with the invisible acceptance screen.
If not you'll have to echo the public key into /data/misc/adb/adb_keys
(I just did this on my B&N Glow '21 when it factory reset and it blocked me with a mandatory OOBE setup.)
Renate said:
Oh, sorry, my bad. The internet will give you an answer to any question, usually wrong.
Is there any chance that you can find the hardware serial console on internal test points?
Then you just need to:
Code:
# settings put global adb_enabled 1
If your ADB was previously enabled, then you won't have to deal with the invisible acceptance screen.
If not you'll have to echo the public key into /data/misc/adb/adb_keys
(I just did this on my B&N Glow '21 when it factory reset and it blocked me with a mandatory OOBE setup.)
Click to expand...
Click to collapse
For one, your solution is not a software solution, which is what I said, that they would not solve this with software alone. That is true and that is all I was saying.
Second, this solution is a hardware approach that the typical user has no experience with, which is why I didn't present them with an option that I am certain they are not comfortable with or experienced enough to attempt, as demonstrated by their attempts with software and unsupported HDMI and then stopping there to ask for help. An answer that more than likely seems more like a risk to them than a solution, isn't really helpful to them. I've helped with users dealing with this issue for years, I've learned that the vast majority of them are not comfortable with resorting to solutions that people like you and I would. With most of them, you may as well be telling them that they can solve their issue by biting a tiger on his ear, they are afraid of the solution. But, I understand, you have a proven, working solution, so you posted it, that is actually good, thank you.
That is why I said to repair the screen or take the device to a tech shop that has the experience and the tools(which requires opening the device to implement a hardware solution, as your posted solution also requires opening the device to implement a hardware solution) to retrieve the data for them(if repairing the screen is not their preferred solution, which obviously isn't). Also, Samsung isn't as simple as B&N hardware, Samsung has some tricky stuff when it comes to hardware, especially their Qcom versions, such as Qfuse(on some nodeld)and other tricky hardware designed to make tampering a real pain or even kill the device with built in components intended to kill the device if triggered. Their bootloader is pretty hard to get past without breaking into the hardware itself also.
Yeah, I know about Samsung, which is why I don't buy it.
In any case, if it's booted to Android, then Android generic solutions will work.
I don't have any idea if a serial port is accessible, but if it were, that would be an easy option.
thanks for the advice guys, @Renate your solution is probably probably beyond my expertise though thanks for your comment, hopefully I can understand it better in future. I'm hoping to use this screen replacement as an entry point into mobile phone repair.
Hi everyone. I post this topic in here, because I don't know where else I could do it, because my device is of a not much known brand. I own a Krono Net 1032, chinese tablet, is rooted via magisk, and everything was going ok with it, until several days ago, when I tried to connect from pc, to adb via wifi, but it didn't connect (adb debugging was enabled and adb returned me 10061 error); action that was performed right without any issue till that day. Uneasied, I tried to connect it via usb, but not only won't connect to adb, but it won't be detected as mass storage... even is not detected as anything. Now, really worried, I tried to connect it by changing usb cable... the same; tried connecting on another usb ports...the same; tried connecting tablet on another pc... the same; tried connecting any peripheral via otg... peripherals won't work; I disabled and reenabled adb debugging... the same. It barely charges, but if I move the tablet, stops charging.
The alarming behavior is that, for I could get root access, it should be connected on preloader mode, for can flash it; so if I told you that this tablet is already rooted, is because in the past I could connect it on that mode and my pc did recognize it with such mode. But now, not even pc recognize such connection.
I suspect that is a hardware issue, but I don't know if that could be happening because of usb port solderings or an usb controller ic issue; and I don't want to open it and try to repair, without before read your opinions.
So please ¿What can be happening there?
Thanks in advance for your answers.
Do a Factory Reset.
xXx yYy said:
Do a Factory Reset.
Click to expand...
Click to collapse
I would do, if my device would be detected on fastboot mode or preloader mode, but none of those usb connection modes are detected by pc. So I don't guess it's an operating system issue; or better said, i'm afraid of doing that, and find that it remains the same. But I'll consider it as my last resort (because i've made many customizations that I don't want to lose -root, gravity box, lsposed, etc-). Anyway I think the reason of what could be happening, would be maybe worst than that (I think is a tablet's usb port issue). Thanks for your opinion.
PS: I forgot to say something that confuses me too much but at the same time, gives me hope that this isn't a hardware issue: Wifi adb isn't working too,and something weird, remote control from pc (eg. via teamviewer or anydesk) doesn't work also.
Don't think device's USB-port is defective, that of all things the lanes are broken, but not the power related connections.
I rather think that USB is not configured correctly in Android's build.prop file, expected USB- setting in build.prop always should be
Code:
persist.sys.usb.config=mtp,adb
xXx yYy said:
Don't think device's USB-port is defective, that of all things the lanes are broken, but not the power related connections.
I rather think that USB is not configured correctly in Android's build.prop file, expected USB- setting in build.prop always should be
Code:
persist.sys.usb.config=mtp,adb
Click to expand...
Click to collapse
I tried adding that line, and rebooted the device, but nothing happened, is still without usb support... But wait a moment, about it ¿is there any specific place to paste that line, or can be pasted wherever inside this file
Did you verify that buld.prop got changed?
Not already existing key-value pairs typically are added to end of build.prop file.
Ckeck for existence of these 2 key-value pairs too:
persist.service.adb.enable=1
persist.service.debuggable=1
Does the USB work properly in fastboot?
Renate said:
Does the USB work properly in fastboot?
Click to expand...
Click to collapse
No, is not recognized in fastboot or preloader. That's why I suspect of tablet's usb port, which would be probably the worst scenary to me. The weird thing is, if the suspected problem is related to hardware ¿Why adb via wifi is not working too? ¿Isn't that a routine separated from usb adb? or definitely ¿if usb adb is not working, wifi adb also stops working?
xXx yYy said:
Ckeck for existence of these 2 key-value pairs too:
persist.service.adb.enable=1
persist.service.debuggable=1
Click to expand...
Click to collapse
Yes, they are already written there, but none of the expected happened (which comes alive again its usb port).
If my problem would be hardware related, I mean, if the problem is at the usb port (i think it is, because, despite it charges when cable is plugged, if I move a little the tablet, it loses charge connection. I tried several cables and happens the same), if sadly i'm right, I think that, being positivist, it would be just solderings retouch on the usb port. But investigating, I can see that micro USB type C (female) connector, is not so easy (even is complicated to not say hard) to resolder, so ¿is there any technique?¿Do i need a hot air gun or something like that?¿or is that only solvable by swapping its main board?
Anyway, If my problem is of hardware, none of the options could be nice.
Often the USB connector is on its own little board connected by a flex printed circuit to the main board.
I Googled "Krono Net 1032 USB connector board" and got https://www.aliexpress.com/i/2255799845922187.html
Yeah, it would be great if they were related, but at least you can see what I mean and how cheap it would be if you could find the right one.
Renate said:
Often the USB connector is on its own little board connected by a flex printed circuit to the main board.
I Googled "Krono Net 1032 USB connector board" and got https://www.aliexpress.com/i/2255799845922187.html
Yeah, it would be great if they were related, but at least you can see what I mean and how cheap it would be if you could find the right one.
Click to expand...
Click to collapse
That board seems to be a spare part of a nokia device. It would be very good if only was disconnecting the suspected bad component, and connecting the new one. But I opened this tablet and what I saw, is that seems, that usb port is integrated with the mainboard.
If it were micro USB 2.0 I'd do it myself.
USB Type C on a motherboard I'm sure that I'd destroy somwthing.
Renate said:
If it were micro USB 2.0 I'd do it myself.
USB Type C on a motherboard I'm sure that I'd destroy somwthing.
Click to expand...
Click to collapse
That's my worry, because it's USB type C.
There are two types of Type C connector:
Real, USB 3.0 24 pin
Lite, USB 2.0 12 pin
I'm not sure that I'd even want to tangle with the 12 pin.
I have an update about this topic. Well, I took courage and disassembled as much carefully I could, I tried to get as much tools I could (besides solder iron, magnifying glass, focal illumination, soldering paste, etc.). I could saw that usb socket pins were tiny but accessible, so, also as much carefully I could, I resoldered them, I cleaned them, and reassembled the tablet.
To be brief, after that treatment, the battery charging was more consistent, more stable (now I can move the tablet without losing charging connection) but it still, doesn't want to be recognized by the pc, wheter if it's on fastboot mode, or normal mode (with tablet on). I must clear that my pc, recognizes other android devices that are plugged into it, but this one doesn't. So, that's very wird to me. My only explanation for that, is that its usb controller IC is working bad or could be broken, but if it would be broken, how could be possible, that tablet still can charges its battery? What do you think about it?
PS: I didn't see too much pins, so I think it has 12 pins.
Renate said:
There are two types of Type C connector:
Real, USB 3.0 24 pin
Lite, USB 2.0 12 pin
I'm not sure that I'd even want to tangle with the 12 pin.
Click to expand...
Click to collapse
I was seized by a big doubt since this problem happened. ¿Is wifi ADB bound to usb adb? I mean, if USB ADB isn't working, ¿Does wifi adb stop working too?
Another question is: Before this, I remember remote control worked on this tablet (control tablet remotely), but now there's no way to make it work ¿Can be this related to the original issue?
Even worst ¿Can the initial issue, be related to a ROM corruption issue? I say "worst" because if it is, I don't know how to reflash it without usb support.
No, WiFi ADB should work even if USB is broken.
You should be able to switch to WiFi ADB using a non-rooted terminal app.
You should be able to do this without root.
Code:
$ setprop service.adb.tcp.port 5555
But adbd has to be stopped and restarted. I'm not sure that this works without rooting.
Code:
$ stop adbd
$ start adbd
But you should be able to go to Settings > Developer options > Enable USB debugging and turn it off then on.
Then:
Code:
C:\>adb connect 192.168.1.12345:5555
Of course 192.168.1.12345 must be the actual IP of the Android on your router.
Renate said:
No, WiFi ADB should work even if USB is broken.
You should be able to switch to WiFi ADB using a non-rooted terminal app.
You should be able to do this without root.
Code:
$ setprop service.adb.tcp.port 5555
But adbd has to be stopped and restarted. I'm not sure that this works without rooting.
Code:
$ stop adbd
$ start adbd
But you should be able to go to Settings > Developer options > Enable USB debugging and turn it off then on.
Then:
Code:
C:\>adb connect 192.168.1.12345:5555
Of course 192.168.1.12345 must be the actual IP of the Android on your router.
Click to expand...
Click to collapse
Ok, I did all that, with a terminal emulator. Without root permission, those commands do nothing. So I invocated root access by typing "su" command; then root request appeared, I gave it to the app root access, and then all those commands worked ok. After corroborate the right wifi adb connection (after enable on developer options "usb debbugging" and all those stuff). I tried a remote control program called "scrcpy", and it worked as expected in a normal condition, I mean, I can see on my pc, the tablet's screen and also i can control the tablet from it, but after that , I'm still wondering, why all other remote control programs, like team viewer and anydesk, don't want to control this tablet, hmmm... ¡anyway!
That news in general to me, is an advance, and is good, but i'm still wondering why usb connection isn't responding (mtp, adb, fastboot nor preloader mode) , not even its OTG support and I'm pretty sure this tablet has it, because with it, came additional an OTG adapter, so why would do they add an otg adapter if tablet wouldn't support it?