Hey guys, I really want to install ROMs, but I'm pretty much a newb of this. I looked in the development section and found out how to download ROM manager and what-not, but I'm not sure, what is NVFLASH and can I download via Mac?
Mikeglongo said:
Hey guys, I really want to install ROMs, but I'm pretty much a newb of this. I looked in the development section and found out how to download ROM manager and what-not, but I'm not sure, what is NVFLASH and can I download via Mac?
Click to expand...
Click to collapse
Only Windows and/or Linux. If you're running Windows under Boot Camp or emulation on your Mac, that should work too.
Also, please search a bit before making a new thread. I'm probably the 19th person to answer that question
Was doing some searching, couldn't find it.
I don't have bootcamp on my mac, so I'm assuming there won't be a way for me to install ROMs then unless I have a windows computer/Linux?
You just need a windows PC to use nvflash to install clockworkmod recovery onto your phone. Ask a friend to use their PC for literally 5 minutes.
If not, get a copy of Windows and install it on your mac via BootCamp. Having Windows as an option on your computer can come in handy (as you can see now).
Yeah, I can ask a friend, but knowing me I'd take forever. I'm new to this and not sure how to do this much. I know an employeee at t-mobile that knows how to do it. I can ask him for a favor and show me how to save my stock ROM, I did it before and it didn't come out too nice.
So i have been getting boot loops on every rom i've tried to flash from my sdcard in cwm. I tried using heimdall one-click on my mac but it keeps getting stuck at "claiming interface". I've already searched many threads but found nothing. Any help on how to fix this?
not to many people are giving up information on heimdall with a Mac. I know the web page talks about something called codeless kext but I don't have a Mac and have no idea what that is. my suggestion is to put Ubuntu on it.... jk but heimdall on Ubuntu is stupid easy, getting the video and wifi and cd-rom can be another story depending on your hardware. I think most Mac users are not to savvy or they'd just be running Linux I know osx is a great OS but it seems to lack users that like to tinker. well not totally true but with so few users the guys that really know Macs are hard to come by.
are you getting that message when you are installing one click to mac ?
Hi!
I'm surprised, nobody asked this already, at least I haven't found it:
Is there a way of flashing/upgrading my GT-S8500 phone a custom firmware/newer stock firmware using linux?
I know, s1 have to use multiloader for flashing, and it's windows only, but maybe some expert can tell me, if there's some alternative, even if it's harder/longer, way of reproducing what multiloader is doing, in linux. Thx in advance!
konrad.lorenz said:
Hi!
I'm surprised, nobody asked this already, at least I haven't found it:
Is there a way of flashing/upgrading my GT-S8500 phone a custom firmware/newer stock firmware using linux?
I know, s1 have to use multiloader for flashing, and it's windows only, but maybe some expert can tell me, if there's some alternative, even if it's harder/longer, way of reproducing what multiloader is doing, in linux. Thx in advance!
Click to expand...
Click to collapse
What exactly are you trying to do. I'm not familiar with the s1 and it's 'multiloader'. Are you referring to dual booting? Sorry if i'm missing your question completely. Some of us at ArcDatum do embedded systems research with ARM boards and have various multibooting devices booting anything from basic stock android stuff to gentoo/arch linux distros both separately and in dual booting environments. We use dev boards like the BeagleBoard and Pandaboards.
If you're trying to flash something weird onto ur phone though, chances are you can't or shouldn't. The only reason why it's safe for us to do it with the dev boards is because the System on a Chip is configured (by pulling specific pins high or low) to boot from the SD card and read the bootloader from there. In the case of most phones, you have locked bootloaders and no way to change that without risking destroying your boot process.
I'm trying to upgrade the factory system of my phone to a newer factory one, or to turkocfw (at first try, i'd be happy with the factory one).
Basically this is done through Kies -but thats windows only- or Multiloader -which is also windows only-, but my laptop has linux on it. I want to know, if there is a way, if I can manually do on linux, what kies and multiloader does on windows.
ArcDatum said:
What exactly are you trying to do. I'm not familiar with the s1 and it's 'multiloader'. Are you referring to dual booting? Sorry if i'm missing your question completely. Some of us at ArcDatum do embedded systems research with ARM boards and have various multibooting devices booting anything from basic stock android stuff to gentoo/arch linux distros both separately and in dual booting environments. We use dev boards like the BeagleBoard and Pandaboards.
If you're trying to flash something weird onto ur phone though, chances are you can't or shouldn't. The only reason why it's safe for us to do it with the dev boards is because the System on a Chip is configured (by pulling specific pins high or low) to boot from the SD card and read the bootloader from there. In the case of most phones, you have locked bootloaders and no way to change that without risking destroying your boot process.
Click to expand...
Click to collapse
Anyone?
That sounds a bit odd..I still dont quite understand how linux comes into play here. All the phones I've had deliver official Samsung updates over the air. Have you tried upgrading directly from ur phone?
Sent from my SGH-I747M using xda app-developers app
It should work under Wine or in a Virtual Machine. If you don't know what these are, you can easily Google them up. A basic concept
Also, for S8500 I would like to recommend http://darkforestgroup.com/forum/ a decent forum for all those older Samsung handsets.
Thats a good point. I havent used wine In a while. Although Id be careful of that, u kno, with the magic wine stuff that they pull off. Might cause some issues and risk ur phone
Edit: vm on the other hand id be more comfortable with
Sent from my SGH-I747M using xda app-developers app
ArcDatum said:
I still dont quite understand how linux comes into play here.
Click to expand...
Click to collapse
That's the operating system of my notebook. I want to use that computer for upgrading/flashing my phone.
ArcDatum said:
All the phones I've had deliver official Samsung updates over the air. Have you tried upgrading directly from ur phone?
Click to expand...
Click to collapse
Yes, but the function is 'defect by design', it is FUBAR, that function doesn't work (not only for me, it doesn't work for anyone using the same system on their phone (bada1.2)). I don't know, if it is working on bada 2.0, because I can't upgrade it.
Eddie^^ said:
It should work under Wine or in a Virtual Machine.
Click to expand...
Click to collapse
It should, but looks like it doesn't. Wherever I've looked (looks like I cannot post outside links to prove my point, sorry :S), I've found the same advice: "Don't use Kies in a VM!"
Eddie^^ said:
Also, for S8500 I would like to recommend darkforestgroup.com/forum/
Click to expand...
Click to collapse
Thanx, I had a look at there, but didn't see anything related
So, the question remains the same, if anyone knows, how (exactly) multiloader works, and that working can be reproduced on linux (without multiloader)...
Or can this be achieved using Heimdall?
Bump?
konrad.lorenz said:
Bump?
Click to expand...
Click to collapse
I would like to know if it is possible as well. Otherwise I might test it, but I'm afraid to break my phone
working on Virtualbox
autra said:
I would like to know if it is possible as well. Otherwise I might test it, but I'm afraid to break my phone
Click to expand...
Click to collapse
Ok, I can confirm it works using VirtualBox and Win7... No particular things to know, just follow the step as you would do on Windows !
Greetings All
I'm a noob who has performed due diligence with the search function as best I could. I'm trying to do to my tablet what I thought was pretty easy with my phone. I'm just can't seem to get my xp box to see the tablet when its in boot loader mode. Why does the same computer that I used Odin with to do my phone not see this tablet? Anyone? Is there a tutorial for SDK setup for xp?
Sent from my SCH-I535 using xda premium
Ameri said:
Greetings All
I'm a noob who has performed due diligence with the search function as best I could. I'm trying to do to my tablet what I thought was pretty easy with my phone. I'm just can't seem to get my xp box to see the tablet when its in boot loader mode. Why does the same computer that I used Odin with to do my phone not see this tablet? Anyone? Is there a tutorial for SDK setup for xp?
Click to expand...
Click to collapse
Please, have you search and read a little before to post something
Use the research by search all forums, type your request...that's all
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.