[App] Ambarella A2 RomKitchen v0.7 (discontinued)

Status
Not open for further replies.
Tobi@s

Tobi@s

Well-Known Member
App Developer
Joined
Nov 12, 2013
Messages
1,379
Reaction score
845
Location
Remote
Country
Germany
Dash Cam
none
Please don't use this application anymore! Move to this thread instead:
http://dashcamtalk.com/forum/threads/app-a7tool-v0-5.6029/

This project has been discontinued!
Click to expand...

Hello,
according to the progress made in this thread: http://dashcamtalk.com/forum/threads/mini0801-hacking-hardware-and-software.3157/ I decided to create a new thread for the application I developed. It's called Ambarella A2 RomKitchen and was made for modifying A2 firmware binaries (only tested with Mini0801 yet).

045.png


General usage:
start it using this command (only if you use the .jar version): "java -jar AmbaRomKitchen-v03-out.jar start"
Always do it this way:
1. File -> Open
2. Export -> All
3. RomFS -> Export files
4. Modify files (wdir=[location where your fw binary is located]/rfs/)
Info: Keep the filename. Please don't rename the file. You'll get a semibricked device if you do.
Protip: Always save logos with Paint because it removes EXIF information.
5. RomFS -> Build RFS
6. RomFS -> Include in fwbuilder
7. Build -> A2 Firmware
8. Built Firmware is located in the sections directory (sections/fwcompiled.bin)

Functions:
-Analysing fw binary
-Export fw parts (header + sections)
-Export all files from RFS section
-Rebuild RFS using exported/maybe modified files
-Rebuild Firmware
Info regarding modifications:
If you modify any section manually (without my tool) always add a zero-byte at the end of the section. every section has to end with a zero-Byte, because it's the identifier for the tool.

Coming soon:
-strings.bin editor
-fonts.bin editor
-bitmaps.bin Editor

Requirements:
-firmware binary (http://dc.p-mc.eu/?page=mini0801.firmware)
-Java JRE min 1.7 or JDK min 1.7 (http://java.com/download)

Releases:
Windows:
v0.7 (.exe): http://dc.p-mc.eu/dl/get.php?f=RomKitchen07exe
Other OS:
v0.7 (.jar): http://dc.p-mc.eu/dl/get.php?f=RomKitchen07jar

Changelog:
v0.7:
-fully functional strings.bin editor included
v0.6:
-version is not public
-Some algorithms where rewitten
v0.5:
-Fixed some GUI bugs
-Fixed a logical error regarding romfs file counting
-Added Support for latest A2 firmwares (2014/02/22 for example)
v0.4.5:
-more noob friendly information texts
-modified shortcut menu (Quick FS Editor)
v0.4.1:
-fixed several bugs
v0.4:
-added shortcut for quick boot/shutdown logo change
v0.3.2:
-fixed the Export failure
v0.3.1:
-fixed a permissions problem (missing manifest for Windows UAC)
v0.3
-Initial fully functional release

Protip:
Always have a USB -> mini USB cable with PIN 4 and 5 linked ("burning cable")

Random Info:
12568 lines of code (excluding empty lines), 90 classes, 16 packages (including res)

Validation:
You don't trust me/my tool? :(
There is an easy way to validate the generated firmware: Decompile the modified Firmware, if there occurs no error, everything should be fine!

Disclaimer:
I am not responsible for any bricked devices, dead SD Cards or anything else that might happen as a result of flashing firmwares you modified with this tool to your dashcam.
 
Last edited by a moderator:
Thanks!

Questions..

I think I remember that the splash screen files must be 838x633 pixels in jpg format. You're saying the replacement splash screen needs to be saved in MS Paint and named logo.jpg; this file then replaces the fw splash screen also named logo.jpg?

How does one modify the fw version for 'no sound', or substitute sound files?
 
Last edited:
The answer to your first question:
After unpacking the romfs you'll get a folder called "romfs" which contains all the files from the filesystem. The files have this format: fileID___filename.Extension
If you want to Change the bootlogo and shutdown logo you have to delete 03___logo.jpg and 06___logo_off.jpg, move the new logo to the Folder and then rename it to 03___logo.jpg and 06___logo_off.jpg. Then you can build the rfs section with the modified files.

question 2:
Create an empty file for the responsible Audio file and replace it.
You can use this command: fsutil file createnew 12___poweron12k.pcm 1000
It will create a new file called 12___poweron12k.pcm with a filesize of 1000 bytes
 
D:
Got that error, too. But I fixed it when I started it using the command java -jar ... and not the exe file.thats really strange. Only get it when I dont start it via commandline.

Did you use exe or jar?
 
Oh, that was my next question... How do I start it from within Windows?

I had assumed you started it from the command line prompt, so I was running AmbaRomKitchen-v03-out (Executable Jar file) from the cmd.exe.
 
Well it's really strange. It's working for me when I start it via commandline but it doesn't when I start it using another way.
+It works using ecplise build&run withour commandline args. Maybe I'm too tired now to see the Problem. Will try to fix it tomorrow.

Maybe it helps when you try to run it directly from C:\ ? If you want to try it...
 
I have tried the RomKitchenv03 but I get an empty directory for the romfs????

upload_2014-2-2_11-32-25.pngupload_2014-2-2_11-32-51.png
 
Seems I have to check my code again.. Strange thing is that it works for me. _.
 
I am running the execuatable version, are the commands the same as for the JAR version? I assume they are:-

General usage:
start it using this command (only if you use the .jar version): "java -jar AmbaRomKitchen-v03-out.jar start"
Always do it this way:
1. File -> Open
2. Export -> All
3. RomFS -> Export files
4. Modify files (wdir=[location where your fw binary is located]/rfs/)
Info: Keep the filename. Please don't rename the file. You'll get a semibricked device if you do.
Protip: Always save logos with Paint because it removes EXIF information.
5. RomFS -> Build RFS
6. RomFS -> Include in fwbuilder
7. Build -> A2 Firmware
 
Yes, it's exactly the same application but with launch4j wrapper
 
Temporary fix for now: Run the .exe as admin or Launch it from an admin cmd Window. No idea why this requires administrative privileges and sectrion Export not.. Please try
 
I now builded the exe tool with a manifest that tells windwos to use higehst available permissions. This fixed the export failure for me. (still no diea why this requires administrative privileges).
If your Windows account is a local admin, just doubleclick the exe, if you account is no local admin run it as Administrator.
v0.3.1: http://dc.p-mc.eu/dl/get.php?f=AmbaRomKitchen-031-exe
 
Always have a USB -> mini USB cable with PIN 4 and 5 linked ("burning cable")
Is there DIY cable or where can I buy it?
 
http://dashcamtalk.com/mini-0801/#Unbricking_the_Camera
Basically it is a cable you can always unbrick your camera with. It's a normal USB -> MiniUSB cable (like the one shipped with the camera) and on the MiniUSB-end pin 4 and 5 are soldered together. It's a very easy DIY task.
 
It is not so dead simple:
usb_cable.jpg
 
I did it a bit different:
If you look close enough you'll see it

P1020810.jpg
 
The .jar file download, I'm getting a "Invalid download token...." trying to download it.

Windows exe, I'm on Windows 8.1 64bit, and still getting the same error when trying to export the romfs.
 
Have you tried starting it as administrator?
 
Tobi@s said:
Have you tried starting it as administrator?
Click to expand...

Yes I have, same issue.
I'm going to try on Windows 7 32bit laptop now.

Update: Same isue, Java.IO.Exception error, file path not found.
 
Last edited:
Status
Not open for further replies.
Back
Top