Database Users

[Q] compile own kernel? configuration

I used rotohammer's method for backing up the AT&T Galaxy Tab and it worked wonderfully. I compiled the GT-P1000_Kernel patched with SGH-I987_Kernel and did a standard make and then flashed the zImage onto the galaxy. It resulted in kernel panic. Does anyone know what parameters to use with make or configuration changes that need to be made?
Thanks
ps. when I used heimdall, I only "heimdall flash --kernel zImage".

I also couldn't find a config.gz in the /proc dir. Does anybody know why it is missing and what has taken its place?

success at last
Yay, it works now! thanks roto for the initramfs tip.

what kind of modification did u make to the kernel? do you mind sharing?

[Q] how did you compile your own kernel?
Hi,
I'm in disperate need to do this. I have downloaded the sources from samsung opensource -> followed the instruction in the README.txt -> compiled the kernel and the modules successfully -> used the initramfs from the stock zImage -> but when I flash the zImage (Size ~ 432 KB) I get kernel panic.
I do not think it is possible to boot in verbose mode or have a serial port console log.
letolkki: please share with us how you did it? how did you compile a zImage which boots.??????
share with us please!

I used make menuconfig to specify the location of the initramfs (compression to none). Do not use the build script above the root as that seemed to mess things up for me. The size of my kernel is approx ~5meg with the initramfs included and ~3 without. Then used Heimdall to push it on.

I didn't make any mods as of yet. Just a quest for knowledge and tinkering. Just making sure I can when I need to.

What exactly did you modify? Here's my config, as related to INITRAMFS:
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_INITRAMFS_COMPRESSION_NONE=y
# CONFIG_INITRAMFS_COMPRESSION_GZIP is not set
# CONFIG_INITRAMFS_COMPRESSION_BZIP2 is not set
# CONFIG_INITRAMFS_COMPRESSION_LZMA is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
My kernel size is only 2.9 megs. What else did you specify that has your kernel at 5 megs?
Thanks

you don't have the initramfs source file specified. Put the complete path to the initramfs in the config.

Even when I specified the file location generated during the compile, it still didn't work...size only 3 meg. Are you using the ramdisk.img generated and output into Android/out/target/product/...? Or, did you pull boot.img from the device and split ramdisk.img from the kernel?

chuckbeasley said:
Even when I specified the file location generated during the compile, it still didn't work...size only 3 meg. Are you using the ramdisk.img generated and output into Android/out/target/product/...? Or, did you pull boot.img from the device and split ramdisk.img from the kernel?
Click to expand...
Click to collapse
yep, i pulled it from the device

Would you please tell me how you did it exactly? I've been attempting over the past several hours and haven't been able to find a tool that would split boot.img. They keep telling me that it's not a valid image, but I pulled it from the device.

chuckbeasley said:
Would you please tell me how you did it exactly? I've been attempting over the past several hours and haven't been able to find a tool that would split boot.img. They keep telling me that it's not a valid image, but I pulled it from the device.
Click to expand...
Click to collapse
I used the script from
http://forum.xda-developers.com/wiki/index.php?title=Extract_initramfs_from_zImage
to get the initramfs from the zImage pulled from the device.

Much appreciated! I'll try this later tonight. Right now, I need a break...

I used verizon_zImage from ClockworkMod, but it fails the extraction with a gzip invalid compressed data--format violated error. How can I pull the zImage directly from the phone? It seems that boot.img doesn't work either.
Thanks

Here are the error messages I'm receiving for both verizon_zImage and boot.img, which I pulled from the GT:
[email protected]:~/ramdisk$ ./extract_initramfs verizon_zImage
-I- Extracting kernel image from verizon_zImage (start = 13117)
gzip: stdin: decompression OK, trailing garbage ignored
5979431+0 records in
5979431+0 records out
5979431 bytes (6.0 MB) copied, 195.453 s, 30.6 kB/s
-I- Extracting compressed cpio image from kernel image (start = 5410216)
gzip: stdin: invalid compressed data--format violated
-I- Extracting initramfs image from /tmp/cpio.img (start = , end = 11)
dd: invalid number `'
[email protected]:~/ramdisk$ ./extract_initramfs boot.img
-I- Extracting kernel image from boot.img (start = 13117)
gzip: stdin: decompression OK, trailing garbage ignored
-I- Extracting compressed cpio image from kernel image (start = 5410216)
gzip: stdin: invalid compressed data--format violated
-I- Extracting initramfs image from /tmp/cpio.img (start = , end = 11)
dd: invalid number `'

Looks like the script had a bug and has been updated. Here's the link: http://forum.xda-developers.com/showthread.php?p=8679959
Here's the updated script that allowed me to extract initramfs.cpio from boot.img:
#!/bin/sh
# This is an update version of the script found at
# http://forum.xda-developers.com/wiki/index.php?title=Extract_initramfs_from_zImage
#
# The problem with that script is that the gzip magic number occasionally occur
# naturally, meaning that some non-compressed files get uncompressed.
zImage=$1
#========================================================
# find start of gziped kernel object in the zImage file:
#========================================================
pos=`grep -P -a -b -m 1 --only-matching $'\x1F\x8B\x08' $zImage | cut -f 1 -d :`
echo -n "-I- Extracting kernel image from $zImage (start = $pos)"
dd if=$zImage bs=1 skip=$pos | gunzip > /tmp/kernel.img
#==========================================================================
# find start and end of the "cpio" initramfs image inside the kernel object:
# ASCII cpio header starts with '070701'
# The end of the cpio archive is marked with an empty file named TRAILER!!!
#==========================================================================
start=`grep -a -b -m 1 --only-matching '070701' /tmp/kernel.img | head -1 | cut -f 1 -d :`
end=`grep -a -b -m 1 --only-matching 'TRAILER!!!' /tmp/kernel.img | head -1 | cut -f 1 -d :`
if [ $start = "" || $end = "" ]; then
#========================================================================
# the cpio archive must be archived
#========================================================================
echo "-I- Extracting compressed cpio image from kernel image (start = $pos)"
pos=`grep -P -a -b -m 1 --only-matching $'\x1F\x8B\x08' /tmp/kernel.img | cut -f 1 -d :`
dd if=/tmp/kernel.img bs=1 skip=$pos | gunzip > /tmp/cpio.img
start=`grep -a -b -m 1 --only-matching '070701' /tmp/cpio.img | head -1 | cut -f 1 -d :`
end=`grep -a -b -m 1 --only-matching 'TRAILER!!!' /tmp/cpio.img | head -1 | cut -f 1 -d :`
inputfile=/tmp/cpio.img
else
echo -n "-I- Already uncompressed cpio.img, not decompressing"
inputfile=/tmp/kernel.img
fi
end=$((end + 10))
count=$((end - start))
if (($count < 0)); then
echo "-E- Couldn't match start/end of the initramfs image."
exit
fi
echo "-I- Extracting initramfs image from $inputfile (start = $start, end = $end)"
dd if=$inputfile bs=1 skip=$start count=$count > initramfs.cpio

chuckbeasley said:
I used verizon_zImage from ClockworkMod, but it fails the extraction with a gzip invalid compressed data--format violated error. How can I pull the zImage directly from the phone? It seems that boot.img doesn't work either.
Thanks
Click to expand...
Click to collapse
I used rotohammer's backup method to pull the zImage from the device.
http://forum.xda-developers.com/showthread.php?t=850359&highlight=backup+install+kernel

So do you guys have working kernels ?
I know from my Nexus days that custom kernels can made a massive difference to performance on the beast, so I am looking forward to seeing what people can do with the TAB
Keep up the good work !

I've built my own kernel to see if I could work around the dialing limitation on my VZW tab. Right now, it crashes randomly, but it does boot! I'm looking into the difference between the international version of Onedram and Verizon's version and why Verizon includes a OnedramRecovery unit. My kernel doesn't reference OnedramRecovery and I made more mods. So, I haven't isolated what is causing the instability. Right now, I'm back to Koush's kernel. I'll keep you informed on my progress.
Sent from my SCH-I800 using XDA App

Help!! stuck in bootloop..

i got a error after trying to flash kpe via odin in my i9003 galaxy sl. after flashing the pda, bootloader, csc, phone the phone doesn't restarts but the recovery comes up showing this message.
E:cant mount /dev/block/mmcblk0p3
your storage not prepared yet, please use ui menu for format and reboot actions.
now if i restart the phone it keeps on showing bootscreen.
plz help!!

re-flash maybe?

second to Jack..Reflash

First of all flash the pit file and then flash the rest....please dont make an unnecessary thread for this...ask questions in relevant threads
Sent from my GT-I9003

ronhoover88 said:
First of all flash the pit file and then flash the rest....please dont make an unnecessary thread for this...ask questions in relevant threads
Sent from my GT-I9003
Click to expand...
Click to collapse
i have reflashed like a 100 times now.. its not working.. the same error.. and for all roms!!

Starting recovery on Sat Jan 1 00:02:02 2000
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery - for I9003 by Skin1980
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /cache rfs /dev/block/stl11 (null)
2 /data rfs /dev/block/mmcblk0p3 (null)
3 /system rfs /dev/block/stl9 (null)
4 /datadata rfs /dev/block/stl10 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 (null)
6 /sd-ext vfat /dev/block/mmcblk0p1 (null)
touch: /etc/mtab: No such file or directory
W:Unable to create /etc/fstab!
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=reboot_recovery
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=latona
ro.revision=0
dpm.allowcamera=0
init.svc.recovery=running
init.svc.adbd=stopping
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mount: mounting /dev/block/mmcblk0p3 on /data failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p3 (File exists)
W:failed to mount /dev/block/mmcblk0p3 (No such file or directory)
Error mounting /data!
this is a catlog after error

minzip: Extracted file "/system/T9DB/phonepad_lt.kdb"
minzip: Extracted file "/system/T9DB/phonepad_lv.kdb"
minzip: Extracted file "/system/T9DB/phonepad_nl.kdb"
minzip: Extracted file "/system/T9DB/phonepad_pl.kdb"
minzip: Extracted file "/system/T9DB/phonepad_pt.kdb"
minzip: Extracted file "/system/T9DB/phonepad_ru.kdb"
minzip: Extracted file "/system/T9DB/phonepad_sk.kdb"
minzip: Extracted file "/system/T9DB/phonepad_tr.kdb"
minzip: Extracted file "/system/T9DB/phonepad_uk.kdb"
minzip: Extracted file "/system/T9DB/qwerty_cs.kdb"
minzip: Extracted file "/system/T9DB/qwerty_de.kdb"
minzip: Extracted file "/system/T9DB/qwerty_el.kdb"
minzip: Extracted file "/system/T9DB/qwerty_en.kdb"
minzip: Extracted file "/system/T9DB/qwerty_es.kdb"
minzip: Extracted file "/system/T9DB/qwerty_et.kdb"
minzip: Extracted file "/system/T9DB/qwerty_fr.kdb"
minzip: Extracted file "/system/T9DB/qwerty_hu.kdb"
minzip: Extracted file "/system/T9DB/qwerty_it.kdb"
minzip: Extracted file "/system/T9DB/qwerty_ko.kdb"
minzip: Extracted file "/system/T9DB/qwerty_lt.kdb"
minzip: Extracted file "/system/T9DB/qwerty_lv.kdb"
minzip: Extracted file "/system/T9DB/qwerty_nl.kdb"
minzip: Extracted file "/system/T9DB/qwerty_pl.kdb"
minzip: Extracted file "/system/T9DB/qwerty_pt.kdb"
minzip: Extracted file "/system/T9DB/qwerty_ru.kdb"
minzip: Extracted file "/system/T9DB/qwerty_sk.kdb"
minzip: Extracted file "/system/T9DB/qwerty_tr.kdb"
minzip: Extracted file "/system/T9DB/qwerty_uk.kdb"
minzip: Extracted file "/system/csc/CPW/system/CSCFiles.txt"
minzip: Extracted file "/system/csc/CPW/system/CSCVersion.txt"
minzip: Extracted file "/system/csc/CPW/system/SW_Configuration.xml"
minzip: Extracted file "/system/csc/CPW/system/csc/contents.db"
minzip: Extracted file "/system/csc/CPW/system/csc/customer.xml"
minzip: Extracted file "/system/csc/CPW/system/csc/feature.xml"
minzip: Extracted file "/system/csc/CPW/system/csc/others.xml"
minzip: Extracted file "/system/csc/CPW/system/csc/sales_code.dat"
minzip: Extracted file "/system/csc/DBT/system/CSCFiles.txt"
minzip: Extracted file "/system/csc/DBT/system/CSCVersion.txt"
minzip: Extracted file "/system/csc/DBT/system/SW_Configuration.xml"
minzip: Extracted file "/system/csc/DBT/system/csc/contents.db"
minzip: Extracted file "/system/csc/DBT/system/csc/customer.xml"
minzip: Extracted file "/system/csc/DBT/system/csc/feature.xml"
minzip: Extracted file "/system/csc/DBT/system/csc/others.xml"
minzip: Extracted file "/system/csc/DBT/system/csc/sales_code.dat"
minzip: Extracted file "/system/csc/ITV/system/CSCFiles.txt"
minzip: Extracted file "/system/csc/ITV/system/CSCVersion.txt"
minzip: Extracted file "/system/csc/ITV/system/SW_Configuration.xml"
minzip: Extracted file "/system/csc/ITV/system/csc/contents.db"
minzip: Extracted file "/system/csc/ITV/system/csc/customer.xml"
minzip: Extracted file "/system/csc/ITV/system/csc/feature.xml"
minzip: Extracted file "/system/csc/ITV/system/csc/others.xml"
minzip: Extracted file "/system/csc/ITV/system/csc/sales_code.dat"
minzip: Extracted file "/system/csc/KOR/system/CSCFiles.txt"
minzip: Extracted file "/system/csc/KOR/system/CSCVersion.txt"
minzip: Extracted file "/system/csc/KOR/system/SW_Configuration.xml"
minzip: Extracted file "/system/csc/KOR/system/csc/contents.db"
minzip: Extracted file "/system/csc/KOR/system/csc/customer.xml"
minzip: Extracted file "/system/csc/KOR/system/csc/feature.xml"
minzip: Extracted file "/system/csc/KOR/system/csc/others.xml"
minzip: Extracted file "/system/csc/KOR/system/csc/sales_code.dat"
minzip: Extracted file "/system/csc/XEF/system/CSCFiles.txt"
minzip: Extracted file "/system/csc/XEF/system/CSCVersion.txt"
minzip: Extracted file "/system/csc/XEF/system/SW_Configuration.xml"
minzip: Extracted file "/system/csc/XEF/system/csc/contents.db"
minzip: Extracted file "/system/csc/XEF/system/csc/customer.xml"
minzip: Extracted file "/system/csc/XEF/system/csc/feature.xml"
minzip: Extracted file "/system/csc/XEF/system/csc/others.xml"
minzip: Extracted file "/system/csc/XEF/system/csc/sales_code.dat"
minzip: Extracted file "/system/csc/XEO/system/CSCFiles.txt"
minzip: Extracted file "/system/csc/XEO/system/CSCVersion.txt"
minzip: Extracted file "/system/csc/XEO/system/SW_Configuration.xml"
minzip: Extracted file "/system/csc/XEO/system/csc/contents.db"
minzip: Extracted file "/system/csc/XEO/system/csc/customer.xml"
minzip: Extracted file "/system/csc/XEO/system/csc/feature.xml"
minzip: Extracted file "/system/csc/XEO/system/csc/others.xml"
minzip: Extracted file "/system/csc/XEO/system/csc/sales_code.dat"
minzip: Extracted file "/system/csc/XEU/system/CSCFiles.txt"
minzip: Extracted file "/system/csc/XEU/system/CSCVersion.txt"
minzip: Extracted file "/system/csc/XEU/system/SW_Configuration.xml"
minzip: Extracted file "/system/csc/XEU/system/csc/contents.db"
minzip: Extracted file "/system/csc/XEU/system/csc/customer.xml"
minzip: Extracted file "/system/csc/XEU/system/csc/feature.xml"
minzip: Extracted file "/system/csc/XEU/system/csc/others.xml"
minzip: Extracted file "/system/csc/XEU/system/csc/sales_code.dat"
minzip: Extracted file "/system/csc/contents.db"
minzip: Extracted file "/system/csc/customer.xml"
minzip: Extracted file "/system/csc/feature.xml"
minzip: Extracted file "/system/csc/others.xml"
minzip: Extracted file "/system/csc/sales_code.dat"
script result was [/system]
DEVENC: crypt_device(0), sdcard_unavailable(0)
[Formatting data]
format_rfs_device -> /sbin/fat.format -F 32 -s 4 -S 4096 /dev/block/mmcblk0p3
fat_init_volume[149]: Check here: No such file or directory
Fail to format
run_program: child exited with status 255
E :format_volume: rfs format failed on /dev/block/mmcblk0p3
format_rfs_device -> /sbin/fat.format -F 16 -s 1 -S 4096 /dev/block/stl10
Success to format
format_rfs_device -> /sbin/fat.format -F 16 -s 1 -S 4096 /dev/block/stl11
Success to format
mount_with_dev_path: mount /dev/block/stl3 at /dev/block/stl3 ret=-1DEVENC:remo
ve_devenc_meta_data: CryptRootMount mounted rm failed for /efs/cryptprop_data, N
o such file or directory
Can't mount /dev/block/mmcblk0p3
(No such file or directory)
rm failed for /efs/cryptprop_dbdata, No such file or directory
Can't mount /dev/block/mmcblk0p3
(No such file or directory)
rm failed for /efs/cryptprop_cache, No such file or directory
Can't mount /dev/block/mmcblk0p3
(No such file or directory)
rm failed for /efs/cryptprop_policy, No such file or directory
Can't mount /dev/block/mmcblk0p3
(No such file or directory)
DEVENC:remove_devenc_meta_data:sdcard(0)
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 996.74
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : Latona Samsung Board
Revision : 0000
Serial : 0000000000000000
=nProcessor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 996.74
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : Latona Samsung Board
Revision : 0000
Serial : 0000000000000000
=nrm failed for /efs/meta_dump_*, No such file or directory
rm failed for /efs/dmp, No such file or directory
rm failed for /efs/cryptprop_lock*, No such file or directory
rm failed for /efs/cryptprop_per*, No such file or directory
rm failed for /efs/cryptprop_applied_result, No such file or directory
rm failed for /efs/cryptprop_MaxAttempts, No such file or directory
rm failed for /efs/data, No such file or directory
mount_with_dev_path: mount /dev/block/stl3 at /dev/block/stl3 ret=-1Data wipe f
ailed.
[ Appling Multi-CSC ]
mount '/dev/block/stl3' '/efs'(rfs)
multi_csc :: code '/system/csc/KOR/system/'
check_point2: /system/
check_point2: access /
check_point2: access /system/
check_point2: access /system/
/system/csc/KOR/system/:
cp_file++ src:/system/csc/KOR/system//CSCFiles.txt dst:/system//CSCFiles.txt
cp_file: write to /system//CSCFiles.txt 316 bytes
cp_file++ src:/system/csc/KOR/system//CSCVersion.txt dst:/system//CSCVersion.txt
cp_file: write to /system//CSCVersion.txt 12 bytes
cp_file++ src:/system/csc/KOR/system//SW_Configuration.xml dst:/system//SW_Confi
guration.xml
cp_file: write to /system//SW_Configuration.xml 703 bytes
/system/csc/KOR/system//csc:
check_point2: /system//csc
check_point2: access /
check_point2: access /system/
check_point2: access /system//
check_point2: access /system//csc
cp_file++ src:/system/csc/KOR/system//csc/contents.db dst:/system//csc/contents.
db
cp_file: write to /system//csc/contents.db 4096 bytes
cp_file++ src:/system/csc/KOR/system//csc/customer.xml dst:/system//csc/customer
.xml
cp_file: write to /system//csc/customer.xml 1306 bytes
cp_file++ src:/system/csc/KOR/system//csc/feature.xml dst:/system//csc/feature.x
ml
cp_file: write to /system//csc/feature.xml 515 bytes
cp_file++ src:/system/csc/KOR/system//csc/others.xml dst:/system//csc/others.xml
cp_file: write to /system//csc/others.xml 2800 bytes
cp_file++ src:/system/csc/KOR/system//csc/sales_code.dat dst:/system//csc/sales_
code.dat
cp_file: write to /system//csc/sales_code.dat 4 bytes
copy_kernel_file :: create kernel log file '/tmp/kernel.log'
copy_kernel_file :: create kernel log file '/cache/recovery/recovery_kernel_log'
mount '/dev/block/stl11' '/cache'(rfs)
copy_log_file :: create recovery log file '/cache/recovery/log'
copy_log_file :: create recovery log file '/cache/recovery/last_log'
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (115), visible(1)
key press -> key (102), visible(1)
[ Wiping data ]
key press -> key (102), visible(1)
copy_log_file :: create recovery log file '/cache/recovery/log'
copy_log_file :: create recovery log file '/cache/recovery/last_log'
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (102), visible(1)
[ Wiping data ]
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (114), visible(1)
key press -> key (102), visible(1)
mount '/dev/block/stl3' '/efs'(rfs)
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 597.64
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : Latona Samsung Board
Revision : 0000
Serial : 0000000000000000
=nformat_rfs_device -> /sbin/fat.format -F 32 -s 4 -S 4096 /dev/block/mmcblk0p3
fat_init_volume[149]: Check here: No such file or directory
Fail to format
run_program: child exited with status 255
E :format_volume: rfs format failed on /dev/block/mmcblk0p3
format_rfs_device -> /sbin/fat.format -F 16 -s 1 -S 4096 /dev/block/stl10
Success to format
mount_with_dev_path: mount /dev/block/stl3 at /dev/block/stl3 ret=-1DEVENC:remo
ve_devenc_meta_data: CryptRootMount mounted rm failed for /efs/cryptprop_data, N
o such file or directory
Can't mount /dev/block/mmcblk0p3
(No such file or directory)
rm failed for /efs/cryptprop_dbdata, No such file or directory
Can't mount /dev/block/mmcblk0p3
(No such file or directory)
rm failed for /efs/cryptprop_cache, No such file or directory
Can't mount /dev/block/mmcblk0p3
(No such file or directory)
rm failed for /efs/cryptprop_policy, No such file or directory
Can't mount /dev/block/mmcblk0p3
(No such file or directory)
DEVENC:remove_devenc_meta_data:sdcard(0)
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 597.64
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : Latona Samsung Board
Revision : 0000
Serial : 0000000000000000
=nProcessor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 597.64
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : Latona Samsung Board
Revision : 0000
Serial : 0000000000000000
=nrm failed for /efs/meta_dump_*, No such file or directory
rm failed for /efs/dmp, No such file or directory
rm failed for /efs/cryptprop_lock*, No such file or directory
rm failed for /efs/cryptprop_per*, No such file or directory
rm failed for /efs/cryptprop_applied_result, No such file or directory
rm failed for /efs/cryptprop_MaxAttempts, No such file or directory
rm failed for /efs/data, No such file or directory
format_rfs_device -> /sbin/fat.format -F 16 -s 1 -S 4096 /dev/block/stl11
Success to format
copy_log_file :: create recovery log file '/cache/recovery/log'
mount '/dev/block/stl11' '/cache'(rfs)
copy_log_file :: create recovery log file '/cache/recovery/last_log'
$
this is the log after flashing with odin.

Download XXKPE flash files again
I think this has something to do with the XXKPE flash files..can you download the flash files again and try flashing..

kirankowshik said:
I think this has something to do with the XXKPE flash files..can you download the flash files again and try flashing..
Click to expand...
Click to collapse
+1 Try downloading the files again it could be because of corrupted files.

its not happening... as i said... i tries flashing other firmware as well (kb3) but still the same issue.

try to push the /dev/block file through adb.extract in ur pc using zipping software

sakindia123 said:
try to push the /dev/block file through adb.extract in ur pc using zipping software
Click to expand...
Click to collapse
where can i find this file. nd how do i do this???

ashishsaggu said:
where can i find this file. nd how do i do this???
Click to expand...
Click to collapse
extract system.rfs from the pda file and search for mm8y3(whatever is written).copy or push to /dev/block/ using cp command in terminal

sakindia123 said:
extract system.rfs from the pda file and search for mm8y3(whatever is written).copy or push to /dev/block/ using cp command in terminal
Click to expand...
Click to collapse
how do i extract it???

Ok, before you get into complexes, try this:
Since you can boot into recoveery, use Skin1980's ext4-conversion zip file. Put it into your SD card. Boot into recovery and choose "Install from zip file" in the menu. Navigate to the ext4-conversion .zip file on the SD card and select it. This will completely format your phone's data and system partitions to ext4.
Now, remember DO NOT REBOOT PHONE!!!
At this point you can either restore your Nandroid backup (provided you have an ext4 compatible CWM and have taken one.
Else, switch off the phone, reflash the firmware from scratch (.pit file, repartition and all).
Try this and tell me if it works.

Erahgon said:
Ok, before you get into complexes, try this:
Since you can boot into recoveery, use Skin1980's ext4-conversion zip file. Put it into your SD card. Boot into recovery and choose "Install from zip file" in the menu. Navigate to the ext4-conversion .zip file on the SD card and select it. This will completely format your phone's data and system partitions to ext4.
Now, remember DO NOT REBOOT PHONE!!!
At this point you can either restore your Nandroid backup (provided you have an ext4 compatible CWM and have taken one.
Else, switch off the phone, reflash the firmware from scratch (.pit file, repartition and all).
Try this and tell me if it works.
Click to expand...
Click to collapse
i m not able to mount sd card in recovery, both internal and external!! so cant flash any zip.

I am also not able to format or mount /data!!!

The "sdcard" in CWM actually means your external SD card. Try reformatting that.
Use an ext4 compatible CWM, like the one for XXKPE and try again to mount anything. Run a total format/wipe using that CWM.
Even I couldn't mount "/data" and stuff when I ran through an entire experience of downgrading back to my original firmware for my phone from XXKPE with ext4 and CF-ROOT.
It all worked fine when I methodically when about solving the problems as such. Now I'm back up and running!

Erahgon said:
The "sdcard" in CWM actually means your external SD card. Try reformatting that.
Use an ext4 compatible CWM, like the one for XXKPE and try again to mount anything. Run a total format/wipe using that CWM.
Even I couldn't mount "/data" and stuff when I ran through an entire experience of downgrading back to my original firmware for my phone from XXKPE with ext4 and CF-ROOT.
It all worked fine when I methodically when about solving the problems as such. Now I'm back up and running!
Click to expand...
Click to collapse
i can not event mount/format the external sd card!! otherwise i could have just used the nandriod backup.... and the problem is with the internal one cause that seems to give he errors while flashing.

ashishsaggu ... I have same errors with bootloop... with "can't mout /data", "Can't mount /sdcard" etc.... Russian forum can't help me too.. :'(

[Q] TWRP flashable ZIP for VS980 failed to flash under TWRP

This seems to be an old problem.
My VS980 is on TWRP v2.8.0.1, and I see there is a newer TWRP from the official site: openrecovery-twrp-2.8.1.0-vs980.zip
So I downloaded that and put it on sdcard, by "installing" this zip, the error was as follows:
Code:
Installing '/usb_otg/ROM/openrecovery-twrp-2.8.1.0-vs980.zip'...
Checking for MD5 file...
MD5 matched
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
*******************************
* TWRP Recovery by Dees_Troy *
*******************************
minzip: Extracted file "/tmp/loki.sh"
minzip: Extracted file "/tmp/loki/loki_flash"
minzip: Extracted file "/tmp/loki/loki_patch"
about to run program [/tmp/loki.sh] with 1 args
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.033627 seconds, 29.7MB/s
[+] loki_patch v2.1
[-] Unsupported aboot image.
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/loki.sh") == 0
assert failed: run_program("/tmp/loki.sh") == 0
Is it because my aboot is already lokified? Or am I doing the upgrade wrong?

[Q] Installing Beanstalk ROM on N910G

Hi guys, I's trying to install custom ROM on my Samsung Galaxy Note 4 (N910G variant). However, I keep getting an error. I'm running Android 4.4.4 KitKat with TWRP 2.8.1. The ROM I'm trying to install is Beanstalk ROM.
Here's the log:
Installing '/sdcard/Download/BeanStalk-5.0035-20150222-trltedt.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
minzip: Extracted 3 file(s)
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
BeanStalk
cp: can't stat '/system/addon.d/*': No such file or directory
chmod: /tmp/addon.d/*.sh: No such file or directory
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
**********************************************
* ____ _ _ _ *
*| __ ) ___ __ _ _ __ ___| |_ __ _| | | __*
*| _ \ / _ \/ _` | '_ \/ __| __/ _` | | |/ /*
*| |_) | __/ (_| | | | \__ \ || (_| | | < *
*|____/ \___|\__,_|_| |_|___/\__\__,_|_|_|\_\*
* *
**********************************************
******************************************
************ BEANSTALK ROM *************
******************************************
* Compiled: Sun Feb 22 01:41:39 CST 2015
* Device: SM-N910T (trltetmo)
******************************************
erasing 972800 blocks
blkdiscard failed: Invalid argument
writing 134489 blocks of new data
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/BeanStalk-5.0035-20150222-trltedt.zip'
Error flashing zip '/sdcard/Download/BeanStalk-5.0035-20150222-trltedt.zip'
Updating partition details...
E:Unable to mount '/system'
Please help, I rooted my device just because i want to install this custom ROM :crying:

Because beanstalk isn't for the N910G it's for the Tmobile variant (N910T)

thelestat said:
Because beanstalk isn't for the N910G it's for the Tmobile variant (N910T)
Click to expand...
Click to collapse
Is there any way i can get it running on my n910G?

error while repo init

Hellow guys, i have an hP laptop with 16 gigs of ram and enough hdd space. also i am running xubuntu 16.04 where i was previously able to compile custom roms. however recently my hard drive had crashed and i had to recover using easeUS. then i formatted it to exFat. Xubuntu as such is giving me write operations on exFat devices. my problem is now whenever am using repo sync a custom rom source it gives error like
Code:
[email protected]:/media/ayan/Ayan/Mobile/mo/pixel$ repo init -u https://github.com/PixelExperience/manifest -b oreo-mr1
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
remote: Finding sources: 100% (5/5)
remote: Total 5 (delta 0), reused 5 (delta 0)
Unpacking objects: 100% (5/5), done.
From https://gerrit.googlesource.com/git-repo
cf7c083..0f2e45a master -> origin/master
Get https://github.com/PixelExperience/manifest
Traceback (most recent call last):
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/main.py", line 531, in <module>
_Main(sys.argv[1:])
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/main.py", line 507, in _Main
result = repo._Run(argv) or 0
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/main.py", line 180, in _Run
result = cmd.Execute(copts, cargs)
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/subcmds/init.py", line 399, in Execute
self._SyncManifest(opt)
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/subcmds/init.py", line 171, in _SyncManifest
m._InitGitDir(mirror_git=mirrored_manifest_git)
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/project.py", line 2292, in _InitGitDir
self._UpdateHooks()
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/project.py", line 2312, in _UpdateHooks
self._InitHooks()
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/project.py", line 2341, in _InitHooks
os.symlink(os.path.relpath(stock_hook, os.path.dirname(dst)), dst)
OSError: [Errno 38] Function not implemented
[email protected]:/media/ayan/Ayan/Mobile/mo/pixel$
any help would be recommended and appreciated

Ayan Uchiha Choudhury said:
Code:
[email protected]:/media/ayan/Ayan/Mobile/mo/pixel$ repo init -u https://github.com/PixelExperience/manifest -b oreo-mr1
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
remote: Finding sources: 100% (5/5)
remote: Total 5 (delta 0), reused 5 (delta 0)
Unpacking objects: 100% (5/5), done.
From https://gerrit.googlesource.com/git-repo
cf7c083..0f2e45a master -> origin/master
Get https://github.com/PixelExperience/manifest
Traceback (most recent call last):
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/main.py", line 531, in <module>
_Main(sys.argv[1:])
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/main.py", line 507, in _Main
result = repo._Run(argv) or 0
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/main.py", line 180, in _Run
result = cmd.Execute(copts, cargs)
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/subcmds/init.py", line 399, in Execute
self._SyncManifest(opt)
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/subcmds/init.py", line 171, in _SyncManifest
m._InitGitDir(mirror_git=mirrored_manifest_git)
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/project.py", line 2292, in _InitGitDir
self._UpdateHooks()
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/project.py", line 2312, in _UpdateHooks
self._InitHooks()
File "/media/ayan/Ayan/Mobile/mo/pixel/.repo/repo/project.py", line 2341, in _InitHooks
os.symlink(os.path.relpath(stock_hook, os.path.dirname(dst)), dst)
OSError: [Errno 38] Function not implemented
[email protected]:/media/ayan/Ayan/Mobile/mo/pixel$
any help would be recommended and appreciated
Click to expand...
Click to collapse
Wrong place to ask but yeah, have you installed the latest version of repo and python2 ?
Or before that try `rm -rf .repo` and then init again.
Android Building queries can be discussed here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763

Yes yes I did both. I also created a new directory and tried repo init. But still

emmm....
Ayan Uchiha Choudhury said:
Yes yes I did both. I also created a new directory and tried repo init. But still
Click to expand...
Click to collapse
Have you found anything to solution ?

SchafferWang said:
Have you found anything to solution ?
Click to expand...
Click to collapse
Exfat was the problem. Formatted to NTFS to fix it