Last week I posted that Odin can't connect to my Galaxy neither under Windows 7 nor under XP Sp2.
Both run on a VMware session (VMware Fusion Version 3.1.3 (416484)) running under OSX Lion 10.7.
When the Galaxy is in 'normal' mode, the drivers are installed normally under the Windows session.
Bur when I put the Galaxy in download mode, the Galaxy is not shown in the 'Removable devices -> USB ' menu, (sometimes is shows 'Samsung Gadget' and then I select 'Connecdt to Windows' but then it desappears.
Here the screenshots:
Peripherals info after connecting the 'download mode' Galaxy to the Mac:
{
"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"
}
Here the selection prompt:
Here the VMware session to select connecting device:
After selecting 'Connect' to the Windows session it is gone !
And also gone from the device list in the first image. It seems it completely disappears.
This is very weird, does somebody else have experience with flashing (attempts) in VMware ?
I have never had this before in VMware, normally VMware runs every Windows task. I flashed Nokia phones with PC Suite without problems.
I can't help you with that but why don't you use Heimdall ?
He should use heimdall, I doubt the working with a VM and Odin.
Sent from my GT-I9000 using XDA Premium App
Related
Somehow adb isnt working for me. Can anyone help? Usb debugging is enabled and lg drivers are also installed.
{
"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 the same issue. I had to choose manually driver adb google interface (newer one). I don't remember full name now and can't check cause I'm on linux.
Sent from my LG-P760 using Tapatalk 2
noob.gamer said:
Somehow adb isnt working for me. Can anyone help? Usb debugging is enabled and lg drivers are also installed.
Click to expand...
Click to collapse
Yes, I've this problem too. In Windows 7, Adb work fine with Stock rom but not CM. But when I use linux adb works for CM. Maybe It's some problem about drivers.
I've been having the same issue with my P769, on AntonX's CM10.1. I'm considering just restoring a Wind backup I have on the SD, since all I need adb for is to replace the recovery. With the stock ROMs, adb was working perfectly fine as well.
If I don't do that, I'll test it out with Linux tonight.
EDIT: Forgot to mention that I'd tried manually installing all the drivers as well. For most of the drivers, no devices were found. For the ADB Testing Interface and the Android Sooner Single Interface drivers, my phone was listed as offline.
Hi all,
I haven't been able to successfully run the included installer to get Remix OS onto a USB stick.
I've tried several different drives on several different PCs (all Windows 10).
Every time, it fails when extracting the system image (I think).
This is as far as I get:
{
"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"
}
And this is the error I get:
I've tried google for help and haven't had any luck, any ideas?
Maybe the download is corrupted...
Try downloading again, and run as Admin.
Which version are you using? EFI or Legacy?
Is the USB stick 3.0? How much space does it have?
More details, please! :silly:
I've downloaded it at least 10 times.
Tried running as admin
Tried running in compatibility mode
Tried both EFI and legacy
Tried two different USB sticks, one 2.0 64GB and one 3.0 128GB
Tried in both a 32bit and 64bit OS
change tool... remix use a kind of unetbootin, try using Rufus or LiLi USB creator (obviously format in FAT32)
Ok thanks, will give those a shot.
I did try with unetbootin which kinda worked didn't quite get there.
had the same issues with a verbatim model 47622 (128Gb usb ssd disk)
rufus finished and boot perfectly
I managed to get it working using a combination of Rufus and the Remix tool.
I have tried everything. drivers, re-downloading ODIN, cords, you name it. Been on it for 5 days and no luck. Anyone out there help me please. Trying to go back so i can get the OTA.
{
"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"
}
cant understand your question
When using odin and I plug phone in, it connects, I add the firmware files to upload to phone. I click start and it gets hung up on the secure connection step and either fails or I have to cancel. It's a common issue but I haven't found any solutions to fix mine. Does that help.
Hi , maybe you can try this:
1. Uninstall Samsung apps like Kies , SmartSwitch
2. Reinstall driver
3. Reset your host file to default (search over the internet how to do that)
4. Reset Windows Defender to default ( search over the internet how to do that for your Windows ...
5. Use another usb cable
6. Put on another usb port 2.0 not 3.0 ...
7. Disable antivirus
8. Clean viruses with malwarebytes antimalware premium ( just to make sure that some virus doesn't make problems)
9. try with old version of odin like 3.12.3
https://odindownload.com/download/#.XOGWdshKjcs
10. Try on another PC .....
Good luck
Troubleshooting Steps on my End:
I started with V14.0 and used the updater to update to 14.1. I'm running the latest version of windows 10 on the PC I'm using, I have adb enabled on the fire 7 (2019) that I'm using and developer options are switched to on, I've tried disabling antivirus software on the Windows device to make sure that the software I have wasn't subtly blocking the connection and I have disconnected and reconnected the fire 7 connection, all to no avail. I have also gone through task manager and closed all of the adb.exe connections between each attempt at opening Fire Toolbox, but the same issue reoccurs.
What it's doing:
When I open the Toolbox, I get the version page, followed by an eternal, "The Toolbox is starting the Android Debug Bridge (ADB) and setting up the environment. Once this process is completed the Toolbox will start." message. I have left it running for more than an hour to see if it was just the fact that I'm using my slower PC to use this tool, but that is not the case either.
Recommendations, tips, or troubleshooting assistance would be very much appreciated in this matter.
I am having the exact same issue, any assistance would be greatly appreciated. Thought at first the cable may only be a charge only cable, swapped out for data cable, same result.
{
"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"
}
The process will hang here for as long as I let it. I am running Windows 10 Home with the latest updates, The tablet is a Fire HD 10 (9th gen) running Fire OS 7.3.2.7,
Thanks in advance for your assistance
Hello,
I hope someone can offer an idea of how to solve issue I'm facing atm.
I have FZ-X1 phone and it's came simlocked from Japan.
I want to run "fastboot oem clearsimlock 0".
I'm trying to communicate to it using fastboot but the problem I have is that once I boot the phone into its stock bootloader, my PC cannot see connected phone in Device Manager:
{
"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"
}
Once phone is fully booted into UI, I can see it recognised running command "adb devices":
I tried both latest Google and original Panasonic ADB drivers available for download. I use Windows 7 x32 version - it shouldn't have issue with drivers signature, right?
Have no clue how to overcome this obstacle. Any ideas or suggestions are very appreciated.
Thanks!
Remove the Google USB driver and the Panasonic ADB driver: All you have to do is to install the proper OEM USB driver suitable for your device:
Download Qualcomm HS-USB QDloader 9008 driver for Windows - 32-bit / 64-bit
You can now download Qualcomm QDLoader HS-USB Driver of 32-bit & 64-bit Installer. We have put up the entire installation process for you.
www.getdroidtips.com
Thank you for your reply! I tried that - unfortunately the phone still not detected by Windows 7 once connected to PC.