I was resizing partitions on my much loved original Nook Simple Touch and I accidently failed to set the "boot" flag on the first partition before restarting. Now the system does not boot, of course. If it won't boot to Android or CWM, then as far as I know, I can't ADB to it in order to set the boot flag. Is there any other way of getting access to the partitions in Windows or Linux that might work?
I searched a bit and see that some other people with partition errors on NSTs have used SD card booting tools like Noogie to fix their partitions, but the mSD slot on my Nook long ago failed and I actually desoldered it from the board since it was shorting. I could potentially buy a new slot component on eBay and try to solder it on, though I'm not so good at soldering and those solder pads look tiny. Would this work for me if I did it, thouh? Would I be able to boot Noogie and restore the BOOT partition even though there's no "boot" flag set at all? I do notice that very briefly "OMAP3630" appears in Windows Device Manager if I plug the Nook into my computer and hold the power button. Maybe that's a good sign?
Any advice would be helpful as I'd really like to get the system working again. I've been using this thing almost daily for 10 years and it's like an old friend to me. I don't think I would like a new reader nearly as much.
Yeah, I wrote a utility for this donkey years ago. It's omaplink.exe
It's in my sig, download it.
Then you need aboot.bin and u-boot12.bin
Then you need a boot image and a ramdisk image out of an update.
Code:
C:\>omaplink.exe aboot.bin u-boot12.bin boot.img ramdisk.img
You can issue the command, then reset the NST and hopefully it will all work out.
If it doesn't, copy/paste the text.
Hi Renate, I would be so happy if you could help me get this system working again!
Unfortunately, I get a message from omaplink.exe that says
Waiting for bootloader or Fastboot or ADB...
The omaplink window appears with a bunch of empty radio buttons. Clicking on it does nothing that I can tell.
If I hold power so that the OMAP3630 appears briefly in device manager, this doesn't seem to do anything either. This OMAP3630 device disappears from the Device Manager almost as soon as it shows up. For the second that it appears, the icon for that OMAP3630 device has an exclamation point anyway, so I think it means there's no drivers for it.
When you say "boot image," you mean a uImage file that normally goes in BOOT, right? and the ramdisk should be the uRamdisk file?
EDIT: I should add that the Nook itself has no activity on the screen at any time. It still shows the CWM menu with "reboot system now" highlighted just like it was when I restarted it after mmucking about with the partitions. Even if I hold the power button (and see the OMAP3630 device in Windows), the screen does not refresh, so it's just on that CWM screen indefinitely.
Yeah, the bootloader 0451/d00e needs a WinUSB device driver.
Use https://zadig.akeo.ie/
Show all devices and look for the 0451/d00e, install WinUSB.
You also need the Google driver for fastboot.
Code:
C:\>omaplink.exe aboot.bin u-boot12.bin uImage uRamdisk
Waiting for bootloader or Fastboot or ADB...
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...
Waiting for Fastboot or ADB...
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 2816000 bytes... ok
Waiting for disconnect...
Waiting for ADB...
Could not open device
(This could not open ADB because the ADB server was already running and it was using it.)
The Zadig tool does seem to have installed a driver. At least the OMAP3630 device now shows in "USB Devices" instead of "Other devices" anyway.
omaplink.exe still just sits with that same message, though. The OMAP3630 device still disappears from the Device Manager after about 1 second, so that seems like the issue. There's no time for omaplink.exe to do anything. It's not even clear that the driver loads before the device is gone. I think the system shuts down right away since holding the power button again will make it appear again in Device Manager pretty quickly.
Are you running omaplink before resetting? You should.
Does the red "LED" flash on reset?
Yes, I start omaplink first. I've tried launching it before plugging in the Nook as well as after plugging it in but before holding down the power button.
I'm not sure which "LED" you mean. On the Nook? The original NST doen't have any red LED that I know of. I've only ever seen it orange when charging or otherwise green. The light currently stays green whenever the USB cable is plugged in. No other colors.
To be clear about this, there's no missing files in the BOOT partition on my system. There's already u-boot, uImage, uRamdisk, and everything else already there. The issue is that the "boot" flag is not set for the partition, so the system doesn't even look at the partition when I start it up. If I can get it to recognize the system, will omaplink set the "boot" flag or does it just transfer these boot files?
The "LEDs" are the colored things on the popup, that you are calling radio buttons.
If you have some other devices, just type omaplink.exe and plug something in.
The ADB (or fastboot) "LED" should light and it should type stuff and exit.
No, this was all just getting something to boot.
I realize that the stuff in flash is ok, but it's going to be ignored.
Just to provide an ending here, I was never able to get omaplink to work with my bricked NST. Then I got the bright idea of just physically holding a microSD card with Noogie on it to the contacts where the card slot used to be. This almost worked and I got a screen refresh out of the system and some changed charging behavior, but then apparently I must have shorted something because now nothing happens at all no matter what I do. No OMAP3630 device in Device Manager, no charging lights, nothing. I think I truly killed the poor baby.
Oh well. I saw another original NST on eBay for $17, bought it, and have now rooted and restored an old backup to it. The fact is, this is a pleasant upgrade for the price since my old one was in pretty poor condition (worn battery, holes in the rubber above the buttons, scratches on the screen, the broken card slot, etc.) and this one I got is virtually new.
Here's to another 10 years of Simple Touching (hm...)!
Related
I don't have much time, this update annoyed the crap out of me.
And for what ever reason RadioComm did not work for me.
I'll try to give a rough step-by-step "cheat sheet" guide here.
This is by no means a real tutorial,...
But this got me back up and running so I can communicate with my Girl after and accidental upgrade which cost me my unlocked bootloader (I never did it yet)
I installed the drivers for all the tools like DFS, QPST, QDXM, etc long long ago, not sure where but I think the ones from this thread should work:
Drivers: http://forum.xda-developers.com/show...hlight=drivers
Direct link: http://forum.xda-developers.com/atta...1&d=1347903431
After installing the drivers, power off the phone, then hold power + volume up + volume down, and select "BP Tools" from the boot menu
(press volume down until it is highlighted, then press volume up)
Wait for the phone to boot, then plug it into the PC.
It should recognize it and install a new COM port and some other crap.
After installing the drivers, install DFS, I got it from this thread and it worked, you may get it somewhere else as well:
Setup DFS 4.7.0.2.zip from http://cdmatool.com/Download
(1) Make sure you still have the phone in BP Tools mode connected, and start DFS.
(4) Click on the "Ports" button, double click on the newly installed COM port (for me it's called "Motorola QC Diag Port"), close ports manager
(4a) Check: Make sure the port is selected in the drop down to the right of the "ports" button
(5) In the main window, select "Qualcomm" on the DM drop down
(6) click on SPC (leave code as 000000), make sure it says "DEVICE UNLOCKED" in the console at the bottom
(7) click on NV tab
(8) enter 8322 the "Start" field, and 8323 in the "End" field, then click "Read range"
(8a) Check: It should show only one item called ITEM_8322
(9) select the item ITEM_8322, type 00 replacing the 01 in the "Edit NV" box below
(10) click "Apply changes", then "Write selected item" (Make sure ITEM_8322 is Highligted Blue and also 00 is highligted)
(10a) Check: repeat step 8 and verify it now reads 00 (Else repeat 8-10 steps, it may take 1-4 tries)
(11) reboot and cross fingers.
Lets hope I didn't miss any steps, but hopefully this helps people that cant get RadioComm to work.
Also this method allows you to do the steps with out rebooting. until it sticks.
Disclaimer: I am not responsible for any damage you might do to your phone, or any other undesirable consequence, as a result of following these instructions.
Hey guys. So I picked up a NST and it has a few issues.
It will not charge (green light stays on), it is stuck on a lock screen with the "push N to wake up your Nook, will not turn on, and looks for OMAP 3630 drivers when I plug it into my usb cable.
It has already been taken apart and the battery removed. That didn't fix it, nor did the countless ways of resetting it.
I believe that this might be due to a failed root or corrupt partition table. Would anyone be able to help me fix this if I am not able to actually turn it on? I would also prefer not to use Linux if I don't have to. Any help would be appreciated. Thanks!
You can try booting it with an SD card, noogie or ClockworkMod Recovery.
You could also do USB booting of an image.
That could be a bit more effort setting it up.
Start reading here: http://forum.xda-developers.com/showthread.php?t=2559915&page=39
Renate NST said:
You can try booting it with an SD card, noogie or ClockworkMod Recovery.
You could also do USB booting of an image.
That could be a bit more effort setting it up.
Start reading here: http://forum.xda-developers.com/showthread.php?t=2559915&page=39
Click to expand...
Click to collapse
Would it boot even if the NST doesn't turn on? I'd assume that would pose a major problem with anything I try.
The problem with eInk is never knowing what it's doing.
You said that an OMAP3630 USB interface pops up, so it's not dead.
Put something on an SD card and see if it boots.
Yeah, will do.
What's odd is that is connects and disconnects the usb every three or so seconds. I can hear the unplug/plug windows alert. It looks like a bootloader issue more than anything. I was going to try the CWM method first.
Edit: So I tried Clockwork and Noogie. Neither work as the device cannot reboot or even turn on. I need to plug it into the micro USB cable for it to even turn one. When it was connected to my computer, it still tries mounting/ejecting every few seconds.
It could be that it thinks that the power is not good.
Try booting an SD card with a charger plugged in.
If this doesn't work, try taking it apart and disconnecting the battery.
If you had a kernel console connected (requires soldering) you could see what it doesn't like.
The only way I can boot it is with it being plugged in., also I've already tried booting it without the battery to no avail. This nook is quite stubborn :/
It needs the battery connected in any case.
u-boot.bin is quite strict about requiring a battery.
I meant disconnect and reconnect the battery.
Are you saying that it boots now?
Oh, in that case I did do so.
No, it does not appear to boot. What I meant was that when i connect it to my computer, it shows a green light, I hear the usb mounting noise on my computer, the LED flashes orange for a split second, and then I hear it unmount. I would assume that it's trying to boot, but can't. The screen still shows the same picture.
The screen is a higher-level function.
You won't get anything to change until the system is pretty happy.
We have no information here to go on.
We can't tell what it's doing.
You've already disconnected/reconnected the battery.
You can try the USB booting as listed above and see how far it gets.
You can solder in a level converter to UART1 and see what's going on.
That's about it.
Alright, I'll just assume it's a list cause. Thanks for the help.
You've charged it overnight and tried to boot it (30 seconds on the power button) with the charger still connected and a good noogie image on an SD card?
Can you check the voltage on the battery?
I'd go through the whole deal with the USB image booting and see if you can get anything working.
Usb image booting might work, but it looks like I'd need Linux, and I have no spare boxes left. Cant find a way to do it in windows.
I'll try charging it overnight, but i already tried changing it for about 5 hours
gustan said:
Usb image booting might work, but it looks like I'd need Linux, and I have no spare boxes left. Cant find a way to do it in windows.
Click to expand...
Click to collapse
There's an entire solution for Windows in that thread.
It uses omaplink.exe, to be found in the signature.
Start reading about here:
http://forum.xda-developers.com/showthread.php?p=49665945#post49665945
http://forum.xda-developers.com/showthread.php?p=50740002&#post50740002
I tried charging it overnight and booting with Noogie. No luck there.
I also tried the Omap usb boot. But when I try to run that from cmd with the proper location of the file/syntax, I receive this message.
http://forum.xda-developers.com/attachment.php?attachmentid=2847676&stc=1&d=1405182337
I cannot also follow the guide as the device doesn't prompt a driver install. I get this to show up as the Nook under my device manager, but it disappears after a second or two so I am unable to install drivers as stated in the guide.
http://forum.xda-developers.com/attachment.php?attachmentid=2847677&stc=1&d=1405182337
Edit: I was able to install it an it is now recognized as an "Android Bootloader Interface"
So I got it working finally.
In the OMAP Link, I have the bootloader flash red and then go back to grey. Here is a cap of what it looks like.
http://forum.xda-developers.com/attachment.php?attachmentid=2847705&stc=1&d=1405183421
http://forum.xda-developers.com/attachment.php?attachmentid=2847714&stc=1&d=1405183942
There could be three reasons why you don't get the yellow FastBoot indicator.
1) Your files you are loading could be the wrong ones. aboot.bin & u-boot12.bin are correct (check sizes).
2) u-boot does not like the state of your power system.
3) You don't have the drivers for FastBoot loaded.
When it stalls waiting for fastboot check the Device Manager for unhappy new devices.
If it asks you for any driver select specifically the driver out of the unzipped drivers in the first link above.
Here's what I use to boot into ClockworkMod Recovery:
Code:
C:\C\OmapLink>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've been wanting to patch a u-boot to make it work even without a battery.
That would be a good test for people with battery problems.
(The stock Android would still raise a stink, but noogie & CWM should work.)
Renate NST said:
There could be three reasons why you don't get the yellow FastBoot indicator.
1) Your files you are loading could be the wrong ones. aboot.bin & u-boot12.bin are correct (check sizes).
2) u-boot does not like the state of your power system.
3) You don't have the drivers for FastBoot loaded.
Click to expand...
Click to collapse
1) would I get the files from the link in the zip?
2) How would I fix that? Seems like a hardware issue in this case.
3) Wouldn't the drivers load with Noogie? Or are they from my computer.
After installing the reccomended drivers, the device doesnt show up as Omap 3630 anymore.
I've lost track of where the files are in that thread.
I did link directly to the aboot.bin (as a zip).
The Windows driver (which I linked above) is for all three device presentations, bootloader, FastBoot, ADB.
Yes, it could be a battery/hardware problem but we don't know that yet.
Okay, so I found your aboot.bin. I also read that I should be using uBoot-12.bin instead of 13. I looked around but was unable to find it.
usbboot-ng2-aboot-noogie-images-v01.zip is what I'm using for most of the .bin, but I'm using the new aboot.bin.
This was gotten off of:
http://forum.xda-developers.com/showpost.php?p=49779966&postcount=285
The aboot.bin was taken off of this page that you had sent me to:
http://forum.xda-developers.com/showthread.php?p=50740002&#post50740002
It doesn't have a yellow yield sign on the device anymore either. Instead it shows up as:
http://forum.xda-developers.com/attachment.php?attachmentid=2848218&stc=1&d=1405215211
Hello everyone. Here's my story
I've been using CM13. After installing their OTA update it ruined my android. So I downloaded new cm13 rom, wiped everything, accidentally clicked reboot (without flashing new rom) and it was over (At least I think this happened, it was some time ago and I'm already trying to fix this for a long).
I am stuck in LG logo. Can't access recovery (I've had this issue before. Could get to recovery only by command from adb).
I can get to Download mode. But PC can't see my device. Tried several PC's, windows, ubuntu. I flashed other phones with this method, only G2 is not visible. I'm doing here everything fine.
Also I tried this:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Success but my phone keeps flashing on and off. I've got access to partitions like every 5 seconds and only for a second. I think I managed to flash those 3 partitions, but there's no difference, pc still can't see phone when in download mode.
Should I trow it to the ocean?
Keep it
Here is my story
Bricked my device (d802) with your stuation no recovey no download mode
My phone's partition table deleted any way, tried wire method which you've already tried
Tried several times and release this wire method put in 2 seperate modes
Found the mode it shows in ubuntu a sda block (with several tries with wire method)
I've got full 32 gig backup, thats my advantage between your stuation
In ubuntu fdisk - l shows all disk and shows my phone as a disk but no information about disk or partitions etc. only sda block
In the end pushed the 32 gig backup with dd if=/(path of my backup) of=/dev/block/sd* bs=4k
Wait some time until process done (30-45 minutes I guess)
Thats all, phone boots normally everything is fine
If you're using 32 gig version I can send you my backup (with imei deleted) so you can boot your device and install kdz
Or I can show you how to backup another LG phone and recover from that backup. http://forum.xda-developers.com/lg-g2/general/how-to-backup-data-16-gb-32-gb-size-t3236558
Thank you for your reply lynxrz
I've got bigger problem. When I enter qhsusb mode, backlight of my screen keeps switching on and off every 3-4 seconds. I can see partition only for a second.
Vergil333 said:
Thank you for your reply lynxrz
I've got bigger problem. When I enter qhsusb mode, backlight of my screen keeps switching on and off every 3-4 seconds. I can see partition only for a second.
Click to expand...
Click to collapse
Not necesaary to see partitions
In ubuntu or any linux enviroment open up a teeminal emulator and "sudo fdisk -l" and it will be like that;
Code:
$ sudo fdisk -l
Disk /dev/sda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00008ec7
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1013 8136891 8e Linux LVM
/dev/sda2 1014 1044 249007+ 5 Extended
/dev/sda5 1014 1044 248976 83 Linux
sda sdb sdc means a phisicial disk. sda1 sda2 sda3 means partitions of "sda" disk. My process depends on overwriting sda disk not partitions, so you don't need to see partitions
Just type "sudo fdisk -l" and tell me you can see any sdb sdc phisical disk permenately. We must know connection can be dropped or not(it can be bootloop). Partitions might disappear but phisical disk have to be there. Look for it.
If you can't see in qhsusb mode try another mode, this is the lucky part of tring the wire method. I don't know exactly how to swich "another" mode but you can detect in window device manager, then switch to linux (Don't be afraid to losing this mode it stays when you plug off usb if you connected battery)
Sorry I don't remember that "another" mode's name but it is exists
Firstly you need to know qhsusb mode can see a "phisical" disc or not?
I'm in work now, but I tried this yesterday.
Phone appears as sdc when I typed
Code:
$ ls /dev/sd*
while in qhsusb mode. (I had to type it several times repeatedly to catch the right moment)
I can get to download mode, so I typed
Code:
$ sudo fdisk -l
and couldn't see sdc there.
Vergil333 said:
I'm in work now, but I tried this yesterday.
Phone appears as sdc when I typed
Code:
$ ls /dev/sd*
while in qhsusb mode. (I had to type it several times repeatedly to catch the right moment)
Click to expand...
Click to collapse
Probably it can be bootloop.
Did you plug off the battery when touching capacitor ? Just asking to be sure.
Sure, I unplugged the battery So qhsusb not stable and download mod not visible to computers.
I already gave up of hope
Ok I will solve how to enter "another" mode (not qhsusb)
But I need time to backup all my data in any case
If I solve, prepare a backup for you and it'll be 32 GB
Edit: Can not find out "another" mode because of data cable problem (severed usb cable charging but not transferring data) You're on your own now to find another usb mode, It can be the "holding time" of cable on capacitor.
Good luck with that
Prepairing your backup with otg
Really thanks for your help lynxrz. I appreciate all effort
Vergil333 said:
Really thanks for your help lynxrz. I appreciate all effort
Click to expand...
Click to collapse
You're welcome
PS: Did I send pm the download link?
You did. 29.1GB rar file. I have no use for it till I find another mode to be able to flash partition.
I already bought G3. Probably I will sell G2 for parts
Uploading now and it was %17 maybe tomorrow will be uploaded %100
20,4 GB and compressed seperated 1 GB rar parts (21 parts)
Realised by you broken usb, I'll solder it but no time for that now, 2 days later I'll try it.
I'm stuborn as hell with that Just wait we'll fix it don't sell
Maybe I can make a tutorial and help the others
UPDATE: Usb works I'll try it tomorrow
I installed relaunchx and rooted the device sucessfully. It was running okay. I set the home button to restart in relaunch rather than the nook software. I rebooted and all it would do is go to the front-screen with the nook barnes and noble logo on the front. I could turn it on and off, but that was it. It charged. I tried to start packages on the device via adb but it said the system wasn't running. I could see processes system processes with ps.
I issued a reboot recovery command via adb. The Nook finally responded with something other than a reboot and it went into recovery and did a full factory reset. I thought I was in the clear. But no. It rebooted and went back to the logo screen as before. However, now I no longer have adb access.This might be because the factory reset turned off usb debugging. So now I can't access the device at all. Does anyone have any ideas how I might be able to proceed? I think the device is functional, but the bootloader is damaged somehow so I can't start Android on the device. Without adb access, I think it's effectively gone.
It's likely that you don't have any home application working.
Or maybe it's completely borked.
Have you tried holding various buttons on a power up to see if you can try recovery again?
The next worst case is just using the hardware console connection (inside the case) to see if you have a shell and what's going on.
For the old NST we had a whole setup to boot over USB even with a totally wiped out flash.
That hasn't been looked at for the newer iMX6 (vs OMAP) Nooks.
Hi,
Renate NST said:
For the old NST we had a whole setup to boot over USB even with a totally wiped out flash.
That hasn't been looked at for the newer iMX6 (vs OMAP) Nooks.
Click to expand...
Click to collapse
I tried to manually root using https://forum.xda-developers.com/showpost.php?p=76496894&postcount=13, replicating commands on Linux, and I totally bricked my Nook - probably bad repacking on boot image.
Code:
[884213.478979] usb 3-3: new high-speed USB device number 123 using xhci_hcd
[884213.607636] usb 3-3: New USB device found, idVendor=15a2, idProduct=0063
[884213.607642] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[884213.607645] usb 3-3: Product: SE Blank MEGREZ
[884213.607648] usb 3-3: Manufacturer: Freescale SemiConductor Inc
[884213.609540] hid-generic 0003:15A2:0063.000C: hiddev0,hidraw0: USB HID v1.10 Device [Freescale SemiConductor
Inc SE Blank MEGREZ] on usb-0000:00:14.0-3/input0
Can you point me to NST setup to recover over USB, I would spend some time to try to recover my Nook.
Thank you!
If you had just wiped out P1 you should still have recovery (on P2) just fine.
Do a restart holding the Home button down.
If this doesn't work you somehow managed to wipe the bootloader.
To get the USB HID bootloader to work would be a bit of a project.
There is the starting point of this tool: https://github.com/boundarydevices/imx_usb_loader
Anything that is written about USB recovery on the NST (which uses OMAP) has nothing to do with the new Glows (iMX6SL).
Hmmm, the Kindle Paper White 2 seems to have the same processor/ROM bootloader...
For what it's worth, here is an overview of the low-level MMC:
Code:
Name 32kB units 512B sectors Byte addresses /dev/block
Start End Start Size Start End
---------- ----- --- ----- ----- ------- ------- ----------
mbr 0 1 0 1FF
sn 1 1 200 3FF
bootloader 2 1022 400 7FFFF
hwcfg 1024 2 80000 803FF
ntxfw 1030 256 80C00 A0BFF
bootenv 1536 510 C0000 FFBFF
boot 33 223 2048 12224 100000 6F7FFF mmcblk0p1
waveform 225 544 14336 20480 700000 10FFFFF
logo 545 608 34816 4096 1100000 12FFFFF
recovery 609 1632 38912 65536 1300000 32FFFFF mmcblk0p2
Renate NST said:
If you had just wiped out P1 you should still have recovery (on P2) just fine.
Do a restart holding the Home button down.
If this doesn't work you somehow managed to wipe the bootloader.
Click to expand...
Click to collapse
I was lucky!
Restart holding the Home button down made no difference.
Trying randomly, I observed restart holding the Home and Right Up buttons goes into fastboot.
I recovered P1 partition for which I had backup and my Nook is live again.
Many thanks!!!
imx_usb_loader would have taken some time to learn.
So you're stuck in the ROM USB bootloader?
To look into a solution I had to get the ROM USB bootloader to run on my Nook to test things.
I didn't feel like bricking the Nook, so that was out.
I disassembled the ROM bootloader and found the correct, erm, workable entry point in the ROM.
Code:
eBR-1A # go [i]<entry address>[/i]
Code:
iManufacturer: 0x01
0x0409: "Freescale SemiConductor Inc "
iProduct: 0x02
0x0409: "SE Blank MEGREZ"
So now I can play around with the ROM USB bootloader.
Renate NST said:
So you're stuck in the ROM USB bootloader?
Click to expand...
Click to collapse
No.
After fastboot got enabled I booted nnglow3.img and then I recovered P1 partition with dd.
My Nook is like new
Thanks,
C
cipibad said:
No.
After fastboot got enabled I booted nnglow3.img and then I recovered P1 partition with dd.
My Nook is like new
Thanks,
C
Click to expand...
Click to collapse
I'm having the same issue as yours, could you please help me to unbrick my device?
I'm a newbie to technology so please help me step by step
Hi there,
Having recently acquired a very cheap and almost new Nook Simple Touch with Glowlight, I have been searching around the XDA forum collecting together as much information as I can easily find about the device and what it runs.
It is clear to me that development on the device has long since become almost abandoned here, many a year ago.
Upon reaching out here regarding my Nook rooting and customisation desires, @nmyshkin has without fail replied and been active and supportive, and with their help I have succeeded in fully converting my unsupported UK Nook into a (somewhat).supported US nook with UK localisation, newer firmware and full root and customisation.
I am now looking to start building proper step by step detailed guides, and a central list of resources available for the Nook Simple Touch / Glowlight, essentially a one stop shop for the majority of the available resources. This post may be edited to be that very thing, or at least link to it.
I am aware of the limitations of CPU and RAM on the device, however this does not out me off nor make me consider the device obsolete. I think there's plenty of room for improvement since the most exciting developments happened almost a decade ago now!
I hope you don't mind the mention, @Renate, as I have seen myself across the forum and in general discussion with @nmyshkin that you seem to be knowledgeable in this and other devices. Do you (,or anyone else) happen to have any answers to the following questions and requests which might assist in my development and learning endeavours:
Any known-good US or UK GPL sources for any NST/G firmware, preferably 1.2.2 or worst case 1.2.1?
Information about board pinouts, voltages? I am aware UART exists, maybe JTAG does on the same connector? Do you know what connector is on the board?
Known hardware names for Linux for things like the infrared touch sensor and EInk panel?
Is there a known way to completely wipe the entirety of the device (after a full byte by byte backup) and restore it to a fully functional state? By full I mean wiping/blanking onboard flash entirely, to the point the bootloader likely wouldn't start (unless it is in a separate chip? See next questions) and SD boot into CWM wouldn't work?
Is the ROM calibration, serial and MAC etc data stored in strictly read-only memory which couldn't be erased by tinkering or does it reside in normal flash?
Is the bootloader in a separate storage device or ROM, protected from tinker erasure?
Is factory.zip in a separate storage device or ROM, protected from tinker erasure?
Sources or binaries for custom community kernels, important augmentation APKs (like USB audio, mod manager etc) and add-on patches like FastMode/2, NoRefesh, USB Audio, Multitouch etc?
If there are any more questions, I shall ask them as a reply to this thread then append them also to this top post.
Thank you for reading and your time in advance!
alexhorner said:
Any known-good US or UK GPL sources for any NST/G firmware, preferably 1.2.2 or worst case 1.2.1?
Click to expand...
Click to collapse
Dunno. I doubt it.
alexhorner said:
Information about board pinouts, voltages? I am aware UART exists, maybe JTAG does on the same connector? Do you know what connector is on the board?
Click to expand...
Click to collapse
See attachment.
alexhorner said:
Known hardware names for Linux for things like the infrared touch sensor and EInk panel?
Click to expand...
Click to collapse
/dev/graphics/fb0, but you can't just write to it and expect results. Touch = /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/ledlevel See my Touch-1.0.apk for diagnostics.
alexhorner said:
Is there a known way to completely wipe the entirety of the device (after a full byte by byte backup) and restore it to a fully functional state? By full I mean wiping/blanking onboard flash entirely, to the point the bootloader likely wouldn't start (unless it is in a separate chip? See next questions) and SD boot into CWM wouldn't work?
Is the bootloader in a separate storage device or ROM, protected from tinker erasure?
Click to expand...
Click to collapse
The ROM bootloader always appears briefly, you can always boot an external image with corrupt flash. Look for the very long thread on my OmapLink.exe
alexhorner said:
Is the ROM calibration, serial and MAC etc data stored in strictly read-only memory which couldn't be erased by tinkering or does it reside in normal flash?
Click to expand...
Click to collapse
/dev/block/mmcblk0p2 = /rom
alexhorner said:
Is factory.zip in a separate storage device or ROM, protected from tinker erasure?
Click to expand...
Click to collapse
It's just a file somewhere.
alexhorner said:
Sources or binaries for custom community kernels, important augmentation APKs (like USB audio, mod manager etc) and add-on patches like FastMode/2, NoRefesh, USB Audio, Multitouch etc?
Click to expand...
Click to collapse
Yeah, they're around. Host USB was always problematical but it can be done if you really like.
HI Renate,
Dunno. I doubt it.
Click to expand...
Click to collapse
No worries, I'm scavenging what I can around and also I bugged BN over email. I know others have before me and success varies but it never hurts to try.
See attachment.
Click to expand...
Click to collapse
Wow, thats perfect, thanks! Do you know what connector type (which would've been soldered to the board) each pinout uses? I doubt theres any way to tell but like usual, worth the ask.
/dev/graphics/fb0, but you can't just write to it and expect results. Touch = /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/ledlevel See my Touch-1.0.apk for diagnostics.
Click to expand...
Click to collapse
That infrared one is certainly interesting, hmm. More research and fiddling required I think.
The ROM bootloader always appears briefly, you can always boot an external image with corrupt flash. Look for the very long thread on my OmapLink.exe
Click to expand...
Click to collapse
Okay now this is pretty damn neat. I only briefly looked at OmapLink.exe last night, but from my understanding, the ROM bootloader is not U-Boot, but instead the Nook's (or rather TI's) permenantly chip-burned first stage bootloader which then loads U-Boot? If this is correct, thats a pretty major win for ease of recovery, impossible to break. Completely corrupt flash recovery is super handy.
I take it from my brief reading OmapLink.exe (or rather, what it talks to) is a very hardware-level permenantly chip-burned board management/recovery tool too, again safe from being messed up and great for recovery?
/dev/block/mmcblk0p2 = /rom
Click to expand...
Click to collapse
Ah, block 0 partition 2? Technically not ROM but overwritable flash memory then I guess... Doesn't matter if I take a full backup before tinkering though I suppose!
It's just a file somewhere.
Click to expand...
Click to collapse
Very much like the not-so-readonly ROM then I would guess.
Yeah, they're around. Host USB was always problematical but it can be done if you really like.
Click to expand...
Click to collapse
I do indeed have the kernels from various forum threads, but the sources, even for individual pathes like FastMode/2, elude me unfortunately, which makes creating new and full featured kernels harder than I am capable of tackling sadly.
Thank you for your responses, they are of great help!
Update on omaplink.exe
So, the whole Windows driver thing. It sucks. A lot. Especially on Windows 10. But I found a much easier method of installing the drivers than the one shown in https://forum.xda-developers.com/t/full-root-for-nook-glowlight.2853056/ but still having trouble
We know the hardware IDs of the Nook are 0451 d00e
I downloaded a tool called USBDeview from https://www.nirsoft.net/utils/usb_devices_view.html, which allows you to list connected and disconnected USB devices on your system. Searching for 0451 finds the (disconnected) bootloader device the Nook presents itself as when connected.
Right clicking on the device allowed me to open its properties. I then have to select Change Settings and confirm administrative request:
Now I can go to Driver and install the BN USB drivers as linked in the original post (I reattached them here for convenience sake)
Except, Windows doesn't allow the driver as it is unsigned. Okay. Close all windows, open Start, open the Power menu and hold shift and click reboot. In the startup menu continue through troubleshooting and then get to startup options and choose option 7 disable driver verification.
Boot back up, do the whole USBDeview dance again, install the driver. Windows is happy.
Except, opamlink.exe is not.
When I start it up for Noogie using the instructions in the post, it starts up and waits perfectly fine. I shut the Nook down, wait a few seconds and reconnect it. Windows reports it malfunctioned (this seems to always happen before the bootloader shows up) disconnect sound, reconnect sound, and then opamlink.exe ignores it completely.
Nook continues to boot stock OS, at which point opamlink.exe sees it and does something, but its too late, we don't get access to the boot partition.
I am certain the bootloader appears at some point after the USB malfunction issue, otherwise Windows would not detect it for it to be listed in USBDeview and allow me to successfully install the driver.
Not to sure how to proceed with that one. I will test on another machine maybe running an older Windows and report back.
It would be nice if there was a Linux process for this. I'd love to make a Live CD for it.
alexhorner said:
Do you know what connector type?
Click to expand...
Click to collapse
It's just a 10 pin 1mm SMD connector. The "ears" on different models don't match but you don't have to solder the ears.
I think that at the time SparkFun happened to sell both connectors and pre-made pigtails, but they don't seem to now.
Yeah, there is a brief period of time for you to latch onto the OMAP ROM bootloader and if Windows is being stupid with drivers it will fail.
I'm not sure if there are some settings to make it less stupid, maybe not scratch its head so much on new devices.
Zadig is another generic WinUSB driver generator.
Renate said:
It's just a 10 pin 1mm SMD connector. The "ears" on different models don't match but you don't have to solder the ears.
I think that at the time SparkFun happened to sell both connectors and pre-made pigtails, but they don't seem to now.
Yeah, there is a brief period of time for you to latch onto the OMAP ROM bootloader and if Windows is being stupid with drivers it will fail.
I'm not sure if there are some settings to make it less stupid, maybe not scratch its head so much on new devices.
Zadig is another generic WinUSB driver generator.
Click to expand...
Click to collapse
Thank you, I'll see if I can get some pigtail leads.
I take it with my other questions, since you have no corrections, my assumptions about your previous answers were correct?
Update again on omaplink.exe:
Windows 10 doesn't seem to like it at all. Or rather, the driver. I installed Windows 7 on a spare machine and I have made some great progress.
Didn't manage to install it with Device Manager - its way too quick! But I used my USBDeview method and that worked perfectly.
omaplink.exe was able to see the device and then transfer omap3.bin to it, received an a-boot response, send u-boot-ng2-exp-v03.bin to it and then the device disconnected.
It didn't got any further than that though unfortunately. Noogie doesn't appear to have started up, for no further interaction has occured between the PC and the Nook, and the Nook remains on its powered off screen. Replugging makes no difference. Holding the power button brings it back to life making it boot into the normal OS.
Also, a question about omaplink.exe - Is it open source / is there a Linux version?
Thanks again!
Edit: In this post you mention that the ROM bootloader checks the SD card. Do you mean the second level UBoot bootloader or the first level, unmodifiable TI bootloader?
Thanks!
With Device Manager > View > Show Hidden Devices, you can check/replace drivers for things that aren't currently visible.
UsbLog.exe (under my sig, up and in the Windows section) will show things popping up.
Likewise EnumUsb.exe does a dump of what has been seen and date of first appearance.
alexhorner said:
omaplink.exe was able to see the device and then transfer omap3.bin to it, received an a-boot response, send u-boot-ng2-exp-v03.bin to it and then the device disconnected.
Click to expand...
Click to collapse
Well, that's what it's supposed to do. That's why it says, "Waiting for disconnect". Do you have drivers for fastboot installed?
It works fine for me:
Code:
C:\>omaplink.exe aboot.bin u-boot12.bin RecImg RecRam
Waiting for bootloader or Fastboot or ADB...
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...
Waiting for Fastboot or ADB...
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect...
Waiting for ADB...
ADB version: 01000000, payload: 4096, type: recovery
uid=0(root) gid=0(root)
Renate said:
With Device Manager > View > Show Hidden Devices, you can check/replace drivers for things that aren't currently visible.
UsbLog.exe (under my sig, up and in the Windows section) will show things popping up.
Likewise EnumUsb.exe does a dump of what has been seen and date of first appearance.
Well, that's what it's supposed to do. That's why it says, "Waiting for disconnect". Do you have drivers for fastboot installed?
It works fine for me:
Code:
C:\>omaplink.exe aboot.bin u-boot12.bin RecImg RecRam
Waiting for bootloader or Fastboot or ADB...
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...
Waiting for Fastboot or ADB...
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect...
Waiting for ADB...
ADB version: 01000000, payload: 4096, type: recovery
uid=0(root) gid=0(root)
Click to expand...
Click to collapse
Indeed, I understand it is meant to disconnect, however it also doesn't reconnect and allow me to access the files.
I should have fastboot installed? I believe having the Android SDK should be enough for that, right? I have the SDK and also Studio installed already. I use it's ADB installation for ADB stuff, having added it to my path.
Apologies for my uncertainty, I am new to Android stuff in general, I'm more used to native Linux stuff. Thats why having so many recovery options is quite exciting and good for learning for me - I can tinker with it as much as I like without needing to mess with JTAG unlike other embedded devices.
Your output seems pretty close to mine so I assume that bit is working fine. Drivers seem to be installed fine now considering opamlink.exe is able to see the device?
USBDeview helped me there with installing drivers on a disconnected device by VID/PID, I was unable to locate the device in Device Manager even with hidden devices enabled - though it probably does not help I have so many disconnected devices on my system making it hard to find anyway.
Further tried omaplink with another win 10 machine, it won't have it sadly.
Going to try another win 7 machine tomorrow.
Renate said:
Do you have drivers for fastboot installed?
Click to expand...
Click to collapse
Based on this android developers page, fastboot is present, so I'd say yes unless you have anything on the contrary
A little more success with the second Windows 7 machine.
omaplink worked fine again, and this time after it ran, I got a new device connected 0451:CAFE instead of 0451\00E
No drives show up however. Maybe the copy of Noogie I have is incompatible? Not sure if thats possible.
Still noo luck with Windows 10... hmmm
Spoiler: Log of omaplink
omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie
Waiting for bootloader or Fastboot or ADB...
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 omap3_aboot.bin, 3480 bytes... ok
Received a-boot response
Sending image file u-boot-ng2-exp-v03.bin, 175048 bytes... ok
Waiting for disconnect...
Waiting for Fastboot or ADB...