Related
Hello, I have CM 7.0.3 encore with the overclocked kernel on my nook. Lately I have not been able to get the thing to connect to my computer in either windows or Linux. (It's XP and "Lucid Lynx" 10.04 Ubuntu if that helps)
If I connect my cable to either the front of back USB ports (because I have tried both under both OSs) at best I get my windows install to see and start to run auto hardware install. This, of course does not work and the machine will inform me that my new hardware (which it correctly ids as a nook until this point) may not work correctly. And, it does not. It displays as 'removable drive' and clicking on it pulls up an 'insert disk please' message.
In Ubuntu the Nook will show up as B&N Ereader. Both SD cards (the internal and the card in slot) show as the same thing. Clicking on them brings up a message that this drive is not a folder and cannot be opened as such.
This thread leads me to think that there should be a notification in windows about the usb being connected...and as soon as I post this I will be restarting to check that... but I really rather do this under Ubuntu. ETA. This does not work for me. Canceling the install software wizard does not work either. (I have been uninstalling the faulty installs each time and rebooting the comp without the nook attached. Oh, and the Nook IS awake too. )
Searches bring up nothing, and I'm a bit lost.
I must be missing something so basic and simple no one has had this issue but me. I mean, Android is a Linux variant, right? They should be able to talk to one another!??
If your trying to accomplish what I think you are then it doesn't matter what your computers says. Plug your Nook into the PC and open your notifications window. There should be a USB icon on the status bar waiting for your input. Just follow the prompts.
Given you have gone through the process of installing the Android SDK, in Linux, from the terminal you need to change to your target folder to
Code:
~/android-sdk-linux_86/platform-tools
then you need to log in as root and kill, then start the server. make sure to exit root when you are done.
Code:
su : enter password
# ./adb kill-server
# ./adb start-server
# exit
then it should pick it up.
I have the same problem as OP and went crazy trying to figure out what I was doing wrong. It's not as simple as everyone suggests.
To be clear I'm using Linux, Ubuntu Natty. I have a Samsung Vibrant also running CM7 nightlies. Start adb, plug in Vibrant, shows up in adb devices list without any problem. Plug in the NC no device in adb. running lsusb there is no android vendorID for the NC but there is for the Vibrant. The NC only shows a vendorID for the mass storage just like the OP says.
The NC is booting with CM7 nightlie on the SD card, not eMMC. Will that make a difference?
IFLATLINE, Thing is, there is no notification popup on my Nook for me to tap.
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
I did manage to brick the nook trying to update the build last night so I'm in the middle of reflashing it. So, as soon as I finish making a boot micro SD (I know, I should just have one I keep for this but I don't) I will be flashing phiremod's version of CM7 on the nook.
digver, I did find somewhere on here that the OC kernel was causing some people grief and that once they removed it they had no issues connecting the the computer... but I think they were windows. I'm not sure if that will fix this very annoying little problem.
katsrevenge said:
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
Click to expand...
Click to collapse
personally i <3 linux. It's the only way to fly esp with dealing with Androids. Android Central has a GREAT write up on how to install the SDK on your Linux unit.
I'll have to look up the link @ home. I'm at work and WebSense blocks 99% of everything.
Has anyone gotten ADB over USB working with the NST 1.1 firmware? There seem to be guides all over the place, but they're either for the 1.0 firmware or for the original Nook, and every set of instructions I've followed doesn't do anything for me.
I'm trying to figure out why when I connect the NST to my computer via USB, adb can't see the device, no matter what I do. Looking at the ramdisk and the init.rc, it seems I have everything set up correctly. Of course, I could just use adb wireless that came with touchnooter, but I'd really like to get the USB version working again.
So, has anyone had any luck?
Not sure what ramdisk you're using but these are the ones used by most rooting methods around here.
The USB one works just fine, but I must say that getting the drivers set up on Windows 7 was a bit of a pita..
After trying several pre-packaged drivers I ended up editing the inf file in the android usb driver pack manually and got it working both at home and at work now, no problems.
Runs good on 1.1. here. I also tried a lot of drivers and the working one only after 3 installs. I think it was the driver of the forum here (but Im not sure anymore after that mess).
Gogolo2 said:
Runs good on 1.1. here. I also tried a lot of drivers and the working one only after 3 installs. I think it was the driver of the forum here (but Im not sure anymore after that mess).
Click to expand...
Click to collapse
Well, it's important to know that all those driver packages are actually based on the one you get with the Android SDK.
So people should save themselves the hassle and just get that one, and edit the android_winusb.inf manually.
Just add this to both the [Google.NTx86] and [Google.NTamd64] sections:
Code:
;B&N Nook Simple Touch
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0003&MI_01
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
Ah, and ofc you need to add/edit %USER/.android/adb_usb.ini
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2080
Thanks for the replies folks. Good to know that those ramdisks work well with 1.1 (those are the ones I've been using too)...so I must be doing something wrong, or my computer must be set up incorrectly. I'm on a Mac, so AFAIK, I don't need to install any extra usb drivers or anything.
I can connect fine to my phone with adb over usb, so I'm not sure why the nook is failing.
michaelwill said:
Thanks for the replies folks. Good to know that those ramdisks work well with 1.1 (those are the ones I've been using too)...so I must be doing something wrong, or my computer must be set up incorrectly. I'm on a Mac, so AFAIK, I don't need to install any extra usb drivers or anything.
I can connect fine to my phone with adb over usb, so I'm not sure why the nook is failing.
Click to expand...
Click to collapse
Well the ramdisks are nothing but a copy of the 1.1.0 ramdisk with adb enabled.
I have zero experience with OSx, but you might want to look at the Linux adb threads..
Yeah - there must be something wrong with my machine. I just reverted to the 1.0 version of the firmware, and went through the rooting procedure again, but my machine still can't see the device over ADB. I swear I had this working some weeks ago.
By the way, when you guys plug in the nook, and it shows the "USB mode" screen, do you first eject it from your PC, and then ADB works? Or does ADB work for you regardless of whether the NOOK drive is ejected or not?
Answering my own question here:
It turned out to be a fairly trivial solution - here's to not checking over your setup carefully enough.
It all came down to adding 0x2080 (the nook touch vendor id - which happens to be the same as the nook color vendor id - you can verify by using lsusb on linux) to the ~/.android/adb_usb.ini file, which basically just tells adb to look at additional vendor ids. This is stated clearly in the nook color docs, and I could have sworn that I did that hours ago, but when I re-looked at the file, I found mine was blank . As soon as I added 0x2080 back, everything started working perfectly.
Note, this is necessary for both mac and linux.
And, it doesn't matter if your NST is on the "Usb mode" screen or not; I got it to work both ways.
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?
Apologies if this is already posted somewhere. just point me to the link and I'll take a look, but everything I have tried so far has failed.
I have been trying to get adb working on my NookColor under Windows 7. I am running a rooted 1.4.2 stock image. I installed the sdk by following the guide at http://nookdevs.com/NookColor_USB_ADB, but when I get to step III.3.1, the device does not show up where the guide tells me it should. I gget a myNOOKcolor device under Portable Devices instead. I tried following the same procedure for this device, but when I get to step III.3.2.3, I get an error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I was able to follow the same procedure to install the driver for my MyTouch 4g. It looks to me like the problem s that Windows identifies my Nook as a portable storage device, rather than an unidentified device type, like my MyTouch was. I've tried uninstalling the driver, but it just reinstalls itself when I unplug and plug the device back in.
Any suggestions would be greatly appreciated.
marchingknight11 said:
Apologies if this is already posted somewhere. just point me to the link and I'll take a look, but everything I have tried so far has failed.
I have been trying to get adb working on my NookColor under Windows 7. I am running a rooted 1.4.2 stock image. I installed the sdk by following the guide at http://nookdevs.com/NookColor_USB_ADB, but when I get to step III.3.1, the device does not show up where the guide tells me it should. I gget a myNOOKcolor device under Portable Devices instead. I tried following the same procedure for this device, but when I get to step III.3.2.3, I get an error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I was able to follow the same procedure to install the driver for my MyTouch 4g. It looks to me like the problem s that Windows identifies my Nook as a portable storage device, rather than an unidentified device type, like my MyTouch was. I've tried uninstalling the driver, but it just reinstalls itself when I unplug and plug the device back in.
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I think the problem is the device id. I posted a workaround for CM9. It might be the same for your upgraded stock. See if my post helps. Look here:
http://forum.xda-developers.com/showthread.php?p=21665649
leapinlar said:
I think the problem is the device id. I posted a workaround for CM9. It might be the same for your upgraded stock. See if my post helps. Look here:
http://forum.xda-developers.com/showthread.php?p=21665649
Click to expand...
Click to collapse
Thanks for the post!
I looked at your workaround and it did not help. There is no nook entry under "Other Devices" in the device manager. the only entry for my nook is the "myNOOKcolor" under portable devices. When I right click on that and go to details, there is no device id listed.
Is there any chance that I may need to revert to 1.4.1 in order for this to work?
marchingknight11 said:
Thanks for the post!
I looked at your workaround and it did not help. There is no nook entry under "Other Devices" in the device manager. the only entry for my nook is the "myNOOKcolor" under portable devices. When I right click on that and go to details, there is no device id listed.
Is there any chance that I may need to revert to 1.4.1 in order for this to work?
Click to expand...
Click to collapse
With CM9, you have to be sure to have usb debugging turned on before the device will show up. That guide was written for an earlier version of the stock software. Is there anything like that in your stock software? Do you have to install nook tools to get at the setting? It's been a long time since I played with stock and the software has changed.
Edit: There is an alternate script listed in that referenced page you listed. Did you try that?
leapinlar said:
With CM9, you have to be sure to have usb debugging turned on before the device will show up. That guide was written for an earlier version of the stock software. Is there anything like that in your stock software? Do you have to install nook tools to get at the setting? It's been a long time since I played with stock and the software has changed.
Edit: There is an alternate script listed in that referenced page you listed. Did you try that?
Click to expand...
Click to collapse
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
marchingknight11 said:
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
Click to expand...
Click to collapse
Yes, but with difficulty. But you don't really want to install to /system, you want to install to /data (on emmc, which is the difficulty doing it from SD). You can use terminal emulator in CM7 to copy the files to emmc /data/apps. You first have to mount emmc /data. If you want to try that, I can help you.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
Yes, but with difficulty. But you don't really want to install to /system, you want to install to /data (on emmc, which is the difficulty doing it from SD). You can use terminal emulator in CM7 to copy the files to emmc /data/apps. You first have to mount emmc /data. If you want to try that, I can help you.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
Well something else actually occurred to me. Will I be able to copy apps to my sdcard (not the CM7 bootable, just a regular sd card), then copy them to /data/app using root explorer? If I can do that, there there's really no problem, I'll just have to deal with the fact that adb doesn't work.
If I can't do that, then yes, please help me do it using a bootable sd
marchingknight11 said:
Well something else actually occurred to me. Will I be able to copy apps to my sdcard (not the CM7 bootable, just a regular sd card), then copy them to /data/app using root explorer? If I can do that, there there's really no problem, I'll just have to deal with the fact that adb doesn't work.
If I can't do that, then yes, please help me do it using a bootable sd
Click to expand...
Click to collapse
If you have root explorer working on emmc, yes you can do it that way. You can actually have root explorer just install for you also.
Sent from my Nook Color running ICS and Tapatalk
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
marchingknight11 said:
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
Click to expand...
Click to collapse
I am using CM10 on my nook color after spending 8+ hours yesterday finally being able to get back to where I started. I can again see my nook and the card but it is now showing up under portable devices. I used to have them listed as drives. this is fine as I have access to the card after I click on the nook in File explorer. I would like it the previous set-up just because Calibre has my card and device flipped and its easy to confuse me. I learned that if I can label my nook f and the card g Calibre will think the first letter is the main drive.
My original reason for this post: I can not find where to disable the automount in CM10 can you tell me where you disabled it? and if anyone can wave their magic wand and get me back to where I can name my nook and card THANKS:fingers-crossed:
Droidatar said:
I am using CM10 on my nook color after spending 8+ hours yesterday finally being able to get back to where I started. I can again see my nook and the card but it is now showing up under portable devices. I used to have them listed as drives. this is fine as I have access to the card after I click on the nook in File explorer. I would like it the previous set-up just because Calibre has my card and device flipped and its easy to confuse me. I learned that if I can label my nook f and the card g Calibre will think the first letter is the main drive.
My original reason for this post: I can not find where to disable the automount in CM10 can you tell me where you disabled it? and if anyone can wave their magic wand and get me back to where I can name my nook and card THANKS:fingers-crossed:
Click to expand...
Click to collapse
You need to activate USB Mass Storage in CM10. It uses MTP by default. Go to settings, storage, menu, USB computer connection and check off Mass Storage rather than MTP. Then they show up as drive letters instead of under portable devices. You may also have to activate in the notification area.
And I think in Windows you can control what the drive letters are. Go to manage computer and select disk management and you can change the drive letters.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
You need to activate USB Mass Storage in CM10. It uses MTP by default. Go to settings, storage, menu, USB computer connection and check off Mass Storage rather than MTP. Then they show up as drive letters instead of under portable devices. You may also have to activate in the notification area.
And I think in Windows you can control what the drive letters are. Go to manage computer and select disk management and you can change the drive letters.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
THANK YOU, so very much it has been driving me crazy. I knew where that was to change it to mass storage but I just never guessed to hit menu. After I read your post I saw the tiny 3 dots in top right. I really should just wear my glasses
and Yes I have changed the letters in the past as you have noted. However it seems a mute point Calibre just released a new version that lets me correct that problem. However it's nice to have the mass storage issue fixed.
Thanks again
Hi folks, I am new here - have been reading for a few months and used NookManager to successfully root/re-root 2 NST and 1 NSTGlowlight now. Huge thanks to all developers!
Being a newbie with <10 posts, I was not allowed to post in the NookManager thread (http://forum.xda-developers.com/showthread.php?t=2040351). So I hope my post is more or less well-placed here.
I am very happy with the functionality of the Glowlight with firmware 1.2.1 rooted with NookManager.
The rooting process is really super-easy! So if possible I'd like to stick with it.
But... now I'd like to have the USB-host functionality as well to connect a keyboard and use the Nook for "typing-in-the-sun".
I have done some research but haven't found an easy way to achieve this.
I have found a description to add USB-host to a 1.2.1 NST (without Glowlight) which had been rooted with Nookmanager here: http://lararthompson.wordpress.com/2013/07/12/e-ink-writing-201-nst-1-2-1-rooted-with-usb-host/
... but unfortunately the uImage and uRamdisk linked/described in that article had the nasty side-effect of turning my NSTGlowlight into a simple NST (without Glowlight). So I had revert to my former backup and re-root with NookManager.
So my question is: What is the best and easiest way (if any) to achieve USB-host on a NST Glowlight with firmware 1.2.1 rooted with NookManager.
Thanks for your attention and help!
same situation
Hi, I'm also new on the forum, just bought my nook simple touch, did the root (Nook manager) and cound't post in the mentioned thread either so I decided to ask here. I wanted to ask if the apps/patches from the first site of that topic are ok for my firmware version 1.2.1? And can anyone explain how to:
1) apply the .diff file? I couldn't find any tips
2) how to install the usb host switcher? When I clicked the github link (from the post) I expected some .apk files, but there are some folders and other files instead. Where to put them so that it works?
3) I don't really get this: "Meanwhile you can simply switch the mode from adb, type
Code: echo host > /sys/devices/platform/musb_hdrc/mode" Where should I type it? Can it be done via cdm (windows) when I already connected my nook with the computer via wifi (and adb works fine)?
I would be really grateful for any hints. Android stuff is really not my thing, however, I would love to attach an external keyboard (I already bought a micro usb one). I have no problems following the instructions and I hope somebody will be that nice to explain it to me like I'm a child.
i want to buy an NST with glowlight but does usb host works on NST with glowlight??
There is a long thread on getting USB host support to work here: http://forum.xda-developers.com/showthread.php?t=1457971
In short, you need a kernel (uImage) that has some fixes in it for USB host mode.
Then (currently) you need something to force it into host mode.
I use my UsbMode.apk (download in the signature).
Glowlight and USB Keyboard
Hello there,
I've been through this and similar threads ten times now looking for a solution to have my NST Glowlight together with both - Glowlight AND usb-keyboard simultaniously. Unfortunately none of the uRamdisks posted do the trick. The one for 1.1.5 doesn't help in my case either because I'm on 1.2.0 (?)
So status as of todate is: I can either run the keyboard or have the lights on, depending on what uRamdisk is currently installed. I could live with that if I could take that solution outside into the sun, but:
bad girl is out playing until its dark and now wants to read a book, having no lightbulb near and having left home the laptop (with ADB to push uRamdisk for the light switch) and the Nook is running on the uRamdisk for the keyboard.
I'd like to ask now if there's the possibility to keep 2 uRamdisks on my Nook and switch them with RootExplorer or anything similar - but I can't find the uRamdisk anywhere on my Nook so I could just overwrite it. There's no boot - which might be good for girls like me who have no respect for the gadgets boot partitions But is there any (simple) way to make that partition visible using some (simple) tool that is on the Nook ? And then is it safe to just overrite that file and reboot ? Actually it shouldn't be any different from pushing the file via PC and do a restart, right ?
Would be so great if someone could help me, or was even still working on that problem of having an external keyboard working without losing the Glowlight. You guy's are doing such great work in providing people with more freedom to do what they want to do. So thank you so much, for all the information here !
No, you probably don't want to deal with two separate uRamdisk's.
(Ok, you could keep one bootable system on SD card and one internal, but that's a hassle.)
There should be a NG1 (Nook Simple Touch with Glowlight, the black case) uImage with support for glowlight and USB mode.
Unfortunately there are so many uImage/uRamdisk floating around that I've lost track.
uImage and uRamdisk
Found it. Can hardly believe it. Thought I really had tried them all. Thanks Renate for your reply. You mentioning that there MUST be one that fits tricked me into starting to search and test from scratch
5 hours later ...
Its "uImage_mt_usbhost_nopowercheck_115.zip" and "uRamdisk_NTG_115_usb.zip" and I have no idea where i found them but with the file name others should be able to find them i hope.
For those with the same problem:
my Nook ST Glowlight has Software Version 1.2.0 (which can't be changed or updated, god knows why ...) and was rooted with NookManager plus NSTAppsAttack installed. For everyone having the same device, the two files above work. They enable keyboard support and keep Glowlight and Multi-Touch working. Just push uImage and uRamdisk using ADB to the boot partition (after rooting) and everything should be fine.
Thanks to all the guys here at xda providing so much help
SusanneM said:
Its "uImage_mt_usbhost_nopowercheck_115.zip" and "uRamdisk_NTG_115_usb.zip" and I have no idea where i found them but with the file name others should be able to find them i hope.
Click to expand...
Click to collapse
Can you please tell me what does the "nopowercheck" signify ?
and what is 115 ? is it the build number, same as 166, 174, 176 ?
Thanks.
115 refers to the (then most recent) Nook software version 1.1.5
The kernel did not change much (I don't think) between 1.1.5 and 1.2.1
You should all be using the 1.2.1 Nook update with whichever kernel works for you.
The latest white Nook Glow has version 1.3 which actually has some older parts in it than the 1.2.1
SusanneM said:
Just push uImage and uRamdisk using ADB to the boot partition (after rooting) and everything should be fine.
Click to expand...
Click to collapse
Hello,
I'm new to the Nook simple root community and new to the Android world.
I try to enable the usb port of my NG1, to use an external keyboard, but i have some difficulties
I've tried to push uImage and uRamdisk via adb but:
1. can't push it, i have the read-only message
2. what is the boot partition, i tried /boot and /root
Thank you if you have any information to help me do this.
/dev/block/mmcblk0p1 is the boot partition.
If you are using noogie, it's mounted and it's what you see.
If you are running ClockWork Mod there should be an option to mount /boot
If you are just running ADB:
Code:
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
Thanks for the quick answer.
In fact, i'm trying with adb, but i think i can't connect because mu computer is on RJ45 and not wifi.
So, how Noogie and Clockwork let me change the uImage et uRamdisk ? via usb ?
edit: in fact i'm lost here, i don't understand how to replace the uImage and uRamdisk files without adb ...
I used the noogie root method to acces the boot partition and replace the uImage and uRamdisk.
After rebooting, i plugged the mini usb keyboard i bought, but it didn't light up. Any way to be sure the usb host is activated ?
Use UsbMode.apk (in the signature).
You need to use an OTG adapter (any kind) that grounds the ID pin in the micro USB connector.
There's a whole long thread on this:
http://forum.xda-developers.com/showthread.php?t=1457971
I installed the UsbMode.apk, thank you.
Do i understand well ? I need to buy an adapter that turns the micro USB connector of the keyboard into a regular USB + an OTG that turns the regular USB into another micro USB in order to ground the ID pin ?
There are plenty of adapters for sale that are micro USB plug (with grounded ID pin) to female full-size USB.
Look up "USB OTG adapter" on eBay.
Since my keyboard is already a micro USB plug, i was wondering if it could work with 2 adapters.
But i try with a micro USB femelle to regular USB before the OTG and it works. Thanx
Now i need to install a azerty french keyboard.
I use, as i read, ES FILE EXPLORER to place the keyboard.apk into system/app, but it refuses to copy.
I'm wondering why...
The copy is probably failing because you haven't given write access to the system.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
Oh. How do i do that ?
You can just use a regular install, it doesn't have to go into /system/app
You'll have to enable the keyboard after it is installed.