FORUMS

Sunday Debate: How Can We Get a No-Compromise Phone?

Join us in a fun Sunday Debate on Compromises. Come with your opinions and … more

PSA: You Can Optimize Your Note 4’s Recents Menu & RAM

The Note 4 never had the fastest Recents Menu, and despite its 3GB of RAM, … more

XDA Picks: Best Apps of the Week (July 25 – Aug 1)

Apps are at the front and center of any smartphone experience, and with over a … more

Voices Of XDA: Orbiting The Earth With Android

Editor’s note: This week’s feature has been written by forum … more

Full Root for Nook Glowlight

185 posts
Thanks Meter: 178
 
By N00b-un-2, Senior Member on 20th August 2014, 05:06 AM
Post Reply Subscribe to Thread Email Thread
18th June 2015, 01:55 PM |#51  
Junior Member
Thanks Meter: 0
 
More
help
Hello guys,

I installed the drivers as in this tutorial, but i just cant run omap link, it says:
"0451:d00e, OMAP , pbi ok
Timeout reading ASIC id"

there is red indiciator by the "bootloader" , then the window closes after few seconds. What could be the problem ?
 
 
19th June 2015, 12:14 PM |#52  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Boston
Thanks Meter: 874
 
More
Oh, yeah, I just remembered how this all goes together...
The bootloader will only issue its ASIC ID once, upon connect.
The bootloader interface might be visible to your PC, but without the inital ASIC ID, it won't initiate anything.
To keep the handshaking all in sync always do things the following way:
  • Disconnect Nook from the USB
  • Full power down of Nook
  • Make sure that no ADB server is running (adb kill-server)
  • Start your omaplink command
  • Then plug the USB cable into the Nook
  • The Nook will awaken and the omaplink will do its stuff
22nd June 2015, 03:47 PM |#53  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Renate NST

Oh, yeah, I just remembered how this all goes together...
The bootloader will only issue its ASIC ID once, upon connect.
The bootloader interface might be visible to your PC, but without the inital ASIC ID, it won't initiate anything.
To keep the handshaking all in sync always do things the following way:

  • Disconnect Nook from the USB
  • Full power down of Nook
  • Make sure that no ADB server is running (adb kill-server)
  • Start your omaplink command
  • Then plug the USB cable into the Nook
  • The Nook will awaken and the omaplink will do its stuff

When I hit "omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie" in the CMD , this command isn't recognized, so i suppose my bootloader drivers wasn't installed correctly right ?
24th June 2015, 01:38 AM |#54  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Boston
Thanks Meter: 874
 
More
Quote:
Originally Posted by nedslark

... this command isn't recognized ...

Huh? Did you download omaplink.exe?
What do you mean "not recognized"?
What did it type out?
Can you just see if the executable is even there?
Code:
C:\>omaplink.exe /?
If your drivers are not installed, the sequence will stall somewhere.
Code:
C:\>omaplink.exe aboot.bin u-boot12.bin uRecImg uRecRam
Waiting for bootloader... 0451:D00E, OMAP3630, pbi, ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file aboot.bin, 3480 bytes... ok
Received a-boot response
Sending image file u-boot12.bin, 170572 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, 3621GOSSAMER, Android Fastboot, ok
product     3621GOSSAMER
version     0.5
Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect... ok
Waiting for ADB... 2080:0003, NOOK, ok
Version: 01000000, payload: 4096, type: recovery
uid=0(root) gid=0(root)
I wipe my USB registry often and I just had to reinstall the fastboot drivers to get the output from above.
24th June 2015, 04:13 AM |#55  
FerociousAndroid's Avatar
Senior Member
Thanks Meter: 20
 
More
Unhappy
Hello all,

Need a bit of help. I'm connected to my Nook GL via Wifi and at the Win7 (32bit) cmd prompt typing the follow commands and having some trouble. Not sure what I'm missing? Thx in advance.

C:\usbboot>adb install superuser.apk
272 KB/s (843503 bytes in 3.026s)
pkg: /data/local/tmp/superuser.a
Success
rm failed for -f, Read-only file system

C:\usbboot>adb shell mkdir -p /system/xbin
mkdir failed for -p, Read-only file system

EDIT:
Thanks geeyoff!
http://forum.xda-developers.com/show...8&postcount=28
Last edited by FerociousAndroid; 24th June 2015 at 04:42 AM.
24th June 2015, 01:09 PM |#56  
FerociousAndroid's Avatar
Senior Member
Thanks Meter: 20
 
More
Question ROOT and SU permanent?
Is there anyway to make the ROOT and SU permanent? I mean implanting the modified uRamdisk and superuser.apk and maybe a launcher like Smart Launcher 2 Free?
Last edited by FerociousAndroid; 24th June 2015 at 01:16 PM.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes