Bricked mini 0801

Sander

New Member
Joined
Nov 11, 2013
Messages
25
Reaction score
2
Country
Netherlands
As someone advised, I made this topic because of my bricked mini 0801. The red led goes on when I connect it to USB, I can put it in the update mode by holding the power button and direct USB is able to connect. (driver is installed).

I choose an .elf file and hit download. It starts to roll and before it says writing firmware I hear the USB device disconnect en disappear from my hardware list. When the writing is done it tries to reconnect but the camera does nothing, I cannot put it on myself.

I have tried the following files;

0801-244-2212-20130821-NO1-SPI-1CARD-2710-NOGPS-M8452-Neutral.elf
20130905-NO1-SPI-1CARD-2710-GPS-MA310.elf
20130903-NO1-SPI-1CARD-2710-GPS-MA310.elf
20130924_0801_2710_SPI_NOGPS_8452.elf

I have used different versions of direct USB and tried it on 2 computers and the all do the same. There is help from givoe but it takes time. They are asking the factory but as I read in another topic the guy in contact with the factory is sick so this could take awhile.

Does it matter what the filename is when flashing a firmware trough direct USB? Is the device supposed to disconnect when its about to start writing?

Any more elf files out there I could try? I'm out of options. :-(
 
Did you set program timeout to 300000?
 
I forgot to mention that, yes i did. Even tried 500000.
 
I gues the LED turns blue (it should) after pressing "Connect"?
How did you brick it?
 
Yes it turns blue when i hit connect.
I probably flashed the wrong firmware for this hardware. I did not change the filename and it asked me if i wanted to update. When i hit yes it was flashing and then nothing.
 
Disassembling would help, maybe.. Which Firmware did you flash?
Anyways.. Could you try my unbricking bundle?
https://drive.google.com/file/d/0B4FRwm9CGCLkRjhRcVlxVnYwZGc/edit?usp=sharing
Then try to flash the mini0801.e2b file. I doubt it'll work but it's worth a try :D


This is what happens during USB recovery flash:

usbflash.png


You said you maybe flashed a wrong firmware. USB flashing should even work with corrupted firmware - this can't be the problem.. It fails somewhere in the progress shown in the picture above. Is your battery charged?
 
Last edited:
As someone advised, I made this topic because of my bricked mini 0801. The red led goes on when I connect it to USB, I can put it in the update mode by holding the power button and direct USB is able to connect. (driver is installed).

what USB cable are you using?
 
Just a few thoughts on the subject of updates.

I've been having a close look and some different version of E-Prance firmware.

E-Prance firmware 0913 is 4,282,368 bytes in size, the latest E-Prance firmware is 4,300,800 bytes in size, as expected running a checksum check on both files show totally different checksums, which is obvious as the files are different.

When firmware is updated, it reads the checksum, and then does a check of the whole file, if the checksums match it goes ahead and flashes the firmware, according to Tobi@s it does multiple checks, that's quiet possible as the only decompiling I've done recently is to dis-assemble a Russian Mio firmware just to satisfy myself that it did indeed support the English language before I updated to it, as I don't read Russian...lol.. which it did.. so I knew it was reasonably safe to use.

The problem I see however with the mini 0801, is that when people change the filename to make it work on their camera, as their camera may not have been made at the same factory, and may have subtle hardware differences/specs, IOW according to joklin they may not even be the same inside, so although in theory it should not brick your camera, some features may not work. The other big issue is some users have more indepth knowledge of computers, who are likely to have far less issues, but another user may have very limited knowledge, so if their device fails, those are the more likely to send camera's back for repair, and this applies to any device not just camera's of course.
Take it from me. you would not believe some things users get up to... then they demand a replacement from the seller, quoting all the consumer laws under the sun...lol. I was in the electronic repair and design business for 40yrs, many years as service manager for MasterCare UK Ltd who do all the servicing for DSG group, ie, Curry's/PC World ect, plus many others, including other service contract work. We used to get on average 20 laptops a week returned simply because users had not heeded and taken basic simple precautions before updating the bios. IOW. They had located online what looked like a more recent bios version and just gone ahead without doing basic checks and precautions first.

I have a relative who is the manager at the Birminham Apple centre, and only a few weeks ago, he was saying that whenever Apple release new updates for say the various iPads, their returns triple, usually they are able to get many of them up and running again when customers take them back to the store. As we all know Apple locks their stuff down pretty tightly, but the fact is staff still see increases in returns when new updates are released, simply because some people don't have a clue...lol

With these camera, anyone with a little knowledge can edit the firmware and make checksums match the file, quite easily, obviously no-one on here would, at least I hope not, but it's possible. The other danger is in the event the file is incorrect for that specific camera. In a ideal world all bases should be covered to prevent a bad update, but the sad fact is it does happen. Most of the people on this forum are more savvy than others, well they showed a bit of smartness by coming on here in the first place.. lol .. I've known some devices be so badly designed that I could rename any file to xxxxx.bin and it would attempt to flash it, even if it was full of crap, guaranteeing a bricked PC/Laptop or other device, unless you had the specific knowledge to recover. When Gigabyte started doing their duel bios boards years ago, their returns for bad/dead motherboards fell dramatically.

Nonetheless, I do empathise with sellers, and understand why they are often reluctant to release firmware versions, where most times they end up being posted on forums for the unwary Joe public to download, thankfully we don't get many users who brick their camera's, I think I've only seen 4 in the last few months, but I still maintain if somethings working okay.. then leave it alone, and only update it if you can afford to bin it. Most people like myself and many others never take our own advice of course. ;-)

This book is available on kindle priced 10p...lol
 
Last edited:
I think i flashed the TS firmware one started a discussion for on this firmware, this was the only firmware the dvr asked me to update.
I use an USB cable with pin 4 and 5 connected. I am able to put the camera in update mode and connect with direct USB.

Tobias: That screenshot of that dosbox. What program are u using there?

Lunar: Thats a whole story. ;-) Im quite into computers for almost 25 years and updated quite a few firmwares for different devices during that time. I do not know if its a crc error but since i tried 4 elf files atleast one should have a good crc but all the files do the same in direct USB.

I will try the dos program when i get back home, maybe that will work. Till now now response from givoe on aliexpress.
 
To get the into the terminal you need an uart to USB converter.. It costs around 15€ I guess..
 
Sander:
Yes I do tend to ramble on at times...lol, I forget I'm on a forum and not writing a book... ;-), it sounds like you have plenty experience, unfortunately sometimes it happens to the best of us, but hopefully, you will manage to sort it, especially if you can get the right .elf file. I suppose just knowing you were working with a known good .elf file would be some assurance, as at least then you could rule that out, had it been from E-Prance I may have been able to help. I hope you manage to sort it between the 2 of you, my money's on SUCCESS. Hope so anyway. So I won't clutter up your thread any more...lol... after all that was the whole point of moving it here so you and Tobi@s can exchange ideas and suggestions, without the confusion of all the other mixed posts, :) I've been following his hacking efforts so AIS previously if he can't help I don't think anyone can. Best of luck anyway.
 
Sorry for this long log posted bellow but this is what i get when i want to flash one of the elf files i got from givoe. Can anyone see what goes wrong?


Set message level: 3
AMBA_Log_Set_Level.()
[2.2.13.0]
AMBA_Parse_Board_Config:
Board Count = 14, Limit = 40.
AMBA_Parse_Board_Config. (0)
AMBA_USB_Init:()
AMBA_USB_Dev_Init:()
Found 1 busses, 1 devices changed
AMBA_OS_Get_USB_Location:(04DC7B18,0032E934,0032E938)
Filename=\\.\libusb0-0001--0x4255-0x0001
bus=0, port=0
AMBA_OS_Get_USB_Location.(0)
AMBA_USB_Configure:(0x04DC7B18,0x0032E93C)
Dev#1: 0x4255 (Amba) : 0x0001 (A4 ) : 123456789ABC has 1 configs
AMBA_USB_Configure.(0x00416F88)
AMBA_Check_State: (0x0032E93C)
State is BOOT
AMBA_Check_State. (0x0)
Found 1 AMBA device!
AMBA_USB_Dev_Init.
AMBA_USB_Init.(1)
ConvertELF(0801-244-2212-20130821-NO1-SPI-1CARD-2710-NOGPS-M8452-NEUTRAL.ELF):
ConvertELF(0).
AMBA_Set_Boot_File: (0x1,0801-244-2212-20130821-NO1-SPI-1CARD-2710-NOGPS-M8452-N
EUTRAL.e2b)
AMBA_Set_Boot_File. ()
Reinit start wait.
AMBA_USB_Download:(0,0x1,4)
AMBA_Load_File_BST: (C:\1\bld\a2s.bin,0xc0000000,1)
AMBA_Load_File: (C:\1\bld\a2s.bin,0x00000000,0x0714EE28)
AMBA_Load_File. (0)
Load file start.
Load file end.
AMBA_Load_File_BST. (0)
[0] AMBA_USB_Reinit_Wait: (1,1)
[0] Wait device re-init...
Reinit start signal.
AMBA_USB_Dev_Scan:()
Found 0 busses, 0 devices changed
AMBA_OS_Get_USB_Location:(04DC7B18,073CF4AC,073CF4B0)
Filename=\\.\libusb0-0001--0x4255-0x0001
bus=0, port=0
AMBA_OS_Get_USB_Location.(0)
AMBA_USB_Configure:(0x04DC7B18,0x073CF4B4)
Dev#1: 0x4255 (AMBA) : 0x0001 (Ambarella USB generic class) : 123456789ABC has 1
configs
AMBA_USB_Configure.(0x00416F88)
AMBA_Check_State: (0x073CF4B4)
State is LOAD
AMBA_Check_State. (0x1)
AMBA_USB_Simple_Command: (0x0,0x8,0x1,0xc00fff00,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x073CF400,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x99005544,0x0,0)
AMBA_Check_State: (0x073CF4B4)
State is LOAD
AMBA_Check_State. (0x1)
Found 1 AMBA device!
AMBA_USB_Dev_Scan.
Reinit start wait.
[0] Found.
[0] AMBA_USB_Reinit_Wait. (0)
AMBA_Load_Kernel: (0x5)
AMBA_Load_Kernel_File: (0801-244-2212-20130821-NO1-SPI-1CARD-2710-NOGPS-M8452-NE
UTRAL.e2b,0x0714F09C,0x2,0xc0100000,0x0)
AMBA_Load_File: (0801-244-2212-20130821-NO1-SPI-1CARD-2710-NOGPS-M8452-NEUTRAL.e
2b,0x00000000,0x0714F010)
AMBA_Load_File. (0)
AMBA_USB_Simple_Send: (0x05120020,4723168,0x2,0xc0100000,0x0)
AMBA_USB_Simple_Command: (0x0,0x2,0xc0100000,0x0,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x1,0x19d1d629,0x0,0x0,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Data: (0,0x05120020,4723168)
AMBA_USB_Simple_Data. (0)
Wait for CRC (3000 ms)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Send. (0)
0801-244-2212-20130821-NO1-SPI-1CARD-2710-NOGPS-M8452-NEUTRAL.e2b sent, size=472
3168
AMBA_Load_Kernel_File. (0)
AMBA_USB_Simple_Command: (0x0,0x8,0x1,0xc0100158,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x0714EFB8,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0xeb000187,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x1,0xc010015c,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x0714EFB8,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0xeb001df0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x1,0xc0100160,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x0714EFB8,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0xe1200070,0x0,0)
AMBA_Patch_FWPROG: address=0xc0100160
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc0100160,0xe3a04103)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc0100164,0xe12fff14)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a0000,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a0004,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a0008,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a000c,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a0010,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a0014,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a0018,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a001c,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a0020,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a0024,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a0028,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x8,0x2,0xc00a002c,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
AMBA_USB_Simple_Command: (0x0,0x15,0x0,0xc0100000,0x0)
AMBA_USB_Simple_Command. (0)
AMBA_USB_Simple_Response: (0x00000000,0x00000000)
AMBA_USB_Simple_Response. (0,0x55525350,0x0,0x0,0x0,0)
Wait firmware programming...
=>Estimation(300000ms)


As far as i can see it goes wrong before or right after flashing the kernel file.
 
Last edited:
Gonna compare it with a successful flash...

Um.. you wrote "kernel file".. Did you choose the kernel option?
 
No i choose the elf file. it should be in the list. Probably the kernel is the first thing it starts with.
 
I'm talking about the Direct USB Option, did you choose the yellow one?

looklikethis.PNG
 
All the settings are the same in my directusb window. I copy paste the debug output in my previous post. Can u post your debug output?
 
If you want fun, get an uart to USB converter cable and solder it to the Board :)
 
Are there any more .elf files available i can try before i send the dvr back to givoe? In my original post u can see the files i have already tried.
 
Back
Top