Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
I've been thinking about this, and if I could just set up the android version of astrill directly in the micro sd (directly set up on nooter) I could then access youtube and finish the job properly.
Do you know if it's in any way possible to do that?
I wonder if you'd be able to use Orbot to be able to gain access to Youtube...
Karibou3 said:
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
Click to expand...
Click to collapse
Read this, its all contained on my manual tutos, adb is gained just by changing uramdisk, there is one for wifi and another for usb, please, check which one you are using, then, follow this:
Here there is a list of all the tutos:
http://forum.xda-developers.com/showthread.php?t=1380400
and here the ones you should read:
Setting up adb manually on the nook touch:
Making the manual process LESS PAINFULL
Setting up root access on NST through adb and installing busybox:
Hope it helps.
For the youtube thing, just set adb correctly (when you get it right) sideload an app to use a proxy, or tor, or anything you like, and try to login on Youtube.
I'm really sorry for not responding to this
I managed to get it rooted in the few days after my post, and I didn't any email notifications of your replies (didn't check on control panel, i'm new here, please don't hurt me )
I found a chinese source for rooting (a seller on taobao.com explained it. The Chinese are quite fond of the nook because it's the only foreign e-reader you can use to read Chinese apparently, and Chinese e-readers are both more expensive than the nook AND crappy.
Anyway I painstakingly translated it and got it to work
what you tell me about the proxy is new to me though, I thought android couldn't run a proxy, that's great news not just for youtube but the zillions of website China blocks and that I could use my nook to check, I'll have a go at it when I get near a wifi network.
cheers
Related
Ok I've researched this to death and tried in on both Windows 7 and osx 10.6.6 to attach using adb and install a couple of .apk's and the same thing happens on both platforms - NOTHING :-(.
You would think this would be pretty basic, but I am missing something somewhere.
Summary:
1. Am running the stock rooted b&n rom.
2. Can access both the internal and SD cards on the nook on both windoze and
osx. Eliminates cables, drivers etc...
3. Debug is selected in the nookstools settings
On both OSX and Win 7 installed the latest version of the Android SDK - both installs provided me with the platform-tools directory from which I will initiate all adb commands. So far so good...
on mac: ./adb devices returns:
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
$
As you can see I never get any device information returned, does not matter if Im on Windows or mac - same response.
Just for grins I downloaded the wireless app and tried to connect adb that way...no luck...
I could go into everything that i have tried over the last 24 hours...but that would also be pointless.
Bottom line...assuming this is something simpleI am just missing. Assuming since the symptoms are the same on both platforms that the issue lies on the nook but for the life of me I cannot find it.
Assuming if I cannot figure this out I will slowly go insane..my next step is to flash either froyo or honeycomb rom and see if this helps with the problems. Of course I MUST have the market available to me or I will not b able to load any .apk's.
Hpe Im in the right place. Any guidance is GREATLY appreciated.
Love this little Nook....BG
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
YMMV, but it solved that issue fo me.
Who Swami - It Worked
Swami,
I fall to my knees and bask in your knowledge: It WORKED!
I knew it was something simple, there is not a post on the entire Internet in any forum I have ever found (and I may have searched them all!) that mentions superuser needs to be running for adb to be able to communicate with the device. I wonder if this is a nook issue only. Will test on my wife's Epic this evening and post the results tonight.
My sanity now restored I bid you all a hearty SEE-Ya!
-BG
Omg I actually helped someone!
Glad it worked for ya I'm sure you felt the same relief I did when I finally stumbled across that fix.. I was pulling my hair out for hours LOL
Thanks Once More
As was I such a simple fix you would think I would have thought about permissions on the client side , such is life and tech thats why we all hang together.
Must say I was going to purchase the iPad 2 when it came out (NEVER buy 1st gen Apple) but now I'm not so sure...LOVING my Nook.
themirthfulswami said:
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
Click to expand...
Click to collapse
I'm not sure if this is related but I *think* that what made it work for me was to freshly enable the Debugging USB mode immediately before connecting the USB cable. Maybe that also triggered the Superuser app??? It's always the small things in life that make us smile
my problem is a little different.... I have sd cards with honeycomb (no market) and froyo (market and other apps). I can see the NC in adb with both, but honeycomb shows the device offline... and adb cannot talk to it. froyo show the device online and I can use adb. Both honeycomb and froyo show up in windows too.
I can't find anything that talks about getting the NC to show online to adb.
Same Problem
I have the same problem of trying to get my nook recognized. The only thing I can see different between my setup and the instructions on NookDevs was that they said I should see Android ADB Composite Interface on my Device Manager. Mine reads Android ADB Interface.
Tried the Superuser and the USB Debugging with no luck. Just really trying to get this set up so in case I need to factory reset. Because the 8x method manually is way too hard.
Have you guys read though this thread?
http://forum.xda-developers.com/showthread.php?t=910008&highlight=ADB
it worked for me like a charm.
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
I had intermittent ADB success with my Mac. After installing the ADB Wireless app there have been no problems.
Seaweedbrain said:
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
Click to expand...
Click to collapse
nvm
i connected my nook to the back of the cpu.
for some reason, it seemed to work fine.
it read the device as online.
got the g-apps
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
CrimsonSentinel13 said:
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
Click to expand...
Click to collapse
BurritoRoot causes the normal adbD to behave as an unsecure one, but if your not seeing the kindle under adb devices then you have PC side problems likely.
I figured it might be PC side. I've tried everything I could after updating the Android SDK. Updating everything with what's needed for the Fire to be seen hasn't worked. I'm a bit at a dead end for ideas... I tried even using the USB3 controller on my mobo but no luck either.
Edit: Fixed!
I uninstalled the Kindle Fire from the Device Manager & got it reinstalled. It now works perfectly with ADB. I'm in the process of rooting it as I type this.
I have the same problem.
However, I have 2 fires, one running CM7 and the other 6.2.1.
The PC recognizes the one running CM7 but not 6.2.1.
So, I don't think it is the PC.
No matter what I do, adb and fastboot, device not found.
Can not access the one with 6.2.1.
Does not show up in device manager.
I have read and try various things from xda, Rootzwili and Liliputing.
follow this video thats wht helped me get past that part ur on
http://www.youtube.com/watch?v=KapnjR89ICA&feature=player_embedded
u have to make sure u update the drive for ur kindle with the driver from sdk
this is also helpful tooo
http://forum.xda-developers.com/showthread.php?t=1409120
What worked for me was following this guide up to step 3. Then, with the device manager it launches, i deleted ALL my adb/android devices and then I let windows re-install the driver when I plugged the kindle (you may need to choose the driver manually), then I could finally access fastboot/adb via cmd..
Solved problem, Thank You.
I have many drivers on my PC, Motorola, Samsung, HTC and Android.
I noticed on one boot the Kindle was listed as Samsung Android Phone.
I uninstalled the Samsung drivers.
Connected the Kindle. All is fine.
Connected my Samsung SGS II, it found the drivers.
Crimson, thanks for sharing your fix of uninstalling then reinstalling. Worked for me.
hi, i would like to apologize in advance, i am new to adb so i'm not sure if i'm even doing it right, but i have successfully rooted and installed cm7, after much googling. i did it a while ago and used the clockwork mod method. i would like to replace it with twrp but the only way i have found to do it is by using adb or the kindle fire utility, which if i understand correctly uses adb. the only problem with that is that i can't get adb to recognize it. i'm assuming it's because i don't have the proper drivers for the "cm7 kindle" because i install them for the stock kindle. please help me. i have no idea how to fix this. thanks
edit: ok guys i'm really sorry, i'm an idiot, i forgot that i had turned off usb debugging. turned it back on, worked perfectly. again sorry.
Hello folks,
I had a WinXP computer, and I installed android SDK, and I was able to connect to my nook via ADB. As it was aging and having fan problem, I bought a new Dell (i5, win7, 4Gb RAM, 500 Gb HD). I installed android SDK, but never tried to ADB my nook. Yesterday I tried it, and whenever I try to connect via IP, or use adb devices, nothing shows up. I tried messing with the firewall, but it was not working at all.
Does anybody have any idea to help me? And also on how to get my firewall back (removed Norton, which I believe is a bloating spyware, and installed avast antivirus, but firewall was not released either, and it gives a 0x80070424 error).
Try this
Attach the usb cable to the NST and see if it is visible in device manager. Ideally if no driver is installed, you would just see it there with an exclamation mark.
Then follow ros87's instructions here. If adb_usb.ini doesnt exist create it.
Then from device manager, update device drivers for the unrecognized nook and point it to the i386/amd folder within the android drivers folder.
once that is done, restart adb, run "adb usb", then try "adb devices". If it worked it should show you the device.
ADB wifi was easier. In fact, it was such a long time since I last used it (before 1.1.1), that I forgot to add the adbwireless button to turn it on.
But thanks anyway. I've never dared to use USB due to inner messiness of the process.
My daughter dropped her HDX 7 and the screen shattered. I was able to secure a new one for her but she had some serious sweat equity into a few games she was playing on the old one. I am trying to get the game files of the old one to move to the new one but the touch screen won't work and as such, will not take her password. (due to the drop).
Is there an easy way to bypass this? I am trying to access the kindle drive from my PC for purposes of copying the files (done a million times) but with the device technically locked, the device does not show in file explorer.
Any suggestions welcome.
Thank You!
Chris
Do you have Safestrap installed?
EncryptedCurse said:
Do you have Safestrap installed?
Click to expand...
Click to collapse
No I don't. The device is purely vanilla right as it came from the factory.
Chriss9, you should try to get adb working. That should allow you to pull data.
lekofraggle said:
Chriss9, you should try to get adb working. That should allow you to pull data.
Click to expand...
Click to collapse
Can you tell me where to get it and maybe some instructions? Thanks so much!!
Chris
Look into the rootkit in the dev section. That should install the drivers for you. Then, search for how to use adb. You may need to download the developer kit from Google as the toolkit is a little limited.
You need to pull the data to your computer then push it to the new Kindle.
ADB pull on locked phone? // Simulate input
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Grtschnk said:
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Click to expand...
Click to collapse
Thanks for the suggestion. I installed ADB on my PC and when I use "ADB DEVICES" my device does not show on the list though it does show in Windows explorer. Am I out of luck here?
Thank you again for your kind support.
Chris
Assuming you have the latest Fire OS 4.5.1 : (If you have the older version installed there may still be a glimpse of hope (see long answer))
Short answer: Sorry, looks grim.
Your ADB is switched off and there is no way I know of to switch it on.
I wanted to make sure it wasn't just a driver issue with your computer so I checked with my Kindle:
ADB set off: Kindle in Windows, but not detected by ADB-program
ADB set on: Kindle in Windows and detected by ADB-program
Long answer (may be frustrating to read because it states all the possibilities the Kindle lacks): On a nonlocked (in terms of bootloader, not screenlock) device there would have been some possibilities. Install a custom recovery that has ADB built in and pull the files or try to enable ADB from within recovery inside the ROM. If the device could act as a USB host a mouse or keyboard could have been hooked up. The Kindle supports Bluetooth input devices but they have to be set up first (from within the device, not possible without touch). If your device has older Fire OS you could try the mentioned steps, however that's beyond my expertise. So I don't know if it is possible/will work. You'd have to check other threads about flashing the device or hope that someone else posts advice in this thread.
I became a Kindle owner quite recently, so I can't guarantee everything I wrote is correct, but I believe as long as noone magically finds a way to unlock the bootloader the more experienced users will agree to my post.
Did you install the driver as well? I recommended the toolkit because comes with the driver and if you are not used to installing adb drivers on Windows, it can be a bear. But, Grtschnk may be right. I always enable it n all my devices. It is the first thing I do.
Just to be really sure about possible driver issue: You (chris) could try to connect an Android phone via ADB (I'm assuming you have one). Enable ADB on it and see if connects. Unfortunately this will only prove more that your Kindle turned into a piece of plastic :/
Grtschnk, unfortunately, that won't prove anything. ADB requires separate drivers for each device. Again, that is why I recommended the rootkit. It sets it up for you and can even test it.
That's why I compared with my Kindle, computer and S2 (CM11). Newly set up computer, no SDK, just Minimal ADB. Never installed special drivers for Kindle or S2. Newest Visual Studio (2013) runs on the machine, but without additional packages there is no Android support.
However if I was in the situation myself I would have also tried the full SDK.
I have the following problem. My Nexus 4's touch is broken, it can show stuff though. I need to run an app (the battle.net authenticator, otherwise I can't log in) through access from my PC, but there are some problems. It is not rooted, its bootleader is locked and everything is stock. I do have USB debugging enabled though. Also I can't do adb commands because this is a new PC and I haven't authorised it (it shows up as unauthorised on adb devices).
After a long series of experiments and a lot of googling, I found a combination of 2 programs ([email protected] and Android Control) to do what I want, and do some stuff when on Recovery Mode to activate the adb thing through cmd (most of those in this site), but my PC can't seem to even see that a device is connected when I am in Recovery Mode. I have tried reinstalling the drivers a couple of times but nothing seems to work.
Does anyone have any ideas?
Xalathal said:
I have the following problem. My Nexus 4's touch is broken, it can show stuff though. I need to run an app (the battle.net authenticator, otherwise I can't log in) through access from my PC, but there are some problems. It is not rooted, its bootleader is locked and everything is stock. I do have USB debugging enabled though. Also I can't do adb commands because this is a new PC and I haven't authorised it (it shows up as unauthorised on adb devices).
After a long series of experiments and a lot of googling, I found a combination of 2 programs ([email protected] and Android Control) to do what I want, and do some stuff when on Recovery Mode to activate the adb thing through cmd (most of those in this site), but my PC can't seem to even see that a device is connected when I am in Recovery Mode. I have tried reinstalling the drivers a couple of times but nothing seems to work.
Does anyone have any ideas?
Click to expand...
Click to collapse
As far as connecting to the PC is concerned have you tried another PC or USB cable? And since that's a battle.net authenticator you can contact their support, either via web ticket or phone (if you live in the supported countries) and after they confirm it's really yours account, they'll remove the authenticator for you.
nerotNS said:
As far as connecting to the PC is concerned have you tried another PC or USB cable? And since that's a battle.net authenticator you can contact their support, either via web ticket or phone (if you live in the supported countries) and after they confirm it's really yours account, they'll remove the authenticator for you.
Click to expand...
Click to collapse
I can see the phone just fine everywhere else, just not in recovery, so no I didn't try that. And I have tried using their support but I was in a pretty special situation for some reason and they couldn't help, but I fixed my problem. I had saved my restoration code for my authenticator ages ago and I didn't remember. Thanks for trying to help out though