i made this small tool to Edit boot images on windows without Linux and cygwin.
i was carefull writing but even if there is any errors.. plz report bugs.
details is given in readme.
i searched over and over on google to find tool that works on windows but couldnt find any
finaly i decided to write my own.. and here is the tool.
New version available (1 aug 2014)
abimE v1.1R2
Hey first of all, nice tool. It seems to extract and recreate the boot.img file correctly although I haven't actually tested it yet.
However, I am getting some strange behavior with the header editor in Windows 7.
First, when selecting the attached image file to extract, I immediately get the error, "HeaderEditorERROR: File does not exists" in the log. This does not prevent me from extracting the image.
Then when attempting to edit the header info file extracted from this image I either get nothing or an overflow error which causes the application to crash.
ok buddy im looking for this
Sent from my Titanium S5 using XDA Free mobile app
temporarily.. you can solve this by deleting boot.img_out folder that you last time extracted..
header not found error:: this app automatically try to load last extracted bootimginfo file.. if it not exists.. it show this error.. its not to worry about.
Sent from my Titanium S5 using XDA Free mobile app
What can be the use of it? can you give more details?
nwalk7800 said:
Hey first of all, nice tool. It seems to extract and recreate the boot.img file correctly although I haven't actually tested it yet.
However, I am getting some strange behavior with the header editor in Windows 7.
First, when selecting the attached image file to extract, I immediately get the error, "HeaderEditorERROR: File does not exists" in the log. This does not prevent me from extracting the image.
Then when attempting to edit the header info file extracted from this image I either get nothing or an overflow error which causes the application to crash.
Click to expand...
Click to collapse
new version (abimE v1.1R2)available.. your reported bug is solved..
also have a look readme.txt inside the zip.
-- m9j_cfALt
net8 said:
What can be the use of it? can you give more details?
Click to expand...
Click to collapse
its used to edit boot.img and recovery.img
you may use it for theming purpose.
or making upgrading ROM
-- m9j_cfALt
m9j_cfALt said:
new version (abimE v1.1R2)available.. your reported bug is solved..
also have a look readme.txt inside the zip.
-- m9j_cfALt
Click to expand...
Click to collapse
Excellent, thank you for the fix. It is working without errors now.
I flashed the image to my device after changing a file and it worked perfectly. Thank you for the easy to use tool
Does not work. Getting a comdlg32.osx missing error.. Tried installing it to system32 from the net, but still does not work.. Did i spot that you used VB6 for this ? Why use something so old
error
Da9L said:
Does not work. Getting a comdlg32.osx missing error.. Tried installing it to system32 from the net, but still does not work.. Did i spot that you used VB6 for this ? Why use something so old
Click to expand...
Click to collapse
I get the same error. (Getting a comdlg32.osx missing error.) I am running Windows 8.1
Just download comdlg32.osx and stick it in the same folder.
Download Arquive OCX
Da9L said:
Does not work. Getting a comdlg32.osx missing error.. Tried installing it to system32 from the net, but still does not work.. Did i spot that you used VB6 for this ? Why use something so old
Click to expand...
Click to collapse
Download file >
View attachment COMCTL32.rar
Download File OCX
Da9L said:
Does not work. Getting a comdlg32.osx missing error.. Tried installing it to system32 from the net, but still does not work.. Did i spot that you used VB6 for this ? Why use something so old
Click to expand...
Click to collapse
Download File OCX
View attachment COMCTL32.rar
Download File OCX
iaTa said:
Just download comdlg32.osx and stick it in the same folder.
Click to expand...
Click to collapse
Download File OCX
View attachment COMCTL32.rar
Download File OCX
iaTa said:
Just download comdlg32.osx and stick it in the same folder.
Click to expand...
Click to collapse
Download File OCX
View attachment COMCTL32.rar
Interesting tool .... it won't unpack a Nexus 9 boot.img, though ...
Says not a valid Android boot img ...
do you still maintain this tool? cause i have successfully pack n repack but when i flash the packed boot.img the device boot into fastboot instead of system
Dont work with Wiko Pulp 3G Boot.img or recovery.img
Error Message:
MGError:byte 1Not a New ASCII Format CPIO directory Header
ERROR: Unpacking Failed!!
It will unpack s6 plus 7.0 boot.img but after repack if you try to flash it will not allow secure check fail boot
Related
This tool is an interactive console application. It makes it easier to use blob tools. All you have to do is run it, choose to unpack or repack. If you choose repack it will ask you to enter the name for each of the required files. After that it will due the rest.
Notice: You either have to enter the full, have the blob file in the same directory/folder or have change changed directories to the location of the blob. For example: cd /path/to/blob's Dir/
Update: I have fixed the case sensitivity issue.
Note: The attachments below will always be the latest.
ostar2 said:
I created an application to make BlobTools easier to use. It is an interactive console application. I made this because I wanted to be of some help to the community. Well anyways, here it is...
Click to expand...
Click to collapse
Files are corrupt. Try again please.
Regards,
Brad
bradslinux said:
Files are corrupt. Try again please.
Regards,
Brad
Click to expand...
Click to collapse
Those were compressed with the LZMA algorithm. Here try these ones there compressed with the normal zip compression for windows.
Edit: To prevent confusion I have removed these attachments please download from The Original Post. Thanks.
ostar2 said:
Those were compressed with the LZMA algorithm. Here try these ones there compressed with the normal zip compression for windows.
Click to expand...
Click to collapse
That did it, thanks.
Nice work.
Regards,
Brad
welcome..
Excellent! Thank you - these will aid me greatly!
I like to be of help to the community so I am happy that this helps others.
Sourcecode and Update
As I am unable to compile for Linux or mac at the moment here is the sourcecode for this tool.
This uses a Code::Blocks IDE for its project/workspace. It can be compiled with just a c++ compiler. The icon is only available on windows as I do not know to implement it on macosx and Linux does not support icons in executables. also, I have updated this application as well the updated binarie zip files and source zip are attached. Enjoy!
Edit: To prevent confusion I have removed these attachments please download from The Original Post. Thanks.
ostar2 said:
As I am unable to compile for Linux or mac at the moment here is the sourcecode for this tool.
This uses a Code::Blocks IDE for its project/workspace. It can be compiled with just a c++ compiler. The icon is only available on windows as I do not know to implement it on macosx and Linux does not support icons in executables. also, I have updated this application as well the updated binarie zip files and source zip are attached. Enjoy!
Click to expand...
Click to collapse
I tried to unpack a blob and it kept failing with an Invalid Option! error. I hit u then typed blob which was in the same directory. I then manually dragged the blob onto the blobunpack.exe and it unpacked it fine.
Any ideas why?
sbdags said:
I tried to unpack a blob and it kept failing with an Invalid Option! error. I hit u then typed blob which was in the same directory. I then manually dragged the blob onto the blobunpack.exe and it unpacked it fine.
Any ideas why?
Click to expand...
Click to collapse
I was unsure of what extenstion the blob file had when I created this. What extenstion do they have? is it .blob? If so I think i can fix it.
Update: Fixed Not unpacking
Hello again I fixed the tool it should work fine now.
Edit: To prevent confusion I have removed these attachments please download from The Original Post. Thanks.
ostar2 said:
I was unsure of what extenstion the blob file had when I created this. What extenstion do they have? is it .blob? If so I think i can fix it.
Click to expand...
Click to collapse
The blobs usually have no extension at all, and the extracted parts have a dot and the partition name as their last part, but I would not call these "extensions" (even if Windows disagrees with me).
_that said:
The blobs usually have no extension at all, and the extracted parts have a dot and the partition name as their last part, but I would not call these "extensions" (even if Windows disagrees with me).
Click to expand...
Click to collapse
Thanks, that makes more sense. Also, I am thinking about having BlobTools print the command usage in more detail or at least a "--help" command displaying detailed usage of BlobTools. Like, how to unpack and repack.
[WIP] New tool
I am going to make gui version of this using wxwidgets and also maby consolidate the two tools into one and then combine it with GUI. That would make it much better.
still getting the "invalid option" message :/
arminneman said:
still getting the "invalid option" message :/
Click to expand...
Click to collapse
Please re-download from the original post. It should work fine. If not let me know.
Ok, its updated let me know if any problems occur.
ostar2 said:
Ok, its updated let me know if any problems occur.
Click to expand...
Click to collapse
I try it on win 7 64bit, run as administrator BlobToolUI select u and blob the name of file and give this error:
Unable to open "b"
Can You help me?
Thanks
Riccardo.
cipolippo said:
I try it on win 7 64bit, run as administrator BlobToolUI select u and blob the name of file and give this error:
Unable to open "b"
Can You help me?
Thanks
Riccardo.
Click to expand...
Click to collapse
Is the blob you want to unpack in the same directory? If that does not work try adding a "." the end of the file name.
ostar2 said:
Is the blob you want to unpack in the same directory? If that does not work try adding a "." the end of the file name.
Click to expand...
Click to collapse
Yes is in the same directory, adding a "." the end of the file does not work..
work if I rename file "blob" in also "b" ?
Thanks.
Hello I am trying to flash the factory image on to my Nexus 5 with the flash all option in the zip file and it keep going missing boot.img as seen in the picture and I am unsure what to do at this point cause I disconnect my phone and it does boot up in to android 4.4.4 but I need help here
hell I would let some one remote connect if that helps any lol
Buckii said:
Hello I am trying to flash the factory image on to my Nexus 5 with the flash all option in the zip file and it keep going missing boot.img as seen in the picture and I am unsure what to do at this point cause I disconnect my phone and it does boot up in to android 4.4.4 but I need help here
hell I would let some one remote connect if that helps any lol
Click to expand...
Click to collapse
1) "Stuck" is NOT a question. Please use descriptive thread titles
2) You haven't unzipped the image-hammerheadxxx.zip that contains the images :/
but I have I followed the instructions to a T and put all file in the folder under platform tools
Buckii said:
but I have I followed the instructions to a T and put all file in the folder under platform tools
Click to expand...
Click to collapse
Not sure what instructions you've followed. Either they're incomplete or you made a mistake. Like I said, your screenshot shows a zip file. You need to unzip that in the location that it is in now
picture
rootSU said:
Not sure what instructions you've followed. Either they're incomplete or you made a mistake. Like I said, your screenshot shows a zip file. You need to unzip that in the location that it is in now
Click to expand...
Click to collapse
This is now what I have done you were right but still missing boot.img
Buckii said:
This is now what I have done you were right but still missing boot.img
Click to expand...
Click to collapse
Just fastboot flash it then.
Link to guides in my signature.
I have similar issues. Mine complains that the archive doesn't contain boot.sig and recovery.sig, and then it fails to allocate space and the update package missing system.img.
Going to do it manually now to see if it works
Desca said:
I have similar issues. Mine complains that the archive doesn't contain boot.sig and recovery.sig, and then it fails to allocate space and the update package missing system.img.
Going to do it manually now to see if it works
Click to expand...
Click to collapse
Mine shows same as you, but just reboot and it is working
Hi!
I'd like to know where the OTAs are stored in our M2. Anyone that hasn't done yet the update download, and that has Root permissions, can use this app to find where they're stored, and if possible, upload it and post a link to it.
Thank you!
Do you still needed the file, sir ?
FunSucker said:
Do you still needed the file, sir ?
Click to expand...
Click to collapse
Yep. It's for some research
I think, the app didn't work sir. After I wait 30 minutes, none of the files were copied to my storage. Then I try searching using manual method, I found one file, the file size is as large as my OTA update. The nama file is "update-package".
The file extension is not ".zip", in the folder recovery (internal storage). My estimate, the file extension .LZMA or .tar.LZMA or .zipx.
I've tried to extract and decompress in the PC (windows os) using some programs, but failed.
If you still need the file, I'll upload it now .
FunSucker said:
I think, the app didn't work sir. After I wait 30 minutes, none of the files were copied to my storage. Then I try searching using manual method, I found one file, the file size is as large as my OTA update. The nama file is "update-package".
The file extension is not ".zip", in the folder recovery (internal storage). My estimate, the file extension .LZMA or .tar.LZMA or .zipx.
I've tried to extract and decompress in the PC (windows os) using some programs, but failed.
If you still need the file, I'll upload it now .
Click to expand...
Click to collapse
Yes please! Thanks
oke, sir. when finished i will share the link.
Oke sir, check this out --> Google Drive
FunSucker said:
Oke sir, check this out --> Google Drive
Click to expand...
Click to collapse
Great, thank you very much!
Okay, so this is what I got:
The update zip refuses to be flashed in UBL devices. FOTAkernel system is broken after you open the bootloader, which leads us with an unused partition (but that's other thing). The recovery logs just say: WARN: Status Rooted, ERR: Bootloader is unlocked.
I've tried to force it using AOSP Recovery commands
Code:
echo 'boot-recovery' > /cache/recovery/command
echo '--update_package=/sdcard/update.zip' >> /cache/recovery/command
reboot recovery
But just got a big nope.
So, now time to have a look at it. I tried to unpack it several times but no luck. The reason seems to be, very probably, because this is a LZMA compressed file (as 7-Zip reported) but with 2 additions at the end (which corrupts the entire read of it): An unencrypted/uncompressed XML which points out which is the software available right now in the phone (<source>), and which is the version that is going to be installed (<target>), plus, some a weird <generation> section. This is the XML
Code:
<?xml version='1.0' encoding='ISO-8859-1'?>
<metadata version="3.3">
<product>
<manufacturer>Sony</manufacturer>
<model>D2302</model>
<hwplatform>msm8226</hwplatform>
</product>
<update>
<generation>
<version>1.1.2</version>
<date>2015-12-28T12:10:19Z</date>
<rb_version>7.0.15.117</rb_version>
<rb_ua_version>7.0.15.117</rb_ua_version>
</generation>
<source>
<software>
<revision>18.6.A.0.175</revision>
</software>
<customization>
<variant>1281-0464</variant>
<revision>R2C</revision>
</customization>
</source>
<target>
<software>
<revision>18.6.A.0.182</revision>
</software>
<customization>
<variant>1281-0464</variant>
<revision>R2C</revision>
</customization>
</target>
</update>
</metadata>
And, right after that, I can perfectly see a SIN header, so I isolated it and, looks quite similar to the FOTAkernel.sin included in FTFs (330613072905Z010U S1_FOTA0 ‚"0), I personally guess it's a very, very small ELF binary, by the size of it.
So, the problem now comes to isolate the 3 parts, the LZMA file, the XML and the SIN, separetly. After that, I think we can probably have a look insde them.
How about linux os? Can we unpack or decompress that file on linux os, sir? Do you have tried?
FunSucker said:
How about linux os? Can we unpack or decompress that file on linux os, sir? Do you have tried?
Click to expand...
Click to collapse
I've tried many tools and combinations (ext4, .img, etc) and none of them worked... I'll think more about it.
This is a thread on how to unpack and repack the system.img.dat file of your Android Rom,to see its content.
Starting from Android 5.x (Lollipop) Custom roms are not compressed like on previous android versions. Earlier all Files were inside the /system folder.And we were able to see all the system files
The problem started in >=5.0 versions because rom size increased and it was necessary to highly compress them again.
You Must Have Following Files Installed in your PC
1. Java SDK = Click here to download java
2. Python 2.xxx= Click here to download Python
How to decompress /Repack these files? Its Sipmle !!
Follow the Instructions Below To do that.
Download the Android Unpack Repack adithyan25.rar from here
Or you can download it from attachments
Run The File And Follow The Instructions As on screen. :good:
Video Tutorial
Special Thanks @xpirt
If you are a good Programmer You Can follow his method .View His Method here
If you Have any doubts or Enquired post in the Comment section
I got an error while repacking the system.img
"Input-IMG\file_contexts: No such file or directory"
Please help.
AmeyRanberg said:
I got an error while repacking the system.img
"Input-IMG\file_contexts: No such file or directory"
Please help.
Click to expand...
Click to collapse
did you copy the files to the creard folder!??... watch the video
adithyan25 said:
did you copy the files to the creard folder!??... watch the video
Click to expand...
Click to collapse
The rom that I had, only had system.img boot.img and those older folders. It didnt have file_contexts. But later I extracted it from boot.img and it worked thanks anyway.
AmeyRanberg said:
The rom that I had, only had system.img boot.img and those older folders. It didnt have file_contexts. But later I extracted it from boot.img and it worked thanks anyway.
Click to expand...
Click to collapse
Great And thank u for trying my app
I falied system.img repacked
Hi~
I wateched your video.
So I succeed system.img unpacked.
But, I tried system.img repack. I failed.
Why failed? T.T
Start Repacking in system.img......
please wait......
Input-IMG\file_contexts: No such file or directory
critical error: main: failed to open input image : No such file or directory
did u copy fule_contexta
Similar to my friends.
http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
same the tool I make http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Kritsada Chaitan said:
same the tool I make http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Click to expand...
Click to collapse
yeah tanks for the info... i made this tool using xpirt post and a screen shot of a software that i saw in google... any way great wrks... i made this through java..
AmeyRanberg said:
The rom that I had, only had system.img boot.img and those older folders. It didnt have file_contexts. But later I extracted it from boot.img and it worked thanks anyway.
Click to expand...
Click to collapse
deleted
adithyan25 said:
did u copy fule_contexta
Click to expand...
Click to collapse
what is file_contexta?
I dont understand..
same here. failed while repack
critical error: main: failed to open input image: No such file or directory
its a file along with the rom that you get.. just watch the video
Sent from my ASUS_Z00A using XDA-Developers mobile app
Problem/
No file " system transfer list". Where to get it? Firmware is given under SPFT.
hi @adithyan25
I'm so interested with this topic.
I tried but still stuck on file_context
please also make written tutorial on this thread.
kevin mitnick said:
hi @adithyan25
I'm so interested with this topic.
I tried but still stuck on file_context
please also make written tutorial on this thread.
Click to expand...
Click to collapse
didnt you watch the video??? i think it had all the component you nedd.. still any prblm cmnt below
Sent from my ASUS_Z00A using XDA-Developers mobile app
adithyan25 said:
didnt you watch the video??? i think it had all the component you nedd.. still any prblm cmnt below
Sent from my ASUS_Z00A using XDA-Developers mobile app
Click to expand...
Click to collapse
i did.
but on video, tutorial about dat file..
Still unable to repack the dat.
Windows says rimg2sdat is not a valid Win32 application.
It works under Windows 7 at work but not under Windows XP Pro like I have at home.
Someone got another version? Is there a XP compatible version of rimg2sdat?
Thanks
Kritsada Chaitan said:
same the tool I make http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Click to expand...
Click to collapse
Thanks to the original work-works correctly!
Working perfectly with Android 6.0.1, Thanks Dev !!
As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?
xdausernl said:
As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?
Click to expand...
Click to collapse
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk
Droidriven said:
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.
xdausernl said:
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.
Click to expand...
Click to collapse
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk
xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
Droidriven said:
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.
xdausernl said:
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.
Click to expand...
Click to collapse
Meanwhile I think I found a possible cause for failure using Heimdall-Frontend.
Heimdall-Frontend uses only extracted content of a stock ROM, in my case that's 10 files.
Although the download of the 'system.img' file completed successfully and Heimdall-Frontend releases the connected device, there's still a slightly different behaviour at reboot of Tab3.
Because after the release of the connected device, Tab3 then immediately goes into reboot.
That's not the case with all other downloaded files.
After releasing the connected device, it then takes a few second until the Tab3 goes into reboot.
So my guess is that at immediate reboot the downloaded 'system.img' file will then be deleted from the Tab3.
That would explain why after reboot nothing has really being changed.