Develop Bugs

***Emergency Thread*** Here To Help!

I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!

In case of emergency!

Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?

Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2

...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.

Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app

lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.

Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.

I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.

heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download

Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.

Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!

frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2

Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!

frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2

Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing

Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!

http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?

Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)

ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2

expert . please help .phone is brick

http://forum.xda-developers.com/showthread.php?t=2217296
i just buy a phone samsung note II few days ago and tried to unlock it but i make a miss galaxy note II ---------------SGH-I317M
1st i didnt made the backup
2nd maybe i install the wrong flash or firmware
so the phone is stuck on a black screen and just samsung logo
it can boot on downloud mode and the clock mode
i use the kies but still have the same problem .system cant mount <invalid argument >
efs cant mount system
cant mount data
cant mount sdcard
even .. i install the stuck rom from rogers
i found the kernel and used the Odin
no thing happens
and were lookig to ---------------PIT------File
to repartion might help
please guys and help

Hi. Ok so once your bootlooped yer pretty much borked.
So you can get into download mode?
I want to be sure you know how and what this is. Sorry if you take this the wrong way but your english is a bit scattered.
Ok dl mode: hold the home, power and volume down all at the same time.
There is no other way to achieve this other than a jig or possibly adb, that idk.
If you can get into dl mode your golden.
If kies isnt helping youre doing it wrong.
Odin is an option but lets try this first.
Please, dont get mad if you feel you tried this before.
First, re download thevusb drivers from samsung. "I already did that!"... trust me,
Do it again unless you are 1000000% sure they are current. Even then, uninstall and dl again to be safe.
Next get the current kies software.
Seems like you got this, but again make sure its the latest version.
So lets double check something.
Try again for ****s and giggles to get into recovery. Press the power, home and volume UP buttons all at the same time.
I know you know this has to be done when the phone is powered off.
We just want to see if your recovery is corrupted or not.
If you can get into recovery just do a factory reset.
This may or may not work.
Its ok.
Ok if it fails back to dl mode.
When you get to dl mode start kies.
Kies aint gonna do nothing but lag and hang if your phone and or recovery is fragged.
Youll need to go to the drop down menu in kies and choose:
"emergency firmware recovery"
its gonna ask you for phone model and such. Its then going to say
Plug your phone in or we it says
Put your phone in dl mode:
After you did the pwr, vol dwn, and home key, it brings you to a screen that says
Push up to cancel down to enter dl mode.
Again dont take offense if you know this.
Connectvyour phone to the pc and push the down button.
Give it time. This process can take upbto 20 min.
Once its done you shoyld now have a completly stock phone.
I highly recomend you remove your sd card for this.
Post back with results.
You can also try Odin.
Youll still need the latest samsung drivers.
Youll need the latest stock rom to flash.
Im sure others will chime in .
Good luck and post back

freakboy13 said:
Hi. Ok so once your bootlooped yer pretty much borked.
So you can get into download mode?
I want to be sure you know how and what this is. Sorry if you take this the wrong way but your english is a bit scattered.
Ok dl mode: hold the home, power and volume down all at the same time.
There is no other way to achieve this other than a jig or possibly adb, that idk.
If you can get into dl mode your golden.
If kies isnt helping youre doing it wrong.
Odin is an option but lets try this first.
Please, dont get mad if you feel you tried this before.
First, re download thevusb drivers from samsung. "I already did that!"... trust me,
Do it again unless you are 1000000% sure they are current. Even then, uninstall and dl again to be safe.
Next get the current kies software.
Seems like you got this, but again make sure its the latest version.
So lets double check something.
Try again for ****s and giggles to get into recovery. Press the power, home and volume UP buttons all at the same time.
I know you know this has to be done when the phone is powered off.
We just want to see if your recovery is corrupted or not.
If you can get into recovery just do a factory reset.
This may or may not work.
Its ok.
Ok if it fails back to dl mode.
When you get to dl mode start kies.
Kies aint gonna do nothing but lag and hang if your phone and or recovery is fragged.
Youll need to go to the drop down menu in kies and choose:
"emergency firmware recovery"
its gonna ask you for phone model and such. Its then going to say
Plug your phone in or we it says
Put your phone in dl mode:
After you did the pwr, vol dwn, and home key, it brings you to a screen that says
Push up to cancel down to enter dl mode.
Again dont take offense if you know this.
Connectvyour phone to the pc and push the down button.
Give it time. This process can take upbto 20 min.
Once its done you shoyld now have a completly stock phone.
I highly recomend you remove your sd card for this.
Post back with results.
You can also try Odin.
Youll still need the latest samsung drivers.
Youll need the latest stock rom to flash.
Im sure others will chime in .
Good luck and post back
Click to expand...
Click to collapse
+1
You told him everything that he needed to do bro.:thumbup::thumbup:
And yes his/her English is broken.. Lol
But this also may help him out:
http://www.sammobile.com/firmwares/1/
http://www.sammobile.com/kies/
http://m.samsung.com/us/support/
Note: phone is soft bricked when it's still coming on. When it's completely dead, blank, Chaput, NADA, it's confirmed hard bricked!!! :banghead:
Just my 2¢®
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2

Hope you fix that phone.what an expensive paper weight that'll be.
Sent from my SAMSUNG-SGH-I317 using xda premium

read ur mesage and thanks for giving me time
i buy the phone from a friend who win from radio station
the phone was locked with roger and i was trying ODIN to downloud wind i guess cause i think that i could do it
i dont knw what i did just the phone suddely start on samsung
i have Kies program and i just made firm upgarde and initialization
the ask 4 phone model and serial number
i removed batery restart in download mode and e software installed into the phone
but the phone even didnt started
it say :
E: failed to mount system <invaled argument>
E; cant mount/ sys invalid argument
E : int main /system invalid argument
E failed to mout data
E failed to mount system ..
when i start at ODIN MODE
Poduct name SGH-I317M_NA_BMC #
coust bianery dwnloud (125)
current bianery (samsung official)
system status (custom)
when i start the phone now give me black screen with battery shade ??
am i doing good or bad so far
please help me tep by step

Hey I replied back but you didnt answer.
But thats ok its better to keep this in the thread so thers can chime in and if we find a solution others who have this exact prob will find a fix.
As I wrote to you please confirm:
Your native language (maybe others who speak your tounge will better help)
I asked you what was the first thing you did with phone. (Root , any mods and exactly which rom.There are to many roms to be vague.)
I asked you what model you said rogers but above I noticed something about wind mobile?
First lesson: if you dont root your phone, you can NOT intsall a new rom, meaning you can ONLY do a factory reset, or install exact OEM (stock) rom viaodin or kies.
By the way . IM not gonna keep repeating "Kies Emergency Firmware Recovery" From now on when I say kies, im only talking about that function of kies.
So Example: A Rogers mobile, rooted or not, CANNOT have a wind, att, verizon tmobile or what ever installed. This is exactly why your phone is s-bricked. Like Bajanman said and as I told you if it powers on your good. Your just stuck.
This is called a bootloop; aka soft brick.
Also to complicate things more I am suspecting that you may have
Installed a custom kernel. Ooooops
Locked phones will def brick if you do that.
rage.jpg
As I said sometimes mobile phones are picky you may have to uninstall and reinstall : usb drivers, microsoft drivers, use different computer etc. Thats another thing; what computer and Operating System are you using?
PC right? What OS?
I dont have and despise face book but here are two other options.
If you live in the usa mail me your phone and ill take care of it.
Right now all other xda'rs are lulzing and gonna say dont do that.
:silly:
Understandably if you say no if you wanna dl yahoo or msn messenger we can do it that way.
The best thing to do dude is find a friend who speaks and understands english better than you and get them to translate
Or help.
If odin fails and kies EFR fails you are doing it wrong.
Even if your recoveryis corruptedit doesnt matter. If you can get
Into Download mode (its a two step process explained above)
Your phone can be fixed.
The other option is adb push and im sorry my fingers would fall off typing that out :lol:
You will have to do some leg work and research using adb to basically "force" the firmware into your partition. This is, c9rrefte if im wrong guys, basically what kies emergency recovery does but "automagically"
Why do I feel like mr miyagi : turn on! Turn off! Put in download mode..again! Now wax my hard drive! !
Do you have a camera? Pics or maybe a youtube vid would help.
Its 3am here im crashin.
I feel for ya bud.
:thumbup:
Edit: I just thought of something. Pull out your sd card and sim.
Dont put them back in until this is fixed.
This may even solve your problem.
From now on evey time you restart your phone pull out your battery and hold pkwer for a few seconds. No this is not a magic trick it just ensures most of the power is drained.

freakboy13 said:
You will have to do some leg work and research using adb to basically "force" the firmware into your partition. This is, c9rrefte if im wrong guys, basically what kies emergency recovery does but "automagically"
Why do I feel like mr miyagi : turn on! Turn off! Put in download mode..again! Now wax my hard drive! !
Do you have a camera? Pics or maybe a youtube vid would help.
Its 3am here im crashin.
I feel for ya bud.
:thumbup:
Edit: I just thought of something. Pull out your sd card and sim.
Dont put them back in until this is fixed.
This may even solve your problem.
From now on evey time you restart your phone pull out your battery and hold pkwer for a few seconds. No this is not a magic trick it just ensures most of the power is drained.
Click to expand...
Click to collapse
+1 again freakboy
Everything your telling him is correct.:thumbup::thumbup:He should be happy he's getting into download mode.
And not hard bricked. But if he's not careful it will b hard bricked.
LMAO at the Mr. Miyagi, wax on wax off..
Classic :thumbup:
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2

I could also try helping you out with TeamViewer later today.
Et je parle français si ça peut aider.
Send me a PM.
Goodbye,
Darkshado
Sent from my SGH-T889V using xda app-developers app

Hello . This post was originally a tutorial for samsung kies EFR.
Since so many people seem to not understand this great tool and to save bandwith
for xda (mods hit my thanks button! :victory: ...oh cmon im jk )
I removed this post and made it into an actual tutorial.
heres my new tutorial for Samsung's KIES Emergency Firmware Recovery Tool:
http://forum.xda-developers.com/showthread.php?p=40966346#post40966346

freakboy13 said:
I would hold off on flashing new roms until you read some more.
I hope this works out for ya!
Edit: its is recomended to unistall kies before using the galaxy note 2 toolkit
Click to expand...
Click to collapse
Very detail write up bro. :thumbup::thumbup: Very nice trying to help out!!
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2

Just a silly obsevation here, but you tell them to pull the battery and then go into recovery with the proper key press sequence. You forgot to tell them to put the battery back in the step by step sequence. Picturing op sitting there and not getting it to power up because battery is sitting next to phone. like I said, silly but I have encountered sillier. I am confident op would put it back in, but......
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By the way, great tutorial. Hope op gets it running.
Sent from the Millennium Falcon somewhere on the Kessel Run

ok guys .. sorry i was not here yesterday ..
just come back and i will do what u told me
thx for the help ..lets see what will happens ....

Mad383Max said:
Just a silly obsevation here, but you tell them to pull the battery and then go into recovery with the proper key press sequence. You forgot to tell them to put the battery back in the step by step sequence. ...... I am confident op would put it back in, but......View attachment 1884163
By the way, great tutorial. Hope op gets it running.
Sent from the Millennium Falcon somewhere on the Kessel Run
Click to expand...
Click to collapse
Dude thats hilarious.
Yes. OP, if you take the battery out....
Ya gotta put it back in for the phone to work!
:beer:

device not responding .
to solve the issue ,reboot the device ..
i did that 5 times and same issue bro
what i can do !!

What happens when you try to get into recovery? Describe the screen please.also describe exactly what happens when you the to the point if using the EFR.
You are doing the efr Right?
You are not doing the upgrade...correct?
You need to describe in more detail whats happening when its failing.
Just saying "its not working" makes it tough.
I still think youre doing something wrong.
Because the next step is to push the firmware and .....thats a bit more complicated.
Make sure you are NOT doing an upgrade, because before I made my pic guide you mentioned "I tried the upgrade".
You dont want to upgrade.
Keep trying dawg.
Please help me help you by explaining and describing the screen.
And so on.
Picsc would be better!
Describe the screen when you are in dl mode please. Remember dl mode is 2 parts.
Maybe some one else can chime in.
Theres gotta be someone in your area on these forums or others, who can maybe meet up and helpnyou in person?

[Q] Samsung t989 Galaxy S II - Bootloop HELP please :(

I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!

still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?

phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.

zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.

If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta

tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?

JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.

sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!

dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know

sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.

JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.

sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.

JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!

sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:

AT&T Galaxy s3 won't boot to Android

Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?

StoneyJSG said:
Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
Click to expand...
Click to collapse
You could try reflashing system and boot partition.

iloveoreos said:
You could try reflashing system and boot partition.
Click to expand...
Click to collapse
Is this done in ODIN? Will it wipe all my data? I'm trying to avoid anything like a data factory reset as I want to recover my stuff that wasn't saved to my SD card.

StoneyJSG said:
Is this done in ODIN? Will it wipe all my data? I'm trying to avoid anything like a data factory reset as I want to recover my stuff that wasn't saved to my SD card.
Click to expand...
Click to collapse
I don't know why it would, but I have never tried it on a Samsung. Flashing something like TWRP doesn't erase data when you flash it.

Which ROM is currently on the phone?
AT&T never released a stock ROM for the sgh-i747 after 4.1.1 or 4.1.2. All system updates were pushed to the phone via OTA; therefore, you can't re-flash the ROM using Odin unless you use a file that was specfically create for Odin.

audit13 said:
Which ROM is currently on the phone?
AT&T never released a stock ROM for the sgh-i747 after 4.1.1 or 4.1.2. All system updates were pushed to the phone via OTA; therefore, you can't re-flash the ROM using Odin unless you use a file that was specfically create for Odin.
Click to expand...
Click to collapse
Would the one for sgh i747m work if you just flashed system and boot? You can get that in 4.4.2.

Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.

​
audit13 said:
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
Click to expand...
Click to collapse
It is on Android 4.4.2 with bootloader NE4. It's the sgh-i747 AT&T variant. My warranty bit is 0. I can boot into download mode and stock recovery fine, just it won't boot into Android. I read somewhere that it might be an IC chip or emmc issue?
Someone took the NE4 OTA and made some ODIN files out of it so I downloaded them. I just want to be able to recover my files from the internal storage so I haven't flashed anything yet.

Glad you are on top of things.
Flashing the same ROM should be fine and it does not normally wipe your data. That being said, there is always a chance that flashing will result in data loss.
If it is an errant app that is causing the issue, you may have no choice but to wipe the data.

Ah ok, that's a bummer. Well I guess I will try flashing the same ROM over it and see what happens. Hopefully my data and apps stay in tact. I thought it might be a chip on the logic board so I took it to a repair shop over the weekend. Now to get it back from them and try flashing the ROM over the ROM.

audit13 said:
Glad you are on top of things.
Flashing the same ROM should be fine and it does not normally wipe your data. That being said, there is always a chance that flashing will result in data loss.
If it is an errant app that is causing the issue, you may have no choice but to wipe the data.
Click to expand...
Click to collapse
Just an update. I managed to fix my phone with Odin. I flashed the NE4 kit kat BL, AP, CSC, and CP files. It did wipe everything and put it back to factory stock like a factor data reset would do, so I lost all my files and apps.

Sorry to hear that the data was wiped.
Thanks for the update.

CrDroid O/S works good on my old Samsung Galaxy S3 i747
audit13 said:
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
Click to expand...
Click to collapse
Firstly, I am a newbie. I don't understand about this "warranty bit" . The Samsung S3 i747 is a very old phone ( hence no warranty after 8+ years ). Please explain !
---------- Post added at 04:46 PM ---------- Previous post was at 04:37 PM ----------
StoneyJSG said:
Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
Click to expand...
Click to collapse
I'm not sure how many of us are out there, tinkering around with the 8+ year old Samsung Galaxy S3 i747 . While I am a newbie, I have enjoyed flashing Custom ROM's , from CyanogenMod, thru various versions of Lineage, and now CRdroid.
You spoke of: " . . . dirty flashing in ODIN . . . "
I have always used ODIN to INSTALL a 'recovery' system such as TWRP ( which is a .Tar file )
After TWRP is installed ( using ODIN ) I unplug phone from my computer. Then boot into TWRP recovery ( holding down the three buttons ). I do a clean install (flash) of the newest O/S that I can find ( Android 4.4 is really old ). It is that .Zip file that I flash, then reboot the phone. Always works for me.
Eventually I learned how to back up all my contacts, SMS, logs, photos, etc.
BTW I am totally free of Google; no Google Play Store, no Google Pay, no Google Framework, no Gapps, no Google spyware, no Google bloatware, no Google tracking etc.
I download all my apps as APK's which are readily available on the Net ( Google them . . . just kidding! ).
My older Samsung S3 i747 was a 'd2att' originally locked to Rogers, in Ottawa, Ontario, Canada. Then switched over to MTS (Manitoba Telephone System). Now running on Bell Canada. My replacement is also a Samsung S3 i747, originally running T-Mobile in Arizona, now running on Bell Canada.
These are damn fine phones.

DavidWCS said:
Firstly, I am a newbie. I don't understand about this "warranty bit" . The Samsung S3 i747 is a very old phone ( hence no warranty after 8+ years ). Please explain !.
Click to expand...
Click to collapse
Do you see anything in the download mode screen that has the term "warranty bit"?
Is the phone model in download mode screen shown as an sgh-i747 or sgh-747m?

audit13 said:
Do you see anything in the download mode screen that has the term "warranty bit"?
Is the phone model in download mode screen shown as an sgh-i747 or sgh-747m?
Click to expand...
Click to collapse
Curious, I rebooted my phone into download mode ( holding volume down in the 3 finger format ).
There is nothing in the download mode screen that has the term "warranty bit". Just the WARNING !! A custom OS can cause critical problems . . .
There is no phone model in download mode screen shown as an sgh-i747 or sgh-747m
Sorry, but I still don't understand the importance of warranty in an 8+ year old phone. Am I still missing something?

DavidWCS said:
Curious, I rebooted my phone into download mode ( holding volume down in the 3 finger format ).
There is nothing in the download mode screen that has the term "warranty bit". Just the WARNING !! A custom OS can cause critical problems . . .
There is no phone model in download mode screen shown as an sgh-i747 or sgh-747m
Sorry, but I still don't understand the importance of warranty in an 8+ year old phone. Am I still missing something?
Click to expand...
Click to collapse
You are not in download mode.
The warranty bit term is not about warranty, it is about whether the phone has a locked bootloader.

audit13 said:
You are not in download mode.
The warranty bit term is not about warranty, it is about whether the phone has a locked bootloader.
Click to expand...
Click to collapse
OK, I tried it again. This time I went one step further. Aha! Tiny print on upper left of screen. Have attached a sample photo showing what I see. And yes, I can see what you mean: " Warranty Bit: 1 " . Thank you, it makes sense now.
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DavidWCS said:
OK, I tried it again. This time I went one step further. Aha! Tiny print on upper left of screen. Have attached a sample photo showing what I see. And yes, I can see what you mean: " Warranty Bit: 1 " . Thank you, it makes sense now.
.View attachment 4991379
Click to expand...
Click to collapse
The phone is not an AT&T S3, it is a T-Mobile s3 sgh-t999?

audit13 said:
The phone is not an AT&T S3, it is a T-Mobile s3 sgh-t999?
Click to expand...
Click to collapse
There are 2 i747 phones; d2Can & T999. In the past, the O/S's that I flashed, were designed for d2att. No difference in how they functioned, as far that I could notice.

DavidWCS said:
There are 2 i747 phones; d2Can & T999. In the past, the O/S's that I flashed, were designed for d2att. No difference in how they functioned, as far that I could notice.
Click to expand...
Click to collapse
Yes, there are two models of the i747: sgh-i747 (AT&T, d2att) and sgh-i747m (non-AT&T, d2can)
The T-Mobile s3 is sgh-t999 (d2tmo).

Note 10+ SM-N975F/DS very very HARD BRICK --- Advice?

After years of flashing roms (and lurking here, especially DrKetan´s thread), I hard bricked my brand new SM-N975F. When I power it on, it goes to the screen that tells me the bootloader is unlocked, then to a welcome screen, and that is where it stays. (see pics).
I have tried the following:
1) All possible hardware combinations. (I tried at least 100 times all combinations between the keys): always the same.
2) Odin3 does not detect the phone in either screen.
3) Samsung Tool 300K does not detect the phone.
4) ADB does not detect the phone. (adb devices comes empty)
I am about to get a hammer and wreck the little guy, but I decided to ask you first.
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i think if u post what firmware u was and what did u flashed or what u did ,,, its better that maybe someone can help
Sent from my SM-N975F using Tapatalk

carlitobahsoun said:
i think if u post what firmware u was and what did u flashed or what u did ,,, its better that maybe someone can help
Click to expand...
Click to collapse
Thank you! I was on stock ROM (Q), with an unlocked bootloader. I was flashing TWRP for Android Q with Odin. It "Pass"ed, and when I rebooted it bricked. Tried every key combination, I can´t get into download mode and the phone is not recognized when connected to the laptop. Tried several cables, too.

dk1965 said:
Thank you! I was on stock ROM (Q), with an unlocked bootloader. I was flashing TWRP for Android Q with Odin. It "Pass"ed, and when I rebooted it bricked. Tried every key combination, I can´t get into download mode and the phone is not recognized when connected to the laptop. Tried several cables, too.
Click to expand...
Click to collapse
i think ur fault was when u let it reboot / u must after odin twrp forced to reboot to custom twrp recovery and do as i think format data , well never root my samsung mobiles 3 years ago , i advice u to be cool + send private msg to dr ketan to get help OR if u have telegrams u can join many group and i know u will get help.
iam out of telegram 1 years ago too so i dont know any groups for n10+ .
try first dr ketan by pm him and wait till anyone read here and help
Sent from my SM-N975F using Tapatalk

you should put the phone in download mode and reflash stock from odin.
reboot [down+pwr] when the screen shut down immediately put the usb cable in the phone usb port (the other already in the port of the pc) keeping the vol down till enters in download mode.
you cannot flash just the twrp partition, you have to flash the disable verity check as well. otherwise the bootloader dont't allow the bootstrap as the integrity check fails.
follow the dr.ketan instructions (carefully).
Inviato dal mio SM-N975F utilizzando Tapatalk

ziotom2 said:
you should put the phone in download mode and reflash stock from odin.
reboot [down+pwr] when the screen shut down immediately put the usb cable in the phone usb port (the other already in the port of the pc) keeping the vol down till enters in download mode.
you cannot flash just the twrp partition, you have to flash the disable verity check as well. otherwise the bootloader dont't allow the bootstrap as the integrity check fails.
follow the dr.ketan instructions (carefully).
Inviato dal mio SM-N975F utilizzando Tapatalk
Click to expand...
Click to collapse
Thank you! I tried Dr Ketan´s instructions, but no matter how hard I try, I can´t get to the download mode. I followed your instructions but the phone does not go to download mode, it just shows the "bootloader modified" screen, then the other one. Odin (nor Samsung Tool 300K) do not recognize the phone at any time, not even for a second, so I can´t flash anything to it.

Sm-n975f hard brick - solved
I hard bricked my SMN975F by uploading the wrong TWRP. The bootloader was already unlocked, but the new TWRP for Q bricked it.
I solved it by sending the phone to a Samsung repair shop. It took them 24 hours (and about 70 dollars), but they were able to flash the bootloader, and the stock Q rom.
Moral of the story: if your Note 10+ is hard bricked, there is a solution. You can try the advice given to me above by these useful members, but if that fails do not toss the phone. Go to a Samsung service store, and they will be able to fix it. Thank you all for their help!

dk1965 said:
I hard bricked my SMN975F by uploading the wrong TWRP. The bootloader was already unlocked, but the new TWRP for Q bricked it.
I solved it by sending the phone to a Samsung repair shop. It took them 24 hours (and about 70 dollars), but they were able to flash the bootloader, and the stock Q rom.
Moral of the story: if your Note 10+ is hard bricked, there is a solution. You can try the advice given to me above by these useful members, but if that fails do not toss the phone. Go to a Samsung service store, and they will be able to fix it. Thank you all for their help!
Click to expand...
Click to collapse
happy they solve it but let me be honest with u , in my country LEBANON middle east i KNOW and more knowledge than SAMSUNG'S guys inside , some small questions they wasent able to answer....so u are lucky guys that in ur country they are good knowledge to fix....
happy new year and keep enjoy ur n10+
Sent from my SM-N975F using Tapatalk

You f##ked it real good but not a hard brick as far as I'm aware. (I may be wrong)
Hard brick is only fixable with a new motherboard.
Well done on getting it sorted and that's great service from sammy

I know you said you tried 100 times, different combinations, by any chance was this - Press and hold the Volume Up + Bixby / Power buttons. - one of them? It should boot into recovery mode not download mode. I had a similar issue, I had to try and try until I was able to get into recovery, from there did wipe data/factory reset several time, and then select reboot to bootloader, then flash the latest firmware(since you probably wont know which booltloader you have on it). Also remember to used the recommended Odin by the XDA team.

Try following alternate way.
- Turn Off Phone, if unable to turn off, wait till battery drain and off itself.
- Press and hold the Volume up and the Power keys at the same time for 3-4 seconds.
- This will bring you to Recovery Screen.
- Use Volume Up and Down Button to Navigate and choose Reboot to bootloader by pressing the power button.
- You are now at Download Mode.

Note 10+ SM-N975F/DS very very HARD BRICK --- Advice?
Andrewtst said:
Try following alternate way.
- Turn Off Phone, if unable to turn off, wait till battery drain and off itself.
- Press and hold the Volume up and the Power keys at the same time for 3-4 seconds.
- This will bring you to Recovery Screen.
- Use Volume Up and Down Button to Navigate and choose Reboot to bootloader by pressing the power button.
- You are now at Download Mode.
Click to expand...
Click to collapse
Thank you for your feedback. I had tried that, but the recovery screen did not come up. The method you suggest will work for most cases, but in my case I had screwed up the recovery itself by flashing the wrong TWRP.
Moral of the story: do not flash the wrong TWRP, because it may corrupt your recovery, and then getting to download mode is a lot more complicated.

exocetdj said:
You f##ked it real good but not a hard brick as far as I'm aware. (I may be wrong)
Hard brick is only fixable with a new motherboard.
Well done on getting it sorted and that's great service from sammy
Click to expand...
Click to collapse
I agree with you, real good. It may not be a complete hard brick, as the repair guys did not open the phone nor changed the motherboard. Still, it was as bad as a soft brick can get....

ust buy a z3 and fix it lol

Samsung Smart Switch
As far as I know, Samsung Smart Switch is the only method to recover your phone. Download it on your pc. Launch the app and connect your phone. Choose to recover bricked phone.

I bricked about 8 different phones with the new A/B thing before I learned TWRP doesn't work and the fix was to flash the stock boot.img to both partitions with:
./fastboot flash boot --slot all <nameofboot.img>

Download the modded version of Odin. Here's a link to it in my Google Drive: https://drive.google.com/folderview?id=10F5bh4YmD0vAduSMfuqF7jQl4ho1s83a
Sent from my [device_name] using XDA-Developers Legacy app

Did it work buddy?
Sent from my [device_name] using XDA-Developers Legacy app

I have the same issue
Sm-n975f hard brick - solved
Guys I solved it. I pressed Volume down + Power, as soon as the screen turned off I quickly pressed Volume up +Volume down as I inserted the cable and voila! Download mode. Now I can reflash stock firmware
That was a very close call.

Plz delete
---------- Post added at 06:20 PM ---------- Previous post was at 06:03 PM ----------
vs|porkchop said:
Sm-n975f hard brick - solved
Guys I solved it. I pressed Volume down + Power, as soon as the screen turned off I quickly pressed Volume up +Volume down as I inserted the cable and voila! Download mode. Now I can reflash stock firmware
That was a very close call.
Click to expand...
Click to collapse
YEAH you saved my ass!!!
Thank you wherever your are :victory:
God bless you :angel: