Hacking the new Nook GlowLight

ErikMunoz · Jan 15, 2014

Smsung solved

Renate NST said:
Well, I'm confused with this Samsung driver stuff.
When does it show this?
See, the bootloader for the Nook is a TI OMAP bootloader and it's totally different, so it can't be showing it then, even if you did load some Samsung driver.
If you ever see something in Device Manager that says "Samsung", click on "Update Driver" and select the extras\google\usb_driver\android_winusb.inf that you modified.

i've deleted all samsung trail of my computer(drivers and registry) and now i can see my device as "Android Device" and " Android Bootloader interface" which is good, i've tried again the command getting the same results:

Code:

Error 0000001F reading response, read 0 bytes

i was hoping the driver issue could solve it.

Renate · Jan 15, 2014

I really think that there is something about x-loader that does not agree with your Nook.

Run omaplink with just one filename.
Try all the files that have aboot in their name and all the files that have x-loader in their name.

I don't believe that I've heard it confirmed from any NG2 loader that x-loader has worked.
The original success on NG2 was with aboot.

Unrelated, just for your reference, here is the complete partitioning scheme:

Code:

Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
128 heads, 32 sectors/track, 1864 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Partition  Format  Id  Start  End   Size (bytes)   Mount
---------  ------  --  -----  ----  -------------  --------
Total                     1   1864  3,909,091,328
MBR                       1                16,384
mmcblk0p1   vfat   0c     1+    38     79,675,392  /boot
mmcblk0p2   vfat   0c    39     46     16,777,216  /rom
mmcblk0p3   ext2   83    47    141    199,229,440  /factory
mmcblk0p4          05   142   1864  3,613,392,896
mmcblk0p5   ext2   83   142    285    301,989,888  /system
mmcblk0p6   vfat   0c   286    539    532,676,608  /media
mmcblk0p7   ext3   83   540    659    251,658,240  /cache
mmcblk0p8   ext3   83   660    791    276,824,064  ???
mmcblk0p9   ext3   83   792   1864  2,250,244,096  /data

ErikMunoz · Jan 15, 2014

got it

Renate NST said:
I really think that there is something about x-loader that does not agree with your Nook.

Run omaplink with just one filename.
Try all the files that have aboot in their name and all the files that have x-loader in their name.

I don't believe that I've heard it confirmed from any NG2 loader that x-loader has worked.
The original success on NG2 was with aboot.

Unrelated, just for your reference, here is the complete partitioning scheme:

Code:

Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes 128 heads, 32 sectors/track, 1864 cylinders Units = cylinders of 4096 * 512 = 2097152 bytes Partition Format Id Start End Size (bytes) Mount --------- ------ -- ----- ---- ------------- -------- Total 1 1864 3,909,091,328 MBR 1 16,384 mmcblk0p1 vfat 0c 1+ 38 79,675,392 /boot mmcblk0p2 vfat 0c 39 46 16,777,216 /rom mmcblk0p3 ext2 83 47 141 199,229,440 /factory mmcblk0p4 05 142 1864 3,613,392,896 mmcblk0p5 ext2 83 142 285 301,989,888 /system mmcblk0p6 vfat 0c 286 539 532,676,608 /media mmcblk0p7 ext3 83 540 659 251,658,240 /cache mmcblk0p8 ext3 83 660 791 276,824,064 ??? mmcblk0p9 ext3 83 792 1864 2,250,244,096 /data

i've followed the instruccions of here http://bbs.cooldu.net/forum.php?mod=viewthread&tid=680 and now i got Fastboot access, but google translator is not good whit chinesse

, i don't know hot to edit the uRamdisk.

Now i'm waiting for ADB but i don't know how to continue.

Why my devices is showed as Gossamer?

Note:
The files that i used with a-boot seems like old files from here.

Renate · Jan 15, 2014

Try replacing the last two files with the noogie image and ramdisk.
When it says "Waiting for ADB..." don't worry, just see if your PC mounted a disk from your Nook.

usenothing · Jan 15, 2014

Renate NST said:
It looks like they create /sdcard in init.rc like the other nooks do but don't have that linked to anywhere.

Code:

export EXTERNAL_STORAGE /sdcard export INTERNAL_STORAGE /media export BN_PURCHASED_CONTENT /data/media

This will probably cause problems with many apps that want to store things on /sdcard
As I've said already, the best solution is to make /data on mmcblk1p8 like the older nooks and make /sdcard on mmcblk1p9
The relative sizes depends on what you want to do.

hi.
500 M is enough for me, and i donot have the need to adjust the "500 M" space.
I just want to know how to achieve "the best choice" you mentioned. Is it the code you quoted in this relpy？

Sent from my Nexus S using xda app-developers app

Renate · Jan 16, 2014

The snippet of code that I posted above is from the NG2 init.rc in uRamdisk.
It just was meant to show the intended storage usage.

Your Nook should run similarly to a Nook Touch without any SD card inserted.
I'm not sure if any apps dislike having no SD card.
They have to store their stuff in the corresponding /data/data/com.example.app/ directory.

It looks right now that there are some problems using the x-loader method with the NG2.
If an NG2 owner has gotten x-loader to work with either Linux or Windows we'd like to know.
For now, use the omap3_aboot.bin with u-boot
The later versions of omaplink.exe support both aboot and x-loader methods

There are 3 possible things to boot, noogie, Clockwork Mod or stock Nook.
As far as I know, only noogie has been successfully booted on a NG2.

If you are an NG2 owner and just want to get it rooted, follow the instructions in this thread using omap3_aboot.bin, u-boot, noogie_image, noogie_ramdisk.
Then modify uRamdisk on the NG2 /boot partition using bootutil.exe and a Unix-style editor on init.rc

straygecko has said that he will eventually be working on trying to get x-loader running better on NG2.

ErikMunoz · Jan 16, 2014

sure

Renate NST said:
Try replacing the last two files with the noogie image and ramdisk.
When it says "Waiting for ADB..." don't worry, just see if your PC mounted a disk from your Nook.

it mounts a boot device...

Renate · Jan 16, 2014

So, copy uRamdisk over to your PC.
Follow the instructions here: http://xdaforums.com/showthread.php?p=49070213#post49070213

ErikMunoz · Jan 16, 2014

Finally i got it

Renate NST said:
So, copy uRamdisk over to your PC.
Follow the instructions here: http://xdaforums.com/showthread.php?p=49070213#post49070213

got it!! now i have ADB enabled

thank you so much!

Renate · Jan 17, 2014

Great!

Could you copy/paste the results of this command:

Code:

adb shell mount

I think I'm confused about what is normally mounted in the NG2.
I didn't see any mention of mmcblk0p6 or mmcblk0p8 in the previous posts from others.

usenothing · Jan 17, 2014

I achieved "running adb" two weeks ago.
1. The result of "mount" :

Code:

mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmas
k=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=rem
ount-ro 0 0
/dev/block/mmcblk0p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk0p9 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=contin
ue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=conti
nue,data=ordered 0 0

2.You said we have three ways to boot.
If ,if we want to boot with CWM mode, what arguments should I use?
I tried

Code:

omaplink x-load-ng2-130-stk.bin u-boot-ng2-130-stk.bin uImage-ng2-130-stk uRamdisk-noogie

one week about ago, and it didn't work (I cannot remember the error hint,sorry) .

Renate NST said:
Great!

Could you copy/paste the results of this command:

Code:

adb shell mount

I think I'm confused about what is normally mounted in the NG2.
I didn't see any mention of mmcblk0p6 or mmcblk0p8 in the previous posts from others.

Renate · Jan 17, 2014

So that dump of mount is what you get on your NG2 when it's happily running the stock reader software?
I'm confused.
When you have your NG2 connected over USB do you see two removable disks on your PC?
What is on these disks? What is the volume label?

I can boot up CWM using bootloader methods easily.
The problem is that the NG2 has a different screen resolution and needs a different CWM.
Without the screen working correctly, all you get out of using CWM is the use of ADB.

Neither straygecko or I have a NG2, so in some ways we've been lucky to get this far.

usenothing · Jan 18, 2014

1.
1.1
When I connect my Nook to PC with USB, I can only open one "removable disk" ('J' in my PC), although I can see another "removable disk" in "my computer"( 'K' in my PC, it's called 'boot' and can be opened in the process of rooting, not now).
In 'J', I can see all my books I have transfered.
1.2
When Iconnect my Nook to PC with usb cable, it's on "USB mode" defaultly . At this time, "adb" works finely, but, I cannot read any books with the Nook hint——You may now safely move files from your PC to your NOOK: please properly eject NOOK from your computer to avoid file transfer problems.

2.
Thanks you and straygecko for all your work. I know we are lucky to get all this ,but ,we should mostly give the credit to

your works ,not "luck".

Renate NST said:
So that dump of mount is what you get on your NG2 when it's happily running the stock reader software?
I'm confused.
When you have your NG2 connected over USB do you see two removable disks on your PC?
What is on these disks? What is the volume label?

I can boot up CWM using bootloader methods easily.
The problem is that the NG2 has a different screen resolution and needs a different CWM.
Without the screen working correctly, all you get out of using CWM is the use of ADB.

Neither straygecko or I have a NG2, so in some ways we've been lucky to get this far.

Renate · Jan 18, 2014

Oh, alright, silly me.

mmcblk0p6 is mounted on /media by vold.
When you are using ADB over USB, the UMS kicks in and unmounts /media from the Nook.

vold.conf does have stuff in it for mounting a (non-existent) SD card on /sdcard.

So the only mystery is what mmcblk0p8 is being saved for?

ErikMunoz · Jan 20, 2014

Sure

Renate NST said:
Great!

Could you copy/paste the results of this command:

Code:

adb shell mount

I think I'm confused about what is normally mounted in the NG2.
I didn't see any mention of mmcblk0p6 or mmcblk0p8 in the previous posts from others.

there you go

Sorry for my late response.

Code:

C:\Users\JGR-AutoTriage-002\AppData\Local\Android\sdk\platform-tools>adb shell m
ount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmas
k=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=rem
ount-ro 0 0
/dev/block/mmcblk0p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk0p9 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=contin
ue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=conti
nue,data=ordered 0 0

C:\Users\JGR-AutoTriage-002\AppData\Local\Android\sdk\platform-tools>

Edit:
i have 2 questions:

Question1:
if i could have a second NG2 could i use my modified uRamdisk on it? or i need to edit the files again?

Quiestion2:
to goes back ( unroot ) i need to replace the uramdisk with the original right?

Renate · Jan 21, 2014

Yes, to root another NG2 you just need to copy over the same modified uRamdisk.
There is nothing personalized in uImage or uRamdisk.
All the devices-specific data is in /rom
You've backed that up already in a safe place, right?

To unroot, just copy the original uRamdisk back.

hrulik · Jan 21, 2014

Cool! can you please make howto root NG2, or program to root for ppl?

ErikMunoz · Jan 21, 2014

Renate NST said:
Yes, to root another NG2 you just need to copy over the same modified uRamdisk.
There is nothing personalized in uImage or uRamdisk.
All the devices-specific data is in /rom
You've backed that up already in a safe place, right?

To unroot, just copy the original uRamdisk back.

yes, everithing is backed up
many thanks renate

Renate · Jan 22, 2014

A short recap of how to root the new NG2:

All of these methods use the Texas Instruments OMAP processor USB bootloader.

The desktop system that you connect the Nook to can be either Linux or Windows.
This only details the Windows method.

The bootloaded system can be either noogie or Clockwork Mod or a modified stock Nook.
For now, we are only using the noogie method.

The bootloading sequence can be either aboot, u-boot or x-loader, u-boot.
For now, we are only using the aboot, u-boot method.

Preparation
In Window, we need drivers to communicate with all USB devices.
The bnusbdriver.zip attached below is the modified stock driver.
Unzip it and when installing or re-installing select this driver manually.
Manually means saying, "No, I will select" until you get down to "Have disk" and select the specific directory.
The driver info is unsigned, although the drivers themselves are stock Windows.

Collect the necessary files.
omaplink.exe can be found in the signature below.
The four files can be downloaded here: http://xdaforums.com/showpost.php?p=49779966&postcount=285

Booting
Fully power your Nook down with the USB disconnected.
Run this command on the PC.

Code:

omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie

Plug the USB into the Nook.
Whenever a "New Device" popup appears manually select android_winusb.inf to be loaded then start this step over.
omaplink should get as far as "Waiting for ADB..."
It won't find it just yet, use ^C to exit.
At this point there should be a new removable disk mounted with a dozen files on it, including uRamdisk

Rooting
Follow the directions here for modifying uRamdisk http://xdaforums.com/showthread.php?p=49070213#post49070213
Reboot to a rooted Nook with ADB over USB access

kazem_aryan · Jan 25, 2014

Driver

Renate NST said:
A short recap of how to root the new NG2:

All of these methods use the Texas Instruments OMAP processor USB bootloader.

The desktop system that you connect the Nook to can be either Linux or Windows.
This only details the Windows method.

The bootloaded system can be either noogie or Clockwork Mod or a modified stock Nook.
For now, we are only using the noogie method.

The bootloading sequence can be either aboot, u-boot or x-loader, u-boot.
For now, we are only using the aboot, u-boot method.

Preparation
In Window, we need drivers to communicate with all USB devices.
You will need the drivers found in the Android SDK under google\extras\usb_driver
android_winusb.inf will need to be modified as in http://xdaforums.com/showpost.php?p=48596138&postcount=35

Booting
Collect the necessary files from the previous posts.
Fully power your Nook down with the USB disconnected.
Run this command on the PC.

Code:

omaplink.exe omap3_aboot.bin u-boot-ng2-130-stk.bin uImage-noogie uRamdisk-noogie

Plug the USB into the Nook.
Whenever a "New Device" popup appears manually select android_winusb.inf to be loaded then start this step over.
omaplink should get as far as "Waiting for ADB..."
It won't find it just yet, use ^C to exit.
At this point there should be a new removable disk mounted with a dozen files on it, including uRamdisk

Rooting
Follow the directions here for modifying uRamdisk http://xdaforums.com/showthread.php?p=49070213#post49070213
Reboot to a rooted Nook with ADB over USB access

Hi
in first step, i can't install driver! i tried in win xp sp3 & win 7
i can't find any location to find the driver
i try this locations :
G:\
<sdk>\extras\google\usb_driver\
google\extras\usb_driver
how can i download the INF driver file?! or have any other way to install the driver?!

tnx

Hacking the new Nook GlowLight

Member

Recognized Contributor / Inactive Recognized Dev

Member

Attachments

Recognized Contributor / Inactive Recognized Dev

Member

Recognized Contributor / Inactive Recognized Dev

Member

Recognized Contributor / Inactive Recognized Dev

Member

Recognized Contributor / Inactive Recognized Dev

Member

Recognized Contributor / Inactive Recognized Dev

Member

Recognized Contributor / Inactive Recognized Dev

Member

Attachments

Recognized Contributor / Inactive Recognized Dev

Senior Member

Member

Recognized Contributor / Inactive Recognized Dev

Attachments

Member

Similar threads

Top Liked Posts