[FLASHER][LINUX] Heimdall Flasher SGSIII/SGNII

KEYofR

Senior Member
Jun 14, 2010
594
220
0
What can I do to help add support for the Sprint note2 SPH-L900?

I'm already all rooted and twrp with odin, I just don't like that I had to use odin and I'd like a better way to recover from future soft bricks.

I have compiled heimdall but have not yet figured out how to take existing rom, firmware, and recovery images and turn them into heimdall packages.

Sent from my SPH-L900 using xda premium
 

A.S._id

Inactive Recognized Developer
Sep 21, 2010
1,211
2,574
153
What can I do to help add support for the Sprint note2 SPH-L900?

I'm already all rooted and twrp with odin, I just don't like that I had to use odin and I'd like a better way to recover from future soft bricks.

I have compiled heimdall but have not yet figured out how to take existing rom, firmware, and recovery images and turn them into heimdall packages.

Sent from my SPH-L900 using xda premium
And, what are your question? Are you want make auto executable package, or what?
If you want simply flash all parts of your rom, then get pit file from your device and upload here, I'll look this...
 
Last edited:

KEYofR

Senior Member
Jun 14, 2010
594
220
0
And, what are your question? Are you want make auto executable package, or what?
If you want simply flash all parts of your rom, then get pit file from your device and upload here, I'll look this...
I'd like to be able to flash bootloader and twrp (or other recovery) from download mode (ie soft bricked or not-yet-rooted) without requiring Windows or ODIN. I don't really need it to be bundled into an auto executable but this IS really cool that you've done this. I landed here because I was just searching for anything where anyone used heimdall to flash anything to a note 2 at all. There is almost no examples for note 2, just other devices.

What's a pit file?

The twrp recovery file is just a tar with a recovery.img file in it. I've flashed replacement roms and firmwares and none of the files said pit. Is it one of the components in a flashable zip? Should I unpack a rom .zip to find it?

I figured that since you had this working for other versions of note 2, then this is the closest/best starting place to figure out how to do it for the Sprint version.

I'll try to find a pit file.

Thanks!

Sent from my SPH-L900 using xda premium
 

A.S._id

Inactive Recognized Developer
Sep 21, 2010
1,211
2,574
153
I'd like to be able to flash bootloader and twrp (or other recovery) from download mode (ie soft bricked or not-yet-rooted) without requiring Windows or ODIN. I don't really need it to be bundled into an auto executable but this IS really cool that you've done this. I landed here because I was just searching for anything where anyone used heimdall to flash anything to a note 2 at all. There is almost no examples for note 2, just other devices.

What's a pit file?

The twrp recovery file is just a tar with a recovery.img file in it. I've flashed replacement roms and firmwares and none of the files said pit. Is it one of the components in a flashable zip? Should I unpack a rom .zip to find it?

I figured that since you had this working for other versions of note 2, then this is the closest/best starting place to figure out how to do it for the Sprint version.

I'll try to find a pit file.

Thanks!

Sent from my SPH-L900 using xda premium
ok man.
1. root needs only for old bootloaders, before version LLA, past it version will flash without problem.
2. for get pit file, you must to turn download mode, connect to pc, enter into terminal heimdall flasher, choose item "download pit", choose name of pit file and push "enter". after this you found got pit in folder of flasher...
Your pit needs for add into item "FULL" parts carrier.img, tombstone.img
3. so you can flash any recovery, choose item "recovery", don't need root
4. heimdall can't flash archives tar or zip, so you must before flashing extract all parts into folder "FLASH"
 
Last edited:
  • Like
Reactions: KEYofR

KEYofR

Senior Member
Jun 14, 2010
594
220
0
Last week I flashed a zip that was supposed to bring me back to 100% stock so as to be able to apply the latest ota, the re-root after.

That all worked fine but now twrp says can not mount or can not find /preload , so I don't 100% trust my partition layout right now. My phone seems to be working in all ways except for that message, but it still means I don't think my phone is a good reference right now.

Sent from my SPH-L900 using xda premium
 

A.S._id

Inactive Recognized Developer
Sep 21, 2010
1,211
2,574
153
Last week I flashed a zip that was supposed to bring me back to 100% stock so as to be able to apply the latest ota, the re-root after.

That all worked fine but now twrp says can not mount or can not find /preload , so I don't 100% trust my partition layout right now. My phone seems to be working in all ways except for that message, but it still means I don't think my phone is a good reference right now.

Sent from my SPH-L900 using xda premium
I think you don't understand some things...
Your phone is good reference for pit download, in any status, if can reboot to download mode...
So do not have to think, you just download a pit file...
That's all...
 

KEYofR

Senior Member
Jun 14, 2010
594
220
0
I think you don't understand some things...
Your phone is good reference for pit download, in any status, if can reboot to download mode...
So do not have to think, you just download a pit file...
That's all...
Oh ok. In that case I should see shortly. Thanks!

Sent from my SPH-L900 using xda premium
 

TheEyes

Senior Member
Aug 20, 2011
135
17
0
Yikes! "Configure tools" is giving me a bunch of compiler errors:

Code:
 install qt
Reading package lists... Done
Building dependency tree       
Reading state information... Done
libqt4-dev is already the newest version.
libqt4-gui is already the newest version.
qt4-dev-tools is already the newest version.
libqt4-core is already the newest version.
The following packages were automatically installed and are no longer required:
  linux-headers-3.2.0-26-generic linux-headers-3.2.0-26
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
 install zlib
Checking for gcc...
Checking for shared library support...
Building shared library libz.so.1.2.7 with gcc.
Checking for off64_t... Yes.
Checking for fseeko... Yes.
Checking for strerror... Yes.
Checking for unistd.h... Yes.
Checking for stdarg.h... Yes.
Checking whether to use vs[n]printf() or s[n]printf()... using vs[n]printf().
Checking for vsnprintf() in stdio.h... Yes.
Checking for return value of vsnprintf()... Yes.
Checking for attribute(visibility) support... Yes.
Looking for a four-byte integer type... Found.
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -I. -c -o example.o test/example.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o adler32.o adler32.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o crc32.o crc32.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o deflate.o deflate.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o infback.o infback.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o inffast.o inffast.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o inflate.o inflate.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o inftrees.o inftrees.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o trees.o trees.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o zutil.o zutil.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o compress.o compress.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o uncompr.o uncompr.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o gzclose.o gzclose.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o gzlib.o gzlib.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o gzread.o gzread.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN   -c -o gzwrite.o gzwrite.c
ar rc libz.a adler32.o crc32.o deflate.o infback.o inffast.o inflate.o inftrees.o trees.o zutil.o compress.o uncompr.o gzclose.o gzlib.o gzread.o gzwrite.o 
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -o example example.o -L. libz.a
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -I. -c -o minigzip.o test/minigzip.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -o minigzip minigzip.o -L. libz.a
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/adler32.o adler32.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/crc32.o crc32.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/deflate.o deflate.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/infback.o infback.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/inffast.o inffast.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/inflate.o inflate.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/inftrees.o inftrees.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/trees.o trees.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/zutil.o zutil.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/compress.o compress.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/uncompr.o uncompr.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/gzclose.o gzclose.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/gzlib.o gzlib.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/gzread.o gzread.c
gcc -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DPIC -c -o objs/gzwrite.o gzwrite.c
gcc -shared -Wl,-soname,libz.so.1,--version-script,zlib.map -O3  -fPIC -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -o libz.so.1.2.7 adler32.lo crc32.lo deflate.lo infback.lo inffast.lo inflate.lo inftrees.lo trees.lo zutil.lo compress.lo uncompr.lo gzclose.lo gzlib.lo gzread.lo gzwrite.lo  -lc 
rm -f libz.so libz.so.1
ln -s libz.so.1.2.7 libz.so
ln -s libz.so.1.2.7 libz.so.1
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -o examplesh example.o -L. libz.so.1.2.7
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -o minigzipsh minigzip.o -L. libz.so.1.2.7
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -I. -D_FILE_OFFSET_BITS=64 -c -o example64.o test/example.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -o example64 example64.o -L. libz.a
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -I. -D_FILE_OFFSET_BITS=64 -c -o minigzip64.o test/minigzip.c
gcc -O3  -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -o minigzip64 minigzip64.o -L. libz.a
cp libz.a /usr/local/lib
chmod 644 /usr/local/lib/libz.a
cp libz.so.1.2.7 /usr/local/lib
chmod 755 /usr/local/lib/libz.so.1.2.7
cp zlib.3 /usr/local/share/man/man3
chmod 644 /usr/local/share/man/man3/zlib.3
cp zlib.pc /usr/local/lib/pkgconfig
chmod 644 /usr/local/lib/pkgconfig/zlib.pc
cp zlib.h zconf.h /usr/local/include
chmod 644 /usr/local/include/zlib.h /usr/local/include/zconf.h
 install libusb
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
configure: WARNING: Libtool does not cope well with whitespace in `pwd`
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for windres... no
checking for inline... inline
checking whether gcc and cc understand -c and -o together... yes
checking operating system... Linux
checking for clock_gettime in -lrt... yes
checking poll.h usability... yes
checking poll.h presence... yes
checking for poll.h... yes
checking sys/timerfd.h usability... yes
checking sys/timerfd.h presence... yes
checking for sys/timerfd.h... yes
checking whether TFD_NONBLOCK is declared... yes
checking whether to use timerfd for timing... yes
checking for struct timespec... yes
checking for sigaction... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for gettimeofday... yes
configure: creating ./config.status
config.status: creating libusb-1.0.pc
config.status: creating Makefile
config.status: creating libusb/Makefile
config.status: creating examples/Makefile
config.status: creating doc/Makefile
config.status: creating doc/doxygen.cfg
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
Making install in libusb
make[1]: Entering directory `/home/aaron/sensation/note 2/heimdall_flasher_v.0.0.5/tools/libusb-1.0.9/libusb'
  CC     libusb_1_0_la-core.lo
  CC     libusb_1_0_la-descriptor.lo
  CC     libusb_1_0_la-io.lo
  CC     libusb_1_0_la-sync.lo
  CC     libusb_1_0_la-linux_usbfs.lo
  CC     libusb_1_0_la-threads_posix.lo
  CCLD   libusb-1.0.la
make[2]: Entering directory `/home/aaron/sensation/note 2/heimdall_flasher_v.0.0.5/tools/libusb-1.0.9/libusb'
test -z "/usr/local/lib" || /bin/mkdir -p "/usr/local/lib"
 /bin/bash ../libtool   --mode=install /usr/bin/install -c   libusb-1.0.la '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/libusb-1.0.so.0.1.0 /usr/local/lib/libusb-1.0.so.0.1.0
libtool: install: (cd /usr/local/lib && { ln -s -f libusb-1.0.so.0.1.0 libusb-1.0.so.0 || { rm -f libusb-1.0.so.0 && ln -s libusb-1.0.so.0.1.0 libusb-1.0.so.0; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libusb-1.0.so.0.1.0 libusb-1.0.so || { rm -f libusb-1.0.so && ln -s libusb-1.0.so.0.1.0 libusb-1.0.so; }; })
libtool: install: /usr/bin/install -c .libs/libusb-1.0.lai /usr/local/lib/libusb-1.0.la
libtool: install: /usr/bin/install -c .libs/libusb-1.0.a /usr/local/lib/libusb-1.0.a
libtool: install: chmod 644 /usr/local/lib/libusb-1.0.a
libtool: install: ranlib /usr/local/lib/libusb-1.0.a
/bin/bash: /home/aaron/sensation/note: No such file or directory
make[2]: *** [install-libLTLIBRARIES] Error 127
make[2]: Leaving directory `/home/aaron/sensation/note 2/heimdall_flasher_v.0.0.5/tools/libusb-1.0.9/libusb'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/aaron/sensation/note 2/heimdall_flasher_v.0.0.5/tools/libusb-1.0.9/libusb'
make: *** [install-recursive] Error 1
 install heimdall
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for C++ compiler default output file name... 
configure: error: in `/home/aaron/sensation/note 2/heimdall_flasher_v.0.0.5/tools/Heimdall_SOURCE/libpit':
configure: error: C++ compiler cannot create executables
See `config.log' for more details.
make: *** No targets specified and no makefile found.  Stop.
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for DEPS... configure: error: Package requirements (libusb-1.0 >= 1.0.8) were not met:

No package 'libusb-1.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables DEPS_CFLAGS
and DEPS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

make: *** No targets specified and no makefile found.  Stop.
make: *** No rule to make target `install'.  Stop.
 install heimdall-frontend
RCC: Warning: No resources in 'mainwindow.qrc'.
/usr/bin/uic-qt4 mainwindow.ui -o GeneratedFiles/ui_mainwindow.h
/usr/bin/uic-qt4 aboutform.ui -o GeneratedFiles/ui_aboutform.h
g++ -c -m64 -pipe -std=c++0x -O2 -Wall -W -D_REENTRANT -DQT_WEBKIT -DQT_LARGEFILE_SUPPORT -DQT_NO_DEBUG -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4 -IGeneratedFiles -I./GeneratedFiles/Release -I../libpit/Source -I. -IGeneratedFiles/release -IGeneratedFiles -o release/aboutform.o Source/aboutform.cpp
make: g++: Command not found
make: *** [release/aboutform.o] Error 127
g++ -c -m64 -pipe -std=c++0x -O2 -Wall -W -D_REENTRANT -DQT_WEBKIT -DQT_LARGEFILE_SUPPORT -DQT_NO_DEBUG -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml -I/usr/include/qt4 -IGeneratedFiles -I./GeneratedFiles/Release -I../libpit/Source -I. -IGeneratedFiles/release -IGeneratedFiles -o release/aboutform.o Source/aboutform.cpp
make: g++: Command not found
make: *** [release/aboutform.o] Error 127
 show version
./tools/configure_tools: line 40: heimdall: command not found
Am I doing something stupid?
 

KEYofR

Senior Member
Jun 14, 2010
594
220
0
Make: g++: command not found.

Means that make tried to run g++ but g++ isn't installed.

Sent from my SPH-L900 using xda premium
 

KEYofR

Senior Member
Jun 14, 2010
594
220
0
Oh, duh. That's what I get for doing that stuff at 4AM. Still, that should be part of the dependencies, shouldn't it?
It's a dependency for you in real world terms because you know you want to build something, but there's really no way for the computer to know that. Even installing make doesn't mean the only possible use for that is with gcc or g++. Make can be used for all sorts of things. You installed qt. That doesn't automatically imply you need g++ either. You might not be building anything, you might be building with a plain c compiler (gcc) instea of c++ (g++), or some other c/c++ besides gcc, or c# or any number of other things that aren't even c-like.

So it's pretty much up to you to resolve build-time dependencies yourself unless you're using something like src rpm's which do specify build-time dependencies, but I don't know if anything like that is available for your platform.

Sent from my SPH-L900 using xda premium
 

Uvoguine

Senior Member
Dec 18, 2011
381
63
0
In concret terms what will be the difference if I choose a standard flash or a full ?

Edit : When I try to flash (FULL and STANDARD) it returns :
Code:
Enter option: 5
 Warning Flash! Do not turn off target!!
total 1563320
-rw-r--r-- 1 user user    5695744 févr.  4 02:53 boot.img
-rw-r--r-- 1 user user  153485916 janv. 18 02:22 cache.img
-rw-r--r-- 1 user user  143053608 janv. 18 02:22 hidden.img
-rw-r--r-- 1 user user   12583168 nov.  26 08:10 modem.bin
-rw-r--r-- 1 user user    6404352 févr.  4 02:53 recovery.img
-rw-r--r-- 1 user user     887040 févr.  4 02:53 sboot.bin
-rw-rw-r-- 1 user user    1674752 févr.  4 01:51 SS_DL.dll
-rw-r--r-- 1 user user 1276873640 févr.  4 02:53 system.img
-rw-r--r-- 1 user user     159744 févr.  4 02:53 tz.img
Device detected
ERROR: "-BOOT" is not a valid argument
That's because I have Heimdall 1.3.1 installed. I almost find all good arguments for my version but I still have a problem with modem.bin. It's like the file doesn't exist but it's actually here.
Code:
sudo heimdall flash --primary-boot boot.img --recovery recovery.img --system system.img --cache cache.img --hidden hidden.img --modem modem.bin
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

Downloading device's PIT file...
PIT file download sucessful

ERROR: Partition corresponding to -modem argument could not be located
Ending session...
Rebooting device...
Re-attaching kernel driver...
 
Last edited:

A.S._id

Inactive Recognized Developer
Sep 21, 2010
1,211
2,574
153

Can someone tell me what option 1. Extract ROM does? Does this take an image of the device's storage? Or otherwise, does anyone know a way to do this on an N7100 that won't start up but can get into download mode? Thanks.
Extract flash parts from tar.md5 - heimdall can't flash from archive
 

Adriy

Member
Oct 8, 2010
20
0
0
sal

Hello, i have a E250L 32G, power only in download mode, need to be repartition. I need a pit file from the same device.
Maybe an E250L user can manage to read this pit file from a good phone, in adb mode or hemidal.

Any help will be apreciated....thanks
.
Plss i am disperate, i need badly pit file partition for SHV-E250L 32G note 2 [email protected]. thx.
.
With this software you can extract PIT a functional phone
http://forum.xda-developers.com/showthread.php?t=1308546
.
PRODUCT NAME: SHV-E250L
CUSTOM BINARY DOWNLOAD: Yes (23 counts)
SYSTEM STATUS: Custom
I gave the command delete the partitions inside the adb shell. it shows me now download mode, connect to Odin's drivers. I ask for flash pit file.
.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone