Develop Bugs

[Q] Odin vs Heimdall

I understand the differences between the two but aren't packages that work for Odin supposed to work for Heimdall also? I run Linux so Heimdall v1.4RC1 is pretty much my only option, but whenever I try to flash an Odin package Heimdall won't flash it because it keeps on saying that the package is missing firmware.xml.
For example, My phone is currently boot looping and I need to reflash TWRP but I can't because even the Odin flashable package that they link to here doesn't work, so I have to wait until my roommate comes home so I can use his windows laptop to use Odin.
Why does Heimdall require firmware.xml but Odin doesn't? Are their Heimdall specific packages?

re: heimdall
brando56894 said:
I understand the differences between the two but aren't packages that work for Odin supposed to work for Heimdall also? I run Linux so Heimdall is pretty much my only option, but whenever I try to flash an Odin package Heimdall won't flash it because it keeps on saying that the package is missing firmware.xml.
For example, My phone is currently boot looping and I need to reflash TWRP but I can't because even the Odin flashable package that they link to here doesn't work, so I have to wait until my roommate comes home so I can use his windows laptop to use Odin.
Why does Heimdall require firmware.xml but Odin doesn't? Are their Heimdall specific packages?
Click to expand...
Click to collapse
I have no idea why heimdall requires firmware.xml but are many Mac users here on XDA who would know more about it..
Personally I like Odin much better although I have flashed many roms using Heimdall over a year ago.
Good luck,

It turns out it's a requirement of the front-end for some reason, it works fine with the command line version.
I flashed a kernel with sudo heimdall flash --20 boot.img and it worked just fine.

re: one click heimdall
brando56894 said:
It turns out it's a requirement of the front-end for some reason, it works fine with the command line version.
I flashed a kernel with sudo heimdall flash --20 boot.img and it worked just fine.
Click to expand...
Click to collapse
Here is the One Click Heimdall , it's latest version. Be sure you update your JAVA installation.
This 1 click heimdall looks so easy, it looks like the only option it has is to locate a TAR file
It opens/loads just fine without any errors..
Here is the download link: https://code.google.com/p/heimdall-one-click/downloads/detail?name=One-Click-Packager2.jar&can=2&q=
Good luck with it.

I need stock firmware from ANYONE SM-t807A it does not exist on the web.

I have spent days looking, turn on goes to kies firmware screen yet when i put in the model and s/n it shuts and the new samsung app to replace kies is of no help. I can get to the download screen and odin shows it up but no ATT 10.5 Tab S Sm-T807A firmware ANYWHERE.
Please help this is a very very expensive paperweight and im not affiliated with ATT so them helping me is out of the question.

Samobile.com

info.sven said:
Samobile.com
Click to expand...
Click to collapse
They dont have it for the SM-T807A

0 Results found
You searched for "sm-t807a"

It would better if you just explain what state the tablet is in and how it got to that state.
There is no official software for the t807a.

OK here how it goes,
The tablet was completely fine.
The original owner ( a family member) tried to root it and didnt accomplish it, somehow through his process it ended up softbricked.
I can enter he download mode for odin but no firmware for this LTE model.
When I turn it on it goes to the kies screen but kies doesnt recognize it, and when I enter the serial it buffers for 2 seconds then closes the process of kies.
Also it says device isnt supported and yes I have installed the right drivers and uninstalled kies numerous times.
The new replacement prog for Kies (forgot the name) is no help either.
Im terrified of what to do next as it does go to the odin screen just no firmware as I stated.

Any update, or could someone upload the stock firmware so i can use Odin on it.
Samsung told me ATT can flash it for free onto it so its deff a possibility however I do not have a ATT account so they cant help me.

It doesn't boot because the stock recovery has been wiped/replaced.
Thats assuming you have tried to boot recovery?
The att models are all bootloader locked.
I'm surprised a bootloader locked device even allowed an unsigned image to flash or did they use something like flashify?
The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image.

I was used with something like kingroot.
"The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image."
this i would highly appreciate as the firmwares not deleted just corrupted.

i have searched the whole web.
here is the link to the pulled stock sm-t807a files from a xda member
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing

PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files

synphonica said:
PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files
Click to expand...
Click to collapse
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.

I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.

also odin was used.

ashyx said:
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.
Click to expand...
Click to collapse
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.

PowerfulJY said:
I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.
Click to expand...
Click to collapse
Please explain in more detail what you have done for the benefit of others.
---------- Post added at 03:22 PM ---------- Previous post was at 03:22 PM ----------
synphonica said:
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.
Click to expand...
Click to collapse
Did you use command line or gui?

I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.

PowerfulJY said:
I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.
Click to expand...
Click to collapse
The gui question was for synphonica about Heimdall.
Are you saying you flashed the images with odin? Which version and which images?
This has been tried before and failed.
Also what do you mean you tried a pc with the same firmware, same firmware as what?

I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.

cluver53 said:
I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.
Click to expand...
Click to collapse
You can only root with Kingroot, don't try any other method or you'll brick it nor can you install a custom kernel or recovery.
Once you have root you can pull the partition images with EFS PRO or PARTITION BACKUP.
The best way to have a back up is to catch the stock Firmware update.
This is tricky so research how to do it.
There is one backup I know of:
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing

SM-J200GU/DS Stock firmware?

Hello,
While trying to root my J200GU I accidently wiped the OS. Now I am left with the TWRP recovery mode and access to Download mode.
I have been trying to flash a stock firmware to my phone using different methods without success:
1- Used Odin tool but it fails when it begins to write the rom
2- ADB sideload - Gives me an error saying the rom is missing the META INF
3- TWRP Install - I tried different zipped roms and all of them give me error saying cannot detect MD5, although the file is there inside.
I am very confused I dont know what is wrong. I am not sure if the roms I use are good but since I already tried multiples I might be doing somethin else wrong.
Can anyone help me out. Does anyone has a stock rom that actually works? or a method?
Thanks.
V.

download the official samsung firmware at sammobile then flash it through odin.

[Recovery][N8000/N801x/N8020] TWRP 3.3.1-0

To make this a little bit more visible for people not interested in my LOS thread but who still want to install the greatest recovery of them all, I'll post this in this separate thread for you.
What is TWRP?
TWRP is a custom recovery that enables you to backup and restore your device partitions, flash Custom ROMs, copy files from your internal storage, sideload stuff to your device and do many more amazing things. For more info visit their website.
A word of warning
The provided files are currently in beta and not fully tested!
My initial tests yielded positive results for a lot of the functions but I may have overlooked something and it may collapse on you. Don't blame me. Only use this if you have access to a computer with Odin to fix your recovery in case anything goes terribly wrong!
Please report any bugs in this thread and I'll try to fix them (or I'll relay them to the great people working on TWRP if I cannot do this).
Links
About TWRP
TWRP Changelog
Official TWRP Downloads
Downloads
The IMG file can be used to upgrade TWRP from an already installed older version, the TAR.MD5 file is for new installations and can be flashed via Odin. Please use the current TWRP from Lirokoa and use the Install Image button to update the recovery to this version. I need to figure out why the build is screwing up the TAR files.
TWRP-3.3.1-N8000-V1 (IMG)
TWRP-3.3.1-N801x-V1 (IMG)
TWRP-3.3.1-N8020-V1 (IMG)
I hope you enjoy this and that everything works as smoothly as it does for me.
For the device config, have a look at my Github repositories for the corresponding devices.
XDA:DevDB Information
TWRP for N8000/N801x/N8020, Tool/Utility for the Samsung Galaxy Note 10.1
Contributors
Don Carnage
Source Code: https://github.com/Viciouss?tab=repositories
Version Information
Status: Beta
Created 2019-01-30
Last Updated 2020-01-11

Reserved
Update Notes
Build 3.3.1-V1 (23.12.2019)
update to TWRP 3.3.1-0
layout override to landscape_mdpi for original layout with bigger bars (this time for real!)
fixed ADB access
Build N2 (28.02.2019)
Fixed wrong layout -> it's now easier to confirm actions
Build N1 (30.01.2019)
Initial release
Old Builds
TWRP-3.2.3-N8000-N1 (IMG)
TWRP-3.2.3-N8000-N1 (TAR.MD5)
TWRP-3.2.3-N801x-N1 (IMG)
TWRP-3.2.3-N801x-N1 (TAR.MD5)
TWRP-3.2.3-N8020-N1 (IMG)
TWRP-3.2.3-N8020-N1 (TAR.MD5)

I'd really appreciate your feedback, positive as well as negative, so that I can get a feeling for whether someone is actually using it and whether this is working. There have to be at least some of you who installed it after 700+ downloads. I want to have a good feeling before handing it over to the people at TWRP so that it can be officially downloaded from their website.

Don Carnage said:
I'd really appreciate your feedback, positive as well as negative, so that I can get a feeling for whether someone is actually using it and whether this is working. There have to be at least some of you who installed it after 700+ downloads. I want to have a good feeling before handing it over to the people at TWRP so that it can be officially downloaded from their website.
Click to expand...
Click to collapse
I did once gave a positive feedback pertaining to this latest version of twrp!! Its 150% fully working on my side, using a N8000!?

Thank you for all your work. Everything you do is at a level of excellence that I've only seen from the very best developers here on xda! I'm using your recovery on my N8013 and it works flawlessly.

Downloading and testing. I will give feedback ASAP.
---------- Post added at 12:48 PM ---------- Previous post was at 12:32 PM ----------
secretwolf98 said:
Downloading and testing. I will give feedback ASAP.
Click to expand...
Click to collapse
Testing went fine. Everything works. But I noticed somethings are small. I'm not sure if it is supposed to be like that?

secretwolf98 said:
Testing went fine. Everything works. But I noticed somethings are small. I'm not sure if it is supposed to be like that?
Click to expand...
Click to collapse
Yes there is an issue with the rotation. Currently TWRP thinks that it is in portrait mode. It's already on my todo list.

I updated the version. Build N2 fixes the layout problem.

I've tried both Odin 3.13.1 and 3.09 with both versions (N1 & N2) of the TAR.MD5 file for my N8000 but I never get any further than the MD5 check. All I receive when I tryy to load the file using the button AP in Odin is: "MD5 error! Binary is invalid"
I have used the Duth file mirrors and also the Canadian file server. All files ends up with the same result. Any ideas on how to proceed please? Thanks!!

MD5 is a damaged file .

bingoSexy said:
I've tried both Odin 3.13.1 and 3.09 with both versions (N1 & N2) of the TAR.MD5 file for my N8000 but I never get any further than the MD5 check. All I receive when I tryy to load the file using the button AP in Odin is: "MD5 error! Binary is invalid"
I have used the Duth file mirrors and also the Canadian file server. All files ends up with the same result. Any ideas on how to proceed please? Thanks!!
Click to expand...
Click to collapse
Change the extension name from MD5 to tar (just remove the MD5) in the file name. It should work.

Flashable file
Hi!
Firstly I would like to thank Don Carnage for great work in keeping this old tablet alive and running! My n8020 is stock recovery/stock rom rooted. Thing is, my usb port is not working and thus can't use odin. So I would need twrp.img-file that I can flash via terminal emulator. Could you provide it?
---------- Post added 19th March 2019 at 12:06 AM ---------- Previous post was 18th March 2019 at 11:55 PM ----------
Comphoton said:
Hi!
Firstly I would like to thank Don Carnage for great work in keeping this old tablet alive and running! My n8020 is stock recovery/stock rom rooted. Thing is, my usb port is not working and thus can't use odin. So I would need twrp.img-file that I can flash via terminal emulator. Could you provide it?
Click to expand...
Click to collapse
Nevermind, I bit the bullet and flashed the .img file that was meant for updating. Worked fine!

I use CWD, can I use odin to flash twrp over CWD without any issue?

CWD ??
TWRP can be flashed ok via recovert or Odin.

timmysk said:
I use CWD, can I use odin to flash twrp over CWD without any issue?
Click to expand...
Click to collapse
You mean Clockwork Mod recovery?

Yes clockwork mod

yeah!. lol.... he perhaps does.....hoorah! to "CWD'

timmysk said:
Yes clockwork mod
Click to expand...
Click to collapse
I think you'll have to flash it via Odin. I do have a copy of Odin that may work. Let me know if you need it.

That recovery is totally outdated and often does not work on latest rom builds .Nandroids may also fail .

timmysk said:
Yes clockwork mod
Click to expand...
Click to collapse
Not sure whether this will work with CWM, you should use Odin/Heimdall instead.
bingoSexy said:
I've tried both Odin 3.13.1 and 3.09 with both versions (N1 & N2) of the TAR.MD5 file for my N8000 but I never get any further than the MD5 check. All I receive when I tryy to load the file using the button AP in Odin is: "MD5 error! Binary is invalid"
I have used the Duth file mirrors and also the Canadian file server. All files ends up with the same result. Any ideas on how to proceed please? Thanks!!
Click to expand...
Click to collapse
I will check the Odin files tomorrow, it's already quite late here and I need some sleep.

‘Vendor’ partition flash fails part-way. Can't start device.

I'm attempting to re-flash the Samsung Galaxy S9 (SM-G960F) partitions from the official firmware.
Most partitions work, but the “VENDOR” partition fails part-way through.
Heimdall reports “ERROR: Failed to send file part packet!” and the session aborts.
According to the device this is because “SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)”
In this state the device refuses to start at all; powering on the device leads instantly to a graphical message:
> An error has occurred while updating the device software.
> Use the Emergency recovery function in the Smart Switch PC software.
I don't use Windows at all, so don't have that software. How can I use Heimdall to flash the full Vendor partition without error?

herbicide said:
I'm attempting to re-flash the Samsung Galaxy S9 (SM-G960F) partitions from the official firmware.
Most partitions work, but the “VENDOR” partition fails part-way through.
Heimdall reports “ERROR: Failed to send file part packet!” and the session aborts.
According to the device this is because “SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)”
In this state the device refuses to start at all; powering on the device leads instantly to a graphical message:
> An error has occurred while updating the device software.
> Use the Emergency recovery function in the Smart Switch PC software.
I don't use Windows at all, so don't have that software. How can I use Heimdall to flash the full Vendor partition without error?
Click to expand...
Click to collapse
Sorry ... I would get a Windows PC, install Samsung drivers and Odin, then flash stock firmware files (if really needed with pit file for re-partitioning) to the phone.
Just for repairing the device. Then you can give the windows PC back to your friend.

Thanks for the reply:
It_ler said:
[…] flash stock firmware files (if really needed with pit file for re-partitioning) to the phone.
Click to expand...
Click to collapse
When I tried that earlier, the device aborted the flash process and displayed the message
SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)
Click to expand...
Click to collapse
I think Odin running on Windows will simply do the same thing; what would be different if I tried again?

herbicide said:
Thanks for the reply:
When I tried that earlier, the device aborted the flash process and displayed the message
I think Odin running on Windows will simply do the same thing; what would be different if I tried again?
Click to expand...
Click to collapse
IDK about Heimdall, but there are patched versions of Odin available with which you can skip some file version validations.
And with Odin you can explicitly flash a pit file to re-partition the internal storage.

It_ler said:
[…] there are patched versions of Odin available with which you can skip some file version validations.
Click to expand...
Click to collapse
Oh, that sounds useful. Where can I find that patched Odin?

herbicide said:
Oh, that sounds useful. Where can I find that patched Odin?
Click to expand...
Click to collapse
There are several versions available, such as here:
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Be careful to flash only files that are compatible with your exact device model.

It_ler said:
Be careful to flash only files that are compatible with your exact device model.
Click to expand...
Click to collapse
One thing I wonder is whether I already attempted to flash the wrong firmware.
If that's what I did, have I actually made the problem worse? Or will flashing the correct firmware work anyway?

SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)
Click to expand...
Click to collapse
this means, the firmware you'll install is to old.
you can't downgrade your device.
search for frija or samfirm reborn (both windows) here in xda to get an actually Firmware, use binary nature.

MikeT. said:
this means, the firmware you'll install is to old.
you can't downgrade your device.
Click to expand...
Click to collapse
Ah, that makes sense. And if I simply flash a newer firmware now, the earlier failure does not matter. Right?
MikeT. said:
search for frija or samfirm reborn (both windows) here in xda to get an actually Firmware, use binary nature.
Click to expand...
Click to collapse
I have found a firmware that appears to match, at https://samfw.com/firmware/SM-G960F/XSA/G960FXXUFFUC6
any reason why that is a bad choice?