Database Develop

[Q] Captivate Boot Loader Brick?

Hi Everyone,
I had previously been running the stock I9000 JK3 ROM on my Captivate with xcal's reoriented kernel. Today I decided to install the I9000 JL2 Rom from samfirmware.com.
I started ODIN, entered Download Mode, and flashed the ROM (in the PDA section) with no problem. After the flash had completed, the phone attempted to reboot, but there was nothing but a black screen. I tried every way I know to get into Download mode but nothing works. I don't even get the Phone--!--Computer image that I've gotten in the past when I've messed up a flash.
I've read that this kind of brick occurs when the boot loader is corrupted, and that the only way to fix it is to use a RIFF JTAG box. My question is: what did I do wrong? I flashed many ROMs before, all through ODIN, but was always able to get back to stock if necessary.
My research suggests that it has something to do with sbl.bin. Can someone enlighten me? How can I tell if a ROM will mess up my bootloader? Do ROMs that mess up bootloaders contain the sbl.bin file?
Any advice or information would be greatly appreciated.

If your getting the phone / computer screen you should still be able to restore.
Use the following method to get into DOWNLOAD mode and then Odin 1 click back to stock.
Take out the battery,SIM, and external SDCard
Turn on Odin JH7 1 Click Back to Stock
Plug in your USB cable
While holding down the Volume +/- Button place the batter back in.
If you get the gray battery charging signal - you need to attempt it again. Should go into DOWNLOAD mode and you can restore your phone back to stock.
The SBL.bin is bad mojo if you fubar it as it has important things like being able to use your buttons to get into the different modes (download/recovery). I don't know what else it controls as I'm not a developer.

Also read this on the General thread: http://forum.xda-developers.com/showthread.php?t=775911
interesting stuff about the SBL.bin - so Flashers beware!

Thank you so much for the information. Unfortunately, I do not see the Phone--!--Computer icon, and I confirmed that the ROM that was flashed did indeed contain an SBL.bin file. The boot loader is most certainly bricked.
I really think a warning about the SBL.bin file should be stickied somewhere prominent, so other people don't make the same mistake that I did.
Thanks Again

It works for me
avgjoegeek said:
If your getting the phone / computer screen you should still be able to restore.
Use the following method to get into DOWNLOAD mode and then Odin 1 click back to stock.
Take out the battery,SIM, and external SDCard
Turn on Odin JH7 1 Click Back to Stock
Plug in your USB cable
While holding down the Volume +/- Button place the batter back in.
If you get the gray battery charging signal - you need to attempt it again. Should go into DOWNLOAD mode and you can restore your phone back to stock.
The SBL.bin is bad mojo if you fubar it as it has important things like being able to use your buttons to get into the different modes (download/recovery). I don't know what else it controls as I'm not a developer.
Click to expand...
Click to collapse
Wow it works for my captivate, after a failed odin update the captivate was death black screen at all, with these procedure I can reflash with odin. thanks a lot.

after i got a soft brick with odin, all i used since were one click .jar's made for my phone.

bricked help

hey, i am posting this for a friend who bricked his phone and doesn't know much about it..
he was running serendipity 7 which is a jvo rom, and tried flashing the pauldiddy remix theme, which says is only meant for jvp and jvq roms. i used a jig, to get the phone into download mode, and the computer detected it when i plugged in the usb. but when i tried to use odin one click to go back to stock, it would get stuck at the "Do not turn off target". im not sure if anyone knows a fix for this, or if i should try using the method from this thread http://forum.xda-developers.com/showthread.php?t=1153310 instead, but i figured i would ask before i messed around with it too much
any feedback would be appreciated

how long do you wait before throwing in the towel? it does take a minute or two to finish it's task ? And are you opening Odin before you hook the usb to the phone ?

waited probably about 5-10 minutes. yeah i opened odin first, and it detected the phone and showed the Added! text

Just out of curiosity, what is the phone doing right now that you're trying to use Odin on it?
The reason I ask is that if you can get to CWM recovery, you might just be able to re-flash the rom (assuming it's a wipe package) and it would take care of the issue.

i cant get into recovery, but i can get into download (using the button combos). not sure if that means anything either

Well keep trying, and you might want to try the odin 1 click. I have a Cappy that got dipped in the pool, it would not go into recovery at all but I could get the download all the time, But it kept getting stuck at the i896 screen or the AT&T screen (odin 1 click) after 3 weeks of trying and having to wait 3 days for it to come out of it's coma it now works fine. If you try the odin 1 click it might work for you just make sure it's not ver 10.10 I think (look under battery). What screen does it go to once you press power IE: black screen rogers screen etc. ?

ive tried using odin 1 click.. like i said, the first time odin actually picked up the device, but it wouldnt get past the "do not turn target off" prompt. but i tried plugging it in again, and now it doesnt seem to even pickup the phone. when i when i try to boot the phone, its just a black screen. thanks for the input though

[Q] Have I ruined my in law's phone? Can anyone help me please?

My father in law bought a new phone SGS on O2 and I offered to unlock it as I have unlocked my husbands last week (he's was on O2 as well but in 2.1 or 2.2.1 version I think-froyo?)
Before I continue may I say I know you guys out there know so much more than me and I really need your help. I really tried to help unlocking this phone and for hours I searched and read things like reboot, download mode, recovery mode, flashing, JKV and so many other words and letter that I could not understand. Very few I understood in the end but may have messed up badly (?).
Please, I need help and please treat me as if I were your mum or even grandma. Step by step in simple normal English please.
My father in law's version is 2.3.3
I tried unlocking it the way I unlocked my husband's but didn't work. After looking for hours I thought that the best way to do it would be to downgrade from 2.3.3 (gingerbread (?)) to 2.2.1 (froyo (?)) and then unlock it.
I found this:
http://forum.xda-developers.com/showthread.php?t=1089989
and tried to follow it.
I downloaded EZRom and EZboot-Froyo-1.0.tar.md5 from the same post.
I followed:
•Download the right version from section above
•Reboot your phone into Download mode
•Connect your phone to computer
•Run EZOdin
•Select EZboot-Froyo-1.0.tar.md5 or EZboot-GingerBread-1.0.tar.md5as a PDA file in EZOdin
•Check the "Phone Bootloader Update" checkbox
•Click Start
I waited for the phone to turn off and feel the little vibration but didn't. Instead it just froze at the first screen when you turn on the phone. The black background with white letters: Samsung Galaxy...
I waited and waited and as nothing was happening I then I took the battery out. Put it back in and tried turning it on. I wouldn't it would just stop and that same screen, the black and white one.
I reread
•Wait until phone reboots and make it reboot into Recovery
SO then I remembered in the many threads I read about the recovery mode so 3 clicked vol up + button at them bottom and turn on bottom.
It gives me a few options. When I click on reboot all it does is show me the black and white screen again and nothing else. ah!!!
I took the battery off and put it back on many times, I also selected the fatory reset option and tried different buttons but nothing. Please help me.
I'm happy to phone any of you guys to help me and guide me even if it's just to put the phone back to what it was before, turning on normally, etc. I'm feeling really sad and a bit stressed as these days are supposed to be a nice time to spend with my little ones and family.
Anyway, please ask me anything.
Thank you so much in advance. I really hope I didn't do anything wrong and I'm just stuck because I'm ignorant in this matter. Thank you

I was never a fan of EZ-stuff.
That said, think you can easily solve that flashing your phone with odin and a proper rom. At this point i am unclear about what bootloaders you have on your phone since you've tried a downgrade.
Without getting into further details (sorry, at work atm). You can get tutorials easy for all of this around this forum.
I'd get Odin, get a proper stock rom from samfirmware with bootloaders included and flash it fresh from start with that. Doesn't really matter if it's froyo or ginger as long as it includes bootloaders.
You'll be left with a working phone at this point.
From here, if you still want to try to unlock it, i'd flash a kernell that would get me root (like the ChainFire one) since i find this the safest and easiest way of getting root on your phone and do a backup of your EFS partition (preferably saved in your computer or wherever outside your phone). This is very important, if you lose of mess up with this part of your phone it will be a pain.
Now, there are several ways of unlocking this phone, the only one i found to be most reliable (but not the easiest one) is to manually edit the nv_data.bin file (located in your EFS partition in hexadecimal.
There's a tut right here
http://forum.xda-developers.com/showthread.php?t=761045&highlight=unlock

Thank you so much for taking the time to reply although you are working!!! Really appreciate it.
I'll try your suggestion but I don't know how to choose the right stock rom with bootloader from samfirmware. I went to the website and registered but don't really know what to do.
I know you are working so might not be able to help me, may be someone else?
Here's where I am. Update. I found a list of firmware. This is the last one on Samfirmware.com.
Europe Samsung I9000 Firmwares.
I9000XXJVS ##
512.PIT
2.3.5
2011 September 8
CSC = I9000OXAJVS
DOWNLOAD
Things I need: (I think)
-Download a firmware (should I use the lastest one?) or 2.2 or 2.3.3? . Is there one better than the other? or is it my choice? How can I choose the best one for me?
-Odin. I have OdinMultiDownloader v4.03 in my desktop. Is that the best thing to use or should I use Ezodin. I don't know what the difference is.
-(Do I need to download or do anything else?)
Things I should do:
-Put phone in download mode
-Plug it to the laptop
-Open Odin (or Exodin?)
-click PDA. Choose the fie I downloaded-firmware.
(-after this I don't know what else I should do or tick or untick)
Am I in the right track or completely off it?
Thank you again to anyone taking the time to read this.

Download Jvt From sammobile. com, you need Odin on your PC (1.7 or 1.8) plus Samsung drivers. Read there flashing guides carefully, check you have download
Mode, battery charged > 50% etc
There is also a video on youtube which shows you how to upgrade to jvt.
Sent using TCP/IP

Sounds like you've got the boot-loop problem, which means that you most likely "soft-bricked" the phone. Don't worry, this isn't that big of a deal and can be fixed with relative ease. I agree with the posters above, a clean flash with Odin will probably fix your problem and get you out of the boot-loop.
I'll go into a bit more detail with some steps (feel free to correct me if I missed anything)
1. Download Odin 1.85 here.
2. Head over to Samfirmware.com and grab the latest firmware for the phone. I recommend Gingerbread 2.3.5 (JVT).
3. Make sure your computer has the proper drivers installed so it can communicate with your Samsung Galaxy GT-I9000. If you've flashed the phone before with your computer then you probably have the drivers installed, but here's a link for them just in case: Samsung USB Drivers
4. Enter download mode on your phone, depending on your firmware, it could be Vol down + power + home OR Vol up + power + home. Pull the battery out, pop it back in, and hold those three buttons until the phone turns on.
If you can't enter download mode with the 3-button hold method, then you might have to do so via ADB with the command "reboot download".
Getting into download mode is pretty critical, as you cannot progress further without it.
5. Once you're in download mode (should see a triangle with an Android shoveling stuff in it), plug your phone into your computer's USB port and open Odin. In Odin, press "Reset" on the right hand side. Odin should be able to detect your phone (this is indicated by a yellow box on the left side). I'm using a PC, so inside the yellow box I see something like this: 0:[COM9]. On a Mac it probably says something different, but as long as you see the yellow box appear then it's all good.
If you don't see the yellow box, then there's no communication between your phone and the computer, which means that you may have to reinstall the Samsung USB drivers.
6. With the contents in the firmware package that you downloaded from Samfirmware.com extracted, load them onto Odin accordingly.
PIT: use s1_odin_20100512.pit
PDA: JVT (sometimes the PDA is labeled CODE instead)
PHONE: JVT (sometimes labeled as MODEM instead)
CSC: use HOME-MULTI-OXAJVT (should be about 9.5 MB in size)
Since your father-in-law's phone was originally 2.3.3, you shouldn't have to alter the bootloader with Odin, so leave the bootloader field empty.
7. Once you've loaded up all the necessary files, make sure Re-partition and Auto-reboot is checked. Leave the rest of the checkboxes as it.
8. Press Start. This should initialize the flashing of the new firmware. After the phone has been flashed, it should reboot automatically and should hopefully be able to get past the Galaxy S black and white logo (aka. boot loop).
9. The phone should be in working order now. I used this method to unlock my SGS: SIM Unlock on the SGS. With this method, your phone needs to be rooted, so head on over to ChainFire's thread here to install his kernal which is already rooted.
Flashing firmware can be pretty scary since nobody wants to end up with a brick that costed $400 and it seems like so much can go wrong, but hopefully the steps I've provided helped. Good luck!

[Q] Completely dead N7000. Hardbrick I think.

Howdy there.
First off, this is not "just another bricked Note thread".
I got this thing from a friend who did not have a clue what he did with it, but he told me he tried to "root it or something" He didn't have any files left, or any memory what he used.
I have for weeks tried every single trick in the book, followed every tutorial, and it shows no sign of coming to life any time soon.
When I got it, it just got stuck on the Samsung flash screen. I couldn't get into any sort of recovery, but I got into download mode, so I tried reflashing the stock firmware with ODIN, but it got stuck on NAND WRITE START for 2 hours, and then failed. All Kies processes were killed, I double checked.
After that, it only shows the "Firmware update failed, start emergency recovery mode in kies"
Kies does not support initialization for N7000, doubted it would have worked anyways.
After this, I went on to read about the brick bug for N7000
Since then I have tried repartitioning the device with all kinds of pit files, I have tried installing about 20 different firmwares, I have tried installing just a kernel, both stock and others, and NOTHING works.
Some pit files get stuck in DO NOT TURN OFF DEVICE for 6-24 hours, until I have disconnected or battery has run out, and some fail by themselves after 20 minutes.
Firmwares get stuck at NAND WRITE START, and fail after about an hour
Kernels fill up the bar with the green dots showing it's doing something but as soon as the log says "NAND Write Start" it gets stuck.
Is there ANYTHING still worth testing, before throwing it in the well? I will not go to a service center and pay to fix a spare phone that will lay in a box until I MIGHT need it some day.
It doesn't matter if my storage space goes down to only 500mb space with some sort of repartitioning, nothing matters. I just want it to run.
I do not have any recovery, and I haven't successfully installed any,
Basically the only thing I can do, is get to Download mode, and the only program so far finding it is ODIN.
I am very thankful for any help, and don't hesitate checking if I forgot something very basic, I might just as well have forgot something very important, but I feel I have tried everything.
Thank you!
-Jimi

It is exactly this: just another bricked Note thread.

ThaiDai said:
It is exactly this: just another bricked Note thread.
Click to expand...
Click to collapse
Well, okay then. Thanks for clearing that up.
I just figured that it's something worse since NOTHING works, hence the "not just another" meaning "not just the same as the others". Atleast I thought it meant that. Perhaps my English isn't so good. Oh well.
I have read dozens of other threads about this where people have been able to get into recovery mode, repartition, or flash a new kernel, or at least SOMETHING, but mine just blocks everything.
-Jimi

Okay then, let's simplify the question/request.
Is there ANY way at all to scan or/and repartition my emmc?
WITHOUT a recovery.
WITHOUT it accepting anything through ODIN, not even the standard pit file, or any of the custom ones I have tried from another thread.
WITHOUT adb.
I can only get to Download Mode.
Heimdall seemed to understand my phone a bit, but couldn't flash anything.
Kernels got stuck at 100%
Factoryfs got stuck at 4%
Recovery got an error "finishing the packet" or something.
Could I use Heimdall to scan or repartition my emmc maybe?

If you are unable to Odin flash a recovery or stock rom then there's no other way. If you found other methods but is still unsuccessful then your phone is dead anyways.

I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.

nokiamodeln91 said:
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
Click to expand...
Click to collapse
Nah, I think the memory is broken.
I have only tested with odin 1.75, but on 3 different PCs
My laptop with Win 8.1
My old computer with XP
And my work computer with Win 7 home
Still, I do not want to give up!
In my frustration I started to flash everything and anything that just had a N7000 tag on it, and somehow somewhere something happened.
I do not have the "firmware failed, use kies recovery" message anymore.
I am instead getting the Samsung splash screen, but it freezes there, I can't do anything.
And also, if my device is off, I can charge it! The battery shows up, but then it freezes with the circle in it before it fills with green to show how much it is charged, but now it atleast accepts charge. Before it didn't.
But I still wonder if I could not scan and repartition my phone with anything else than recovery mode? Perhaps I could flash a repartitioned custom Pit file with Odin if I could just scan it somehow?

I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.

froyoguy said:
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
Click to expand...
Click to collapse
Which rom was this?

AutumQueen92 said:
Which rom was this?
Click to expand...
Click to collapse
Thanks for your reply. Couldn't check it until last night. I was running NightOwl when this happened. Last night, I thought something and flashed the same Philz recovery through Odin and some how it worked.
I have started realizing that it is a hardware issue, since the device does not start without being connected to a power source. 1 out of 20 tries take me into recovery (of course while the device is connected to the charger, or else the screen is always black).
However, the recovery doesn't stay too long. I tried flashing a newer version of NightOwl, but while the recovery is still opening the package, the phone restarts .
One weird thing is that the phone doesn't starts without being connected to the PC or the charger. But when connected, within seconds, the offline charging screen says 100%, which is making me believe something is wrong with the hardware.

Part of the "hardware" is your battery...

Unusual Boot Loop - No Recovery, Odin Flash Appears to Succeed but Doesnt Fix Loop

Hello,
For the past few days I've been reading up on XDA and other forums to attempt to solve my boot loop issue. I'm hoping this forum can help me.
Hardware/Locale:
AT&T S6 Edge (USA)
Android 5.1.1, Stock
G925AUCU3BOJ7 firmware version
Issue:
At some point after completing a call using a paired Bluetooth device, the phone entered and remains stuck in a boot loop, exhibiting the following behaviors:
Phone powers on when plugged in to either phone or wall outlet
Upon power on, phone attempts to boot, getting as far as the Samsung Galaxy S6 Edge screen (NOT the Samsung logo screen)
After a few seconds, the phone reboots, and repeats the pattern
No LED lights activated on the phone; no "Blue" LED, or other colors, flash at any time
...with complications/other factors:
Cannot access Recovery - pressing the standard combination of buttons (Power-Home-VolumeUp) at any/all points in the process fails to start recovery; tested procedures on my spouse's identical S6 Edge with identical firmware, and was able to start Recovery
Cannot access Safe Mode - pressing the standard combination of buttons does not cause the phone to enter Safe Mode
EDIT:
Tried Kies - claims device is Unsupported.
EDIT:
Tried Smart Switch - claims device is Unsupported.
Fixes Attempted:
Discharge the phone completely and try again - No effect; problem remains
Charge the phone using a different wall charger, USB cable, or even laptop as power source - No effect; problem remains
Boot to Download Mode and flash G925AUCU3BOJ7 stock firmware obtained from XDA in combinations of 1) Just AP, 2) AP + BL, and 3) AP, BL, CP, and CSC - Appears to flash successfully, based on ODIN behavior, but No effect; problem remains
Boot to Download Mode and try previous versions of stock firmware for my device obtained from XDA - Same behavior as above
Were there not currently a blizzard raging outside my house, I'd drive over to the AT&T store and ask for help. But there's that whole blizzard thing. Not going anywhere.
Any ideas?

wmbutler said:
Hello,
For the past few days I've been reading up on XDA and other forums to attempt to solve my boot loop issue. I'm hoping this forum can help me.
Hardware/Locale:
AT&T S6 Edge (USA)
Android 5.1.1, Stock
G925AUCU3BOJ7 firmware version
Issue:
At some point after completing a call using a paired Bluetooth device, the phone entered and remains stuck in a boot loop, exhibiting the following behaviors:
Phone powers on when plugged in to either phone or wall outlet
Upon power on, phone attempts to boot, getting as far as the Samsung Galaxy S6 Edge screen (NOT the Samsung logo screen)
After a few seconds, the phone reboots, and repeats the pattern
No LED lights activated on the phone; no "Blue" LED, or other colors, flash at any time
...with complications/other factors:
Cannot access Recovery - pressing the standard combination of buttons (Power-Home-VolumeUp) at any/all points in the process fails to start recovery; tested procedures on my spouse's identical S6 Edge with identical firmware, and was able to start Recovery
Cannot access Safe Mode - pressing the standard combination of buttons does not cause the phone to enter Safe Mode
EDIT:
Tried Kies - claims device is Unsupported.
EDIT:
Tried Smart Switch - claims device is Unsupported.
Fixes Attempted:
Discharge the phone completely and try again - No effect; problem remains
Charge the phone using a different wall charger, USB cable, or even laptop as power source - No effect; problem remains
Boot to Download Mode and flash G925AUCU3BOJ7 stock firmware obtained from XDA in combinations of 1) Just AP, 2) AP + BL, and 3) AP, BL, CP, and CSC - Appears to flash successfully, based on ODIN behavior, but No effect; problem remains
Boot to Download Mode and try previous versions of stock firmware for my device obtained from XDA - Same behavior as above
Were there not currently a blizzard raging outside my house, I'd drive over to the AT&T store and ask for help. But there's that whole blizzard thing. Not going anywhere.
Any ideas?
Click to expand...
Click to collapse
Wish i Could Help..anyways found an article
http://thedroidguy.com/2015/09/gala...n-download-mode-other-charging-issues-1049588

Hi. Did you find the solution / explanation for this situation?

Same problem
facing the same problem, did you find any solution. please help me out.

same thing happened to mine on Jan 2. Phone did its usual all night charge (so was fully charged). I used it a little that morning to check facebook etc. Laid it down, that afternoon needed to make a phone call, hit the power button and now i'm in this loop. ATT was ZERO help. To add, i have red and black lines as my background (which is usually just black) when booting up. I have done all the things you have and phone continues to cycle. This phone has been an absolute piece of poo poo. The laminate started to peel off the front at one of the corners. I keep my phone in a case and don't drop it or haven't in a long time. The camera lens is cracked, so is my sons. You can't root it. Now this...i will never own another samsung product again. I moved back to my son's old htc one ( i gave mine away ...stoopid me). This morning it had a software update (it hasn't been on in 1.5 years) so I said yes. Now it won't boot. GRRR!!!! Keep us posted. I'll do same if I figure it out.
Edit: meant to add, my blue light stays on until eventual total power drain.

Same issue
Hi Guys,
I'm facing the same issue. I tried re-flashing different roms, odin says success but i'm stuck with bootloop. I can go into only download mode, no recovery, no hard reset. I visited the samsung service center and they said that they can't help since KNOX counter is tripped: 1 (0x0500) . Were you guys able to fix this issue. ?
If anyone has a solution please share it here.

stuck in bootloop also
I am having the same problems as you guys for the last 4 days, it doesn't go into recovery mode, only thing it does is go into ODIN mode ,I have also tried flashing the stock firmware through ODIN and it passes but it's still stuck in a boot loop. Please let me know if one of you guys fixed your phone.

its same here anybody can show a guide how to fix this or jtag needed ? or need to return service?

Hi
same problem for me...

same here tired many things and cannot boot nor in recovery

Facing the same issue with my s6 edge. No safe mode, no recovery, just download mode. Also did what everyone else did. Installed the latest ROM for it. Odin looked quite happy with itself for passing the download successfully, but in my case, the phone doesn't boot loop, it just stays on the S6 edge startup screen and doesn't budge until I unplug it. Doesn't appear that the battery is charging either, even though a new one was installed recently, so I am at a loss as to what needs to be done to fix this thing and apparently so is everyone else. Hope we get some answers soon!

Any update on this issue? I assume no other solution than replacing the motherboard has been found. This phone has been only trouble for me...

gunmoule said:
Any update on this issue? I assume no other solution than replacing the motherboard has been found. This phone has been only trouble for me...
Click to expand...
Click to collapse
Apparently not! I guess that seems to be where I'm headed too, but not until the prices of motherboards come down. On ebay I'm still seeing working mobos for around $100. In my opinion, that's way to much for a phone this old.

Viking8 said:
Facing the same issue with my s6 edge. No safe mode, no recovery, just download mode. Also did what everyone else did. Installed the latest ROM for it. Odin looked quite happy with itself for passing the download successfully, but in my case, the phone doesn't boot loop, it just stays on the S6 edge startup screen and doesn't budge until I unplug it. Doesn't appear that the battery is charging either, even though a new one was installed recently, so I am at a loss as to what needs to be done to fix this thing and apparently so is everyone else. Hope we get some answers soon!
Click to expand...
Click to collapse
I used Heimdall. Download any stock rom preferably the higher version from installed rom. Unpack all the DOT.tar.DOT.md5 get the full image at least : sboot.bin system.img recovery.img boot.img param.bin flash it on download mode:
Code:
$ heimdall flash --BOOTLOADER sboot.bin --PARAM param.bin --RECOVERY recovery.img --SYSTEM system.img --BOOT boot.img
if the room version is higher, flashing bootloader is mandatory, if the rom version at the same level bootloader not neccessary. Modem is not neccessary but optional can also flash.

x1123 said:
I used Heimdall. Download any stock rom preferably the higher version from installed rom. Unpack all the DOT.tar.DOT.md5 get the full image at least : sboot.bin system.img recovery.img boot.img param.bin flash it on download mode:
Code:
$ heimdall flash --BOOTLOADER sboot.bin --PARAM param.bin --RECOVERY recovery.img --SYSTEM system.img --BOOT boot.img
if the room version is higher, flashing bootloader is mandatory, if the rom version at the same level bootloader not neccessary. Modem is not neccessary but optional can also flash.
Click to expand...
Click to collapse
I tried through the GUI of Heimdall, but it never actually flashes anything. It says it's "Beginning Session....." waits for a couple minutes and then releases the device. The SM-G925T I have has these files in the tar file when unpacked.
boot.img
cache.img
cm.bin
modem.bin
recovery.img
sboot.bin
system.img
Could you show me what the syntax would look like in the CMD for these files?
Ex. $ heimdall flash --BOOTLOADER sboot.bin --RECOVERY recovery.img --SYSTEM system.img --BOOT boot.img etc. etc.
Clayton
NEW INFO:
I tried to flash just the recovery to see if it would install, but Heimdall in the cmd does the same thing as the GUI.
Initializing connection....
Detecting device....
Claiming interface....
Setting up interface....
Initializing protocol....
ERROR: Failed to send data! Releasing device interface....
MORE INFO: (About 30 minutes later)
I tried a different version of ODIN, (3.10) and I was able to successfully load G925TUVS6FRC1_G925TTMB6FRC1_G925TUVS6FRC1_HOME.tar, but it just sits at the Samsung Galaxy S6 Edge screen forever like it did before. Not sure what to do at this point. Any other suggestions would be welcomed!