Hello,
I am presuming that questions regarding the Note 6 Pro belong here as I cannot find a forum dedicated to that device. The question probably applies to multiple Redmi devices, anyway.
When I hook the device to my laptop I am consistently getting a dialog from Android asking if USB should be used to:
Charge this device
Transfer files
Transfer photos (PTP)
I would like for it to remember the, "Transfer files," choice like my Samsung device did, but I cannot for the life of me figure out where to find the settings that would allow me to do that.
Any assistance would be much appreciated.
under about phone, keep clicking MIUI version to obtain developer status. Click back to additional settings, developer options where you can set your MTP settings.
Thank you hiitsrudd!
I think it took 7 or 8 presses of the MIUI version and after I think the third it started giving a countdown until you "become a developer."
Why it has to be this difficult and cryptic will remain a mystery.
Related
Hello, I've recently joined this forum to lurk for some information about adding new LTE bands to my phone(Pantech's Vega Iron2(IM-910S))
It's a phone released in Korea back in April I think, anyway putting aside the irrelevant facts about my phone.
I have been playing with my phone to access my phone through RNDIS, ADB, MODEM mode. And I think I had partially made it happen.
The reason why I think so is because the phone shows up in the device manager as Port 5 and 6. Port 5 being the USB Mode and Port 6 being the diagnostic Mode.
Anyway even though it shows Port 5, when I try to add new port through QPST it says "no phone." So I'm guessing it's not properly connected.
On the other hand Prt 6, the diagnostic one shows that it does have something and it reads MSM8974 which is the processor of my phone.
It looked great until now, but when I tried to back up the NV items in case I screw everything up, it failed. I'm guessing it failed to write or properly read the items.
Also when I try to utilize the port through Serviceprog, it fails saying "Online Connection Failure : Unspecified Error."
I've searched and found that it might be happening because of the old version of my QPST(378). So I've tried the new 411 build but found no port at all...
I've enabled USB Debugging and all but I'm assuming it's not taking effect because the phone is turned off? Can anyone help me out?
Hi,
I can't find anything relevant on XDA for your device. Also I see you've already asked about this in the appropriate place. If you don't find help there, you can ask here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
I am a PC technician and don't know much about phones. A customer brought me in a mostly dead phone and wants pictures of his kids recovered. I believe this is probably possible given the state. I want to give enough information without overloading anyone looking to help, so I will put it in sections.
What I know about the phone:
I never saw it working and I'm not a phone guy. The back says the model is XT901. This customer is not a tech, so only push updates would have likely been done., if even those were done. It came in roughly 2 weeks ago. That is pretty much the extent of what I know about the phone and its OS.
What the problem is:
When booting normally the Motorola logo comes up with the swirling blue around it. It stays on that screen forever.
What the phone can do:
I can get into a couple different menu systems with different key presses (which I don't exactly remember right now. It's kind of trial and error to get into the one I want). The less helpful menu has a "Recovery" option which just makes the phone boot to the swirling logo again. By retrying with different keypress combinations I can get it to show the android on his back with the exclamation mark. From there I can reboot into a different menu, where I found QC Diag, among other things.
What I need to do:
I need to connect the phone to a Windows 7 Professional 64 bit computer to recover, especially, pictures of his kid that he didn't have backed up.
The problem I ran into:
Four devices do show up in the device manager as "Unknown device". I did manage to get the QC Diag port set up following the instructions here:
googlebought.blogspot.com
/2014/12/motorola-qc-diagnostic-driver.html (separated because I can't post links, but the information might be important)
I used the PID listed on the page since I have no idea what to change it to or even if I need to change it, but it did seem to work for one unknown device. I then right-clicked on each of the 4 "Unknown" devices and browsed to that folder. One was detected and updated, the Motorola QC Diag Port on COM3. This did not make a drive letter show up as I had hoped.
What I have tried:
Downloading a few dozen drivers to get all 4 of these devices detected, starting with the latest standard drivers for the phone, Motorola Device Manager 2.5.4 and Motorola Mobile Drivers Installation 6.4.0. This is how I got to just 4 devices listed as "Unknown". Of course, there are currently only 3 unknown since getting the QC Diag port going.
My technical abilities:
I have been a PC tech for about 15 years and am pretty good at it. I have rooted Android devices before, but frankly that's just "download a program, push a button". I am utterly unskilled in Android, but I can follow even complicated instructions.
I am hoping that there is a mode I can go into (I believe I've tried all I can get into) or a driver I can install which will allow me to browse the directories on the phone. I realize this is more complicated than it sounds because of the difference in file systems. I would imagine that since I can see these devices in certain modes this is probably possible.
Thank you in advance for any help you can offer. I'm sorry it's long-winded, but I wanted to be thorough. Hopefully it's organized enough that you can skip over any information you don't need.
XDA Visitor said:
I am a PC technician and don't know much about phones. A customer brought me in a mostly dead phone and wants pictures of his kids recovered. I believe this is probably possible given the state. I want to give enough information without overloading anyone looking to help, so I will put it in sections.
What I know about the phone:
I never saw it working and I'm not a phone guy. The back says the model is XT901. This customer is not a tech, so only push updates would have likely been done., if even those were done. It came in roughly 2 weeks ago. That is pretty much the extent of what I know about the phone and its OS.
What the problem is:
When booting normally the Motorola logo comes up with the swirling blue around it. It stays on that screen forever.
What the phone can do:
I can get into a couple different menu systems with different key presses (which I don't exactly remember right now. It's kind of trial and error to get into the one I want). The less helpful menu has a "Recovery" option which just makes the phone boot to the swirling logo again. By retrying with different keypress combinations I can get it to show the android on his back with the exclamation mark. From there I can reboot into a different menu, where I found QC Diag, among other things.
What I need to do:
I need to connect the phone to a Windows 7 Professional 64 bit computer to recover, especially, pictures of his kid that he didn't have backed up.
The problem I ran into:
Four devices do show up in the device manager as "Unknown device". I did manage to get the QC Diag port set up following the instructions here:
googlebought.blogspot.com
/2014/12/motorola-qc-diagnostic-driver.html (separated because I can't post links, but the information might be important)
I used the PID listed on the page since I have no idea what to change it to or even if I need to change it, but it did seem to work for one unknown device. I then right-clicked on each of the 4 "Unknown" devices and browsed to that folder. One was detected and updated, the Motorola QC Diag Port on COM3. This did not make a drive letter show up as I had hoped.
What I have tried:
Downloading a few dozen drivers to get all 4 of these devices detected, starting with the latest standard drivers for the phone, Motorola Device Manager 2.5.4 and Motorola Mobile Drivers Installation 6.4.0. This is how I got to just 4 devices listed as "Unknown". Of course, there are currently only 3 unknown since getting the QC Diag port going.
My technical abilities:
I have been a PC tech for about 15 years and am pretty good at it. I have rooted Android devices before, but frankly that's just "download a program, push a button". I am utterly unskilled in Android, but I can follow even complicated instructions.
I am hoping that there is a mode I can go into (I believe I've tried all I can get into) or a driver I can install which will allow me to browse the directories on the phone. I realize this is more complicated than it sounds because of the difference in file systems. I would imagine that since I can see these devices in certain modes this is probably possible.
Thank you in advance for any help you can offer. I'm sorry it's long-winded, but I wanted to be thorough. Hopefully it's organized enough that you can skip over any information you don't need.
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here but it's very quiet as it isn't the most popular phonein the world.
You can try posting your query there or in: Android Q&A,Help and Troubleshooting.
You'll have to create an account to post in the main forums.
Good luck
A friend of mine just dropped her phone and the LCD stopped working (no cracks, tactile was still working), her phone (Oneplus X) was running stock, unrooted and USB Debugging was disabled, so none of the available solutions were useful in this case. I almost lost hope after reading everywhere that there was not much left to be done when USB Debugging was diabled, so I tried a different approach.
There are a bunch of software that claim they can recover data but they all need USB Debugging to be enabled, so this was a big barrier. After a few tries I finally came up with a solution that I think can help anyone facing a similar situation. In my case I did all this blindly tapping on the blank screen, if your screen is more damaged you can use an OTG cable and a mouse or keyboard, you can find more info on this in other threads.
Step 1: Connect to a WiFi Network
First I needed to connect the phone to a wifi network, which I managed creating an unprotected network with a freshly installed DD-WRT router and clicking blindly on the phone. We all have a mental image of where things are located on the phone so this should be easily doable (slide from the top, tap to enable wifi, long press to see list of available networks, tap to select network) and if you are sitting next to the router the unprotected network will appear first in the list. On the router check for connected devices and the IP of the phone. A ping test will confirm that the phone is succesfuly connected to the network.
Step 2: Install AirDroid
Fortunately when I received the phone it had already installed Airdroid, so this made the process a little easier for me. The first time you run Airdroid a couple of extra screens will appear trying to get you to subscribe to access all the extra features so this will make things a little more complicated for those installing for the first time, try to google these images so you know whre to tap. I understand there are other apps with similar functionality but the fact that Airdroid starts with an A is very helpful here because it shows (at least for me) on the first row of your Apps Drawer.
Step 3: Connect to Airdroid
Now it's time to connect to AirDroid, to do this you need a computer connected to the same wifi network that the phone is connected, and since you already know the phone's IP this becomes a process of trial and error. Again, blindly tapping on your phone access the Apps Drawer and start the app placed on the first position (upper left corner under the search bar), in your computer's browser type the phone's IP followed by ":8888" (192.168.1.143:8888 in my case). If you fail to open AirDroid the page will just time out so you go for the app on the second position and reload the page on your browser, then the third and so forth.... once you successfully manage to open AirDroid a page will finally load and you'll hear a notification from your phone (it was the fourth try for me). Now there should be a notification window waiting for your confimation on your phone (google this to see where it is) so it shoud be an easy guess on where to tap. Once you can access your phone via AirDroid, the hard part is over! Now we can download pictures, files, ringtones and other stuff, but if you want to backup contacts there's no tool for this so we need to enable USB Debugging.
Step 4: Enable USB Debugging
With AirDroid running we can now take screenshots of the phone with the hardware buttons and view them using the "Photos" folder in AirDroid, so you open the notification drawer and tap where the "settings wheel" should be, take a screenshot and view it to confirm you succeeded, then scroll all the way down and take another screenshot to se if "Developer Options" are enabled. I'm sure by now you get the idea of the process, after any tap or scroll take a screenshot and view it to confirm your progress, once I got Developer Options enabled I managed to scroll down to USB Debugging and to enable it!
Now with USB Debugging enabled you can use programs like MyPhoneExplorer to backup your contacts to a .csv file or use screen cast apps like Vysor to see your phone's screen on your computer vía USB.
rtorresz said:
A friend of mine just dropped her phone and the LCD stopped working (no cracks, tactile was still working), her phone (Oneplus X) was running stock, unrooted and USB Debugging was disabled, so none of the available solutions were useful in this case. I almost lost hope after reading everywhere that there was not much left to be done when USB Debugging was diabled, so I tried a different approach.
There are a bunch of software that claim they can recover data but they all need USB Debugging to be enabled, so this was a big barrier. After a few tries I finally came up with a solution that I think can help anyone facing a similar situation. In my case I did all this blindly tapping on the blank screen, if your screen is more damaged you can use an OTG cable and a mouse or keyboard, you can find more info on this in other threads.
Step 1: Connect to a WiFi Network
First I needed to connect the phone to a wifi network, which I managed creating an unprotected network with a freshly installed DD-WRT router and clicking blindly on the phone. We all have a mental image of where things are located on the phone so this should be easily doable (slide from the top, tap to enable wifi, long press to see list of available networks, tap to select network) and if you are sitting next to the router the unprotected network will appear first in the list. On the router check for connected devices and the IP of the phone. A ping test will confirm that the phone is succesfuly connected to the network.
Step 2: Install AirDroid
Fortunately when I received the phone it had already installed Airdroid, so this made the process a little easier for me. The first time you run Airdroid a couple of extra screens will appear trying to get you to subscribe to access all the extra features so this will make things a little more complicated for those installing for the first time, try to google these images so you know whre to tap. I understand there are other apps with similar functionality but the fact that Airdroid starts with an A is very helpful here because it shows (at least for me) on the first row of your Apps Drawer.
Step 3: Connect to Airdroid
Now it's time to connect to AirDroid, to do this you need a computer connected to the same wifi network that the phone is connected, and since you already know the phone's IP this becomes a process of trial and error. Again, blindly tapping on your phone access the Apps Drawer and start the app placed on the first position (upper left corner under the search bar), in your computer's browser type the phone's IP followed by ":8888" (192.168.1.143:8888 in my case). If you fail to open AirDroid the page will just time out so you go for the app on the second position and reload the page on your browser, then the third and so forth.... once you successfully manage to open AirDroid a page will finally load and you'll hear a notification from your phone (it was the fourth try for me). Now there should be a notification window waiting for your confimation on your phone (google this to see where it is) so it shoud be an easy guess on where to tap. Once you can access your phone via AirDroid, the hard part is over! Now we can download pictures, files, ringtones and other stuff, but if you want to backup contacts there's no tool for this so we need to enable USB Debugging.
Step 4: Enable USB Debugging
With AirDroid running we can now take screenshots of the phone with the hardware buttons and view them using the "Photos" folder in AirDroid, so you open the notification drawer and tap where the "settings wheel" should be, take a screenshot and view it to confirm you succeeded, then scroll all the way down and take another screenshot to se if "Developer Options" are enabled. I'm sure by now you get the idea of the process, after any tap or scroll take a screenshot and view it to confirm your progress, once I got Developer Options enabled I managed to scroll down to USB Debugging and to enable it!
Now with USB Debugging enabled you can use programs like MyPhoneExplorer to backup your contacts to a .csv file or use screen cast apps like Vysor to see your phone's screen on your computer vía USB.
Click to expand...
Click to collapse
Greetings mate,
XDA Assist is for newbies finding their way around XDA Developers.
You may post the guide in Miscellaneous Android Development Forum where people looking for the same could use your help.
Thread closed!
Regards
Vatsal,
Forum Moderator.
A friend has a stock S7 with a broken screen and USB debugging disabled.
I have read posts here about this situation and it looks like the prognosis is bleak, but it has been more than a year since the last one I found, and things do change with time as more is learned, especially on popular phones like the Galaxy line, so it seemed like a good idea to ask again. His wife has baby pictures on it that are worth a good bit to them. Why they weren't backed up to the cloud is anyone's guess - I get that some folks dislike sharing private lives with Google, but there are plenty of Boxcryptor type apps one can use - but the point is moot. They have their privacy and no baby pictures. It is what it is.
A quick Google search finds lots of proprietary software that claims that it doesn't need USB debugging to be enabled or that it can enable it, but the sparse details provided about this superhuman ability makes this seem unlikely.
Someone mentioned a way to sideload a custom kernel in order to somehow enable USB debugging via ADB. Is this possible? Can USB debugging be enabled from stock recovery on the S7, or any other route?
There are all sorts of Octopus / Miracle Box type gadgets and software packages that claim to make various phones dance and sing, but I can't find one that will recover files from the S7. It might be worth buying such a package, if it existed.
Some posts, articles and videos suggest using an OTG to connect a mouse or keyboard and navigate the broken screen, either from memory or by taking screenshots and retrieving them from phone storage. We have not tried this yet, and any tips specific to the S7 would be really appreciated.
Someone posted an application here, that is apparently intended to help with this situation, but mirroring a phone screen requires USB debugging to be enabled.
https://forum.xda-developers.com/showthread.php?t=2786395
Thanks to anyone who might be able to help, and I apologize for adding a redundant question. I am just hoping that there is something new in the Galaxy world that might have made this situation salvageable.
SmilingPerson said:
A friend has a stock S7 with a broken screen and USB debugging disabled.
I have read posts here about this situation and it looks like the prognosis is bleak, but it has been more than a year since the last one I found, and things do change with time as more is learned, especially on popular phones like the Galaxy line, so it seemed like a good idea to ask again. His wife has baby pictures on it that are worth a good bit to them. Why they weren't backed up to the cloud is anyone's guess - I get that some folks dislike sharing private lives with Google, but there are plenty of Boxcryptor type apps one can use - but the point is moot. They have their privacy and no baby pictures. It is what it is.
A quick Google search finds lots of proprietary software that claims that it doesn't need USB debugging to be enabled or that it can enable it, but the sparse details provided about this superhuman ability makes this seem unlikely.
Someone mentioned a way to sideload a custom kernel in order to somehow enable USB debugging via ADB. Is this possible? Can USB debugging be enabled from stock recovery on the S7, or any other route?
There are all sorts of Octopus / Miracle Box type gadgets and software packages that claim to make various phones dance and sing, but I can't find one that will recover files from the S7. It might be worth buying such a package, if it existed.
Some posts, articles and videos suggest using an OTG to connect a mouse or keyboard and navigate the broken screen, either from memory or by taking screenshots and retrieving them from phone storage. We have not tried this yet, and any tips specific to the S7 would be really appreciated.
Someone posted an application here, that is apparently intended to help with this situation, but mirroring a phone screen requires USB debugging to be enabled.
https://forum.xda-developers.com/showthread.php?t=2786395
Thanks to anyone who might be able to help, and I apologize for adding a redundant question. I am just hoping that there is something new in the Galaxy world that might have made this situation salvageable.
Click to expand...
Click to collapse
Try the solution in the link you've posted, i'm sure you no longer need debugging enabled.
Also the real issue is you need to unlock the phone, so if the screen is just black?? You can usualy guess where the patterns or numbers appear etc, easy if you have another s7 next to it.
Also other options here
cooltt said:
Try the solution in the link you've posted, i'm sure you no longer need debugging enabled.
Also the real issue is you need to unlock the phone, so if the screen is just black?? You can usualy guess where the patterns or numbers appear etc, easy if you have another s7 next to it.
"]here [/URL]
Click to expand...
Click to collapse
Thank you! This is very helpful.
I think debugging must be enabled for that solution, but I hadn't read far enough or close enough to find Msmtx's solution for enabling it from ADB.
https://forum.xda-developers.com/showpost.php?p=66731042&postcount=260
My blind spot now rectified, I am going to give this a try. I know nothing about stock recoveries - is the one in the S7 going to allow me to do this, or will I have to install or boot TWRP or Safestrap?
Thanks again mate, it will be great to get those pics back. I just hope they have learned from this the great value of backups...
Sent from my unknown using Tapatalk
Hi @SmilingPerson - Did you get this resolved? I'm facing the same issues, and on top of all the OTG ideas, the phone I need to access has a swipe lock, so I'm pretty sure connecting a mouse without seeing anything is useless. Would appreciate any tips.
I wish I could tell you something, but nothing worked, sadly, and I used the old phone for parts.
Good luck though, hope you fare better than I.
I have an android 9 device which has got broken screen but the phone is very much alive. Its developer settings are on but USB debugging is off. Screen is locked with a numeric pin that I do remember. ADB shows it as unauthorized device. I have family photos in it that I want to backup(I had no cloud backup, I know I’ve been stupid) but I don’t want them circulating on the internet. So, if I get it repaired at an electronics store is it possible my data may get stolen? Please reply only if you know this stuff. The reason I am asking this question here in general QnA is because I want most developers and security experts to see the question rather than only device specific.
1.
To backup an Android device it's Android must be rooted and USB-Debugging must got enabled.
2.
My guess is that any autorized service center has the tool to fetch the data you're are interested in, even if the 2 requirements listed aren't met.