FORUMS
Remove All Ads from XDA

Wink Hub root

45 posts
Thanks Meter: 29
 
By FreeFly, Member on 10th December 2014, 09:47 PM
Post Reply Email Thread
3rd September 2018, 07:16 PM |#301  
Senior Member
Thanks Meter: 23
 
More
My followed the Pin 29 ground method and got the uboot prompt on Wink Hub Gen 1. I set up init /bin/sh, and booted the hub. Unfortunately, i receive the following error on bootup.

Code:
IFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   75550720 bytes (73780 KiB, 72 MiB, 595 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:11.
Freeing init memory: 124K
UBIFS error (pid 952): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 952): ubifs_read_node: bad node at LEB 213:64680
UBIFS error (pid 952): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 952): ubifs_read_node: bad node at LEB 213:76288
can't run '/bin/mount': Invalid argument
UBIFS error (pid 1): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 1): ubifs_read_node: bad node at LEB 213:67680
UBIFS error (pid 1): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 1): ubifs_read_node: bad node at LEB 213:67680
UBIFS error (pid 1): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 1): ubifs_read_node: bad node at LEB 213:67680
UBIFS error (pid 1): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 1): ubifs_read_node: bad node at LEB 213:67680
UBIFS error (pid 1): ubifs_read_node: bad node type (

Boot ROM Geometry
-----------------
Boot Area Count            : 1
Boot Area Size in Bytes    : 3145728 (0x300000)
Stride Size in Pages       : 64
Search Area Stride Exponent: 2
Scanning device for bad blocks
Bad eraseblock 280 at 0x000002300000
Bad eraseblock 281 at 0x000002320000
Bad eraseblock 282 at 0x000002340000
Bad eraseblock 283 at 0x000002360000
Bad eraseblock 288 at 0x000002400000
Bad eraseblock 289 at 0x000002420000
Bad eraseblock 290 at 0x000002440000
Bad eraseblock 291 at 0x000002460000
Bad eraseblock 296 at 0x000002500000
Bad eraseblock 297 at 0x000002520000
Bad eraseblock 298 at 0x000002540000
Bad eraseblock 299 at 0x000002560000
Bad eraseblock 304 at 0x000002600000
Bad eraseblock 305 at 0x000002620000
Bad eraseblock 306 at 0x000002640000
Bad eraseblock 331 at 0x000002960000
Bad eraseblock 339 at 0x000002a60000
Boot area protection is enabled.
Creating 6 MTD partitions on "gpmi-nfc-main":
0x000000000000-0x000000300000 : "gpmi-nfc-0-boot"
0x000000300000-0x000000700000 : "updater-kernel"
0x000000700000-0x000002300000 : "updater-rootfs"
0x000002300000-0x000002b00000 : "database"
0x000002b00000-0x000003300000 : "app-kernel"
0x000003300000-0x000008000000 : "gpmi-nfc-general-use"
cmdlinepart partition parsing not available
UBI: attaching mtd5 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd5 to ubi0
UBI: MTD device name:            "gpmi-nfc-general-use"
UBI: MTD device size:            77 MiB
UBI: number of good PEBs:        616
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 616
UBI: number of PEBs reserved for bad PEB handling: 6
UBI: max/mean erase counter: 68/48
UBI: image sequence number: 1024843640
UBI: background thread "ubi_bgt0d" started, PID 922
 ubiblka: unknown partition table
mice: PS/2 mouse device common for all mice
MXS RTC driver v1.0 hardware v2.3.0
mxs-rtc mxs-rtc.0: rtc core: registered mxs-rtc as rtc0
mxs watchdog: initialized, heartbeat 19 sec
mxs-mmc: MXS SSP Controller MMC Interface driver
__mxs_reset_block(f0010000): timeout when resetting
__mxs_reset_block(f0010000): timeout when resetting
mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96 
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
lib80211: common routines for IEEE802.11 drivers
mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:00:17 UTC (17)
mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
mmc0: queuing unknown CIS tuple 0x80 (6 bytes)
UBIFS: recovery needed
mmc0: new high speed SDIO card at address 0001
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   75550720 bytes (73780 KiB, 72 MiB, 595 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:11.
Freeing init memory: 124K
UBIFS error (pid 1): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 1): ubifs_read_node: bad node at LEB 213:83752
Failed to execute /bin/sh.  Attempting defaults...
UBIFS error (pid 952): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 952): ubifs_read_node: bad node at LEB 213:64680
UBIFS error (pid 952): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 952): ubifs_read_node: bad node at LEB 213:76288
Only way to recover this is by pressing the 'reset' button on the back. I have tried this several times, but the device refuses to run /bin/sh.

Any idea what could be the issue?
 
 
30th July 2019, 10:33 PM |#302  
Junior Member
Thanks Meter: 0
 
More
Hi, I am trying to get a root console on my wink hub 1 and have followed all the pin29 procedures however in /etc/inittab I have "::respawn:/root/platform/spawnTerminal.sh # GENERIC_SERIAL" instead of "#ttyAM0::respawn:/sbin/getty -L ttyAM0 115200 vt100 # GENERIC_SERIAL" as expected. I have tried adding the line and tried several normal linix commands but still do not get a console on normal boot, just the status info. Any help would be appreciated!
J
10th August 2019, 02:57 PM |#303  
Junior Member
Thanks Meter: 0
 
More
No ideas on why this won't work for me?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes