Database Users

[Q] USB Host for non-techs

I just started a wiki here
USB Host mode
I am hoping that you who actually know how to do it would help develop a set of instructions that are simple enough for a literate, adventurous non-tech (like me) to follow.
UPDATE: The wiki now has a complete list of installation instructions. You'll have to hunt through verygreen's thread below for operating instructions till they organized on the wiki.
The wiki and this thread (where noobs like me can post) are based on verygreen's
[WIP] USB Host support (working)
I asked verygreen and ros87 to do the USB Host mode for the Nook Simple Touch. Verygreen announced success within 48 hours. The hack has gotten whipped into shape there with the amazing help of ros87, Renate NST, mali100, and other superb xda people.
The project started at mobileread.com:
Project: E-Paper Tablet (touch-typable!)
Thanks to fellow mobilereaders for support, especially Kumabjorn, poliorcetes, and nealsharmon for donating money for devices.
The wiki is super rough. It assumes a new device in the box and a non-tech user. I started the instructions to show how simple they need to be. I will continue helping with that because it does seem difficult for techs to believe just how lost we can be with this stuff. My goal is to bridge the gap between techs and literate users so that non-programmers who want to type on the NST can. If you are an expert writer of users manuals, maybe you would help, too.
Honestly, I don't know the first thing to do now that my NST is on and registered. For example, I don't even know if I need to:
root the NST first
install adb (which I also don't know about)
or what. I have studied the thread, so I will be familiar with the terms. But I'm completely clueless about actually doing the hack. I managed to unbox my refurbished NST, update its software to 1.1.2 and install a microSD card. The issue is, what exactly should be done now? Please leave your answers in the wiki! Thank you!

I would say the best way to start is from eded333's Minimal Touch http://forum.xda-developers.com/showthread.php?t=1346748 . That gives you a nice system with market and a launcher to install and start your texteditor or writing apps.
If I find some time i will create a small update-package that installs all the necessary things for the usb-host mode.

Cool. Will the 1.1.2 NST software update screw any of this up? I have it installed now because it fixed wifi connection issues that affected me.

andrewed said:
Cool. Will the 1.1.2 NST software update screw any of this up? I have it installed now because it fixed wifi connection issues that affected me.
Click to expand...
Click to collapse
1.1.2 is fine. You can still use eded333's MinimalTouch to root it and get a launcher.

Awesome. Will dive in, then!

As promised I created a small update package, to install all the necessary files and tools.
It is installable via Clockwork Recovery in the same way as eded333's MinimalTouch, which should be installed first, to get root, a launcher and a working Market.
Requirements:
Software version 1.1 or 1.1.2 (1.1.2 is recommended, as it fixes WLAN issues)
root, a launcher and working market (I recommend using eded333's MinimalTouch)
What it does:
changes the kernel to NST-kernel v0.1 with USB-Host and multitouch support
changes the uRamdisk to a uRamdisk with fixed init (needed for USB Input devices) and adb-usb
installs the busybox and sqlite binaries
adds the permission node for multitouch to /etc/permissions/required_hardware.xml
installs the app UsbMode-1.2 and the NullKbd-1.1 by Renate NST
adds the permission to enable the NullKbd
changes the qwerty.kl and qwerty.kcm.bin to the remapped one by Renate NST
installs the NookColorTools, so you can switch to the NullKbd
DISCLAMER and WARNING:
I'm not responsible for bricked devices, dead SD cards, lost data, fried USB-Devices. Make a backup before you try anything described here!
USB-Host support is still WIP (work in progress), the battery drain is noticeable higher.
this is the first release and only tested by myself, so don't expect it to be bulletproof.
Credits go to:
verygreen, ros87 and everybody who helped with the USB-Host mode,
Renate NST, for all the effort making USB-Host support userfriendly (USB-Mode app, NullKbd, key remapping, testing),
wheilitjohnny and arkusuma for the Multitouch support,
eded333, for his great MinimalTouch,
Download:
usb-host-mt-pack_0.1.zip

Thanks, mali100.
I'd just like to point out that you can switch to the NullKbd just by hitting the Ctrl key and selecting it from the popup IME picker.

Renate NST said:
I'd just like to point out that you can switch to the NullKbd just by hitting the Ctrl key and selecting it from the popup IME picker.
Click to expand...
Click to collapse
Nice easter-egg didn't noticed this before. Thanks

Ok, I will have to get a card reader. In the meantime, I'm getting a grip on the instructions by reading through the fine print. It led me to the noogie/backup process.
It says I need a class 6 microSD card. but I got a class 2 as per verygreen's instructions for the hack itself. Do I definitely also need a class 6 card just for the backup, or can I use my class 2 card?
Now that the hack is finally in reach, I want to do it right.

andrewed said:
Ok, I will have to get a card reader. In the meantime, I'm getting a grip on the instructions by reading through the fine print. It led me to the noogie/backup process.
It says I need a class 6 microSD card. but I got a class 2 as per verygreen's instructions for the hack itself. Do I definitely also need a class 6 card just for the backup, or can I use my class 2 card?
Now that the hack is finally in reach, I want to do it right.
Click to expand...
Click to collapse
I'm using a 4G class 2 micro SD card for NOOGIE and it's fine.

where to?
Hi where to put content of META-INF? (dont wanna root again...)

mrWax said:
Hi where to put content of META-INF?
Click to expand...
Click to collapse
The META-INF folder contains the insallation script and the interpreter for the script, they are used by CWM to install the package and not copied to the nook.
(dont wanna root again...)
Click to expand...
Click to collapse
If you mean that your device isn't rooted, and you don't want to, then I have to tell you that root is needed to switch between usb-host mode and peripheral-mode, so root is mandatory.
If you mean your device is already rooted and you don't want to redo it, then don't worry, this package doesn't contain files that root the nook.

I had already rooted my nook another way...now what?
Friends,
I rooted my Nook using the instructions here (SalsichaNooter):
http://www.youtube.com/watch?v=O05Y7C9a4eU
I didn't use the Clockwork method. I don't know how to revert and go back to your original instructions. I tried downloading usb-host-mt_pack-0.1.zip and installing the apps only but that didn't work.
Any suggestions on how I should go about the process without Clockwork? Or should I follow these directions to install clockwork even though I'm already rooted with SalsichaNooter?
I really would like to get a keyboard working on my Nook and feel like I'm so close.

nealsharmon said:
I didn't use the Clockwork method. I don't know how to revert and go back to your original instructions.
Click to expand...
Click to collapse
You don't have to revert anything, a device rooted with salsichanooter works fine.
I tried downloading usb-host-mt_pack-0.1.zip and installing the apps only but that didn't work.
Click to expand...
Click to collapse
That's because you also need another kernel and uramdisk and some configuration, that gets done by the updatepackage.
Any suggestions on how I should go about the process without Clockwork? Or should I follow these directions to install clockwork even though I'm already rooted with SalsichaNooter?
Click to expand...
Click to collapse
This update-package can only be installed with the Clockwork-mod recovery. You don't have to install CWM on the Nook, just write it to a sdcard (like you did with the salsichanooter image), copy the updatepackage onto the sdcard, put the card into the nook and reboot. The Nook then boots into Clockworkmod Recovery, then you got to "install zip from sdcard", choose the usb-host-package, click yes and wait, eject the sd card, and click reboot.

thank you
Thanks for your input. I will try the process you suggested.

It worked!
mali100 said:
You don't have to revert anything, a device rooted with salsichanooter works fine.
That's because you also need another kernel and uramdisk and some configuration, that gets done by the updatepackage.
This update-package can only be installed with the Clockwork-mod recovery. You don't have to install CWM on the Nook, just write it to a sdcard (like you did with the salsichanooter image), copy the updatepackage onto the sdcard, put the card into the nook and reboot. The Nook then boots into Clockworkmod Recovery, then you got to "install zip from sdcard", choose the usb-host-package, click yes and wait, eject the sd card, and click reboot.
Click to expand...
Click to collapse
I followed your instructions and it worked. Thank you very much.

Still Not working
I'm very new at this.
I have followed the above directions and patched with usb-host-mt-pack_0.1 successfully but my two USB keyboards are still not working.
I originally rooted my nook using TouchNooter 2.1.31.
I am using an OTG cable and am getting the solid green light after turning off current and selecting Host.
When i plug either keyboard (or bluetooth dongle for that matter) State changes from a_idle to a_host.
Other results:
Keyboard: none
all fields below that are blank.
Any suggestions on how i should proceed? Could this just be a matter of the keyboards not being compatible? What are the recommended keyboards?
Many thanks!

When you are having trouble, try a wall-powered hub (at least as a test).
I have seen where it switches to a_host but it's not really connected.
The "View USB" button is helpful and will show VID/PID.
If for some screwy reason you have a keyboard that is non-standard,
a lack of a black dot will indicate no driver is loaded.

Renate NST said:
When you are having trouble, try a wall-powered hub (at least as a test).
I have seen where it switches to a_host but it's not really connected.
The "View USB" button is helpful and will show VID/PID.
If for some screwy reason you have a keyboard that is non-standard,
a lack of a black dot will indicate no driver is loaded.
Click to expand...
Click to collapse
Thank you, Renate. That worked great. My Bluetooth is working and I'm using my apple wireless keyboard to word process. My arrow keys don't work so I have to do some touching or backspacing to edit in google documents.
I have a chronic case of CVS (eye condition). This is really gonna help me. Do you recommend a stand with space at the bottom for the cord?
Thank you so much!

Stand? I love mine. http://forum.xda-developers.com/showthread.php?t=1661902
You can use either a desk stand or the little bendy tripod.
The arrow keys should work, but they get rotated when in landscape mode.
There is a mod to make them not rotate.
http://forum.xda-developers.com/showthread.php?p=30260821&highlight=keyinputqueue#post30260821

[Q] Multitouch and the NTG

I attempted to use the multitouch kernel with clockwork mod after rooting my glowlight and for some reason it seems to have hosed the glowlight controls completely. I was hoping that the n2t recovery by ros87 would help but the server hosting the image is not working. Does anyone have a mirror of the image?
EDIT: In my panic I didn't check the entire thread and found a dropbox mirror of the file further on in the thread. Let this serve as a warning to first stay calm and also not to attempt multitouch on the NTG. Sorry if I wasted your time.

Schneicw said:
I attempted to use the multitouch kernel vi clockwork mod after rooting my glowlight and for some reason it seems to have hosed the glowlight controls completely. I was hoping that the n2t recovery by ros87 would help but the server hosting the image is not working. Does anyone have a mirror of the image?
Click to expand...
Click to collapse
Here you go.
Just wait for a NTG modded kernel, dont use the device specific resources for the NST.

Thanks for the quick response and the advice which I will be sure to remember. Any idea how long it's going to take to port multitouch to the NTG

Schneicw said:
Thanks for the quick response and the advice which I will be sure to remember. Any idea how long it's going to take to port multitouch to the NTG
Click to expand...
Click to collapse
It'll take about the amount of time for whoever brought multitouch to the Nook Simple Touch to download the source for NTG and then make the appropriate changes. That's if they even care.

Hi,
the kernel in the attachment should work for the NTG. I patched it a month ago and totally forgot to upload it .
Works also on the normal NST.
The zip file includes only the kernel, its not flashable by cwm, you have to push it manually to your boot partition and add the permissions in the xml-file.
Git-Repository: https://github.com/mali1/NST-kernel_115

Thank you. Is it possible to replace the uimage in the original CWM zip with this one and do the same thing as for the nst or should I follow the directions in the original thread which if I understand right involves burning noogie to an sdcard then then booting the nook up, connecting it to a computer, finding uimage and replacing it.

Schneicw said:
Thank you. Is it possible to replace the uimage in the original CWM zip with this one and do the same thing as for the nst
Click to expand...
Click to collapse
Yes, that should work.

Hello everybody!
I haму some questions about this: http://forum.xda-developers.com/showthread.php?p=24180134
Can I use this method if I had already NST [email protected] with root? I want get multitouch, NoRefresh and usb-host.
All what I should to do is just replace uImage through Noogie?

This particular thread is regarding Multitouch on the Nook Touch Glow, not the Nook Simple Touch.

mali100 said:
Hi,
the kernel in the attachment should work for the NTG. I patched it a month ago and totally forgot to upload it .
Works also on the normal NST.
The zip file includes only the kernel, its not flashable by cwm, you have to push it manually to your boot partition and add the permissions in the xml-file.
Git-Repository: https://github.com/mali1/NST-kernel_115
Click to expand...
Click to collapse
I've installed this kernel on my NTG and it works great. Thanks!

>>you have to push it manually to your boot partition and add the permissions in the xml-file
Using Root Explorer, where do I have to copy the (extracted kernel) file to (exact path/folder)?
Add permissions: Can I do that in Root Explorer rather than opening the xml file (filename?)? I do not have an editor for xml files....(which one would you recommend if I cannot change the permissions directly using Root Explorer)?
Thanks!

nrseife said:
>>you have to push it manually to your boot partition and add the permissions in the xml-file
Using Root Explorer, where do I have to copy the (extracted kernel) file to (exact path/folder)?
Add permissions: Can I do that in Root Explorer rather than opening the xml file (filename?)? I do not have an editor for xml files....(which one would you recommend if I cannot change the permissions directly using Root Explorer)?
Thanks!
Click to expand...
Click to collapse
Follow the instructions in the original multitouch thread http://forum.xda-developers.com/showthread.php?t=1563645

Glowlight not working
Hello,
I have a problem with my Nook Simple Touch Glowlight that I hoped you could help me with.
I rooted it and it was working fine. Then, I tried to add the multitouch mod, but I think it was for the NST, and now the glowlight doesn't work at all. I did not have a backup, unfortunately. I tried doing a factory reset and rerooting, but when it gets to the "try the glowlight" part of the setup. I can't go any further because the light doesn't work. How do I fix this problem?
Thanks,
Joe

Glow + multitouch + Norefresh?
After rooting my Glow I downloaded and installed the .zip I found in another thread to enable multi touch and an APK that was to enable NoRefresh. The norefresh didnt work at all and the multi touch worked but killed the glowlight. Now I understand what happened, but basically i ended up with the kernal for the NST that enabled Multitouch.
After downloading and ADB pushing the the kernal that has both Glow and MultiTouch I am satisfied but not completely happy. I would really want the addition of norefresh but I have not been able to find a kernal that has all three.
USB host would not be a bad thing to have also, as long as it doesn't hose the battery life. It isn't a required component for my needs.

I've been looking around to see who has been working on this.
As mentioned elsewhere, EpdController has been changed in 1.2 which will break anything designed to play with Epd modes.
I've no experience or real interest in "NoRefresh" since for what I want
it's better to integrate Epd control at the application level, which I do.

Oh, I should have mentioned. I am at 1.1.5. I used Glownooter because I wanted the Market access, utilizing the Search Market tool. As far as I could tell, the rooting methods that work on 1.2 don't include Market capability.
If I could update to 1.2 and keep market that would be cool. It might be that any dev work has been scrapped for 1.1.5 as that is an old version.

here is multitouch for nook glowlight, it is in zip format for installing with CWM, I made it changing the uimage file for the rigth one in the NST CWM zip file from the first post
I have tried it in my nook glow with firmware 1.2, spanish language, and previously rooted with glownooter, I had installed too the norefresh toggle previously, it works like a charm with opera browser, and of course light is working
I installed it after previously have done with the no glow version and having lost my light, so it works also as an amendment to this failure
View attachment multitouchNSTG.zip

elsita could you please tell if this kernel is compatibile with fw 1.21 on NSTG to enable multitouch and fast refresh on this device? thanks!

soolcio said:
elsita could you please tell if this kernel is compatibile with fw 1.21 on NSTG to enable multitouch and fast refresh on this device? thanks!
Click to expand...
Click to collapse
I can't tell for sure but I guess so, no refresh though is an app AFAIK
Enviado desde mi ZP800 usando Tapatalk 2

soolcio, will you share your attempt's results here, please, if any - a lot of people now have NSTG FW 1.2.1 and wanna have multitouch without loosing GlowLight feature working as usual

[Q] Rooting newer Nook version: how to know which software?

I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.

There are at least two methods that work with the Glowworm.
You should not use any method until after you have
- made a noogie disk
- booted from it
- backed up your device
- restored that backup to a test disk (a 2 gig or larger microSD card, for instance) and confirmed that the test results in a disk that has 8 partitions.
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore seems to be only getting one partition restored and blowing out the other partitions.
I don't know if the stuff that eded is working on has come to fruition yet - he was looking at building a tool that could detect whether it was run on an NST or NSTG and root appropriately to the device.
The two routes I know work are:
- glownooter, the nooter project tool, includes Google apps and market support
- tinynoot, pasted together from various tools, gives you minimal root without google apps and with amazon appstore. Will work with either NST or NSTG because it's approach is so minimalist.

Thanks, roustabout! I will be sure to test the backups before I install anything else, then. Good to know!
In any case, what I am most concerned about is getting the right version of the rooting software for my device. I see that Nook devices have different firmware and that certain tools only work with certain firmware versions. I see no mention of my firmware version in any tools' websites, hence my apprehension.

hence the value of a backup
I saw your request on that and I think one of the issues here is that so many folks use Windows exclusively, and the backup process is so easy on linux that trying to tell people how to do it in Windows is like jabbing yourself in the eye with a stick, given that linux is free, vmware player is free, and linux can be installed and used for this job entirely in vmware player. On the other side of the coin, if you know nothing of linux, even using dd correctly will be a challenge since there's a pretty steep learning curve behind setting up a new OS successfully just to be able to get backups off an 80-130 dollar device.
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'

I didn't mention it, but I also use Linux at home (Kubuntu, like Ubuntu but with a better UI). So many people are now using Ubuntu that I find it surprising that the instructions even bother mentioning the OSes for which the operation is as difficult as you say. I remember when doing things in Linux was hard and Windows was easy, and at that time Linux was hardly ever mentioned!
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'
Click to expand...
Click to collapse
I did not realize that the 1.1.5 release is glowlight-only. Great, thanks, I'm on to hacking this thing!

ok, so for you the backup process is:
- make the noogie disk
- put it into your device
- power cycle your device
- when it boots to "rooted forever," connect the USB cable to your linux box
- once the linux box mounts the NSTG as storage, pay attention to which device it is mounting it at. Assuming it's sdX:
- backup with dd if=/dev/sdX of=backup.img bs=1M
When that's done, disconnect your NSTG, throw media of some sort, larger than 2G, onto your box and test your restore with
dd if=backup.img of=/dev/sdY bs=1M
Once that's done, do an
fdisk /dev/sdY
and a
p to print the partition table.
You should have 8 partitions (and your backup.img file should be just under 2 gig.)
Hack away; if you ever need to restore, you can just drop the virgin image back on.
I take a snapshot like this of my device every so often since remembering how I got to whatever config I liked is harder than just backing it up.

Thanks for the backup instructions, the idea of testing it on a DVD-ROM looks to save quite a bit of trouble with the actual device..
I rooted with this terrific guide:
http://forum.xda-developers.com/showthread.php?t=1675706
The process was simple. I do have an issue where I need to install a Hebrew font but ES File Manager doesn't seem to see the root folders. I'm having a hard time googling my way out of this one, bu all the other little issues were fairly simple.
One issue that I will mention that was hard to solve was the inability to perform searches in the Market. This page helped me resolve that issue:
blog.the-ebook-reader . com/2011/07/15/rooted-nook-touch-fixing-market-search-and-other-tips-and-tricks-video/

I just figured out that the file manager has to have Root permissions enabled. I've enabled it and added some fonts to /system/fonts but I still cannot get Hebrew text to display on this device. All I get are the typical rectangles instead of characters. Any ideas about how to proceed?
Thanks.

Restore Nook 1.1.2
roustabout said:
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore .
Click to expand...
Click to collapse
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)

bubblewrapper said:
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
Click to expand...
Click to collapse
Few people who will be knowledgeable will find your post buried here under this thread. i suggest that you simply start a new thread with a good descriptive title so that the gurus will find it.

Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.

roustabout said:
Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.
Click to expand...
Click to collapse
Actually, I think that I just need the fonts (or at least that would be a great first step). I put fonts with Hebrew glyphs in /system/fonts (using ES File Explorer in Root mode) but even after a restart it does not find the fonts (i.e. Hebrew text still shows as rectangles). I will fight with it some more in the coming days, if I don't succeed I will start a new, concise thread on the topic. There are plenty of Google posts on the subject, but all of the ones that I have seen (not Nook-specific) suggest that dropping the fonts is /system/fonts should be enough. Perhaps it is a permissions issue, I'll see if I can SSH into the device to see permissions.

dotancohen said:
I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.
Click to expand...
Click to collapse
Sorry that I am so slow to respond, but I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/

ladykayaker said:
Sorry that I am so slow to respond,
Click to expand...
Click to collapse
Thank you! You don't need to apologize for taking time to respond, you are under no obligation! But I very much do appreciate your assistance and am happy to wait patiently! You will notice that I usually google issues first to try to save us both the time!
I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Click to expand...
Click to collapse
Thank you. It seems that those posts are Windows-centric summerizations of information found here at XDA-developers. The root is pretty much the process that I used, but from the guide right here which has Linux directions as well.
By the way, the-ebook-reader site is often not responding for me. Is it just for me, or does everyone have trouble with that site?
Thanks!

version 1.2.0
UK glowlight ships with 1.2.0. Use tinynooter to root this. You may have issues installing apps atm though but you will get the browser at least.
http://forum.xda-developers.com/showthread.php?t=1961835

Thanks, Loney. In fact, I got this Glowlight in the US, and it reports that it has software verion 1.1.5. But the information will be good for others who might google this thread!

UK Nook Glowlight software 1.2.0 - Don't use glownooter

I got a uk glow worm on the 27th (2 days before release ) and one of the first things that I tried to do was to root with glownooter. Bad idea! I thought that I had bricked my device. I had to use a lot of trickery to recover from a loading screen lock-up and once I did the first thing that I did was backup my nook (Which i should have done before).
UPDATE!
Please try my new ROOT install pack HERE:
http://forum.xda-developers.com/showthread.php?p=34216660#post34216660
This can be used to root and install the most requested things of this thread in just one zip.
Here is a quick guide to most things you will need to do to get started. I will update this guide as I discover and build new modifications.
To Backup and Restore
Follow this guide. Please do this BEFORE any other tinkering!
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Its important to check your backup before proceeding! Please listen to roustabout and dont skip this step... He knows what he's talking about
roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks roustabout
To Root!
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994 (Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593 (Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
To Add Apps
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Setup ADB over USB
OK I have taken the liberty of building a quick driver mod to support your nook through USB. It works for me. First you need to have the android SDK if you don't already (sure you do but just in case ).
http://developer.android.com/sdk/index.html
Make sure you tick to install the android USB driver when the SDK is installed.
Browse to extras\google\usb_driver in your SDK folder (wherever you put it) and replace android_winusb.inf with my file:
http://dl.dropbox.com/u/13673492/android_winusb.inf
Next go to C:\Users\your_user_account\.android and replace adb_usb.ini with my file:
http://dl.dropbox.com/u/13673492/adb_usb.ini
In device manager, point google ADB driver to this and hopefully that should get you set up!
To test type
Code:
adb devices
Its working if you get something like this:
Code:
* daemon not running. starting it now on port ____ *
* daemon started successfully *
List of devices attached
[YOUR NOOK] device
And then try
Code:
adb install app_of_your_choice.apk
UPDATE
Install Multitouch Kernel With Overclocking
Install the CWM zip using your clockworkmod SD card
http://forum.xda-developers.com/showthread.php?t=1906507
:good: Thanks to johnjtaylor for discovering that this kernel works works.
Hopefully this more comprehensive guide will get others with this software to start playing around.
If this helps, be polite and say thankyou

Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.

David0226 said:
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
Click to expand...
Click to collapse
Thanks for replying. I'm actually working setting up ADB now. As for books I only just got my nook so all of my titles are epub format on an sd card so i wouldn't think it would be that. As soon as I get ADB set up I will post back my results incase it helps anyone else with this new software version.

Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.

I set up ADB.
Plenty of space in all partitions including /data for the apps that I want. Managed to install through "adb install some_app_i_want.apk" so problem resides with the amazon app store. Not really an issue for me because I have a specific set of apps that I want and don't need to browse the app store.
I will try to work out what's wrong for others.

staylo said:
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
Click to expand...
Click to collapse
Thanks. I'm looking for it now

No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?

loney01843 said:
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
Click to expand...
Click to collapse
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)

staylo said:
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
Click to expand...
Click to collapse
You're obviously not that lazy. Thanks for looking and gathering all of the extra info I need. I'll send B&N an e-mail and see what they say. I wouldn't be surprised if they didn't want to hand it out considering you can use it for an easy root setup and install the amazon and kobo stores which could financially damage their advance into new territories! What are we to do! Can't even subscribe to a newspaper or magazine through the nook store yet!
I'll let you know when / if I get a response

There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.

roustabout said:
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
Click to expand...
Click to collapse
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!

UK tinynoot attempt failing
loney01843 said:
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
Click to expand...
Click to collapse
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?

smerrett said:
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
Click to expand...
Click to collapse
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!

loney01843 said:
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
Click to expand...
Click to collapse
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?

smerrett said:
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
Click to expand...
Click to collapse
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.

loney01843 said:
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
Click to expand...
Click to collapse
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.

smerrett said:
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/13673492/n2T-Recovery_0.2.img
This is the file needed to force factory reset. However a quality backup like you have is far more important.
For anyone who wants to give this a go, here is a quick guide for root access and app installs using windows tools until I can make something more complete:
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994
(Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593
(Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.

loney01843 said:
If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
Click to expand...
Click to collapse
Great - thanks to your more detailed instructions, I have persevered and the second attempt at installing the tinynoot zips worked. Your post gave me the confidence to try installing apks for the first time and for anyone else who is unfamiliar with the processes used, I found these two pages useful for:
navigating within a command prompt (how naive): pcstats.com/articleview.cfm?articleid=1723&page=3
Pasting text into a command prompt (ditto): megaleecher.net/Copy_Paste_Text_Dos_Window
Sorry, as a newb I'm not trusted to post outside links yet. It took a couple of attempts of pasting and pressing enter to work out how to install using the adb code but it's not as hard as I expected.
I have tried installing the 1 Mobile Market which works but it is unable to install apps itself (not enough space).
Also, I have just installed NoRefreshToggle and can't seem to get it to work. Any thoughts - is 1.2 to blame? Really want this to work as Business Calendar Free is just a series of blinks at the moment!

Great! I'm glad you pushed onward and have root.
I am going through possibilities of other ways to install apps and mods.
No refresh is something that I would like as well but I think that the framework may need editing for 1.2.0. For fast mode a new kernel will need to be made or existing one modified.
Be aware that installing kernels not designed for this firmware can give you some serious problems.
Once I can setup app markets, I will work on these other modifications.
Stay tuned :good:

Take a look at the overclock kernel - it's got a lot of the norefresh features baked in, and gives you a nice ability to control both clock and kernel tuning (via the governor control.)
You're right, you can flash the two zips back to back with no ill effect, I was mistaken about what the second zip was doing.
I mistyped when I typed "nook touch tools," I meant nook color tools.
I'm very interested that the amazon store is not working in 1.2. I will see if the software's available for my device, so I can try to see what's happened.
As of now, the us bn site does not mention an os 1.2 for the glowlight.

My setup with Ubuntu and a custom permissive Kernel

Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/

Thank you for this!
Sent from my SM-P900 using Tapatalk

trying to build kernel
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:

dodo99x said:
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:
Click to expand...
Click to collapse
It looks like you're in Windows. To my knowledge it is not possible to compile a Linux kernel in windows. I would recommend downloading virtual box and installing some Linux distro in there. This is what I was talking about in the "environment" section at the top of the article.
For android development I find that you need access to a lot of tools where some are only available on Windows and others are only available on Linux so a Windows PC with a Linux VM is ideal in my opinion.

Oh ok, no problem. I just misread the guide. I've setup a build environment in a vm before to compile aosp for my Nexus 10. Shouldn't be too hard to do it again. I recently rebuilt my pc so the vm I had got nuked.
Sent from my SM-P900 using Tapatalk

ok I got my Ubuntu VM up and running using this guide
http://forum.xda-developers.com/showpost.php?p=50748836&postcount=25
installed android NDK to ~android/NDK, and unzipped the kernel source to ~android/kernel
followed your guide to build a SELinux permissive kernel but i'm getting some errors when trying to compile. here's the output:
http://pastebin.com/Npdu7J5h
EDIT: retried doing the EXPORT command and now it seems to be compiling

dodo99x said:
EDIT: retried doing the EXPORT command and now it seems to be compiling
Click to expand...
Click to collapse
When you export a variable in the terminal it only exists for that one session, so if you open a new terminal instance you need to run the command again. If you want to set it permanently normally you can just put the export command into ~/.bashrc

Oh I see. I'll give that a try. I was able to create a new boot.img following the rest of your guide. I have yet to try flashing it though. Will have to find some info about all the kernel options that can be set. Hopefully be able to integrate HMP to get all eight cores running at the same time.
Sent from my SM-P900 using Tapatalk

Cool, let us know how that goes. I wonder how much it would affect battery life.

Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/
Click to expand...
Click to collapse
I tried to install this using VBox Odin and I couldnt get it to work. Tried using BOOTLOADER and also PDA. Not sure the correct one but neither worked for me. Also, Moblie ODin hasnt yet worked but when it does, things will be much easier for me at least.
I have a newly rooted SM-900. I will have to find time someday to compile the kernel against what I have. Must be a slightly newer version than the one you posted. That is only thing I can think since I just got my 12.2. Thanks for the detailed info.

Camera?
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?

aarstar said:
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?
Click to expand...
Click to collapse
The camera fails for me too. I dumped a logcat and isolated the issue here:
W/ActivityManager( 2746): Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
V/ApplicationPolicy( 2746): isApplicationStateBlocked userId 0 pkgname com.google.android.GoogleCamera
But... the camera is not a huge deal. It did, however, break wifi. I did not get a logcat of that yet, but I would assume it is also a permission issue.

Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.

aarstar said:
Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.
Click to expand...
Click to collapse
Wow, I totally missed that entire line in the OP... You literally just made my whole day. I fought this all day long, desperate to get ubuntu working. Thank you for pointing that out.

I get "xt_mark.h" is missing (no such file or directory) error. Any idea why that may be?
I'm using the source for p900 international hoping that I may sidestep the camera issue that way (by enabling permissive to the international kernel I mean), but as it stands it does not compile.
I've googled it but until now it was/is to no avail...

Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play).
Click to expand...
Click to collapse
Hey Graeme H,
we both have the same intention. I am downloading the international Kernel at the moment and will compile it again for you guys. The download takes a little longer as I am at vacations.
I am going this route: doviak.net/debian-kit/debian-kit_p00.html . In the future I would like to have arch linux running on this device but a customized debian would be okay for the beginning, too.
Eventually I will try to use framebuffer instead of vnc or something like that. I would love to use sublime-text and dwm on that device with that resolution
Good luck guys. I will try to update.
Edit: hehe I have dwm in front of me now and the resolution is so high that I am barely able to read
Compiled the kernel and flashed in on my device but my camera is still not working. Maybe we need to edit the config:
# Camera sensor devices
#
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_TCM825X is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
CONFIG_VIDEO_S5K6B2=y
# CONFIG_S5K6B2_CSI_C is not set
CONFIG_S5K6B2_CSI_D=y
CONFIG_S5K6B2_POSITION_FRONT=y
# CONFIG_S5K6B2_POSITION_REAR is not set
CONFIG_VISION_MODE=y
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_S5K6AA is not set
Click to expand...
Click to collapse

Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank

PHP:
smylion said:
Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank
Click to expand...
Click to collapse
Compiled from Kitkat source. [ur#l]erhan.es/upload/sm-p900-permissive-intl.tar[/url] (odin)

Thank you but the link does not work

smylion said:
Thank you but the link does not work
Click to expand...
Click to collapse
Sorry, it is erhan.es/upload/sm-p900-intl-permissive.tar