[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] zertyz:
Hi there jamaljmys!

Since you have root, you may try a different thing -- and let us know so we can learn a bit on the process.

Reading this topic, I'd like to double check the following concepts (mates, please correct me if I am wrong):

1) The bootloader & kernel ARE NOT at the same place -- the bootloader & download tool lies between offsets ~512 & ~4194304

2) The internal sdcard & kernel & cache & data & bootloader & etc as well as the partition information are stored on the same device -- /dev/block/mmcblk0

Since you PITted your device, you'd better double check the partition scheme.

Which devices do you have on /dev/block after a fresh boot?

You should have, at least, "mmcblk0" (the whole device), "mmcblk0p9" (/system), "mmcblk0p7" (cache), "mmcblk0p11" (the sdcard) and "mmcblk0p5" (kernel).

My complete list follows (the output of "ls -l /dev/block/mmc*" console command):

brw------- 1 root root 179, 0 Apr 24 21:14 /dev/block/mmcblk0

brw------- 1 root root 179, 1 Apr 24 21:14 /dev/block/mmcblk0p1

brw------- 1 root root 259, 2 Apr 24 21:14 /dev/block/mmcblk0p10

brw------- 1 root root 259, 3 Apr 24 21:14 /dev/block/mmcblk0p11

brw------- 1 root root 259, 4 Apr 24 21:14 /dev/block/mmcblk0p12

brw------- 1 root root 179, 2 Apr 24 21:14 /dev/block/mmcblk0p2

brw------- 1 root root 179, 3 Apr 24 21:14 /dev/block/mmcblk0p3

brw------- 1 root root 179, 4 Apr 24 21:14 /dev/block/mmcblk0p4

brw------- 1 root root 179, 5 Apr 24 21:14 /dev/block/mmcblk0p5

brw------- 1 root root 179, 6 Apr 24 21:14 /dev/block/mmcblk0p6

brw------- 1 root root 179, 7 Apr 24 21:14 /dev/block/mmcblk0p7

brw-rw---- 1 system radio 259, 0 Apr 24 21:14 /dev/block/mmcblk0p8

brw------- 1 root root 259, 1 Apr 24 21:14 /dev/block/mmcblk0p9

In case you don't have these (expected), this means you partition scheme needs fixing.

Although advised NOT TO DO SO, you may proceed reading this post :)

1) FIX THE DEVICES

If you don't have the mmcblk0 device, make it with:

# mknod /dev/block/mmcblk0 179 0

2) USE PARTED TO FIX YOUR PARTITION LAYOUT

Do this by hand at a adb console. This will only work if you have, at least, the mmcblk0 device on /dev/block

First, know your current partition layout with:

# parted /dev/block/mmcblk0 unit b print

Here is mine:

Model: MMC VYL00M (sd/mmc)

Disk /dev/block/mmcblk0: 15758000128B

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 4194304B 25165823B 20971520B ext4 EFS

2 25165824B 26476543B 1310720B SBL1

3 27262976B 28573695B 1310720B SBL2

4 29360128B 37748735B 8388608B PARAM

5 37748736B 46137343B 8388608B KERNEL

6 46137344B 54525951B 8388608B RECOVERY

7 54525952B 264241151B 209715200B ext4 CACHE

8 264241152B 281018367B 16777216B MODEM

9 281018368B 1174405119B 893386752B ext4 FACTORYFS

10 1174405120B 3321888767B 2147483648B ext4 DATAFS

11 3321888768B 15216934911B 11895046144B fat32 UMS

12 15216934912B 15753805823B 536870912B ext4 HIDDEN

In case your partition layout needs fixing, you're advised to study how parted works before commiting any changes.

3) FORCED KERNEL FLASHING -- tested on GT-N7000 16GB

For this to work you should have at least the mmcblk0 device -- if you don't have it, forget... the next boot will bring you the old kernel as well.

Force a flash with the following command (you certainly don't want to do this for it will probably brick the device if something goes wrong):

# dd bs=1 seek=37748736 count=8388608 if=/<path-to-kernel>/zImage of=/dev/block/mmcblk0

Hope this helps, good luck and don't forget to share your outputs so we can learn more about the phone internals...

[]s