Simple tool for viewing of Bada firmware

Search This thread

Shoorik29

Member
Dec 26, 2011
5
0
Rostov-on-Don
Попробуй просто расшифровать и потом зашифровать файл на третьей вкладке, не устанавливая чек бокс на wave3, затем подпиши и попробуй прошить. Результат сюда.

Сделал всё как сказал(дамп не делал),rc1 прошился.
 

ho1od

Senior Member
Jan 12, 2008
271
675
Значит, это просто ошибка при прошивке. Сбой мультилоадера. Попробуй еще раз прошиться.
 

Shoorik29

Member
Dec 26, 2011
5
0
Rostov-on-Don
Значит, это просто ошибка при прошивке. Сбой мультилоадера. Попробуй еще раз прошиться.

Родной rc1 шьётся без проблемм,а перепакованный нет.
Пробовали уже раз 7,а то и больше.

---------- Post added at 05:07 PM ---------- Previous post was at 05:03 PM ----------

Ещё попробую
 

AeroxTobi

Senior Member
Apr 13, 2012
65
6
Neuburg a. d. Donau
I dont understandt...

please write it in english this is english forum...

The RC1, SHP APP, FFS Data can not Flash!
It come Write Error...
CSC flashing is not Problem.. but the other data..
 

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
@ S8600 and or S7230 Value Pack User...

Please...
Upload examples or post MORE details!

It is impossible to find solution... if you write only.
I can't flash RC1, SHP APP, FFS....

This is useless blabla...

Lets start with SIMPLE task... Create valid PFS file for S8600 and/or S7230...

Attached file is S8500 compatible...

If PFS work... then theory Create FFS is not far...

So step by step... we could find solution. :cool:

Best Regards
 

Attachments

  • pfsTEST1.rar
    579 bytes · Views: 110

AeroxTobi

Senior Member
Apr 13, 2012
65
6
Neuburg a. d. Donau
Download Start Ch[0]
ERR : NAK_FLASH_ERROR 0
Error : PFS Write [0.2s]

Come when i will Flash the Test PFS on my Wave 723 Value Pack...

//Edit

All Errors on my Flash what come... on my Wave 723 Value Pack ( Bada 2.0 )


74% come:
ERR : NAK_BAD_SEC_CODE 0
Error : Rsrc1 Write [44.1s]

ERR : NAK_INVALID_FCS 0
Error : FFS Write [2.1s]

62% come:
ERR : NAK_INVALID_FCS 0
Error : CSC Write [39.3s]

ERR : NAK_INVALID_FCS 0
Error : SHPAPP Write [0.2s]
 
Last edited:
  • Like
Reactions: adfree

ho1od

Senior Member
Jan 12, 2008
271
675
AeroxTobi

You encrypt files after a build? It is not necessary. Everything is done automatically.
 
  • Like
Reactions: adfree

AeroxTobi

Senior Member
Apr 13, 2012
65
6
Neuburg a. d. Donau
I have Encrypt:
RC1 -> 99% NAK_BAD_SEC 0
SHPAPP -> 86% NAK_BAD_SEC 0
FFS -> 90% NAK_BAD_SEC 0

I haven't Encrypt:
RC1 -> 75% NAK_BAD_SEC 0
SHPAPP -> 1% NAK_BAD_SEC 0
FFS -> 43% NAK_BAD_SEC 0


Is it due to my PC?
or is it due Wave Remaker?
 

Gunter33

Member
Apr 29, 2012
43
62
First of all, many thanks to ho1od for your efforts.

I just made a dump with the files using Wave_Remaker_NEW_2_0_7_4 and 0_2_8.
No changes, simply saved them again:

PFS_S8600_Open_Europe_Common_XXLA1.pfs is 3.654.656 bytes large
PFS_S8600_Open_Europe_Common_XXLA1_new.pfs is 3.654.656 bytes large

ShpApp_HD.app is 81.445.888 bytes large
ShpApp_HD_new.app is 81.445.888 bytes large
The new ShpApp and PFS are flashable on the Wave 3.

CSC_S8600_DBTLB1.csc is 40.821.764 bytes
CSC_S8600_DBTLB1_new.csc is 48.423.940 bytes
The new CSC is almolst 8 Mbytes larger.

Rsrc_S8600_Open_Europe_Common.rc1 is 40.371.200 Bytes
Rsrc_S8600_Open_Europe_Common_new.rc1 is 50.594.816 Bytes
The new Rsrc is more than 10 Mbytes larger.

It's not possible to flash the new CSC and Rsrc on the Wave 3.

Another test for the FactoryFs_S8600_Open_Europe_Common.ffs from the S8600XXKJC_OXA:

FactoryFs_S8600_Open_Europe_Common.ffs is 53.871.616 Bytes
FactoryFs_S8600_Open_Europe_Common_new.ffs is 53.888.000 Bytes
Compared to WInHex, 49.972.662 Bytes are not identical.

I hope you go on exploring and wish you good luck.
Again, ho1od, thanks a lot for your efforts.

Kind Regards.
 

SpiritOfVite

New member
Apr 30, 2012
1
3
Hi ho1od

I've tested PFS flashing yesterday.

I think there must be a bug present in some large files about 10MB.

I uploaded my Test Files at Rapidshare.com

A working PFS File:
h**ps://rapidshare.c*m/files/2372542527/PFS_S8600_Open_China_LD1.pfs[/url]
9.94 MB (10'424'320 Bytes

Download Start Ch[0]
PFS 10420.2KB OK[24.3s]
All files complete[24.9s]


A non working PSF File:
h**ps://rapidshare.c*m/files/1254382320/PFS_S8600_Open_China_LD1_NON-working.pfs
10.0 MB (10'489'856 Bytes)

Download Start Ch[0]
ERR : NAK_BAD_SEC_CODE 0
Error : PFS Write [23.9s]


In SystemFS\Media\Sounds\Ringtones you should find some Trash Files. In non-Working Version is an 64.0 KB (65'536 Bytes) File extra


Tested with:

Wave_Remaker_NEW_0_2_8.exe
Wave_Remaker_NEW_2_0_7_3.exe
Wave_Remaker_NEW_2_0_7_4.exe

This Files should work in China and DBT Version. I have only added the Missing SamsungLBS Files from DBT in China PFS
 
Last edited:

hero355

Senior Member
Dec 10, 2011
1,674
1,882
Baku
All New Wave Remaker Can't open S5250 .FFS file.And Remaker Can Open and saving rc1 file.But RC1 giving error on Multiliader :confused:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 26
    This is a my program for viewing of bada firmware.




    This source code
    22
    This source code Wave_Remaker. Everyone can use it in their programs. Everyone can continue to develop this program. Thanks to everyone who helped me. Goodbye Bada.
    16
    Update v 0.0.3

    New features:

    Added decrypt and encrypt files (apps_compressed.bin , boot_loader.mbn)

    The program can be downloaded in the first post

    Attention! Encrypted files are not signed


    PS

    This is a picture from the decrypted Loader :)
    13
    update 0.2.0
    Only for test

    Added QMD routines from b.kubica
    Added tooltips wish file size
    Added few bug fixes

    Thank you b.kubica
    12
    bada 2.0 has enabled signature checking. as we know last 0x10 bytes of encrypted data are stored in footer at offset 0x198. Next 0x40 bytes is rsa signature taken from sha1 hash of 0x160 bytes (in footer 0x48-0x1A7).
    No chance to generate valid signature but we can reverse this pattern and modify encrypted data to pass rsa1 signature check :)

    3 things needs to be done to pass BL security:

    1. rsa signature needs to be valid (in footer)
    2. last 0x10 bytes of encrypted data must be equal to 0x10 bytes at footer offset 0x198
    3. last 0x10 bytes of decrypted data must be equal to 0x10 bytes of seed key (FF FF FF FF ...)

    attached routines does that - encrypted apps pass BL security checks and we can download it to phone with no problems. We lose 0x10 bytes of nand apps space but who cares? :)

    regards,
    Bartek