I have followed the guide, did the edit to the android_winusb.ini and the 0x54c in the adb_usb.ini but I still can't get it to show up as a device when I type adb devices (did restart ADB via adb kill-server after editing the files)
It took me awhile to change the driver for Win 7 recognise it as "Android Composite ADB Interface". I had to use
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4
otherwise it kept saying it couldn't find a compatible driver
Model is SGPT112GB/S
Any ideas?
try this "Auto-Installer". In most cases it has helped.
http://forum.xda-developers.com/showthread.php?t=1488822
Tried it already, didn't appear to work, plus as I ran ADB with it, it said it was out of date
Go into System Devices whilst the Tab is connected via USB, delete and uninstall the device there and the re-install. Thats what i'd to do because the first time I installed it I missed the ox54c bit and it only half installed.
Tried that, adb still doesn't list any devices :/ ADB definitely works as it picks up my phone (X10 mini pro) when I plug that in
Some pictures can help, adb manager, device manager and probably de ini file.
Is your Tablet showing up in Device Manager and if so what as ?
defsix said:
Is your Tablet showing up in Device Manager and if so what as ?
Click to expand...
Click to collapse
{
"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"
}
Before it was showing up under Portable Devices. So I followed the instructions to Update the driver and point to the inf file, but it kept saying couldn't find a compatible driver, so I went into the properties for it and checked the Hardware ID, and it wasn't the same as it said in the guide so I changed it in the inf file, once that was done, I was able to update the driver.
confuserr said:
Before it was showing up under Portable Devices. So I followed the instructions to Update the driver and point to the inf file, but it kept saying couldn't find a compatible driver, so I went into the properties for it and checked the Hardware ID, and it wasn't the same as it said in the guide so I changed it in the inf file, once that was done, I was able to update the driver.
Click to expand...
Click to collapse
As stated in my automated installer, you need TWO devices to show up:
If you're not getting the portable device, you need the MTP driver.
Uninstall both devices and reinstall the drivers or manually force an update on them.
Which OS are you running?
Win 7 64bit, either it shows up under portable devices or under Android phone. Not both. Ive tried your installer but it still doesn't work :/ This probably sounds stupid but if i uninstall, to install again just replug the tablet back in right and do the driver update thing? If not, then maybe thats where im going wrong :S
Update: Ok uninstalled, tried your installer. Now only shows under portable
http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001734.png
CMD prompt that opened afterwards: http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001000.png
confuserr said:
Win 7 64bit, either it shows up under portable devices or under Android phone. Not both. Ive tried your installer but it still doesn't work :/ This probably sounds stupid but if i uninstall, to install again just replug the tablet back in right and do the driver update thing? If not, then maybe thats where im going wrong :S
Update: Ok uninstalled, tried your installer. Now only shows under portable
http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001734.png
CMD prompt that opened afterwards: http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001000.png
Click to expand...
Click to collapse
When you uninstall, did you check the box that says "Delete the driver software..."
Is USB debugging checked on your tablet? You have to have two items in Device Manager. One is to transfer files (MPT/Sony Tablet S under Portable Devices) and the other under an Android heading (ADB).
If you're plugging in the tablet with USB Debugging checked and nothing's showing up, something's wrong with your system. At the very least, you should get an unknown device. Go to "View" and check "Show hidden devices" and check to see if anything's there. Try another USB port.
Bottom line: you need both items.
I followed your video exactly, USB debugging is enabled.
As soon as I plug the tablet in, it looks for new software. It then says successfully installed and pops up with the auto play options. Under devices it shows up under "Portable Devices". If I do the Update Driver, choose the .inf file, it installs but then it no longer shows up under Portable Devices but instead I have the "Android Phone" category with the Composite ADB Interface.
When uninstalling, it only comes up with the checkbox asking delete driver software when I uninstall the ADB Interface one, not the tablet under "Portable Devices"
I have done "Show hidden devices" all that changes is it shows a category called "Non-Plug and Play Drivers"
Confuserr, Im in the exact same position - and on win 7 x64.
Ive done both SDK install and Automated, nothing works.
I never could update the usb drivers though as windows decides the one I have is perfectly good - will try your little trick.
As soon as i get it to work ill post here, just wanted you to know that your not alone in this..
//Cliff
---------- Post added at 04:29 PM ---------- Previous post was at 04:15 PM ----------
And a second later it works atleast in the device manager.
I did the USB driver install according to the guide in the root thread http://forum.xda-developers.com/showthread.php?t=1487020, now unistalled the drivers (2 times) and installed again pointing to the correct location (android/extras/usb_drivers/)
Ran the latest version of the exploit from above thread and done, successfully rooted - now i just need to figure out what to do with my new rights (except taking away social feed reader and speed it up a bit)
//cliff
I can only assume the problem lies in the fact that the ADB guide Sony posted http://www.kb.sony.com/selfservice/documentLink.do?externalId=C1024692
Says
Region
Canada
Latin America
United States
Products
SGPT11 Series
Click to expand...
Click to collapse
Where as my Region is United Kingdom and SGPT112GB/S but im just taking stabs in the dark now
I have reinstalled the entire SDK Manager and still having problems :/
Edit: I've sent an email to Sony, lets see what they reply with
for me it worked after the removal of the old drivers and then using the ones downloaded from google, untuched. My guess is that this will work for you aswell. Good luck /Cliff
confuserr said:
I can only assume the problem lies in the fact that the ADB guide Sony posted
Where as my Region is United Kingdom and SGPT112GB/S but im just taking stabs in the dark now
I have reinstalled the entire SDK Manager and still having problems
Click to expand...
Click to collapse
I don't think it is your region. I cannot get adb to recognize my tab either and I am in the US (not region related). The strange thing is, I was able to ROOT... I also noticed, that while the ROOT tool was running, adb recognized my device. So, when the ROOT tool paused and was awaiting for me to press any key, I decided to mess around with a few codes to see what happened. I input:
Code:
su
mount -o remount rw /system
cp /system/build.prop /sdcard
busybox /sbin/sh
reboot
Everything worked as it should have. While the tab was rebooting, I shout down the ROOT tool, and after the tab rebooted, everything seems to be working as it should.
I have NO CLUE what the hell was going on. But, it works now and that is all that matters to me... Now on to perfect the custom recovery...
UPDATE
I figured it out! It's something with windows. For some reason, it is not starting the adb server... Here is the solution:
In command prompt type (cd to the directory where your adb.exe is):
Code:
adb kill-server
then press enter
Then type:
Code:
adb start-server
then press enter
Then you can go ahead and type:
Code:
adb shell
then press enter
And now you are on your way!
Related
Hi all I'm having problems with getting ADB to see my device and was hoping someone with more brains can help me to solve this problem. I've searched this as much as I can on XDA and Google in general but nothing I find works device specifically.
First setup: I'm running the brilliant ARHD 11.0 JB with build.prop tweaks on top of Siya 1.6.8 and I don't think that Mike and GM need any introduction since they are both household names in our forums.
My machine OS: 7 Ultimate 64
The drivers I've installed: (this might be a factor in the problem)
Latest Kies. I've also installed the s3 drivers when connecting the device in download mode. I have uninstalled Kies because it's unless after the device drivers have been installed IMHO.
The ADB I am trying to use: I downloaded the generic ADB since I think the bridge is generic and mentioning the platform is irrelevant. But it was not the one bundled into the SDK since its not necessary. I have run it as Admin
My problem: I have connected my phone with debug enabled and disabled Auto play but as soon as I "adb shell" in cmd (after cd the adb directory) I still get the "error: device not found" message.
I've tried what I can but can figure it out could someone with the brain. I wish I had please slap me around the room and point out my obvious error and set me on the right path or at least cry with me in my frustration.
If I could get a devs input it would be awesome but if anyone could help me out, I would greatly appreciate it.
Please tell me if I've ommited any important info.
Thanx guys!
CM
christophermaisch said:
Hi all I'm having problems with getting ADB to see my device and was hoping someone with more brains can help me to solve this problem. I've searched this as much as I can on XDA and Google in general but nothing I find works device specifically.
First setup: I'm running the brilliant ARHD 11.0 JB with build.prop tweaks on top of Siya 1.6.8 and I don't think that Mike and GM need any introduction since they are both household names in our forums.
My machine OS: 7 Ultimate 64
The drivers I've installed: (this might be a factor in the problem)
Latest Kies. I've also installed the s3 drivers when connecting the device in download mode. I have uninstalled Kies because it's unless after the device drivers have been installed IMHO.
The ADB I am trying to use: I downloaded the generic ADB since I think the bridge is generic and mentioning the platform is irrelevant. But it was not the one bundled into the SDK since its not necessary. I have run it as Admin
My problem: I have connected my phone with debug enabled and disabled Auto play but as soon as I "adb shell" in cmd (after cd the adb directory) I still get the "error: device not found" message.
I've tried what I can but can figure it out could someone with the brain. I wish I had please slap me around the room and point out my obvious error and set me on the right path or at least cry with me in my frustration.
If I could get a devs input it would be awesome but if anyone could help me out, I would greatly appreciate it.
Please tell me if I've ommited any important info.
Thanx guys!
CM
Click to expand...
Click to collapse
Your problem determinated drivers , install drivers for samsung devices, reboot your pc, connect your device to your pc , expect driver installation , then check if updated , then if the sdk is installed correctly , adb devices.... USB Debugging enabled ......
i had an isssue last night with adb...
unplug phone from pc and turn off and then on usb debuging on the phone...
enter cmd mode on pc, then
adb kill-server
adb start-server
adb devices
then hopefully it will show the device is connected....
p.s. drivers should be installed and checked, this step it is mandatory....
hope it helps ...
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
May this help connect your usb to direct motherboard port. Do not use usb hub if you are
Sent from my GT-I9300 using xda premium
christophermaisch said:
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
Click to expand...
Click to collapse
Debug/test apps on device over the air, no cable. Must-have developer tool. WiFi ADB
You just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny
When you have USB Debugging mode turned on on your phone and you connect to the computer and you look at Device Manager (Win+R, devmgmt.msc) do you see 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"
}
If you get Unknown Devices automatically expanded, then you haven't got the correct drivers installed.
You don't need to install Kies to have the latest drivers installed; you can extract them from the setup itself:
Download KIES and run the setup but don't do anything with it
Open up your Temporary Files folder: Win+R, %TEMP%
Look for the folders that start with a '{' and end with a '}' and have a bunch of letters, numbers and 4 hyphens in them and within this selection of folders find the folder that has its Date Modified timestamp matching the time you opened the KIES installer exe (in my case it was {44A91F3A-3D8C-43DE-A0BC-04E01C756397}). If you're in the right place, you'll find "Samsung Kies.msi".
Grab Less MSIérables, point it to Samsung Kies.msi and extract SAMSUNG_USB_Driver_for_Mobile_Phones.exe somewhere. lessmsi is a little slow...
You'll see a new folder "SourceDir" wherever you chose to extract the file, navigate through it until you find the EXE. Close the KIES installer and run the driver setup
Oh, rather than using some random version of ADB off the Internet, get it from Google themselves. The latest versions can be found in the platform-tools ZIPs for the SDK, but you don't need to install the SDK just for ADB: Open http://dl.google.com/android/repository/platform-tools_r14-windows.zip (14 is the latest version as of this post) and extract the three adb files from the ZIP and place them somewhere. This way you know it's not a problem of using an old ADB version.
You can also check to see if adbd is actually running on the phone when you plug it in by grabbing Terminal Emulator off the market and running: "/system/bin/ps | grep adbd" (note: you only get grep if you have BusyBox instaled)
Finally, if you really can't get USB connections to work, then use https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb&hl=en :\
christophermaisch said:
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
Click to expand...
Click to collapse
Hey,
I had the exact same problem. This Tutorial : http://goo.gl/OS3Vi worked for me.
Hope it helps
I am having some problem remove an Nandroid backup; (it is impossible to remove it either with Root Exporer or in the terminal as root (rm -rf blah)).
However, now I am trying to use ADB to get rid of it I installed adb and some new drivers for my I9300.
Looked through my phone debug-settings, checked if ADB found my phone (adb start-server, adb devices). Then I rebooted my phone into recovery via CWM - however - now my phone does not want to be found.
Windows Device Manager recognize the phone, but the drivers-icon are yellow-ish (not sure if this is how they are supposed to look). adb devices gives me nothing.
I could really use some help over here.
The MoDaCo Mod for MOJO, which adds root and increased Play Store app availability to the MadCatz MOJO, is now available!
The mod takes the form of a Superboot image (as used on many devices previously), with additional features to resolve the Play Store lack-of-apps issue.
What is this?
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
What are the pre-requisites?
You need a MOJO (duh) and a USB Male A-A cable to carry out this process. And a computer I suppose (Windows, Mac or Linux).
Any caveats?
You should note that while rooting may affect your ability to receive future OTAs, reverting back to stock is easy enough. We'll cross that bridge when we come to it.
Download
APPLY THIS AT YOUR OWN RISK!
Superboot MMM³ - DOWNLOAD - MD5: 835de32dd795d2825ade1ed1be422abf
How to use Superboot - Windows, Linux and OSX
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Unplug the power cable and any USB cables (the dongle can stay in), insert the USB Male A-A cable in the port labelled '2.0', then insert the power cable. 'Key driver not found.. Booting OS' will appear on screen.
WINDOWS - install the device drivers from the directory you extracted above if required, then run 'superboot-windows.bat' as Administrator
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by 'sudo ./superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by 'sudo ./superboot-linux.sh'
You will see 'Booting downloaded image' and a black screen, then the screen will return to 'Key driver not found.. Booting OS'. At this point, unplug the USB cable and the power cable, wait a few moments, then reconnect the power cable to boot as normal.
For all the missing apps to show up on the Play Store, you may need to clear data on the Play Store in 'Settings -> Applications' and reboot, then run the Play Store again.
Enjoy!
P
{
"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!
Thank you for kicking off true development for the Mojo to move forward. I'll try this as soon as I can and respond.
you rock!
Now I'm off to get dog food! Oh...I mean I'm using that as an excuse to run and get myself a USB cable. You're awesome, paulobrien. I'll root this evening!
There we go!!! What we've all been waiting for!!!
BTW, what are the changes to the Play Store that enable all the apps?
Thanks for this! Now I need an A-A cable...
Ok it's finaly come so happy thanks Paul O'Brien
I don't understand why my pc won't see my mojo there is no sound when i plug into it i try usb 2 and 3 with a usb 3 male male cable
So after i type reboot bootloader the mojo reboot normaly even if i unplug the power etc... and the pc do nothing
Thanks for what you did this is awesome
Mojo goes into fastboot mode and installed drivers fine. However currently running into issue where when I run the superboot-windows.bat file in admin mode it opens cmd for a second then immediately closes. The mojo doesn't seem to respond whatsoever. Any thoughts?
Ya same here mojo say key driver not found... Booting OS but when I run the .bat file doesnt close just sitting waiting for device
buggin0915 said:
Ya same here mojo say key driver not found... Booting OS but when I run the .bat file doesnt close just sitting waiting for device
Click to expand...
Click to collapse
Are running the bat file as an admin? right click>run as admin
ya ran in admin also tried to run adb just to see if i can connect device but nothing. computer is connecting just not the device with adb/fastboot
2 things to try:
1) Run the bat file in an actual command window to see the output, or edit it and add pause at the end (likely device not found or fastboot isn't in the path)
2) Manually force a driver (I believe the fastboot driver from the Android SDK should be able to be forced, since this is just a Tegra 4 chipset)
To ensure its ready to go, you should be able to write:
"fastboot devices"
And see that there is a device there. I will try when I get my cable
Thanks I'll try out more tomorrow.
For me i have to add absolute filepath to script if i run it as admin
if the folder is under C:\ it is: C:\r1-mojo-superboot-mmm\fastboot-windows.exe boot boot.superboot.img
But just telling me "waiting for device". driver is installed properly and device is recognized as usb device.
saenta said:
For me i have to add absolute filepath to script if i run it as admin
if the folder is under C:\ it is: C:\r1-mojo-superboot-mmm\fastboot-windows.exe boot boot.superboot.img
But just telling me "waiting for device". driver is installed properly and device is recognized as usb device.
Click to expand...
Click to collapse
Could you try editing the batch file, replacing 'fastboot boot' with 'fastboot -i 0x0738 boot'? I don't think that should be necessary on Windows (I use a Mac) but it's worth a try!
P
paulobrien said:
Could you try editing the batch file, replacing 'fastboot boot' with 'fastboot -i 0x0738 boot'? I don't think that should be necessary on Windows (I use a Mac) but it's worth a try!
P
Click to expand...
Click to collapse
Perfect thanks that worked!
saenta said:
Perfect thanks that worked!
Click to expand...
Click to collapse
Ah, awesome, i'll update the script in the zip.
P
Hi i'm facing a problem and i see i'm the only one for the moment
i use a usb 3 male male cable but when i plug into the mojo and pc nothing hapens no sound of windows who say there is an usb plug so maybe it's because i use a usb 3 cable ( the cable is pluged into the usb 2 port )
and the other thing it's when i reboot into bootloader the device reboot normaly i don't see "Key driver not found.. Booting OS"
Download updated to r2 (Windows fix).
P
Dead-neM said:
Hi i'm facing a problem and i see i'm the only one for the moment
i use a usb 3 male male cable but when i plug into the mojo and pc nothing hapens no sound of windows who say there is an usb plug so maybe it's because i use a usb 3 cable ( the cable is pluged into the usb 2 port )
and the other thing it's when i reboot into bootloader the device reboot normaly i don't see "Key driver not found.. Booting OS"
Click to expand...
Click to collapse
Have you followed the instructions precisely or are you trying to do it a different way?
P
paulobrien said:
Have you followed the instructions precisely or are you trying to do it a different way?
P
Click to expand...
Click to collapse
Thanks for reply
Yes i think i'm doing it exactly like it's described
I have no problem with my phone and driver but the mojo looks dead with usb slave
Dead-neM said:
Thanks for reply
Yes i think i'm doing it exactly like it's described
I have no problem with my phone and driver but the mojo looks dead with usb slave
Click to expand...
Click to collapse
You won't see it when you plug it in, open device manager you will see fastboot device without driver.
To install the Mojo driver on Windows 8 you need to disable driver signature checking, else install will fail.
Your USB3 cable is backward compatible to USB2.
Have you taken mojo from power? if you only reboot bootloader you won't see anything.
I rooted my AT&T HTC One and when i was going to flash a rom I accidentally wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now.
Please help please help!!!!!!
coachpete said:
i rooted my at&t htc one and when i was going to flash a rom i accidentally wiped the phone completely. I can go into twrp but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a usb otg cable but the phone didnt seem to recognize it. Please help. I've been stuck without a phone for about a week now.
Click to expand...
Click to collapse
can someone please help me!!!!!!
HTC One not recognized by Windows 7 or Windows 8
coachpete said:
I rooted my AT&T HTC One and when i was going to flash a rom I accidentally wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now.
Click to expand...
Click to collapse
I am baby stepping through the trouble shooting process to try to get an image over to the phone so I can reimage through TWRP v2.7.0.0 but neither my Windows 7 machine nor my Windows 8 machine are recognizing the HTC One as a media device. I have tried the updated drivers with no luck. PLEASE HELP!!
coachpete said:
I am baby stepping through the trouble shooting process to try to get an image over to the phone so I can reimage through TWRP v2.7.0.0 but neither my Windows 7 machine nor my Windows 8 machine are recognizing the HTC One as a media device. I have tried the updated drivers with no luck. PLEASE HELP!!
Click to expand...
Click to collapse
you can use ADB from twrp recovery to push a rom to your /sdcard
follow this guide step by step and quote me here if you have question.
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer, either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\android-sdk-windows\tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery (2.6.3.3 or higher) on your device.
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
Here is a list of the HTC M7 roms
Connect your phone to computer using usb cable
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes and there is no progress bar. When the command prompt give you back the hand and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Computer doesn't recognize my HTC ONE
alray said:
you can use ADB from twrp recovery to push a rom to your /sdcard
follow this guide step by step and quote me here if you have question.
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Click to expand...
Click to collapse
Thank you but my computer does not recognize my HTC one. I have tried installing the drivers from various sources but still no go! please help @alray
coachpete said:
Thank you but my computer does not recognize my HTC one. I have tried installing the drivers from various sources but still no go! please help @alray
Click to expand...
Click to collapse
check step 4 of the above prerequisites, click on ''show content'' then you'll find the instruction how to correctly install drivers.
Still no luck with the drivers
alray said:
check step 4 of the above prerequisites, click on ''show content'' then you'll find the instruction how to correctly install drivers.
Click to expand...
Click to collapse
Followed the detailed instructions for downloading and installing the correct drivers and my Windows 7 machine still does not recognize the HTC One correctly.
coachpete said:
Followed the detailed instructions for downloading and installing the correct drivers and my Windows 7 machine still does not recognize the HTC One correctly.
Click to expand...
Click to collapse
boot your phone in twrp, go in windows device manager and take a screenshot and post it here
when your phone is in twrp main menu, open a cmd prompt and do this command:
Code:
adb devices
what is the output?
FINALLY
alray said:
boot your phone in twrp, go in windows device manager and take a screenshot and post it here
when your phone is in twrp main menu, open a cmd prompt and do this command:
Code:
adb devices
what is the output?
Click to expand...
Click to collapse
Thanks for all your help I am now up and running!!!!!!
Hello.
Could anybody point me towards, or drag me along, a path to revive a Nexus 7, please?
If I have wandered into the big boys forum please feel free to tell me to clear off or, better, suggest an alternative forum more suited to my ability. After two weeks of "research" I am stuck at what I suspect is a simple matter around connectivity. Is this a suitable place to ask for any help & guidance? ; I am well aware that it would be needed in a simplistic form.
As a learning project, I managed to root a Nexus 7 2013 which was displaying problems, and enabled USB debugging.. However, whilst exploring the TWRP options on the Nexus, I wiped everything, including the OS and I had not made a backup.
On a Windows XP tower, I installed Nexus Root Toolkit & an Android OS version plus a multitude of files, such as TWRP & GAPP.
When connected by USB cable, the XP machine finds new hardware, but the installation wizard fails and the Nexus does not show up in Device Manager or elsewhere.
Running NRT shows ADB /Fastboot connectivity as failed. (fastboot gelvar lock)
(I have had no success in trying to follow the NRT proffered solutions including driver updates, although the google drivers show as downloaded.)
On the Nexus I can access the basic TWRP screen and the Android Start screen, from which only the Google lock screen can be displayed.
Thanks for reading so far.
Nexus7 (2013 WiFi) OS 5.1.1
Fastboot mode, Product name Grouper, HU Version ER3, Bootloader version 4.23 Baseband version N/A Signing Not defined Yet, Lockstate UNLOCKED
TW1234 said:
Hello.
Could anybody point me towards, or drag me along, a path to revive a Nexus 7, please?
If I have wandered into the big boys forum please feel free to tell me to clear off or, better, suggest an alternative forum more suited to my ability. After two weeks of "research" I am stuck at what I suspect is a simple matter around connectivity. Is this a suitable place to ask for any help & guidance? ; I am well aware that it would be needed in a simplistic form.
As a learning project, I managed to root a Nexus 7 2013 which was displaying problems, and enabled USB debugging.. However, whilst exploring the TWRP options on the Nexus, I wiped everything, including the OS and I had not made a backup.
On a Windows XP tower, I installed Nexus Root Toolkit & an Android OS version plus a multitude of files, such as TWRP & GAPP.
When connected by USB cable, the XP machine finds new hardware, but the installation wizard fails and the Nexus does not show up in Device Manager or elsewhere.
Running NRT shows ADB /Fastboot connectivity as failed. (fastboot gelvar lock)
(I have had no success in trying to follow the NRT proffered solutions including driver updates, although the google drivers show as downloaded.)
On the Nexus I can access the basic TWRP screen and the Android Start screen, from which only the Google lock screen can be displayed.
Thanks for reading so far.
Nexus7 (2013 WiFi) OS 5.1.1
Fastboot mode, Product name Grouper, HU Version ER3, Bootloader version 4.23 Baseband version N/A Signing Not defined Yet, Lockstate UNLOCKED
Click to expand...
Click to collapse
Did you search/read HERE. That is the forum for the N7. I also have the same model and I also know that posting in that forum will fetch a reply, if at all, at a much later date. That is why I have not moved your thread there.
I also used the NRT in the initial days of my learning process and faced the driver issue also. One solution that worked was to install USBDview and remove all the unnecessary drivers before using NRT for installing drivers and for flashing.
Did you go through the NRT thread for the driver issue?
Thanks. ( I have read through some of the Nexus section threads, but cannot find a suitable solution.)
Using USBDview within NRT enabled me to clear several Nexua & Android items and get folders for Portable Devices and MTR to show in XP Device Manager; however the MTR displays a fault (exclamation) marking, (although it reports as working OK and no better update is found with the wizard.).
Using NRT firstly reports that "updates cannot access serve" and using "Unlock Bootloader" indicates "Fastboot device Connected, before changing the Nexus screen from Start arrow to Google lock screen, At the same time XP reports new hardware found (MTR device) and the wizard reports it as installed
So there must be some form of connection.
However if Full Driver Test is then run, NRT just reports ADR device not found.
TheNRT subsequent suggestions hinge on having USB Debugging toggle access.
Sorry, but I have no idea for a suitable logical rectification route.
Google Asus Nexus 7 (2013) is based on Qualcomm-Snapdragon chipset hence you need to download and install Qualcomm-Snapdragon-suitable USB-drivers ( incl. ADB / Fastboot ) what is a must need to connect a Snapdragon Chipset based device with a computer: the USB-drivers (ADB / Fastboot) what are offered on hundreds of websites - as also here on XDA - are developed by Google for Google Pixel phones, although they may work on other devices, too.
Thanks. I have now got a Qualcomm (unzipped)) folder Driver with sub folders & tried to set this for the MTP device in the XP Device manager. No success, probably due to my lack of knowledge.
How do I proceed, please?
By asking such basic questions, should I abandon the Nexus until I have learned to walk?
TW1234 said:
Thanks. I have now got a Qualcomm (unzipped)) folder Driver with sub folders & tried to set this for the MTP device in the XP Device manager. No success, probably due to my lack of knowledge.
How do I proceed, please?
By asking such basic questions, should I abandon the Nexus until I have learned to walk?
Click to expand...
Click to collapse
In the NRT, there is a section on driver installation and also drivers. After removing redundant drivers with USBDview, try the drivers and methods given in NRT itself. Unless proper drivers are installed, you can't do anything whether with NRT or adb.
Also, try a different PC or laptop.
I tried on a Windows10 laptop but the trial followed exactly the same route as already followed & ended in exactly the same place.
Drivers were installed from within NRT. The NRT signposted ones are Google (No mention of Qualcomm)
Still getting "No ADB connectivity for MTR device"
TW1234 said:
Thanks. I have now got a Qualcomm (unzipped)) folder Driver with sub folders & tried to set this for the MTP device in the XP Device manager. No success, probably due to my lack of knowledge.
How do I proceed, please?
By asking such basic questions, should I abandon the Nexus until I have learned to walk?
Click to expand...
Click to collapse
Why not simply use
{
"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"
}
Thanks. I had already tried that Install wizard, but have repeated it. It runs and reports "Drivers installed" (although I cannot find where). The Nexus still shows in XP Device Manager as a portable device and with MTP showing fault requesting reinstall drivers.
Since there is no proper information about unlocking the bootloader for the newer versions of Oneplus Nord 2, this is how I got it to unlock and actually work.
For my system it did reset the device, clearing all the files and factory restoring the device, just make sure to make a backup before you do anything.
Just like any other post, no warranties or anything, this is all at your own risk.
1: Make sure to enable OEM unlocking and ADB Debugging in the developer options
1.1: To have these options, first go to About phone > Version
1.2: Keep tapping the "Build number" to unlock the developer options
1.3: Navigate back to settings and open Additional Settings. There you will find the Developer Options.
2: Install: Platform tools: https://androidfilehost.com/?fid=17248734326145690420
3: Install: MediaTek Preloader USB VCOM drivers: https://drive.google.com/file/d/1TPbW-v9-yOrzH15OaHmsPQad420mULeF/view
4: CMD to the root of the platform tools and use the command "adb reboot bootloader"
5: While in the weird tiny screen, validate that your device is there by typing "fastboot devices"
6: If so, type fastboot flashing unlock
7: Profit.
Hope this helps any other people searching for a proper way to do this.
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
meterpreter said:
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
Click to expand...
Click to collapse
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Eastw1ng said:
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Click to expand...
Click to collapse
I hope so too. I would really like to put lineage on this thing, probably the only os that can make a usable device out of this actually very good phone
Unlocking the bootloader requires two settings to be made in Android's Developer Options:
ADB Debugging
Allow OEM Unlock
@Eastw1ng, as obvious as this may be once you remember, unlocking the bootloader is something most people don't do very often - it might make sense to include that in the OP
@NetSoerfer, you're not wrong, quickly added it to the start.
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
CapnRene said:
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
Click to expand...
Click to collapse
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
HofaTheRipper said:
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
CapnRene said:
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
Click to expand...
Click to collapse
Can you tell me how to install these drivers I tried but still not detecting
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
X:\Users\XXX>where adb
X:\platform-tools\adb.exe
And system variables
{
"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"
}
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
pankspoo said:
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
Click to expand...
Click to collapse
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
pankspoo said:
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
Click to expand...
Click to collapse
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Eastw1ng said:
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
Click to expand...
Click to collapse
Yes installed
Eastw1ng said:
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Click to expand...
Click to collapse
V10 bootloader means boot.img? If you have that please send me
pankspoo said:
V10 bootloader means boot.img? If you have that please send me
Click to expand...
Click to collapse
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
pankspoo said:
Yes installed
Click to expand...
Click to collapse
Alright, well just put it into fastboot mode and check your device manager, does it show any devices that are not properly installed? If so, try to resolve it from there
Eastw1ng said:
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
Click to expand...
Click to collapse
Thanks