yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 General] ejectedmatrix:
This thread is like a discussion thread for the SM-N910T3 Model of the Note 4, I am going to edit this later, and add any crucial links that may be useful, I wish they could add a separate discussion area for this model.

The T3 model has a feature called FRP (Factory Reset Protection) That is pretty much an unlockable bootloader.

TO GET PAST THE "CUSTOM BINARY BLOCKED BY FRP" MESSAGE, FOLLOW THESE INSTRUCTIONS:

Go with stock ROM for the T3, and go to about device, and go unlock Developer Options, search it up if u don't know how to, after that , look for an option called OEM unlocked, and turn it on. To make sure that you don't have FRP on (Factory Reset Protection), go to download mode (odin mode) and look at the info and look for FRP lock, make sure it says FRP LOCK: OFF.

Please PM me if you have any problems!!!!

So yeah Ima edit this later and then yeah u get the idea.:)
[Galaxy Note 4 General] ejectedmatrix:
[RESERVED]
[Galaxy Note 4 General] ejectedmatrix:
[reserved] 1
[Galaxy Note 4 General] ejectedmatrix:
[reserved] 2
[Galaxy Note 4 General] ejectedmatrix:
[reserved] 3
[Galaxy Note 4 General] ejectedmatrix:
[reserved] 4
[Galaxy Note 4 General] ejectedmatrix:
[reserved] 5
[Android Head-Units] koti:
This thread I started to get some help for custom roms for witson head units. This HU similar to MTCB with Configuration OS Android 4.4.4 system CPU Rockchip 3188(PX3) Cortex A9 Quad*coreRAM DDR3 1GBFlash Built in 16GB , But cannot be installe custom roms of malaysk .

I tried various ways to flash but has not worked yet. I am not a developer so would not able do much.

There is no way to enter recovery by buttons , I tried everything I could as per instruction from [ROM][RK3066/RK3188][SD/HD] Malaysk ROMs thread.

I tried these after getting latest factory firmware for back up.

1] extracted custom romes and replaced boot, system, oem and misc img files in stock firmware folder and flashed,

everything works but stuck at recovery. did clean wipe and install from storage but sd card does not show or failed to mount. please check pics.

2] when reboot at that stage , it starts without problem but no sound , what might be the problem? it reboots itself every 2 minutes!!

3] thought reinstall MCU but factory setting password does not work tried 126/ 3368 (stock rom code), is there any workaround.

I feel some problem may be due to mixing up stock firmware and custom firmware file( I don't understand as i am not a developer) . Attached stock firmware folder sceenshot, can anyone suggest how to manage these files.

Russian forum has a thread on these units but no much progress.

can anyone help me out to flash custom roms.

I attached couple of pics and firmware details with factory firmware link thanks to 4pda.

Latest firmware

Older Factory Firmwares download link
[Android Head-Units] henri_p:
please check the below link to update your device

https://www.youtube.com/watch?v=xTozK6aDc1E&feature=youtu.be

are you sure the firmware you post is correct?
[Android Head-Units] koti:
Yes, I got it from witson seller and it works great. there is no separate mcu file .

but both are included in single firmware folder.
[Android Head-Units] derici84:
are u sure u put the sd cart on gps slot couse on my device if i pull out the sd card from gps slot on recovery mod it says no such device same as ur picture
[Android Head-Units] koti:
Yes, I do use the sdcard slot to update. for stock rom update, we need insert into sdcard slot( GPS Slot) then restart the unit. then it updates automatically till the end before reboots, it says to remove sdcard. once sdcard removed it reboots thats it. it never stops at recovery mode while factory firmware update.

I cannot use update.img file to update firmware.

I cannot enter recovery mode by pressing any buttons even I tried on pcb board, do you have any idea to overcome it?

yes i could root it with kingsroot.

I am looking for a custom rom like malaysk kind of to flash. I am waiting for someone who could help.
[Android Head-Units] derici84:
Try another rom friend maybe something wrong on that rom did you try malaysk rom for ur device ?

---------- Post added at 05:31 PM ---------- Previous post was at 05:09 PM ----------

Get into recovery

Try this

1 Press reset button and power button together

2 After about 5 secs release reset button, but keep pressing power button

3 When booting screen appears release power button.

4 It boots into recovery.

--Update 1-- some units without front USB have a different procedure

Firstly power on the unit and then long press the power button and then reset. Then the unit will get three rings and you loose your hand on the power button and short press the power button again. (thanx [MENTION=5917532]netay[/MENTION])

--Update 2-- some others have this procedure (thanx [MENTION=1436975]R4D3N[/MENTION])

1. Turn off the unit by holding 3-4 sec the power button.

2. Hold the RESET button + POWER button for 5 sec

3. Release the RESET button and keep pressing the POWER button for 2 sec

4. Release the POWER button and wait. The Recovery menu appears.

5. With the Volume knob you can move up/down and long press on Volume/Power button to select the option.

And download malaysk rom for ur device

Find resolution and chip model dont flash wrong rom
[Android Head-Units] koti:
I tried different roms fused/normal older/newer . flashing format for this model is different . check screen shot of firmware folder in my first post. Thanks

I did most the procedure you suggested but still i would try once again in couple of days.

I asked many times supplier as well , he said it is not possible to enter recovery. thanks mate
[Android Head-Units] derici84:
i really wanna help but i have nothing

i have a head unit which brand is android navimex 4.4.4 and its rk3066 800x480 i bought it in my country (Turkey) and i tried to flash malaysk rom and its done working nice and no problem

but how comes its imposible to get recovery couse its android and i am sure there is way to get recovery mode

what if u try to flash with computer on usb port i think u should check it friend
[Android Head-Units] ufo01:
Hello, I have the same problem I cannot enter in recovery mode and install custom roms of malaysk .

I have a Witson W2-F9111T.

who could help me
[Android Head-Units] henri_p:
there is no recovery implemented, no fastboot.. so I have no idea how to flash those
[Android Head-Units] CadillacMike:
aren't the Witson head units the same as the RoadNavi S160? if so, then Kotix makes a ROM for them, check the S160 thread
[Android Head-Units] henri_p:
Could you share the instructions you got from the seller?.

I'm also in the same lane, I cant seem to find any custom rom for my device, the good part though is that our hardware is way better :p

Now i have plenty of small issues, so I want to flash the original rom back.

Thanks !
[Android Head-Units] koti:
1) Format a blank SD card to FAT32 .

2)Copy all files from UI folder to root direction of sd card.

3) Insert sd card to GPS card slot.

4) press reset button with pin/toothpick the device and power on dvd

5)The screen should appear updating windows and updating work automatically .

6) After updating work finished, remove sd card and power on DVD.

Hope this works for you good luck
[Android Head-Units] henri_p:
Found this already on the russian website.

I think we CAN use malaysk rom if we use just the system image, and keep our uboot and MCU.

Will try this out and feedback here.
[Android Head-Units] koti:
Please let know your work thanks
[Android Head-Units] henri_p:
http://4pda.ru/pages/go/?u=https://yadi.sk/d/trtQM-26u7dtA&e=52041559

there "seems" to be a 5.1 release, however the build.prop shows 4.4.4 ?
[Android Head-Units] rocker2016:
Do you have firmware 5.1.1 from Witson?
[Android Head-Units] dawcior-al:
I've updated my radio to 5.1.1. In my opinion nothing has changed, besides the information in the settings version of android 5.1.1

I think this is an old android only has written 5.1.1. The system looks the same as when you press the Application Manager can see the logo android 4.4 kitkat on the notification bar.
[Android Head-Units] henri_p:
I think it's a hacked 4.4 to show 5.1

If you look in the build.prop of the download then it clearly shows a 4.4///

aaah... typical chinese cheating here, even on a firmware
[Android Head-Units] dawcior-al:
Yes, i see build.prop earlier :)

As such a large company can just cheat customers.
[Android Head-Units] ozzyboy:
Anyone found a way to get into recovery mode... Also I have a Witson Head Unit (a5308 with ll5. 1) and I can't get into recovery mode... I tried allways posted here an all founded on YouTube... None of all this methods works.

Thx!
[Android Head-Units] ivo1bg:
Hi. I have a HU with this info in About Device like in the pic and I think that my unit is Witson. A week ago I tried to update the ROM, but the only thing that happened was that I have a black screen now. I tried to update the unit with 5 or 6 different OEM ROMs but without any success. The screen is still black. Sometimes the light of the buttons blink and that's all. Could someone describe me how to bring back this device to life?

[IMG="Witson"]http://pics.data.bg/storage/pics/1860887/32222/1da5adb728f7b979b52b24508ae354bb[/IMG]
[Android Head-Units] aubreykloppers:
Did you ever get your black screen sorted out?
[Android Head-Units] wifi75:
I would lik to update my witson px5 to oreo.

But the sd card with inside new recovery after reboot not star update automatically.

why?
[Android Head-Units] Clandaries:
Are there updates?

MCU and Firmware?

Regards
[Android Head-Units] BillTheCat:
I'm also looking for a firmware update.

I recently purchased a Witson 8236 (BMW CIC for F12/13) 10.25" Android 8.1 from someone pre-owned and I'm having trouble with error messages from the car related to my headlamps, and the iDrive controller doesn't work in Android at all.

Is there a place where we can download the latest firmware?

MCUVer: 615043bALS-CIC-HW7-190109[B1280_170325]

FrameworkVer: 8.1.0 OPM5.171019.019 eng.zxw.20181228.162012

AndroidVer 8.1.0

APPVer: 2019012501_1280x480_970

Nandflash: 24.34G/25.33

RAM: 2G

Build number

rk3399-userdebug 8.1.0 OPM5.171019.019 eng.zxw.20181228.162012 test-keys
[Android Q&A, Help & Troubleshooting] GraysonPeddie:
Softkey Enabler app from the Play Store prevented my phone from booting up and I have created a backup of all my user data and the stock recovery split the backup into four files:

userdata_20160421_162907.backup (2.1GB)

userdata_20160421_162907.backup2 (2.1GB)

userdata_20160421_162907.backup3 (2.1GB)

userdata_20160421_162907.backup4 (~200MB)

I wish I could use adb to restore the file, but it got stuck in the boot stage after the animation and won't get me to the home screen. I have no CWM or TWRP installed. I rooted my phone using KingRoot. I can't even unlock the bootloader for some reason; I tried "fastboot oem unlock" and the only option is "no," so pressing the "volume up" button does not work. The volume up key works in recovery screen, however. I'm not sure why the volume down key only works in bootloader.

I went into the thread more than a half an hour ago and when I execute the following command, it tells me it's not in gzipped format:

[grayson@htpc android-backup]$ dd if=userdata_20160421_162907.backup bs=512 skip=1 | gunzip -c | tar x

gzip: stdin: not in gzip format
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors

I am running Linux in my desktop, so any ideas on how I can resolve my problem?

And is there any reason why I cannot press volume up to confirm that I want to unlock my bootloader?
[Android Q&A, Help & Troubleshooting] GraysonPeddie:
I have a video posted in YouTube demonstrating that I cannot get my smartphone to unlock. Please pardon me for bumping my thread, but I hope this video can help:

https://www.youtube.com/watch?v=WuDIR-_BPFM
[Android Q&A, Help & Troubleshooting] GraysonPeddie:
I want to report in my progress that I've ordered a Nexus 6P from Project Fi and will retire my hard-bricked BLU Studio 6.0 HD. SP Flash Tool is no help with DRAM failure even with a correct ROM.

https://plus.google.com/u/0/+GraysonPeddie/posts/Z7cZcACdUez
[G3 Themes and Apps] macdaddie87:
I am working on a mod of the dialer to look more like the G5 the only problem i am having is editing the status bar color of the messenger and dialer/contacts app. Does anyone know how to do this to the apps themselves without xposed? I am not sure if its an xml thats making it not seemless or what.

I want to make it a seemless transition to where the app and status bar is the same color.

View attachment 3726582
[G3 Themes and Apps] marinalin85:
Decompile both of them and look in the Manifest for the first activity that has a style. After you found that, go to res/values/style and search for that specific style. Then add this line

<item name="android:statusBarColor">#ffff0000</item>
[iPAQ rw6828, XDA Atom Software Upgrading] scorpio16v:
Hi

I have the new XDA Comet (same as XDA Atom Life) with WM6 in german.

I've dumped the ROM with pdocread. All you need is mamaich's imgfs tools to extract its contents.

Version is OS 5.2.1616 (build 18120.0.4.0) it's the same build like the english Atom Life WM 6 Rom, but maybe you'll build a german ROM. :D

Anyway, if someone is interested, here is the download link:

http://rapidshare.com/files/62060494/XDA_Comet_german.rar.html
[iPAQ rw6828, XDA Atom Software Upgrading] jiggs:
hi scorpio16v,

thank you very much for the ROM dump. can you share how you managed itsutils to work with your xda comet?

i have tried various ways... only pdocread -l works on our Atom. other tools didn't work, and yes I have installed enbalerapi.cab before using the tools.

i'm hoping your solution would be similar to our Atom. if this will work, we can change bootscreen and pagepool without reflashing...

regards,

Jiggs

here's a dump of pdocread:

60.86M (0x3cdb000) MSFlash
| 1.24M (0x13e000) Part00
| 3.25M (0x340000) Part01
| 56.36M (0x385b000) Part02
43.99M (0x2bfd400) TrueFFS
| 43.99M (0x2bfc800) Part00
15.61M (0xf9c000) DSK2:
| 15.61M (0xf9bc00) Part00
127.50k (0x1fe00) DSK3:
| 127.00k (0x1fc00) Part00
STRG handles:
handle c3c31bba127.00k (0x1fc00)
handle 03f802ca 15.61M (0xf9bc00)
handle c3f80686 43.99M (0x2bfc800)
handle 63f957b2 56.36M (0x385b000)
handle a3f9578e 3.25M (0x340000)
handle 03f95666 1.24M (0x13e000)
disk c3c31bba
3 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 03f802ca
3 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c3f80686
3 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 f0 36 02 01 08 27 07 24 1a 0b 05 c4
disk 63f957b2
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a3f9578e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 03f95666
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[iPAQ rw6828, XDA Atom Software Upgrading] scorpio16v:
As I said, I'm not very experienced in such thinks, it's not my own solution.

The way, I managed the dump, you can find posted by Oki in the Mio forum.

Here is the link:

http://www.miousers.co.uk/viewtopic.php?t=426&postdays=0&postorder=asc&highlight=pdocread&start=15

Hope you have success, because the output from pdocread -l is different to this from my Comet.

C:\itsutils\build>pdocread.exe -l
79.92M TRUEFFS
| 1.12M Part00
| 1.69M Part01
| 77.11M Part02
797.66M TRUEFFS
| 1.12M Part00
| 1.69M Part01
| 77.11M Part02
63.94M TRUEFFS
| 1.12M Part00
| 1.69M Part01
| 77.11M Part02
STRG handles: 23bd9a56
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
( 35.96M) 83f93f52
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
(796.88M) 03f931ca
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
( 77.11M) 63facfbe
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
( 1.69M) 83facf9a
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
( 1.12M)

C:\itsutils\build>

Just to make it comlete I attach the two other dumped parts. As I understand that must be the two XIP parts, right ?

But where are the ExtROM ? May be we must unhide it ?

Bootloader and Radiopart are also missing.

I think I could dump the rest with Haret, I hope so.:)

Parts_00_01
[iPAQ rw6828, XDA Atom Software Upgrading] jiggs:
The Atom Life has a 36mb extended ROM image... this will give you a clue now.

Thanks for the mio lead. I'll try to check that out.
[iPAQ rw6828, XDA Atom Software Upgrading] scorpio16v:
yes, that might be this:

4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
( [B]35.96M[/B]) 83f93f52

But I have no clue, how I can take access to this file. :confused:
[iPAQ rw6828, XDA Atom Software Upgrading] scorpio16v:
Ok,

some times I need some more time to understand. :D

I've the damned ExtROM

At first I get the latest itsutils, not longer the old one, that I've used.

C:\itsutilsbin-20070705>pdocread -l
79.92M (0x4fec000) TRUEFFS
| 1.12M (0x11fc00) Part00
| 1.69M (0x1b0000) Part01
| 77.11M (0x4d1c000) Part02
797.66M (0x31da8000) TRUEFFS
| 1.12M (0x11fc00) Part00
| 1.69M (0x1b0000) Part01
| 77.11M (0x4d1c000) Part02
63.94M (0x3ff0000) TRUEFFS
| 1.12M (0x11fc00) Part00
| 1.69M (0x1b0000) Part01
| 77.11M (0x4d1c000) Part02
1.89G (0x79280000) DSK1:
| 1.89G (0x79120e00) Part00
STRG handles:
handle c3face7a 1.89G (0x79120e00)
handle [B]03fc3fae[/B] 35.96M ([B]0x23f6400[/B])
handle a3f93f52796.88M (0x31ce0000)
handle 63f931ca 77.11M (0x4d1c000)
handle c3facfbe 1.69M (0x1b0000)
handle c3facf9a 1.12M (0x11fc00)
disk c3face7a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 03fc3fae
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
disk a3f93f52
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
disk 63f931ca
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
disk c3facfbe
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98
disk c3facf9a
4 partitions, 3 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 67 28 02 01 03 13 14 5f 19 0b 06 98

This is the damned ExtROM. And that's the way I get it:

C:\itsutilsbin-20070705>pdocread -h 0x[B]03fc3fae[/B] 0 [B]0x23f6400[/B] Ext_ROM.raw
CopyTFFSToFile(0x0, 0x23f6400, Ext_ROM.raw)

I think you can get the other parts in the same way. :)

Now, I need some help to make this flashable for german Atom Life user.

Comet_ExtROM

You can open it with WinImage.
[iPAQ rw6828, XDA Atom Software Upgrading] jiggs:
great! unfortunately, it did not work on my Atom. How do I know I have the latest version of itsutils? :(
[iPAQ rw6828, XDA Atom Software Upgrading] scorpio16v:
You can download the latest version from "itsme's" page.

The latest is "itsutilsbin-20070705".

Link:

http://www.xs4all.nl/~itsme/projects/xda/tools.html
[iPAQ rw6828, XDA Atom Software Upgrading] oswin:
Hi scorpio16v,

Can you post the steps that you did to dump the ROM from XDA Comet (Atom Life) please?

This is what I've done so far:

E:\Atom_Rom_Stuff\Utils>pdocread.exe -l
79.92M (0x4fec000) TRUEFFS
| 1.12M (0x11fc00) Part00
| 1.69M (0x1b0000) Part01
| 65.19M (0x4130000) Part02
797.66M (0x31da8000) TRUEFFS
| 1.12M (0x11fc00) Part00
| 1.69M (0x1b0000) Part01
| 65.19M (0x4130000) Part02
63.94M (0x3ff0000) TRUEFFS
| 1.12M (0x11fc00) Part00
| 1.69M (0x1b0000) Part01
| 65.19M (0x4130000) Part02
STRG handles:
handle 23fc3fae 35.96M (0x23f6400)
handle e3f93f52796.85M (0x31cd9c00)
handle 03f931ca 65.19M (0x4130000)
handle c3facfbe 1.69M (0x1b0000)
handle c3facf9a 1.12M (0x11fc00)
disk 23fc3fae
4 partitions, 3 binary partitions
customerid=060a0000 uniqueid= 00 00 0a 06 0f 36 0b f8 00 00 00 c3 00 00 00 ce
disk e3f93f52
4 partitions, 3 binary partitions
customerid=060a0000 uniqueid= 00 00 0a 06 0f 36 0b f8 00 00 00 c3 00 00 00 ce
disk 03f931ca
4 partitions, 3 binary partitions
customerid=060a0000 uniqueid= 00 00 0a 06 0f 36 0b f8 00 00 00 c3 00 00 00 ce
disk c3facfbe
4 partitions, 3 binary partitions
customerid=060a0000 uniqueid= 00 00 0a 06 0f 36 0b f8 00 00 00 c3 00 00 00 ce
disk c3facf9a
4 partitions, 3 binary partitions
customerid=060a0000 uniqueid= 00 00 0a 06 0f 36 0b f8 00 00 00 c3 00 00 00 ce

E:\Atom_Rom_Stuff\Utils>pdocread -w -d TRUEFFS -p Part00 -t
real nr of sectors: 2302 - 1.12Mbyte (0x11fc00)

E:\Atom_Rom_Stuff\Utils>pdocread -w -d TRUEFFS -p Part01 -t
real nr of sectors: 3456 - 1.69Mbyte (0x1b0000)

E:\Atom_Rom_Stuff\Utils>pdocread -w -d TRUEFFS -p Part02 -t
real nr of sectors: 133504 - 65.19Mbyte (0x4130000)

Am I on the right track?
[iPAQ rw6828, XDA Atom Software Upgrading] scorpio16v:
yes, that looks fine, but you can skip this step and try the following way for example:

pdocread -h 0x[B]03f931ca[/B] 0 0x[B]4130000[/B] Part02.raw

That will dump the imgfs part. For the other parts do the same way.

Please do the pdocread.exe -l again and compare the right datas.

And don't forget the 35.96 MB Part. It's the extended ROM.

Hope that'll help you.:)
[iPAQ rw6828, XDA Atom Software Upgrading] jiggs:
Hi,

Sorry, I only looked at this now. You just need to add a 12-byte header for this to work on normal flashing. You need to rename this to flash in bootloader mode. Unfortunately, I don't know what the name is. You can try to enter into bootloader mode and insert a blank miniSD. In the Atom, it lists all filenames it can't find though. Hope it works the same way as the comet.

cheers,

Jiggs

edit: a 1gb miniSD doesn't work. 512mb and 256mb miniSD works fine with SD card flashing.
[iPAQ rw6828, XDA Atom Software Upgrading] scorpio16v:
Thanks for your reply.

I've ordered an 256 MB MiniSD. Hope it works. :)

On Developers FTP there is an folder called "ATOMLife_MiniSD".

The text file inside says AL1.DIO is the OS image and ExRom.img is the name for the Extended ROM file. Hope it works.

Ok the way to flash the Extended ROM is now clear,

how can I restore the OS ?

The other 3 parts that I've dumped are the Imgfs and the XIP parts ? :confused:

Is it right, that I must merge the 3 parts with SPRX tolls from Scooter-Kitchen and restore the 12 byte header ?

An other question is, if it is possible to flash this via RUU ? And for what are the *.mbn files in the official Atom Life update ?

At first, I must find the way to restore my Comet with my Romdump.

Than I think an AKU 0.7.0 like your Atom ROM would be fine for the Atom Life /Comet too. :D