Related
I know many of us are new to the whole rooting thing. I'm coming from the Windows Mobile world of custom ROMs, kitchens, etc., but I do have some linux experience. However, I can't for the life of me figure out how to do a lot of what comes "standard" in MoDaCo's ROM. Obviously it would be easier to simply install Paul's ROM and be done with it, but I'd really like to learn how to do it on my own too.
So, that being said, maybe we can pull together some tutorials, guides, and/or links to existing guides which explain how to go about setting up our Rooted phones manually. Here are some of the built-in mods the MoDaCo ROM comes with which would be nice to be able to do manually or on a one-off basis:
Included in MoDaCo 1.1 'core':
Rooted with 'adb remount' permission and superuser APK
A2SD included (fully automatic thanks cyanogen!) create a EXT2 partition as your second partition to use. dalvik-cache remains on device.
Added Jbed Java
Added Dropbear SSH running by default, check 'About' screen for password (port 2222). You can now remove this by running /system/bin/removedropbear.sh
Added Notes app from Dragon
Added Spare Parts (run it and switch the 2 animation types to 'fast' for an even better experience!)
Added android-wifi-tether 1.60 pre3 (props to the developer, this is a great app!)
Added WiFi Status indicator, with kind permission of Andrew Schwimmer
Added busybox 1.15.2 tweaked such that 'get information' in Swapper now works as desired
Added nano 2.09 text editor for use in shell mode
Added parted and sqlite tools
Added terminfo and settings to boot.img to allow nano etc. use
Added files required for Debian linux including loxley's updated bootdeb script
Moved Quickoffice to data partition to allow easy uninstall
Moved Google Maps and Google Voice Search to data partition to allow easy update
Silenced boot sound (it's still there and can be reactivated with a file edit)
Click to expand...
Click to collapse
*********
*********
!Working!
Wireless Tethering:
http://android-wifi-tether.googlecode.com/
Go to the "Downloads" tab and download version 1.61-pre
!Not Working!
Superuser Whitelist App
I found two threads here that describe how to install Superuser.apk.
http://forum.xda-developers.com/showthread.php?t=582140
http://forum.xda-developers.com/showpost.php?p=4897587&postcount=5
Using the first one, I was able to get the files onto the phone and I used the chmod commands found in the second file in the hopes this would work; however, whenever I try to use it, nothing happens. The ES File Explorer, in particular, used to work with MoDaCo. When I'd try to browse as root, Superuser would pop-up and ask if I wanted to grant the app permissions. Now it just hangs there (black screen) and ES File Explorer says I don't have root access. Other Root apps work fine though, it's just they don't seem to be dependant on Superuser Whitelist.
'adb remount' permission
This requires that the default.prop file be edited from ro.secure=1 to ro.secure=0. Unfortunately, I can't seem to get this file to stick. If I use the mv command using adb shell, I get some kind of permissions error. If I use the cp command when booting into the recovery menu and using adb shell, the file reverts to the original on boot. Or maybe it's simply not being overwritten, but not throwing any errors either
I think I may have found a thread that will help with the default.prop changes. Looks like this has to be done in the recovery.img which apparently overwrites any modifications in the root of the device on each reboot. I'll post an update if/when I figure it out.
HOWTO: Unpack, Edit, and Repack Boot Images
http://forum.xda-developers.com/showthread.php?t=443994
The adb remount permission issue is driving me crazy. Please keep us updated if you figure out a way of resetting that without installing a new ROM.
I ended up modifying one of the MoDaCo update scripts to set up ADB Remount, Superuser.apk, and Busybox. It's been working fine for me, but be sure to do a backup before you apply the update. Check it out here:
http://forum.xda-developers.com/showthread.php?t=593952
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..
As noob I needed long time to reach my main rooting objectives which was to run Cifs in my SG3 in order to
(i) access network shares AND
(ii) create symbolic links to these network shares located on my Synology NAS
This is now working and i wanna share my experiences with people who needs step-by-step guide
My objective was to be able to use a music player app (i.e. PowerAMP), while the music are located in my NAS (not in the phone or any external card)
I first began applying the hints of viulian in this thread . It did not work because my firmware (see below) is not supported.
My last successful try included the following steps:
- Re-flash stock ROM/Kernel
- Install CF-Root (includes SuperSU, ClockWorkMod Recovery, CWM Manager)
- Download/Install SuperSU Pro
- Check root in ES file Explorer (seemed to be OK)
- Create BackUp using CWM (into extSdCard)
- Run TriangleAway (to reset flash counter)
- Restore BackUp (to reset device status to normal)
- Install app Mobile ODIN Pro
- Download & flash SiyahKernel (incl. adbd insecure & Cifs Module) using Mobile ODIN Pro. Now I can see cifs.ko under /lib/modules/
- Install CifsManager
- Install BusyBox using app BusyBox Pro (i don't know if this step was really necessary for my purpose ?)
Furthermore i create a new share entry in CifsManager with these details
- Share path = 192.168.178.20/music
- Mount Point = /mnt/extSdCard/music/cifs
- User name = xxxxxx
- Password = yyyyyy
Hint: the default folder in CifsManager setting for the cifs.ko location is /system/lib/modules/ . You must change this to /lib/modules/. This is the folder used by Siyah kernel installation
Now i could mount the shares via CifsManager. Then i got a green point above right. A click on the mount entry will open folder /mnt/cifs/music in ES file explorer. From now on even the SG3 standard file explorer will show you the NAS music files under the folder /mnt/extSdCard/music/cifs.
Some info about my SG3
- Baseband Version: I9300XXLF5
- Bild Number: IMM76D.I9300XXALF06
- Kernel Version: 3.0.36.Siyah-s3-v1.3.8a
Good luck trying !!!!
bass.n said:
As noob I needed long time to reach my main rooting objectives which was to run Cifs in my SG3 in order to
(i) access network shares AND
(ii) create symbolic links to these network shares located on my Synology NAS
....
Click to expand...
Click to collapse
Does this still work for you? I just got a new tablet, and can't get Poweramp to see anything but the onboard flash. Arg, wish they'd left the library requester alone!
THIS METHOD IS NO LONGER WORKS as of update version 2.0.5 and higher.
Please visit this thread instead for the current rooting method.
Posting in this thread will get you nowhere, let it RIP.
ANNOUNCEMENT:
If you have a new Nook HD/HD+ and want to root and get the GAPPS running, you should follow the guide at the All-in-One thread instead. That said, I won't copy all the information here to there, so you should continue to read on.
Let me start by saying that I didn't come up with the working root method. The original root instruction came from verygreen in this thread. And I am not a developer, I merely have a few linux background and even less so in the Android. I worked on this on my spare time by myself.
I merely take what was working, but unusable to make it usable. I found something that he is missed. This may actually be working on Nook HD (non-plus) also, but since I don't own one I can't say that it will.
Disclaimer:
If something gone wrong, it's all your fault. I take ZERO responsibility for what happen to your device, your life, your wife/husband, your kids, your unborn child and etc. You get the idea.
Background:
When I found out the root doesn't actually work past a reboot, I start looking what actually cause the Nook to be pissed and factory reset itself. Well, it seem that the /system and anything in there is basically coming from a /dev/block/mmcblk0p8 And if something got change, Nook get pissed and do a FULL FACTORY RESET(I'll explain in a moment). Well, at least I start investigated under that idea.
What I found:
What I found, or at least what I think I found is that, probably just adding file, or increase in the size(maybe there is a threshold for this), will cause it to do a full factory reset. What I also found is that there is a $PATH for /system/sbin but not pointing to anywhere. So I come up with the idea of making another ext4 file system in a file and loop mount it to /system/sbin I guess that work(very well). What I also found is that, there are two kind of factory resets. The one that you perform yourself, which is actually not a full factory reset and the one that Nook get pissed and do the full one.
A factory reset that you perform yourself, whether from the GUI or button combination will basically clean the partition /data while a full blown one will basically restore other partition such as /system
What is included:
basically a zip file, inside that zip file are 6 files.
boot_complete_hook.sh.bak this is basically a modified version of verygreen's
busybox & su are basically from his thread
superuser.apk well I found this one floating around and seem like a good idea to stick it in there (not even sure if it gonna work w/ Nook)
makeroot.bat this is basically what do most of the work. It's base on verygreen original rooting instruction.
sbin_mount This is basically an ext4 file system which have su and another version of busybox all setup nice and tidy for you all. This version of busybox is 1.20.2r2 which I grabbed from here.
Prerequisite:
ADB, it's your responsibility to have adb up and running, meaning not just have it install, but it can see your nook also.
leapinlar wrote a post to help you getting ADB to work here.
Now to get root:
all you have to do is unzip it and run makeroot.bat (obviously you run this in windows command prompt). Yub that's all. The batch file will do the rest, including reboot the nook and wait for it to reboot and stuff. Won't make a coffee for you though.
The manual and hard way:
well, I will only explain this in a summarize way. Basically this start with verygreen rooting method. It basically take advantage of the exploit and run /data/boot_complete_hook.sh which you adb push yourself(with correct permission) with root privilege. What you can run in there is basically up to your creativity. So obviously in this case, you mount the sbin_mount as an ext4 filesystem in the /system/sbin You can make this file yourself if you want to, in linux using dd and mkfs command. Basically using dd to create a file volume to the size you want and mkfs to format it to ext4. Mount it and start uploading stuff you want in there. You will have to correct all the file permission as well. Since all of this will be mounted to /system/sbin you should be aware what you gonna put in there. I guess I could make this thing 100MB, but for this specific purpose 10MB is enough. I my case, just the su and busybox and the symbolic links for the busybox. I'm doing this for the long term. I'm too lazy to point to busybox everytime I wanna do something.
What to do afterward:
Now that you have root, you can Enable Unknown Source to allow you to install app from within the device and install GAPPS. Follow the two guides below if you interested.
Enable Unknown Source: Again, I make an easy little tool for you here.
GAPPS: here.
Did I missed something:
Well, as I said I'm no coder so if I didn't do a clean job, you can refine it. If I didn't document or give proper credit, then I guess I missed that. Sorry about that, again I'm no coder and never done this. And finally:
If this thing work for you, feel free to hit that "THANKS" button. I spent many hours trying to come up with this solution.
FAQ:
Q: My so and so application when attempting to have root access get freeze up, or superuser doesn't work?
A: Well, I'm not sure if this is dued to how the Nook side-loading work or not, but it seem for some reason superuser won't start by itself. So you have to start it manually the first time.
Q: I type in "adb root" and I can't get in as root, it doesn't work?
A: yes it does, it's just not working with adb root. You can get in via "adb shell" once you get in, type in "su" and you can see that you now should have root access.
Thank you so much! This works perfectly. Survives reboot.
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
This sounds like a good idea initially.
It is true that the B&N does not just check for /system/xbin/su directly like they did in the past.
This time they check for something else and I just had no time to look into it more deeply to find out what is it they are actually checking for. I plan to figure this out on Friday when I am back home.
Also wanted to tell you that having Linux background is a great thing when tinkering with Android (at a low level, anyway). I don't have much Android background to speak of as well.
This works really well, and thanks to Someone (and mad props too) for getting persistent root working on this.
I may be being very naive, but my suspicion on the reboot is around the manifest file that's present at root.
It seems to be generated by the boot process and it might provide a quick and dirty list of what's permitted on the device to check. With persistent root, lots of investigation becomes a lot less painful. I expect that by end of day we'll have install unsigned running.
Early in my experimenting with the HD+, I noted:
- some versions of the Google Services Framework can be installed via adb
- when I launched the native calendar app after installing gsf, it wanted to sync to a google account, and was able to add the google account
- one version of the Play store installed and launched as far as throwing the 'you must accept the terms of service' before crashing
What BN most likely does is calculating the hash value (or digest, if you prefer) of certain system files that they think shouldn't be tampered with, then during reboot, the values of these files must match, or they will do a factory reset.
The key point is to find out where they do these checks and fool the check.
This sound simple but it depends on how they implement it. If they use binary decisions (like if the hash_value == calculated), then it is easy to get around. If not (e.g. using white box algorithm to hide keys), then it get more complicated.
excellent and very elegant solution. Kudos!
I'm heading out to work, and if you think your theory is right, try poking around with it. Now that your have root, you can try to dd those bootloading partitions out to user area and upload them out to PC and inspect them.
looking at the vold.fstab
Code:
xloader -> /dev/block/mmcblk0p1
bootloader -> /dev/block/mmcblk0p2
recovery -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p4
rom -> /dev/block/mmcblk0p5
bootdata -> /dev/block/mmcblk0p6
factory -> /dev/block/mmcblk0p7
system -> /dev/block/mmcblk0p8
cache -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p10
Be extra careful when touching those partition if you not sure, don't touch them. But making a block copy of them and taking them out should be relatively easy and safe. Obviously you gonna need a Linux box to do this. I setup a VM on one of my PC last night because I need to get a ext4 partition and put all the goodies in there.
krylon360 said:
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
Click to expand...
Click to collapse
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
someone0 said:
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
Click to expand...
Click to collapse
works just fine.
I chmod a+x'd the script before putting it into the zip.
heh, yeah, it works. Forgot I had my touchpad pluged in and it rebooted it....
whoops.
thanks for posting the location of the /recovery partition. I want to put a copy of htat on ice to prevent BN from undoing any of my work in a future update - I may want some of the fixes they have, but I want to be able to roll them back if needed.
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder and was able to see it in my sideloaded launcher, was able to uncheck/check install non market apps which sets the setting for US to be able to install .apk files from the nook itself, ONLY ISSUE is since I put that file in the system/app folder and the nook didnt like it I got stuck in a bootloop and get to start this process all over again! (nook resetted to ground zero)
maybe we temporary can leave it there get us the permission to install non market apps then remove the file and we will be ok or maybe stuck in another bootloop.
---------- Post added at 09:20 PM ---------- Previous post was at 08:52 PM ----------
GOT IT WORKING NOW:
1. Once rooted, get a file manager with root support and enable read/write permission to /system
2. temporary copy nook tools ver .02 .apk to the system/app folder
3. have a sideloaded launcher and check the app drawer youll see nook tools, run it, first screen uncheck and check the install non market apps box couple of times make sure its checked afterwards
4. have a test .apk to run the BN installer on and see you can now install .apks from the NOOK HD and HD+
5. remove the nook tools.apk file from the system/app folder and quit your file explorer which should reset everything for the system folder back to the way it orginally is!
6. reboot, if you reboot successfully with no boot loop 8 times, your GOLDEN FOR NOW! once again load up a file manager go select an .apk file and see you can now install it! Next step is trying to get amazon market working! then google somehow, but for google you need files in system/app folder permanently!
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
someone0 said:
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
Click to expand...
Click to collapse
when you sidelaod it OR install or have it installed to another folder or ran from another folder it cant modify the setting to allow non market apps to install!!
has to be in the /system/app folder THEN RAN from app drawer then you can set the setting uncheck and check box quit program and for now YOU HAVE to remove the .apk from the system/app folder and then you can reboot and the setting sticks! I GOT AMAZON MARKET INSTALLED right now installing apps! NOW WE GOT A KINDLE ladys and gentleman!
Amazon apk installs in internal memory. Apps downloaded from Amazon get installed in internal memory. You can then move them to SD card or leave them in internal memory. System apps are provided in the ROMs by the developers or vendors. ALWAYS back up before making system changes.. Now rooted - use Titanium Backup. System/app should be static throughout ROM lifecycle unless modified by user.
skyhawk21 said:
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Click to expand...
Click to collapse
This is why I put the /system back to ro, at least that is what I think I did.
Amazon Store working on ROOTED Nook HD
Proof of Concept:
http://youtu.be/wCyd730L74Y
skyhawk21 said:
Proof of Concept:
http://youtu.be/wCyd730L74Y
Click to expand...
Click to collapse
LOL, your internet is slow. Could have cut the video time by 1/2 if not 2/3 if you switch to faster ISP.
skyhawk21 said:
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder
Click to expand...
Click to collapse
What exactly did you install? I cannot find "nook color tools" in Google Play or on APKTOP. Thanks for your hard work!
NEVERMIND! I found the thread that has the link for the app: http://forum.xda-developers.com/showthread.php?t=868366 Thanks again.
does this root method work on Nook HD+2.0.2?
if not how I can downgrade to 2.0.0?
Hi everyone
I am a fan of Nook ST, however, the biggest problem with this cute reader is that It does not use Unicode Font. Hence, I cant read ebooks in my maternal language ( Vietnamese). Does any one know how to replace those default fonts with unicode fonts ( Of window) . I dont want to root my Nook because I just use it for reading
Thanks in advance
You can find some helpful info/pointers at the following links:
http://phanquochuy.me/?p=114
http://nookdevs.com/Font_Changes
http://bookclubs.barnesandnoble.com...n-t-display-Vietnamese-characters/td-p/494819
http://www.mobileread.com/forums/showthread.php?t=178623
Usually the route to supporting unsupported character sets is to use the fallback font, DroidSansFallback.ttf
You might try a font from a newer version of Android or replacing it with some big font.
Since I don't know Vietnamese, I don't know exactly what chars you are looking for.
Are your books in Vietnamese using pre-compiled chars, that is a single char for glyph and accent?
There are reasonably wide choices of fonts that can render the (modern) vietnamese character set (subset of latin alphabet with diacritical marks on vowels, plus one modified consonant), unfortunately none of them is in the stock Nook's font set, and the OP does not want to root his/her NST. Embedding font in the epubs is a pain, even with the referenced plug-in for Calibre.
Well, they may not want to root their Nook, but there is rooting and rooting.
If they slap Clockwork Mod Recovery on an SD card they can remount system, replace DroidSansFallback.ttf and reboot.
No harm done and no one the wiser.
Renate NST said:
Usually the route to supporting unsupported character sets is to use the fallback font, DroidSansFallback.ttf
...
Click to expand...
Click to collapse
I took a peek at /system/fonts: DroidSansFallback.ttf is there but it does not show up in the font menu of the stock Reader. To get it in one would have to muck with the Reader's apk content.
DroidSansFallback.ttf is the fallback font.
You never specify it.
When you punch up a website in Hindi and your regular font does not support Hindi letters, the system tries the fallback font.
There is a lot of stuff in DroidSansFallback.ttf, but not everything.
On my desktop, for instance, Arial Unicode MS is the biggest font that I have.
It has pretty comprehensive support for many languages.
The Android 2.1 DroidSansFallback.ttf is 3,081,908 bytes.
The Android 4.0 DroidSansFallback.ttf is 5,300,184 bytes.
Arial Unicode MS is 24,172,892 bytes!
thank digimax for such useful advice. I knew how to embed font into epub however it will be a bit trouble everytime i want to read a new book
I have an idea when I follow given links, especially Font_Changes of Nookdevs. If we modify the reader app in backup nook (.img) or in update files from B&N(.zip) then restore to device, will it work ?
ectacy said:
thank digimax for such useful advice. I knew how to embed font into epub however it will be a bit trouble everytime i want to read a new book
I have an idea when I follow given links, especially Font_Changes of Nookdevs. If we modify the reader app in backup nook (.img) or in update files from B&N(.zip) then restore to device, will it work ?
Click to expand...
Click to collapse
Your idea might work but it seems a bit "heavy-handed", I personally would explore and opt for a more surgical approach along the line @Renate posted above: e.g., use SD CWM to get the file-system mounted as writable then <adb push> the modified reader apk over.
BTW, what are some good sources of good Vietnamese books in epub formats?
digixmax said:
Your idea might work but it seems a bit "heavy-handed", I personally would explore and opt for a more surgical approach along the line @Renate posted above: e.g., use SD CWM to get the file-system mounted as writable then <adb push> the modified reader apk over.
BTW, what are some good sources of good Vietnamese books in epub formats?
Click to expand...
Click to collapse
Here I attach an Vietnamese epub file, you can take it as sample for "nook surgery" ( I dont know which epub is good source of format, hence i picked one which is not converted by Calibre ) . I am newbie in Android, so much thing to explore and learn ADB seems a complicated tool :silly:
I took a peek at Reader.apk (extracted from FW v1.1.2 I currently use): opening and hacking it up is more work than what I would invest into an exercise I thought of doing just for kick.
If you think stuffs like ADB is complicated, I'd suggest the path I had taken: root your NST and get free Mantano Reader from the Google Play store (it opens and displays just fine the Tuyet Son Phi Ho epub you posted above).
digixmax said:
I took a peek at Reader.apk (extracted from FW v1.1.2 I currently use): opening and hacking it up is more work than what I would invest into an exercise I thought of doing just for kick.
If you think stuffs like ADB is complicated, I'd suggest the path I had taken: root your NST and get free Mantano Reader from the Google Play store (it opens and displays just fine the Tuyet Son Phi Ho epub you posted above).
Click to expand...
Click to collapse
thank you I will consider your advice about rooting and matano . Another solution is to sell my nook and get a kindle , no more epub, no more font ... just prc, just read.
In point of fact, the Reader doesn't handle fallback correctly.
You can get your font to work a number of ways.
The easiest is to substitute one of the fonts like Trebuchet.
Copy arialuni.ttf (Arial Unicode MS) from somewhere to DroidSansFallback.ttf
Create a few links so that bold and italics will work.
Connect with ADB shell:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
cd system/fonts
mv Trebuchet.ttf Trebuchet.bak
mv Trebuchet-Bold.ttf Trebuchet-Bold.bak
mv Trebuchet-BoldItalic.ttf Trebuchet-BoldItalic.bak
mv Trebuchet-Italic.ttf Trebuchet-Italic.bak
Push with ADB:
Code:
adb push arialuni.ttf /system/fonts/DroidSansFallback.ttf
Back to ADB shell:
Code:
cd system/fonts
ln DroidSansFallback.ttf Trebuchet.ttf
ln DroidSansFallback.ttf Trebuchet-Bold.ttf
ln DroidSansFallback.ttf Trebuchet-BoldItalic.ttf
ln DroidSansFallback.ttf Trebuchet-Italic.ttf
Open the book up and select "Trebuchet" as the font.
Here's the first page:
Renate NST said:
In point of fact, the Reader doesn't handle fallback correctly.
You can get your font to work a number of ways.
The easiest is to substitute one of the fonts like Trebuchet.
Copy arialuni.ttf (Arial Unicode MS) from somewhere to DroidSansFallback.ttf
Create a few links so that bold and italics will work.
Connect with ADB shell:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
cd system/fonts
mv Trebuchet.ttf Trebuchet.bak
mv Trebuchet-Bold.ttf Trebuchet-Bold.bak
mv Trebuchet-BoldItalic.ttf Trebuchet-BoldItalic.bak
mv Trebuchet-Italic.ttf Trebuchet-Italic.bak
Push with ADB:
Code:
adb push arialuni.ttf /system/fonts/DroidSansFallback.ttf
Back to ADB shell:
Code:
cd system/fonts
ln DroidSansFallback.ttf Trebuchet.ttf
ln DroidSansFallback.ttf Trebuchet-Bold.ttf
ln DroidSansFallback.ttf Trebuchet-BoldItalic.ttf
ln DroidSansFallback.ttf Trebuchet-Italic.ttf
Open the book up and select "Trebuchet" as the font.
Here's the first page:
Click to expand...
Click to collapse
Do I need to root my Nook touch to connect it with ADB ?
thank Renate NST for your help :-? I think Swapping default reader and modified reader can be done without rooting I am reading your topic about modifying APK . It could be hard but I wont give up
ectacy said:
I think Swapping default reader and modified reader can be done ...
Click to expand...
Click to collapse
This is not about swapping Reader.apk (or ReaderRMSDK.apk).
This is just about swapping fonts for one that support Vietnamese characters.
It doesn't involve changing anything in the boot partition.
Yes, to change anything in the system partition you must have root access somehow for as long as it takes to make the changes.
You have to put something on a SD card and boot up on that.
Your choices are:
Use one of the handy-dandy rooter tools that people post
Use Clockwork Mod Recovery that will directly allow you to use ADB
Use noogie and a Linux system to access the /system partition directly
I have found a way to accomplish this with minimal work on the Nook itself.
A little background. I like using the Caecilia font, but it really bugs me that I can't tell the difference between "normal" and "bold" text because for the latest version of Caecilia installed on the nook the weights of "normal" and "bold" are nearly identical. So I went looking for a way to fix that. Here is what I came with. It should work for any font you want to replace.
1) Obtain a copy of the font you want to use, in my case Lexia DaMa.
2) Obtain a copy of Type Light 3.2.
3) Using some temporary or permanent rooting method, copy the font you want to replace from the /system/fonts directory on your nook using adb pull.
4) Open the font file pulled from your nook in Type light 3.2 and note the name of the font stored INTERNALLY in the file.
5) Open the font you want to use in Type light 3.2 and rename it to match the font you are replacing.
6) Using adb push, copy your replacement font over the EXACT file names for the original font on your nook.
7) Reboot your nook.
7) Use your "new" font by selecting the name of the font you replaced.
You do not need to permanently root your device for this method to work and in does not involved creating links which a non-techie can easily mess up. You can do all of the font files for a particular font, or only the regular font file, depending on your purpose. For the OP's purpose, all of the font files should be done. For my purpose, I only did the "regular" file as Lexia DaMa and Caecilia are very close and the Caecilia BOLD, ITALIC, and BOLDITALIC work just fine for me. You should make a backup copy of the original font files from your nook either on or off the device in case you ever want to switch back.
If anyone is interested, I can post a more detailed (including actual commands) description of this method.
Links aren't that complicated.
In any case, the purpose of the links is to:
Insure that foreign language titles appear correctly in indexes.
Avoid the 4 times duplication of a 24 Meg font file!
David0226 said:
I have found a way to accomplish this with minimal work on the Nook itself.
A little background. I like using the Caecilia font, but it really bugs me that I can't tell the difference between "normal" and "bold" text because for the latest version of Caecilia installed on the nook the weights of "normal" and "bold" are nearly identical. So I went looking for a way to fix that. Here is what I came with. It should work for any font you want to replace.
1) Obtain a copy of the font you want to use, in my case Lexia DaMa.
2) Obtain a copy of Type Light 3.2.
3) Using some temporary or permanent rooting method, copy the font you want to replace from the /system/fonts directory on your nook using adb pull.
4) Open the font file pulled from your nook in Type light 3.2 and note the name of the font stored INTERNALLY in the file.
5) Open the font you want to use in Type light 3.2 and rename it to match the font you are replacing.
6) Using adb push, copy your replacement font over the EXACT file names for the original font on your nook.
7) Reboot your nook.
7) Use your "new" font by selecting the name of the font you replaced.
You do not need to permanently root your device for this method to work and in does not involved creating links which a non-techie can easily mess up. You can do all of the font files for a particular font, or only the regular font file, depending on your purpose. For the OP's purpose, all of the font files should be done. For my purpose, I only did the "regular" file as Lexia DaMa and Caecilia are very close and the Caecilia BOLD, ITALIC, and BOLDITALIC work just fine for me. You should make a backup copy of the original font files from your nook either on or off the device in case you ever want to switch back.
If anyone is interested, I can post a more detailed (including actual commands) description of this method.
Click to expand...
Click to collapse
Your solution seems understandable for me @@ I am buried in a jumble of ADB, CWM, Shell,... :cyclops:
Renate NST said:
This is not about swapping Reader.apk (or ReaderRMSDK.apk).
This is just about swapping fonts for one that support Vietnamese characters.
It doesn't involve changing anything in the boot partition.
Yes, to change anything in the system partition you must have root access somehow for as long as it takes to make the changes.
You have to put something on a SD card and boot up on that.
Your choices are:
Use one of the handy-dandy rooter tools that people post
Use Clockwork Mod Recovery that will directly allow you to use ADB
Use noogie and a Linux system to access the /system partition directly
Click to expand...
Click to collapse
Can you give me detail instruction on this solution. I am having noogie and a CD of Ubuntu. Are they enough to follow this method :victory: