[Q] Nook ST Glowlight - ready to root?

Search This thread
By:
Advanced…
F

Funkdafied

New member
May 16, 2012
3
0
Amazing! Thank you.. I managed to get it working by doing the factory reset through power cycles. I think perhaps I was waiting too long previous and the failed boot count was getting reset.

Its back to factory and I think I'll wait for an update to TouchNooter before trying anything again :) Will also make sure I take a backup this time!

Really appreciate all the effort you went through, roustabout. Thanks!
 
R

roustabout

Senior Member
Feb 12, 2011
825
212
You're welcome. I was interested in what bcb was doing, your post made me go look at it and then try to see a little more about bcb.

My advice would be to make your noogie disk and get a backup now.

If the Android market isn't critical to you, you can then make a CWR boot disk and root using tinynooter and use the Amazon store for apps.

Zydraka made a video, at http://blog.the-ebook-reader.com/2012/05/12/how-to-root-glowlight-nook-touch-with-tinynoot-video/

You can grab CWR for the ST and glow here:

http://xdaforums.com/attachment.php?attachmentid=806433&d=1323121269

unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)

Once you've imaged the SD card, copy in the two tinynoot zipfiles - leave them zipped:

http://www.mediafire.com/?ig75l5b9c24e7q6

http://www.mediafire.com/?2tfitzt97qqfaw7

Apply 1 of 2, then reboot, then
Apply 2 of 2

pull your card, reboot, and you should be rooted.

Many folks are finding you can apply 1 and then apply 2 without even needing to reboot.
 
  • Like
Reactions: Funkdafied
JoeF2

JoeF2

Senior Member
Jan 4, 2011
224
111
Austin, TX
I'm having a problem with the Market on my Glowworm: Enter is not accepted in the search field. I remember that there was a fixed Market for the original Touch, but I forgot where. Anybody have a link?

Sent from my Nexus One using xda app-developers app
 
D

dukenookem

Member
Aug 16, 2012
5
0
bad rooting

Guys, I had quite bad experience rooting my glowlight nook with touchnooter . Basically messed smth up so it couldn't start (just kept flashing). didn't save my back up. had to do unrooting with the software 1.1 that I guess was from nook without glowlight. Unrooting went fine, but the glowlight function is not working anymore. does anyone know how to solve this or could give me a link to download the proper software? thanks!
 
JoeF2

JoeF2

Senior Member
Jan 4, 2011
224
111
Austin, TX
dukenookem said:
Guys, I had quite bad experience rooting my glowlight nook with touchnooter . Basically messed smth up so it couldn't start (just kept flashing). didn't save my back up. had to do unrooting with the software 1.1 that I guess was from nook without glowlight. Unrooting went fine, but the glowlight function is not working anymore. does anyone know how to solve this or could give me a link to download the proper software? thanks!
Click to expand...
Click to collapse
All the guides say to make a backup first... They say that for a reason...
You can not use touchnooter on the Glow. The framework is different. You need the glownooter.
You may try to do a factory reset.
 
Last edited:
T

todortk

Member
May 7, 2011
39
18
I think that for factory reset you must keep the power button for 40 seconds or something like this
 
N

nicolasgleria

New member
Oct 18, 2012
2
0
help! same problem

David Suthers said:
Just attempted to touchnooter the NST Glow. No luck. Here is what happened...

  1. Downloaded Touchnooter-2-1-31
  2. Used WinImage to create the microSD boot "disc"
  3. Powered off Nook and inserted microSD card
  4. Powered Nook on, showed Touchnooter instructions on boot (black flash, remove, reboot, etc.)
  5. Removed microSD and rebooted
  6. Came up to normal "Nook - Read Forever" initial boot screen
  7. Displayed "Nook" boot screen (the one with 5 dots)
  8. Counted through the dots a few times, sorry I didn't get the exact count
  9. Glow light comes on and stays on
  10. Screen will flash black and it will count 3 dots, then flash again and repeat

I let the unit stay on this "stuck loop" for several minutes (at least 10) and nothing changed.

I ended up doing the 8 failed boots restore and the unit is functional again, and "unrooted", so I didn't brick it. But it looks like there is a little work that needs to be done to root the NST Glow.
Click to expand...
Click to collapse

Hello, my name is Nicolas, I'm from Argentina. I was searching in the web for some help and ended up in this thread. So I registered in the forum.
I don't really have any rooting experience. I got my NST Glow a few days ago, and today I tried to root it with no luck. I got the same problem you did.
I was wondering what you mean by "I ended up doing the 8 failed boots restore and the unit is functional again"?
I found a way to restore it but when I did I realize that I had downgraded my NST Glow to the 1.1.0 disabling the glowlight function.
Is there a way to upgrade it back to the original factory firmware?
Thanks in advance for your help!!
 
R

roustabout

Senior Member
Feb 12, 2011
825
212
If you are lucky, your recovery file is still tucked away.

Power off the device. Power it on. As soon as the screen starts to change, hold the power button in until it shuts down again.

If you interrupt the boot process 8 times, you trigger a device restore.

That is the "8 failed boots" process.

For rooting:

Touchnooter won't work.

Tinynoot will work (no android market support.)

Glownooter will work (has android market support.)
 
Last edited:
N

nicolasgleria

New member
Oct 18, 2012
2
0
reset fail rooted NST Glowlight

roustabout said:
If you are lucky, your recovery file is still tucked away.

Power off the device. Power it on. As soon as the screen starts to change, hold the power button in until it shuts down again.

If you interrupt the boot process 8 times, you trigger a device restore.

That is the "8 failed boots" process.

For rooting:

Touchnooter won't work.

Tinynoot will work (no android market support.)

Glownooter will work (has android market support.)
Click to expand...
Click to collapse

Thanks a lot for your help!!!!
I did just that and it worked! my nook went back to factory firmware 1.1.5.
Then the glowlight capability was back.
Something perhaps to keep in mind if someone falls in the same problem I did. Once I got the factory firmware back, everything seemed to work just fine, except for the fact that I couldn't acces the "screen" option inside the "settings" menu. It was not that important since it just allows you to tweak the time the nook takes to go to sleep when there is no activiy (it's 5 minutes by default) and change the screensaver theme (authors or nature).
When I realized this all I did was make a reset with the "botom buttons method", that is:
1º turn off your nook
2º turn it back on holding the Power On button until you see the whole white screen
3º inmediately after the white screen apears release the Power On button and press both bottom "page turn" buttons until a "reset" sign apears
4º touch yes to reset
5º touch yes to confirm resetting
6º nook will reset and reboot
That's it. After I did that everything when back to normal, unrooted, exactly as it was when I unboxed it.

Once again thank you guys for your help!
 
You must log in or register to reply here.

Similar threads

W
New Nook Glowlight Plus
Replies
792
Views
297K
B
broreader
E
Hacking the new Nook GlowLight
Replies
595
Views
171K
Renate
Renate
W
Nook Glowlight 3
Replies
239
Views
82K
C
cde198
N
Full Root for Nook Glowlight
Replies
80
Views
55K
stryker9
stryker9
W
Nook Simple Touch -> Nook Multi Touch [Screensaver Locking Issue Explanation Added]
Replies
128
Views
142K
A
aiamuzz

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    G
    GabrialDestruir
    DeanGibson said:
    GabrialDestruir, your uRamdisk in uRamdisk.zip:

    • When copied to the boot partition, booted fine, and the GlowLight works.
    • However, I do not have ADB access (like I did with the uRamdisk for the Touch 1.1.0 on both the Touch and the Glow).

    Did you enable ADB over USB or over WiFi? I tried to connect using both connection methods. If you provided a WiFi version, I can ping it, but "adb connect ..." doesn't connect. Note that the uRamdisk (for WiFI) for the original Touch allows connections just fine (but alas, no GlowLight).
    Click to expand...
    Click to collapse

    It should be USB enabled from the changes I made.
    New version with default.prop modified uploaded below.
    Also posted the changed files.

    Modified init.rc in this version:
    Code: 
    on init



loglevel 3



# setup the global environment

    export PATH /sbin:/system/sbin:/system/bin:/system/xbin

    export LD_LIBRARY_PATH /system/lib

    export ANDROID_BOOTLOGO 1

    export ANDROID_ROOT /system

    export ANDROID_ASSETS /system/app

    export ANDROID_DATA /data

    export EXTERNAL_STORAGE /sdcard

    export INTERNAL_STORAGE /media

    export BN_PURCHASED_CONTENT /data/media

    export BOOTCLASSPATH /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar

    export DSP_PATH /system/lib/dsp

    export DEFAULT_BASEIMAGE /system/lib/dsp/baseimage.dof

    export QOSDYN_FILE /system/lib/dsp/qosdyn_3430.dll64P

    export PM_TBLFILE /system/etc/policytable.tbl



# setup TSLIB environment

    export TSLIB_CONSOLEDEVICE none

    export TSLIB_FBDEVICE /dev/graphics/fb0

    export TSLIB_TSDEVICE /dev/input/event2

    export TSLIB_CALIBFILE /etc/pointercal

    export TSLIB_CONFFILE /etc/ts.conf

    export TSLIB_PLUGINDIR /system/lib/ts/plugins



# Location of BT firmware files

    export BT_FW_PATH /system/lib/firmware    

# Backward compatibility

    symlink /system/etc /etc



# create mountpoints and mount tmpfs on sqlite_stmt_journals

    mkdir /system

    mkdir /tmp 0777

    mkdir /data 0771 system system

    mkdir /cache 0770 system cache

    mkdir /media 0777 system system

    mkdir /sdcard 0777 system system

    mkdir /sqlite_stmt_journals 01777 root root

    mkdir /rom 0770 root root

    mount tmpfs tmpfs /sqlite_stmt_journals size=4m



    mount rootfs rootfs / ro remount



    write /proc/sys/kernel/panic_on_oops 1

    write /proc/sys/kernel/hung_task_timeout_secs 0

    write /proc/cpu/alignment 4

    write /proc/sys/kernel/sched_latency_ns 10000000

    write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000



# mount MMC partitions

    mount vfat /dev/block/mmcblk0p2 /rom sync noatime nodiratime uid=1000,gid=1000,fmask=117,dmask=007



    # Mount /system rw first to give the filesystem a chance to save a checkpoint

    mount ext2 /dev/block/mmcblk0p5 /system

    mount ext2 /dev/block/mmcblk0p5 /system ro remount



    # We chown/chmod /data again so because mount is run as root + defaults

    mount ext3 /dev/block/mmcblk0p8 /data nosuid nodev noatime nodiratime

    chown system system /data

    chmod 0771 /data



    # Same reason as /data above

    mount ext3 /dev/block/mmcblk0p7 /cache nosuid nodev noatime nodiratime

    chown system cache /cache

    chmod 0770 /cache



    # This may have been created by the recovery system with odd permissions

    chown system system /cache/recovery

    chmod 0770 /cache/recovery



# create basic filesystem structure

    mkdir /data/misc 01771 system misc

    mkdir /data/misc/hcid 0770 bluetooth bluetooth

    mkdir /data/misc/keystore 0700 keystore keystore

    mkdir /data/misc/wifi 0771 wifi wifi

    mkdir /data/misc/wifi/sockets 0771 wifi wifi

    mkdir /data/misc/dhcp 0777 wifi wifi

    mkdir /data/misc/udhcpd 0777 wifi wifi

    mkdir /data/local 0771 shell shell

    mkdir /data/local/tmp 0771 shell shell

    mkdir /data/data 0771 system system

    mkdir /data/app-private 0771 system system

    mkdir /data/app 0771 system system

    mkdir /data/property 0700 root root



    # BN PurchasedContent

    mkdir /data/media 0777 media system

    mkdir /data/media/B\&N\ Downloads 0777 media system

    mkdir /data/media/B\&N\ Downloads/Books 0777 media system

    mkdir /data/media/B\&N\ Downloads/Magazines 0777 media system

    mkdir /data/media/B\&N\ Downloads/Newspapers 0777 media system

    mkdir /data/media/B\&N\ Downloads/Extras 0777 media system

    # make sure folder has correct owner and access if the folder exists

    chown media system /data/media

    chown media system /data/media/B\&N\ Downloads

    chown media system /data/media/B\&N\ Downloads/Books

    chown media system /data/media/B\&N\ Downloads/Magazines

    chown media system /data/media/B\&N\ Downloads/Newspapers

    chown media system /data/media/B\&N\ Downloads/Extras

    chmod 0777 /data/media

    chmod 0777 /data/media/B\&N\ Downloads

    chmod 0777 /data/media/B\&N\ Downloads/Books

    chmod 0777 /data/media/B\&N\ Downloads/Magazines

    chmod 0777 /data/media/B\&N\ Downloads/Newspapers

    chmod 0777 /data/media/B\&N\ Downloads/Extras

	

    # create dalvik-cache and double-check the perms

    mkdir /data/dalvik-cache 0771 system system

    chown system system /data/dalvik-cache

    chmod 0771 /data/dalvik-cache



    # create the lost+found directories, so as to enforce our permissions

#    mkdir /data/lost+found 0770

#    mkdir /cache/lost+found 0770



    # change permissions for alsa nodes

    symlink /dev/snd/pcmC0D0c /dev/pcmC0D0c

    symlink /dev/snd/pcmC0D0p /dev/pcmC0D0p

    symlink /dev/snd/controlC0 /dev/controlC0

    symlink /dev/snd/timer /dev/timer

    chmod 0777 /dev/pcmC0D0c

    chmod 0777 /dev/pcmC0D0p

    chmod 0777 /dev/controlC0

    chmod 0777 /dev/timer



    # change permissions for modem

    chmod 0660 /dev/ttyS0

    chown radio radio /dev/ttyS0



    # change permissions for bridge.  Symlink search directory

    chmod 0777 /dev/DspBridge



    # change permissions for Camera

    chmod 0777 /dev/video5

    chmod 0777 /dev/video0



    # change permissions for Overlay

    chmod 0777 /dev/video1

    chmod 0777 /dev/video2

    



# change permissions for overlay managers and display devices

    chmod 0777 /sys/devices/platform/omapdss/manager0/name

    chmod 0777 /sys/devices/platform/omapdss/manager1/name



    chmod 0777 /sys/devices/platform/omapdss/display0/name

    chmod 0777 /sys/devices/platform/omapdss/display1/name



    chmod 0777 /sys/devices/platform/omapdss/display0/enabled

    chmod 0777 /sys/devices/platform/omapdss/display1/enabled



    chmod 0777 /sys/devices/platform/omapdss/display1/timings

    chmod 0777 /sys/devices/platform/omapdss/display0/timings



    chmod 0777 /sys/devices/platform/omapdss/overlay0/manager

    chmod 0777 /sys/devices/platform/omapdss/overlay1/manager

    chmod 0777 /sys/devices/platform/omapdss/overlay2/manager



    chmod 0777 /sys/devices/platform/omapdss/overlay0/enabled

    chmod 0777 /sys/devices/platform/omapdss/overlay1/enabled

    chmod 0777 /sys/devices/platform/omapdss/overlay2/enabled



# change permissions for calibration

    chmod 0666 /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/forcecal



# change permissions for display jni ioct

    chmod 0666 /dev/graphics/fb0



    # change permissions for Previewer and Resizer

    chmod 0777 /dev/omap-previewer

    chmod 0777 /dev/omap-resizer



    # double check the perms, in case lost+found already exists, and set owner

    chown root root /lost+found

    chmod 0770 /lost+found

#    chown root root /data/lost+found

#    chmod 0770 /data/lost+found

#    chown root root /cache/lost+found

#    chmod 0770 /cache/lost+found



#Owners, Modes for Bluetooth

    chmod 0660 /dev/ttyS1

    chown bluetooth bluetooth /dev/ttyS1

    chmod 0660 sys/class/rfkill/rfkill0/state

    chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state

    write sys/class/rfkill/rfkill0/state 0



# Needed when building with DDK

    chown system system /data/data

    chown system system /data/system

    chown system system /data/app

    chown system system /data



on boot

# basic network init

    ifup lo

    hostname localhost

    domainname localdomain



# set RLIMIT_NICE to allow priorities from 19 to -20

    setrlimit 13 40 40



# Set timeout value for rmnet stats.

    write /sys/devices/virtual/net/rmnet0/timeout_suspend 5000000



# Define the oom_adj values for the classes of processes that can be

# killed by the kernel.  These are used in ActivityManagerService.

#    setprop service.adb.tcp.port 5555

    setprop ro.FOREGROUND_APP_ADJ 0

    setprop ro.VISIBLE_APP_ADJ 1

    setprop ro.SECONDARY_SERVER_ADJ 2

    setprop ro.BACKUP_APP_ADJ 2

    setprop ro.HOME_APP_ADJ 4

    setprop ro.HIDDEN_APP_MIN_ADJ 7

    setprop ro.CONTENT_PROVIDER_ADJ 14

    setprop ro.EMPTY_APP_ADJ 15



# Define the memory thresholds at which the above process classes will

# be killed.  These numbers are in pages (4k).

    setprop ro.FOREGROUND_APP_MEM 1536

    setprop ro.VISIBLE_APP_MEM 2048

    setprop ro.SECONDARY_SERVER_MEM 4096

    setprop ro.BACKUP_APP_MEM 4096

    setprop ro.HOME_APP_MEM 4096

    setprop ro.HIDDEN_APP_MEM 5120

    setprop ro.CONTENT_PROVIDER_MEM 5632

    setprop ro.EMPTY_APP_MEM 6144



# Enable auto-mounting of USB mass storage

    setprop persist.service.mount.umsauto 1



# Write value must be consistent with the above properties.

# Note that the driver only supports 6 slots, so we have HOME_APP at the

# same memory level as services.

    write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15



    write /proc/sys/vm/overcommit_memory 1

    write /proc/sys/vm/min_free_order_shift 4

    write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144



    # Set init its forked children's oom_adj.

    write /proc/1/oom_adj -16



# Copying hostapd.conf (WLAN soft AP)

    copy /system/etc/wifi/softap/hostapd.conf /data/misc/wifi/hostapd.conf

    chown wifi wifi /data/misc/wifi



# Enabling Power Management features



    # Enabling sleep in idle path

    write /sys/power/sleep_while_idle 1



    # Enabling OFF mode

    write /sys/power/enable_off_mode 1



    # Enabling Voltage OFF in idle path

    write /sys/power/voltage_off_while_idle 1



    # Enablig DVFS with conservative governor

    write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor conservative



    # Enabling SmartReflex for Zoom3 OMAP3630

    write  /sys/power/sr_vdd1_autocomp 0

    write  /sys/power/sr_vdd2_autocomp 0



    # Permissions for System Server and daemons.

    chmod 0444 /system/usr/keychars/omap_twl4030keypad.kcm.bin

    chmod 0444 /system/usr/keychars/TWL4030_Keypad.kcm.bin

    chmod 0444 /system/usr/keychars/gpio-keys.kcm.bin

    chmod 0444 /system/usr/keychars/qwerty.kcm.bin

    chown radio system /sys/android_power/state

    chown radio system /sys/android_power/request_state

    chown radio system /sys/android_power/acquire_full_wake_lock

    chown radio system /sys/android_power/acquire_partial_wake_lock

    chown radio system /sys/android_power/release_wake_lock

    chown radio system /sys/power/state

    chown radio system /sys/power/wake_lock

    chown radio system /sys/power/wake_unlock

    chmod 0660 /sys/power/state

    chmod 0660 /sys/power/wake_lock

    chmod 0660 /sys/power/wake_unlock

    chown system system /sys/class/timed_output/vibrator/enable

    chown system system /sys/class/leds/keyboard-backlight/brightness

    chown system system /sys/class/leds/lcd-backlight/brightness

    chown system system /sys/class/leds/lcd-backlight/dim_brightness

    chown system system /sys/class/leds/lcd-backlight2/dim_brightness

    chown system system /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0040/dim_start

    chown system system /sys/class/leds/button-backlight/brightness

    chown system system /sys/class/leds/jogball-backlight/brightness

    chown system system /sys/class/leds/red/brightness

    chown system system /sys/class/leds/green/brightness

    chown system system /sys/class/leds/blue/brightness

    chown system system /sys/class/leds/red/device/grpfreq

    chown system system /sys/class/leds/red/device/grppwm

    chown system system /sys/class/leds/red/device/blink

    chown system system /sys/class/leds/red/brightness

    chown system system /sys/class/leds/green/brightness

    chown system system /sys/class/leds/blue/brightness

    chown system system /sys/class/leds/red/device/grpfreq

    chown system system /sys/class/leds/red/device/grppwm

    chown system system /sys/class/leds/red/device/blink

    chown system system /sys/class/timed_output/vibrator/enable

    chown system system /sys/module/sco/parameters/disable_esco

    chown system system /sys/kernel/ipv4/tcp_wmem_min

    chown system system /sys/kernel/ipv4/tcp_wmem_def

    chown system system /sys/kernel/ipv4/tcp_wmem_max

    chown system system /sys/kernel/ipv4/tcp_rmem_min

    chown system system /sys/kernel/ipv4/tcp_rmem_def

    chown system system /sys/kernel/ipv4/tcp_rmem_max

    chown root radio /proc/cmdline



    # Set default dim speed to 500ms

    write /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0040/dim_time 500



# Define TCP buffer sizes for various networks

#   ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,

    setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208

    setprop net.tcp.buffersize.wifi    4095,87380,110208,4096,16384,110208

    setprop net.tcp.buffersize.umts    4094,87380,110208,4096,16384,110208

    setprop net.tcp.buffersize.edge    4093,26280,35040,4096,16384,35040

    setprop net.tcp.buffersize.gprs    4092,8760,11680,4096,8760,11680



# Define modem related settings

    setprop ro.radio.use-ppp yes

    setprop keyguard.no_require_sim 1 

    setprop ro.config.nocheckin yes



# Set EPD Flushing Update percentage for AUTO Mode.

    write /sys/class/graphics/fb0/epd_percent 85

# Set EPD Flush elimination window (ms) for AUTO Mode.

    write /sys/class/graphics/fb0/epd_delay 100



    class_start default



    start omap-edpd



#    start console





## Daemon processes to be run by init.

##

service console /system/bin/sh

    console



# load DSP firmware

service baseimage /system/bin/cexec.out /system/lib/dsp/baseimage.dof

    user root

    group audio

    oneshot



# Responsable of DSP recovery

service bridged /system/bin/bridged

     user root

     group system

     oneshot



service omx_pm /system/bin/OMXPolicyManager

    oneshot



service omx_rm /system/bin/OMXResourceManager

    oneshot



# adbd is permanent

service adbd /sbin/adbd





service bootanim /system/bin/bootanimation

    user graphics

    group graphics

    disabled

    oneshot



#service mux /system/bin/gsm0710muxd -s /dev/ttyS1 -n 3 -m basic

#service mux /system/bin/gsm0710muxd -v -s /dev/ttyS0 -b 460800 -n 3 -m advanced

#    user radio      

#    group radio cache inet misc

#    oneshot



service servicemanager /system/bin/servicemanager

    user system

    critical

    onrestart restart zygote

    onrestart restart media



service vold /system/bin/vold

    socket vold stream 0660 root mount



#service mountd /system/bin/mountd

#    socket mountd stream 0660 root mount



service debuggerd /system/bin/debuggerd



# Start of SGX driver

service pvrsrv /system/bin/sh /system/bin/sgx/rc.pvr start

    user root

    oneshot



#service ril-daemon /system/bin/rild -l /system/lib/libidcc6071-ril.so -- -d /dev/pts/0

#service ril-daemon /system/bin/rild -l /system/lib/libenforaedg308-ril.so -- -d /dev/pts/0

#    socket rild stream 660 root radio

#    socket rild-debug stream 660 radio system

#    user root

#    group radio cache inet misc



#service pppd_gprs /etc/init.gprs-pppd /dev/pts/1

#   user root

#   group radio cache inet misc

#   disabled



service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server

    socket zygote stream 666

    onrestart write /sys/android_power/request_state wake



service media /system/bin/mediaserver

    user media

    group system audio camera graphics inet net_bt net_bt_admin



#service fw3a /system/bin/fw3a_core

#    user root

#    group root



#service bootsound /system/bin/playmp3

#    user media

#    group audio

#    oneshot



service dbus /system/bin/dbus-daemon --system --nofork

    socket dbus stream 660 bluetooth bluetooth

    user bluetooth

    group bluetooth net_bt_admin



#service bluetoothd /system/bin/bluetoothd -d -n

#    socket bluetooth stream 660 bluetooth bluetooth

#    socket dbus_bluetooth stream 660 bluetooth bluetooth

#    # init.rc does not yet support applying capabilities, so run as root and

#    # let hcid drop uid to bluetooth with the right linux capabilities

#    group bluetooth net_bt_admin misc

#    disabled

#    oneshot



#service uim /system/xbin/uim /dev/ttyS1 3000000 1 /sys/uim/pid 19

#   user root

#   group media bluetooth

#   oneshot



#service hciattach /system/bin/hciattach -l 

#    user root

## changing user to root from bluetooth is a potential security issue

## service hciattach_legacy is used instead of hciattach because, we dont 

## have nodes named ttyHS0

#    group bluetooth net_bt_admin misc

#    disabled

#    oneshot



#service hciattach_legacy /system/bin/hciattach -n /dev/ttyS1 texas 3000000

#    user root

## changing user to root from bluetooth is a potential security issue

#    group bluetooth net_bt_admin misc

#    disabled

#    oneshot



#service hfag /system/bin/sdptool add --channel=10 HFAG

#    user bluetooth

#    group bluetooth net_bt_admin

#    disabled

#   oneshot



#service hsag /system/bin/sdptool add --channel=11 HSAG

#    user bluetooth

#    group bluetooth net_bt_admin

#    disabled

#    oneshot



#service opush /system/bin/sdptool add --channel=12 OPUSH

#    user bluetooth

#    group bluetooth net_bt_admin

#    disabled

#    oneshot



#service pbap /system/bin/sdptool add --channel=19 PBAP

#    user bluetooth

#    group bluetooth net_bt_admin

#    disabled

#    oneshot





service installd /system/bin/installd

    socket installd stream 600 system system



service flash_recovery /system/bin/flash_image recovery /system/recovery.img

    oneshot



service wlan_loader /system/bin/tiwlan_loader \

    -f /system/etc/wifi/firmware.bin \

    -i /system/etc/wifi/tiwlan.ini \

    -e /rom/devconf/WiFiBackupCalibration

    disabled

    oneshot



service ifcfg_ti /system/bin/ifconfig tiwlan0 up

    disabled

    oneshot



service wpa_supplicant /system/bin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf -dd

    socket wpa_tiwlan0 dgram 660 wifi wifi

    disabled

    oneshot



service dhcpcd /system/bin/dhcpcd -ABKL -d tiwlan0

    disabled 

    oneshot



# TI WLAN Soft AP related services and configuration



service wlan_ap_loader /system/bin/tiap_loader \

    -f /system/etc/wifi/softap/firmware_ap.bin \

    -i /system/etc/wifi/softap/tiwlan_ap.ini

    disabled

    oneshot



service udhcpd /system/bin/udhcpd /system/etc/udhcpd/udhcpdWlan.conf

    disabled

    oneshot



service hostapd /system/bin/hostapd -dd /data/misc/wifi/hostapd.conf

    disabled

    oneshot



service keystore /system/bin/keystore /data/misc/keystore

    user keystore

    group keystore

    socket keystore stream 666



# TODO: load waveform file from ROM token /rom/devconf/EpdWaveform instead

service omap-edpd /system/bin/omap-edpd.elf -n --timeout=2 -pV220 --fbdev=/dev/graphics/fb0 -s /system/lib/dsp/subframeip_snode_dsp.dll64P -w /rom/devconf/EpdWaveform,/system/etc/default_waveform.bin

    oneshot

    disabled



on property:dev.bootcomplete=1

    start bootcnt



service bootcnt /system/bin/clrbootcount.sh

    disabled

    oneshot



service debuglog /system/bin/debuglog.sh

    user root



    Modified default.prop in this version:
    Code: 
    #
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
    View
    3
    G
    GabrialDestruir
    Here we go, uRamdisk for NTG is attached.
    Should enable ADB permanently without affecting anything else.
    View
    2
    D
    David Suthers
    Just attempted to touchnooter the NST Glow. No luck. Here is what happened...

    1. Downloaded Touchnooter-2-1-31
    2. Used WinImage to create the microSD boot "disc"
    3. Powered off Nook and inserted microSD card
    4. Powered Nook on, showed Touchnooter instructions on boot (black flash, remove, reboot, etc.)
    5. Removed microSD and rebooted
    6. Came up to normal "Nook - Read Forever" initial boot screen
    7. Displayed "Nook" boot screen (the one with 5 dots)
    8. Counted through the dots a few times, sorry I didn't get the exact count
    9. Glow light comes on and stays on
    10. Screen will flash black and it will count 3 dots, then flash again and repeat

    I let the unit stay on this "stuck loop" for several minutes (at least 10) and nothing changed.

    I ended up doing the 8 failed boots restore and the unit is functional again, and "unrooted", so I didn't brick it. But it looks like there is a little work that needs to be done to root the NST Glow.
    View
    2
    R
    roustabout
    I just posted a minimal touch based rooting script (ie, a clockwork script that copies in a few files) for rooting the glowworm.

    See http://xdaforums.com/showthread.php?p=26015994#post26015994

    for the details including links to the NST/glowworm CWR disk and the two rooting files I made, both installed via Clockwork.

    I have to run out the door very soon or I'd post more, but many many thanks to all who made it possible - all the parts were around, all I needed to do was put them together. (and leave out the ones I'm clueless about!)
    View
    2
    R
    roustabout
    Many, many thanks to Gabrial for his hard and continuing work!

    I copied in his second uRamdisk and am now rooted w/ADB support over wifi.

    Copy in adb wireless to your /data/apps folder, and a launcher (both while booted from noogie, with a linux host mounting up the filesystems.) Set up /system properly for su, again just copying in from your stock ST. Enable ADB over wireless using that tool - persistent would be cool, but being able to turn it on at all is great.

    I have an alternate launcher, adb over wifi, su installed.

    Repartiitioning is done, symlinks are done. I didn't get the partitions exactly how I wanted them, but I have 880
    mb of internal storage for myself, the unit is registered and is downloading to /media so I can fish the files I want
    back out.

    Win, except that the illumination is pretty uneven on my unit.

    Does that improve over time?

    I haven't tried getting the G market running, but I did just set up the Amazon market and it is running with no trouble at all.

    I see with interest that the glowworm has a browser built into it still, exposed once you install a launcher and Button Savior.
    View

New posts