Related
Ok.. I tried using Heimdall 1.1.1 (latest) last night to restore my i897 Captivate to stock. It failed and I got the connect-to-pc screen. Easily fixed by going back to download mode and using ODIN 1-Click.
I have been searching and reading for 2 days trying to get this to work and failed on my first attempt.
When I tried to flash JF6 I included the 512 PIT file that we use with ODIN. However, in the directions on the i9000 for flashing with Heimdall (LINK) - they say you don't need the PIT file unless you'r flashing a firmware that uses a different PIT file, but to my knowledge all Captivate ROMs use the 512 file.
So I'm wondering if you need the PIT file to flash to stock from a custom ROM? It's always used when using ODIN so I don't understand why it wouldn't be needed with Heimdall.
Just trying to be cautious as I don't really want to brick my phone and doing random stuff without any knowledge of it sounds like a good way to get an expensive paperweight. I am running Heimdall on ArchLinux btw. I have to steal my friends Windows PC to use ODIN.
Any insight is much appreciated. If I can successfully get this to work I plan on posting an easy step-by-step guide for using Heimdall for those of us that don't use Windows.
You can opt out of flashing the PIT, since some thing it's safer that way.
Also check this out, it's a pretty easy guide to follow:
http://forum.xda-developers.com/showthread.php?t=878686
That's the post I followed and failed. Its linked in the OP.
Following those directions got my phone stuck on the "computer -> phone" screen.
I also have an issue with Heimdall. I couldn't get it to recognize my phone. Yes... I did install the drivers and it was in download mode. Any suggestions?
Did you reboot after installing drivers?
i've flashed with and without pit files. both work fine.
i was flashed my phone with the Perception-II-Beta-1 rom and now i cant enter to the recovery or fastboot mode,i need the flash.img of clockwork recovery or like that...to flash the recovery via terminal emulator,please help me.
i only was found the zip archive in the net...
when i try to enter to recovery mode the at&t logo appear and dont change...and when i press power is reboot...
:S when i can say the recovery when the capture program of sdk qtadb...
i was try to flash a zip watching the capture image but,the phone reboot...
Hi, you must be new here. There is no 'fastboot' on galaxy s phones, and you don't need to actually flash clockworkmod. What you need to do is get your phone into download mode and fix it with odin. Take a deep breath and a timeout to peruse the Captivate subforums. There is a wealth of information here about your very problem (particularly the stickied threads).
yes im new here,my old phone was a htc g1...and i was get the captivate on april 23...the problem is that i dont have windows and dont have any way of get it...im using gnu/linux,and odin is only for windows.
pd:sorry my bad english,my national language is the spanish...
That's what you get for being a non-conformist
Anyway, I think there's a linux version called heimdall. Or, you can simply run windows in a virtual machine, or try your luck with wine.
modest_mandroid said:
That's what you get for being a non-conformist
Anyway, I think there's a linux version called heimdall. Or, you can simply run windows in a virtual machine, or try your luck with wine.
Click to expand...
Click to collapse
Odin doesn't like virtual desktops. You need to use heimdall on linux or (barf) mac.
thanks guys,im downloading heimdall to try it...
studacris said:
Odin doesn't like virtual desktops. You need to use heimdall on linux or (barf) mac.
Click to expand...
Click to collapse
works great for me
i run vmware workstation on my laptop thats running ubuntu. thats the only way i use ODIN...in a VM, unless i'm at work
install a VM?? oh i dont know about that.. my computer is at least 200 times bigger than my phone... i dunno if i can program something that big and complicated.....
*sarcasm* aiming for that 51%
nothink...i cant compile heimdall in fedora...is no any form to do that with the terminal emulator? or some like it...
Wait a second.. did you try to flash Percep 2 without flashing the new 2.3.3 bootloaders? If so, you won't be able to reboot back into recovery until you either use odin to go back to a 2.2 rom and keep your old bootloaders, or use odin to flash the stock JVB with the new bootloaders. Either way, the only solution at this point (if my assumption is correct and you flashed a 2.3 rom without the new bootloaders) is to use odin.
i was resolved my problem with odin how you say thank you ...sorry for the disturb...
Alright, this is just odd.
Generally, I want to get rid of the bloatware and make it so my phone doesn't run so much crap in the background, so I have turned to rooting it. However, this is more of a pain than anything.
I followed the Odin guide in order to get CWM, bloat removal, root, stock kernel, stock rom, etc, and its odd whats going on.
When I connect my phone to my computer, outside of download mode, and have it in USB debug, then it detects my phone in odin just fine. However, when I put it in download mode, it decides my phone is in a different dimension. Why is this?
When I unbricked it, I had to use heimdall. Odin detected it then, but couldn't fix, which turns out because I was using a crappy cord. I'm using the new cord now, and still getting problems with it detecting it in Odin.
Other info: I have the drivers installed from Kies Mini, I am currently trying to root with superoneclick, I have already cleared data via recovery mode, and oppan gangnam style.
Anyone able to help me understand why odin doesn't wanna detect my phone?
Spectre370 said:
Alright, this is just odd.
Generally, I want to get rid of the bloatware and make it so my phone doesn't run so much crap in the background, so I have turned to rooting it. However, this is more of a pain than anything.
I followed the Odin guide in order to get CWM, bloat removal, root, stock kernel, stock rom, etc, and its odd whats going on.
When I connect my phone to my computer, outside of download mode, and have it in USB debug, then it detects my phone in odin just fine. However, when I put it in download mode, it decides my phone is in a different dimension. Why is this?
When I unbricked it, I had to use heimdall. Odin detected it then, but couldn't fix, which turns out because I was using a crappy cord. I'm using the new cord now, and still getting problems with it detecting it in Odin.
Other info: I have the drivers installed from Kies Mini, I am currently trying to root with superoneclick, I have already cleared data via recovery mode, and oppan gangnam style.
Anyone able to help me understand why odin doesn't wanna detect my phone?
Click to expand...
Click to collapse
bleh windows and odin problems. it might be a usb controller problem. or a driver problem... the usb chord should always be plugged directly into the back of the computer into the ports on the motherboard preferably. no hubs or anything. also the heimdall driver might be messing with the samsung download mode driver. there is actually different drivers for download mode and normal connections from samsung. it looks to the computer like different devices. for odin to work you need to connect in download mode and wait for windows to install the drivers or download the drivers from the samsung support website and install them manually. this might require removing all existing samsung drivers and the heimdall driver and starting over.
i have to ask though, if you unbricked the phone with heimdall why not use heimdall to flash the cwm kernel? all you have to do is extract the zImage from the .tar and flash it to the kernel partition.
also fyi super one click can not work on official gingerbread. the att official gingerbread is apparently very secure. or the real hackers never paid it any mind because it is so easy to work around that limitation with odin or heimdall.
Well, I can try digging through and see if the heimdall driver might still be there, idk if it is or not. Also, when I plug it in in download mode, it installs a driver, but when I look through device manager, it says the device isn't there.
Also, I read somewhere you couldn't root the phone with heimdall using the same method I was trying to get ahold of, so thats why I didnt use heimdall. But in that case, any chance you could link me to a guide on how to do that? The main thing I want is to get rid of this bloatware and crap.
Spectre370 said:
Well, I can try digging through and see if the heimdall driver might still be there, idk if it is or not. Also, when I plug it in in download mode, it installs a driver, but when I look through device manager, it says the device isn't there.
Also, I read somewhere you couldn't root the phone with heimdall using the same method I was trying to get ahold of, so thats why I didnt use heimdall. But in that case, any chance you could link me to a guide on how to do that? The main thing I want is to get rid of this bloatware and crap.
Click to expand...
Click to collapse
what link were you following? so i can see what you are working with..
the only ways to root is to flash a pre-rooted /system image(but i haven't seen one, i've been too lazy to make one myself) or flash a cwm kernel and use it to flash an su and superuser package. some of the older kernels had a rooting script but it sometimes borks su if you update it and will downgrade su when you reboot so the devs took the rooting feature out of the kernels. both the /system image and the kernel method need heimdall or odin. anything that odin does heimdall does but heimdall uses different packages or no "package" at all.
heimdall can be done in command line and it's easier to explain that way than the ui. are you comfortable with command line?
THis is the link to the guide i was using. http://forum.xda-developers.com/showthread.php?t=1613523
And I'm not too great with command lines. I have next to no experience with linux os, and though I've tried to learn some, it just doesn't seem to stick.
Hell, most of what you said doesn't entirely make sense to me.
New info. Computer detects it in download mode, but odin doesnt. Grr to this stuff.
I think I found the main problem.
When I unbricked my phone, I upgraded to GB. Now I'm at GB, and according to what I read, thats where all the problems are stemming from. Is there a way to root when you are on GB? Or do I need to downgrade to Froyo, root, then go back to GB?
If I have to do the latter, then I'll just skip GB and figure out the CM9 stuff.
you should still be able to use heimdall, and i think it can work with the samsung drivers, the open source driver heimdall uses may help in some situations but i dont think it's needed. odin can be weird. i never use it.
you have 2 options asuming heimdall works(i think it will). you can use option a from that thread but flash it through heimdall, or you can go to the thread for entropy's kernel and download the zImage and flash that through heimdall.
for heimdall download this and extract it to a folder somewhere. https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.1-win32.zip
you may also need this but it may already be on your system http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en
download the rom .tar file (or kernel zImage if you want cwm) that you choose and extract the contents to the folder that contains the heimdall files.
if you are using the rooted rom, stock kernel no cwm package it is in .rar and there is a .tar or .tar.md5 inside of that. remember to extract the .tar and not just the .rar.
now if you are already on the att release if gingerbread uclb3 you will only need the factoryfs.rfs remeber that it should be in the same folder as the heimdall.exe file
put the phone in download mode and connect the usb cable then open a command prompt and navigate to the folder with heimdall and the factoryfs.rfs (c:\users\<login name>\<whatever folder you made or chose>\ ) and type
Code:
heimdall flash --factoryfs factoryfs.rfs
if you chose to use a kernel with cwm instead then you will use the zImage file. download the kernel you want and extract the zImage file into the heimdall folder or what ever you called it. go into a command prompt and type
Code:
heimdall flash --kernel zImage
after you have cwm you can download this http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip for root, move it to the sdcard and reboot to recovery and flash it in cwm
if you are not comfortable with command line you can use the frontend but it requires the pit file which you need to get from the unbrick packages.
First, I tried searching for hours, and I haven't been able to find this same issue anywhere on the forums yet. If I missed it, sorry, and thanks.
I downloaded the stock 2.3.6 firmware from the Hiemdall One-touch thread here, and ran it on my phone (SGH-T959V Galaxy S 4G, and I made sure the firmware was for that specific model and not the Vibrant). It ran through the first time just fine, and then I went to do the bootloader (which I gather I probably shouldn't have done and didn't need to do maybe). Heimdall One-Click started running, then gave me this message and restarted the phone to a black screen:
Code:
Uploading PIT
PIT upload failed!
Ending session...
Rebooting device...
Now, I can pull the battery and get the phone into Download Mode just fine, and I've tried running the same firmware as well as several others (AntonX-Basic_with_a_twist, Stock KJ6 + root-One-Click, hampsterblade-Basic_MIUI_Kernel_r2_OC_UV, at least), but while they all do the first restore fine, none will load the bootloader and I get the same results every time. The phone is obviously not 100% bricked since I can get into Download Mode, but all I get is a black screen, no lights under the buttons and nothing on screen, not even the rainbow pattern or the Samsung logo. It's as if the phone isn't doing anything at all, and it doesn't change if I just pull the battery and leave it (tried for 15-20 minutes a little while ago). The only thing I can do is put it back into Download Mode, but none of the firmwares I've found have worked to restore the bootloader.
I am using a Mac with 10.8 and Java 1.7, and if it's necessary I can get access to Windows, but that will take me some time and effort, so if there's any way to resolve it using just the Mac that'd be best.
jW
When you flash the Heimdall package, does the phone boot fine?
It should have work with Mac, can you double check things?
If possible can you try re-downloading the .jar package.
And in the terminal run the .jar package (sorry I don't know OS X commands).
Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW
jondesu said:
Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW
Click to expand...
Click to collapse
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.
th3controller said:
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.
Click to expand...
Click to collapse
Thanks, I've got a Linux distro downloading and I'm looking into whether I could get a copy of Windows or borrow a PC easily.
jW
You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.
FBis251 said:
You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.
Click to expand...
Click to collapse
Thanks, I'll give that a try (still trying to get Linux installed here to try that as well). The first one I tried, and the one I think I'd prefer to use is the T959VUVKJ6 Stock UVKJ6 from the Heimdall One-Click thread in the forums here. I tried some of the others when that one failed. It downloaded fine, and I tried downloading it again with no change in the results.
I should clarify, btw, that I have been trying flashing it without the bootloader, but when I do that, it still sits on the black screen. The very first time I did it and one other time later, I did get the rainbow screen (and the first time, but never again, it did boot up to the stock OS and home screen), but now if I flash with or without the bootloader, I get nothing, probably because the bootloader got screwed up by the first bad flash.
My first step today will be using another cable (there's one handy, I just didn't think about it), and then I'll move on to trying Linux/Windows.
jW
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
micheal3chaife said:
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
I'm a part-time Linux user also but I can't say that I've ever had luck with using Heimdall to flash Samsung devices. Many people have used it and had success but for me it has always been a pain getting the right "extra" packages installed and configured correctly for Heimdall to function correctly, it involves more than just installing and running Heimdall.
In my experience, Odin on a Windows PC is hands down the best way to go for flashing Samsung Devices.
Also, when you say they all fail in the end, what do you mean? Are they not working at all or are you able to begin the flash but it fails before it finishes the flash?
Droidriven said:
I'm a part-time Linux user also but I can't say that I've ever had luck with using Heimdall to flash Samsung devices. Many people have used it and had success but for me it has always been a pain getting the right "extra" packages installed and configured correctly for Heimdall to function correctly, it involves more than just installing and running Heimdall.
In my experience, Odin on a Windows PC is hands down the best way to go for flashing Samsung Devices.
Also, when you say they all fail in the end, what do you mean? Are they not working at all or are you able to begin the flash but it fails before it finishes the flash?
Click to expand...
Click to collapse
Hi, thanks for the sympathetic response (read: 'shouder to cry on').
"Break" in the sense that eventually, each of the programs I have tried - Heimdall, JOdin3, and Odin - have shown errors that, so far, have proven fatal:
*Heimdall requires 'Heimdall Packages' that seem to exist nowhere
*Odin fails to communicate with the phone
*JOdin3 returns a 'corrupted file' message when one directs it to the firmware to upload and flash. This issue has been reported to the maintainer's github as of 12 days ago, meaning it is a very recent issue.
The Heimdall issue *may* have a workaround - one can try, as per the maintainer's instructions on his github, feeding the component files one by one to the main process. I will try that.
A further possibility lies in the fact that previously, I had not enabled 'USB debugging' on the phone itself, which may or may not help with the interface.
There is also ADB, which I took a cursory look at last night. ADB appears to be able to work to move packets between a computer and a phone.
There is the option, on Samsung phones, to 'Appy update from SD card', which is what I propose to try now.
Latly, there is the option of installing an entirey different OS on the phone, and to hell with Android (?).
I will keep all you folks who are now rooted to the edge of your seats updated as things move along.
micheal3chaife said:
Hi, thanks for the sympathetic response (read: 'shouder to cry on').
"Break" in the sense that eventually, each of the programs I have tried - Heimdall, JOdin3, and Odin - have shown errors that, so far, have proven fatal:
*Heimdall requires 'Heimdall Packages' that seem to exist nowhere
*Odin fails to communicate with the phone
*JOdin3 returns a 'corrupted file' message when one directs it to the firmware to upload and flash. This issue has been reported to the maintainer's github as of 12 days ago, meaning it is a very recent issue.
The Heimdall issue *may* have a workaround - one can try, as per the maintainer's instructions on his github, feeding the component files one by one to the main process. I will try that.
A further possibility lies in the fact that previously, I had not enabled 'USB debugging' on the phone itself, which may or may not help with the interface.
There is also ADB, which I took a cursory look at last night. ADB appears to be able to work to move packets between a computer and a phone.
There is the option, on Samsung phones, to 'Appy update from SD card', which is what I propose to try now.
Latly, there is the option of installing an entirey different OS on the phone, and to hell with Android (?).
I will keep all you folks who are now rooted to the edge of your seats updated as things move along.
Click to expand...
Click to collapse
USB debugging makes a difference. Have you tried using older or different versions of Heimdall?
Are you running a VM to run windows and windows programs on linux or are you using wine to run windows programs? Wine doesn't work well enough to make it a viable option to run Odin.
I really suggest you bite the bullet and use a Windows system to use Odin. As long as you haven't corrupted any of the partitions on the device, flashing via Odin on a Windows PC will be effortless, a few clicks and a few minutes, done and done.
I think it could be dependent on the quality of the packages built by the packagers for your distro as to whether 'heimdall' works for you. I recently flashed LineageOS (2 days ago) on my old Galaxy Note 10.1 (2014) tablet using heimdall. I posted about it here: https://forum.xda-developers.com/f/galaxy-note-10-1-2014-edition-q-a-help-troubl.2502/
Note that hardware aspects such as a quality USB cable can at times be issues, and you may have better luck using a PC's USB-2 port instead of a USB-3 port.
In my case, for openSUSE LEAP-15.2 I successfully used heimdall-1.4.2
I also used android-tools-9.0.0 packaged for same openSUSE version, which provided 'adb' and 'fastboot'. While 'adb' worked for me, I could not not get 'fastboot' to detect my tablet when the tablet was in 'Odin' mode - and hence I could not flash with 'fastboot'. Fortunately heimdall did detect the Tablet when the Tablet was in 'odin' mode, and I was thus able to flash TWRP from 'heimdall'. I note specifying 'RECOVERY" in 'heimdall' did not work for me, but instead specifying the 'Entry' location for the flash (after checking the PIT) did work for me. Again, documented the details in that thread above.
In all cases on my GNU/Linux I used command line and not GUI front ends.
Goodl luck in your efforts.
Droidriven said:
USB debugging makes a difference. Have you tried using older or different versions of Heimdall?
Are you running a VM to run windows and windows programs on linux or are you using wine to run windows programs? Wine doesn't work well enough to make it a viable option to run Odin.
I really suggest you bite the bullet and use a Windows system to use Odin. As long as you haven't corrupted any of the partitions on the device, flashing via Odin on a Windows PC will be effortless, a few clicks and a few minutes, done and done.
Click to expand...
Click to collapse
I do not have ready access to a Windows machine, alas... Thanks for the other suggestions. Yes, I've been trying with wine, but with USB debugging disabled. My next attempt will probably be with Heimdall + USB debugging.
If I go the VM route, do you have a suggestion on how to set that up?
RE: Heimdall, I was under the impression that the most recent version (1.4.2, if I'm not mistaken) is best.
Again, thanks for the imput. Wish me ... maybe not luck, but continued systematic determination. And a little common sense.
You can run ADB wirelessly, means over Wi-Fi. So no Windows machine is required.
xXx yYy said:
You can run ADB wirelessly, means over Wi-Fi. So no Windows machine is required.
Click to expand...
Click to collapse
I"m not sure that helps them.
micheal3chaife said:
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
....
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
I hope you managed to finally succeed.
'Fresh' on the successful install of LineagOS-14.1 on my Samsung Galaxy-10.1 (2014) using adb and Heimdall on openSUSE-LEAP-15.2 (v.1.4.2 of heimdall) I then a couple of days ago proceeded to install LineageOS-14.1 on my wife's old Samsung Note-8 tablet.
As before, I pre-positioned the zip files for lineageOS and for GAPPS on her tablet, and then used heimdall to flash TWRP from my GNU/Linux PC.
it took me 3 attempts to flash TWRP, with the first failed attempted breaking the regular Android 4.1 boot to the Tablet, but fortunately it would still boot to the Tablet's recovery 'download' (flashboot) mode. The issue with the failures with me was a somewhat flaky USB cable. This is the best of about a dozen USB cables I own, and it works great for charging .... but for data transfer in a flash, my experience is the cable has to be very very VERY good. Note I was using a USB2 port.
Once TWRP was flashed, I tried to boot the Tablet to recovery mode, but the darn thing booted instead to the old Android 4.1. I was afraid that would wipe the TWRP, ... so I then with the Tablet still powered, ran 'adb' with appropriate recovery reboot options (from my GNU/Linux with Tablet connected), and the Tablet fortunately booted to TWRP (and it had not yet been wiped).
With TWRP running it was a simple matter to flash LineageOS and GAPPS. This time, BEFORE rebooting after the LineageOS/GAPPS flash, I was then careful to ensure TWRP re-flashed/installed, and it kept TWRP on the Samsung Galaxy Note-8. With my previous Samsung Galaxy Note-10.1 (2014) install I did not do that, and I had TWRP wiped after my reboot to LineageOS.
Again good luck in your efforts. I can say heimdall in GNU/Linux does work (together with adb).
micheal3chaife said:
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
Look here.