So, I'm new here, and I got kinda lost in all these threads. I've already searcehd (a lot) for a solution for my problem, but even within here I can't find it.
So, the matter is quite simple. I have a I9000B branded phone (by Claro, Brazil). And despite the not-so-recent leaking of a Vivo ROM on the web (wich I could find here, btw), apparently the operators and maybe Samsung Brazil are not caring much about updating our firmwares from 2.1 to 2.2 (and 2.3 is quite far, even for a fream around here). As I've heard/read, Vivo phones and unbranded ones are already receiving this update via Kies. The thing is:
1) Kies says I have the latest firmware available.
2) I downloaded the Vivo ROM (the hardware is the same form mine), and triee to install it via Clockwork ROM Manager, without success.
3) I tried to flash via ODIN, but when I get my phone on download mode the yellow working robot sign appears OK, but the phone doesn't get recognized by my PC. When it's on and in mass storage or kies mode, it works fine (for the intended purposes of the modes).
So, I'm kinda running out of ideas here on how to get the friggin update running.
Just for reference, I could find these 3 (and only) ROMs for the I9000B. Are they like... almost the same thing?
http://forum.xda-developers.com/showthread.php?t=889451
http://forum.xda-developers.com/showthread.php?t=858483
http://forum.xda-developers.com/showthread.php?t=869544
Thank you all!
So, answering:
Don't be so afraid of bricking your phone. Instead os plugging the USB cable and then turning on the phone in dowload mode (3 button combo), try turning the device on and then plugging the USB.
Another thing: this ROM (and apparently the other ones too) doesn't need a .PIT file to work on ODIN. Just use the .tar and have fun!
As for the ROMs, the I9000B_JPD_JPD_JPD_JPD_VJ_ZTO is a later build and should be better. Still got no idea what's a deoxed ROM, though...
Thanks man, you're a genius! Seriously, you're the only guy who answered me! It really seems like a completely new and unorthodox approach, but it really worked!
You're welcome. Always a pleasure to help myself.
Hello there ! I'm probably going to flash a new rom or at least recovery.
I'm first time flasher and have one question:
should I use Odin or Heimdall (I've got Windows 7 x64) ?
I've read that Heimdall is more reliable but Odin is best for flashing more things at once.
I want to know what do you think is the best.
Edit: Drivers don't work on Windows (error 10, adb ones are ok), so maybe I'll try Heimdall on linux.
Edit 2: I've booted into bootloader, then connected the phone and it worked.
Hello!
While I prefer Heimdall (which is free software, has native Linux support and supports both command-line and graphical interfaces), both apps were reliably flashing my S6310. I think that it’s not a problem to flash many partitions at once using Heimdall, but AFAIK it doesn’t support Odin’s .tar.md5 files.
All,
I read a lot here and gained a lot of "passive" help and information. Since I just ran into some newbie situations I'd like to give back a little bit of my experiences. Please note that this is NOT a highly technical post - just a few thoughts and ideas how to recover from potentially scary situations.
I've tried to get stock firmware on my T-Mobile S8 (this would also apply to the S8+). I've followed one of the many guides here - I think this one is the most complete (even though it's not up to date): https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
Even though I used the correct Odin and firmware, I unfortunately ran into the following issues:
1.) Odin reported a "write error"
2.) After that, the phone could not boot into the download mode anymore, reporting a "An error has occurred while updating the device software", a potential soft-brick situation.
3.) Odin got stuck at "setup connection"
Again, this is all pretty basic stuff and it is important: DON'T PANIC!!
1.) Odin "Write error"
Odin connected to the device, showed "Added", I added all files I wanted to flash, hit the start button and after 5s I received a write error. Well, the problem here turned out to be a faulty cable. I used an "old" USB cable with a Type-C adapter which was - in my case - the reason I almost "bricked" my phone. So make sure you use a high-quality cable.
Second, this also can happen at a later stage of the flash process. Most likely it is related to the wrong Odin version or wrong firmware. Again: don't panic! Read through the posts in the link above. A newer patched Odin is mentioned there which did the trick for me. Also, be sure you understand which firmware you wand and what bootloader you need.
2.) Recovering from "An error has occurred while updating the device software"
This "soft brick" looks scary at first. The device will not switch to download mode anymore, showing just the message looking like https://i.ytimg.com/vi/MvUXqEbwVvs/maxresdefault.jpg and mentioning something about Smart Switch. First, playing around with Smart Switch initially is not a good idea. It might be plan b but for now: you can stick with Odin. This thread here (https://forum.xda-developers.com/galaxy-s8+/help/help-potential-softbrick-g955f-t3747425) - last post - describes that the screen showing "an error has occured..." still allows Odin to work as desired. All I did was:
- used a good cable
- used the correct Odin (3.13 Patch B)
- used the correct Firmware (U1 XAA for non-carrier Samsung Stock)
Connect the phone, insert all 4 files into Odin, hit "Start" and here we go
Odin not connecting
This is another "minor" issues that might cause some anxiety - especially when combined with #2 above. The simple solution: just reboot. Other things that might help:
- use a good cable
- start Odin as admin
Again, this is not a very sophisticated post but I hope I can help some folks running into the same situation(s). I guess most users don't flash their phone daily and hence are not comfortable with running in such situations.
Cheers
J
Just wait until you encounter an SBL error.
Sent from my SM-G950U1 using Tapatalk
I want to add to OP
Make sure you always use USB 2.0 on S8 3.0 ports some reason cause issues on our devices...
As well
auth errors are normally trying to flash incorrect bootloader versions
The S8/+ and many other devices not limited to just Samsung employ Anti rollback
this will work for canadian s8 sm-950w
Angeloland said:
this will work for canadian s8 sm-950w
Click to expand...
Click to collapse
I'm pretty sure same method applies.
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.
Hi y'all. I'm new to the forums of XDA Developers. But, I'm not new to technology, phones, PC's, etc. I'm a noob in flashing a ROM to any specific phone. So, I decided to get help of other people to correct my issues. Any help will be really appreciated So here's what I've experienced:
I have the Samsung Galaxy A20s (SM-A207F). I want to flash a ROM on it (not custom ROM!). So, it currently runs OneUI 3.1 based on Android 11 and has 3 GB of RAM which means it will not support Android 12. And that's precisely what happened. I'm sick of Samsung's in-house OneUI and I wanna get the stock Android literally in my phone. I'm tired of using launchers, customizers, etc., because they don't do much. And now I'm on the verge of flashing my phone. I have downloaded the GSI of Android 12 and 11, since I wanna get Android 12 on it. And if it doesn't work, I'll just flash Android 11. Now, I'm aware of the risks involved in this process. It can soft brick my phone or even hard brick. But I don't wanna get the Pixel because this phone does the job smoothly, but un-intuitively due to Samsung's Android skin. I have unlocked the bootloader sucessfully, and yes, that did erase my whole phone. I don't have any data anyway. So, I tried flashing the phone with Odin on my PC. Since i have only a single .img image and Odin only accepts .tar files, I had to convert it to a .tar file. I used ImgToTar to do the job. Now, there are several fields in the app. Specifically, CP, AP, CSC and HOME CSC if I remember the names correctly. Now, i only have one tar file, so where should I put it? And also, I tried putting it in the AP column, and it failed halfway miserably. The phone still worked fine after rebooting though. Now I'm waiting, and I hope someone helps me.