Fix for bricked Glow2, 3, 4

Search This thread

Renate

Recognized Contributor / Inactive Recognized Dev
Well, I finally got it together and figured out how to use the ROM bootloader on the iMX6 Nooks (Glow2, 3, 4).
You can get into u-boot even with a trashed disk.
Of course, that may not be the end of your problems.
You may have to repair stuff.
Having a UART console wired up will certainly make things clearer/easier.

So, if you have a bricked Glow (that still bongs when you plug it into a computer),
I have a program for downloading the u-boot.
I can try to make a version of u-boot that goes straight into fastboot.

So, does anybody have a bricked Glow?

You can check in Device Manager (devmgmt.msc) if you can find:
Code:
Human Interface Device
USB Input Device
USB\VID_15A2&PID_0063
 
  • Like
Reactions: Kramar111

Renate

Recognized Contributor / Inactive Recognized Dev
Well, I've been playing around with all this.
I got a bit too arrogant playing around and swapping u-boots.
If you have a SBL (secondary bootloader, possibly u-boot) that looks good enough to the ROM bootloader
but doesn't actually work, you can sort of lock yourself out.
I had to disable (by grounding a test point) the eMMC to allow the ROM bootloader to run.
I've got to wiggle out and see if the boot options actually have their own test points.
I'm trying to get some more UARTs configured for GPS sensors.

The iMX6 bootloader is a known thing, but all the software out there seems half baked.
I tried one that was 7 Megs in size, but it didn't actually work.
My version weighs in at 68k, i.e. 1/100th the size.
 
  • Like
  • Love
Reactions: lal68 and Kramar111

Renate

Recognized Contributor / Inactive Recognized Dev
So, I've got a cleaned up version (available in the signature).
Code:
C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Idle

C:\>imxboot ub3
Load addr 87800400, DCD offset 002c, DCD size 0220
Found iMX6SL, VID=15a2, PID=0063
67 DCD ops processed
Write, addr 87800400, size 00039270
**********************************************************************************************************
Jumping to 87800400
Device disconnected correctly
 
  • Like
Reactions: Kramar111

companion79

Member
Dec 15, 2019
7
0
Hi.
I have bricked Glow 3.
I tried to restore the bootloader according to your instructions and I have a problem
Code:
C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Could not write device
 

Renate

Recognized Contributor / Inactive Recognized Dev
Code:
Could not write device
Hmm, strange.
Hold the reset button for 10 seconds. It should get a disconnect "bong".
Hold the reset button for 3 seconds. It should get a connect "bong".
Try imxboot by itself again.

It's strange because I have a separate error if the connection got disconnected.
I've been using imxboot alot myself on a Glow3 and never a problem.
 

companion79

Member
Dec 15, 2019
7
0
Hmm, strange.
Hold the reset button for 10 seconds. It should get a disconnect "bong".
Hold the reset button for 3 seconds. It should get a connect "bong".
Try imxboot by itself again.

It's strange because I have a separate error if the connection got disconnected.
I've been using imxboot alot myself on a Glow3 and never a problem.

Reset button on the book? Where is this button? Perhaps I do not understand, perhaps you need to connect through the UART module? I was connecting through the command line.
 

companion79

Member
Dec 15, 2019
7
0
So write about an attempt to restore bricked nook Glow3, now position here is such
Code:
C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Idle

C:\>imxboot ub3fb
Load addr 87800400, DCD offset 002c, DCD size 0220
Found iMX6SL, VID=15a2, PID=0063
67 DCD ops processed
Write, addr 87800400, size 00039270
**********************************************************************************************************
Jumping to 87800400
Could not read device

Now in Device Manager I find
Android ADB Interface:
USB\VID_18D1&PID_0D02&REV_0311
USB\VID_18D1&PID_0D02

I trying to run
Code:
C:\>adb reboot fastboot
error: no devices found

please help me what should I do next
 

Renate

Recognized Contributor / Inactive Recognized Dev
Now in Device Manager I find
Android ADB Interface:
USB\VID_18D1&PID_0D02&REV_0311
USB\VID_18D1&PID_0D02
Oops, sorry, my stupid. Fastboot uses its own bogus VID/PID.

You booted ub3fb, therefore you should be looking for fastboot, not ADB.
Windows handling of WinUSB drivers makes this all a bit obtuse.

Code:
 C:\>imxboot ub3fb
...
Jumped to ...
...
C:\>fastboot devices
12345678 fastboot
C:\>fastboot boot nnglow3.img
C:\>adb shell
# ls -l
 
  • Like
Reactions: Kramar111

companion79

Member
Dec 15, 2019
7
0
That's what I see now
Code:
 C:\>imxboot ub3fb
...
Jumped to ...
...
C:\>fastboot devices
???????????? fastboot
C:\>fastboot boot nnglow3.img
Sending
Booting
Finished.
C:\>adb shell
Error: no devices/emulators found
After that, the device in the Device Manager disappears and is not detected again, reboot again returns the device to its original state.
 

Renate

Recognized Contributor / Inactive Recognized Dev
After that, the device in the Device Manager disappears and is not detected again.
Ok, but if at this point you pull the USB connection does Windows make a "bong" that something has been disconnected?
If so, that means that you've got something there and that the problem could be drivers for the ADB.
If not, that could mean your hwcfg is badly broken.
 

egor_omsk

New member
Jan 3, 2020
4
0
Hi! In response to "imxboot ub3fb" the request writes "Could open file ub3fb". Where can I get this file? Please help!!!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Well, I've been playing around with all this.
    I got a bit too arrogant playing around and swapping u-boots.
    If you have a SBL (secondary bootloader, possibly u-boot) that looks good enough to the ROM bootloader
    but doesn't actually work, you can sort of lock yourself out.
    I had to disable (by grounding a test point) the eMMC to allow the ROM bootloader to run.
    I've got to wiggle out and see if the boot options actually have their own test points.
    I'm trying to get some more UARTs configured for GPS sensors.

    The iMX6 bootloader is a known thing, but all the software out there seems half baked.
    I tried one that was 7 Megs in size, but it didn't actually work.
    My version weighs in at 68k, i.e. 1/100th the size.
    1
    Well, I finally got it together and figured out how to use the ROM bootloader on the iMX6 Nooks (Glow2, 3, 4).
    You can get into u-boot even with a trashed disk.
    Of course, that may not be the end of your problems.
    You may have to repair stuff.
    Having a UART console wired up will certainly make things clearer/easier.

    So, if you have a bricked Glow (that still bongs when you plug it into a computer),
    I have a program for downloading the u-boot.
    I can try to make a version of u-boot that goes straight into fastboot.

    So, does anybody have a bricked Glow?

    You can check in Device Manager (devmgmt.msc) if you can find:
    Code:
    Human Interface Device
    USB Input Device
    USB\VID_15A2&PID_0063
    1
    So, I've got a cleaned up version (available in the signature).
    Code:
    C:\>imxboot
    Found iMX6SL, VID=15a2, PID=0063
    Security: Unlocked
    Status: Idle
    
    C:\>imxboot ub3
    Load addr 87800400, DCD offset 002c, DCD size 0220
    Found iMX6SL, VID=15a2, PID=0063
    67 DCD ops processed
    Write, addr 87800400, size 00039270
    **********************************************************************************************************
    Jumping to 87800400
    Device disconnected correctly
    1
    Now in Device Manager I find
    Android ADB Interface:
    USB\VID_18D1&PID_0D02&REV_0311
    USB\VID_18D1&PID_0D02
    Oops, sorry, my stupid. Fastboot uses its own bogus VID/PID.

    You booted ub3fb, therefore you should be looking for fastboot, not ADB.
    Windows handling of WinUSB drivers makes this all a bit obtuse.

    Code:
     C:\>imxboot ub3fb
    ...
    Jumped to ...
    ...
    C:\>fastboot devices
    12345678 fastboot
    C:\>fastboot boot nnglow3.img
    C:\>adb shell
    # ls -l
    1
    Where can I get this file?
    Mmm, it's attached.
    (It's the stock u-boot for the Glow3 with automatic jump to fastboot.)