New Camera - Flashed (I think!), cannot get sd card loaded with hack...

[Swiftnesses]

Hi,

I have successfully flashed (I believe so anyway, as the version in the log is now much lower than what I originally had!). The issue is, after flashing and loading the sd card, I cannot get the camera to connect to wifi - I'm not even convinced it's booting from the sd card as it's supposed to.

Log is here: https://pastebin.com/ryud1Xyt

Thanks in advance.

[jmtatsch]

Not running our custom fw.

[Swiftnesses]

Guess my camera is one of the new ones (seems they ship this version now). Tried flashing multiple times, is there a workaround for the new firmwares?

[Swiftnesses]

Strange, as it seems like the demo.bin flashes?

U-Boot 2013.07 (Dec 21 2017 - 18:44:33)

Board: ISVP (Ingenic XBurst T20 SoC)
DRAM:  128 MiB
Top of RAM usable for U-Boot at: 84000000
Reserving 399k for U-Boot at: 83f9c000
Reserving 32784k for malloc() at: 81f98000
Reserving 32 Bytes for Board Info at: 81f97fe0
Reserving 124 Bytes for Global Data at: 81f97f64
Reserving 128k for boot params() at: 81f77f64
Stack Pointer at: 81f77f48
Now running in RAM - U-Boot at: 83f9c000
MMC:   msc: 0
the manufacturer c8
SF: Detected GD25Q128

*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
misc_init_r before change the wifi_enable_gpio
gpio_request lable = wifi_enable_gpio gpio = 62
misc_init_r after gpio_request the wifi_enable_gpio ret is 62
misc_init_r after change the wifi_enable_gpio ret is 0
misc_init_r before change the yellow_gpio
gpio_request lable = yellow_gpio gpio = 38
misc_init_r after gpio_request the yellow_gpio ret is 38
misc_init_r after change the yellow_gpio ret is 0
misc_init_r before change the blue_gpio
gpio_request lable = blue_gpio gpio = 39
misc_init_r after gpio_request the blue_gpio ret is 39
misc_init_r after change the blue_gpio ret is 1
gpio_request lable = night_gpio gpio = 81
misc_init_r after gpio_request the night_gpio ret is 81
misc_init_r after change the night_gpio ret is 0
gpio_request lable = night_gpio gpio = 25
misc_init_r after gpio_request the night_gpio ret is 25
misc_init_r after change the night_gpio ret is 0
gpio_request lable = night_gpio gpio = 49
misc_init_r after gpio_request the night_gpio ret is 49
misc_init_r after change the night_gpio ret is 0
gpio_request lable = USB_able_gpio gpio = 47
misc_init_r after gpio_request the USB_able_gpio ret is 47
misc_init_r after change the USB_able_gpio ret is 0
gpio_request lable = TF_able_gpio gpio = 43
misc_init_r after gpio_request the TF_able_gpio ret is 43
misc_init_r after change the TF_able_gpio ret is 1
gpio_request lable = SPK_able_gpio gpio = 63
misc_init_r after gpio_request the SPK_able_gpio ret is 63
misc_init_r after change the SPK_able_gpio ret is 0
gpio_request lable = SD_able_gpio gpio = 48
misc_init_r after gpio_request the SD_able_gpio ret is 48
misc_init_r after change the SD_able_gpio ret is 0
misc_init_r before change the wifi_enable_gpio
gpio_request lable = wifi_enable_gpio gpio = 62
misc_init_r after gpio_request the wifi_enable_gpio ret is 62
misc_init_r after change the wifi_enable_gpio ret is 1
Hit any key to stop autoboot:  0 
jiabo_do_auto_update!!!!!!!!!!!!!!!!!!!!!!!!
gpio_request lable = sdupgrade gpio = 46
setup_button set long!!!!!!!!!!!!!!!!!!!
Interface:  MMC
  Device 0: Vendor: Man 000002 Snr 1b4d5200 Rev: 2.2 Prod: SA32G
            Type: Removable Hard Disk
            Capacity: 30028.0 MB = 29.3 GB (61497344 x 512)
Filesystem: FAT32 "NO NAME    "
the manufacturer c8
SF: Detected GD25Q128

reading demo.bin
reading demo.bin
jiabo_au_check_cksum_valid!!!!!!!!!!!!!!!!!!!!!!!!
jiabo_idx=4
misc_init_r before change the blue_gpio
gpio_request lable = blue_gpio gpio = 39
misc_init_r after gpio_request the blue_gpio ret is 39
misc_init_r after change the blue_gpio ret is 0
jiabo_start=40000,jiabo_len=a90000
flash erase...
flash write...
misc_init_r after change the blue_gpio ret is 1
the manufacturer c8
SF: Detected GD25Q128

--->probe spend 4 ms
SF: 2621440 bytes @ 0x40000 Read: OK
--->read spend 381 ms
## Booting kernel from Legacy Image at 80600000 ...
   Image Name:   Linux-3.10.14
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1804956 Bytes = 1.7 MiB
   Load Address: 80010000
   Entry Point:  803e3200
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

[Swiftnesses]

I have access to U-BOOT via serial, can I flash another bootloader from there?

[jmtatsch]

Interesting, which Xiaomi stock fw was running before? @EliasKotlyar do you see what’s wrong?

[Swiftnesses]

TBH, I lost track, certainly one of the latest, think it ended in .48?

[deten]

I am having similar issue, how can I check the current firmware installed?

[blueacidic]

I'm currently on 5.5.1.418 and not able to flash the bootloader

I believe @Swiftnesses might be running the same?

[jmtatsch]

Attach a serial interface and dump the defunct boot loader, upload it here.

[blueacidic]

I don't have a serial interface, is there something else i could do?

[jmtatsch]

No, except buying that interface :)

[Swiftnesses]

My device came with a new bootloader which prevented booting from the SD (documented on here).

I worked around it by flashing a new uboot image via the normal command line (using serial). I placed the image on the SD, booted, ignored the debug messages and flashed from the media directory using these commands:

flash_eraseall /dev/mtd0
dd if=bootloaderfile.bin of=/dev/mtd0 

[blueacidic]

Only way to check the bootloader is also to collect via serial?

[Swiftnesses]

I believe so...

[blueacidic]

U-Boot 2013.07 (Dec 21 2017 - 18:44:33)

Is this the bootloader version which you flashed?

[Swiftnesses]

That's the bootloader I had, I first flashed the one from there (custom) and then reverted back to the one from the original folder of the hacks...