Related
I rooted 1.2.0 via manual nooter 4.5.2. Before I updated from my rooted 1.1 I could go to the android market on my PC and install apps from there. Once I manual rooted 1.2.0 with 4.5.2 I can no longer install market apps via the PC. The market shows I have no phone (4.5.2 was the update that had the samsung added). Does anyone know a cure for that? I can live with it, but it was nice to find and research apps via the pc and install from there. The market works fine from my nook, though. Thanks for any suggestions.
4.5.6 has the same problem and more
I have done the manual nooter process for my Nook (Stock 1.2) as described in
http://forum.xda-developers.com/showthread.php?t=1054027
Even if the installation went well I have the following problems:
The installed Market does not contain very many of the apps I am interested in.
Installing from android market from my PC does not work. There is no device shown in the list when I press <install>.
Manual installs from an apk file has problems.
I downloaded <Android File Manager> with the market app. And tried to install 3 different downloaded apk files (one of them was Kindle). AFM asked if I wanted to install, but the only thing that seemed to happen was that the apk file was erased. I managed to install the third app which was an alternative keyboard. Even so, the keyboard did not become visible in <Choose Keyboard> in NookColorTools, even if it was listed under <manage applications> in NCT.
My last resort was to try a manual install from my PC with ADB. I installed “nookcolor-easyADB” on my PC (Windows XP). I enabled ADB in the settings on my Nook. But my PC was not able to detect the Nook when I plugged it in, except for the hard drives of course. I manually installed the driver. The installer said it was OK, but it did’t help. The driver did not turn up in the device list on my PC.
Does anyone have a clew
bjornulf said:
I have done the manual nooter process for my Nook (Stock 1.2) as described in
http://forum.xda-developers.com/showthread.php?t=1054027
Even if the installation went well I have the following problems:
The installed Market does not contain very many of the apps I am interested in.
Installing from android market from my PC does not work. There is no device shown in the list when I press <install>.
Manual installs from an apk file has problems.
I downloaded <Android File Manager> with the market app. And tried to install 3 different downloaded apk files (one of them was Kindle). AFM asked if I wanted to install, but the only thing that seemed to happen was that the apk file was erased. I managed to install the third app which was an alternative keyboard. Even so, the keyboard did not become visible in <Choose Keyboard> in NookColorTools, even if it was listed under <manage applications> in NCT.
My last resort was to try a manual install from my PC with ADB. I installed “nookcolor-easyADB” on my PC (Windows XP). I enabled ADB in the settings on my Nook. But my PC was not able to detect the Nook when I plugged it in, except for the hard drives of course. I manually installed the driver. The installer said it was OK, but it did’t help. The driver did not turn up in the device list on my PC.
Does anyone have a clew
Click to expand...
Click to collapse
You did the market visibility workaround STEP BY STEP EXACTLY as described in the Manual Nooter OP?
Than you. The solution to the market problem was there. I just didn't notice. I followed the instructions and it worked.
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
Apologies if this duplicates an old thread, but I couldn't find another one...
I rooted my Nook Simple Touch using Touchnooter 1.1, and now it can't be recognized by my PC. I can't copy files to it.
I bought several Google eBooks recently that I'd like to read on my NST, but they can't be loaded, as Adobe Digital Editions can't see the Nook (or doesn't recognize it). Google Books doesn't work, either. It just stays on a rotating 'loading' icon forever, never loading the book.
Any thoughts?
Not recognized? You mean on USB? No volumes mounted?
You can certainly transfer your books over ADB on WiFi if that's working.
If you can get to a shell on ADB try a "mount" command.
The last two lines should be like:
Code:
/dev/block//vold/179:6 /media vfat rw ...
/dev/block//vold/179:17 /sdcard vfat rw ...
DoomMunky said:
Apologies if this duplicates an old thread, but I couldn't find another one...
I rooted my Nook Simple Touch using Touchnooter 1.1, and now it can't be recognized by my PC. I can't copy files to it.
I bought several Google eBooks recently that I'd like to read on my NST, but they can't be loaded, as Adobe Digital Editions can't see the Nook (or doesn't recognize it). Google Books doesn't work, either. It just stays on a rotating 'loading' icon forever, never loading the book.
Any thoughts?
Click to expand...
Click to collapse
Using a root method that enables ADB over USB can mess up the drivers on Windows and make the Nook partition inaccessible.
There are two options:
1: Re-root with a ramdisk that enables ADB over WiFi (might not help)
2: Properly install Google drivers for ADB over USB (search this forum)
Dammit. It's so darn complicated. I was hoping to recommend this method to my non-geek friends so they could have simple little tablets too, but this all is just too much work for them (and for me). This is why people buy Apple.
If I go back to a rooted Nook (I returned to stock) I'll look into this stuff. Thanks for the tips, folks.
Oh! Check what driver you have on the Windows machine.
Under "Device Manager" if it shows Android anywhere then you have the Android ADB USB drivers loaded.
This would prevent the USB Mass Storage driver from being loaded.
Did you load the ADB USB drivers?
God, I have no idea if I loaded the ADB USB drivers. I just did the normal TouchNooter1.1 install, which includes basic Google Apps.
Then when my PC didn't recognize the rooted NST, I gave up and went back to stock! I'm not a true rooter.
@DoomMunky: Aw, don't get disheartened. Soon you'll be rolling your own kernels!
So you got your Nook to be recognized by your PC now?
Only by reverting to stock firmware. I'm running basic 1.1 now, no Android anything, and it's fine.
If I end up re-rooting in the future, what steps should I take to ensure my PC still allows simple book transfers to my Nook Simple Touch?
hi guys inhd eed help for my kindle fire hd.
i want to add the "google play store" app, so i'm going to root it
i downloaded all files
but when i open cmd and type: "adb shell" appears this error: "device not found"
please help me!!!!
Google Play Market Kindle 7" Software 7.2.3
diego_berta said:
hi guys inhd eed help for my kindle fire hd.
i want to add the "google play store" app, so i'm going to root it
i downloaded all files
but when i open cmd and type: "adb shell" appears this error: "device not found"
please help me!!!!
Click to expand...
Click to collapse
I suspect your Kindle Fire 7" HD is now running Software Version 7.2.3 (Device - About), correct?
Your problem "Device not Found" is either driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/showthread.php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/showthread.php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/showthread.php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Downloaded and install the GoogleServicesFramework.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Play.apk to upgrade the the android market to the current Google Play market.
I have also attached copies of these noted files to this thread.
prokennexusa said:
I suspect your Kindle Fire 7" HD is now running Software Version 7.2.3 (Device - About), correct?
Your problem "Device not Found" is either driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/showthread.php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/showthread.php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/showthread.php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Downloaded and install the GoogleServicesFramework.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Play.apk to upgrade the the android market to the current Google Play market.
I have also attached copies of these noted files to this thread.
Click to expand...
Click to collapse
thanks dude but still not working.
ADB enabled on the indle fire HD - Version: 7.2.3
Root step 1: when i open root MANY ANDROIDS i press 1 (normal methods). Error: adb server is out of date. killing...
how can i do now??? P.S. now adb is installed
diego_berta said:
thanks dude but still not working.
ADB enabled on the indle fire HD - Version: 7.2.3
Root step 1: when i open root MANY ANDROIDS i press 1 (normal methods). Error: adb server is out of date. killing...
how can i do now??? P.S. now adb is installed
Click to expand...
Click to collapse
Seems you still have a driver issue. If you open the device manager on your pc you should see the kindle recognized as android composite adb interface. That is how you'll know if its just your driver(which most likely is).
Try using this first:
https://docs.google.com/folder/d/0B4lZEJI5lYeMdnFHeVRMQUtRYWc/edit
It is the driver application provided by amazon for sdk
If that doesn't do it (or even if it does) then I would recommend installing SDK, it will insure you have everything you need. Amazon provides add-ons, including usb drivers so you'll know for sure its all right. I posted link below for amazons page for installing sdk and kindle add-ons
https://developer.amazon.com/sdk/fire/setup.html
After you fix the drivers then use the method posted above to root. Good luck hope this works for you.
hi guys i'm a new forum member. I'm trying to root my kindle fire hd (7.2.3) but when i run "RunMe.bat" the device seems not to be connected! I've enabled the adb on the kindle and installed the ADB driver package. help!!!
ps sorry for my english
onemeila said:
Seems you still have a driver issue. If you open the device manager on your pc you should see the kindle recognized as android composite adb interface. That is how you'll know if its just your driver(which most likely is).
Try using this first: REMOVED : NEW USERS CAN'T LINKS
It is the driver application provided by amazon for sdk
If that doesn't do it (or even if it does) then I would recommend installing SDK, it will insure you have everything you need. Amazon provides add-ons, including usb drivers so you'll know for sure its all right. I posted link below for amazons page for installing sdk and kindle add-ons
REMOVED : NEW USERS CAN'T LINKS
After you fix the drivers then use the method posted above to root. Good luck hope this works for you.
Click to expand...
Click to collapse
so bad. still same problem.
devices installed, sdk installed (with superuser and su), kindle is recognized as android composite adb interface, kindle software version 7.2.3
i tried some tutorials with cmd, with qemu and with "root many android"
here the problems:
WITH CMD) Error: cannot create /data/local.prop permission denied
WITH Qemu) Error: you must install your device specific drivers so that the device is visible to ADB
WITH ROOT MANY ANDROID) Error: adb server is out of date. killing..
thanks guys to help but it didn't work yet i'm lost
adb server is out of date. killing..
diego_berta said:
so bad. still same problem.
devices installed, sdk installed (with superuser and su), kindle is recognized as android composite adb interface, kindle software version 7.2.3
i tried some tutorials with cmd, with qemu and with "root many android"
here the problems:
WITH CMD) Error: cannot create /data/local.prop permission denied
WITH Qemu) Error: you must install your device specific drivers so that the device is visible to ADB
WITH ROOT MANY ANDROID) Error: adb server is out of date. killing..
thanks guys to help but it didn't work yet i'm lost
Click to expand...
Click to collapse
Looks like you made quite a bit of progress. If I understand correctly, you have the driver installed and when you go into the Windows Device Manager you actually see "Android Composite ADB Interface" when the Kindle is plugged into USB, correct?
Looks like the SDK ADB Server is running or someones ADB Server is running. Drop to CMD and type: adb devices do you see a serial number? If yes, this is your Kindle, type: adb kill-server - this should terminate any adb server running. Now run Root Many Android, choose normal method. Ignore the errors, does the Kindle show a Restore All dialogue box? If yes, proceed to my original response. If no, are you sure you have enabled ADB on the Kindle? Also, when the Root Many Android and Qemu Batch files run, they both call to there own ADB Server. If you created a PATH statement in Windows pointing to the SDK ADB Server, there is a possibility of failure in these scripts. To eliminate this possibility, Rename the SDK ADB executable to ADB-TEMP, then run Root Many Android, does the error "Error: adb server is out of date. killing.." disappear? If yes, proceed in Normal mode IGNORING all the errors. When you execute the Root Many Android batch file, it will attempt to communicate with the Kindle and transfer some files through ADB. You will know this transfer was successful when the Kindle has an active dialogue box asking to "Restore All".
Note: The idea at this point is to focus on getting the ADB Communication path opened to your Kindle, once this is done everything else should be easy. Also, run Root Many Android and Qemu from your desktop. That is, when you extract these utilities, extract them to a folder on your desktop.
ADB driver
Raffo17 said:
hi guys i'm a new forum member. I'm trying to root my kindle fire hd (7.2.3) but when i run "RunMe.bat" the device seems not to be connected! I've enabled the adb on the kindle and installed the ADB driver package. help!!!
ps sorry for my english
Click to expand...
Click to collapse
What version of Windows are you running? Is your version of Windows 32-bit or 64-bit? If you plugin your Kindle Fire 7" HD to USB do you see the Kindle drive in My Computer? The Kindle power is on and the battery has a solid charge, correct?
Depending on your version of Windows, the directions will vary a little bit. Let's look in the Windows Device manger: Right Hand Mouse Click on My Computer or Computer, choose Properties. Now Click on Device Manager. Do you see something like "android composite adb interface" in the device manager when the Kindle is Powered up and plugged into USB?
Reply back with the answers and I will try to help you.
diego_berta said:
so bad. still same problem.
devices installed, sdk installed (with superuser and su), kindle is recognized as android composite adb interface, kindle software version 7.2.3
i tried some tutorials with cmd, with qemu and with "root many android"
here the problems:
WITH CMD) Error: cannot create /data/local.prop permission denied
WITH Qemu) Error: you must install your device specific drivers so that the device is visible to ADB
WITH ROOT MANY ANDROID) Error: adb server is out of date. killing..
thanks guys to help but it didn't work yet i'm lost
Click to expand...
Click to collapse
Open a cmd prompt and type this command:
Code:
android update adb
Then type these:
Code:
adb kill-server
adb start-server
adb devices
If all is working properly then you should see the device listed as a serial number
prokennexusa said:
What version of Windows are you running? Is your version of Windows 32-bit or 64-bit? If you plugin your Kindle Fire 7" HD to USB do you see the Kindle drive in My Computer? The Kindle power is on and the battery has a solid charge, correct?
Depending on your version of Windows, the directions will vary a little bit. Let's look in the Windows Device manger: Right Hand Mouse Click on My Computer or Computer, choose Properties. Now Click on Device Manager. Do you see something like "android composite adb interface" in the device manager when the Kindle is Powered up and plugged into USB?
Reply back with the answers and I will try to help you.
Click to expand...
Click to collapse
first of all thx for your reply. On my pc runs Windows 7 Professional 64-bit. when i plugin my kindle i can see it in my computer and obviously it's power on :laugh:
furthermore in Device Manager when i click on kindle i can see "android composite adb interface"!
the only thing that I could not install is the sdk.
Raffo17 said:
first of all thx for your reply. On my pc runs Windows 7 Professional 64-bit. when i plugin my kindle i can see it in my computer and obviously it's power on :laugh:
furthermore in Device Manager when i click on kindle i can see "android composite adb interface"!
the only thing that I could not install is the sdk.
Click to expand...
Click to collapse
Raffo17,
Unless you are going to do Android software development, you can do without the SDK. People like Bin4ry (Root MANY ANDROID!) and sparkym3 (Qemu automated root) have spent a lot of time to develop these tools so we can focus on other aspects of the Kindle.
Judging by your response, it looks like nothing should stop you from Rooting the Kindle. Go back to my original response in this Thread, download and extract to your desktop Root MANY ANDROID! and Qemu automated root. When you run Root MANY ANDROID! in Normal Mode, you will notice quite a few errors, ignore these errors. You will know that Root MANY ANDROID! has done its job when your Kindle asks to be Restored and then your Kindle will Reboot.
Go back to my instructions and remember, you are performing a risky upgrade(although it is worth it), so be careful.
prokennexusa said:
Looks like you made quite a bit of progress. If I understand correctly, you have the driver installed and when you go into the Windows Device Manager you actually see "Android Composite ADB Interface" when the Kindle is plugged into USB, correct?
Looks like the SDK ADB Server is running or someones ADB Server is running. Drop to CMD and type: adb devices do you see a serial number? If yes, this is your Kindle, type: adb kill-server - this should terminate any adb server running. Now run Root Many Android, choose normal method. Ignore the errors, does the Kindle show a Restore All dialogue box? If yes, proceed to my original response. If no, are you sure you have enabled ADB on the Kindle? Also, when the Root Many Android and Qemu Batch files run, they both call to there own ADB Server. If you created a PATH statement in Windows pointing to the SDK ADB Server, there is a possibility of failure in these scripts. To eliminate this possibility, Rename the SDK ADB executable to ADB-TEMP, then run Root Many Android, does the error "Error: adb server is out of date. killing.." disappear? If yes, proceed in Normal mode IGNORING all the errors. When you execute the Root Many Android batch file, it will attempt to communicate with the Kindle and transfer some files through ADB. You will know this transfer was successful when the Kindle has an active dialogue box asking to "Restore All".
Note: The idea at this point is to focus on getting the ADB Communication path opened to your Kindle, once this is done everything else should be easy. Also, run Root Many Android and Qemu from your desktop. That is, when you extract these utilities, extract them to a folder on your desktop.
Click to expand...
Click to collapse
thanks again prokennexusa, tomorrow i'll try it then i reply to this post and tell news... sorry bad english
Update - Kindle Fire HD Root then install Google Play
diego_berta said:
thanks again prokennexusa, tomorrow i'll try it then i reply to this post and tell news... sorry bad english
Click to expand...
Click to collapse
Diego_berta,
I will be available tomorrow, so I will watch for your response.
Rooting kindlefireHD 7.2.3
hello there,
now i have tried to do all of this under windows 7 32b.
But have same problem. When i run adb.exe devices, its doesnt return me anything. Just empty.
I have Kindle in mz computer, so the drivers is installed succesfully.
Any idea why i get empty list in device with adb.exe command ?
prokennexusa said:
Diego_berta,
I will be available tomorrow, so I will watch for your response.
Click to expand...
Click to collapse
hi prokennexusa again, i rooted the kindle with succes with root many androids but it react very slowly but it's blocked i can't do nothing sorry bad english
diego_berta said:
hi prokennexusa again, i rooted the kindle with succes with root many androids but it react very slowly but it's blocked i can't do nothing sorry bad english
Click to expand...
Click to collapse
Diego_Berta,
Looks like you are at Step 2, proceed to Step 3 and now run Qemu automated root, the Kindle will return to normal speed once you have completed ALL the steps.
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
---------- Post added at 12:05 PM ---------- Previous post was at 11:54 AM ----------
dagelo said:
hello there,
now i have tried to do all of this under windows 7 32b.
But have same problem. When i run adb.exe devices, its doesnt return me anything. Just empty.
I have Kindle in mz computer, so the drivers is installed succesfully.
Any idea why i get empty list in device with adb.exe command ?
Click to expand...
Click to collapse
Dagelo,
The utility adb is used for Android Software development and advanced users. Sure you can root the Kindle using adb but you need to spend time learning the adb commands. I would recommend you download Root MANY ANDROID! and Qemu automated root, use these utilities to root your Kindle 7" Fire HD - they have adb embedded in each utility, so no need to install the SDK.
The following steps assume you have the Kindle plugged into USB, the driver is installed, you can see the adb driver in Windows Device Manager and adb is enabled on the Kindle (go back to the beginning of this tread for more details).
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete all the steps.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root!
---------- Post added at 12:25 PM ---------- Previous post was at 12:05 PM ----------
dagelo said:
hello there,
now i have tried to do all of this under windows 7 32b.
But have same problem. When i run adb.exe devices, its doesnt return me anything. Just empty.
I have Kindle in mz computer, so the drivers is installed succesfully.
Any idea why i get empty list in device with adb.exe command ?
Click to expand...
Click to collapse
Dagelo,
If you want to work with ADB, open a new Thread since this thread seems to be focusing on Rooting Kindle 7" Fire HD and then installing Google Play. I would be happy to try to help in the new thread, although since there are many capable people in this community so you will probably not need my help.
There can be many reasons for the missing device: Device driver problem, ADB out of date, ADB disabled on the Kindle, etc.
Send me a PM once you open the new thread.
no sorry i didn't tell you all... the qemu doesn' t work it gives me the same error: you must install your device specific drivers so that the device is visible to ADB. tomorrow i'll try again with qemu and i'll tell u all... thanks again, good night!
diego_berta said:
no sorry i didn't tell you all... the qemu doesn' t work it gives me the same error: you must install your device specific drivers so that the device is visible to ADB. tomorrow i'll try again with qemu and i'll tell u all... thanks again, good night!
Click to expand...
Click to collapse
diego_berta,
So if I understand you correctly:
A) You have installed the device drivers and ADB driver shows up in Windows Device Manager
B) You ran Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
C) When executed Root MANY ANDROID! RunMe.bat in Normal Mode
D) You pressed "Restore" On the Kindle and the Kindle rebooted
Now the Kindle is slow and will not do anything - this is normal.
Leave the Kindle plugged into USB - turned on, you are 1/2 way done!
The error you are describing in Qemu is normal and can be ignored. Run Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838 following these detailed instructions:
1) Plug in the Kindle Fire 7" HD into USB
2) On your desktop should be Qemu, open the folder
3) Run RootQemu.bat
4) Select Option 1 - Root
5) Ignore the first error, press Enter
6) Ignore the second error/warning, press Enter
7) ADB daemon will start and detect the Kindle
8) Next it will begin to transfer the binary files across ADB, then Exploit the Kindle
9) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
10) Press Enter
11) ADB daemon will start and detect the Kindle
12) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
13) Continue to follow the Qemu instructions allowing the Kindle to be detected by Windows again - about 60-120 Second after every reboot
14) After about 2 - 3 more Reboots Qemu will test the Superuser account and display a Success message
15) When fully completed Qemu will close automatically
16) You should now have root
17) Download and install Root Explorer from the Amazon Apps - it is free
18) Go back to the beginning of this Thread and follow the instructions to install Google Play
prokennexusa said:
diego_berta,
So if I understand you correctly:
A) You have installed the device drivers and ADB driver shows up in Windows Device Manager
B) You ran Root MANY ANDROID!. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
C) When executed Root MANY ANDROID! RunMe.bat in Normal Mode
D) You pressed "Restore" On the Kindle and the Kindle rebooted
Now the Kindle is slow and will not do anything - this is normal.
Leave the Kindle plugged into USB - turned on, you are 1/2 way done!
The error you are describing in Qemu is normal and can be ignored. Run Run Qemu automated root following these detailed instructions:
1) Plug in the Kindle Fire 7" HD into USB
2) On your desktop should be Qemu, open the folder
3) Run RootQemu.bat
4) Select Option 1 - Root
5) Ignore the first error, press Enter
6) Ignore the second error/warning, press Enter
7) ADB daemon will start and detect the Kindle
8) Next it will begin to transfer the binary files across ADB, then Exploit the Kindle
9) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
10) Press Enter
11) ADB daemon will start and detect the Kindle
12) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
13) Continue to follow the Qemu instructions allowing the Kindle to be detected by Windows again - about 60-120 Second after every reboot
14) After about 2 - 3 more Reboots Qemu will test the Superuser account and display a Success message
15) When fully completed Qemu will close automatically
16) You should now have root
17) Download and install Root Explorer from the Amazon Apps - it is free
18) Go back to the beginning of this Thread and follow the instructions to install Google Play
Click to expand...
Click to collapse
i moved vending.apk but the kindle is blocked again and gave me error. i had to restore all to factory settings... tomorrow i'll re-root the kindle but why it was blocked???
i try to root my kindle fire hd 7 7.2.3 using the tool Run Root MANY ANDROID! but nothing happens appear only :
If the device is not detected you may try to unplug it and reconnect it.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and other time appear:
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
ADB has all kinds of uses, but it's a pain to enable on Windows 7* with a Cyanogenmod Nook HD/HD+, especially with the spread out documentation. Not with this guide, however. (This is for emmc, no idea if it works with sdcard/hybrid installs)
Credit to Leapinlar for noticing the changed device ID.
EDIT: As jamus28 noted, you will also need the Google USB drivers. They come with the ADT.
1. Download usb_driver_r04-windows-B&N.zip here, courtesy of Leapinlar and B&N.
2. Enable Android debugging in developer settings.
3. Plug Nook into PC and open Device Manager.
4. Go to Portable Devices/BN Nook HD/HD+ and open properties.
5. Go to the details tab and then hardware ID's in the menu.
6. Leaving that window open, unzip the usb driver. Open the folder, and then open android_winusb.inf in an editor. (I used Notepad++)
7. In the .inf file, scroll through [Google.NTx86] and find your device name. Replace USB\whatever with the first hardware ID in the list from step 5.
8. Do the same in [Google.NTamd64]
9. Save and close the file, and then go back to device manager. Click update driver/browse my computer for software in properties.
10. Navigate through and choose the modified usb_driver_r04-windows folder.
11. Open your adb file location in command prompt and type adb devices. If a random string of letters and numbers show up labeled device, it worked. You can now use adb over usb. (and wifi, after enabling network adb on your device)
*Probably similar for other versions of Windows
I had to install the Google USB android drivers from the SDK as well. Without these, I spent hours trying to get it to work. The b&n drivers alone were not enough.
Win 7 x64
jamus28 said:
I had to install the Google USB android drivers from the SDK as well. Without these, I spent hours trying to get it to work. The b&n drivers alone were not enough.
Win 7 x64
Click to expand...
Click to collapse
Thanks both Ardent_V and jamus28 for the explanation.
Yes I have to apply both methods in order to have the adb command to recognize my Nook HD+ device ID.
I'm using windows 7 x64.
Sorry. I assumed if you had adb you would have the SDK and Google drivers as well.
On previous devices, adb.exe and a few DLLs were enough.
Thank you for posting this!!!
I did have to deviate from the instructions a bit to get it working though.
1. In the INF file, I had to use the *second* line from Hardware Id's, not the first. The value that worked for me in the INF file is:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&MI_01
The first Hardware Id's line has a "REV_02" in it; Windows would not accept the driver with that in it. Took that part out and it worked!
2. Instead of updating the driver in Device Manager from Portable Devices, I had to update the "BN NookHD+" that was listed with a yellow symbol under "Other devices." Then I got the expected Android Phone -> Android Composite ADB Interface device to show up in the list.
3. ADB at first listed the device as "offline." I had ADB working on stock and didn't realize that the newer version of Android has an extra security check. I actually had to Google it to realize that I just had to unlock the tablet and hit "Accept" on a dialog box on the device! After that, it went from "offline" to "device" and all was well.
What's a bit strange is that before ADB listed a random bunch of letters and numbers (a device ID I guess?). But now it lists the Nook as 012345679ABCEDEF. I'm guessing that's just how it works under CM10.1? I suppose it hardly matters.
The bottom line is that I got it to work, thanks to this thread. Nice!
Steve Tack said:
What's a bit strange is that before ADB listed a random bunch of letters and numbers (a device ID I guess?). But now it lists the Nook as 012345679ABCEDEF. I'm guessing that's just how it works under CM10.1? I suppose it hardly matters.
Click to expand...
Click to collapse
That's just me being lazy and not gettin around to pass around serial number yet.
Steve Tack said:
Thank you for posting this!!!
I did have to deviate from the instructions a bit to get it working though.
1. In the INF file, I had to use the *second* line from Hardware Id's, not the first. The value that worked for me in the INF file is:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&MI_01
The first Hardware Id's line has a "REV_02" in it; Windows would not accept the driver with that in it. Took that part out and it worked!
2. Instead of updating the driver in Device Manager from Portable Devices, I had to update the "BN NookHD+" that was listed with a yellow symbol under "Other devices." Then I got the expected Android Phone -> Android Composite ADB Interface device to show up in the list.
3. ADB at first listed the device as "offline." I had ADB working on stock and didn't realize that the newer version of Android has an extra security check. I actually had to Google it to realize that I just had to unlock the tablet and hit "Accept" on a dialog box on the device! After that, it went from "offline" to "device" and all was well.
What's a bit strange is that before ADB listed a random bunch of letters and numbers (a device ID I guess?). But now it lists the Nook as 012345679ABCEDEF. I'm guessing that's just how it works under CM10.1? I suppose it hardly matters.
The bottom line is that I got it to work, thanks to this thread. Nice!
Click to expand...
Click to collapse
Made sure that I had updated Google Drivers and tried both strings and Windows showed no erros but when I type adb devices it is blank.
verygreen said:
That's just me being lazy and not gettin around to pass around serial number yet.
Click to expand...
Click to collapse
Hehe, figured it was something like that. Is there any downside to not having the real serial number returned? Doesn't seem to cause any issues that I've seen.
---------- Post added at 01:41 PM ---------- Previous post was at 01:36 PM ----------
dawgpoundfan said:
Made sure that I had updated Google Drivers and tried both strings and Windows showed no erros but when I type adb devices it is blank.
Click to expand...
Click to collapse
Do you see a device category in Device Manager called Android Phone? On my system, I see that and under that is a device called Android Composite ADB. Both times I've set it up, it wouldn't show up in ADB until I got to the point where that device showed up in the list.
If you do see that device, I suppose you could try "adb kill-server" before "adb devices" just for grins.
Steve Tack said:
Hehe, figured it was something like that. Is there any downside to not having the real serial number returned? Doesn't seem to cause any issues that I've seen.
Click to expand...
Click to collapse
Dunno, but 6/30 release added that. I imagine some apps might be using serial number for things like ensuring you don't steal stuff, also google play probably uses that to distinguish between several identical device you might have
If you are running the latest Carbon B11 emmc, and are wondering why you can't get "adb devices" to show your device, you need to insert a line to:
%userprofile%\.android\adb_usb.inf
add: 0x2080
Without this, ADB will not recognize a device with a B&N VID.
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
Crap, just realized I skipped step 7 in Leapinlar's thread on setting up ADB...
error
Ardent_V said:
ADB has all kinds of uses, but it's a pain to enable on Windows 7* with a Cyanogenmod Nook HD/HD+, especially with the spread out documentation. Not with this guide, however. (This is for emmc, no idea if it works with sdcard/hybrid installs)
Credit to Leapinlar for noticing the changed device ID.
EDIT: As jamus28 noted, you will also need the Google USB drivers. They come with the ADT.
1. Download usb_driver_r04-windows-B&N.zip here, courtesy of Leapinlar and B&N.
2. Enable Android debugging in developer settings.
3. Plug Nook into PC and open Device Manager.
4. Go to Portable Devices/BN Nook HD/HD+ and open properties.
5. Go to the details tab and then hardware ID's in the menu.
6. Leaving that window open, unzip the usb driver. Open the folder, and then open android_winusb.inf in an editor. (I used Notepad++)
7. In the .inf file, scroll through [Google.NTx86] and find your device name. Replace USB\whatever with the first hardware ID in the list from step 5.
8. Do the same in [Google.NTamd64]
9. Save and close the file, and then go back to device manager. Click update driver/browse my computer for software in properties.
10. Navigate through and choose the modified usb_driver_r04-windows folder.
11. Open your adb file location in command prompt and type adb devices. If a random string of letters and numbers show up labeled device, it worked. You can now use adb over usb. (and wifi, after enabling network adb on your device)
*Probably similar for other versions of Windows
Click to expand...
Click to collapse
I followed all the steps. I got the device connected. When I tried to sideload a stock rom zip, I get an error. "failed to write data protocol fault <no status>". What can I do to fix it?
toplist said:
I followed all the steps. I got the device connected. When I tried to sideload a stock rom zip, I get an error. "failed to write data protocol fault <no status>". What can I do to fix it?
Click to expand...
Click to collapse
What do you mean sideload a stock rom zip? Sideloading is for apps.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
What do you mean sideload a stock rom zip? Sideloading is for apps.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I had bokbokan's hybrid running on nook hd+. I saw an experimental version of cm10.2 and wanted to give it a try. I thought that since I can boot to stock and cm, I don't need to go back to my original bn rom. So, I deleted my cm10,1 zip from my internal storage and replaced it with cm10.2. I turned off my tablet, took out my sd card with hybrid and rewrote it with cwm for sd cm10.2. The cm10.2 updates but doesn't work when you reboot. When I turned back on, my nook gets stuck on infinite loop cyanogenmod logo instead of booting to stock . Clockworkmod shows that I have a backup but when I try it says "no files found." I have backups for original bn rom and a cm version on my pc. But since there is only 115 mb space left on my sd card after writing, I can't copy my 1+ GB back up files. I was searching on google and I came across how to update rom using adb sideloading and was trying that. That's where I get this error message. Is there any way for me get out of this mess and go back to cm? :crying::crying::crying:
toplist said:
I had bokbokan's hybrid running on nook hd+. I saw an experimental version of cm10.2 and wanted to give it a try. I thought that since I can boot to stock and cm, I don't need to go back to my original bn rom. So, I deleted my cm10,1 zip from my internal storage and replaced it with cm10.2. I turned off my tablet, took out my sd card with hybrid and rewrote it with cwm for sd cm10.2. The cm10.2 updates but doesn't work when you reboot. When I turned back on, my nook gets stuck on infinite loop cyanogenmod logo instead of booting to stock . Clockworkmod shows that I have a backup but when I try it says "no files found." I have backups for original bn rom and a cm version on my pc. But since there is only 115 mb space left on my sd card after writing, I can't copy my 1+ GB back up files. I was searching on google and I came across how to update rom using adb sideloading and was trying that. That's where I get this error message. Is there any way for me get out of this mess and go back to cm? :crying::crying::crying:
Click to expand...
Click to collapse
See my response in my HD/HD+ Tips thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
See my response in my HD/HD+ Tips thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I read your post and went through 15 pages to see if you wanted me to find anything specific. But I'm not sure what I should look for. I tried step 1 and step 2 from your post. When I tired to sideload app, I get "errors:closed" (attached image). I don't know what to do :crying:. My sdcard has CWM based recovery V6.0.3.2 for hybrid. When it is inserted, I boot to recovery. When I take off the sdcard, I get to cyanogenmod logo with infinite loop (attached image). Did I break my tablet? Is there any solution to fix this?
toplist said:
I read your post and went through 15 pages to see if you wanted me to find anything specific. But I'm not sure what I should look for. I tried step 1 and step 2 from your post. When I tired to sideload app, I get "errors:closed" (attached image). I don't know what to do :crying:. My sdcard has CWM based recovery V6.0.3.2 for hybrid. When it is inserted, I boot to recovery. When I take off the sdcard, I get to cyanogenmod logo with infinite loop (attached image). Did I break my tablet? Is there any solution to fix this?
Click to expand...
Click to collapse
I wanted you to respond on my HD/HD+ Tips thread, that is why I posted the answer there. I don't want to clutter this thread with non ADB things. Continue this discussion on my thread.
It is not broke. Make the CWM SD as detailed in item 1a. Then use that to restore your stock backup.
Sent from my Nook HD+ running CM10.1 on emmc.
Ardent_V said:
ADB has all kinds of uses, but it's a pain to enable on Windows 7* with a Cyanogenmod Nook HD/HD+, especially with the spread out documentation. Not with this guide, however. (This is for emmc, no idea if it works with sdcard/hybrid installs)
Credit to Leapinlar for noticing the changed device ID.
EDIT: As jamus28 noted, you will also need the Google USB drivers. They come with the ADT.
1. Download usb_driver_r04-windows-B&N.zip here, courtesy of Leapinlar and B&N.
[Steps 2 to 10 removed for brevity.]
11. Open your adb file location in command prompt and type adb devices. If a random string of letters and numbers show up labeled device, it worked. You can now use adb over usb. (and wifi, after enabling network adb on your device)
*Probably similar for other versions of Windows
Click to expand...
Click to collapse
I recently installed the CM10.2 ROM on my Nook HD (I don't mind living dangerously!) To my surprise, I found that ADB worked out of the box, and the Nook showed up as MyNook in Windows Explorer and in Device Manager (under Portable Devices). However, after I installed the Eclipse+ADT bundle on my PC yesterday, ADB over USB stopped working, although I could still use ADB over wifi and could still open MyNook in Explorer.
So I thought I would try the instructions in the above post to repair ADB over USB. Everything seemed to work fine, there were no error messages, and ADB over USB is indeed working again. BUT, the MyNook Device Manager entry under Portable Devices has disappeared, to be replaced by an Android Composite ADB Interface entry under Android Phones, and the Nook no longer appears in Windows Explorer. In Devices and Printers it appears as a camera icon labelled "MTP" - strangely, as of course the Nook HD doesn't have a camera.
Does anyone have any suggestions for how I might get everything working again? Or would I be best to use System Restore to go back to how things were before?
My PC is running Windows 7 SP1 Home Premium.
UPDATE
=======
I have now solved this. I disconnected the Nook HD, disabled the Android Composite ADB Interface in Device Manager, and reconnected the Nook. Windows 7 installed the drivers, and the Portable Device entry reappeared in Device Manager, this time called "BN Nook HD" rather than "MyNook" (an improvement!). I then re-enabled the Android Composite ADB Interface, and everything is now working. The Nook is visible in Windows Explorer; ADB is working via USB; and the Nook's icon in Devices and Printers is now that of a portable media device - it's still labelled "MTP", but I can live with that.
Android_winusb.inf entry for HD+ running official CM11
FWIW, I just installed ADB on my Win 8.1 PC and found that the entry needed in android_winusb.inf for the HD+ running official CM11 is:
Code:
;Nook HD+
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0005&MI_01
Note the trailing &MI_01, my ADB interface will not come up without it.