[Q] Connecting to PC via USB After JB Update gives "Connected As An Installer"
I did the OTA Jellybean update the day it came out and all was well. But now I have an issue when I connect the phone to my computer via USB.
When I first plug it in it says "Connected as an installer" and creates a CD Drive on my computer with the volume name being "Verizon Mobile". An autoplay prompt dialogue appears showing that I can run some executable called ToolLauncher-Bootstrap.exe.
Inside the folder is the Samsung USB Driver installer and some other weird files. In USB mode settings neither mode is checked and if I try to select MTP manually it switches right back to installer. Then after about 10-15 seconds the phone switches over to MTP mode like usual.
So it only works if I let it connect as an installer and wait the 10 seconds for it to switch on it's own. So it still works but is incredibly annoying. Does anyone have any clue what this is? I'm pretty saavy but this has me stumped.
Pictures below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had this question myself. I wondered why that installer comes up before the media device.
Sent from my SCH-I535 using xda app-developers app
Maybe the Mayan Calendar ending has something to do with it....
I get the same thing, did you run the installer? Maybe its a file manager utility that samsung added to their JB release for better file transfer between phone and pc. Wonder if it will auto MTP once you let the installer finish. It might be a one time deal.
VittoCornelius said:
I get the same thing, did you run the installer? Maybe its a file manager utility that samsung added to their JB release for better file transfer between phone and pc. Wonder if it will auto MTP once you let the installer finish. It might be a one time deal.
Click to expand...
Click to collapse
You should read the original thread. I mentioned that it only connects as installer for about 10 seconds and then switches over to MTP. So it works still it just is incredibly annoying and inconvenient to have to keep waiting every time. Especially since it didn't do this before the JB update.
I've tried running one of the programs and some weird thing pops up from Verizon to install something. But it cuts over to MTP mode before you ever get a chance to do anything.
It's very strange and I think this might have to do with using EZ-Unlock and messing with the bootloader on 4.1.1. I mean I find it odd that it's connecting as an installer for the bootstrap and that's basically what the bootloader is. I bet we'll hear that EZ Unlock needs to be fixed soon.
Doesn't have anything to do with EZ-Unlock or being rooted.
My 535 did the same thing stock.
The same thing happened to me just click the notification then check the mount as media device option and that should get you back to normal.
zaccat4 said:
The same thing happened to me just click the notification then check the mount as media device option and that should get you back to normal.
Click to expand...
Click to collapse
Again I mentioned this already as well in the OP. I really ask that you guys read the entire post. When I go to USB settings and set it manually it switches over to MTP but then quickly goes back to installer. Then it will start the process over again and automatically switch to MTP 10 seconds later on it's own.
Basically I have to let it connect as installer and let it switch to MTP on it's own otherwise it won't stay on MTP mode. Surely someone must have a clue why this is happening? I never had this issue on stock nor rooted ICS regardless of what others have said. It was only when I upgraded to JB. It happened BEFORE I applied EZ Unlock or root now that I think about it.
wushdishmeen said:
Again I mentioned this already as well in the OP. I really ask that you guys read the entire post. When I go to USB settings and set it manually it switches over to MTP but then quickly goes back to installer. Then it will start the process over again and automatically switch to MTP 10 seconds later on it's own.
Basically I have to let it connect as installer and let it switch to MTP on it's own otherwise it won't stay on MTP mode. Surely someone must have a clue why this is happening? I never had this issue on stock nor rooted ICS regardless of what others have said. It was only when I upgraded to JB. It happened BEFORE I applied EZ Unlock or root now that I think about it.
Click to expand...
Click to collapse
Here's the fix. Not sure what all the side effects are, but it definitely kills that stupid installer mode auto mount thing.
(Part of this is from user triggerm8)
1) You'll probably have to unlock the hidden menus by entering *#22745927 in the dialer.
2) Go into the USB I2C Mode Control menu by entering *#7284#.
3) Select Qualcomm USB Options
4) Choose MTP + ADB and save.
Next time you plug in your phone, it will go right to MTP mode bypassing that irritating Verizon install disc mount!
Averix said:
Here's the fix. Not sure what all the side effects are, but it definitely kills that stupid installer mode auto mount thing.
(Part of this is from user triggerm8)
1) You'll probably have to unlock the hidden menus by entering *#22745927 in the dialer.
2) Go into the USB I2C Mode Control menu by entering *#7284#.
3) Select Qualcomm USB Options
4) Choose MTP + ADB and save.
Next time you plug in your phone, it will go right to MTP mode bypassing that irritating Verizon install disc mount!
Click to expand...
Click to collapse
Thanks! :good:
Averix said:
Here's the fix. Not sure what all the side effects are, but it definitely kills that stupid installer mode auto mount thing.
(Part of this is from user triggerm8)
1) You'll probably have to unlock the hidden menus by entering *#22745927 in the dialer.
2) Go into the USB I2C Mode Control menu by entering *#7284#.
3) Select Qualcomm USB Options
4) Choose MTP + ADB and save.
Next time you plug in your phone, it will go right to MTP mode bypassing that irritating Verizon install disc mount!
Click to expand...
Click to collapse
Thanks this worked perfectly. So glad someone figured it out because it was driving me nuts. :laugh:
Averix said:
1) You'll probably have to unlock the hidden menus by entering *#22745927 in the dialer.
2) Go into the USB I2C Mode Control menu by entering *#7284#.
3) Select Qualcomm USB Options
4) Choose MTP + ADB and save.
Click to expand...
Click to collapse
Thanks. I've tried this solution before, but it sort of meets my needs: I select
PTP + ADB
and it connects (directly, bypassing the Installer mode) as MTP.
So, I still need to manually change the connection mode. FYI.
- ooofest
Related
Hello guys,
I've bought myself a secondhand I-mate Jam with a French Rom on it which I offcourse want to change.
After trying many many I just don't seem to work. I think I never got in the Bootloader mode (hold Camera button + power button and then press the reset button) but when I do this my screen just turns black and nothing happens.
If I try to start up everytime I get the startup wizard with pen calibration. Then he goes to windows and starts with the customization untill the screen goes black again and I can't do anything. If I want to powerup again I need to slide the battery cover back and forth and then I can powerup again. Only just to get the startup wizard again.
Please help me with this. I'm going crazy with trying and trying.
Cheers,
Veek
After more searching and trying I finally got the HTCMAG_ROM_WWE_O3 from Cotulla installed. Only my radio isn't the good version.
So trying to go back to older rom with good radio and then install HTCMAG_ROM_WWE_O3 again.
And I think with I-mate the bootloader is just a black screen. I still keep getting a black screen when I try to acces bootloader mode.
Cheers,
Veek
bootloader mode on htc magician marked with a black screen and there are writings SERIAL or USB (if connected with USBSync) at the top center of the screen, while the bottom of the screen are made V1.xx (bootloader version)...
I think i have your same problem! it keeps rebooting and everytime i try to install a new radio version it turns to boot mode (or almost that should be usb + 1.0 ) and nothin happens... i want to give him life back! =(
Geko90 said:
I think i have your same problem! it keeps rebooting and everytime i try to install a new radio version it turns to boot mode (or almost that should be usb + 1.0 ) and nothin happens... i want to give him life back! =(
Click to expand...
Click to collapse
try reflash Radio Rom again ! for smooth and successful flashing process should remove the SIM card from your device
Installation:
- Extract files Radio Rom
- Enter bootloader mode on device (Press POWER + CAMERA + RESET, you will see Serial/USB at top and 1.0X at bottom)
- Connect via USB to PC
- Run MaUpgradeUt_noID.exe
- Follow instructions in Update program.
- At the end you should see at device screen: "100% Upgrade Radio Image Complete".
- After flashing press reset.
Hakim Rahman said:
try reflash Radio Rom again ! for smooth and successful flashing process should remove the SIM card from your device
Installation:
- Extract files Radio Rom
- Enter bootloader mode on device (Press POWER + CAMERA + RESET, you will see Serial/USB at top and 1.0X at bottom)
- Connect via USB to PC
- Run MaUpgradeUt_noID.exe
- Follow instructions in Update program.
- At the end you should see at device screen: "100% Upgrade Radio Image Complete".
- After flashing press reset.
Click to expand...
Click to collapse
I'm trying to do this, but something's wrong... when I run maupgradeut_noID.exe the window says the ppc has to be connected via usb and synced with active sync... issues start after clicking on "Upgrade", because the phone goes in boot mode and nothing more happens... only that less than a minute later the pc loses connection of the phone =(
Geko90 said:
I'm trying to do this, but something's wrong... when I run maupgradeut_noID.exe the window says the ppc has to be connected via usb and synced with active sync... issues start after clicking on "Upgrade", because the phone goes in boot mode and nothing more happens... only that less than a minute later the pc loses connection of the phone =(
Click to expand...
Click to collapse
if so, then try to disable connections Ms. ActiveSync on your PC
open Ms ActiveSync --> File --> Connection Settings --> do not check column Allow USB connections
Hakim Rahman said:
if so, then try to disable connections Ms. ActiveSync on your PC
open Ms ActiveSync --> File --> Connection Settings --> do not check column Allow USB connections
Click to expand...
Click to collapse
I'm going to try it! Finger crossed for me xD
tryed... if I uncheck "usb connection", the pc doesn't recognize the ppc at all =(
that's what I get when trying to upgrade radio or rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I sync it it shows me the pocketpc disk in "computer" and I can explore it... is it someway useful? also, when synced, I get this window (trying to update):
now... do you think there is still some possibility for my magician to wake up from this long sleep?
THANKS
Geko90 said:
I'm going to try it! Finger crossed for me xD
tryed... if I uncheck "usb connection", the pc doesn't recognize the ppc at all =(
that's what I get when trying to upgrade radio or rom
If I sync it it shows me the pocketpc disk in "computer" and I can explore it... is it someway useful? also, when synced, I get this window (trying to update):
now... do you think there is still some possibility for my magician to wake up from this long sleep?
THANKS
Click to expand...
Click to collapse
even if you uncheck the " usb connection " and the pc does not recognize the device, however the upgrade process is still running
Hakim Rahman said:
even if you uncheck the " usb connection " and the pc does not recognize the device, however the upgrade process is still running
Click to expand...
Click to collapse
Hi,
i'm experiencing the same problem. I have never been able to access the bootloader by pressing those 3 buttons. The device just freezes and i need to remove the battery in order to reset it. Others also have experienced the same problem. Why won't the bootloader show up?
My phone can only charge but not be recognized on USB, when I plug it into my computer it says it's unrecognizable from my computer (like an error pops up). It wasn't like this before I installed the new update to the cygeonmod rom. I tried going back to stock gingerbread, other roms. Like at least 4 roms i've tried I just don't know what to do now. Any Ideas?
Are you trying to access the storage or use development tools (like adb) via USB?
Also, have you tried with a different USB port (preferably one on the motherboard of your computer)?
WindSlash said:
Are you trying to access the storage or use development tools (like adb) via USB?
Also, have you tried with a different USB port (preferably one on the motherboard of your computer)?
Click to expand...
Click to collapse
I'm just trying to access the storage, I've tried different usb ports but it just keeps saying USB Device Not Recognized.
I'm assuming you're using Windows... can you go under Device Manager and see if there is one with an exclamation mark (!) when your device is plugged in?
WindSlash said:
I'm assuming you're using Windows... can you go under Device Manager and see if there is one with an exclamation mark (!) when your device is plugged in?
Click to expand...
Click to collapse
yes theres and exclamation mark when I plug it in and it says (!) Unknown Device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone got any solutions?
tdog1o1 said:
My phone can only charge but not be recognized on USB, when I plug it into my computer it says it's unrecognizable from my computer (like an error pops up). It wasn't like this before I installed the new update to the cygeonmod rom. I tried going back to stock gingerbread, other roms. Like at least 4 roms i've tried I just don't know what to do now. Any Ideas?
Click to expand...
Click to collapse
Had the same problem and it ended up being a faulty USB cable. Pretty unlikely, but try a different cable and see if that helps.
XK72 said:
Had the same problem and it ended up being a faulty USB cable. Pretty unlikely, but try a different cable and see if that helps.
Click to expand...
Click to collapse
I've tried different usb cables with different computers and with different usb slots in each computer. Nothing works. Is it possible that my nexus s is missing a file allowing me to connect usb to my computer? Because every computer I use it says USB DEVICE NOT RECOGNIZED so I was just wondering if that's the case.
tdog1o1 said:
I've tried different usb cables with different computers and with different usb slots in each computer. Nothing works. Is it possible that my nexus s is missing a file allowing me to connect usb to my computer? Because every computer I use it says USB DEVICE NOT RECOGNIZED so I was just wondering if that's the case.
Click to expand...
Click to collapse
It sounds like your problem can be isolated to the phone, but I'm not familiar with working in a Windows environment. I'd try booting into (the phone's) Recovery and seeing if you can mount the drive from there. Might help you isolate whether or not your issue is related to a particular volume.
XK72 said:
It sounds like your problem can be isolated to the phone, but I'm not familiar with working in a Windows environment. I'd try booting into (the phone's) Recovery and seeing if you can mount the drive from there. Might help you isolate whether or not your issue is related to a particular volume.
Click to expand...
Click to collapse
I tried that going into the phone's recovery mode and plugging in the usb cord and it still says the same thing. When I go into further like clicking the message it gives me a Code 43 warning on my computer. I also tried hard factory resetting my phone when I was on the phone with Samsung and that didn't work either. Everything was fine before I flashed Cygenmod rom on my phone everything was perfect.
tdog1o1 said:
I tried that going into the phone's recovery mode and plugging in the usb cord and it still says the same thing. When I go into further like clicking the message it gives me a Code 43 warning on my computer. I also tried hard factory resetting my phone when I was on the phone with Samsung and that didn't work either. Everything was fine before I flashed Cygenmod rom on my phone everything was perfect.
Click to expand...
Click to collapse
Have you installed the drivers from http://developer.android.com/sdk/win-usb.html?
XK72 said:
Have you installed the drivers from http://developer.android.com/sdk/win-usb.html?
Click to expand...
Click to collapse
I tried it and nothing is working.
Can you go back to Device Manager?
Double click on the "Unknown Device", then click on "Details" tab, under "Property", select "Hardware Ids", and take a screenshot of what's there?
WindSlash said:
Can you go back to Device Manager?
Double click on the "Unknown Device", then click on "Details" tab, under "Property", select "Hardware Ids", and take a screenshot of what's there?
Click to expand...
Click to collapse
Here you go.
Interesting... now let me ask you from another angle, with the phone connected and USB debugging on, are you able to access the phone using adb devices / fastboot?
download and install PDANet
worked like a charm for me, installed my usb drivers to my phone which i had problems with just like you.
WindSlash said:
Interesting... now let me ask you from another angle, with the phone connected and USB debugging on, are you able to access the phone using adb devices / fastboot?
Click to expand...
Click to collapse
No i'm not able to access it with fastboot or adb devices. All it says is USB device not recognized.
Nexus S Woes
I had the exact same story and errors as tdog1o1, and the ONLY fix I found useful was on an mp3 forum.
" I had code 43 problems with my usb ports until I found a thread on MSI's website. My front panel usb ports connected to a 9 pin usb header on the motherboard. Only 8 pins are needed. If pin 9 has a black ground wire then remove it. I didnt give this fix much hope but it fixed my problems! "
After many hours of driver installs, front usb port changes, and a dozen reboots, this actually worked!
I merely used the USB at the back of the computer and Voila!
Looks Wind Slash nailed it at the beginning of this thread.
Nexus S
I am having the exact problem, have found a solution.
My brother attempted to root my Galaxy Tab P6200 (and succeeded), and then tried to run an app which increased pixel density which is when everything went downhill.
Thereafter, I constantly get this message "Sorry! The application Tw Launcher (process com.android.launcher) has stopped unexpectedly." and my tab has been rendered useless for the time being.
I have been desperately trying to flash various packages, right from the Official firmware from here to Clockwork Mod from here.
All to no avail, as I am constantly getting the error as shown below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am using a Macbook Pro running OSX Lion 10.7.4, Heimdall-Frontend v 1.3.1
I do have access to a Windows machine (running Vista) as well, but there my problem is that the tab is not getting recognised (inspite of installing KIES and Samsung drivers).
Any ideas on how to resolve this? Thank you for your time.
Jambavan said:
My brother attempted to root my Galaxy Tab P6200 (and succeeded), and then tried to run an app which increased pixel density which is when everything went downhill.
Thereafter, I constantly get this message "Sorry! The application Tw Launcher (process com.android.launcher) has stopped unexpectedly." and my tab has been rendered useless for the time being.
I have been desperately trying to flash various packages, right from the Official firmware from here to Clockwork Mod from here.
All to no avail, as I am constantly getting the error as shown below.
View attachment 1227962
View attachment 1227963
I am using a Macbook Pro running OSX Lion 10.7.4, Heimdall-Frontend v 1.3.1
I do have access to a Windows machine (running Vista) as well, but there my problem is that the tab is not getting recognised (inspite of installing KIES and Samsung drivers).
Any ideas on how to resolve this? Thank you for your time.
Click to expand...
Click to collapse
I remember I messed up my tablet using the DPI Changer app when I first got it (I think I tried setting DPI to 170 or 180, I don't remember), but I had already made a backup in CWM which I restored and that fixed the problem.
I don't know whether the following will help or not. Have you used the Play Store on your device to download apps? You could try installing a different launcher (that works at the DPI you set) directly to your device using the Play Store from a web browser on your PC ( https://play.google.com/store?hl=en ). You may need to tap the home button on your tablet to select it/set it as default after it has been installed.
BTW, that CM 9 ZIP you tried to flash should be installed using ClockworkMod (CWM).
It might be worth a try. I hope this helps.
Hi k_t_b, thanks for your reply.
Unfortunately, I am no longer signed in to my account on the tab, and can't seem to sign in either because of the TW launcher problem.
Jambavan said:
Hi k_t_b, thanks for your reply.
Unfortunately, I am no longer signed in to my account on the tab, and can't seem to sign in either because of the TW launcher problem.
Click to expand...
Click to collapse
So, when you visit the play store using a web browser on your computer, signed-in to your account, you aren't able to click "INSTALL" and select your device from the list "SEND TO ANOTHER DEVICE..."? Even if you can't tap the home button on your status bar to select an alternate launcher after installing a different launcher, you should be able to select the other launcher upon rebooting your tablet.
But, If I am understanding you correctly, you signed-out of your google account on the tablet (removed your account or turned off syncing) before you changed the DPI? If that's the case, I suppose my suggestion isn't an option.
If you can get ADB working (you have the Android SDK installed and the USB drivers from Samsung KIES) then you might want to try to pull the build.prop file, edit the DPI value and push build.prop back to your tablet.
Are you able to boot into recovery mode? (With your tablet off, Hold the Volume Up and Power buttons at the same time)
k_t_b said:
So, when you visit the play store using a web browser on your computer, signed-in to your account, you aren't able to click "INSTALL" and select your device from the list "SEND TO ANOTHER DEVICE..."? Even if you can't tap the home button on your status bar to select an alternate launcher after installing a different launcher, you should be able to select the other launcher upon rebooting your tablet.
But, If I am understanding you correctly, you signed-out of your google account on the tablet (removed your account or turned off syncing) before you changed the DPI? If that's the case, I suppose my suggestion isn't an option.
If you can get ADB working (you have the Android SDK installed and the USB drivers from Samsung KIES) then you might want to try to pull the build.prop file, edit the DPI value and push build.prop back to your tablet.
Are you able to boot into recovery mode? (With your tablet off, Hold the Volume Up and Power buttons at the same time)
Click to expand...
Click to collapse
Hi again,
Yes you are right, I am no longer signed in. When I found the tab in its current state, I got into recovery mode and selected 'factory rest'. On rebooting, I found out that I was no longer signed in to my google account, nor could I try to sign back in since at every stage the TW Launcher fails.
Also, as of now, the tab is in Download mode (since I was trying to flash the firmware), and it says something on the lines of "Do not switch off target device". So not sure if I should turn off the tab or not.
Jambavan said:
Hi again,
Yes you are right, I am no longer signed in. When I found the tab in its current state, I got into recovery mode and selected 'factory rest'. On rebooting, I found out that I was no longer signed in to my google account, nor could I try to sign back in since at every stage the TW Launcher fails.
Also, as of now, the tab is in Download mode (since I was trying to flash the firmware), and it says something on the lines of "Do not switch off target device". So not sure if I should turn off the tab or not.
Click to expand...
Click to collapse
Don't worry about that. If this was a phone with a removable battery, then you might remove the battery to get it out of download mode. You should be able to power off this tablet without a problem as long as you aren't in the middle of flashing it.
If you can't use ADB successfully while booted normally or in recovery, then I believe your only option will be to flash a stock firmware with Odin, Heimdall or flash CM 9. If you want to go the CM 9 route, then make sure you flash CWM first ( garyd9's CWM http://forum.xda-developers.com/showthread.php?t=1392348 - you can find instructions in his CWM for the 6210 thread and I think you'll need to have a microSD card to perform this operation ) , then install that CM 9 zip (which you attempted to flash using Heimdall) using CWM.
Thanks once again for your reply, I really appreciate the help. :good:
I will try and use the adb route and reply if I have any luck. Just one thing though, will it make a difference if I am using Linux as a virtual machine? (Ubuntu run via Parallels on a Macbook).
Also, while I agree with each of the three modes suggested by you, as of now I am stuck with both Mac and Windows (running Windows Vista) telling me while using Heimdall that it has "failed to detect compatible download-mode device". Odin on the other hand, doesn't show any signs of the port turning yellow.
I have installed KIES on both the machines, so not sure what the issue is. Also tried the usual restarting and changing USB ports procedures.
I think that with the cmw is possible to install unsigned packages. So is just a question of making a package with a corrected build.prop. the structure of a update package is real simple, look the one on the thread about root.
Just an idea.
Sent from my GT-P6210 using Tapatalk 2
leodfs said:
I think that with the cmw is possible to install unsigned packages. So is just a question of making a package with a corrected build.prop. the structure of a update package is real simple, look the one on the thread about root.
Just an idea.
Sent from my GT-P6210 using Tapatalk 2
Click to expand...
Click to collapse
As of now, my problem is that neither my Mac nor my PC is recognising the P6200 when in "Download" mode. I have installed Kies (on both Windows and Mac), and also the drivers that come with Heimdall (For Windows).
Literally all you have to do is just reflash the Rom in recovery without wiping. Factory reset won't do it. Done it myself a time or 2
Sent from my myTouch 4g via Tapatalk
I finally flashed the stock rom using Odin. Also, I had to install certain drivers for the USB, details of which I will post later.
Sent from my GT-P6200 using xda app-developers app
I just received the Pixel 2. Connected it to a Windows 10 box. Windows installed Microsoft drivers. I can't install Google drivers because Winblows says that the best drivers for my device are already installed. So I open an Explorer window, and there's the Pixel 2. I open that and it's a totally blank window. No, it's not the phone - ES shows directories in internal storage. (To make sure, I took a picture. It's in /DCIM/Camera.)
Enable debugging. Enable unlock. adb devices. No devices.
Okay, manually reboot to the bootloader. (The last line is Device State: locked) Fastboot sees the device.
fastboot boot twrp.img (I renamed it to make it easier). "FAILED (remote: Operation is not allowed in Lock State)"
I've owned Samsungs for so long I forgot that there were other manufacturers. What am I doing wrong? (I know it's got to be me, not the phone.)
How do I force Windows to replace the drivers (or do I really have to boot into Linux?) And how do I get the thing unlocked? Yes, I googled it. I searched here. I'm still stumped.
Maybe try this all in one tool
https://forum.xda-developers.com/pixel-2/development/tool-tool-one-driversunlocktwrpfactory-t3730228
Then check this out:
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
flashing unlock did it. Thanks. Now to see if I can install everything (TWRP, Magisk, etc.) then a day of reinstalling all my apps and data.
Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)
Rukbat said:
Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)
Click to expand...
Click to collapse
To get your device to show up you have to pull the notification shade down and then change the device mode to mtp storage mode. As for updating to new security patchs I usually just use the factory image from Google and the flash-all script with the -w option removed in order to keep my data. Then flash my kernal and magisk.
I already had it set - I guess unlocking the bootloader resets it.
Rukbat said:
I already had it set - I guess unlocking the bootloader resets it.
Click to expand...
Click to collapse
It resets Everytime you disconnect the device or reboot for some dumb reason. It gets annoying.
Maybe in an update far away ...
Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank You
_satish_ said:
Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
Thank You
Click to expand...
Click to collapse
Attaching Screen shot
"Allow USB Debugging" to allow computer's RSA Keyprint not popping up (Windows 10)
Hey all,
I recently got a new Windows 10 laptop and tried connecting my Pixel 3 to it today. The internal storage of the phone shows up no problem when plugging in. However, I cannot get ADB to work with the laptop. I have USB Debugging selected on the phone but when my phone connects to the laptop, there isn't any popup where it says "Allow USB Debugging?" and it also says the computer's RSA Keyprint.
On my old Windows 8.1 laptop, when it connected to my phone for the first time, a popup asking for permission to "Allow USB Debugging" would popup and I would allow it and things would work. I've opened a CommandPrompt window where my SDK platform tools are to check "adb devices" and it doesn't show up. Anybody able to help?
Have you gone into developer options and turned on USB debugging manually?
I would also try revoking authorizations on the phone. Try in ADB and Fastboot both (adb devices / fastboot devices) and see if it registers at all there. Make sure you have the latest SDK/platform tools, try a different cable, different port on the PC, etc. I've also had success with changing the USB mode to the various options (ptp, media, etc). Once you get the phone to show up as unauthorized in ADB you should see the prompt to approve it. I don't think Fastboot asks for auth but if fastboot works and ADB doesn't, it might indicate a problem with the drivers or platform tools version.
They can been picky sometimes.
Exokan said:
Have you gone into developer options and turned on USB debugging manually?
Click to expand...
Click to collapse
Yep, under developer options I have USB debugging turned on.
fury683 said:
I would also try revoking authorizations on the phone. Try in ADB and Fastboot both (adb devices / fastboot devices) and see if it registers at all there. Make sure you have the latest SDK/platform tools, try a different cable, different port on the PC, etc. I've also had success with changing the USB mode to the various options (ptp, media, etc). Once you get the phone to show up as unauthorized in ADB you should see the prompt to approve it. I don't think Fastboot asks for auth but if fastboot works and ADB doesn't, it might indicate a problem with the drivers or platform tools version.
They can been picky sometimes.
Click to expand...
Click to collapse
I've revoked authorizations and plugged the phone into my old Windows 8.1 laptop and right away on the pixel the popup asking to authorize USB debugging popped up. I will try later with the new laptop to see if it'll start working. I downloaded the newest SDK tools yesterday via downloading Android Studio and have the latest platform tools as well during the first time I tried. Will try with a different cable and port also to see if that's the issue, same with fastboot mode.
EDIT: OK, I've tried using 2 different cables now to try and connect the phone to the laptop, one more USB-A to USB-C and a direct USB-C to USB-C connection, both sense the phone but no authorization popup to allow USB debugging on the Pixel. I've also tried to switch different USB mode on the Pixel to different options like PTP, charging only etc. but nothing. No popup.
Toronadian said:
Yep, under developer options I have USB debugging turned on.
Click to expand...
Click to collapse
Sorry, I missed that in your original post. So when you plug the phone in the Pixel isn't showing the little P System Icon? And you're opening the command prompt (not Power Shell) in the same folder as the Tools from here: https://developer.android.com/studio/releases/platform-tools.html ? I honestly don't remember an authorization pop-up so this is weird...
Exokan said:
I honestly don't remember an authorization pop-up so this is weird...
Click to expand...
Click to collapse
It's this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usually comes up the first time you use a given machine to connect via ADB but sometimes gets goofed and you have to remove and reauth it.
Exokan said:
Sorry, I missed that in your original post. So when you plug the phone in the Pixel isn't showing the little P System Icon? And you're opening the command prompt (not Power Shell) in the same folder as the Tools from here: https://developer.android.com/studio/releases/platform-tools.html ? I honestly don't remember an authorization pop-up so this is weird...
Click to expand...
Click to collapse
BINGO. Thank you. I've been using Powershell thinking it's the same for some reason. I use the same Shift+Right Click shortcut and kept clicking open powershell window thinking it's the same. Instead, opened up a proper command prompt window this time (the bar at the top of Windows Explorer, typed "cmd"), and when I typed "adb devices", the authorization popup came and now everything works.
Toronadian said:
BINGO. Thank you. I've been using Powershell thinking it's the same for some reason. I use the same Shift+Right Click shortcut and kept clicking open powershell window thinking it's the same. Instead, opened up a proper command prompt window this time (the bar at the top of Windows Explorer, typed "cmd"), and when I typed "adb devices", the authorization popup came and now everything works.
Click to expand...
Click to collapse
Awesome! And yeah, that's tripped me up before as well!