• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root What's happening on the rooting scene.

That's the way I understand it, Rad. I still have faith that the Devs will find a solid exploit for the bootloader on the NT. For now, a rooted tablet is enough for me... Honestly, I think for the price, even if the bootloader is never cracked, I'm still down.
 
Locked bootloader just means that the kernel has to stay on what it's on now (GB I assume).

It doesn't mean it's not impossible, it might just mean a lot more work for the devs.
 
Is there an elegant/simple way around the driver issue? Every method I have seen (which is only, like, 3, so I don't claim an exhaustive knowledge) relies on re-installing the Android USB drivers, and every compluter I have has had multiple android devices attached to it, and unlike my USUAL Microsoft experience, Windows (XP and 7) are being really good (read: bad) about automatically installing the device drivers and stopping the whole show before it gets started.
 
Nothing I've read has avoided that issue all together.
This forum was a great help to me.
In the end Usbdview was the thing that got it done for me.
For reference, should anything go wrong after you've rooted and a restore should prove necessary (I had the 1.4.1 OTA sneak through), the driver dance proved unnecessary. Zergy worked just fine without playing that game again.
 
I don't know about elegant, but it's definitely doable. I've had 3 different Android devices connected to my Win 7 desktop and was able to get this working.

First, here's a video of someone getting the drivers set up.

And here's the thread over at XDA that the video is following. (The video is actually linked in that thread.)

Two additions to the video:

1) I'd try this first, because this is what finally got it working for me:

Go to Start Button > Right click Computer > Properties > Advanced System Settings > Hardware tab > Device Installation Settings

Select "No, let me choose what to do"
Select "Never install driver software from Windows Update"

Save Changes

(You'll probably want to change that back after you're done)

2) If you need to nuke the drivers, then try Usbview, which was pointed out by yumms in that same thread.

[Edit: And this is why we don't start a reply, walk away for a few hours, then come back and submit. I hadn't seen aceofspades626's post before submitting my own.]
 
Yours was actually more in line with what I needed, AnotherHiggins. I never quite caught how to get to the right menu in the system settings. The options always looked wrong and I was chosing the closest one. My windows experience is mostly with XD, and I'm not familiar with all the details of 7.

I just killed the auto driver update, and I'll try the install again when I get up in a few hours (worked all night, now I'm fried, and that's exactly the wrong time to do techy things to expensive electronic devices)

Thanks!
 
No dice.

Despite having the above-listed items checked in the Advanced System Settings menu, Windows is still installing the drivers and telling me, if I try to do it manually, that the best driver is already installed.

Open the pod bay doors, HAL.
 
You shouldn't already have any driver installed. Use USBDView to delete Android drivers on your computer. Then check Device Installation Settings. Then plug in the NT.

You want to see an exclamation point in a triangle in the Device Manager, which indicates that there is no driver loaded.
 
Yeah, I did that. I used usbdeview to eliminate anything with Nook or Android associated with it, including all unnamed "mass storage devices", made sure the aforementioned stuff was checked, then plugged in the NT. It promptly installs the drivers.

I may have an old Windows XP box in the basement. Android didn't exist the last time it was plugged in. If I still have it, I'll give ita shot tomorrow afternoon.

Mike
 
Ok. Now we've advanced to the next problem. I dug out my old xp box, went through the process with it and got further. The it brought up the nook with the error symbol, and I instructed windows to install the usb drivers from the root pack. It started, said the drivers were unsigned/verified, asked me to stop or continue. I chose continue. It went through the install process and ended with a failure message, saying the new drivers could not be installed. I then tried running nook and zergy, and as I suspected it went nowhere.

Any ideas?

Thanks,

Mike
 
Update: I never did get Win7 to cooperate, and I guess my old XP computer was to elderly to handle the driver install. I borrowed a laptop running XP sp 3 from a friend and I'm in business. Once I got the drivers to install it was cake; no harder than rooting a phone and easier than some of those, too. Hat tip to the revs who pulled it off, the issues are completely on windows' end.

Mike
 
I just spent a LONG time pouring over a ton of posts I don't understand over @ XDA. Long story short, it SOUNDS like custom roms aren't far away. Those guys are pretty amazing!
 
You must log in or register to reply here.
Back
Top Bottom