Related
Hi,
I recently bought my first Android phone, an HTC Hero, from a helpful eBayer here in the UK. When I got the phone, it had already been rooted and had a custom ROM, v4 RC1 of EzHero, installed.
I want to update this custom ROM to v5.1, because there are some problems with the current version that's installed. (For example, the phone doesn't ring because there are no ringtones installed! Also, the camera doesn't work, and the phone crashed and rebooted whilst I was in the middle of a call last night.)
So, after some reading around on these forums, I tried following the instructions on this thread: http://cleanimport.xda/index.php?threads/709220/. The basic first step is to download the SDK from Google and instruct it to download the USB driver. So far so good. (I am using Windows 7 BTW.)
However, I have been unable to get the USB driver installed correctly, such that when I run the command:
Code:
adb devices
I get nothing back. (Not strictly true -- the first time I ran it it said it was starting a daemon, then said something like "devices list", but listed no devices. The second time I ran it, it didn't mention the daemon, but still didn't list my device.)
When I connect the phone to my computer (via USB, and with USB debugging enabled), I basically get a balloon at the bottom right of the screen to say that it is installing drivers, and then it says it had some problems. It lists out several devices, each with a green tick or a red cross against them. Invariably, one of the devices listed is called simply "ADB", and it always has a red cross against it. I am not specifically prompted to point the system towards any drivers for the device.
If I go into Device Manager, I currently see, under "Other devices", three devices:
- ADB
- Multimedia Controller
- Multimedia Video Controller.
The icon for each of these has a little yellow exclamation mark. If I double-click on ADB, I am given the chance to Update driver. Doing this gives me two options, and I choose "Browse my computer for driver software". This prompts me to "search for driver in this location" and I choose "C:\android-sdk-windows\usb_driver". (I have also tried pointing it to the subfolder "i386", but this gives the same result. I am on a 32-bit Intel system.) There is also a checkbox "Include subfolders", again I have tried both options, and both lead to the same outcome.
I then click Next and receive this error message:
Windows was unable to install your ADB
Windows could not find driver software for your device.
[...]
Click to expand...
Click to collapse
If, instead of clicking Next, I click "Let me pick from a list of device drivers on my computer" and then select "Mobile devices" and click Next, I am presented with a blank list and a button reading "Have Disk". Clicking on this lets me browse, this time, for an .inf file. But selecting the android_winusb.inf file gives the following error message:
---------------------------
Select Device
---------------------------
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a
driver, make sure it is designed to work with Windows for 32-bit systems.
---------------------------
OK
---------------------------
Click to expand...
Click to collapse
This is about as far as I have got! I have tried experimenting with a couple of things, but with ultimately the same result:
Running (as administrator) USBDEview and uninstalling anything that starts with HTC, or ADB, or Android, or USB Mass Storage device
Editing the .inf file using the modifications described below:
The first modification I tried is described in comment 44 of issue 1039 on the Android Google Code forum (link removed because I don't have permission to post external links!):
Code:
;HTC Hero
%USB\VID_0BB4&PID_0FFE.DeviceDescRelease%=androidusb.Dev, USB\Vid_0bb4&Pid_0ffe&Rev_0100
You can find / adapt those description with your material manager (look in advanced tabs)
To have a nice name of device, add at the end of file something like
USB\VID_0BB4&PID_0FFE.DeviceDescRelease="HTC Hero rev 0100"
The second modification I tried is described in comment 99:
Code:
[Google.NTx86]
; HTC Hero
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9A
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9A&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C9A
And the third is described in post 2 of a recent Android Developers Google
Groups thread entitled "cannot install USB drivers for HTC Slide, Android 2.1, Windows Vista 32 bit" (link removed because I am not allowed to post external links!). For this one, I consulted the information displayed when I go into Device Manager > ADB > Properties > Details > Hardware Ids, so the actual lines I added to the .inf file are as follows:
Code:
;HTC Hero 2.1
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&REV_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
I also tried a slight twist on this:
Code:
;HTC Hero 2.1
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
since all the other devices in the .inf file didn't include the &REV_0100&MI_01 parameters for the %SingleAdbInterface% line.
Finally, I also tried various times to uninstall devices from Device Manager, e.g. ADB, the two multimedia controllers with exclamation marks against them, and USB Mass Storage Device (which does indeed have three lines on the Properties > Details > Compatible Ids screen, as advised by a blog post I found on the Android Simplicity blog entitled "How-To #0: How to Install Usb Driver on Your Computer" (link removed because I do not have permission to post external links!).)
I really can't think of much more to try, so would really appreciate any pointers, however small, from the experts!
Another option might be to give up on Windows and try doing the whole process under Ubuntu Linux, which I have installed under dual-boot. However, the instructions for updating ROMs/making backups/recovery/etc. appeared to rely on some Windows executables so I figured that could be a risky approach (especially given I know very little about how to work Linux...!).
Thanks for reading
Michael
Don't need them. Get the latest HTC Sync and install the My HTC driver and adb will work.
Thanks for such a quick reply btdag!
Really? That would certainly make things a lot easier, however dreamersipaq does make a point of reinforcing how important it is not to have HTC Sync installed in his instructions:
At this point, I'm going to ask that you uninstall HTC Sync. Also, please uninstall HTC Driver... (whatever it's called) Nobody likes them (really though, it will mess up a lot of things. You can install them later when all this is done)
Click to expand...
Click to collapse
[...]
HTC Sync does not like to play nice with the reflash tool
Click to expand...
Click to collapse
[...]
Ok, at this point, I'm going to ASSUME that you don't have HTC SYNC installed (or uninstalled it)
Click to expand...
Click to collapse
Does this not matter after all?
To get adb working I just installed the latest HTC Sync and drivers and then added ;C:\Path\To\SDK\Tools to my Windows Environment Variables as described in this guide:
http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735&sid=d1d70142a6264965b8c370bf1afa64d0
no problems with adb since
As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!
Thanks for all the help.
I'm pleased to say I've now managed to install the update, and my phone is now ringing!
In the end I worked out that I did not in fact need ADB at all. Since the phone had already been rooted and had a custom ROM installed, it dawned on me that it must already have the requisite recovery image installed. And indeed it did. So all I had to do was install Titanium Backup, back up my apps and settings, also take a nandroid backup just to be on the safe side, and then factory reset/wipe and install the update. (And then restore apps and settings using Titanium Backup.) Problem solved!
As an aside, I think there is certainly scope for more 'newbie' documentation. (Or would this be on the Wiki, currently down?) I'm certainly very grateful to those who have taken the trouble to set out what they have learnt already, for the benefit of others. For example though, even after spending several hours searching and reading up all the newbie guides I could find, I still had to read between the lines quite a lot to work out what a 'radio' was, what purpose the recovery image serves, how ADB fits into the whole picture, why there are multiple custom ROMs available for the same version of Android and how to choose one, etc. Perhaps one day I will be advanced enough to attempt that myself!
CyberWalrus said:
As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!
Click to expand...
Click to collapse
Thank you very much! I was reading this trying to get my G1 to work and it did. Windows 7 x64 won't allow me to install the android_winusb.inf driver but droid explorer did.
Phone nor computer will recognize adb/usb
First of all, my is rooted but somehow the superuser.apk file is missing. When trying to activate wifi tethering it asks if the device is rooted. The answer is, yes! I can boot into recovery mode but I do not have a way to get the superuser to open without adb. Can anyone help me?
Unable to Instal ADB Drivers
I'm having similar issues trying to root my MyTouch 4G. I've been following steps on the cyanogen wiki website for this device, which refers you to their site's instructions for setting up SDK & ADB drivers.
I've downloaded the SDK zip file, extracted to the C drive and made sure file paths are all the same as per the instructions. When following the instructions under Windows, I've added to variable values ;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools (and double checked these folders on C drive to be sure they're accurate).
When trying to manually update device drivers for ADB, I select the file android_winusb.inf and get error: "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
My device has USB debugging enabled and is in mass storage mode (I've read on other forums that this can fix).
Not really sure what else to try? Any way I can change the .inf file to make Windows recognize it? Running Windows Vista 64.
A tutorial for how to get ADB and DroidExplorer up and running for your Rhodium in Windows Vista.
All this information exists in bits and pieces of posts throughout this (and other) forums, though I felt it would be helpful to compile it in one place.
If you’re running a different version of windows, the differences should generally be fairly minor. Please let me know if there’s any mistakes or modifications I should make here.
ADB refers to the Android Debug Bridge, a tool put out by google, which lets you access your android device via the USB connection for the purposes of debugging it. One particularly useful component is the ability to access your phone from your PC via a terminal window (similar to a command prompt). While not necessarily intended for this purpose, it may be used for a rudimentary level of USB access to transfer files to and from your device. It will NOT let you have any of the advanced functions that a native driver would.
Optional First Step: Download ADB from Google:
You may choose to install the SDK yourself, but this will be incorporated in your installation of DroidExplorer in step 4 if you don't already have the SDK installed.
ADB is part of the Android SDK (Software Development Kit), which you can download from:
http://developer.android.com/sdk/index.htmlInstall the most recent version for windows. For simplicity sake, I suggest you extract/install it to the root, so for example, to
C:\android-sdk-windows\
Optional:
To make your life easier, it’s a good idea to add the folder containing adb to your system environment path, so you can use adb from anywhere on your drive.
To do this, right click on My Computer, click ‘Advanced System Settings’, and then click on ‘Environment Variables’.
Choose one of the PATH variables (either for your user, or the system wide one), and add the path containing the adb.exe file. For example, if you extracted the sdk to the root of C drive as I had suggested, the path would be:
[blah blah, preceding path values] ;C:\android-sdk-windows\platform-tools\
Make sure you remember to have a semicolon preceding the path you’re adding, so windows knows it is separate from the previous entry.
Second Step: Remove previous drivers:
If you have tried to connect your phone (in android mode) to your PC, you may need to go to the device manager and remove the incorrectly-installed drivers.
Third Step: Install Drivers:
The key obstacle here is that there is no driver made by HTC (or others) specifically to connect the Rhodium in Android mode to a PC. While there may eventually one day be such a driver, we need to resort to a work-around.
Drivers Option #1:
A product called PDANet installs software on your android phone and your windows PC that then functions as a PC and device driver set. (The application has other intended uses, as you can read on their website, but these are secondary to our purpose).
Download and install the latest version of PDANet, on both your android Rhodium (via marketplace) and your PC (via the below link):
http://www.junefabrics.com/android/index.php
You will then need to follow the prompts to connect your phone, select the manufacturer (HTC), and the HTX XDA Driver will be installed. Windows security may require you to approve the installation, as the driver is unsigned. After installing, you will need to restart your computer before the drivers will work.
As part of the install, you will be asked to connect your RHOD phone to your computer via the USB cable. The new hardware wizard should pop up, and you should choose to install the driver automatically (given that you’ve previously placed the driver onto your system with PDANet – if you’ve managed to locate the specific driver file as I’ve heard rumors of, then browse to that file).
USB Debugging needs to be enabled on your device, which it is in the stock builds provided here (Settings->Applications->Development->USB debugging).
Drivers Option #2:
Install the HTC Sync Drivers - this has been described for Windows 7, although there are mixed reports as to the success. Information is in the below links:
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
Optional:
To check that your phone is working, type ‘adb devices’ into your command prompt. If you see your device, you’re good to go. (if you didn’t set the environment path to include the location of adb.exe, you’ll have to either cd to the directory first, or type
C:\android-sdk-windows\platform-tools\adb devices(if you installed the sdk elsewhere, then modify the expression appropriately
What can you do now? To see a list of commands you can use, simply type adb from the command prompt.
To use adb to send a file ‘picture.jpg’ to your sd card, in your command prompt, go to the location of the picture, and then type :
adb push picture.jpg /sdcard/to see the contents of /sdcard , type:
adb shell ls /sdcard/Read more about ADB here: http://developer.android.com/guide/developing/tools/adb.html
And for more details on setting up and using ADB, see this (the source for this workaround):
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
--
Fourth Step: Install Droid Explorer
Now that this is working, you may appreciate an application called DroidExplorer, which gives you a GUI that lets you navigate your device in a manner similar to windows explorer. From here, you can copy, move and delete files, as well as install and uninstall applications.
Download and install DroidExplorer from here:
http://de.codeplex.com/
Startup DroidExplorer, and you’re finished. Do read up on ADB and DroidExplorer on their respective pages so that you know both what you can do as well as what you might inadvertently break by blindly playing with options.
As has been said frequently on this website, if you want safe, stick to the default ‘stable’ XDAndroid install for the Rhodium, and keep your windows mobile running as a backup. If you want more, know that you’ll have lots of learning to do, and potentially may loose all the data on your phone and need to spend hours learning and fixing it. You may even brick your phone (make it unusable and unsalvageable – make it about as valuable as a brick).
Helpful Links:
The wiki for ADB on XDAndroid:
http://xdandroid.com/wiki/FAQ#What_is_ADB_.2F_How-To_ADB
Original xda thread on getting USB to work on the rhodium:
http://forum.xda-developers.com/showthread.php?t=849718
If you have any additional comments/changes to suggest, please let me know, and I’ll modify this initial post.
Heh, I always meant to turn that "original XDA thread" into an ADB tutorial for Windows users... but I just never got around to it.
Thanks for putting this together - do you mind if I reference it in the FAQ?
Just skimmed over the how-to - perhaps you should mention that in lieu of the Android SDK, you can simply download Droid Explorer. It usually takes care of the nitty gritty stuff, but pdanet seems to fill in the gaps with driver issues...
I actually found the drivers we needed (XDA in Device Manager)
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
AkumaX said:
I actually found the drivers we needed (XDA in Device Manager)
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
Click to expand...
Click to collapse
Droid Explorer took care of all the drivers for me on Windows the first time. The second time, PDA.net took care of them for me. I had issues with a ton of different drivers the second time around; even tried wiping them from the system, etc... PDA.net was the only solution that worked for me, as you can see in the linked thread I started.
arrrghhh said:
Droid Explorer took care of all the drivers for me on Windows the first time. The second time, PDA.net took care of them for me. I had issues with a ton of different drivers the second time around; even tried wiping them from the system, etc... PDA.net was the only solution that worked for me, as you can see in the linked thread I started.
Click to expand...
Click to collapse
I installed Droid Explorer and was left w/ 3 (!) Drivers missing, CDC abstract control model ACM x 2, and XDA. After I installed the HTC Sync drivers, it found the driver for XDA and then that gave the ability to let Droid Explorer install the other two *shrugs*
AkumaX, which version of windows did you get the drivers working with? Had you previously tried to install other versions of drivers, or was this 'fresh'? I haven't tried this route (being happy with my PDANet drivers working) - would you say the instructions are good on: http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
arrrghhh, please go ahead and link to this post. I had included the SDK portion because I had mis-read the droidexplorer main page, where the author stated his intent to stop updating the SDK and default to the pre-installed SDK. I see now that he intends to link to the SDK, and thus facilitate its installation for the user. I'll update that in the first post.
slycker said:
AkumaX, which version of windows did you get the drivers working with? Had you previously tried to install other versions of drivers, or was this 'fresh'? I haven't tried this route (being happy with my PDANet drivers working) - would you say the instructions are good on: http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
arrrghhh, please go ahead and link to this post. I had included the SDK portion because I had mis-read the droidexplorer main page, where the author stated his intent to stop updating the SDK and default to the pre-installed SDK. I see now that he intends to link to the SDK, and thus facilitate its installation for the user. I'll update that in the first post.
Click to expand...
Click to collapse
I'm using Win7-64 bit, so I used those drivers. It was a fresh install, and I never even thought to use PDANet, my own searching stumbled upon that thread for the HTC Sync Drivers. It could be better that you install the HTC Sync Drivers before Droid Explorer, but I'd have to find another 'clean' system to try on
AkumaX said:
I'm using Win7-64 bit, so I used those drivers. It was a fresh install, and I never even thought to use PDANet, my own searching stumbled upon that thread for the HTC Sync Drivers. It could be better that you install the HTC Sync Drivers before Droid Explorer, but I'd have to find another 'clean' system to try on
Click to expand...
Click to collapse
That's what VirtualBox is for! lol.
yes i can install usb drivers thank you !
Sorry to make a whole thread for this, but I don't have enough posts to post in the development section thread.
I'm trying to run S-OFF, and the HTC drivers we're told to first download from the site (the standard lazy panda page, I can't link it because I don't have enough posts..). Don't seem to work for me. The most certainly say "windows" next to the download link, but when I run it, it says, "This driver installer is not supported in this operating system!"
Now I am running windows 8, but I've seen several posts from people running W8 on the S-OFF thread saying that it worked flawlessly for them. I also tried running the installer in both windows 7 and windows xp compatibility mode.
Any ideas?
download the ones in regawmod thread. make sure you install the 64bit drivers if you are running 64bit. I believe the ones in lazy pandas are 32bit drivers.
Well, I gave that a shot. They unfortunately seem to be the exact same drivers, or at least with the exact same file name. Either way, I got the same error with those
And you're right, I am on 64bit. I don't see any place to download different versions of the drivers. Both those pages only give one option.
Shadnic said:
Well, I gave that a shot. They unfortunately seem to be the exact same drivers, or at least with the exact same file name. Either way, I got the same error with those
And you're right, I am on 64bit. I don't see any place to download different versions of the drivers. Both those pages only give one option.
Click to expand...
Click to collapse
I keep having the same problem. And everywhere i have looked it the same driver. I might try and download the latest HTC Sync to see if that helps.
I am running Windows 8 64-bit, and found the solution after researching. You need to expand a zip of the HTC drivers, launch device manager, locate the unknown device identified with a question mark that represents your LTEVO, right click on this icon, and manually install the drivers by browsing to the location where you expanded the drivers. Try that!
I believe I followed this exact procedure, although for the One X, works for the LTEVO:
http://forum.xda-developers.com/showthread.php?t=1775870
Sent from my LTEVO via XDA Premium
I've been unable to install the ADB drivers for the Nook Tablet on Windows 8. I get as far as browsing to the folder which contains the inf file after clicking on Have Disk... and I get a message saying Windows could not find driver software for your device. I've tried on two different computers.
Has anyone had any luck installing the ADB drivers for the NT? I'm running Windows 8 RTM.
question: why would you have windows 8...
whatever
If I am correct I heard you need to disable drivers signature checking by Windows (google it, shouldn't be hard) and then it works like 7.
get you started:
http://www.google.com/search?client...pw.r_qf.&fp=5cc52e1fec28dbe3&biw=1333&bih=602
424aca said:
question: why would you have windows 8...
whatever
]
Click to expand...
Click to collapse
Because many people are allowed to have it for beta testing as well as corporate enterprise testing. It isn't pirated if that is the reason for the why followed by the whatever.
my bad homie, wasn't accusing you of nothing
but my reply did it work?
(Shrug) I didn't post with the problem I was just addressing what seemed like a possible disgust emotion brewing for having pirated software. Just wanted to set the record straight for those not in the know about Win 8's release status.
Hello...these forums seem to be both about older Dell Venue 8 models and also the newish Venue 8 7000 (7840). I do not know if they are supposed to be the same for rooting purposes.
I am not a complete newbie, having rooted several phones and tablets in the past, but I did that by faithfully following setp-by-step instructions I found here. I did find the following thread:
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
which seems to be relevant for the 7840, but post#1 assumes much prior knowledge and is beyond my capability to follow and implement.
Any advice or guidance would be appreciated, and pointing me to a set of instructions that doesn't assume much expertise would be fantastic.
Chuckles960 said:
Hello...these forums seem to be both about older Dell Venue 8 models and also the newish Venue 8 7000 (7840). I do not know if they are supposed to be the same for rooting purposes.
I am not a complete newbie, having rooted several phones and tablets in the past, but I did that by faithfully following setp-by-step instructions I found here. I did find the following thread:
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
which seems to be relevant for the 7840, but post#1 assumes much prior knowledge and is beyond my capability to follow and implement.
Any advice or guidance would be appreciated, and pointing me to a set of instructions that doesn't assume much expertise would be fantastic.
Click to expand...
Click to collapse
That is what I used.
bamfsig45 said:
That is what I used.
Click to expand...
Click to collapse
That may be, but as I noted above, I cannot follow these instructions. The poster himself/herself notes that these are rough notes. Would anyone be able/willing to provide a walkthrough for non-experts?
If you have any fear, do not proceed or get help from a knowledgeable warm body
Chuckles960 said:
That may be, but as I noted above, I cannot follow these instructions. The poster himself/herself notes that these are rough notes. Would anyone be able/willing to provide a walkthrough for non-experts?
Click to expand...
Click to collapse
@Chuckles960 - I know this isn't the answer you want to hear, but I would not attempt this method if you in any way feel uncomfortable with the process. The Venue 7840 does not have any 'reverse'/unbrick procedures out there (as of yet). Also, Dell does not offer their ROM for reinstall like other manufacturers do. However, there is a link to a full Nandroid backup of the 4.4.4 stock ROM within the Venue General forum.
Have you ever installed recovery, unlocked bootloader(s) or rooted any other Android devices?
-Jay
PS - By 'knowledgeable warm body', I didn't mean it offensively. Just a friend or someone you can meet locally that can help you in person. Trust me, this is hard to translate over a forum. I just want to make sure you don't have any frustrations with your Venue. Congrats on the purchase!
It's easy...
1) Install the Intel ADB Drivers from: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
(Use compatibilty mode if you are using Windows 8.1)
2) Device Manager may not properly detect the drivers so you have to specify the Android ADB driver from the install folder above.
3) Extract IntelAndroid-FBRL-01-17-2015.7z into a folder.
4) Copy UPDATE-SuperSU-vX.Xx.zip to the internal storage or SD card
5) Run launcher.bat and and make sure it detects your device in debug mode (Turn on debug from Settings on the device.)
6) Choose the T3 mode and wait for Fastboot to load and select the SuperSU zip and install. Reboot... It should be rooted.
This worked for my 7840 and 3840...
And, in case you were not aware, enable USB Debugging on your 7840. After doing so, upon the first cable connection to the PC, a pop-up will appear asking for permissions to connect. Be sure to approve this.
DanielNTX said:
It's easy...
1) Install the Intel ADB Drivers from: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
(Use compatibilty mode if you are using Windows 8.1)
2) Device Manager may not properly detect the drivers so you have to specify the Android ADB driver from the install folder above.
3) Extract IntelAndroid-FBRL-01-17-2015.7z into a folder.
4) Copy UPDATE-SuperSU-vX.Xx.zip to the internal storage or SD card
5) Run launcher.bat and and make sure it detects your device in debug mode (Turn on debug from Settings on the device.)
6) Choose the T3 mode and wait for Fastboot to load and select the SuperSU zip and install. Reboot... It should be rooted.
This worked for my 7840 and 3840...
Click to expand...
Click to collapse
Chuckles960 said:
That may be, but as I noted above, I cannot follow these instructions. The poster himself/herself notes that these are rough notes. Would anyone be able/willing to provide a walkthrough for non-experts?
Click to expand...
Click to collapse
I'm right there with you - The challenge I'm having seems to be more with the Windows drivers... it always sees the device as MTP or just a portable device regardless of having the Intel and pointing Windows to the Intel install folder. Can't seem to get it to recognize the device correctly.
In my case I to select the ADB Interface driver manually (can't remember exactly) rather than relying on Windows to identify which driver it needed on it's own. IIRC you have to click 'Have disk' and go through the steps there until you get two lists, one of manufacturers and the other of device types. You're looking for an intel ADB interface or similar.
anggusss said:
In my case I to select the ADB Interface driver manually (can't remember exactly) rather than relying on Windows to identify which driver it needed on it's own. IIRC you have to click 'Have disk' and go through the steps there until you get two lists, one of manufacturers and the other of device types. You're looking for an intel ADB interface or similar.
Click to expand...
Click to collapse
This was the piece I was missing!!!! I used the Have Disk and managed to load the ADB driver that way. THANK YOU!
Thanks to all for the tips! I will try it now.
Question: there is a Lollipop update promised for this month (or so). Will I be able to root again after the update, using the same procedures? (I am sure this is a naive question.)
DanielNTX said:
It's easy...
1) Install the Intel ADB Drivers from: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
(Use compatibilty mode if you are using Windows 8.1)
2) Device Manager may not properly detect the drivers so you have to specify the Android ADB driver from the install folder above.
3) Extract IntelAndroid-FBRL-01-17-2015.7z into a folder.
4) Copy UPDATE-SuperSU-vX.Xx.zip to the internal storage or SD card
5) Run launcher.bat and and make sure it detects your device in debug mode (Turn on debug from Settings on the device.)
6) Choose the T3 mode and wait for Fastboot to load and select the SuperSU zip and install. Reboot... It should be rooted.
This worked for my 7840 and 3840...
Click to expand...
Click to collapse
This worked fine on my 7840, but only after some struggling with drivers. I have Win8.1 64bit, and the ADB driver from these instructions (line#1) did not work. Going back to the main thread (linked in the first post on this thread) and paging through to (I think) page 10, I found a link to Win8.1 ADB drivers and those worked.
Other than that, everything went smoothly. Thanks to everyone who responded helpfully!
Now what happens when we get Lollipop? TBD?
Chuckles960 said:
This worked fine on my 7840, but only after some struggling with drivers. I have Win8.1 64bit, and the ADB driver from these instructions (line#1) did not work. Going back to the main thread (linked in the first post on this thread) and paging through to (I think) page 10, I found a link to Win8.1 ADB drivers and those worked.
Other than that, everything went smoothly. Thanks to everyone who responded helpfully!
Now what happens when we get Lollipop? TBD?
Click to expand...
Click to collapse
Exactly! If SuperSU build supports that version of Lollipop, the tethered CWM should hopefully work ONLY if Dell doesn't have some f***ery in any new boot.img updates
Thanks for making this thread, I just successfully rooted my 7840. Now hopefully Dell comes out with a lollipop update and we still keep root :fingers-crossed:
Has anyone tried this with Lollipop yet ?
I accidentally (!) installed the OTA.
I wanted to install LinuxDeploy
Many thanks
Old method not working with latest lollipop update...
Can someone post the screen shot of trigger T2 from the tethered cwm recovery , I know it doesn't work but I need to see the batch screen output.
screens T2 T3
here r the screens for T2 , cannot attach pictures or 2 dumb
https://drive.google.com/folderview...I1REJPOVZhWEx5dlNGZF9iV1MzNnJ0c3c&usp=sharing
and T3
https://drive.google.com/folderview...BkRm5DUHdFbkJqdVpIVXJjM1FicGNtWjg&usp=sharing
Bad news on the root and 5.0.2. I feel pretty confident that it will eventually come to be. I just wish there were more development and fanfare for the 7840. It is such a stunning piece of technical
Gonna need a couple testers soon, think I found away just need to work out a few kinks,
I have an early test ready if interested reply to this post.
yeah, i'm in :good: