[Android Software Development] stefano_te:
I downloaded the firmware from SamMobile: N7000XXLT9_N7000ITVLT3_ITV.zip

I extracted the file N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 with winrar.

With right-click on the file (rename), I deleted “.md5” and I renamed the file in: N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar

I moved the file in the folder C:\cygwin\home\Marco\Kitchen\original_update

cygwin terminal (kitchen v.0.224):

cd kitchen [enter]

./menu [enter]

1 [enter] (set up working folder from ROM)

“CREATE WORKING FOLDER FOR ROM

==============================

Ensure there is at least one ROM under the 'original_update' folder!

Select an option:

s - Show supported formats

x - Abort, don't create working folder

Or press Enter to continue?”

[enter] to continue

“scripts/choose_rom: line 110: more: command not found

Enter selection number (default=1, cancel=0, r=refresh):”

1 [enter]

“Selected N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar

The new working folder will be named WORKING_040614_172502

Change the name (y/n)? (default: n):”

n [enter]

“Creating working folder WORKING_040614_172502 ...

Extracting ROM from TAR file ...

cache.img

factoryfs.img

hidden.img

modem.bin

zImage

NOTE: Ensure you use a rooted kernel (zImage), such as CF-Root, which

allows flashing of custom ROMs. If you instead decide to flash a

stock kernel then you must use Odin afterwards to flash back a rooted

kernel.

Compiling simg2img ...

simg2img.exe successfully compiled

Converting factoryfs.img into a format for unpacking ...

Adding an update-script ...

#####################################################################

READ INSTRUCTIONS BELOW TO EXTRACT FILES FROM ext4_factoryfs.img:

1) Ignore the 'Cannot Read Disk' warning dialog (press 'OK') if it

appears!

2) When Ext2Explore appears, use 'File->Open Image' to open:

C:\cygwin\home\Marco\kitchen\WORKING_040614_172502\system\ext4_factoryfs.img

3) After it loads, right-click on the new icon displayed in the left

frame, and select Save

4) Select C:\cygwin\home\Marco\kitchen\WORKING_040614_172502\system

5) Wait for extraction to finish and then close Ext2Explore

#####################################################################

>>>> PERFORM THE STEPS ABOVE BEFORE PRESSING ENTER! <<<<

Press Enter to continue”

[enter]

“The file ext4_factoryfs.img has been fully unpacked into:

/home/Marco/kitchen/WORKING_040614_172502/system

The /system/app folder is potentially missing some APK/ODEX files

These are probably found in hidden.img

Converting hidden.img into a format for unpacking ...

#####################################################################

READ INSTRUCTIONS BELOW TO EXTRACT FILES FROM ext4_hidden.img:

1) Ignore the 'Cannot Read Disk' warning dialog (press 'OK') if it

appears!

2) When Ext2Explore appears, use 'File->Open Image' to open:

C:\cygwin\home\Marco\kitchen\WORKING_040614_172502\hidden\ext4_hidden.img

3) After it loads, right-click on the new icon displayed in the left

frame, and select Save

4) Select C:\cygwin\home\Marco\kitchen\WORKING_040614_172502\hidden

5) Wait for extraction to finish and then close Ext2Explore

#####################################################################

>>>> PERFORM THE STEPS ABOVE BEFORE PRESSING ENTER! <<<<

Press Enter to continue”

[enter]

“Found <<33>> APK and ODEX files under hidden.img

The mount point for /preload has already been defined for this

device as /dev/block/mmcblk0p12 under /tools/edify_defs/GT-I9100.

Good.

NOTE: If you wish to de-odex this ROM, you will need to move the APK

and ODEX files from the /preload apps folder to /system/app before you

de-odex them. The kitchen will automatically handle this.

Press Enter to continue”

[enter]

“Do you wish to extract the Customer Software Customization (CSC)

from the cache.img (y/n)? (default: y):”

y [enter]

“Converting cache.img into a format for unpacking ...

#####################################################################

READ INSTRUCTIONS BELOW TO EXTRACT FILES FROM ext4_cache.img:

1) Ensure you have installed DiskInternals Linux Reader, found

under tools/diskinternals_windows/Linux_Reader.exe

2) Launch Linux Reader and use 'Drives->Mount Image' to mount:

C:\cygwin\home\Marco\kitchen\WORKING_040614_174914\system\ext4_cache.img

3) From the Linux Reader explorer, double-click 'Linux native

Volume 1' so that the image's folders are now shown

4) Open the 'recovery' folder so that sec_csc.zip is shown

5) Right-click on sec_csc.zip, select 'Save' and then click 'Next'.

6) UNCHECK the box for 'Save directory structure' and choose folder

C:\cygwin\home\Marco\kitchen\WORKING_040614_174914\system

NOTE: The program will show the last used path if you don't change

the folder. Thus ensure an old working folder isn't used!

7) Click on 'Next' twice, wait for extraction to finish and then

close Linux Reader

NOTE: This program adds Administrator ownership to the extracted

files, so the kitchen -might- have problems moving or

deleting your ROM's working folder afterwards (unless you do

this manually with Windows explorer)!

#####################################################################

>>>> PERFORM THE STEPS ABOVE BEFORE PRESSING ENTER! <<<<

Press Enter to continue”

[enter]

“Extracting the required files from sec_csc.zip ...

These are the apps found in sec_csc.zip:

./system/app/Books.apk

./system/app/Flipboard.apk

Copy the apps to your working folder (y/n)? (default: n):”

n [enter]

“"./system/app/Books.apk" rimosso

"./system/app/Flipboard.apk" rimosso

Warning: A valid boot.img is not found. You have the option to add a

'fake' boot.img so that the features of the kitchen can still

function normally.

This boot.img will be automatically removed from your ROM's

ZIP file when it is built. is normal this warning?

Add boot.img (y/n)? (default: y):”

y [enter]

“Copying null boot.img ...

Looking for symbolic links under /system/bin ...

None detected

Adding a default set of toolbox symlinks to update-script .................................................................................................

Adding dumpcrash symlink ...

Looking for symbolic links under system/xbin of working folder ...

None detected

/preload/symlink/system/app found under working folder

Updating update-script with /preload app symlinks entries

Listing of WORKING_040614_174914:

totale 20492

-rwx------+ 1 Marco Nessuno 6144 6 apr 18.17 boot.img

drwxr-xr-x+ 1 Marco Nessuno 0 6 apr 17.57 META-INF

-rwxrwxrwx+ 1 Marco Nessuno 12583168 20 mar 2013 modem.bin

drwxr-xr-x+ 1 Marco Nessuno 0 6 apr 18.06 preload

drwxrwxrwx+ 1 Marco Nessuno 0 6 apr 18.17 system

-rwxrwxrwx+ 1 Marco Nessuno 8387840 4 giu 2013 zImage

Finished setting up working folder!

Would you like to view this ROM's info (y/n)? (default: y):”

y [enter]

“Working folder information (v)

Android OS version : 4.1.2

Device : GT-N7000

Model : GT-N7000

ROM Name : JZO54K.N7000XXLT9

CSC version :

Rooted (Superuser app + su) : NO

Rooted (unsecured boot.img) : UNKNOWN is normal?

BusyBox installed : NO

BusyBox run-parts support : UNKNOWN is normal?

Apps2SD (Apps to EXT) enabled : NO

/data/app enabled : NO

Custom boot animation allowed : NO

Nano text editor installed : NO

Bash shell support : NO

/system/framework is deodexed : NO

/system/app is deodexed : NO

modem.bin found : YES

ROM will wipe all data : NO

Press Enter to continue”

I have the following structure in working folder:

WORKING_040614_174914\META-INF\com\google\android:

update-script

update-script.bak

WORKING_040614_174914\preload\symlink\system\app: I have 33 apk

WORKING_040614_174914\system: I think the content equal to the folder of the video

WORKING_040614_174914:

Boot.img [6 kb]

Modem.bin

zImage

how to solve?