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.
hey guys i'm having a little issue here i cant seem to connect my phone into USB debugging mode i am running the latest zenwich
yes i went to dev options and enabled USB debugging yet adb wont recognize it.
any help or tips would be great
thnx
aldoit01 said:
hey guys i'm having a little issue here i cant seem to connect my phone into USB debugging mode i am running the latest zenwich
yes i went to dev options and enabled USB debugging yet adb wont recognize it.
any help or tips would be great
thnx
Click to expand...
Click to collapse
What operating system are you using? Do you have the Vibrant drivers installed?? Also, with this ROM you need the Nexus S drivers installed since the code is based off the Nexus S.
I found out your problem, you probably have the wrong drivers installed, you need the drivers from the Android SDK. You can install them under the "extras" section. Here's some more detailed instructions I wrote up:
Download the Android SDK: http://developer.android.com/sdk/index.html
Under Extras install "Google USB Driver Package"
then browse to the folder the Android SDK installed to: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open device manager, browse for drivers and paste that location
Tynen said:
What operating system are you using? Do you have the Vibrant drivers installed?? Also, with this ROM you need the Nexus S drivers installed since the code is based off the Nexus S.
I found out your problem, you probably have the wrong drivers installed, you need the drivers from the Android SDK. You can install them under the "extras" section. Here's some more detailed instructions I wrote up:
Download the Android SDK: http://developer.android.com/sdk/index.html
Under Extras install "Google USB Driver Package"
then browse to the folder the Android SDK installed to: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open device manager, browse for drivers and paste that location
Click to expand...
Click to collapse
k i will try things out thanx for everything and
i have xp on this computer also i do have the samsung drivers installed
You definitely need the sdk drivers then
Sent from my Dell Streak 7 using xda premium
I have recently installed Windows 8 Release preview and can't manage to install fastboot drivers. Tried already installing them from flashtool drivers folder but windows doesn't recognize them, also tried manually from device manager pointing at the extracted drivers from flashtool drivers setup (used universal extractor). Last i tried the inf file from SE bootloader unlocking page....no way....does anyone know how to do it? In HTC 3d they solved this with a modified fastboot driver for Windows 8. I really am beginning to like the interface of this new windows , don't want to switch back to 7.
EDIT: Found the solution . Just disabled the driver signature check in windows 8 .
how you have done it?
Fastboot drivers
just download rar file i have created from link above and extract it to your computer.connect your device to fastboot mode and when windows ask for drivers point the location to extracted fastboot folder.you must remember to point the location drivers folder and you exactly must point x64 folder or x86 folder(x64 for 64-bit os x84 for 32-bit os) otherwise windows will not find the drivers for you........(NOTE:do not point folders inside x86 or x64)...just try this,if this helpful don't forget to thanx.....
(dl.dropbox.com/u/82612571/fastboot.rar)i am new user because i cant put direct link.copy this to adress bar.
gdeliana said:
Just disabled the driver signature check in windows 8 .
Click to expand...
Click to collapse
for those who don't know how to do it, following link is a good guide:
disable driver signature check in windows 8/
Thanks guys, I get it using this two posts togethers...
First, use this tutorial to disable drivers signature for Win 8
a_ejazz said:
for those who don't know how to do it, following link is a good guide:
disable driver signature check in windows 8/
Click to expand...
Click to collapse
Than use the drivers from link bellow
Lasanda said:
just download rar file i have created from link above and extract it to your computer.connect your device to fastboot mode and when windows ask for drivers point the location to extracted fastboot folder.you must remember to point the location drivers folder and you exactly must point x64 folder or x86 folder(x64 for 64-bit os x84 for 32-bit os) otherwise windows will not find the drivers for you........(NOTE:do not point folders inside x86 or x64)...just try this,if this helpful don't forget to thanx.....
(dl.dropbox.com/u/82612571/fastboot.rar)i am new user because i cant put direct link.copy this to adress bar.
Click to expand...
Click to collapse
Everythings is working fine now!
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment Rockusb.rar
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
Thanks for the info. Will be giving it a go later today
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
when in doubt go back to the forums. I can not get the inf in the rockusb to install. "Installation for this file type not permited" . So I'm stuck, the program will not complete. I'm on windows 7 so maybe the driver is for another system. If you can provide futher help, Thanks in advance.
New approach
Ok I cannot get the drivers to install on my computer. Window 7 seems to default to its own driver and will not let me install the rockusb drivers.
With that said, I have the system Update.img and was wandering if the img itself can be rooted and then updated to the tablet. If this is possible and anyone with the knowledge is willing I will upload it. Or if someone is really patient and would like to walk me through the process and I will attempt to do this myself
No Help
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
Can't tell your level of PC knowledge so if you already know this don't get offended. The .inf is editable and there are areas in there that allow manufacturers to prevent installation on some OS's to prevent conflicts. Make a system restore point or better yet a backup and then post the contents of the INF somewhere and point the folks here to it and they may be able to help you edit it to install. Regardless, you'll have to use the "have disk" option instead of letting windows search for a driver even if you get the edits right. And the usual disclaimers about me not being responsible for any issues with your equipment as a result of this are in effect.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
I was able to root using the instructions above although i don't think you need the rockusb drivers. You just need the usb drivers that come with the android sdk. I am on Win 7. Thanks for the above info for rooting.
I was able to install ROM manager and now proceeding to backup ROM and upgrade using this guide: cant post link as forum is preventing, but search for rom flash guide on androidpolice com.
Hope this helps.
Big thanks to this thread to get me going...!!!
?
could someone please, Barney style, Explain how I am supposed to select the android_winusb.inf because my steps are as follows. Right click on device p771a in device manager, browse my computer, let me pick from a list of device drivers, have disk, point to the google usb driver (C:/Android/android-sdk/extras/google/usb_driver) select the android_winusb.inf open. Hit ok, (The folder you specified doesn't contain a compatible software driver for you device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems). Hope this helps explain my troubles. Glad that my thread is helping others to root this device but it does not work for me.
Could it really be that simple?
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
tannerjames said:
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
Click to expand...
Click to collapse
Glad you could figure it out...
I was not able to use the ROM Manager to backup the ROM since the device is not supported on this tool, but see below for how you can obtain the stock image.
I've tried to flash multiple different ROMs using RKAndroid to the tablet, spending days on this, with no success. The tool itself works great and I am able to flash the ROMs since it supports the RK29 chipset which I believe this tablet has. The stock ROM for this device is available from the manufacturers web site (the link is available when you go to Settings => About Device => System Update, hkcdigital dot com slash update slash update.img), if anyone would like to take the stock rom and upgrade it to Android 4.2/JB.
I was able to unpack/repack the stock image using the wendal image tools and modify / cook the ROM using Android kitchen method described elsewhere in this forum. Rockchip Batch Tool is another great utility to flash custom ROMs to this device. Also, If you put the ROM as update.zip or update.img file on the microSD card, the tablet will take it and flash the image as long as it is in the right format. Ofcourse you can put the tablet into recovery and restore from there as well. I've found that the stock image (update.img) has the following file/folder format when unpacked: /RK29xxLoader(L)_V2.27.bin, /package-file, /parameter, /recover-script, /update-script, /Image/boot.img, /Image/system.img, /Image/recovery.img and /Image/misc.img.
Is it possible to upgrade this tablet to Android 4.2 or atleast Jelly Bean? Would be very helpful if someone is able to do this. The most success I've had so far is with the custom ROM Oma_Odys_Loox_JB_4.1.1_v1.2.2a flashed using RKAndroid. It flashed the tablet fine, updated the boot etc. On tablet boot I am able to see the new logo, but then the it doesn't go anywhere from there. I think customizing this ROM or the stock ROM we should be able to get the new OS on to the HKC tablet. I've given up for now since I don't have the time to spend on this anymore. If someone is able to do this, please post the instructions or upload the custom ROM, as I am sure it will benefit a lot of people and will be much appreciated. Happy cooking!
Thanks!
jawadshaik- rom manager
If you have successfully flashed rom manager on this device could you post the steps you took to do so. What version? Manual flash? The program itself says there is no recovery for this device.
Sorry jumped the gun on that last post. Thanks for the info
What's the secret to keeping the battery from draining so quickly while it's idle? I just got this and see it drained about 40% in about 2 hours I think and I wasn't using it.
tannerjames said:
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
Click to expand...
Click to collapse
@jawadshaik
Just out of curiosity, when you were flashing that Rom that brought up the boot screen, did you do a wipe/factory reset from recovery mode before flashing? I have no idea if that would help or not, but most if not all roms require a data wipe before flashing... Just curious if you had tried this as I have heard of this happening on other devices because a data wipe wasn't done first. Might be worth a shot if you haven't tried it already, just a thought
Sent from my Huawei u8651s using xda app-developers app
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
So after doing working on this a while, I've finally figured it out. Here are some caveats:
1. You can't do this on a Mac or Linux box. Don't ask me why, you just cant.
2. You have to turn on USB debugging, change the Security to allow Unknown sources and MOST IMPORTANT: when you plug it in, you have to change it to "Connected as a Camera". Putting it in storage mode doesn't work!
HOW TO INSTALL THE PROPER DRIVER & ROOT THE DEVICE:
1. Follow the steps quoted above and download the Google Android SDK, and the Java JDK (from oracle.com/java).
2. When you first plug it in (use the USB plug labeled USB not the HOST one), it complains and will discover a P771A device. When it does, right click on your computer, choose Manage my computer, go to the device manager and then right click on the P771A device. Click "Update Device Driver". Choose "Browse my computer for Driver software". Then choose, "Let me pick from a list of drivers on my computer". Browse to the \adt-bundle-windows-x86_64\sdk\extras\google\usb_driver folder which you would have if you had downloaded and installed the Google Android SDK. A list of 3 drivers will appear when you click OK. CHOOSE THE "ANDROID BOOTLOADER INTERFACE" as the driver. None of the others work.
3. Run the root script batch file mentioned above which can be found here at: sourceforge.net/projects/androidroot
4. The root script isn't really great at explaining so I'll try. When you first run it, make sure your device is unlocked and on the home screen.
5. The first thing it will do is reboot your machine. Don't press enter until your machine comes back up.
6. After your machine boots unlock it and then press Enter again. Your machine will reboot. This time it won't seem to come up but the backlight will remain on.
7. Wait about 30-45 seconds then press enter again. You should get: uid=0(root) gid=0(root) in the command prompt window.
8. Press Enter. You should get:
remount succeeded
727 KB/s (22364 bytes in 0.030s)
Removing changes except ROOT...
Installing superuser...
2288 KB/s (843503 bytes in 0.360s)
9. After about 30-60 seconds, your device should reboot. You'll see a box briefly saying "Android is Upgrading" and you'll arrive at the lock screen. Press Enter to exit the command prompt.
Your device is now rooted and you should see "SuperUser" installed. I promptly installed "root uninstaller" to get rid of Facebook, Skype, and Youtube which my little kids don't need access to. This device doesn't have a bootloader or recovery mode so rooting it doesn't get you much besides the ability to uninstall the system software. Have fun.
This may help someone but on step 2 of the guide on the second page, after you right click your device and go to "Let me pick from a list of drivers on my computer". You then click "Show All Devices" then "Have Disk..." Direct it to the root of the adt-bundle folder you downloaded then you can select from the three drivers. I'm on windows 7 32bit and the drivers didn't show up for me like how it was suppose to..
I also could NOT get any of the drivers in the "manufacturer USB" packet to install... I WAS able to install the google drivers, but that also would not allow ADB to see the device... So still stuck with everyone else...
P771A possible problem
I'm having a similar problem where the USB driver downloaded through Android SDK's -> Extras -> Google USB Driver, tells me that the file contains no information about my device. I noticed in the Sources of SDK, there wasn't an API for 4.0.4, only 4.0.3 then 4.1, so i downloaded 4.0.3 repo.
============================================
my devices is on 4.0.4, and my Kernal is as follows:
3.0.8+
[email protected] #8
Wed Aug 29 09:59:19 PDT 2012
Build Number:
P771A-user 4.0.4 IMM76D user.v402.007 release-keys
============================================
I've also made sure weather Unknown Sources is on, as well as USB debugging.
Might the Kernal be the problem? Also, does it matter weather its MTP or CTP?
Now HKC is telling me that they don't support the ability to jail break their devices
Sent from my P771A using xda app-developers app
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: