DISCLAIMER: Since this is a third-party supplied file, flashing this file places any and all outcomes on YOU, the flasher (get your mind out of the gutter, thanks.) This file, though supplied by Samsung Kies 3, may cause issues or have undesirable effects. What these effects are, I have no clue. If you have a custom recovery, it will be overwritten with the stock recovery. Again, if you use this, you are the one responsible for any negative outcome.
This the official stock ROM flashable via Odin. This took me a few hours to download several times and locate the temp directory that housed it. It is a 2.12 gig tar.md5 file. Since Samsung does not have an open source copy for us to download, I used Kies 3 to download it.
FLASHING INSTRUCTIONS:
Using the most recent Odin, put the file in the AP section and flash it.
Link
Thank you so much it fixed my bricked device!
Thank you so much - Accidentally upgraded firmware and lost root and could not re-root. Worked like a charm and used kingroot to gain root again. You rock!
It downloads as a .RAR file if converted to .TAR, ODIN can not load it. How can the .rar file be used by ODIN?
bunivers said:
It downloads as a .RAR file if converted to .TAR, ODIN can not load it. How can the .rar file be used by ODIN?
Click to expand...
Click to collapse
The flashable .Tar file that you will use to restore your device via Odin, is located inside the .RAR provided in the download link. Once the .RAR file has been unrared/unzipped using 7zip, you will have your restore .Tar file that you're referring to. If you need to, you can Google 7zip and download it. The program is free and open-source, and it supports .RAR .TAR .ZIP etc. Happy Restore!
@jaywillsoul Please add to the OP that this firmware will wipe the device.
Thanks again for the firmware!
Sent from my XT1528 using XDA Labs
I was able to un-brick my wife's Verizon Core Prime with this. Thank you for your time and effort, @jaywillsoul.
Donation sent.
Fail
I downloaded the firmware, began to flash and Odin wrote "FAIL", and the screen after turning on is "Software update failed. Your device didnt update successfully. Use the Verizon Software Repair Assistant on a computer to repare your device and complete the update." But the Verizon Software Repair Assistant after this can not find the phone.
Thank you for this wonderful gift to the underdeveloped Core Prime! :good: worked for me and I was able to root afterwards!
is that process unlock the sim card lock for Verizon
ty it work's. I can root now
Sorry to bump this thread, but will updating through recovery mode end up wiping all the data of the phone? (like pictures, and files)
I was dumb and didn't enable usb debugging before my phone got soft bricked, now it freezes on the carrier animation
My phone is a model SM-G360T1
Link999123 said:
Sorry to bump this thread, but will updating through recovery mode end up wiping all the data of the phone? (like pictures, and files)
I was dumb and didn't enable usb debugging before my phone got soft bricked, now it freezes on the carrier animation
My phone is a model SM-G360T1
Click to expand...
Click to collapse
You have the wrong model - this guide is for the G360V, not the G360T1. Sorry.
I was wondering if anyone has a solution to why I get a crc failure when trying to extract zip files. I have the at&t note 8 and I want to convert it back to stock firmware in order to root it. I'm on oreo as of now. But every (20+) downloads I have acquired all give me a crc failure when trying to extract the files from a zip folder. I never had this issue with the note 3 when I use to root it. I've heard they different browser, redownload file, etc. Nothing works!!! I still get crc failure every single time and its beginning to frustrate me!!!
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.
Hello y'all.
I got this SM-A530F/DS, a galaxy A8 (2018), from a relative that got a problem. I am not sure about specifics, but it was never tampered with or rooted, I believe that things start to go bad after an unsuccesful OTA update. The phone does not boot, it just stays on samsung logo screen indefinetly, I can put the phone on download mode though so I think this is fixable by flashing the stock rom anew.
Now I got the stock firmware from sammobile and it seems good, but it is on a format for Odin, unfortunately I dont have access to a Windows computer, just Linux. So I got heimdall and read through whatever info I could find and I think I grok the fundamentals.
TLDR:
I have the following questions about the process:
1) Inside the stock files there is a .pit file that I assume is tailored to the stock ROM being distributed, should I use this .pit or should I use the one that I can extract from the phone with Heimdall?
2) The .img files seem to be lz4 compressed so should I first decompress those, or can I pass the compressed file to heimdall?
3) Inside the tar file for Odin {AP, BL, CP, CSC} there are a meta-data folder with a fota.zip file, does this file in any way influence heimdall flashing process?
p.s. I not sure if this should be moved to the device subforum as the questions mainly deal with the Samsung devices and heimdall in general and I could not find a Samsung sub forum to post this to
So I got the situation sorted.
1) The .pit file in the stock rom was the same as the phones, so I didnt have to do anything about that
2) The .img, .bin files must be decompressed first, not a great deal just had to 'lz4 -d' those
3) Those fota.zip didnt matter for heimdall, I just followed the phones .pit file to match partition names to partitions file and did a single 'heimdall flash' command
Hello, apologies if this isn't the right place to post this question but I'm at a complete lost and I'm desperately trying to fix the device. My goal was to simply root the device.
I tried following this guide but by the end of my first run of the guide I had errors with the contacts and phone android apps. But the device still wasn't root. I attempted it again only to break the device completely. I wasn't even able to open Android Recovery and only flashing the bootloader only did I manage to to back to the recovery screen. However, from here, I am unable to flash the firmware any further. I only get a message now notifying me: "only official released binaries are allowed to be flashed".
What I'm hoping to achieve with this question is to get some direct guidance on how to resolve my current error. I've followed a few guides and thread a few threads but nothing seems 100% applicable to my issue or the device.
Using Odin3_v3.13.1 and what I think is the stock firmware for J4 (following the download links on the guides) I do the following:
Unzip the binaries with 7zip ZS to uncompressed the various files, specifically the AP, BL, CP, CSC and HOME MD5 files.
I further unzip the AP file and drag the boot.img.lz4 into lz4.exe to just give me the img file.
I run that through Magisk Manager to create a patch file (on another phone) and reupload back to the pc.
I then take the patched file and drag it into lz4.exe to just give me the img.lz4 file
I then delete the original boot.img file and select all of the files and compress into a tar archive.
OR, even without doing any of that and just straight selecting the AP file without doing the patching, I either get a straight up FAIL! (Auth) from Odin and if that doesn't happen, I get the error on the phone itself saying that "only official released binaries are allowed to be flashed".
And that's where I'm just stuck. I know there are many guides, and I tried making sure I have the best one and knowing what to do, but I think I messed something up along the lines. Any assistance would really be greatly appreciated.
Thank you.