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:
Related
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 !
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Good write up!
The procedure worked fine on my laptop. When I did it on on my home PC I forgot to disable auto-mount and the Nook installed itself as mass storage. I was able to right click -> un-install all the USB Mass Storage entries (with the Nook unplugged), disable auto-mount, plug the Nook back in, and have it show up correctly.
In short, I did not need to use "USBDeView" as I was able to remove the diveres manually. I suppose if you have more than a handful for USB devices (I just have a Mouse, Keyboard, and printer) "USBDeView" might be helpful to determine which drivers to un-install...
The device manager is enough for most people, but there is a somewhat large number of us that are having trouble still. Possibly because of other devices we have installed before. (I dont understand how all the drivers work and I wont pretend to)
Some people have go so far as putting a fresh install on Windows on a partition of a PC.
I had this problem with both my laptop and my desktop, which surprised me. This worked on both the laptop and PC, so hopefully it can help other people.
I cant wait to get my own tablet on the 12, I will take lot of pictures and make this process more user friendly.
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
mtelesha said:
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
Click to expand...
Click to collapse
Did you sort by last time plugged in and delete all of those too? Have you re-checked and then re-un-checked automount/usb debugging and such?
This is interesting, you'll have to come back and let me know if you ever get it working on your PC. Maybe its a good excuse for a nice healthy re-format and reinstall of windows?
l3ft3r1s said:
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
Click to expand...
Click to collapse
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
The_Joe said:
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
Click to expand...
Click to collapse
Yeap, that did the trick, thanks. Drives installed successfully this time, but adb devices still returns nothing.
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
adb error: device offline
This drove me nuts for at least a day. Turns out it is what happens when you are plugged into a USB 3.0 port on your PC side. Find out which USB is 2.0 (Front Panel for ZT Systems), use it and life suddenly gets really good.
The_Joe said:
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
Click to expand...
Click to collapse
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
l3ft3r1s said:
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
Click to expand...
Click to collapse
The problem is sdk uninstall and use ccleaner to clean your PC and registries. Use the drivers provided in this forum
Sent from XDA using one of my Android Toys
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
LadyPenley said:
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Click to expand...
Click to collapse
In the future don't delete your original, just post an edit with the fix. That way when someone else has a similar problem your post can help.
Sent from my BNTV250 using xda premium
mtelesha said:
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
Click to expand...
Click to collapse
Did you find a solution? Thats a problem I sadly dont know how to help with. I would start with:
-Check USBDeview and delete anything android/Nook/usb related. Delete just about everything.
-Restart the device
-Uncheck and recheck the USB Debugging boxes
-Recheck and uncheck the auto-mount box
-Test
-Try a different USB Port
-Try another PC
Thanks but didn't work.
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
The_Joe said:
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Click to expand...
Click to collapse
whitets said:
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
Click to expand...
Click to collapse
I had literally this exact same problem the 6th time I restored and flashed. IF im right, you just need to uncheck then recheck usb debugging.
Let me know if it works!
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.
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
In reading carrett's root, unlock and install guide as well as thecubed's Project FreeGee thread, it's clear that adb needs to be installed on my phone. Unless it's hidden somewhere, I believe that I need to install it as well as install adb drivers on my laptop. As far as the phone goes, Google play has wifi apps, but I can't find a tethered app to install. In addition, after a couple hours of searching, I don't find adb software or drivers to install on my laptop.
I'd prefer to not brick my phone on 1st attempt, so I pose the following questions:
1) Am I completely confusing things or am I correct in thinking that I need to explicity install adb both on my phone and laptop
2) assuming that some sort of adb install must happen, where do I find the installation files?
I think that I've finally found the answers to my questions: install the ADT bundle which includes adb. I'm downloading and installing it as I write this.
If a mod wants to delete this thread, please do.
dbgeek said:
I think that I've finally found the answers to my questions: install the ADT bundle which includes adb. I'm downloading and installing it as I write this.
If a mod wants to delete this thread, please do.
Click to expand...
Click to collapse
dude link it?
Uh, ADB support is built into Android.
You need to have USB Debugging turned on for some stuff to work though. In Settings>Developer Options>(check USB debugging box).
Then ADB SHOULD be installed with the LG drivers (if not I think the FreeGee download has it built in).
And if it is not, you can always install the Android SDK (HERE).
I know it is in there.
(Sorry, my memory is fuzzy, I've had ADB on my laptop for a few years now... not sure where I got it)
bleached45 said:
Uh, ADB support is built into Android.
You need to have USB Debugging turned on for some stuff to work though. In Settings>Developer Options>(check USB debugging box).
Then ADB SHOULD be installed with the LG drivers (if not I think the FreeGee download has it built in).
And if it is not, you can always install the Android SDK (HERE).
I know it is in there.
(Sorry, my memory is fuzzy, I've had ADB on my laptop for a few years now... not sure where I got it)
Click to expand...
Click to collapse
That's the issue I had with it, but just today I got rid of my old one troubleshooting.... thinking I messed it up ( which is why I had to find another)
Sent from my LG-E970 using Tapatalk 2