junari_ has quit [Remote host closed the connection]
pabs has quit [Ping timeout: 480 seconds]
pabs has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
gsz has joined #linux-sunxi
rajkosto has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
dliviu has quit [Read error: No route to host]
dliviu has joined #linux-sunxi
evgeny_boger has joined #linux-sunxi
gsz has quit [Ping timeout: 480 seconds]
rajkosto has quit [Quit: Leaving]
rajkosto has joined #linux-sunxi
ftg has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
rajkosto has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
gsz has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit []
vagrantc has joined #linux-sunxi
bananicorn has quit [Remote host closed the connection]
bananicorn has joined #linux-sunxi
apritzel has joined #linux-sunxi
bauen1 has joined #linux-sunxi
dsbeka has joined #linux-sunxi
<dsbeka>
answer! hello. I got a board:H313-r69-v2.0 cpu:allwinner H313. bricked at reflashing a new firmware. how to fix this?
<dsbeka>
grming has joined #linux-sunxi
<apritzel>
dsbeka: how did you flash the firmware? From inside Android? Or using a USB cable?
<dsbeka>
from usb cable
<apritzel>
using PhoenixSuite?
<dsbeka>
yes
<dsbeka>
i have a log from UART send you to chat
<apritzel>
did you enter FEL mode by pushing some hidden button inside the headphone jack?
<apritzel>
a log is not really needed
<dsbeka>
yes
<dsbeka>
my bootloader locked and i flashed H313-10.1.x29.img file and stuck at boot logo
<dsbeka>
before flash installed by factory MBOX 10.1x27 firmware and i not backuped them
<apritzel>
so you think you flashed the wrong firmware?
<dsbeka>
yes i flashed firmware for T95 Mini board with empc
<dsbeka>
my board not empc, my board has 2gb ram and samsung emmc
evgeny_boger has quit [Ping timeout: 480 seconds]
<apritzel>
so I don't think there is some hidden rescue boot partition on the board, if that is your question
<apritzel>
but you should be able to just flash the right firmware, by booting into FEL mode and use the proper image file
<apritzel>
if you find that somewhere
<apritzel>
because FEL mode is a function of the BootROM, so cannot be overwritten
<dsbeka>
can i download linux for this board?
<dsbeka>
board developers can not answer and not giving right image
<apritzel>
we are about to enable mainline support for some of those H313/H616 TV boxes, but it's not ready yet
<apritzel>
I don't know if Armbian has some working image already, but I doubt it
<apritzel>
in the last week there were some people here with similar boxes, and I think we know what to do to boot mainline U-Boot and Linux on them
<dsbeka>
BootROM not have a stopautoboot?
<apritzel>
normally the BootROM tries to boot from SD card, then eMMC, then falls back to FEL USB debug mode
<apritzel>
unless you hit that hidden FEL button, then it goes to FEL mode immediately
<dsbeka>
how to boot fastboot mode?
<apritzel>
(press that FEL button during reset or power-on, I mean)
<apritzel>
fastboot is already part of the firmware
<apritzel>
but FEL mode has even more powers, so it's just a matter of finding the right image
<dsbeka>
not giving results
<dsbeka>
i flashed all h616 h313 images from xda and 4pda
<dsbeka>
only 1 image gives boot logo suck
<dsbeka>
only 1 image gives boot logo stuck*
<dsbeka>
all images not booting (black screeen and no uart log)
<apritzel>
why did you flash another vendor based image anyway?
<dsbeka>
to find the right one
<dsbeka>
devs of this board not responding
<apritzel>
did you really expect anything from those throw-away vendors?
<apritzel>
those TV boxes are all very similar, but differ in stupid details, like GPIO assignment, and PMIC details, which makes those images mostly incompatible to each other
<apritzel>
you will be
<dsbeka>
I thought they would send the firmware file but I was wrong
<apritzel>
... able to use the box with mainline Linux in the future, but I am afraid for now you are stuck with finding some image, somewhere
gsz has quit [Ping timeout: 480 seconds]
<apritzel>
I mean why did you flash something in the first place? Were you not happy with what the box did?
<dsbeka>
firmware had a lot of problems
<dsbeka>
the worst is the crash of the built-in launcher and no sleep mode
<apritzel>
just to be sure: this channel is more about mainline Linux support on any kind of Allwinner based devices
<apritzel>
we know that the vendor provided firmware is mostly crap
<apritzel>
and we typically don't bother to find another similarly crappy firmware, but put proper Open Source firmware and kernels on them
vagrantc has quit [Quit: leaving]
<dsbeka>
how to boot to console mode to send commands to uart
<dsbeka>
maybe i boot linux on this board
<apritzel>
to boot Linux you need U-Boot, configured for this board
<apritzel>
so you need to know the DRAM parameters, and other board details that allow you to create a devicetree
<dsbeka>
i have a u-boot configured to this board
<dsbeka>
but this u-boot at 1.7gb img file
<dsbeka>
how to extract them idk (((
<apritzel>
if this U-Boot is from a vendor firmware: that doesn't help
<apritzel>
because this U-Boot is typically part of the crap already ;-)
<apritzel>
so do you have a working image file?
<dsbeka>
Is there anyone who can help me build a u-boot?
<dsbeka>
i have 1 image with working uart logs and boot logo stuck
<apritzel>
or the vendor U-Boot might not allow to stop the autoboot, actually
<apritzel>
anyway getting into the vendor U-Boot won't be of little help
<apritzel>
I guess you have opened up the box, to get access to the UART pins?
<apritzel>
can you post a picture of the PCB, to see what components are there? In particular we need to know if there is a PMIC and if yes, which one it is