How do I prepare a file to flash my phone withHow to save an Android Activity state using save instance state?How do I center text horizontally and vertically in a TextView?Why is the Android emulator so slow? How can we speed up the Android emulator?How do I fix android.os.NetworkOnMainThreadException?Android Huawei Ideos X3 (U8510) : Restoring static boot logo and animation from ClockWorkMod backup?Running ARM binaries for Android on Linux ARMLoading custom kernel on Nexus 7Edit android executable fileGoogle's shipping 64-bit SDK stuff by default now?Samsung Opensource: Compiled kernel size is bigger than stock kernel
Professor Roman loves to teach unorthodox Chemistry
How to befriend someone who doesn't like to talk?
Are regulatory compliance checks performed within the EU bloc?
5 band resistor. Red, orange, black, gold and black. It doesn't fit in to normal rules
Do Veracrypt encrypted volumes have any kind of brute force protection?
What's the best way to quit a job mostly because of money?
Why do (or did, until very recently) aircraft transponders wait to be interrogated before broadcasting beacon signals?
What do you call the action of "describing events as they happen" like sports anchors do?
Do SFDX commands count toward limits?
Is there a better way to do partial sums of array items in JavaScript?
Can a Warforged suffer from magical exhaustion?
Why do Bhargava-Skinner-Zhang consider the ordering by height?
How much web presence should I have?
Suppose leased car is totalled: what are financial implications?
That's not my X, its Y is too Z
Grandpa has another non math question
Why is it bad to use your whole foot in rock climbing
What is Gilligan's full Name?
A life of PhD: is it feasible?
What is the STRONGEST end-of-line knot to use if you want to use a steel-thimble at the end, so that you've got a steel-eyelet at the end of the line?
What exactly "triggers an additional time" in the interaction between Afterlife and Teysa Karlov?
What plausible reason could I give for my FTL drive only working in space
Why is the distribution of dark matter in a Galaxy different from the distribution of normal matter?
When to use и or а as “and”?
How do I prepare a file to flash my phone with
How to save an Android Activity state using save instance state?How do I center text horizontally and vertically in a TextView?Why is the Android emulator so slow? How can we speed up the Android emulator?How do I fix android.os.NetworkOnMainThreadException?Android Huawei Ideos X3 (U8510) : Restoring static boot logo and animation from ClockWorkMod backup?Running ARM binaries for Android on Linux ARMLoading custom kernel on Nexus 7Edit android executable fileGoogle's shipping 64-bit SDK stuff by default now?Samsung Opensource: Compiled kernel size is bigger than stock kernel
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I want to create an image for the Arm chip and deploy it on my Samsung Note 3. I have a compiled copy of
the Samsung source. I added another module to this copy for added functionality. I then downloaded a copy
of the stock firmware, which I have used a number of times to flash my phone. I took the boot.img file of
the stock firmware split it open with a tool online, and replaced the zImage with the zImage that I got
from compiling my source. After several attempts, I seem to be able to create a complete tar.md5 file of
everything in the directory of modified stock source. When I flash the phone with this file using Odin,
the file goes in fine, but the phone is stuck in download mode. I am trying to figure out the main cause
of phone going into download mode, and is the root cause one of packing the files incorrectly or did I not
include a file that is required? Here is what I did to create the tar file with md5 authentication:
I created the tar file:
tar -H ustar -c aboot.mbn sbl1.mbn rpm.mbn tz.mbn sdi.mbn NON-HLOS.bin boot.img recovery.img
system.img.ext4 cache.img.ext4 modem.bin > tarfile.tar
cp tarfile.tar tarfile.tar.md5
md5sum tarfile.tar >> tarfile.tar.md5
I then tried to do a sanity check by comparing the file with a tar archive in an image I have used to
flash my phone with using the file command, and here is what I get ( note: I put my results in the
/expermental directory and the unpacked validated tar file in /originalstck/originaltarfile directory ) (
Note also that the file called tarfile below is the result of packing my files vs.
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 is what was in the validated stock rom ) :
@ubuntu:~/expermental_stock$ file *
aboot.mbn: Hitachi SH big-endian COFF object, not stripped
boot.img: data
cache.img.ext4: data
info: ASCII text
initramfs.cpio.gz: gzip compressed data, from Unix
modem.bin: x86 boot sector
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive
N900PVPUCNC5_N900PSPTCNC5_SPR.zip: Zip archive data, at least v2.0 to extract
NON-HLOS.bin: x86 boot sector
recovery.img: data
rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
sbl1.mbn: data
sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
SS_DL.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS
Windows
system.img.ext4: data
tarfile.tar: POSIX tar archive (GNU)
tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
zImage: Linux kernel ARM boot executable zImage (little-
endian)
file ~/originalstock/originaltarfile/*
/aboot.mbn: Hitachi SH big-endian COFF object, not stripped
/boot.img: data
/cache.img.ext4: data
/modem.bin: x86 boot sector
/N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive
/NON-HLOS.bin: x86 boot sector
/recovery.img: data
/rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
/sbl1.mbn: data
/sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
/system.img.ext4: data
/tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
( Note: Here tarfile.tar is the file I made, and I am comparing it with the original tar file that came with the stock rom, which is called N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5.) There are two things that concern me with the above output as I am comparing tarfile.tar in /experimentalstock directory with N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 file in the originalstock/originaltarfile dirctory. 1- tarfile.tar is smaller. I added more modules to the source. But that may be explained by the source I started from. I did compare the boot.img files, and the one I created by adding my zImage to it is larger than the one that came with stock rom. I started from the Samsung source code which may not contain the telecom provider's files. 2- My other concern is the output associated with the file command; for tar.file I get: POSIX tar archive (GNU) and for N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 I get POSIX tar archive. Is there a difference between the GNU version vs. whatever is the default format?
My other question is how can see what is going on during the boot when I push my image to the phone? Is there some way I can save the logs on a phone that is unrooted?
According to one of the online sources I used to get this far, I also need to or may include kernel modules. As far as I remember these files have a km extension? I did a search in my Kernel's directory, and do not see any files with this extension:
user@ubuntu:~$ locate -r '^/home/user/androidkernel3/.*.km$'
/home/user/androidkernel3/arch/arm/mvp/commkm
/home/user/androidkernel3/arch/arm/mvp/mvpkm
/home/user/androidkernel3/arch/arm/mvp/oektestkm
/home/user/androidkernel3/arch/arm/mvp/pvtcpkm
user@ubuntu:~$
Sean
android android-source asked Nov 2 '14 at 20:03
user3326293user3326293
402728
add a comment |
I want to create an image for the Arm chip and deploy it on my Samsung Note 3. I have a compiled copy of
the Samsung source. I added another module to this copy for added functionality. I then downloaded a copy
of the stock firmware, which I have used a number of times to flash my phone. I took the boot.img file of
the stock firmware split it open with a tool online, and replaced the zImage with the zImage that I got
from compiling my source. After several attempts, I seem to be able to create a complete tar.md5 file of
everything in the directory of modified stock source. When I flash the phone with this file using Odin,
the file goes in fine, but the phone is stuck in download mode. I am trying to figure out the main cause
of phone going into download mode, and is the root cause one of packing the files incorrectly or did I not
include a file that is required? Here is what I did to create the tar file with md5 authentication:
I created the tar file:
tar -H ustar -c aboot.mbn sbl1.mbn rpm.mbn tz.mbn sdi.mbn NON-HLOS.bin boot.img recovery.img
system.img.ext4 cache.img.ext4 modem.bin > tarfile.tar
cp tarfile.tar tarfile.tar.md5
md5sum tarfile.tar >> tarfile.tar.md5
I then tried to do a sanity check by comparing the file with a tar archive in an image I have used to
flash my phone with using the file command, and here is what I get ( note: I put my results in the
/expermental directory and the unpacked validated tar file in /originalstck/originaltarfile directory ) (
Note also that the file called tarfile below is the result of packing my files vs.
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 is what was in the validated stock rom ) :
@ubuntu:~/expermental_stock$ file *
aboot.mbn: Hitachi SH big-endian COFF object, not stripped
boot.img: data
cache.img.ext4: data
info: ASCII text
initramfs.cpio.gz: gzip compressed data, from Unix
modem.bin: x86 boot sector
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive
N900PVPUCNC5_N900PSPTCNC5_SPR.zip: Zip archive data, at least v2.0 to extract
NON-HLOS.bin: x86 boot sector
recovery.img: data
rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
sbl1.mbn: data
sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
SS_DL.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS
Windows
system.img.ext4: data
tarfile.tar: POSIX tar archive (GNU)
tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
zImage: Linux kernel ARM boot executable zImage (little-
endian)
file ~/originalstock/originaltarfile/*
/aboot.mbn: Hitachi SH big-endian COFF object, not stripped
/boot.img: data
/cache.img.ext4: data
/modem.bin: x86 boot sector
/N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive
/NON-HLOS.bin: x86 boot sector
/recovery.img: data
/rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
/sbl1.mbn: data
/sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
/system.img.ext4: data
/tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
( Note: Here tarfile.tar is the file I made, and I am comparing it with the original tar file that came with the stock rom, which is called N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5.) There are two things that concern me with the above output as I am comparing tarfile.tar in /experimentalstock directory with N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 file in the originalstock/originaltarfile dirctory. 1- tarfile.tar is smaller. I added more modules to the source. But that may be explained by the source I started from. I did compare the boot.img files, and the one I created by adding my zImage to it is larger than the one that came with stock rom. I started from the Samsung source code which may not contain the telecom provider's files. 2- My other concern is the output associated with the file command; for tar.file I get: POSIX tar archive (GNU) and for N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 I get POSIX tar archive. Is there a difference between the GNU version vs. whatever is the default format?
My other question is how can see what is going on during the boot when I push my image to the phone? Is there some way I can save the logs on a phone that is unrooted?
According to one of the online sources I used to get this far, I also need to or may include kernel modules. As far as I remember these files have a km extension? I did a search in my Kernel's directory, and do not see any files with this extension:
user@ubuntu:~$ locate -r '^/home/user/androidkernel3/.*.km$'
/home/user/androidkernel3/arch/arm/mvp/commkm
/home/user/androidkernel3/arch/arm/mvp/mvpkm
/home/user/androidkernel3/arch/arm/mvp/oektestkm
/home/user/androidkernel3/arch/arm/mvp/pvtcpkm
user@ubuntu:~$
Sean
android android-source asked Nov 2 '14 at 20:03
user3326293user3326293
402728
3
This is in fact a software development question - the poster is trying to install and run their freshly compiled program. That said program is an operating system in no way makes the question off topic.
– Chris Stratton
Nov 2 '14 at 20:17
@ChrisStratton If you were being really picky, I'd say the Android Stack Exchange could be a better place: android.stackexchange.com. However as you said, it's a software development question and belongs here, however the users of the Android Stack Exchange may be able to supply more help in this instance.
– AStopher
Nov 2 '14 at 21:22
@cybermonkey My question is more related to native development for the arm chip; not so much Android development. I did not use a single line of java. All of the above has been done with GNU make.
– user3326293
Nov 2 '14 at 21:30
@cybermonkey This would not actually be an appropriate question for the Android site; at the root, it's all about how the app is packaged for deployment.
– Andrew Barber
Nov 2 '14 at 22:15
Unless you have already unlocked the bootloader I doubt this is going to work. I would expect that the Note 3 will have a locked bootloader, which is not going to boot your custom kernel as it won't have been signed by Samsung's relevant keys. When you flash the "stock" firmware images from Samsung, they will have been appropriately signed, hence why they work and why your modified ones won't.
– Maks
Jul 8 '15 at 0:26
add a comment |
I want to create an image for the Arm chip and deploy it on my Samsung Note 3. I have a compiled copy of
the Samsung source. I added another module to this copy for added functionality. I then downloaded a copy
of the stock firmware, which I have used a number of times to flash my phone. I took the boot.img file of
the stock firmware split it open with a tool online, and replaced the zImage with the zImage that I got
from compiling my source. After several attempts, I seem to be able to create a complete tar.md5 file of
everything in the directory of modified stock source. When I flash the phone with this file using Odin,
the file goes in fine, but the phone is stuck in download mode. I am trying to figure out the main cause
of phone going into download mode, and is the root cause one of packing the files incorrectly or did I not
include a file that is required? Here is what I did to create the tar file with md5 authentication:
I created the tar file:
tar -H ustar -c aboot.mbn sbl1.mbn rpm.mbn tz.mbn sdi.mbn NON-HLOS.bin boot.img recovery.img
system.img.ext4 cache.img.ext4 modem.bin > tarfile.tar
cp tarfile.tar tarfile.tar.md5
md5sum tarfile.tar >> tarfile.tar.md5
I then tried to do a sanity check by comparing the file with a tar archive in an image I have used to
flash my phone with using the file command, and here is what I get ( note: I put my results in the
/expermental directory and the unpacked validated tar file in /originalstck/originaltarfile directory ) (
Note also that the file called tarfile below is the result of packing my files vs.
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 is what was in the validated stock rom ) :
@ubuntu:~/expermental_stock$ file *
aboot.mbn: Hitachi SH big-endian COFF object, not stripped
boot.img: data
cache.img.ext4: data
info: ASCII text
initramfs.cpio.gz: gzip compressed data, from Unix
modem.bin: x86 boot sector
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive
N900PVPUCNC5_N900PSPTCNC5_SPR.zip: Zip archive data, at least v2.0 to extract
NON-HLOS.bin: x86 boot sector
recovery.img: data
rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
sbl1.mbn: data
sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
SS_DL.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS
Windows
system.img.ext4: data
tarfile.tar: POSIX tar archive (GNU)
tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
zImage: Linux kernel ARM boot executable zImage (little-
endian)
file ~/originalstock/originaltarfile/*
/aboot.mbn: Hitachi SH big-endian COFF object, not stripped
/boot.img: data
/cache.img.ext4: data
/modem.bin: x86 boot sector
/N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive
/NON-HLOS.bin: x86 boot sector
/recovery.img: data
/rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
/sbl1.mbn: data
/sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
/system.img.ext4: data
/tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
( Note: Here tarfile.tar is the file I made, and I am comparing it with the original tar file that came with the stock rom, which is called N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5.) There are two things that concern me with the above output as I am comparing tarfile.tar in /experimentalstock directory with N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 file in the originalstock/originaltarfile dirctory. 1- tarfile.tar is smaller. I added more modules to the source. But that may be explained by the source I started from. I did compare the boot.img files, and the one I created by adding my zImage to it is larger than the one that came with stock rom. I started from the Samsung source code which may not contain the telecom provider's files. 2- My other concern is the output associated with the file command; for tar.file I get: POSIX tar archive (GNU) and for N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 I get POSIX tar archive. Is there a difference between the GNU version vs. whatever is the default format?
My other question is how can see what is going on during the boot when I push my image to the phone? Is there some way I can save the logs on a phone that is unrooted?
According to one of the online sources I used to get this far, I also need to or may include kernel modules. As far as I remember these files have a km extension? I did a search in my Kernel's directory, and do not see any files with this extension:
user@ubuntu:~$ locate -r '^/home/user/androidkernel3/.*.km$'
/home/user/androidkernel3/arch/arm/mvp/commkm
/home/user/androidkernel3/arch/arm/mvp/mvpkm
/home/user/androidkernel3/arch/arm/mvp/oektestkm
/home/user/androidkernel3/arch/arm/mvp/pvtcpkm
user@ubuntu:~$
Sean
android android-source asked Nov 2 '14 at 20:03
user3326293user3326293
402728
I want to create an image for the Arm chip and deploy it on my Samsung Note 3. I have a compiled copy of
the Samsung source. I added another module to this copy for added functionality. I then downloaded a copy
of the stock firmware, which I have used a number of times to flash my phone. I took the boot.img file of
the stock firmware split it open with a tool online, and replaced the zImage with the zImage that I got
from compiling my source. After several attempts, I seem to be able to create a complete tar.md5 file of
everything in the directory of modified stock source. When I flash the phone with this file using Odin,
the file goes in fine, but the phone is stuck in download mode. I am trying to figure out the main cause
of phone going into download mode, and is the root cause one of packing the files incorrectly or did I not
include a file that is required? Here is what I did to create the tar file with md5 authentication:
I created the tar file:
tar -H ustar -c aboot.mbn sbl1.mbn rpm.mbn tz.mbn sdi.mbn NON-HLOS.bin boot.img recovery.img
system.img.ext4 cache.img.ext4 modem.bin > tarfile.tar
cp tarfile.tar tarfile.tar.md5
md5sum tarfile.tar >> tarfile.tar.md5
I then tried to do a sanity check by comparing the file with a tar archive in an image I have used to
flash my phone with using the file command, and here is what I get ( note: I put my results in the
/expermental directory and the unpacked validated tar file in /originalstck/originaltarfile directory ) (
Note also that the file called tarfile below is the result of packing my files vs.
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 is what was in the validated stock rom ) :
@ubuntu:~/expermental_stock$ file *
aboot.mbn: Hitachi SH big-endian COFF object, not stripped
boot.img: data
cache.img.ext4: data
info: ASCII text
initramfs.cpio.gz: gzip compressed data, from Unix
modem.bin: x86 boot sector
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive
N900PVPUCNC5_N900PSPTCNC5_SPR.zip: Zip archive data, at least v2.0 to extract
NON-HLOS.bin: x86 boot sector
recovery.img: data
rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
sbl1.mbn: data
sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
SS_DL.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS
Windows
system.img.ext4: data
tarfile.tar: POSIX tar archive (GNU)
tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
zImage: Linux kernel ARM boot executable zImage (little-
endian)
file ~/originalstock/originaltarfile/*
/aboot.mbn: Hitachi SH big-endian COFF object, not stripped
/boot.img: data
/cache.img.ext4: data
/modem.bin: x86 boot sector
/N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive
/NON-HLOS.bin: x86 boot sector
/recovery.img: data
/rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
/sbl1.mbn: data
/sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
/system.img.ext4: data
/tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1
(SYSV), statically linked, stripped
( Note: Here tarfile.tar is the file I made, and I am comparing it with the original tar file that came with the stock rom, which is called N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5.) There are two things that concern me with the above output as I am comparing tarfile.tar in /experimentalstock directory with N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 file in the originalstock/originaltarfile dirctory. 1- tarfile.tar is smaller. I added more modules to the source. But that may be explained by the source I started from. I did compare the boot.img files, and the one I created by adding my zImage to it is larger than the one that came with stock rom. I started from the Samsung source code which may not contain the telecom provider's files. 2- My other concern is the output associated with the file command; for tar.file I get: POSIX tar archive (GNU) and for N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 I get POSIX tar archive. Is there a difference between the GNU version vs. whatever is the default format?
My other question is how can see what is going on during the boot when I push my image to the phone? Is there some way I can save the logs on a phone that is unrooted?
According to one of the online sources I used to get this far, I also need to or may include kernel modules. As far as I remember these files have a km extension? I did a search in my Kernel's directory, and do not see any files with this extension:
user@ubuntu:~$ locate -r '^/home/user/androidkernel3/.*.km$'
/home/user/androidkernel3/arch/arm/mvp/commkm
/home/user/androidkernel3/arch/arm/mvp/mvpkm
/home/user/androidkernel3/arch/arm/mvp/oektestkm
/home/user/androidkernel3/arch/arm/mvp/pvtcpkm
user@ubuntu:~$
Sean
android android-source android android-source asked Nov 2 '14 at 20:03
user3326293user3326293
402728
asked Nov 2 '14 at 20:03
user3326293user3326293
402728
edited Nov 9 '14 at 20:47
user3326293
asked Nov 2 '14 at 20:03
user3326293user3326293
402728
asked Nov 2 '14 at 20:03
user3326293user3326293
402728
asked Nov 2 '14 at 20:03
user3326293user3326293
402728
402728
3
This is in fact a software development question - the poster is trying to install and run their freshly compiled program. That said program is an operating system in no way makes the question off topic.
– Chris Stratton
Nov 2 '14 at 20:17
@ChrisStratton If you were being really picky, I'd say the Android Stack Exchange could be a better place: android.stackexchange.com. However as you said, it's a software development question and belongs here, however the users of the Android Stack Exchange may be able to supply more help in this instance.
– AStopher
Nov 2 '14 at 21:22
@cybermonkey My question is more related to native development for the arm chip; not so much Android development. I did not use a single line of java. All of the above has been done with GNU make.
– user3326293
Nov 2 '14 at 21:30
@cybermonkey This would not actually be an appropriate question for the Android site; at the root, it's all about how the app is packaged for deployment.
– Andrew Barber
Nov 2 '14 at 22:15
Unless you have already unlocked the bootloader I doubt this is going to work. I would expect that the Note 3 will have a locked bootloader, which is not going to boot your custom kernel as it won't have been signed by Samsung's relevant keys. When you flash the "stock" firmware images from Samsung, they will have been appropriately signed, hence why they work and why your modified ones won't.
– Maks
Jul 8 '15 at 0:26
add a comment |
3
This is in fact a software development question - the poster is trying to install and run their freshly compiled program. That said program is an operating system in no way makes the question off topic.
– Chris Stratton
Nov 2 '14 at 20:17
@ChrisStratton If you were being really picky, I'd say the Android Stack Exchange could be a better place: android.stackexchange.com. However as you said, it's a software development question and belongs here, however the users of the Android Stack Exchange may be able to supply more help in this instance.
– AStopher
Nov 2 '14 at 21:22
@cybermonkey My question is more related to native development for the arm chip; not so much Android development. I did not use a single line of java. All of the above has been done with GNU make.
– user3326293
Nov 2 '14 at 21:30
@cybermonkey This would not actually be an appropriate question for the Android site; at the root, it's all about how the app is packaged for deployment.
– Andrew Barber
Nov 2 '14 at 22:15
Unless you have already unlocked the bootloader I doubt this is going to work. I would expect that the Note 3 will have a locked bootloader, which is not going to boot your custom kernel as it won't have been signed by Samsung's relevant keys. When you flash the "stock" firmware images from Samsung, they will have been appropriately signed, hence why they work and why your modified ones won't.
– Maks
Jul 8 '15 at 0:26
3
3
This is in fact a software development question - the poster is trying to install and run their freshly compiled program. That said program is an operating system in no way makes the question off topic.
– Chris Stratton
Nov 2 '14 at 20:17
This is in fact a software development question - the poster is trying to install and run their freshly compiled program. That said program is an operating system in no way makes the question off topic.
– Chris Stratton
Nov 2 '14 at 20:17
@ChrisStratton If you were being really picky, I'd say the Android Stack Exchange could be a better place: android.stackexchange.com. However as you said, it's a software development question and belongs here, however the users of the Android Stack Exchange may be able to supply more help in this instance.
– AStopher
Nov 2 '14 at 21:22
@ChrisStratton If you were being really picky, I'd say the Android Stack Exchange could be a better place: android.stackexchange.com. However as you said, it's a software development question and belongs here, however the users of the Android Stack Exchange may be able to supply more help in this instance.
– AStopher
Nov 2 '14 at 21:22
@cybermonkey My question is more related to native development for the arm chip; not so much Android development. I did not use a single line of java. All of the above has been done with GNU make.
– user3326293
Nov 2 '14 at 21:30
@cybermonkey My question is more related to native development for the arm chip; not so much Android development. I did not use a single line of java. All of the above has been done with GNU make.
– user3326293
Nov 2 '14 at 21:30
@cybermonkey This would not actually be an appropriate question for the Android site; at the root, it's all about how the app is packaged for deployment.
– Andrew Barber
Nov 2 '14 at 22:15
@cybermonkey This would not actually be an appropriate question for the Android site; at the root, it's all about how the app is packaged for deployment.
– Andrew Barber
Nov 2 '14 at 22:15
Unless you have already unlocked the bootloader I doubt this is going to work. I would expect that the Note 3 will have a locked bootloader, which is not going to boot your custom kernel as it won't have been signed by Samsung's relevant keys. When you flash the "stock" firmware images from Samsung, they will have been appropriately signed, hence why they work and why your modified ones won't.
– Maks
Jul 8 '15 at 0:26
Unless you have already unlocked the bootloader I doubt this is going to work. I would expect that the Note 3 will have a locked bootloader, which is not going to boot your custom kernel as it won't have been signed by Samsung's relevant keys. When you flash the "stock" firmware images from Samsung, they will have been appropriately signed, hence why they work and why your modified ones won't.
– Maks
Jul 8 '15 at 0:26
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f26703750%2fhow-do-i-prepare-a-file-to-flash-my-phone-with%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f26703750%2fhow-do-i-prepare-a-file-to-flash-my-phone-with%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
This is in fact a software development question - the poster is trying to install and run their freshly compiled program. That said program is an operating system in no way makes the question off topic.
– Chris Stratton
Nov 2 '14 at 20:17
@ChrisStratton If you were being really picky, I'd say the Android Stack Exchange could be a better place: android.stackexchange.com. However as you said, it's a software development question and belongs here, however the users of the Android Stack Exchange may be able to supply more help in this instance.
– AStopher
Nov 2 '14 at 21:22
@cybermonkey My question is more related to native development for the arm chip; not so much Android development. I did not use a single line of java. All of the above has been done with GNU make.
– user3326293
Nov 2 '14 at 21:30
@cybermonkey This would not actually be an appropriate question for the Android site; at the root, it's all about how the app is packaged for deployment.
– Andrew Barber
Nov 2 '14 at 22:15
Unless you have already unlocked the bootloader I doubt this is going to work. I would expect that the Note 3 will have a locked bootloader, which is not going to boot your custom kernel as it won't have been signed by Samsung's relevant keys. When you flash the "stock" firmware images from Samsung, they will have been appropriately signed, hence why they work and why your modified ones won't.
– Maks
Jul 8 '15 at 0:26