[Bada Software and Hacking General] adfree:
Uploading a zImage to Ram for testing without flashing using fastboot

There is a way to upload a zImage into the RAM without flashing it into the eMMC or putting it on a SD Card.

By using fastboot you can use the following command:

fastboot -b 0x80008000 boot <path to zImage> <path to ramdisk>

Adding -c to this command will append additional bootargs to the command line.

fastboot -c "foo" -b 0x80008000 boot <path to zImage> <path to ramdisk>

This will add foo to the command line arguments.

You can also additionally flash this into the emmc using the following command.

fastboot -b 0x80008000 -c "foo" flash:raw boot <path to zImage> <path to ramdisk>

Tip started on the ICS mail list. This is the way to use it on the current HW.

Found this on first Link Galaxy3HELL...

Thanx.

[MENTION=4570762]Taxidriver05[/MENTION]

Ich weiß nicht wie die S. funktioniert mit dem Android Kernel.

Deshalb ist das momentan s.egal welche Android Version.

Ich kann auch nix mit loggen...

Alles was bei S8500 ging... geht hier einfach nicht. :mad:

I have NO UART output... :crying:

All I know is boot.img from I9001 and I8150 is in partition 8...

Android Kernel from I9001 and I8150... NO idea where they stopping to work...

As I see NOTHING on Screen and I have NO Log output... :eek:

Logfile is for instance this:

http://xdaforums.com/showpost.php?p=37157782&postcount=1

[370] Panel is power on
[370] Display initialized
[370] Display logo
[370] Waiting for modem+++
[370] Waiting for modem: Done
[370] smem ram ptable found: ver: 0 len: 6
[370] scratch: 0x8000000
[370] Starting in SD mode!
[370] SD_DETECT pin : 0x0
[380] Initializing MMC host data structure and clock!
[380] Error No. 2: Failure Initializing MMC Card!
[400] Decoded CID fields:
[400] Manufacturer ID: 27
[400] OEM ID: 0x5048
[400] Product Name: SD16G
[400] Product revision: 3.0
[400] Product serial number: 7C88FF04
[400] Manufacturing date: 2 2012
[410] Serial number -[410] serial number:
[410] partition misc doesn't exist
[410] error in emmc_recovery_init
[580]
kernel @ 208000 (4132528 bytes)
[580] ramdisk @ 1200000 (175204 bytes)
[580] cmdline = 'console=null androidboot.hardware=qcom user_debug=31'
[580]
Booting Linux
[580] smem ram ptable found: ver: 0 len: 6
[580] booting linux @ 0x208000, ramdisk @ 0x1200000 (175204)
[590] cmdline: console=null androidboot.hardware=qcom user_debug=31
Uncompressing Linux... done, booting the kernel.

HOW?

WHERE?

WHO?

Wer wie was wo ?

:confused:

With oleg_k """"Bootloader""" I can see only this:

http://xdaforums.com/showpost.php?p=51596851&postcount=67

I have to find FU. RAM addresses...

I have to start from scratch... to teach my self.

And I am trying alone... :rolleyes:

If someone would support me, by trying same steps... on REAL S8600.

This could increase speed of progress...

Best Regards

Edit 1.

Only little tiny correction.

My work is done/successfully finished. 100 % complete successfully.

I never told I make now Android Kernel... this exceeds my skills. :o

For Kernel Developer with experience it is 0 problemo to tell RAM address.

I8150 and I9001 Kernel Developer should know, from where boot.img/Kernel is executed in RAM...

And if they use alternate methods to push Kernel via USB cable into device...

Check out oleg_k Log...

[B]kernel @ 208000[/B] (4132528 bytes)
[580] ramdisk @ 1200000 (175204 bytes)
[580] cmdline = 'console=null androidboot.hardware=qcom user_debug=31'
[580]
Booting Linux
[580] smem ram ptable found: ver: 0 len: 6
[580] booting linux @ 0x208000, ramdisk @ 0x1200000 (175204)

His Kernel seems to load and executed at 0x0020 8000... 4 MB big

RAMdisk is set to 17 MB... at 0x0120 0000

Now go and find infos for I9001 Kernel and /or I8150.

Because something is wrong... in my head or somewhere else...

At the moment I have only access read/write at 0x8000 0000...

And I have 7 Zeros after 8...

Lower addresses seems not to work... BUT this could MY fault, my low brain...

To be sure, its not my fault...

I am trying to collect infos about:

DBL RAM address

OSBL RAM address

eMMCboot RAM address...

Kernel RAM address...

NO it is NOT the same like in S8500... (I think)...

Best Regards

---------- Post added at 11:58 AM ---------- Previous post was at 11:13 AM ----------

No JTAG needed...

Kernel Source for I9001 and I8150... is available...

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=I9001

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=I8150

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=I847

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SPH-M950

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SPH-M840

According to this compatibility list:

http://xdaforums.com/showpost.php?p=52129324&postcount=24

Thanx again for this. :good:

Now please, ask I9001 or I8150 or other Kernel Developers about RAM address?

Where is Kernel loaded and executed into RAM?

Thanx in advance.

If someone need... XDA area for I9001 and I8150:

http://xdaforums.com/galaxy-s-i9000/i9001-development

http://xdaforums.com/galaxy-w

No JTAG is needed.

Simple search or ask or do nothing.

Your choice. :angel:

Thanx in advance.

Best Regards