Related
Hey, I was wondering if anyone had a link to download the HTC Bootloader drivers. It fails when I try and load "something" in Windows.
Thanks.
p.s: This will lead to good things...
The only drivers that I am aware of are the ones that are in the Android SDK Toolbox and in the HTC Sync program. Correct me if I am wrong, but as far as I know, they aren't specific drivers ie "bootloader" drivers. They are just drivers to get your comp to recognize the phone when its attached.
I'm assuming this is something you're expirementing with to get root via the adb in recovery, if so, good luck.
-------------------------------------
Sent via the XDA Tapatalk App
Hi crax0r,
The folks at Android (aka Google) provide these instructions for installing the drivers. It involves installing their SDK first, and installing Java for that, and an IDE called eclipse.... UGH.
The HTC "Sync" Application that hoovnick is referring to can be found here.
It has been so long ago that I installed drivers (on a WinXp x32 laptop) that I can't remember what order I did things in, whether or not the driver used by HTC sync is sufficient for fastboot but not adb (or vice versa), whether I did the SDK install first, etc etc etc. As a matter of fact, it's been so long ago that the computer that I did it on is now dead, and here I am using a Linux machine.
For all I know, the order you do things in affects the outcome - it sure seems like a lot of folks with Windows 7 complained about driver troubles.
One thing is for sure, though - setting up the entire Android SDK (+ Java + Eclipse + ...) in order to install a device driver has to be the worlds most roundabout way of doing a driver install.
If you are considering using the "fastboot" method to install Amon_RA's recovery boot, you might try just installing HTC Sync first, and see if that is sufficient for getting fastboot talking to the phone. That install is way, way easier than setting up the SDK to get a driver installed.
The other thing which is an option, if you are a little bit Linux-savvy, is to boot one of those "Live CDs" (Ubuntu, SuSe, etc) on your PC - there are no drivers to install in the case of Linux, you just need to be running as "root" on the Live (linux) CD to get fastboot to talk to the phone. The downloads (fastboot for Linux and the Amon_RA recovery image) are small, and they will both easily fit in the /tmp folder of the Linux (Live CD) boot on the PC.
Once you have Amon_RA on the phone, you won't need the SDK any longer, unless you want to start doing dev-like things; that's why a one-time boot into Linux would also work.
bftb0
I <3 Ubuntu. It's amazing!
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
crax0r said:
It's OK. I'm running Ubuntu now.
Click to expand...
Click to collapse
Excellent. Just remember to always run fastboot as root, and if using adb, then the first time after you boot (the PC), run adb as root.
The reason is that by default, Ubuntu won't let an unprivileged user access the USB.
Since I have adb and fastboot in my Ubuntu (regular user) PATH, I usually just do a
$ sudo `which adb` blah-blah-blah
or
$ sudo `which fastboot` blah-blah-blah
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
I don't know - I've already forgotten everything I did with the driver install in Windows, and I don't currently have a working Windows machine. Sorry I can't be of more help. As I said, the troubles people have been having seem to depend on which version of Windows (Xp/Vista/7), whether its x32 or x64, phase of the moon, etc. Seems like people run into snags on Win7 or x64 versions of Windows more than Xp-32, but I don't know why that is.
Keep plugging away at it. If you are looking for resources to help resolve the problem, I would go look at docs relating to Windows driver install troubleshooting - the driver install problem seems to be a Windows issue, not really anything to do with the SDK.
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
Sounds like what happened to me. i had to hit the icon at the top of my phone that showed the usb cable.. i had to switch charge only to disk drive "mount as disk drive"... folder popped right up on my windows machine asking how i wanted to open the file
I have the SDK running and my phone being recognized on my computer with Vista but I have another one running XP 32 bit and windows will NOT recognize the .inf? Any ideas? I deleted all previous HTC drivers and tried that approach but nothing seems to be working.
downloaded all the stuff from the thread. everything went smoothly. i watched the video step by step. after uploading the usbdrivers to my NT it said
"Android ADB interface" instead of "android composite ADB interface"
it shows up in my device manager as a nook tablet still.
i derped. so i thought it would be ok anyways and then tried to zerg rush the baster-ahem NT only to see that the Zerg didn't even find my device.
i promptly decided to just wipe everything from my nook and start fresh but also every single thing i tried has failed to get rid of that blasted "android ADB device" from the one click unroot thing to doing a 8 step reset thingy and just plainly reset and wipe data from the stock settings, and now many hours later i have had enough and decided to swallow my pride and flaunt the noob card. i need help. i must find a way to wipe everything or maybe i can take a step from here. i dunno. derpy derp.
windows 7 ultimate 64bit
nook tablet 8 gb sd card.
(^^this is how people write these things right?)
wagon_burner said:
downloaded all the stuff from the thread. everything went smoothly. i watched the video step by step. after uploading the usbdrivers to my NT it said
"Android ADB interface" instead of "android composite ADB interface"
it shows up in my device manager as a nook tablet still.
i derped. so i thought it would be ok anyways and then tried to zerg rush the baster-ahem NT only to see that the Zerg didn't even find my device.
i promptly decided to just wipe everything from my nook and start fresh but also every single thing i tried has failed to get rid of that blasted "android ADB device" from the one click unroot thing to doing a 8 step reset thingy and just plainly reset and wipe data from the stock settings, and now many hours later i have had enough and decided to swallow my pride and flaunt the noob card. i need help. i must find a way to wipe everything or maybe i can take a step from here. i dunno. derpy derp
windows 7 ultimate 64bit
nook tablet 8 gb sd card.
(^^this is how people write these things right?)
Click to expand...
Click to collapse
hm... well not sure if this is hidden anywhere in your description but did you try reinstalling the nook tablet drivers? since you have android adb device right now, uninstall that and if windows prompts you to restart you should do that. When you uninstall the adb drivers if there is a checkbox saying delete driver software for this device make sure to check that as well. basically what i am trying to say is you want to start fresh as in there should not be any reference to android or nook on your windows pc
another program that may be helpful is using usbdreview which is a program that monitors all devices with usb drivers. this may help is attempting to delete any reference to android and nook on your windows pc. hope this helps!
EDIT: just to add this tidbit in, if your having troubles with ADB, chances are it has nothing to do with your NT but rather with the drivers that Windows has installed already. There's a guide to installing ADB correctly, here's a link:
http://forum.xda-developers.com/showthread.php?t=1424563
ShinnAsuka said:
hm... well not sure if this is hidden anywhere in your description but did you try reinstalling the nook tablet drivers? since you have android adb device right now, uninstall that and if windows prompts you to restart you should do that. When you uninstall the adb drivers if there is a checkbox saying delete driver software for this device make sure to check that as well. basically what i am trying to say is you want to start fresh as in there should not be any reference to android or nook on your windows pc
another program that may be helpful is using usbdreview which is a program that monitors all devices with usb drivers. this may help is attempting to delete any reference to android and nook on your windows pc. hope this helps!
EDIT: just to add this tidbit in, if your having troubles with ADB, chances are it has nothing to do with your NT but rather with the drivers that Windows has installed already. There's a guide to installing ADB correctly, here's a link:
http://forum.xda-developers.com/showthread.php?t=1424563
Click to expand...
Click to collapse
thanks for the reply, tried it. i tried the process and my computer said itfound drivers for my device but couldn't install new drivers on my android ADB interface.
same problem i had previously.
wagon_burner said:
thanks for the reply, tried it. i tried the process and my computer said itfound drivers for my device but couldn't install new drivers on my android ADB interface.
same problem i had previously.
Click to expand...
Click to collapse
hm.. well if it keeps on auto installing generic drivers you will need to disable auto installation of drivers by windows. try looking through each of these links and see if it solves your problem. fyi you should uninstall all drivers relating to android and nook before proceeding
http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/
hope this helps
ShinnAsuka said:
hm.. well if it keeps on auto installing generic drivers you will need to disable auto installation of drivers by windows. try looking through each of these links and see if it solves your problem. fyi you should uninstall all drivers relating to android and nook before proceeding
hope this helps
Click to expand...
Click to collapse
well this is weird one atleast for me. i had all those settings on at the very start of the rooting process. and in the end i need to enable in the system config the USER to override the automatic driver install policy. so my anti install was thwarting me this entire time!!! ugh!!! total noob but we all gotta start somewhere. thanks to everyone for helping me out!
I got a new Nook Tablet and it came with 1.4.1 installed, so I downloaded the acclaim_update.zip and put it on a microSD card and successfully downgraded to 1.4.0 but had to do a factory reset and opted out of the "out of box experience".
The problem seems to be that I have a Windows 7 64 bit system and this prevents me from "upgrading" the drivers on my system so that I can root the tablet.
Would it be easier to use the script for rooting the tablet using a Linux system?
I am going to see if I can find that script online in case that is the only way to go.
I do not have a 32 bit Windows system.
thanks
I have Windows 7 x64 bits and i had no problems at all even having my LG GT 540 drivers installed, i have windows update disabled "never check for updates" and before install the drivers u need to run the runmefirst.bat if you are having conflict with drivers there is a step by step guide try that and report back. Also do not run as administrator the .bat scripts. In my FAQ (link in my signature) there are other links to troubleshoot drivers if needed.
~ Veronica
I can't offer you much help, but I rooted my NT (1.4.0 out of the box) twice on two different machines running Win7 x64 without issue...
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
lavero.burgos said:
I have Windows 7 x64 bits and i had no problems at all even having my LG GT 540 drivers installed, i have windows update disabled "never check for updates" and before install the drivers u need to run the runmefirst.bat if you are having conflict with drivers there is a step by step guide try that and report back. Also do not run as administrator the .bat scripts.
~ Veronica
Click to expand...
Click to collapse
Note also that I had two "runmedirst.bat" files - one packed with the drivers and one with zergrush. The first time I tried I used the wrong one and couldn't root. I *think* you want the one that was packed with zergrush.
lavero.burgos said:
I have Windows 7 x64 bits and i had no problems at all even having my LG GT 540 drivers installed, i have windows update disabled "never check for updates" and before install the drivers u need to run the runmefirst.bat if you are having conflict with drivers there is a step by step guide try that and report back. Also do not run as administrator the .bat scripts. In my FAQ (link in my signature) there are other links to troubleshoot drivers if needed.
~ Veronica
Click to expand...
Click to collapse
Thanks for the reply. The problem is that the moment I connect to wifi on the NT, it will be upgraded to 1.4.1, right? Can I download the TGPS_Launcher.apk on a pc and copy the file to MicroSD card and install from there? I am unable to install apk's at the moment since no installer is on the NT and I think I can only install from Market. I don't know how to get around this problem.
LordGibson said:
Note also that I had two "runmedirst.bat" files - one packed with the drivers and one with zergrush. The first time I tried I used the wrong one and couldn't root. I *think* you want the one that was packed with zergrush.
Click to expand...
Click to collapse
Thanks for this tip. I will look for the second script. It is likely I used the wrong one. If I do not see it, I will look for a separate Zergrush. I know I have one file or directory by that name with the drivers I downloaded.
spottedtadpole said:
Thanks for the reply. The problem is that the moment I connect to wifi on the NT, it will be upgraded to 1.4.1, right? Can I download the TGPS_Launcher.apk on a pc and copy the file to MicroSD card and install from there? I am unable to install apk's at the moment since no installer is on the NT and I think I can only install from Market. I don't know how to get around this problem.
Click to expand...
Click to collapse
You must install the drivers in order to root. LordGibson is right use the runmefirst.bat from Nook&Zergy.zip i too had issues with the runmefirst.bat from the drivers.zip
lavero.burgos said:
I have Windows 7 x64 bits and i had no problems at all even having my LG GT 540 drivers installed, i have windows update disabled "never check for updates" and before install the drivers u need to run the runmefirst.bat if you are having conflict with drivers there is a step by step guide try that and report back. Also do not run as administrator the .bat scripts. In my FAQ (link in my signature) there are other links to troubleshoot drivers if needed.
~ Veronica
Click to expand...
Click to collapse
I downloaded the other Zergy and drivers files and had the same problems. I think the problem is the Windows 7 system and I could not get the "new" drivers to install. I will check your FAQ and if that does not work, I will try to get it rooted via Linux, but that approach seems not so easy.
Also, do I need to make a new Google account in order to download an app to the tablet? I tried it and it just sends the app to my phone.
thanks
Windows 7 64-bit here as well. The drivers are a pain but keep trying with usbdeviewer helping you and you will get it.
Also I have rooted three times and each time I had the tablet hooked to WIFI for extended periods and never once did it show any signs of upgrading to 1.4.1
spottedtadpole said:
I downloaded the other Zergy and drivers files and had the same problems. I think the problem is the Windows 7 system and I could not get the "new" drivers to install. I will check your FAQ and if that does not work, I will try to get it rooted via Linux, but that approach seems not so easy.
Also, do I need to make a new Google account in order to download an app to the tablet? I tried it and it just sends the app to my phone.
thanks
Click to expand...
Click to collapse
for sideload apps like tgps_launcher.apk you dont need a google account, but for download from android market you will need one after you root.
Check out Albert's videos:
~ Veronica
I watched the video but was unable to install tgps_launcher.apk due to a parsing error. I do not think this is going to work.
I have never registered this device, I was afraid that if I did that, the device would revert to 1.4.1.
Linux also did not get this thing rooted with the NARS script. Although the Linux netbook mounts the tablet and I can see the files on it, the NARS script can't find the device.
thanks
P.S. I was able to install another package called AppMenu and that allowed me to enable USB debugging. This might be helpful.
blawens said:
Windows 7 64-bit here as well. The drivers are a pain but keep trying with usbdeviewer helping you and you will get it.
Also I have rooted three times and each time I had the tablet hooked to WIFI for extended periods and never once did it show any signs of upgrading to 1.4.1
Click to expand...
Click to collapse
It seems as though it will wait to upgrade when one registers the device with B&N and I have not yet done this.
lavero.burgos said:
for sideload apps like tgps_launcher.apk you dont need a google account, but for download from android market you will need one after you root.
Check out Albert's videos:
~ Veronica
Click to expand...
Click to collapse
Thanks for all the help. The video showed me what (I think) I might have done wrong. I did not think it was still necessary to reboot the machine after removing a driver. That and the link the video gives for an AppMenu really helped.
I am not certain whether all went well because the window closed abruptly after I selected removal of game apps during the installation process. I only wanted to remove the games and leave everything else. Going to reboot the NT. At least if something went wrong, I know I can restart.
spottedtadpole said:
Thanks for all the help. The video showed me what (I think) I might have done wrong. I did not think it was still necessary to reboot the machine after removing a driver. That and the link the video gives for an AppMenu really helped.
I am not certain whether all went well because the window closed abruptly after I selected removal of game apps during the installation process. I only wanted to remove the games and leave everything else. Going to reboot the NT. At least if something went wrong, I know I can restart.
Click to expand...
Click to collapse
You can uninstall the games later manually no need to run the script again, just make sure it rooted your device and you be good to go, also do not forget to block OTA. Indirect has another post for that specifically.
Download this app to uninstall data and system applications...
http://dl.dropbox.com/u/21630798/Apps/root_app_remover_vip_4.4Final.apk
Just in case read this is you ever want to debloat:
http://forum.xda-developers.com/showpost.php?p=21339441&postcount=2
~ Veronica
lavero.burgos said:
Just in case read this is you ever want to full debloat:
http://forum.xda-developers.com/showpost.php?p=21339441&postcount=2
~ Veronica
Click to expand...
Click to collapse
I did not full debloat because I thought I would lose all access to B&N. It happens that when I try to access B&N's Nook apps, to look for more apps, I get errors. This is probably not a big deal since I can probably get everything B&N has, from Android Market.
I did not know which launcher to install since I am unfamiliar with them. I just went with the "Go" launcher because it was first on the list; it's okay I am not voting for politicians, just a launcher for my tablet.
BTW, the first thing I did after restarting the tablet was to use Titanium Backup, then I replaced the backup files with three I had downloaded a few days ago, then I did a "restore" to those files. I checked my device information and confirmed that all went well.
I think this is why I can't access more Nook apps from B&N.
is there any other way to fix this? my comp is 32bit
trying to root using this method: http://zepinventory.wordpress.com/2014/03/31/how-to-root-azpen-a727-tablet/
I couldn't make it work from XP, and had to do it from Win7
I couldn't make it work from XP either. XP said it couldn't find the Android drivers, even though they were where I pointed to.
I had to DL the 64bit version of tha Andriod SDK, and to the driver install on my SO's 64 bit Win7 laptop, From there, Kingo Root could root it, and I could remove the SDK and Kingo Root from the SO's machine.
I got it to work once using the SDK on Windows 7 Professional, but subsequent tries did not. And for the life of me I can't figure out how I did it.
I'm assuming I need to install the Android ADB Interface as opposed to Android Composite ADB Interface, correct?
gotroot801 said:
I got it to work once using the SDK on Windows 7 Professional, but subsequent tries did not. And for the life of me I can't figure out how I did it.
I'm assuming I need to install the Android ADB Interface as opposed to Android Composite ADB Interface, correct?
Click to expand...
Click to collapse
AFAIK, yes. I believe that's what I installed. It's a "do once" operation, as once the driver is in place, you can root the device.
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: