Database Users

People with hardware locked vibrants..

What can we do? I dont want to mess with anything again because i know if anything goes wrong i cant get in to download mode.. But i too want to flash the new roms and gps fixes. Is there anyway to make the hardware buttons unlocked?

Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.

You can root using clockworks and run some of the patch through clockworks too. Try not to use odin unless you really know what you're doing. A lot have odin hang on them. Other than that, you can flash rom using clockworks.
Sent from my SGH-T959 using XDA App

jonathan3579 said:
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
Click to expand...
Click to collapse
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*

TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.

glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
exactly my point. this is what happened to me. but think about this lets say i flash a rom right and you know how sometimes it hangs on the vibrant screen and just stays there. and in order to get it back i am going have to use odin. which i cant.......... so i think i wont mess with anything anymore. Rather just wait for official 2.2 ota update.

Chief Geek said:
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
Click to expand...
Click to collapse
Take it back and do a warranty exchange cause the buttons arent working correctly.

I've never tried it because I could never get Kies to connect to my phone, but isn't there a way to update firmware through Kies? I know the i9000 guys use Kies to upgrade, but I think that's only to get drivers and the updates though. I wish Samsung had a better interface than Odin to flash firmware. It's absolute garbage.

Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????

glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
This is how I got out of "phone to pc"
get into download mode (i went through it manually, as in plug in the phone, and pressing the volume buttons together at the same time)
Connected to ODIN, and by perfect accident, I clicked on "start" without placing ANY files in ANY spots.
This is what I thought "OMG $h!t" Well my phone was already bricked enough, so i just let it run its course through ODIN. My phone magically rebooted, and it booted into the ROM i had installed before I got the "phone to pc" problem.

Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA

demo23019 said:
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
Click to expand...
Click to collapse
The disadvantage is that it is harder (maybe impossible in some situations?) to get into the Download mode if something goes wrong during a ROM update. You can still load custom ROMS but if something goes wrong, you might not be able to get to Download mode to be able to fix it.
I had the phone ! PC screen on mine when I first tried to unsuccessfully flash Vibrant8. Luckily, my Vibrant doesn't seem to be hardware locked and I was able to get back into Download mode and re-flash it with Odin.

I'm able to access download mode with volume keys and i can access recovery mode so i guess im ok
also date on box is 8/27/10

How do you know whether you have a hardware locked Vibrant or not?

No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene

eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I trust what you're saying.. but is there any way to test that out without having an already bricked phone? I want to make sure I can recover my phone before flashing your Vibrant hybrid ROM. So after Step 6 do you get the download mode screen? Or does ODIN now show a COM port and it works, even without the little digger guy?

eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).

johnny12times said:
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
Click to expand...
Click to collapse
Download Mode is controlled by SBL, so if they truly changed anything that would be the cause.
I would think you could target redbend to update the SBL or even boot.bin bml /stl location.. I've not tried this, nor do I need too.. Just tossing options out there for people to try & don't mind risking a brick..
If you can get the SBL / Boot.bin for the Stock to flash via redbend, then this will solve the HW locks.. Now, Regarding my Phone, I can still get into Download Mode however, only by doing the USB trick &/or ADB reboot download.
I can not get into recovery unless I use clockwork Manager or ADB into
By the way, this is not a Hardware Lock issue as the thread states.. Not being able to get into download Mode like described, is a zImage issue & not the SBL / BOOT.bin
just as a FYI.
~Eugene

Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
Click to expand...
Click to collapse
Its happening because you ran a full titanium backup including system data. Yeah, dont do that. Reflash, then reinstall user apps with data, and pick and choose the system ones that are obvious (mms, bluetooth settings, wireless settings, etc.) Then reboot for changes to take effect. When in doubt, dont restore.
Good luck. Although you won't need it if you do what I just told you.
Sent from my SGH-T959 using Tapatalk

Just to share...
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I had the phone!computer bricked Vibrant, and just got my replacement from Asurion (in fact, of the phones in front of me are from Asurion since my original got stolen 2days after it came out ).
On phone1: The original TMO date is 8/12/2010, while the Asurion date is 8/19/2010. Also the ID is GJ/HLP. This one was HW Locked.
On phone2: The original TMO date is 9/2/2010, while the Asurion date is 9/10/2010. Also the ID is SM/HLP. This one doesn't seem to be HW Loocked, I can get into recovery easily, DL Mode ... not so much . Booting with vol+&- gets me into recovery, but booting with just vol- does nothing ...
Any thoughts?

[Tutorial] How To Unbrick your galaxy 3

If your phone doesn’t boot into download mode and you have a black screen after flashing froyo heres how you unbrick it, it worked for me.
Step 1 – Prepare odin with the firmware u want to flash (in my case was I5800XXJPM) and get it ready to go;
Step 2 – Remove battery, SIM and SD card, next connect your galaxy 3 to the computer;
Step 3 – Hold Volume down + Power + Home button at the same time;
Step 4 – Insert the battery and wait a bit;
Step 5 – At this point Odin should have detected your SG3 ( Yellow rectangle should appear in your );
Step 6 – Click Start button in Odin and wait about 5 min.
If all goes well it should come back to life.
If You Find It Useful Click Thanks.

When you said Brick, it's Hardbrick or SoftBrick ?

Darius_AWS said:
When you said Brick, it's Hardbrick or SoftBrick ?
Click to expand...
Click to collapse
"If your phone doesn’t boot into download mode and you have a black screen after flashing froyo" => hard brick...

kyrillos13 said:
"If your phone doesn’t boot into download mode and you have a black screen after flashing froyo" => hard brick...
Click to expand...
Click to collapse
Lestat should try it

dude u shud have made this thread 3 months ago it wud have been very helpfull for me coz it wud save my 2hardbricks......hard luck though for me i got my motherboard chnged both times and the 2nd time they gave me i5800 motherboard but my model is i5801...l...so bloody hell samsung service centres......and i think they have given me a 2nd hand motherboard this time..,.....

Now no need to worry about hard brick. Do What you want to do with Your Samsung devices.
The above tutorial work with every device which support odin firmware flashing.

shreyasharusia said:
Now no need to worry about hard brick. Do What you want to do with Your Samsung devices.
The above tutorial work with every device which support odin firmware flashing.
Click to expand...
Click to collapse
That's a relaxing thought!

You can skip step 3 - after reboot phone WILL go thrue download phase - this is how the bootloader is built. Just connect your phone, switch it on and after you PC Odin detected it push START - that`s it!!!

aarrun said:
dude u shud have made this thread 3 months ago it wud have been very helpfull for me coz it wud save my 2hardbricks......hard luck though for me i got my motherboard chnged both times and the 2nd time they gave me i5800 motherboard but my model is i5801...l...so bloody hell samsung service centres......and i think they have given me a 2nd hand motherboard this time..,.....
Click to expand...
Click to collapse
they always replace with used motherboards....
had to wait one month for them to do that

dude you saved my ass. Thank you so much.

alcsilian said:
dude you saved my ass. Thank you so much.
Click to expand...
Click to collapse
did u really hard bricked and saved by this method?

Does its really working?

Unfortunately it is not working for me... After yesterday's attempting to upgrade to froyo I have a brick... Holding power down, trying enter the download menu, connecting USB cable - nothing happening - black screen. I have tried both methods described above and nothing happened

Hmmmm.... Im sorry if im asking something wihtout trying...
But is it really possible to boot the phone into Download Mode/Recovery/whatever WITHOUT the battery???

jinxskore said:
Hmmmm.... Im sorry if im asking something wihtout trying...
But is it really possible to boot the phone into Download Mode/Recovery/whatever WITHOUT the battery???
Click to expand...
Click to collapse
Who said without the battery. Connect the mobile to computer without battery,press and held both the volume rocker and then insert the battery . You will get the downloading mode and odin will detect your phone and then flash.

shreyasharusia said:
If your phone doesn’t boot into download mode and you have a black screen after flashing froyo heres how you unbrick it, it worked for me.
Step 1 – Prepare odin with the firmware u want to flash (in my case was I5800XXJPM) and get it ready to go;
Step 2 – Remove battery, SIM and SD card, next connect your galaxy 3 to the computer;
Step 3 – Hold Volume down + Power + Home button at the same time;
Step 4 – Insert the battery and wait a bit;
Step 5 – At this point Odin should have detected your SG3 ( Yellow rectangle should appear in your );
Step 6 – Click Start button in Odin and wait about 5 min.
If all goes well it should come back to life.
If You Find It Useful Click Thanks.
Click to expand...
Click to collapse
Im sorry. I dont mean to prove you or anyone wrong. Maybe i just got things wrong...
Step 2 says to remove battery.
Step 3 basically means trying to start the phone into Download Mode.
Step 4 Well, if its only me, i cant imagine Holding Volume Down+Home+Power buttons and manage to insert the battery at the same time.
NOTE: I just asked if something was possible. Not particularly in accordance to your Tut. I just asked a general question. Sorry again if i offended anyone.
EDIT: The main reason was my curiosity, if the phone could work on power from the USB. LoL

i think it powers the phone without the battery through the USB cable from PC. never tried it though but i think it works since the battery charges while plugged in usb cable (this means it has juice).

I think its starting download mode when you put in the battery :S
If you are really that curious as to whether it will enter download mode just on usb power you dont have to wait for your phone to get hard bricked, just try it.

shreyasharusia said:
Now no need to worry about hard brick. Do What you want to do with Your Samsung devices.
The above tutorial work with every device which support odin firmware flashing.
Click to expand...
Click to collapse
same here bro. i too changed my motherboard from samsung service center
and i dont this one is same as the previous one

unfortunately that doesn't work for me... stupidly enough, I tried to change something in the firmware file (just the logo.png file), and then it got stuck during flashing in Odin. So even more stupidly, I disconnected the phone, and when it didn't turn off I just took out the battery, and since then it behaves as a total brick, and doesn't even show any sign of life when I try to turn it on, or when I try the above mentioned methods (Odin doesn't detect anything).
Any other ideas, or things that I may have done wrong trying to revive it? and do you think that the JIG method could work?
thanks

S7 Edge "Bootloader Exception" bug

Hi all,
I've received my S7 Edge today(Exynos), yay.
All was working flawlessly until few moments ago, I was running 3Dmark, and before I even start to bench, while i was downloading the first scene The screen goes all black, then after 10 seconds, there's a message on top (in the same way a rooted phone would display "kernel is not seandroid enforced..."):
Bootloader Exception
[RST_START = 0x100000000 ]
[...]
Exception: do_handler_serror: SERROR(esr: 0xbf00000000)
[...]
I didn't install any rom, root or else, it's pure stock untouched. I tried to reboot phone using volume down+power, it reboots I think (screen goes all black) but quickly the same message appears...
I'm surely going to call phone operator to tell them that phone is KO, but if one of you guys has any idea that would avoid me to send back phone to warranty, it would be nice
Thanks !

@mods : Sorry for posting in wrong section

Try this...
https://www.youtube.com/watch?v=UV0Zp7F1LHs

I'd suggest a factory reset if the above fails.
Hold Power + Volume Up + Menu
Then use the volume keys to scroll to factory reset and select using menu or power buttons.

Hi guys,
Thanks very much for you answers,
Unfortunately any key combination is not working can't get into recovery nor download mode ...
I don't want to try Odin, scared about potential warranty issues ... but it kills me to have to send the phone back to sammy and wait ..

Mr_PoPoP said:
Hi guys,
Thanks very much for you answers,
Unfortunately any key combination is not working can't get into recovery nor download mode ...
I don't want to try Odin, scared about potential warranty issues ... but it kills me to have to send the phone back to sammy and wait ..
Click to expand...
Click to collapse
The phone must be off for the Volume Up + Power + Home button combination to work. Keep those pressed for like 10 seconds, even after the phone powers on. I just tried it on my S7 Edge (which drops every call) and could restore to factory settings (but didn't solve the issue).

Cst79 said:
The phone must be off for the Volume Up + Power + Home button combination to work. Keep those pressed for like 10 seconds, even after the phone powers on. I just tried it on my S7 Edge (which drops every call) and could restore to factory settings (but didn't solve the issue).
Click to expand...
Click to collapse
Thanks for your advices !
Unfortunately, even with this combination and a lot of patience I cannot manage to "bypass" this Bootloader error ...
I'm mad because it will take one month to get a new phone from my operator(just called them ...)
So maybe i'm going to try Odin ... but if I cannot put my phone into download mode, i'm f*ckued, right ?
Here's a photo of the error message :
https://drive.google.com/open?id=0B_3xOO1wyNGMVWl1RUFybTZoM3c

Mr_PoPoP said:
Thanks for your advices !
Unfortunately, even with this combination and a lot of patience I cannot manage to "bypass" this Bootloader error ...
I'm mad because it will take one month to get a new phone from my operator(just called them ...)
So maybe i'm going to try Odin ... but if I cannot put my phone into download mode, i'm f*ckued, right ?
Here's a photo of the error message :
https://drive.google.com/open?id=0B_3xOO1wyNGMVWl1RUFybTZoM3c
Click to expand...
Click to collapse
I'm stumped. I've never seen that before

From where did you order your phone?

thunderroid said:
From where did you order your phone?
Click to expand...
Click to collapse
A french mobile operator , Bouygues Telecom.

Can you do a factory reset from the Settings menu?

thunderroid said:
Can you do a factory reset from the Settings menu?
Click to expand...
Click to collapse
Nope, the phone doesn't boot anymore... it only displays the bootloader error message...
And no possibility to access reboot or recovery...
Maybe I can try to check with ADB, but my problem is that i would need to active USB debugging in settings ... but i can't do that

Return it. Nand flash died.
Sent from my iPad using Tapatalk

Yap, I think you have to return it.

hiepgia said:
Return it. Nand flash died.
Click to expand...
Click to collapse
Yep, I wanted to avoid it, but I don't see other reasonnable option. The phone didn't last more than 24h ... ok, it happens, I know ...
My previous (Still actual (sic)) Phone was a Note 3 and I installed so much roms, soft bricked the device so many times, but I could always restore it ... But not the S7 EDGE ... And I didn't spot any other user with same bootloader issue...
I've just sent back the phone for replacement, Thanks for all who replied to me in this thread
Oh and by the way : don't download 3DMark from play store , it will Hard brick your phone !!! (haha just kidding , i know it's not what caused my phone to die, I'm sure of it , however I won't try to install it anymore i think^^ )
Cheers XDA crew !!

Mine has done just the same. went to bed, woke up this morning and the same message as yourself.

Borgella said:
Mine has done just the same. went to bed, woke up this morning and the same message as yourself.
Click to expand...
Click to collapse
Sorry to hear that bro
Try things to troubleshoot if you wanna, but my advice : don't lose one day of trying to fix it, send it back directly to warranty...
I tried lot of things, key combination to reboot phone in recovery or download, I tried Kies, Odin, ADB....
I believe it's a real samsung bug that will happen to many people, So send it now before sammy is drowned under hard bricked S7 phones and start to have issues to provide replacement devices....

the S7 edge is getting a "urgent" update on approx 3mb..maybe this is a fix of some sort.

johanbiff said:
the S7 edge is getting a "urgent" update on approx 3mb..maybe this is a fix of some sort.
Click to expand...
Click to collapse
That is to correct the Screen Edge sensitivity

For anyone else who runs into this issue, I managed to fix my phone.
Holding the power and VOL down buttons for about 5-10 seconds will reboot the phone; if you hold home at the same time you can get into download mode (might take a couple tries).
From there, you can flash a new bootloader (BL option in odin) and then get back into recovery to do whatever you need to do.
Went from soft-brick to full restore in about ten minutes--not even a factory reset necessary.
Hope this helps!

Went to sleep, phone died, now stuck in a bootloop, can't enter recovery and etc.

Stock 7.0 AT&T model, I went to sleep, forgot to plug in phone. It died in the middle of the night, and the phone refuses to boot past the s7 edge splash screen and restarts every 10-15 seconds. It also will not enter recovery mode and says "Recovery booting..." I can make it enter download mode but I have attempted almost everything I have found and I either get a binary issue or it will successfully flash but then nothing will happen and it will continue to be in this bootloop. I actually brought it to a samsung "representative" at Best buy today and she said it wasn't recognizing the phone at first then it did, and she flashed something that she didn't say what it was and then it still didn't work. She then told me to send it in to samsung but since my glass is cracked (2nd day I had it too...) they try to say that i'm at fault. I just want to know how to fix this, I haven't had my phone in 5 days, I don't care about my data cause it's all already backed up online! Any help would be greatly appreciated.

alecmaw said:
Stock 7.0 AT&T model, I went to sleep, forgot to plug in phone. It died in the middle of the night, and the phone refuses to boot past the s7 edge splash screen and restarts every 10-15 seconds. It also will not enter recovery mode and says "Recovery booting..." I can make it enter download mode but I have attempted almost everything I have found and I either get a binary issue or it will successfully flash but then nothing will happen and it will continue to be in this bootloop. I actually brought it to a samsung "representative" at Best buy today and she said it wasn't recognizing the phone at first then it did, and she flashed something that she didn't say what it was and then it still didn't work. She then told me to send it in to samsung but since my glass is cracked (2nd day I had it too...) they try to say that i'm at fault. I just want to know how to fix this, I haven't had my phone in 5 days, I don't care about my data cause it's all already backed up online! Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using samsung smart switch?

use samsung smart switch emergency software recovery initialization which is in the right up corner in "more". if its gonna be stuck and installing the software then connect your phone to a charger, hold volume down and power button and turn it off, this way the phone should stay turned off. then go to download mode and install s7 edge firmware from sammobile through odin

RomBetaTester said:
Have you tried using samsung smart switch?
Click to expand...
Click to collapse
****, I forgot to mention, yes I have tried smart switch and every time I input the model number and S/N, it just closes out. Based on my research, that means initialisation isn't possible.

arofaz said:
use samsung smart switch emergency software recovery initialization which is in the right up corner in "more". if its gonna be stuck and installing the software then connect your phone to a charger, hold volume down and power button and turn it off, this way the phone should stay turned off. then go to download mode and install s7 edge firmware from sammobile through odin
Click to expand...
Click to collapse
I forgot to mention, that yes I have tried smart switch, and everytime I input the model number and S/N it closes out.

you'll need quick hand play
push volume down boton and power at the same time when the phone restars quick push the download mod conmbinaison and flash a stock at&t firmware you can download throught sammobile.com site;*,
edit : download the firmware throught this post: https://forum.xda-developers.com/att-s7-edge/how-to/firmware-att-s7-edge-g935a-official-t3412312
another edit lol: don't forget to unzip downloaded files
tell me if it works

Recently, I have seen many phones with bootloop problems and, at the end, the sim card was the one to blame.
I know it's silly but have you tried booting it without the sim card and micro sd?

nouninou said:
you'll need quick hand play
push volume down boton and power at the same time when the phone restars quick push the download mod conmbinaison and flash a stock at&t firmware you can download throught sammobile.com site;*,
edit : download the firmware throught this post: https://forum.xda-developers.com/att-s7-edge/how-to/firmware-att-s7-edge-g935a-official-t3412312
another edit lol: don't forget to unzip downloaded files
tell me if it works
Click to expand...
Click to collapse
I keep getting SW REV CHECK FAIL : [ABOUT] FUSED 4 > BINARY 2 and odin fails. this is what has been happening each time I attempt odin. Also Smart switch just closes.

angourakis said:
Recently, I have seen many phones with bootloop problems and, at the end, the sim card was the one to blame.
I know it's silly but have you tried booting it without the sim card and micro sd?
Click to expand...
Click to collapse
Yup, nothing :/

arofaz said:
use samsung smart switch emergency software recovery initialization which is in the right up corner in "more". if its gonna be stuck and installing the software then connect your phone to a charger, hold volume down and power button and turn it off, this way the phone should stay turned off. then go to download mode and install s7 edge firmware from sammobile through odin
Click to expand...
Click to collapse
Smart Switch just closes out each time i input S/N and Model number :/

I just actually successfully flashed SM-G935U firmware but to no avail it is still in this bootloop. I am about to just replace the screen and send into samsung ffs

Tab A 10.1 (SM-T580) can't get to download/odin

I feel really dumb, but I've got a few new Tab A 10.1 SM-T580s for my work, stock ROM, not rooted. I loaded some device management software that allowed me to blacklist the Settings app (my fault for not paying attention to what boxes I was checking).
Where I'm at:
- Devices all bootloop at the 2nd Samsung screen.
- I can get into recovery mode (power + up + home) and have tried all the options. I can't reset to factory because the device management software blocks it.
- I can't get into download mode (power + down + home) no matter what I tried*. Device boots like normal and instead of download shows the 2nd Samsung logo briefly and then the device reboots (power + down soft reset) over and over until I let go. When I let go, the device will re-enter bootloop, unless it's plugged in. If it's plugged in, I get the battery charging icon, then a battery percentage indicator, then I can unplug the device and it will "turn off".
- Tried opening it up and pulling the battery connector and letting it sit for a bit. Did not make a difference.
*Here's the weird thing: I did somehow manage to get one of the devices into download mode, so I know it's possible. Once in download, I Odin'd the stock firmware, booted it back up, and it's been fine since. But for the life of me I can't figure out what magical steps I performed on this one device that I can't replicate on the other 3.
I would greatly appreciate any suggestions as to where to go from here. I'm leaning hard into buying/making a jig, but I'm hoping there's something simple I missed.
Thanks,
Chris

chrisk82 said:
I feel really dumb, but I've got a few new Tab A 10.1 SM-T580s for my work, stock ROM, not rooted. I loaded some device management software that allowed me to blacklist the Settings app (my fault for not paying attention to what boxes I was checking).
Where I'm at:
- Devices all bootloop at the 2nd Samsung screen.
- I can get into recovery mode (power + up + home) and have tried all the options. I can't reset to factory because the device management software blocks it.
- I can't get into download mode (power + down + home) no matter what I tried*. Device boots like normal and instead of download shows the 2nd Samsung logo briefly and then the device reboots (power + down soft reset) over and over until I let go. When I let go, the device will re-enter bootloop, unless it's plugged in. If it's plugged in, I get the battery charging icon, then a battery percentage indicator, then I can unplug the device and it will "turn off".
- Tried opening it up and pulling the battery connector and letting it sit for a bit. Did not make a difference.
*Here's the weird thing: I did somehow manage to get one of the devices into download mode, so I know it's possible. Once in download, I Odin'd the stock firmware, booted it back up, and it's been fine since. But for the life of me I can't figure out what magical steps I performed on this one device that I can't replicate on the other 3.
I would greatly appreciate any suggestions as to where to go from here. I'm leaning hard into buying/making a jig, but I'm hoping there's something simple I missed.
Thanks,
Chris
Click to expand...
Click to collapse
Since the problem is obviously the device management software, contacting their tech support would be my first step. None of us are going to be familiar with their software.

lewmur said:
Since the problem is obviously the device management software, contacting their tech support would be my first step. None of us are going to be familiar with their software.
Click to expand...
Click to collapse
I contacted their support, which is how I found out about the Settings blacklist issue. They said to contact Samsung to get the device reset. Samsung said I'd have to take the device to a retail chain, though it was unclear as to what the retail chain was going to be able to do that I couldn't with a copy of the firmware.
Also, the fact that I was able to get one of the devices un-borked makes me think the device management software shouldn't be blocking download mode, but I can double check with them.
Edit: FWIW, contacted the company (ManageEngine, since I didn't note it before), they said their software should not block the hardware key commands.
Thanks,
Chris

chrisk82 said:
I contacted their support, which is how I found out about the Settings blacklist issue. They said to contact Samsung to get the device reset. Samsung said I'd have to take the device to a retail chain, though it was unclear as to what the retail chain was going to be able to do that I couldn't with a copy of the firmware.
Also, the fact that I was able to get one of the devices un-borked makes me think the device management software shouldn't be blocking download mode, but I can double check with them.
Edit: FWIW, contacted the company (ManageEngine, since I didn't note it before), they said their software should not block the hardware key commands.
Thanks,
Chris
Click to expand...
Click to collapse
Pilot error.
I've never heard of any management software capable of preventing downloading mode.
It's just not possible.
Either you're not holding the buttons in the correct sequence or not holding for long enough.
If you can boot to recovery then just select 'Boot to Bootloader' from the list.

ashyx said:
Pilot error.
I've never heard of any management software capable of preventing downloading mode.
It's just not possible.
Either you're not holding the buttons in the correct sequence or not holding for long enough.
If you can boot to recovery then just select 'Boot to Bootloader' from the list.
Click to expand...
Click to collapse
This was my assumption as well. I did get hold of one of our old tablets (also a SM-T580, but purchased 6 months ago) and it went right in to download mode. Went back to the non-working device with the exact same button sequence, and it just started boot looping again. Even the one that I successfully re-flashed won't go in to download mode, so I'm really beginning to wonder if I got a bad batch.
"Booting to bootloader" just reboots the device as normal.
I found a "Samsung 300K Tool" that's intended to mimic the USB jig trick. Puts the old device straight in to download mode, new devices reboot, no download mode.
Only thing I can think is looking at the build versions, the newer ones are on a different version, so maybe Samsung changed something.
Old one is
Kernel 3.18.14-11346422
Build NRD90M.T580UEU2BQF1
New one is
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
I'll see if I can get anything further out of Samsung support (weren't very helpful first go round, so I won't hold my breath).
Thanks,
Chris

chrisk82 said:
This was my assumption as well. I did get hold of one of our old tablets (also a SM-T580, but purchased 6 months ago) and it went right in to download mode. Went back to the non-working device with the exact same button sequence, and it just started boot looping again. Even the one that I successfully re-flashed won't go in to download mode, so I'm really beginning to wonder if I got a bad batch.
"Booting to bootloader" just reboots the device as normal.
I found a "Samsung 300K Tool" that's intended to mimic the USB jig trick. Puts the old device straight in to download mode, new devices reboot, no download mode.
Only thing I can think is looking at the build versions, the newer ones are on a different version, so maybe Samsung changed something.
Old one is
Kernel 3.18.14-11346422
Build NRD90M.T580UEU2BQF1
New one is
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
I'll see if I can get anything further out of Samsung support (weren't very helpful first go round, so I won't hold my breath).
Thanks,
Chris
Click to expand...
Click to collapse
Hold the 3 buttons in this order and ensure they are firmly pressed. If you fail to hold the HOME button in it will continually reboot.
HOME + VOL DOWN + POWER.
It's best if you can do this from Power off.
When the device starts up hold for another few seconds and then let go.

chrisk82 said:
This was my assumption as well. I did get hold of one of our old tablets (also a SM-T580, but purchased 6 months ago) and it went right in to download mode. Went back to the non-working device with the exact same button sequence, and it just started boot looping again. Even the one that I successfully re-flashed won't go in to download mode, so I'm really beginning to wonder if I got a bad batch.
"Booting to bootloader" just reboots the device as normal.
I found a "Samsung 300K Tool" that's intended to mimic the USB jig trick. Puts the old device straight in to download mode, new devices reboot, no download mode.
Only thing I can think is looking at the build versions, the newer ones are on a different version, so maybe Samsung changed something.
Old one is
Kernel 3.18.14-11346422
Build NRD90M.T580UEU2BQF1
New one is
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
I'll see if I can get anything further out of Samsung support (weren't very helpful first go round, so I won't hold my breath).
Thanks,
Chris
Click to expand...
Click to collapse
It isn't a problem with the build.
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
This is the latest build from Samsung. Mine has that exact same build and it goes to download without any problem. I still say the problem is with the "device management software". THAT is what is different.

I'm confused as to how you are veryfying the builds if the device cannot boot?

ashyx said:
I'm confused as to how you are veryfying the builds if the device cannot boot?
Click to expand...
Click to collapse
The build shows in the recovery screen. But not the kernel version.
---------- Post added at 12:31 PM ---------- Previous post was at 12:28 PM ----------
chrisk82 said:
This was my assumption as well. I did get hold of one of our old tablets (also a SM-T580, but purchased 6 months ago) and it went right in to download mode. Went back to the non-working device with the exact same button sequence, and it just started boot looping again. Even the one that I successfully re-flashed won't go in to download mode, so I'm really beginning to wonder if I got a bad batch.
"Booting to bootloader" just reboots the device as normal.
I found a "Samsung 300K Tool" that's intended to mimic the USB jig trick. Puts the old device straight in to download mode, new devices reboot, no download mode.
Only thing I can think is looking at the build versions, the newer ones are on a different version, so maybe Samsung changed something.
Old one is
Kernel 3.18.14-11346422
Build NRD90M.T580UEU2BQF1
New one is
Kernel 3.18.14-12479655
Build NRD90M.T580UEU2BQL1
I'll see if I can get anything further out of Samsung support (weren't very helpful first go round, so I won't hold my breath).
Thanks,
Chris
Click to expand...
Click to collapse
Does the "Update from ADB" option work in recovery? If so, you could extract the image files from the .tar file and use ADB to flash them individually.

lewmur said:
Does the "Update from ADB" option work in recovery? If so, you could extract the image files from the .tar file and use ADB to flash them individually.
Click to expand...
Click to collapse
It doesn't work like that. Update zip packages are signed.
For that to even have a chance you need to catch the OTA.

ashyx said:
Hold the 3 buttons in this order and ensure they are firmly pressed. If you fail to hold the HOME button in it will continually reboot.
HOME + VOL DOWN + POWER.
It's best if you can do this from Power off.
When the device starts up hold for another few seconds and then let go.
Click to expand...
Click to collapse
Tried this from a device with a dead battery charged up to over 20% (maybe needs more?), still boots up to normal Samsung start screen and loop.
ashyx said:
I'm confused as to how you are veryfying the builds if the device cannot boot?
Click to expand...
Click to collapse
I'm using the build and kernel off the one device I was able to reflash (which has rebooted unexpectedly a few times now, so that's concerning). I suppose it's not a safe assumption they're the same as the boot-loopers.
lewmur said:
Does the "Update from ADB" option work in recovery? If so, you could extract the image files from the .tar file and use ADB to flash them individually.
Click to expand...
Click to collapse
It does, and I did try that route, but as was noted, it doesn't validate the zip as signed. I'd assume the same result if I loaded the zip off the SD Card. And since that option mounts ADB in sideload only, I can't do much else with it.
I've re-contacted Samsung, and they insist that if I take them to the local Best Buy, there's a Samsung tech there that can get them working. So I'll take the devices there, and report back what I find out. I'm highly skeptical, but we'll see.
Thanks again for all the suggestions and help.
Chris

A quick update:
Took the tablets to the nearest local Best Buy, they looked at me like I had horns when I said Samsung sent me there. Of course, the Samsung rep (who everybody assumed was just a sales rep) was only there on weekends. So maybe others would have had better luck.
In this case, with them still under warranty, I called Samsung back and got them shipped out to a repair center to be flashed by Samsung.
So no clear answer one way or the other, I'm still a bit skeptical of the device management software preventing the download keys, but who knows. Hopefully they'll be back from Samsung shortly all shiny and new and I can try again (make sure to not disable factory reset in the future, I guess).
Chris

Just to final update:
Utilmately, lewmur was correct.
Devices came back from Samsung with their main boards replaced and I was able to get in to download mode...until I put the device management software on them. I re-contacted ManageEngine support, got a different person, and they pointed to a security setting called "Safe Mode" that their software provides that only applies to Samsung devices to prevent ODIN mode. Sorry to have wasted everybody's time on my not understand the software, but thanks again for the suggestions.
Chris