I downloaded AT&T Radio codes from a link that was given on XDA. I tried to install the file using TWRP but it failed to flash. I can't find the website anymore.
I copied the winzip file to the external sd card on my Galaxy Note SGH-I717, then tried flashing the file with TWRP. As I stated earlier, the flash failed. Usually I can flash, or install roms very easily with this software.
There is a mdm.bin file and a amss.bin file. Should I try installing the mdm.bin file? There were no instructions for flashing/installing these files. Also, the files were meant for Odin. Should that make a difference?
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
So i downloaded Giefroot a couple times, from here and another source. winzip says its corrupt and i need to redownload. Winrar opens the file so i see the contents but when i try to extract, it says files are corrupt.. halp
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.