yashsingh1/xdaforums huggingface dataset:
[Android Development on Bada] mijoma:
Normally in the bootloader the sequence to run Download Mode looks like this:

maxim_charging_control(2,0);

disp_Dload_Init();

DloadMain();

For Upload to PC it's done like this:

DRV_Modem_BootingStart();

disp_Upload_Init();

FSA9480_ResetDevice();

Sycon_Power_off_exceptLCD();

Sycon_ARMCLK_Change(200);

maxim_usb_ldo_control(1);

UploadMain();

You may find the symbols' offsets in the elf or map file.
[Android Development on Bada] adfree:
Thank you very much mijoma :good:

I will try to understand this.

Found via text search in BL3_univ.map

DloadMain [B]0x42083c44[/B] ARM Code 880 dload.o(.text)
UploadMain [B]0x42084a80[/B] ARM Code 420 dload.o(.text)

With your Tool bl_crc.exe I can find CRC...

offset [B]0x42083C44[/B] -> CRC = 0x56A837AE
offset [B]0x42084A80[/B] -> CRC = 0xB599F72A

As help for noobs like me... maybe this is helpfull.

To generate first dummy file 0x42080000 then add BL3_univ.nb0

I will do this for me. :o

Then I can investigate by enter adresses from *.map file for educational purposes...

Best Regards
[Android Development on Bada] adfree:
Taken from XXLA1 S8500 BL3_univ.map

disp_dimming_backlight 0x420af87c ARM Code 28 disp_Lismore.o(.text)
disp_Main_Clean 0x420af898 ARM Code 56 disp_Lismore.o(.text)
disp_Main_Clean_All 0x420af8d0 ARM Code 44 disp_Lismore.o(.text)
disp_Main_Update 0x420af8fc ARM Code 188 disp_Lismore.o(.text)
disp_Main_Dload_DisplayFirst 0x420af9b8 ARM Code 564 disp_Lismore.o(.text)
disp_Main_Dload_Update 0x420afbec ARM Code 288 disp_Lismore.o(.text)
disp_Main_Dload_Message 0x420afd0c ARM Code 840 disp_Lismore.o(.text)
disp_Normal_Init 0x420b0054 ARM Code 44 disp_Lismore.o(.text)
disp_First_Image 0x420b0080 ARM Code 32 disp_Lismore.o(.text)
disp_Dload_Init 0x420b00a0 ARM Code 100 disp_Lismore.o(.text)
disp_TFlashDload_Init 0x420b0104 ARM Code 60 disp_Lismore.o(.text)
disp_Upload_Init 0x420b0140 ARM Code 100 disp_Lismore.o(.text)
disp_Dload_User_Init 0x420b01a4 ARM Code 36 disp_Lismore.o(.text)
disp_Dload_Fail_Init 0x420b01c8 ARM Code 36 disp_Lismore.o(.text)
disp_LPM_Init 0x420b01ec ARM Code 352 disp_Lismore.o(.text)
disp_FPM_Init 0x420b034c ARM Code 156 disp_Lismore.o(.text)
disp_FOTA_Init 0x420b03e8 ARM Code 52 disp_Lismore.o(.text)
disp_FOTA_Printf 0x420b041c ARM Code 88 disp_Lismore.o(.text)

Few I have tested as alternate "fun" :D for disp_FOTA_Init...

See post above...

CRC you can find via bl_crc.exe

Compatible at the moment only with DEcrypted boot_loader.mbn from S8500/S8530/M210S

Short tested with boot2.img (570 KB) from S5250... Broadcom device...

file too small

But this is from S8600 osbl.bin... XXKJC

offset 0x038D7EFA -> CRC = 0x45404D93
.
.

Best Regards

Edit 1.

I have wrong file choosen... the decrypted osbl.bin... so wrong output for S8600...
[Android Development on Bada] adfree:
Some ideas for FOTA...

Maybe allready released... no idea yet.

1.

Need way to erase some areas in 512 MB OneNAND...

I mean range between 0x400000 to 0x20000000

For example...

I have now 2x S8530 with M210S Firmware... and I can't go back... :crying:

S8530 apps_compressed is now not more valid...

2.

Start apps_compressed.bin without F%&& Security checks...

Example... Bootloader has all Display related settings...

If fu. Bootloader not more check last 1024 Byte... then for instance S8500 can run S8530/M210S or S8600 or S8000 apps_compressed.bin or S8500 XXJB6

With S8500 I could check... and repair with JTAG if something goes wrong...

Maybe someone has an idea... :angel:

Best Regards
[Android Development on Bada] Rebellos:
You could use this: https://code.google.com/p/badadroid/source/browse/trunk/FOTA/flash_write.ASM#65

Removing completely lines

BL	__PfsNandInit
BL	__PfsMassInit

MOV	R0, 12345
BL	int_debugprint

and

LDR	R0, [s_flashpath_a]
LDR	R1, [dump_buf]
LDR	R2, [dump_size]
BL	loadfile
LDR	R2, [dump_size]
CMP	R0, R2
BNE	fail

That would cause writing 0x00400000 0x00 bytes under 0x1F000000. You can also use Flash_Erase function instead of Flash_Write_Data

Flash_Erase though does take block number and block count as arguments.

Also remember that writing some areas with this method will cause code to hang. For eg. I think you shouldn't crossover different BML partitions with single write operation.
[Android Development on Bada] adfree:
Yes, it seems not easy with 1 click...

I have little progress in BL3 dload_nand_erase with Multiloader:

http://xdaforums.com/showpost.php?p=41287393&postcount=207

Need few more tests...

But it seems now I can use RC1 in Multiloader to erase from 0x00400000 to end of RC1... higher 0x19800000

Later I will try to identify RC2 start address... seems highest area...

with 0x1D900000

To find end addresses seems much harder for me... :o

Best Regards
[Android Development on Bada] adfree:
For some stupid tests I have reduced and removed some data from Original FOTA...

It seems I can overwrite all areas from 0 to end with 00...

Only text String seems mandatory, otherwise you got white Screen with missing FOTA info...

FOTA_ENGINE_VER_INFO_2.0

Tested with S8530 XXLA1... Wave starts normal...

Will do some more tests... later then with S8600...

Best Regards
[Android Development on Bada] adfree:
It seems S8600 is better secured... :o

Simple test with 2 files... nothing special...

First file is with 2 Text Strings..

FOTA_ENGINE_VER_INFO_2.0

Second file is complete empty... only 00...

Both files are valid... S8600 start normally...

Tested with:

XXKJ7
XXKJC

Will test again with XXLD1... but I think test is correct...

But maybe someone else can confirm please...

Command shows nothing in modified FOTA files , but in Original FOTA...

GetFotaEngineVer

So I am 93 % sure, there is NO Shadow Backup or my FOTA is ignored...

To be 100 % I need FULL dump... but I have found no way yet...

Best Regards

P.S.:

Here my testfiles for S5250 Broadcom...

http://xdaforums.com/showpost.php?p=42953648&postcount=62
[Android Development on Bada] adfree:
http://xdaforums.com/showpost.php?p=43056621&postcount=32

Here are testfiles for S7250 and S5830, if FOTA is higher secured like in S8600...

Waiting for answer...

Here is testfile for S5250...

http://xdaforums.com/showpost.php?p=42953648&postcount=62

Waiting for answer...

I will do such test files for all our Broadcom bada devices...

S8600 Qualcomm I am able to test self...

Maybe if time I will check M210S Firmware... only for fun.

Then we know if FOTA is only working for S8500 and S8530 as "OS Loader"...

Best Regards
[Android Development on Bada] adfree:
:good:

Nice. :cool:

http://xdaforums.com/showpost.php?p=43264974&postcount=35

Thanx rafaelvasconcelos

He confirmed that S5380 aka Wave Y is able to use ""modified"" FOTA.

I will wait for feedback of S7250 users

For now I now only both have same resolution:

And both are Broadcom based...

So maybe Wave M and Y users should work together.

Best Regards
[Android Development on Bada] hero355:
As my tests I can say Wave M and Y are very close as S8500 and 8530 :o
[Android Development on Bada] adfree:
For study I will try with M210S KRLC1 Boot...

Step 1.

bl_crc.exe :good:

So I have adresses and CRCs

My result is attached.

Few tests before:

http://xdaforums.com/showpost.php?p=40583484&postcount=41

Step 2.

I will generate dummy file for study... to understand addresses and maybe understand how CRC is generated...

http://xdaforums.com/showpost.php?p=40702051&postcount=204

Step 3.

Need to check again base addresses... So I need again compare S8500 and S8530 and M210S

Step 4.

No idea yet. :D

Best Regards

Edit 1.

Added results from bl_crc.exe for XXLA1:

S8500
S8530

So I have now 3 files for compare and study...

Edit 2.

No idea yet how long "Function" is... but short searched and I can see all hits looks like this:

10[B]40[/B]2D[B]E9[/B]

Second Byte @ and ends with é...

So maybe length 4 Byte... :confused:
[Android Development on Bada] adfree:
OUTPUT_FORMAT("elf32-littlearm", "elf32-littlearm", "elf32-littlearm")
OUTPUT_ARCH(arm)
ENTRY(main)
MODEL = 0x30333538;
FOTA_NAND_START = 0x09500000;
BL3_DRAM_START = 0x42080000;
MEMORY
{
fota (i) : ORIGIN = 0x43200000, LENGTH = 0x280010
}
SECTIONS
{
.header 0x43200000: { Obj/header.o (.text) } > fota
.footer 0x43480000: {Obj/footer.o (.text)}
__fota_start = ADDR(.header);

. = __fota_start + 0x300;
.text :
{
*(.text)
}
.data : { *(.data) }
.bss 0x44000000: { *(.bss) }

}

Short compared FBOOT_S8530_b2x.lds with FBOOT_S8500_b2x.lds

Model and FOTA differs...

FOTA address is between M210S and S8530 same...

Model unknown, I hope this is not really mandatory. :o :o :o

Will check...

Maybe Model is in ELF Header of apps_compressed.bin...

:confused: :confused:

Will try to identify...

Best Regards
[Android Development on Bada] adfree:
Please, can we make basic workshop for bada Bootloader?

Is IDA Demo enough?

:confused:

Is IDA Demo enough for Noob tests?

https://www.hex-rays.com/products/ida/support/download_demo.shtml

Lesson 1.

Download IDA Demo. :o

Thanx in advance.

Best Regards
[Android Development on Bada] adfree:
Could we make workshop for Keys?

I mean instead Call Key press Cam Key or something similar...

If I have more time, I will check self...

Best Regards
[Android Development on Bada] adfree:
Keys for noobs...

I can find first hints in:

BL3.c

{
int i;
KEYIFCOL = ((~(1 << 2) & (0xFF)) << 8); //COL 2
for(i = 0; i < 10000; i++); //short delay
if((1 << 0) & (KEYIFROW & 0xFF)) //COL 2 & ROW 0 - menu key, if its high its not pressed
return 0;
return 1;
}

BL3.h

#define KEY_CALL 2
#define KEY_CAM1 3
#define KEY_CAM2 6
#define KEY_LOCK 8
#define KEY_MENU 0
#define KEY_VOLD 4
#define KEY_VOLU 7

Now maybe someone could help to explain how Keys can be changed/replaced?

Best Regards
[Android Development on Bada] adfree:
https://github.com/ihavenick/android_bootable_wave-fboot

Thanx for more description...

Best Regards

Edit 1.

By Copy and Paste... I was able to replace Call Key with Volume Up... in source file:

BL3.c

In source code this is 2 Bytes change, BUT in Binary then many changes...

So no chance by playing with HEX Editor easily...

So next step to check out what FASM is...

Or I need adon FASMARM too?

http://arm.flatassembler.net/
[Android Development on Bada] Tigrouzen:
Don't understand, you want compile it ?
[Android Development on Bada] adfree:
User aashil16 need solution:

http://xdaforums.com/showpost.php?p=46491564&postcount=379

I can't help him... soon...

Only if he wait 2 years... when I have finished study of FOTA compiling. :D

Please, help him.

Thanx in advance.

Best Regards
[Android Development on Bada] adfree:
Nice if I compare these 2 sources...

https://github.com/Badadroid/android_bootable_wave-fboot

and

https://github.com/ihavenick/android_bootable_wave-fboot

For me I have problems to find correct "Makefile settings"... :o

To use it in same way I was able to do this with this:

http://xdaforums.com/showpost.php?p=34856402&postcount=4

I have only bada SDK installed...

Best Regards
[Android Development on Bada] Tigrouzen:
It is interesting if we can make same like Acer bootmenu

Rebellos say advantage its on C then all its possible with can adding module

https://github.com/SkrilaxCZ/a500_bootmenu

But a500 bootmenu it use other language

Then we can get best boot
[Android Development on Bada] aashil16:
[MENTION=1030585]adfree[/MENTION] The key remap functionality cannot be changed by modifying FOTA. This is what user ihavenick told me.

Good news : I recently contacted user [MENTION=5449129]krischat1001[/MENTION] regarding my problem. After working for 2-3 days, he managed to remap the home key to sleep(lock) key[just for CWM]. Here is the link to his modified kernel http://filebin.ca/104AuW6hobPR

It works with volk's ROM. I haven't tested with Tigrouzen's ROM. you can contact him to know how he did it.

All credit for the work goes to krischat1001.
[Android Development on Bada] ihavenick:
Dont forgot me :P i told you its kernel

you can add functions :D add .h 's and .c's for it :)

No problem :P if you need help anyting on it Pm me :P

And i am trying to close phone when shutdowned from android

if FOTA finds a file named Shutdown. on sdcard it will close phone but fota finding it and crash

maybe renaming function makes it crashed :)

do you want to test it ?
[Android Development on Bada] aashil16:
Thanks to [MENTION=5093789]ihavenick[/MENTION] for guiding me in a proper direction. :)
[Android Development on Bada] hero355:
Anyone is able to build FBoot with badasdk ?
[Android Development on Bada] adfree:
http://xdaforums.com/showpost.php?p=34856402&postcount=4

This is 100 % working, start with this...

minimum changes...

Check 2 files for correct path for bada SDK:

[B]make.cmd
Makefile[/B]

But with these both I have bigger problems to work with bada SDK...

http://xdaforums.com/showpost.php?p=46846271&postcount=63

"Badadroid" source I was able to compile with copy & paste from ihavenick source...

But not start proper...

:confused: :confused:

And I was not able to compile ihavenick source... :rolleyes: :o

Later more.

Please try first with mijoma s example...

Thanx.

Best Regards
[Android Development on Bada] adfree:
Started again from scratch...

Step 1.

I copy 230 MB + from bada to path:

[B]c:\bada\2.0.3\Tools\[/B]Toolchains\ARM\bin\cs-make.exe

Step 2.

http://xdaforums.com/showpost.php?p=34856402&postcount=4

Click make.cmd

-----------------

Additional steps...

Add Pause to make.cmd to see progress or Errors...

@c:\bada\2.0.3\Tools\Toolchains\ARM\bin\cs-make.exe %1 %2 %3 %4
[B]Pause[/B]

Be sure folders are available:

Source
Obj
Output

Folder names in newer sources are different...

------------------

Now I will try again with here:

https://github.com/Badadroid/android_bootable_wave-fboot

Found for/from Badadroid... no idea if latest, working or maybe wrong source...

And second source from ihavenick

https://github.com/ihavenick/android_bootable_wave-fboot

I will post my results.

Will download source now, to be sure I have not make stupid mistake last timeS...

Best Regards

Edit 1.

Minor change to make.cmd added Pause, now I see:

gcc -DWINDOWS -c -Os src/FOTA.c -o out/FOTA.o
process_begin: CreateProcess(NULL, gcc -DWINDOWS -c -Os src/FOTA.c -o out/FOTA.o
, ...) failed.
make (e=2): Das System kann die angegebene Datei nicht finden.
cs-make: *** [[COLOR="Red"][B]out[/B][/COLOR]/FOTA.o] Error 2

First idea, folder out not exisiting... so I will create folder out...

Edit 2.

Created folder out, but nothing better, seems same Error:

gcc -DWINDOWS -c -Os src/FOTA.c -o out/FOTA.o
process_begin: CreateProcess(NULL, gcc -DWINDOWS -c -Os src/FOTA.c -o out/FOTA.o
, ...) failed.
make (e=2): Das System kann die angegebene Datei nicht finden.
cs-make: *** [out/FOTA.o] Error 2

:confused:

Will proceed with ihavenick sources...

-------------------------------------

Edit 3.

For easier tests...

I have rename MY path to:

c:\bada\2.0.3\Tools\Toolchains
c:\bada\2.0.[B]6[/B]\Tools\Toolchains

To match ihavenick paths...

And I have removed result files from folders out and obj... Again 3 folders only other names:

src
obj
out

Edit 4.

c:\bada\2.0.6\Tools\Toolchains\ARM/bin/arm-bada-eabi-gcc.exe -DWINDOWS -c -Os sr
c/FOTA.c -o obj/FOTA.o
src/FOTA.c: In function 'main':
src/FOTA.c:77:15: [COLOR="Red"][B]error[/B][/COLOR]: 'rm_BIGMEM' undeclared (first use in this function)
src/FOTA.c:77:15: note: each undeclared identifier is reported only once for eac
h function it appears in
src/FOTA.c:83:15: [COLOR="Red"][B]error[/B][/COLOR]: 'rm_FPFK' undeclared (first use in this function)
cs-make: *** [obj/FOTA.o] [COLOR="Red"][B]Error 1[/B][/COLOR]
[Android Development on Bada] hero355:
Changed path on makefile and make,but Got this problem .

"cs-make : *** No targets specified and no makefile found. Stop."
[Android Development on Bada] adfree:
We are talking about mijoma example fboot.zip from here:

http://xdaforums.com/showpost.php?p=34856402&postcount=4

:confused:

3 Folders

Obj and Output empty...

Obj
Output
Source

Folder Source contain these files:

Source\BL3.c
Source\BL3.h
Source\BL3_FBOOT_S8500_b1x.c
Source\BL3_FBOOT_S8500_b2x.c
Source\BL3_FBOOT_S8530_b1x.c
Source\BL3_FBOOT_S8530_b2x.c
Source\crc32.h
Source\crc32.s
Source\footer.s
Source\FOTA.c
Source\header.s
[B][COLOR="Red"]Source\Makefile[/COLOR][/B]
Source\s5pc110.h
Source\sha1.h
Source\sha1.s
Source\string.c

Only do here path correction:

make.cmd AND Makefile

FBOOT_S8500_b1x.lds
FBOOT_S8500_b2x.lds
FBOOT_S8530_b1x.lds
FBOOT_S8530_b2x.lds
[B]make.cmd[/B]
[B]Makefile[/B]
Make_dirs

Best Regards
[Android Development on Bada] hero355:
Off Course, I did change only them (as you marked)

Possible problem with badasdk 2.0.6 or Win8.1 ?
[Android Development on Bada] adfree:
Tested by me on XP 32 bit...

I can only test Win 7 32 and 64 bit... maybe

I hate Win 8.x ... no idea if here is problem. :o

Sorry, no idea if Win 8 big difference...

http://xdaforums.com/showpost.php?p=47251040&postcount=9

This could be Win 7...

---------------------------------------------------

My little progress...

1.

For me its helpfull if I get *.map files for my little brain...

So check Makefile in Source/src folder

$(LD) -T $*.lds [B]-Map=$(OutDir)/$*.map[/B] $(AppObjectsWithPath) $(ObjDir)/RAW_$*.o $(ObjDir)/BL3_$*.o -o $(ObjDir)/$*.elf

2.

""Magic"" in FOTA if pressing any Key is mandatory... or normal Boot starts Android...

Check BL3.c

BL3 means if NO Key pressed, then normal bada action...

return rm_BL3;

This means modified FOTA is executed without pressing any key...

return rm_FOTA_RUN;

If I compare Binary, I see 5 Bytes change... maybe this this possible to change in existing Binary, without having the Source...

Will check later...

3.

Unsolved yet...

Hmmm, maybe for study interesting to prevent RM.EXE to remove all *.o files...

Best Regards
[Android Development on Bada] Nitesh19:
i got 4 FOTA files in output folder and 4 ELF file in obj folder

i made changes in make.cmd and makefile (C:\bada\2.0.3\Tools\Toolchains\ARM\bin\ to C:\bada\2.0.5\Tools\Toolchains\ARM\bin\)

im using XP and bada 2.0.5

now i dont know what to do with those files :confused:
[Android Development on Bada] adfree:
Good question. Depend what you wanted to try...

But first thanx for posting. :good:

If you also used mijoma example fboot.zip from here:

http://xdaforums.com/showpost.php?p=34856402&postcount=4

These 4 FOTA files are:

2 for S8500 and 2 for S8530...

bada 1 and bada 2, because different addresses needed, because Bootloader ""minor"" differences...

For XXLA1 for instance this is correct file to try:

FBOOT_S8500_b[B]2[/B]x.fota

This seems not full Android FOTA, only example...

You can see TEXT if you press CAll Key during Boot...

"More" interesting to compile the other sources from here proper:

http://xdaforums.com/showpost.php?p=46846271&postcount=63

I have no luck... :o

If I compile with bada SDK, then RESULT is strange, because I see nearly same Text... on WHITE Background...

Instead blue and red... and Android start...

:confused: :confused:

Best Regards
[Android Development on Bada] Nitesh19:
im using wave1

i compiled fota from this source : https://github.com/ihavenick/android_bootable_wave-fboot

in out folder got FBOOT_S8500_b2x

flashed using multiloader...

got white screen saying Booting Android

and my phone booted in android :)

i made same changes in fota.c file....

original code :

if(mode == rm_BIGMEM)
{
setup_cmdline_tag(cmdlnBG);
disp_FOTA_Printf("Bigmem mode");
DRV_Modem_BootingStart();
}
if(mode == rm_FPFK)
{
disp_FOTA_Printf("Under Maintise :D");
}
if(mode == rm_FOTA_RECOVERY)
{
setup_cmdline_tag(cmdlnRM);
disp_FOTA_Printf("recovery mode Activated");
}

changed code :

if(mode == 'rm_BIGMEM')
{
setup_cmdline_tag(cmdlnBG);
disp_FOTA_Printf("Bigmem mode");
DRV_Modem_BootingStart();
}
if(mode == 'rm_FPFK')
{
disp_FOTA_Printf("Under Maintise :D");
}
if(mode == 'rm_FOTA_RECOVERY')
{
setup_cmdline_tag(cmdlnRM);
disp_FOTA_Printf("recovery mode Activated");
}

i added single quotes to

rm_BIGMEM
rm_FPFK
rm_FOTA_RECOVERY

in order to remove error ;)
[Android Development on Bada] adfree:
:good:

Thanx for confirm white screen...

This I can see also.

But my tries failed with starting, but maybe my fault...

Meanwhile I have solved optical difference by using FASM with OTHER source in other FORMAT with *.inc and *asm files...

See here:

http://xdaforums.com/showpost.php?p=47278899&postcount=13

Now I can see the ASCII Art... :D

Best Regards

Edit 1.

Please Nitesh19 :angel:

Can you check this Source for me.

https://github.com/Badadroid/android_bootable_wave-fboot

Thanx in advance.

My result is also white Screen with Text...

:confused:
[Android Development on Bada] Nitesh19:
in order to boot in android u need ur kernel in sd card...

im using bux rom....
[Android Development on Bada] adfree:
If I remember correct, my result of compiling this:

https://github.com/Badadroid/android_bootable_wave-fboot

Looks similar...

I had zImage on both...

internal and SD... but maybe my fault. As I have tried many stupid things... :o

With half closed eyes because tired... :o

If you could confirm, this would help me a lot to better understand.

Thanx :cool:

Best Regards
[Android Development on Bada] Nitesh19:
i think https://github.com/Badadroid/android...ble_wave-fboot is requires kernel in internal memory....

and i dont have internal memory as im using nand version

But....

in https://github.com/Badadroid/android_bootable_wave-fboot/blob/master/src/FOTA.c

void* kernelImage = L"/[COLOR="Red"]g[/COLOR]/zImage";

in https://github.com/ihavenick/android_bootable_wave-fboot/blob/master/src/FOTA.c

void* kernelImage = L"/[COLOR="Red"]e[/COLOR]/zImage";

i can replace that g with e

and i think g is for internal memory and e is for sd card
[Android Development on Bada] adfree:
https://github.com/Badadroid/androi...tree/fe647bcb2610e6ffc7f2e8a82253e98fd297639a

:rolleyes:

Nice by stupid clicking around. I have realized what .gitignore do.

:eek:

https://github.com/Badadroid/android_bootable_wave-fboot

Maybe now I can find my failure...

Because now *.elf + FOTA is inside for compare with my result...

Best Regards
[Android Development on Bada] adfree:
https://github.com/Badadroid/androi...mmit/ca3bfd8dd82bcea5109f6dabd69f6f27c59c86cd

I give up... :crying:

If I try FBOOT_S8500_b2x.fota with XXLA1 I see nothing... black screen...

It seems nothing happens...

If I compare few files, I see few changes...

I have no idea, how to find working Source Code... :confused:

https://github.com/Badadroid/android_bootable_wave-fboot

Best Regards
[Android Development on Bada] Nitesh19:
try the attached FOTA file and let me know result....

i have compiled that from https://github.com/Badadroid/android_bootable_wave-fboot this source
[Android Development on Bada] adfree:
This is exactly what I was also able to compile, since here:

http://xdaforums.com/showpost.php?p=46890157&postcount=64

My result and your FOTA from here are 1:1 identical:

http://xdaforums.com/showpost.php?p=47313532&postcount=87

I see white Screen...

FOTA Bootloader...

Nothing happens after minutes, hours...

I am pretty sure I have zImage on correct position... because I can use this:

http://xdaforums.com/showthread.php?t=2400126

With other FOTA...

Tested on S8500 XXLA1...

Best Regards
[Android Development on Bada] Nitesh19:
problem with https://github.com/Badadroid/android_bootable_wave-fboot this fota, its not able to find zImage(kernel)...

i changed the e to g in(ihavenick's fboot)

void* kernelImage = L"/[B][COLOR="Red"]e[/COLOR][/B]/zImage";

and got same result white screen with text no boot....

from above we can conclude that https://github.com/Badadroid/android_bootable_wave-fboot this fota not able to find zImage

May be we are making mistake somewhere or source is not updated....

---------- Post added at 08:06 PM ---------- Previous post was at 07:20 PM ----------

made a lot of changes in https://github.com/Badadroid/android_bootable_wave-fboot

and after that i booted android from sdcard :D
[Android Development on Bada] volk204:
[MENTION=1030585]adfree[/MENTION]

try to change https://github.com/Badadroid/android_bootable_wave-fboot/blob/master/src/FOTA.c#L88

0x891 to 8500 for wave 1 and to 8530 for wave 2

like here

https://github.com/ihavenick/android_bootable_wave-fboot/blob/master/src/FOTA.c#L108