WeTek Community Forum

[HOWTO] Unbrick WeTek Play

ChristianTroyChristianTroy Posts: 1,913WeTek Community Member, Developers
edited February 2016 in Recovery
It might be very rare (actually it happened to me only once, few months ago, while doing "dev work" and I had no RS232 cable, I locked myself out because of a bad rom flashing) but if your device seems dead and refuses to boot to recovery using the bottom located pinhole as trigger to enter recovery (see CWM or TWRP threads for more infos about entering recovery) don't be afraid because, unless you suffer of an hardware failure, you will be able to unbrick it using this MicroSD rescue method.

Download "USB Image Tool" and "WeTek Play rescue" files (you can use 7-zip to unzip them).

Plug a MicroSD to your PC using an adapter / card reader (backup anything on it because its content is going to be erased) and launch "USB Image Tool.exe".

You will see something like this:

Vd5pjaW.png

1. As first thing select the removable disk that points to your MicroSD
2. Click "Add" button and navigate to the path where you extracted the rescue image and double click on it
3. Click "Restore" button and wait few minutes

Your rescue MicroSD has now been created, you can unplug it from your pc and insert it in WeTek Play's MicroSD slot (remove any USB peripherals eventually connected), and boot it with the usual "recovery trigger" combination.

After few moments you will see stock recovery doing its work and once it's done it will automatically reboot and you'll be able to enjoy WeTek Play again ;)

To restore your MicroSD to its original capacity (I created a 512MB rescue image so now your MicroSD will be listed as a 512MB one) you can use SD Formatter choosing those options: "FORMAT TYPE -> FULL (Overwrite)" and "FORMAT SIZE ADJUSTMENT -> ON"


Note for Linux users:

On Linux you don't need any tool like "USB Image Tool" because every distro comes with "dd" command bundled.
Just plug your MicroSD to your pc and with a command like "dmesg | tail" see how your kernel names it (it can be something like "sdb" in case you have only one SSD/HDD installed or "sdc", "sdd", etc.).
Anyway, once you know what's your MicroSD card path (pay extremely attention to it or you might wipe important data if you choose the wrong unit), just type a command like "sudo dd if=/path/to/rescue.img of=/dev/sdc bs=512".

Actually the cool thing is that you can do the same using a spare WeTek Play (in case you own more than one unit): just insert the MicroSD in its slot, put the rescue image on a flash drive and plug it in.
Now, if you're using one of my custom rom builds your flash drive's content will be located under "/storage/usbdisk0", "/storage/usbdisk1" or "/storage/usbdisk2" (I did this to allow Android's vold to be able to mount at the same time up to 3 disks / flash drives, one per WeTek Play's USB port), just check with a command like "ls /storage/usbdisk0" where is located your rescue image and modify the dd command according to it.
Example: "su" (accept the eventual SuperUser / SuperSu prompt) and after that "dd if=/storage/usbdisk0/rescue.img of=/dev/block/cardblksd bs=512"
«1

Comments

  • canthackitcanthackit Posts: 21WeTek Community Member
    It looks like i've bricked mine, so as i don't boot incorrectly " and boot it with the usual "recovery trigger combination" does this mean boot the system as we do reflashing the box ie press and hold the reset button on the bottom of the unit and plug in the power? or do i just reboot with the SD card and let the system take care of the repair?

    Regards: canthackit
  • ChristianTroyChristianTroy Posts: 1,913WeTek Community Member, Developers
    Just do the same as if you were updating the rom (so powering the device with the toothstick in the pinhole), but with the prepared microsd card inserted
  • pauldbpauldb Posts: 15WeTek Community Member
    looks like iv bricked my wetek as well, tried to go from cm11 back to stock

    tried above method and even tried to go back to cm11 but no joy,just wondering if its the micro sd slot thats broke

    get nothing, also tried used open elec on sd card again nothing ,just a blue light and the ethernet flashing

    any help greatly appreciate
  • H0nch0H0nch0 Posts: 210WeTek Community Member
    also tryed this to recover one of my wetek's get nothing bar black screen
  • H0nch0H0nch0 Posts: 210WeTek Community Member
    pauldb wrote: »
    looks like iv bricked my wetek as well, tried to go from cm11 back to stock

    tried above method and even tried to go back to cm11 but no joy,just wondering if its the micro sd slot thats broke

    get nothing, also tried used open elec on sd card again nothing ,just a blue light and the ethernet flashing

    any help greatly appreciate

    as above ? any promting to another solution ?

    UPATE , i had not ran program in admin mode all back up and running again doing 1.1.4 OTA update now :)
    many thanx and remember run as admin the program guys
  • tomtomclubtomtomclub Posts: 16WeTek Community Member
    dead link usb tool. see CWM or TWRP threads kut forum dit noting works her!!
  • freshpotsfreshpots Posts: 7WeTek Community Member
    Is a different rescue image needed for the wetek openelec?


    Edit: Some more info:I bought an wetek openlec, had e2 running on msd, all ok, went to install e2 to nand and now, didn't work and i factory reset via recovery which i think wiped openelec from nand? I ran the rescue img and now it boots up to the wetek play splash logo and bootloops without a msd. If i insert the msd with e2 on it. It will boot into that.

    Anyone have any tips on how to get the box back to the way it was on day 1 with openelec preinstalled? Seems the only method I haven't tried is the hard recovery but I really don't want to do that unless I have no other option.
  • HamsiHamsi Posts: 11WeTek Community Member
    freshpots

    http://openelec.tv/forum/146-wetek-p...-nand-download

    You must read the second message.

    HNY16
  • freshpotsfreshpots Posts: 7WeTek Community Member
    Hamsi wrote: »
    Tried that before and didn't work. Just tried it again now and it worked, not sure why but I'm back up and running now anyway thanks.
  • mauromauro Posts: 29WeTek Community Member
    Hi there,

    I would say that I've bricked the wetek play too if I would have a clear idea about how a bricked machine doesn't work.

    I tried to run openelec from an SD card and after a negative result (who knows why so far) the wetek play starts with the white splash screen with wetek.play written and keep rebooting endless stopping at this point.

    I tried to flash the box with same official ROM I flashed last time, the system starts the flashing splash screen, finish the process, reboot but nothing change...

    Any idea?
    Also the Wetek play rescue doesn't exist on Mega NZ anymore..

    Helps are welcome

    thanks
  • AnimaAnima Posts: 1,833WeTek Support Team
    edited February 2016
    mauro said:

    Hi there,

    I would say that I've bricked the wetek play too if I would have a clear idea about how a bricked machine doesn't work.

    I tried to run openelec from an SD card and after a negative result (who knows why so far) the wetek play starts with the white splash screen with wetek.play written and keep rebooting endless stopping at this point.

    I tried to flash the box with same official ROM I flashed last time, the system starts the flashing splash screen, finish the process, reboot but nothing change...

    Any idea?
    Also the Wetek play rescue doesn't exist on Mega NZ anymore..

    Helps are welcome

    thanks


    Hello @mauro

    I'm sorry for the incovenience that this problem has caused you

    Your wetek has Android or OpenELEC on NAND?

    Best regards


  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    Hello,

    The links are back online

    Best regards

  • mauromauro Posts: 29WeTek Community Member
    HI there thanks for your attention!!!

    @Anima: it is a openelec box and I Installed Androind on NAND as by video and manual with no problem and worked smoothly until I tried to boot openelec. I tried to install and boot openelec on sd in different ways with linux with no positive result and this time I used win32XXX under windows 7 which created an ext4 fs (for your record)

    @MasterChief117 : thanks for the links I'll try later on today

    ciao
  • AnimaAnima Posts: 1,833WeTek Support Team
    Hello @mauro

    Usually on the OpenELEC boxes the bootloop problem is due to the security SIM card

    Try this tutorial:

    http://www.wetekforums.com/v/index.php?p=/discussion/13059/tutorial-how-to-check-your-security-sim-on-wetek-openelec#latest

    NOTE: You will not lose the warranty in this process :smile:

    Give us feedback on the issue

    Best regards

  • mauromauro Posts: 29WeTek Community Member
    Last update.

    After creating a recovery sd card with linux and dd command as suggested I followed the recovery procedure but nothing has changed.

    Rom apparently installed and self reboot. Box start but keeps looping up to the white splash screen.

    Moro options?

    At this stage I'm thinking about installing the recovery and ROM using ADB and serial cable but I'm not sure it is correct nor I know the procedure.

    I'm open to any hints

    ciao
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    edited February 2016
    mauro said:

    Last update.

    After creating a recovery sd card with linux and dd command as suggested I followed the recovery procedure but nothing has changed.

    Rom apparently installed and self reboot. Box start but keeps looping up to the white splash screen.

    Moro options?

    At this stage I'm thinking about installing the recovery and ROM using ADB and serial cable but I'm not sure it is correct nor I know the procedure.

    I'm open to any hints

    ciao

    Check the sim card please :)

    Best regards

  • mauromauro Posts: 29WeTek Community Member
    edited February 2016
    :(

    ejected and inserted and tested twice, nothing changed...

    Do you think that this issue is after a try to start openelec from SD this could not have damaged the file system?

    Open to a new try and thanks for your patience
  • AnimaAnima Posts: 1,833WeTek Support Team
    edited February 2016
    Hello @mauro

    The next step would be a soft-recovery

    wetekforums.com/v/index.php?p=/discussion/20136/soft-recovery-for-wetek-play-openelec

    But this is only possible if you have a serial debug connection to your pc.
    Do you?

    Best regards

  • mauromauro Posts: 29WeTek Community Member
    edited February 2016
    I need to find a serial 2usb adaptor. Do u have any suggestion about what to buy or more important what not to buy?

    Thanks for ur time

    Ciao
  • AnimaAnima Posts: 1,833WeTek Support Team
    mauro said:

    I need to find a serial 2usb adaptor. Do u have any suggestion about what to buy or more important what not to buy?

    Thanks for ur time

    Ciao

    Hello @mauro

    there is no recommendation for a serial cable, any should work properly

    Best regards


  • mauromauro Posts: 29WeTek Community Member
    Ciao @Anima,

    Quick update. I'm still waiting for the serial 2usb adapter but I've just tried to create the soft recovery sd card and my only achievement is apparently keep formatting the sdcard. I enabled to show hidden file in case the .bin is considered as such by the system and still the folder is empty. I'm working on a windows 7 machine if this make any difference otherwise I normally work on linux pc

    Could u check that the files from you links are not corrupted some how?

    Thanks
  • AnimaAnima Posts: 1,833WeTek Support Team
    hello @mauro

    After the first run with the program, with the format option enabled.
    Run the program a second time without the option enabled

    When it ends eject the mSD card, insert it again and load the u.boot.bin manually.
    And it should be ready to use.

    Best regards

  • mauromauro Posts: 29WeTek Community Member
    Hello @Anima,

    I've tried to do a soft recovery and save log. Positive the log, negative for the soft recovery

    I had few issues like:
    after typing:
    "fatload mmc 0 0x82000000 u-boot.bin"
    or
    "sf write 0x82000000 0 60000"
    the box reboots.

    after the command sf probe 2 I receive the following msg:
    "SF: detected MX25L3205D with page size 256, total 4MiB
    SPI NOR Flash have write protect!!!
    4096 KiB MX25L3205Dat 0:2 is now current device"

    insted of
    wetek#
    I have
    m6_mbx#

    at the boot msg I can read
    "NAND bbt detect factory Bad block at a8200000"

    After all, I started the box connected to the tv and this time it doesn't even shows the splash screen

    I've tried to copy and past the log file but this would exceed the maximum text length. Let me know how I could forward

    thanks
  • AnimaAnima Posts: 1,833WeTek Support Team
    edited February 2016
    Hello @mauro
    insted of
    wetek#
    I have
    m6_mbx#
    It seems you have loaded a bootloader from a different device and with a bit of luck, all went fine.

    Just Install an Android build and see if the u.boot boots normally.
    wetekforums.com/v/index.php?p=/discussion/20706/wetek-os-1-1-6-for-wetek-play-25-11-2015/p1

    Use this File:
    https://mega.nz/#!uVBXwJzB!SGvb9hsxYBdOXpRCi4dAPw0CgmAXrtgDjWrmyvxpblQ

    We'll go from there

  • mauromauro Posts: 29WeTek Community Member
    edited February 2016
    Ciao @Anima,

    for your record. First soft recovery attempt was using linux and serial 2 usb and the prompt was
    w6_mbx#
    Yesterday I connected the serial directly to a wondows tower and the prompt was wetek#...I leave to you the reasons for this;)

    I tried to reinstall Androind as I did positively the first time. I've the log from putty if you'd like to take a look at it but I need your email.

    Here a couple of lines which worn me a bit.

    Thanks

    Code below:
    i=0,register --- nand_key
    NAND bbt detect Bad block at 0
    NAND bbt detect factory Bad block at b400000
    NAND bbt detect factory Bad block at b600000
    NAND bbt detect factory Bad block at a8e00000
    Creating 8 MTD partitions on "nandnormal":
    0x000000800000-0x000001000000 : "logo"
    0x000001000000-0x000001800000 : "aml_logo"
    0x000001800000-0x000002000000 : "recovery"
    0x000002000000-0x000002800000 : "boot"
    0x000002800000-0x000042c00000 : "system"
    NAND bbt detect factory Bad block at b400000
    NAND bbt detect factory Bad block at b600000
    0x000042c00000-0x000062c00000 : "cache"
    0x000062c00000-0x000072c00000 : "backup"
    0x000072c00000-0x0000ff000000 : "data"
    NAND bbt detect factory Bad block at a8e00000
    nandnormal initialized ok
    >>>>

    <<<<
    NAND erase: whole chip.
    NAND bbt detect Bad block at 0

    Skipping bad block at 0x00000000

    Erasing at 0x200000 -- 0% complete.
    Erasing at 0x2800000 -- 1% complete.
    Erasing at 0x5000000 -- 2% complete.
    Erasing at 0x7a00000 -- 3% complete.
    Erasing at 0xa200000 -- 4% complete. NAND bbt detect factory Bad block at b400000

    Skipping bad block at 0x0b400000
    NAND bbt detect factory Bad block at b600000

    Skipping bad block at 0x0b600000

    Erasing at 0xcc00000 -- 5% complete.
    .
    .
    Erasing at 0xa3c00000 -- 64% complete.
    Erasing at 0xa6600000 -- 65% complete. NAND bbt detect factory Bad block at a8e00000

    Skipping bad block at 0xa8e00000

    Erasing at 0xa9000000 -- 66% complete.
    .
    .
    .
    Erasing at 0xffe00000 -- 100% complete.
    OK
    (Re)start USB(0)...
    USB: dwc_usb driver version: 2.94 6-June-2012
    USB (1) peri reg base: c1108420
    USB (1) use clock source: XTAL input
    USB (1) PHY Clock not detected!
    USB (1) base addr: 0xc90c0000
    Force id mode: Host
    dwc_otg: Highspeed device found !

    scanning bus for devices... 1 USB Device(s) found
    scanning bus for storage devices... 0 Storage Device(s) found

    ** Invalid boot device **
    enter recovery


    NAND read: logo whole chip
    8388608 bytes read: OK
    Err imgPack(L72):magic of oldest img not item header!
    Err imgPack(L115):Err res header.
    cp - memory copy

    Usage:
    cp [.b, .w, .l] source target count
    Device: SDIO Port B
    Manufacturer ID: 0
    OEM: 0
    Name: #Tran Speed: 40000000
    Rd Block Len: 512
    SD version 2.0
    High Capacity: No
    Capacity: 1967128576
    Boot Part Size: 0
    Bus Width: 4-bit
    reading recovery.img

    5103616 bytes read
    ## ANDROID Format IMAGE
    ## Booting kernel from Legacy Image at 82000000 ...
    Image Name: Linux-3.0.50-wetek
    Image Type: ARM Linux Kernel Image (lzma compressed)
    Data Size: 3478163 Bytes = 3.3 MiB
    Load Address: 80008000
    Entry Point: 80008000
    Verifying Checksum ... OK
    Ramdisk start addr = 0x82352000, len = 0x18b9fa
    board_usb_stop cfg: 0
    Uncompressing Kernel Image ... OK
    uboot time: 13934877 us.
    machid from environment: 0x4e27
    EFUSE machid is not set.
    Using machid 0x4e27 from environment

    Starting kernel ...
    .
    .
    >>>>>

    <<<<
    .
    .
    [ 3.945589@0] ####Version of Uboot must be newer than U1.06.011!!!!!
    [ 3.952093@0] 2
    [ 3.953751@0] SPI BOOT, m3_nand_probe continue i 0
    [ 3.958576@0] chip->controller=c0a55f04
    [ 3.962341@0] checking ChiprevD :0
    [ 3.965727@0] aml_nand_probe checked chiprev:0
    [ 3.970196@0] init bus_cycle=17, bus_timing=10, start_cycle=10, end_cycle=10,system=5.0ns
    [ 3.978765@0] No NAND device found.
    [ 3.982025@0] NAND device id: 2c 44 44 4b a9 0
    [ 3.986307@0] NAND device: Manufacturer ID: 0x2c, Chip ID: 0x2c (Micron D revision NAND 4GiB MT29F32G08CBADA)
    [ 3.996391@0] #####aml_nand_init, with RB pins and chip->chip_delay:20
    [ 4.002737@0] bus_cycle=4, bus_timing=5, start_cycle=5, end_cycle=6,system=5.0ns
    [ 4.010109@0] oob size is not enough for selected bch mode: NAND_BCH60_1K_MODE force bch to mode: NAND_BCH40_1K_MODE
    [ 4.020609@0] aml_chip->oob_fill_cnt =168,aml_chip->oob_size =744,bch_bytes =70
    [ 4.027878@0] multi plane error for selected plane mode: NAND_TWO_PLANE_MODE force plane to : NAND_SINGLE_PLANE_MODE
    [ 4.038427@0] oob layout use nand base oob layout oobsize = 16,oobmul =1,mtd->oobsize =744,aml_chip->oob_size =744
    [ 4.057368@0] aml nand env valid addr: 20000
    [ 4.089614@0] nand env: nand_env_probe.
    [ 4.090282@0] nand key: nand_key_probe.
    [ 4.091803@0] key start_blk=2040,end_blk=2047,aml_nand_key_init:651
    [ 4.105121@0] aml nand key valid addr: ff010000
    [ 4.105146@0] aml nand key valid addr: ff210000
    [ 4.108723@0] aml nand key valid addr: ff410000
    [ 4.113295@0] aml nand key valid addr: ff610000
    [ 4.117959@0] i=0,register --- nand_key NAND bbt detect Bad block at 0
    [ 4.124504@0] NAND bbt detect factory Bad block at b400000
    [ 4.130188@0] NAND bbt detect factory Bad block at b600000
    [ 4.135860@0] NAND bbt detect factory Bad block at a8e00000
    [ 4.141584@1] Indeed it is in host mode hprt0 = 00021501
    [ 4.141597@0] Creating 8 MTD partitions on "D revision NAND 4GiB MT29F32G08CBADA":
    [ 4.141611@0] 0x000000800000-0x000001000000 : "logo"
    [ 4.148734@0] 0x000001000000-0x000001800000 : "aml_logo"
    [ 4.150099@0] 0x000001800000-0x000002000000 : "recovery"
    [ 4.151295@0] 0x000002000000-0x000002800000 : "boot"
    [ 4.152489@0] 0x000002800000-0x000042c00000 : "system"
    [ 4.152502@0] NAND bbt detect factory Bad block at b400000
    [ 4.152507@0] NAND bbt detect factory Bad block at b600000
    [ 4.153746@0] 0x000042c00000-0x000062c00000 : "cache"
    [ 4.154959@0] 0x000062c00000-0x000072c00000 : "backup"
    [ 4.156167@0] 0x000072c00000-0x0000ff000000 : "data"
    [ 4.156204@0] NAND bbt detect factory Bad block at a8e00000
    [ 4.157661@0] init_aml_nftl start
    [ 4.157675@0] mtd->name: system
    [ 4.157685@0] nftl version 140415a
    [ 4.157744@0] nftl part attr 0
    [ 4.157762@0] NAND bbt detect factory Bad block at b400000
    [ 4.157768@0] NAND bbt detect factory Bad block at b600000
    [ 4.157818@0] size_in_blk 514; total_block 512;
    [ 4.157823@0] nftl start:512,64
    [ 4.159006@0] first
    [ 4.180125@0] NAND bbt detect factory Bad block at b400000
    [ 4.180132@0] NAND bbt detect factory Bad block at b600000
    [ 4.311026@0] average_erase_count:0
    [ 4.311063@0] second 0,448
    [ 4.311565@0] all block full!!
    [ 4.314605@0] free block cnt = 512
    [ 4.318035@0] new current block is 513
    [ 4.321719@0] nftl ok!
    [ 4.324488@0] aml_nftl_blk->mbd.tr.name =system
    [ 4.329379@1] aml_nftl_init_bounce_buf, use cache here
    [ 4.333779@0] system: unknown partition table
    [ 4.338457@0] _nftl_init_bounce_buf already init 1000
    [ 4.343158@0] aml_nftl_add_mtd ok
    [ 4.346460@0] mtd->name: cache
    [ 4.349537@0] nftl version 140415a
    [ 4.352906@0] nftl part attr 0
    [ 4.355949@0] nftl start:256,32
    [ 4.359671@0] first
    [ 4.436718@0] average_erase_count:0
    [ 4.436742@0] second 0,224
    [ 4.437250@0] all block full!!
    [ 4.440313@0] free block cnt = 256
    [ 4.443674@0] new current block is 255
    [ 4.447405@0] nftl ok!
    [ 4.450203@0] aml_nftl_blk->mbd.tr.name =cache
    [ 4.454788@1] aml_nftl_init_bounce_buf, use cache here
    [ 4.459385@0] cache: unknown partition table
    [ 4.463902@0] _nftl_init_bounce_buf already init 1000
    [ 4.468709@0] aml_nftl_add_mtd ok
    [ 4.471972@0] mtd->name: backup
    [ 4.475100@0] nftl version 140415a
    [ 4.478517@0] nftl part attr 0
    [ 4.481535@0] nftl start:128,16
    [ 4.484921@0] first
    [ 4.524598@0] average_erase_count:0
    [ 4.524621@0] second 0,112
    [ 4.525136@0] all block full!!
    [ 4.528200@0] free block cnt = 128
    [ 4.531560@0] new current block is 127
    [ 4.535290@0] nftl ok!
    [ 4.537995@1] usb 2-1: new high speed USB device number 2 using dwc_otg
    [ 4.538115@0] aml_nftl_blk->mbd.tr.name =backup
    [ 4.538934@0] aml_nftl_init_bounce_buf, use cache here
    [ 4.539045@0] backup: unknown partition table
    [ 4.558692@0] _nftl_init_bounce_buf already init 1000
    [ 4.563326@0] aml_nftl_add_mtd ok
    [ 4.566628@0] mtd->name: data
    [ 4.569623@0] nftl version 140415a
    [ 4.573064@0] nftl part attr 0
    [ 4.576052@0] NAND bbt detect factory Bad block at a8e00000
    [ 4.581845@0] size_in_blk 1122; total_block 1121;
    [ 4.586503@0] nftl start:1121,140
    [ 4.593586@0] first
    [ 4.593889@1] hub 2-1:1.0: USB hub found
    [ 4.596105@1] hub 2-1:1.0: 4 ports detected
    [ 4.721839@0] NAND bbt detect factory Bad block at a8e00000
    [ 4.925579@0] average_erase_count:0
    [ 4.925622@0] second 0,981
    [ 4.926113@0] all block full!!
    [ 4.929198@0] free block cnt = 1121
    [ 4.932623@0] new current block is 1121
    [ 4.936439@0] nftl ok!
    [ 4.939260@0] aml_nftl_blk->mbd.tr.name =data
    [ 4.943921@1] aml_nftl_init_bounce_buf, use cache here
    [ 4.948346@0] data: unknown partition table
    [ 4.952839@0] _nftl_init_bounce_buf already init 1000
    [ 4.957532@0] aml_nftl_add_mtd ok
    [ 4.960894@0] init_aml_nftl end
    >>>>


    <<<
    [ 6.254163@0] #SD_MMC_ERROR_DRIVER_FAILURE error occured in sd_voltage_validation()
    >>>
  • AnimaAnima Posts: 1,833WeTek Support Team
    Hello @mauro

    So the Android still doesn't boot?

    Upload the full log on MEGA and post it here, so we can take a look at it.

    Best regards

  • mauromauro Posts: 29WeTek Community Member
    Hi @Anima

    Confirmed!!!
    The box doesn't boot, still looping but at least I gained the white wetek splash screen.

    Tomorrow I'll post the log

    Ciao
  • mauromauro Posts: 29WeTek Community Member
  • mauromauro Posts: 29WeTek Community Member
    Ciao @Anima,

    I have uploaded 3 more logs which I saved before the one above (older that the above one)
    I think that the above one has an updated Uboot and shows #wetek, those 3 have an older uboot version and prompt #m6_mbx
    putty_output
    putty_putput_1
    putty_output_2

    If it is so at least I know that is not a way of using an Serial2USB cable!

    Hope to hear back good news from you soon

    ciao
  • AnimaAnima Posts: 1,833WeTek Support Team
    hello @mauro

    Your last logs require a verification key, i cannot access without it.
    Re-upload them please or send me private message with the key.
    Your previous log is already being looked by our developers

    Best regards

Sign In or Register to comment.
© Copyright 2014 - Creative Dreams | Powered by Vanilla
All times are UTC