If this is the wrong thread I'm sorry and mods please move it.
My nook is currently rooted...
I have tried all the 3rd party e-readers different launchers.
I'm really over the idea of being rooted with the exception of "Current book cover screensaver + custom shutdown image" hack and possibly resizing my partitions.
Is it possible to replace the Uramdisk with one that had adb enabled and then just manually push over the modded files?
or am i going to need to install busybox, su, and superuser.apk?
I would like to keep it as close to original firmware as possible...
Can anyone shed some light on this?
Ok so i'm guessing busybox is required to be able to run the Current Book Cover Screensaver.
1st i turned on adb wireless.. installed the files per the instructions over ADB
rebooted and I was stuck in a boot loop
2nd restored to a fresh firmware.
Installed adb wireless, superuser, su, and busybox.
Then installed the files per the instructions over ADB
rebooted and everything works great.
Now i just wonder if i can uninstall Superuser or busybox...
persichini said:
Ok so i'm guessing busybox is required to be able to run the Current Book Cover Screensaver.
1st i turned on adb wireless.. installed the files per the instructions over ADB
rebooted and I was stuck in a boot loop
2nd restored to a fresh firmware.
Installed adb wireless, superuser, su, and busybox.
Then installed the files per the instructions over ADB
rebooted and everything works great.
Now i just wonder if i can uninstall Superuser or busybox...
Click to expand...
Click to collapse
hi,
while i'm not totally sure, i suppose you can definitely uninstall both superuser and busybox.
In any case, the modified ramdisk with ADB enabled (either WiFi or USB) is enough to allow you to push/pull files to Nook, and to open a shell (as root).
Busybox is just convenient if you plan to use shell sessions since it includes commands like cp to copy files, and others, but you can live without it (using ADB push to copy files, or using command dd, for instance).
Superuser, if you refer to android application (APK) it's just used by all other applications requiring root privileges (like RootExplorer, for instance), but if you don't plan to use them, then it's not needed.
In any case, you have practically my same configuration (as close as possible as stock firmware): after all, i use Nook just to read books, so don't need custom launcher and google apps! I would just mention XorZone modification that is really useful for me, since it's can act as a sort of launcher, and can deal with useful features like button remapping. The only other application i have installed is this PDF reader, since the stock one is really poor, while this one has a better zoom management, and also has specific features for e-ink devices and expecially for the Nook (like partial refresh).
Of course, to install the applications, i just use ADB.
traycold said:
In any case, you have practically my same configuration (as close as possible as stock firmware): after all, i use Nook just to read books, so don't need custom launcher and google apps!
Of course, to install the applications, i just use ADB.
Click to expand...
Click to collapse
Ok so something must have gone wrong when I installed your screen saver mod if i was stuck in a boot loop. Because I assuming you have it installed on yours with out superuser, and busybox... i just i can just install them now and then it should still work.
I also just use the nook to read EPUB book, i have a very nice android tablet that i use for anything and everything else. I would much rather have a high battery life on the nook then bells and whistles i don't ever use.
If you're running linux or have access to a linux box, you could just grab noogie and it should show all partitions. With this you could make the changes without ever having to touch the uRamdisk or ADB or needlessly installing anything to actually root the device.
As it is if you were to try this your way you'd have to first root it using like Minimal Nooter or TouchNooter then remove everything you don't want afterwards (su/superuser/busybox/gapps/etc).
Personally what I did was I installed touchnooter and because I like my devices to appear stock I left all the buttons unmodified while leaving a very faint button savior icon on one side that'll allow me access to android launcher the app drawer etc. This way I can use it like a proper android device without having it appear as anything more than a basic reader.
GabrialDestruir said:
If you're running linux or have access to a linux box, you could just grab noogie and it should show all partitions. With this you could make the changes without ever having to touch the uRamdisk or ADB or needlessly installing anything to actually root the device.
As it is if you were to try this your way you'd have to first root it using like Minimal Nooter or TouchNooter then remove everything you don't want afterwards (su/superuser/busybox/gapps/etc).
Personally what I did was I installed touchnooter and because I like my devices to appear stock I left all the buttons unmodified while leaving a very faint button savior icon on one side that'll allow me access to android launcher the app drawer etc. This way I can use it like a proper android device without having it appear as anything more than a basic reader.
Click to expand...
Click to collapse
Hmm interesting...
What i did was i restored to stock... so my nook was completely unrooted...
Switched the uRamdisk using noogie then ADB the following files over and set the permission...
android.policy.jar [needed only for "current book cover screensaver"];
services.jar [needed only for "current book cover screensaver"];
Settings.apk [needed only for "current book cover screensaver"];
framework.jar [needed only for "custom shutdown image"];
What your saying is just use noogie and linux to replace the files and set the permissions.
I plan on Dual Booting my G-Tablet with linux so i can resize the partitions on the nook, I'm going to try your suggestion and see how it goes..
so i saw Terminal IDE, apparently a great programming environment, and was wondering if anybody has installed it on the kindle fire, and if so, how'd it go?
the reason i ask (and an comcerned about it) is because it mentions that it completely reinstalls the ~/system folder, and i don't know if doing that on the kindle would mess anything up or if that has all been accounted for or what?
i would really like to be able to use it but i want to make sure installing it won't brick my kindle or anything.
Are you talking about
https://market.android.com/details?id=com.spartacusrex.spartacuside
If so, I don't see anything about it talking about making changes to /system and it states that it AND the whole app runs WITHOUT needing ROOT permissions which means it would not have permission to do so anyway.
krelvinaz said:
Are you talking about
xhttps://market.android.com/details?id=com.spartacusrex.spartacuside
If so, I don't see anything about it talking about making changes to /system and it states that it AND the whole app runs WITHOUT needing ROOT permissions which means it would not have permission to do so anyway.
Click to expand...
Click to collapse
yeah, that app. when you download and install it (before you actually install the IDE from inside it), you then go to install the IDE, it says "The ~/system folder will be DELETED and re-written. you should not be storing your work there." or is this talking about somewhere else?
~/system
Is a relative address and not the same as /system
I would assume it is talking about its own directory structure.
I went ahead and installed this. Great app, doesn't mess with the actual /system. Krelvinaz is correct.
Sent from my Kindle Fire using XDA Premium.
awesome! thanks guys!
did the keyboard work for you guys?
Could you install a debian squeeze via this app?
I'm looking for a full copy of Cyanoboot for the HD+. I know that there is a copy installed with CM 10.1 SD card installs, which works fine for me, however I would like to be able to have the full menu, fastboot, ect.
Thread for the Nook Color
http://forum.xda-developers.com/showthread.php?t=1522226
If I can find this, I plan to port Arch, and Debian Linux to this device, without android. I already have a chroot with full framebuffer access, but I think that this would be the next logical step. It runs really well.
Also, as a quick side question, has anyone gotten USB host mode to work? I haven't been able to try (female to female USB cable needed, same as the nook color)
EDIT:
https://github.com/NookieDevs/u-boot-hummingbird-ovation
I'm willing to compile from source, but I'm having trouble with finding what type of CPU is in this. I know it's a Dual core, 1500 MHz, ARM Cortex-A9, but I don't know what CPU in that lost would equate to.
kdb424 said:
I'm looking for a full copy of Cyanoboot for the HD+. I know that there is a copy installed with CM 10.1 SD card installs, which works fine for me, however I would like to be able to have the full menu, fastboot, ect.
Thread for the Nook Color
http://forum.xda-developers.com/showthread.php?t=1522226
If I can find this, I plan to port Arch, and Debian Linux to this device, without android. I already have a chroot with full framebuffer access, but I think that this would be the next logical step. It runs really well.
Click to expand...
Click to collapse
There is not a prebuilt cyanoboot (u-boot.bin) for the HD+. There is a github here. This is what verygreen built his with, and in his it is named uImage in his boot partition. It is also known as the second bootloader which is what breaks the lock from B&N.
He has not included the normal menu items because he could not get the volume up/down keys to work. Bokbokan on the HD overcame that by using just the n key to manipulate the cursor by a series of n pushes. So the HD has a boot menu. You can see his source posted on his CM10 thread. He does not have a github set up but the source is there so you can look how he set up the menu for HD.
Any chance that you know what CPU type (from the list that uboot has to offer) that the nook HD+ has in it? I have the source, and I'm ready to compile, but not sure which one it is. Once I'm past the bootloader issue, I should have no trouble setting up linux on this device.
kdb424 said:
Any chance that you know what CPU type (from the list that uboot has to offer) that the nook HD+ has in it? I have the source, and I'm ready to compile, but not sure which one it is. Once I'm past the bootloader issue, I should have no trouble setting up linux on this device.
Click to expand...
Click to collapse
Be sure to use the one from fattire, not the nookiedevs. It is an omap4.
EDIT: I added some commands I got from bokbokan some time back. See attached zip
EDIT 2: I removed the attchment and just going to post the commands here
export ARCH=arm
export CROSS_COMPILE=arm-none-linux-gnueabi-
export PATH=<location where u-boot source is extracted>/tools:$PATH
cd <location where u-boot source is extracted>
make distclean
make bn_ovation_config
make
This will compile the original source from verygreen initial u-boot source.
mkimage -A arm -O linux -T kernel -C none -a 0x83000000 -e 0x83000000 -n "2nd Bootloader" -d u-boot.bin uImage
Click to expand...
Click to collapse
Having trouble getting it to find OMAP4, but I'll continue looking into it after work. There's a compiled uImage, I'll try that also. I don't need to change the source really, so if it's compiled, I should be able to skip that step. Wish me luck.
seems that my cross compile environment is currently broken, and it looks like the uboot images for the HD won't work on the HD+. That'll stall my development until I can either fix it, or if someone else can compile and send it to me.
Booting to a black screen after compiling as per your instructions. Replaced u-boot.bin and uImage. Any ideas?
kdb424 said:
Booting to a black screen after compiling as per your instructions. Replaced u-boot.bin and uImage. Any ideas?
Click to expand...
Click to collapse
U-boot.bin is stock and should remain the same as before. Only uImage gets added to the boot partition so that it can be the second bootloader loaded by the stock u-boot.bin. Like you said, you can just copy verygreen's uImage and it should boot. You can get it from his image zips on his thread. The HD and HD+ uImage files are not compatible with each other.
Sent from my Nook HD+ running CM10.1 on emmc.
Grabbed the source from Bokbokan's thread for uboot, got compile to work as per your instructions, replaced uImage with my newly compiled uImage, and it just boots the EMMC without even acting like there is an SD card in there. It was booting the old uImage (I started with the CM10.1 SD card install and made sure that booted)
kdb424 said:
Grabbed the source from Bokbokan's thread for uboot, got compile to work as per your instructions, replaced uImage with my newly compiled uImage, and it just boots the EMMC without even acting like there is an SD card in there. It was booting the old uImage (I started with the CM10.1 SD card install and made sure that booted)
Click to expand...
Click to collapse
You should be using the source from the fattire github, not bokbokan's source if you want HD+.
Sent from my Nook HD+ running CM10.1 on emmc.
Whoops. That explains it. I misread. I'll check back in here once I get that done.
leapinlar said:
You should be using the source from the fattire github, not bokbokan's source if you want HD+.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I got an error with the fattire source, but not the other sources, so I know my env is set up correctly.
{standard input}:265: Error: selected processor does not support ARM mode smc #0 Ideas?
EDIT:
Could be this. Looking into it.
http://forum.xda-developers.com/showpost.php?p=21393475&postcount=424
EDIT2: This is "wrong" but compiles. Testing
http://ding34.blogspot.com/2013/05/error-selected-processor-does-not.html
EDIT3: Still bypassing the SDcard. With the original uImage, it boots my SD, but with my new uImage from fattire source, it skips it.
kdb424 said:
I got an error with the fattire source, but not the other sources, so I know my env is set up correctly.
{standard input}:265: Error: selected processor does not support ARM mode smc #0 Ideas?
EDIT:
Could be this. Looking into it.
http://forum.xda-developers.com/showpost.php?p=21393475&postcount=424
EDIT2: This is "wrong" but compiles. Testing
http://ding34.blogspot.com/2013/05/error-selected-processor-does-not.html
EDIT3: Still bypassing the SDcard. With the original uImage, it boots my SD, but with my new uImage from fattire source, it skips it.
Click to expand...
Click to collapse
I got that error and it had to do with version of the toolchain. I had to downgrade to an earlier codesourcery, I think.
Sent from my Nook HD+ running CM10.1 on emmc.
It compiled just fine. If you want the fixed source (well, by fixed, I mean more compatible) let me know. It doesn't boot as far as I can tell, but I may just be oblivious to something.
kdb424 said:
It compiled just fine. If you want the fixed source (well, by fixed, I mean more compatible) let me know. It doesn't boot as far as I can tell, but I may just be oblivious to something.
Click to expand...
Click to collapse
Oh, you used the wrong branch in fattire. You need to do the second loader branch, not the master.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Oh, you used the wrong branch in fattire. You need to do the second loader branch, not the master.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Well, your were right, I cloned the master the first time. This time, I had the same errors, which that fixed also worked, but this time, I sit at a black screen. No fastboot, no anything. Just hangs.
kdb424 said:
Well, your were right, I cloned the master the first time. This time, I had the same errors, which that fixed also worked, but this time, I sit at a black screen. No fastboot, no anything. Just hangs.
Click to expand...
Click to collapse
Well, I know I was able to build it and made a change so that you hold the n key and it booted to stock instead of the hybrid. So you must have something wrong in your setup.
Sent from my Nook HD+ running CM10.1 on emmc.
Isn't there supposed to be a menu or something? I though there was a screen telling you what options you had. I mainly need fastboot access. I mean, I can do it with recovery, butI know fastboot a lot better.
kdb424 said:
Isn't there supposed to be a menu or something? I though there was a screen telling you what options you had. I mainly need fastboot access. I mean, I can do it with recovery, butI know fastboot a lot better.
Click to expand...
Click to collapse
That is why I pointed you to bokbokan's source for the hummingbird. He has an example in his of the menu. I think it is menu.c, but remember the hardware is different for the hummingbird so his will not work on the ovation. Also, I thought fastboot was only for partitions that were in fastboot format. The SD install is all MTD partitions.
Sent from my Nook HD+ running CM10.1 on emmc.
Got ya. I'll get on that. I was under the impression that one could simply be reconfigured. I'll look into the code when I finally get a day off. Thank you for all of your help.
Hi,
I have rooted my nook touch and I am trying to install an ssh server on it. I found a document on github (I can't post links but if you google "github dropbear sft android" you should see it) which describes how to cross compile dropbear ssh on debian for Android.
But when I start the cross compiled dropbear on the Nook it tells me :
FATAL: kernel too old
[1] Segmentation fault ./dropbearmulti
What does this mean or has anyone managed to get an ssh server running without some sort of UI thingy like sshdroid?
Thanks,
Ralph.
Ok, I found out the libc I am using for cross compiling (from emdebian) is compiled for Linux kernel 2.6.32 while the nook is using Linux 2.6.18. That is why my cross compiled dropbear does not work.
Any ideas on an easy way of getting a dropbear executable for the Nook without recompiling everything?
NookManager has dropbear in its uRamdisk. You could extract it from there.
straygecko said:
NookManager has dropbear in its uRamdisk. You could extract it from there.
Click to expand...
Click to collapse
Ah, great idea. I tried to run it but it does not work (it says 'not found')
I even installed all the shared libraries dropbear requires from the uRamdisk to the nook but that did not help either...
I found an easier way:
On the nookdevs.com wiki there is a page called DropNook and it contains a compiled version of dropbear for the Classic. After some tinkering it also works for the Nook Touch.