Database Develop

[Q] How to compile the kernel from source and flash it in samsung galaxy tab p1000

How to compile a kernel from orginal source provided by samsung and port it in samsung galaxy tab p1000. I followed the steps below is not working
i downloaded the source from opensource.samsung.com. Phone details
PDA: P1000XXJME
PHONE : P1000XXJMA
CSC1000CXAJME
i extracted the source GT-P1000_OpenSource. I compiled the kernel using ./build_kernel.sh. I got zImage then created tar file. i flashed the tar file , but it is not working.
The size of the zImage is 3mb, The size of orginal zImage is 7.5mb
Is the above steps are right
Thanks
sivakumar

[Q]

I want to root my SGN but i am confused which metod i should to use?
TNx?
1.2. If you are not rooted yet: Using the zergRush exploit
(while it still works on our firmwares, this exploit will probably be fixed soon! Known to work on KJ1 and KJ4 firmwares)
- Download the attached "InitialRootFlasher.zip" and extract it somewhere
- Download one of the CF-Root kernels, and extract it (repeat) until you end up with a zImage file
- Place the zImage file from the CF-Root kernel in the zImage folder from InitialRootFlasher
- Start "not-rooted-yet.bat" and follow the instructions
1.3. If you are not rooted yet: Flash a modified FACTORYFS
I am providing this method just this once, for the KJ1 firmware. This is the /system part of the KJ1 firmware, modified so at first boot it will flash the KJ1 CF-Root and reboot, without getting you the yellow triangle or increasing the flash counter.
Using a newer firmware? Do this operation first, then flash the newer firmware back using CWM Manager. This is explained in Chapter 3 below.
Download: http://www.multiupload.com/YB9EL8D8O3
- Optional: flash the full KJ1 firmware first
- Unzip the file, you should get "SGN_XX_OXA_KJ1_FACTORYFS.tar"
- Make sure your SGN is NOT connected to your computer
- Reboot your SGN into "download mode" (see below)
- Start ODIN
- Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
- Connect the SGN to your computer
- Make sure "repartition" is NOT checked
- Click the START button
- Wait for the phone to reboot TWICE
- Done
If you do not know how to get into download mode:
- Turn off the device
- Count to 10
- Hold the "home" (the big physical button in the middle) and "volume down" buttons
- Press and release the power button (keep holding "home" and "volume down" !) to turn the device on
- You should get a download mode screen
- If it tells you to press a button to continue, do so
--- Chapter 2: Getting rid of ODIN ---
This is easy. Find ODIN, and delete it. In the future you should only need it to flash bootloaders, which probably will only really be needed one time: when upgrading from Gingerbread to Ice Cream Sandwich.
--- Chapter 3: Upgrading your firmware ---
My CWM Manager application has a full-fledged firmware flasher built in. Using the flasher from CWM Manager does NOT give you the yellow triangle or increase the flash counter.
3.1. Flashing a new kernel
This is easy. CWM Manager can flash zImage files (on any rooted kernel), zImage files inside a .tar file (only on a CF-Root kernel), and zImage files inside a .tar.zip (only on a CF-Root kernel). Note that zImage must be the ONLY file in an archive, if is is inside a tar or zipped tar.
- Put the zImage (or tar, or zip) file on your SD card
- Open the CWM Manager app
- Select "Flash kernel"
- Select the file you just put on your device
- CWM Manager will flash the kernel and reboot
If you flash a non-CF-Root kernel, you will lose a lot of functionality from CWM Manager. However, the app will (likely) still allow you to flash kernels.
3.2. Flashing a new firmware
Important: This works ONLY on a CF-Root kernel !
CWM Manager has the ability to flash firmware parts either from separate files (zImage, factoryfs.img, etc) or from .tar / .tar.md5 files that they usually come packaged in.
- Download the firmware you want to flash
- If you have a ZIP or RAR file, extract it until you have seperate files, or .tar / .tar.md5 files
- Create a folder named 'firmware' on your external SD card
- Copy the files you want to flash to this folder ( /sdcard/external_sd/firmware ). factoryfs ("system") is mandatory part at the moment.
- TIP: If you are flashing a new firmware that already has a CF-Root kernel available, put it in the 'firmware' folder as well in zImage or .tar form (NOT .zip). Select it when asked which kernel to use, then use the "Flash normally" option later on.
- Open the CWM Manager app
- Select "Flash stock firmware"
- At this point, CWM Manager will tell you about the firmware parts it has found, and which ones it will flash. It will also give you warnings about bootloaders and PIT files if those were found. If some firmware parts are present multiple times, it will ask you which file to use as source.
- If what you are flashing includes both kernel and system parts, CWM Manager will warn you about this as you are about to lose root. It will provide you with three options:
1: Keep CF-Root kernel
Keeps the current CF-Root kernel, only flash the other parts. You will not lose root or CWM Recovery. You can flash a newer CF-Root kernel later (or maybe you have already done so), see 3.1 above.
2: Pre-root system
Flashes both kernel and system parts, but roots system during the flash. You will lose CWM Recovery, but you will keep root (if all goes well). The CWM Manager application will also remain, and allow you to flash the correct CF-Root kernel at a different time (if you have not done so before), see 3.1 above.
3: Flash normally
Doesn't do anything specific. If the kernel you are flashing is not a CF-Root (or similar) kernel, you will lose root, and CWM Recovery.
- CWM Manager will reboot into CWM Recovery, and will flash the firmware, rebooting afterwards.

Go here and just read after 16Nov edit
http://forum.xda-developers.com/showthread.php?t=1329360

Problem rooting + CWM recovery Galaxy note

Hey guys, m sorry to bug you wid this query but this is my first post.
i was on the official ICS for india which was rooted using Dr. ketans guide.
All was working good till i saw the PARANOID ROm and i wanted to install it.
so i downloaded N7000DDLC1_N7000ODDLC1_INU and installed it with ODIN and then did a wipe factory data and wipe cache.
Now my phone shows the following settings in the about phone menu:
Baseband : N7000DDLC1
Kernel Version : [email protected]#2
Build number : GINGERBREAD.DDLC1
please can someone guide me on how to root it and install CWM recovery so i can flash the PARANOID ROM.
please guys...will appreciate ur quick reply.

Method 1 : Easy Rooting Toolkit [v1.0](zergRush Exploit) with newest zergRush binary , and newer superuser file. (WINDOWS ONLY) WILL WORK ON BOTH LOCKED & UNLOCKED BOOTLOADER DEVICES! just download the attached file, extract it using winzip/winrargo to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen! Download here : http://forum.xda-developers.com/attachment.php?attachmentid=841876&d=1325678726 .method 2.cwm recovery . 1. Initial CFroot flasher 2. Two other folder having zImage file , you need one only
Which file do I use ? Listen closely, for I will say zis only once! Go to Settings -> About phone -> Kernel Version. Note the string present there: 2.6.35.7-N7000XXKJ4-CL641703 What matters most (KJ4) in this case, is in bold. Try to find the matching file e.g. CF-Root-SGN_XX_XEN_KJ4-v5.0-CWM4.zip)so choose accordingly- Place the zImage file accordingly in folder 1.initial CFroot flasher /zImage folder- Start "already-rooted.bat" and follow the instructions If you are Rooted already OR - Start "not-rooted-yet.bat" and follow the instructions.
Note : Just below this, where you download actual flash programme, that includes initial CF root as well i have already placed zimage accordingly. I am Already Rooted - Execute "already-rooted.bat" and follow the instructions
I am Non-rooted - Execute "not-rooted-yet.bat" and follow the instructions... you need to firmware downgrade : http://www.sammobile.com/firmware/. Use to rom gingerbread 2.3.6 after you have downloaded the firmware, for the flash use odin 1.85 click here : http://www.mediafire.com/?36mcl2rs5gwrvsj ... and why 'your firmware is not rootable. Which kernel You have?
(Go to Settings -> About phone -> Kernel Version. Note the string present there: 2.6.35.7-N7000XXKJ4-CL641703 Here Red is kernel version)
For download here: http://forum.xda-developers.com/showthread.php?t=1329360
I have Kernel KJ1 - – and Extrac
I have Kernel KJ4 - - and Extract..
I Have Kernel KJ6/KJ7/KJ8 - and extract
I have Kernel KK1/KK2/KK3/KK4/KK5 - - and Extract
I have Kernel KKA - - and Extract
I have Kernel KK9 -- and Extract
I have kernel KL3 - - and Extract
I have Kernel KL1 - - and Extract

Here's a guide for the entire process, from rooting your GB ROM to upgrading to ParanoidAndroid: http://www.android.gs/update-samsun...-paranoidandroid-ics-4-0-4-tablet-hybrid-cm9/

How to flash Kernel

Will somebody guide how to flash a kernel thru Mobile Odin Pro? thanks.

copy required kernel in .tar format (if you have it in zip then extract zImage from it) to Sd card(Int/Ext)
-Open mobile Odin
-select kernel tab
-Point to kernel file you copied
-Flash

Building/Flashing custom kernel to SM-G780F(Exynos) help

Obligatory first post on the forums here so hopefully this is the right place!
I have been lurking on the forums for the past month or so and have been working on building a custom kernel from source for the SM-G780F/DSC(Exynos) edition. I've built some kernels from source before so I have some experience there, but actually getting the kernel to flash and run on the device is a different story. I have built the kernel with the modifications that I wanted, fixed some flashing issues I was running into, finally got the boot.img to flash succefully to the device, rebooted the device and the phone just hangs at the Samsung logo. (See "Image from iOS.png").
Here is the steps that I did:
Unlock Bootloader on the device.USB Debugging on, OEM Unlocking enabled in dev settings/ OEM Lock: OFF(U) in DL mode.
Checked to make sure KG State is not Prenormal, it is in checking state.
Device is currently running stock G780FXXS7CUI5, so I download this version source from https://opensource.samsung.com/uploadSearch?searchValue=SM-G780F
Extract Kernel.tar.gz, update toolchain paths in the Makefile/build_kernel.sh, and I make some modifications to the defconfig file.
Code:
./build_kernel.sh
; Fix compiler errors/warnings as they appear. Rinse and repeat until the kernel is built.
Now that the kernel is built I pull the stock ROM that this device is currently running from Sammobile. https://www.sammobile.com/samsung/g.../SM-G780F/MID/download/G780FXXS7CUI5/1583411/
Extract the AP directory from the Sammobile ROM download.
Extract the boot.img.lz4 from the AP directory so I now have the uncompressed boot.img.
Copy over the the stock boot.img to my AIK directory. (AIK-Kinux-V3.8)
Code:
./unpackimg.sh boot.img
, cd into split_img, rm the stock boot.img-kernel
Move my custom kernel image to the AIK directory,
Code:
mv kernel_source/out/arch/arm64/boot/Image /AIK-Linux/split_img/boot.img-kernel
Run AIK repackimage.sh
Now I have a SM-G780G(Snapdragon edition) S20_FE with Magisk installed. So I copy over my image-new.img to this device and patch the image-new.img with Magisk
Move back the patched image to my linux enviroment. Rename my patched image boot.img.
Compress my boot img with
Code:
lz4 -B6 --content-size boot.img boot.img.lz4
.
Replace the stock boot.img.lz4 in my AP directory with my modded boot.img.lz4
Pull down a clean vbmeta.img from https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Compress this image as well
Code:
lz4 -B6 --content-size vbmeta.img vbmeta.img.lz4
Replace the stock vbmeta.img.lz4 in the AP directory with my clean vbmeta.img.lz4 in the
So the contents of the AP directory currently is
Code:
22556009 Apr 7 12:57 boot.img.lz4
1155 Sep 23 2021 dqmdbg.img.lz4
219753 Sep 23 2021 dtbo.img.lz4
4096 Sep 23 2021 meta-data
1148 Sep 23 2021 metadata.img.lz4
2773 Sep 23 2021 misc.bin.lz4
35115127 Sep 23 2021 recovery.img.lz4
5457239441 Sep 23 2021 super.img.lz4
822394050 Sep 23 2021 userdata.img.lz4
2375 Apr 7 12:57 vbmeta.img.lz4
2812 Sep 23 2021 vbmeta_samsung.img.lz4
tarball all these files with
Code:
tar -cvf Modded_AP.tar *
Spin up latest version of ODIN
Place Custom AP into AP slot, Stock BL into BL slot, Stock CP into CP slot, and Stock HOME_CSC into CSC slot
Start Flashing.
Flashing is successful.
Device reboots, and hangs at the Samsung Galaxy S20FE Screen with the warning "I am not running samsungs official software."
A couple of questions I am asking myself is the stock vbmeta_samsung.img.lz4 necessary, as well as some of the other stock files? Is patching my boot.img with Magisk running on a different
device giving me issues? Am i missing a step somewhere or is there still extra steps I need to take to get a modded kernel running on this device. Any help would be greatly appreciated or if I need to provide any more insight please let me know! Thanks again!

you'd be extremely welcome in our little group
S20 FE Modding
Exynos AOSP: https://t.me/S20FE_Exy TurboUI: https://t.me/projectxs20fe Prime Kernel Snap: https:/t.mes20fesnapdragon Prime Kernel Exynos: https://t.me+vpzEK9kPMc41MmY9 Bandido Kernel https://t.me/bandidokernel Klimbo Kernel https://t.me/klimbokernel
t.me
there's also a kernel dev there from time to time who has built kernels for all versions FE completely blind, i.e. without being able to flash them himself. maybe we can get you two talking.

it sounds like you've added two kernels to your AP archive. as I understand it once you've built your kernel, compressed it to .lz4 you can just archive it inside a tar file and flash that alone (as long as it matches your firmware).

Hi there Buddy, so answering your questions- we dont need vbmeta everytime, we only use it once to flash twrp after which flashing vbmeta not necessary. Now yes patching boot.img with other device other than the one you are running causes problems here and device doesnt like to boot. As per the last kernel dev he just used our stock boot.img and compiled his changes. And we flash hi kernel like normal flash.
S20 FE Modding
Exynos AOSP: https://t.me/S20FE_Exy TurboUI: https://t.me/projectxs20fe Prime Kernel Snap: https:/t.mes20fesnapdragon Prime Kernel Exynos: https://t.me+vpzEK9kPMc41MmY9 Bandido Kernel https://t.me/bandidokernel Klimbo Kernel https://t.me/klimbokernel
t.me
You can even join this group, there are many people willing to help others.

Also i have been developing stock based roms for all the variants, so would be happy to test them once they get stable enough to boot.

Thanks for the responses everyone! I'll take my follow up questions to the group!

Hi. There are some kernel changes that is needed to be applied in order to successfully boot the custom kernel. I suggest you post the kernel source so I can review it. You don't need to place everything inside the AP. You can just archive the boot.img.lz4 as tar.
Also, a lot of your steps can be simplified by making a twrp-flashable zip instead. You can use my template here:
android_kernel_samsung_s20fe/AnyKernel3 at exynos · pascua28/android_kernel_samsung_s20fe
Custom kernel for Samsung S20 FE (Snapdragon and Exynos variants) - android_kernel_samsung_s20fe/AnyKernel3 at exynos · pascua28/android_kernel_samsung_s20fe
github.com
Just move the arch/arm64/boot/Image as zImage and you can zip the AnyKernel3 folder and there you have a twrp-flashable zip. It's a lot more convenient this way as people do not need to carry around their computers whenever they need to flash custom stuffs plus, it's more universal this way as they don't have to have a matching firmware version; it will just use the existing boot image, unpack it, replace the kernel, repack and then flash it back to the device.
If you have any questions, feel free to contact me on telegram (pascua14). I hope you succeed
Regards