Database Develop

Messed up SGS3 4G - Root failed, can't start phone - Wiped everything.

Recently I used ODIN 3.0.7 to try and root my Samsung Galaxy S3 (Telia) 4G with a so-called "CF-Root-SGS3-v6.4".
It is the 16 GB, 2 GB RAM 4G/LTE version, and it was running at Android 4.1.2 when I tried to do the root.
The phone booted up fine and ODIN claimed it was a success, I immediately noticed that the phone had stopped recognizing my SIM card, and the Root Checker also stated that something was wrong and it wasn't rooted. so I download a stock ROM and try to install that, however when I choose the SD card to try and install it, it says no files are found.I had made it to the CWM Recovery tool on the phone, and I could start the phone that way ("Reboot Phone Now", but it still didn't recognize my stuff, so I tried following the stock ROM instructions I was given, and I wiped all data, cache and stuff after backing it up on my PC in the CWM recovery tool.
Now, at this point, the phone is stuck at "Downloading - Do not turn off target!". When I try turning it off, the screen goes black for 2 seconds, and then the screen appears again. If I am quick, I can get into the "ODIN" mode, where I can once again try and root it. It fails again, but now I get to the CWM Recovery Tool again, but no files are found at all, and if I reboot the phone, it just goes back to the Downloading screen (I left it on overnight and it stayed on that screen, by the way. I doubt it is ACTUALLY downloading anything).
I do not know the Kernel or ROM version. The phone was bought in the start of February, though, so I could imagine it's rather new.
What do I do now? I just wish to get my phone back to normal Android, normal everything even if it means a factory reset.

You need to goto the NV backup sticky thread in the dev section that I put together, look near the bottom.
Download the param binary and flash with odin to revive your device.
Sent from my GT-I9305 using Tapatalk 2

Hello, I followed the guide and flashed the phone with the param with ODIN, however, the phone is still stuck on its "Downloading - Do Not Turn Off Target!" screen (though it is not showing the ODIN mode at the corner anymore.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Param_Bin_I9305.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> param.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... *0*
<OSM> All threads completed. (succeed 1 / failed 0)
The box is green and says "PASS!", but the phone is unresponsive.
Did I do something wrong?

Right now you need to read then run this via odin from you PC...
http://forum.xda-developers.com/showthread.php?t=1942150

You probably corrupted your efs partition by flashing a CF Root not intended for your phone. The CF Root is for SGS3 not I9305 LTE.
Sent from my GT-I9305 using XDA Premium HD app

Raistlin1158 said:
Right now you need to read then run this via odin from you PC...
http://forum.xda-developers.com/showthread.php?t=1942150
Click to expand...
Click to collapse
This did it, thank you!
Time to reinstall a lot of apps, and be more careful with the root I pick.. ;_;

You already have root with this rom

Hello again, sorry for sort of necroing.
So I got it running again, there is one nasty problem, though - The phone won't recognize my SIM card, meaning that it simply doesn't register that there is one.
I'd guess the phone warranty is void at this point, so what do I do? Is there any DIY fix?

Azortharion said:
Hello again, sorry for sort of necroing.
So I got it running again, there is one nasty problem, though - The phone won't recognize my SIM card, meaning that it simply doesn't register that there is one.
I'd guess the phone warranty is void at this point, so what do I do? Is there any DIY fix?
Click to expand...
Click to collapse
Did you check your IMEI??? After messing with your phone you could simply lost it.
Sent from my GT-I9305 using xda app-developers app

How do you check IMEAI
DjeMBeY said:
Did you check your IMEI??? After messing with your phone you could simply lost it.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse

hard bricked galaxy sIII I9305
guys i got a much worse situation, my device is a galaxy I9305, and i turned my phone off during the flash of a firmware where it was saying "FAIL" for a long time. I'm desperate at the moment and i'm not finding out any way how to debrick it, any help would be greately appreciated! My device is stuck on "Downloading... Do not turn off target!!" it's only this text in the center, with nothing more

[Q] Potential self-brick of my GT-N7000 Galaxy Note

Hello everyone!
After browsing the forums and reading through some of the information available on bricked Galaxy Note N7000 devices, I decided to post a thread about my specific issue, given that it happened spontaneously, on a device which was never modded/rooted in any way, and which has been kept gingerly for almost four years! I will provide a brief, step-by-step overview of the issue as well as the different attempts at addressing it that have already been undertaken, in the hope that some of you will be so kind as to give me your opinion on what I could do next!
- A couple days ago, I received a phone call, and, as usual, I connected my headphones to the device. I immediately heard a crackling noise from them, as the device rebooted itself.
- I noticed that the device was stuck on the Samsung Galaxy Note GT - N7000 black and white logo. As a result, I tried turning it off, and connecting it to my charger. The grey battery icon popped up, and was quickly substituted by the green "charging" icon with moving dots. After a few minutes, I tried turning on the phone again, and it was stuck on the splash screen once more.
- I tried going into the recovery menu, which I successfully did, and, upon rebooting from it, the phone moved past the splash screen to the pink and purple Samsung animated logo; that was quickly followed by a screen I had never seen before, a password bar, and the message "Enter password to use encrypted device storage". Not knowing what to do, I turned off the device.
- the next logical step was to contact Samsung Italy, and I was told to try wiping cache and data from the recovery menu and attempt a restore to factory settings. Nothing particular happened, as the phone got once again stuck on the Note splashscreen, and the recovery menu showed a series of red lines, containing information such as:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system ((No such file or directory))
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /cache (No such file or directory)
can't mount '/cache' (No such file or directory)
- Next step was to take the phone to a local repair shop, where I was told that flashing the firmware was really my only option, given the functioning download and recovery menus; I left the phone with the technician, who called me later in the evening asking me if the phone was still under warranty. I told him there was no warranty, so he attempted to install a custom recovery menu via Odin, namely the following versions of PhilZ: PhilZ-cwm6-XXLSZ-OXA-4.93.6.tar and PhilZ-cwm6-XXLTA-ATL-5.15.0.tar. Upon seeing the failed install, he decided to wait for the firmware to finish its download (abysmal connection speeds in my area) and try flashing it.
- The following morning, I joined the technician in his office as he showed me that the phone could now no longer access recovery mode, seeing as the custom recovery install failed, and the flash attempt counter had gone up to three (like I mentioned earlier, I took great care not to do anything too fancy with this phone, seeing as it's my work phone), with a yellow warning sign appearing under the splash screen.
- The technician's attempt to install stock firmware (N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5) was met with failure. Odin fails at the "NAND Write" step, as shown by the following log (I replicated it at home):
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin engine v(ID:3.1005)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> cache.img
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
- attempting to install a PIT file via Odin to repartition the device (filename: Q1_20110914_16GB) was also met with failure (the error message said something like "failed to repartition"), but, as I didn't pay enough attention to the steps taken by the technician to be able to replicate the operations at home - like I said, I've never done this before.
To sum up, the phone is showing the following symptoms:
- battery icon not changing from grey to green
- stock recovery menu not accessible due to a failed attempt at installing a custom recovery menu (+3 custom flash counter)
- yellow triangle on splash screen, where the device remains stuck indefinitely
- download mode still accessible, device recognized by Odin, firmware flash fails at NAND Write Start
I really hope some of you will be able to give me your two cents on how to proceed! Thank you in advance for any and all help!
Lightside

Sounds tough, but you did right by pouring everything you know on the problem here.
First I'd try to use the stock partition available here: http://forum.xda-developers.com/showthread.php?t=2642299
Then look for a PhilZ recovery in this forum to Odin flash.
If it works, then proceed to flash a stock rom via recovery.
If not, then try the partition method with a stock rom. I used the guide provided in the link above and it worked flawlessly.
I'd wait for other members to pour in their thoughts on this if they're gracious enough but you're still welcome to try this

AutumQueen92 said:
Sounds tough, but you did right by pouring everything you know on the problem here.
First I'd try to use the stock partition available here: http://forum.xda-developers.com/showthread.php?t=2642299
Then look for a PhilZ recovery in this forum to Odin flash.
If it works, then proceed to flash a stock rom via recovery.
If not, then try the partition method with a stock rom. I used the guide provided in the link above and it worked flawlessly.
I'd wait for other members to pour in their thoughts on this if they're gracious enough but you're still welcome to try this
Click to expand...
Click to collapse
Hello, and thank you for your advice! I have just tried flashing the pit file provided in the thread you linked, and this is the Odin log:
<ID:0/012> Added!!
<ID:0/012> Odin engine v(ID:3.1005)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: I've tried every Odin version I could get my hands on, and attempted using all 5 custom pit files. I even tried reflashing PhilZ-cwm6-XXLTA-ATL-5.15.0.tar, to no avail. Have I exhausted all my options?

Lightside said:
Hello everyone!
After browsing the forums and reading through some of the information available on bricked Galaxy Note N7000 devices, I decided to post a thread about my specific issue, given that it happened spontaneously, on a device which was never modded/rooted in any way, and which has been kept gingerly for almost four years! I will provide a brief, step-by-step overview of the issue as well as the different attempts at addressing it that have already been undertaken, in the hope that some of you will be so kind as to give me your opinion on what I could do next!
- A couple days ago, I received a phone call, and, as usual, I connected my headphones to the device. I immediately heard a crackling noise from them, as the device rebooted itself.
- I noticed that the device was stuck on the Samsung Galaxy Note GT - N7000 black and white logo. As a result, I tried turning it off, and connecting it to my charger. The grey battery icon popped up, and was quickly substituted by the green "charging" icon with moving dots. After a few minutes, I tried turning on the phone again, and it was stuck on the splash screen once more.
- I tried going into the recovery menu, which I successfully did, and, upon rebooting from it, the phone moved past the splash screen to the pink and purple Samsung animated logo; that was quickly followed by a screen I had never seen before, a password bar, and the message "Enter password to use encrypted device storage". Not knowing what to do, I turned off the device.
- the next logical step was to contact Samsung Italy, and I was told to try wiping cache and data from the recovery menu and attempt a restore to factory settings. Nothing particular happened, as the phone got once again stuck on the Note splashscreen, and the recovery menu showed a series of red lines, containing information such as:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system ((No such file or directory))
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /cache (No such file or directory)
can't mount '/cache' (No such file or directory)
- Next step was to take the phone to a local repair shop, where I was told that flashing the firmware was really my only option, given the functioning download and recovery menus; I left the phone with the technician, who called me later in the evening asking me if the phone was still under warranty. I told him there was no warranty, so he attempted to install a custom recovery menu via Odin, namely the following versions of PhilZ: PhilZ-cwm6-XXLSZ-OXA-4.93.6.tar and PhilZ-cwm6-XXLTA-ATL-5.15.0.tar. Upon seeing the failed install, he decided to wait for the firmware to finish its download (abysmal connection speeds in my area) and try flashing it.
- The following morning, I joined the technician in his office as he showed me that the phone could now no longer access recovery mode, seeing as the custom recovery install failed, and the flash attempt counter had gone up to three (like I mentioned earlier, I took great care not to do anything too fancy with this phone, seeing as it's my work phone), with a yellow warning sign appearing under the splash screen.
- The technician's attempt to install stock firmware (N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5) was met with failure. Odin fails at the "NAND Write" step, as shown by the following log (I replicated it at home):
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin engine v(ID:3.1005)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> cache.img
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
- attempting to install a PIT file via Odin to repartition the device (filename: Q1_20110914_16GB) was also met with failure (the error message said something like "failed to repartition"), but, as I didn't pay enough attention to the steps taken by the technician to be able to replicate the operations at home - like I said, I've never done this before.
To sum up, the phone is showing the following symptoms:
- battery icon not changing from grey to green
- stock recovery menu not accessible due to a failed attempt at installing a custom recovery menu (+3 custom flash counter)
- yellow triangle on splash screen, where the device remains stuck indefinitely
- download mode still accessible, device recognized by Odin, firmware flash fails at NAND Write Start
I really hope some of you will be able to give me your two cents on how to proceed! Thank you in advance for any and all help!
Lightside
Click to expand...
Click to collapse
OMG this is the condition of my GS2 , my note is perfect, im trying something tomorrow, will let you know

coko___bear said:
OMG this is the condition of my GS2 , my note is perfect, im trying something tomorrow, will let you know
Click to expand...
Click to collapse
At this point, I appreciate any and all help, so thanks for replying

Up?

Please help in root note 5 SM-N920G

Guys, first sorry for my bad and confusing english.
-
I had a Samsung note 5 version SM-N920G and need rooting this cel but is really impossible ¬¬
I search and tried make a various tutorials here in XDA and in others foruns.
Droid version 5.1.1 - Bandbase -> N920GUBUAOj3 /// Number of compilation : LMY47X.N920GUBU2AOJ4
I tried use a ODIN version: Odin3_v3.10.6
And flash a SM-N920C-kernel-SkyHigh_TW_v3.6--[16-01-16].tar.
Nerver get a Succes, only fail like this code:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tryed use this too:
CF-Auto-Root-noblelte-noblelteub-smn920g.tar
get same erros above.
----------------
Please friends, anybody can help-me?
Sorry for english, hug's for all.

Have you tried turning off "Reactivation Lock" in settings->security?
What it "Reactivation Lock" does is, it turns off the ability to flash roms so that, when your phone gets stolen, it becomes useless if its password protected. To turn it off go to setting> security and turn off 'Reactivation Lock'.
Originally Reported on Reddit by KinKingSons
reddit.com/r/galaxynote4/comments/332ixf/unable_to_root_odin_fail/
If this method doesn't work, please describe in detail exactly what steps you did.

akhilkedia94 said:
What it "Reactivation Lock" does is, it turns off the ability to flash roms so that, when your phone gets stolen, it becomes useless if its password protected. To turn it off go to setting> security and turn off 'Reactivation Lock'.
Originally Reported on Reddit by KinKingSons
reddit.com/r/galaxynote4/comments/332ixf/unable_to_root_odin_fail/
If this method doesn't work, please describe in detail exactly what steps you did.
Click to expand...
Click to collapse
Thank you for your help my friend;
Reactivation Lock not reoganize in note 5.
-
I follow this steps:
unlock deve mode, turn on USB Debugging..
shutdown my phone, enter in download mode.
open odin, select the modified kernel in AP option. and click in start.
I see this mensage in download mode:
Custom Binary(boot) Blocked by FRP lock - have any connection with Fingerprint unlock metod?

Kindly be clear as to whether or not the "reactivation lock" is off on your phone.
Here is a link which shows detailed steps as to how to find the reactivation lock option on the phone -
samsung.com/us/support/answer/ANS00040928/997345371/SM-G920AZKZAIO
The link is for s6, but you can roughly follow the steps to find the option for reactivation lock in note 5.
Revert back when you have found it.

akhilkedia94 said:
Kindly be clear as to whether or not the "reactivation lock" is off on your phone.
Here is a link which shows detailed steps as to how to find the reactivation lock option on the phone -
samsung.com/us/support/answer/ANS00040928/997345371/SM-G920AZKZAIO
The link is for s6, but you can roughly follow the steps to find the option for reactivation lock in note 5.
Revert back when you have found it.
Click to expand...
Click to collapse
In my note 5 have only :
Remote control
google location serve
and sim change alert.
Dont show Reactvation lock

Here are a few steps you could try, and if none of them work, I am sorry I cannot help you -
1) Go into developer options-> enable the OEM unlock and try flashing via Odin again
2) Settings>Search>Reactivation Lock>log in into Samsung account and disable (Seriously, it should be there. Please look.)
3) Use this link for Odin - dl.sammobile.com/Odin3_v3.10.7.zip
And this link for your kernel - androidfilehost.com/?fid=24369303960688397
Bruno Santos. said:
In my note 5 have only :
Remote control
google location serve
and sim change alert.
Dont show Reactvation lock
Click to expand...
Click to collapse

akhilkedia94 said:
Here are a few steps you could try, and if none of them work, I am sorry I cannot help you -
1) Go into developer options-> enable the OEM unlock and try flashing via Odin again
2) Settings>Search>Reactivation Lock>log in into Samsung account and disable (Seriously, it should be there. Please look.)
3) Use this link for Odin - dl.sammobile.com/Odin3_v3.10.7.zip
And this link for your kernel - androidfilehost.com/?fid=24369303960688397
Click to expand...
Click to collapse
Steps 1 2 3 dont work.
Step 4: sorry for i'm like a dumbass but the kernel you send to me is a .zip file, where i put in odin if accept only .tar .md5 etc etc...
i need to rename extension?
man, sorry and i appreciate your help, really thank you for your time.

My understanding is that Samsung took out the Reactivation Lock for the Note 5. There are a few guides in the general section. Here is one that another poster mentioned. http://forum.xda-developers.com/note5/general/how-to-root-note-5-t3205073
There are others. My advice to you is read, read, read, and then read some more. Learn how to get back to stock in the event something goes wrong. There are a lot of helpful people here but I do not think there are a lot of people who are willing to hold your hand the whole way. I am not trying to be rude to you and for all I know there is no root for your version. Good luck

hey guys, i had success on root!
really thanks for yours time and help.
god bless you folks!!!!!

root your n920g? thanks
Bruno Santos. said:
hey guys, i had success on root!
really thanks for yours time and help.
god bless you folks!!!!!
Click to expand...
Click to collapse
can you be able to explain how you were able to root your n920g?

need help how to root n920g india variant

Bruno Santos. said:
hey guys, i had success on root!
really thanks for yours time and help.
god bless you folks!!!!!
Click to expand...
Click to collapse
Can u explain or make a thread on how obtained root

Need some help Please

I have a sm-n910t3 phone I recently got. It was already flashed with some rom, twistd i think . I got an su binary is occupied error so i thought I would just reload stock and downloaded the \N910T3UVS3EQE2_N910T3TMB3EQE2_N910T3UVS3EQE2_HOME.tar.md5 since that what the phone say it is in the battery compartment. HOWEVER,
if i look at the about device, settings, it says the model is sm-g935t
when i run odin it checks the md5, adds it to the ap block and click start I get
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Removed!!
Twrp 3.2.1-0 is installed and accessable
all i wanted was to put on stock 6.0.1, twrp, root and magisk but now it seems i have a very basic os with little else.
any help will be greatly appreciated

SO i HAVE MANAGED TO PRETTY MUCH ALMOST BRICK MY 910T3. after screwing around with it for way too long it now will not boot at all keeps returning to twrp. odin will not download due to the device error mentioned above. I still have hope but it is dwindling every day may have a $200 brick.

cmccarter said:
SO i HAVE MANAGED TO PRETTY MUCH ALMOST BRICK MY 910T3. after screwing around with it for way too long it now will not boot at all keeps returning to twrp. odin will not download due to the device error mentioned above. I still have hope but it is dwindling every day may have a $200 brick.
Click to expand...
Click to collapse
Have you tried another Firmware ? this one might be corrupted, if you can boot into TWRP why don't you try to reformat the memory? and flash a rom?
Also try to get a firmware with the AP,BL,CSC, CP so you can Deep Clean the phone. try this webpage gsm-firmware(dot)com

Got it working thanks to all for the help. Did a full install of Lineage which kinda put the phone back in a regular mode. I had had Twistd d7 port installed was the main culprit that was making my phone think it was a 935. I then installed a deodexed, debloated (sorry cannot remembed whose it was) 6.0.1 that was rooted also and the phone is now 100% operational. I do want to get rid of super su and go with magisk but not real sure how to get rid of the SU that is already flashed into the phone.
Again my thanks to all who provided input to help me get everything working again.

Please help - Sorry if this is the place

Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?

Jeppe_77 said:
Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?
Click to expand...
Click to collapse
I am no expert, just going to suggest what I would try, hopefully someone may know what to do exactly.
You could try downloading stock filmware from Sammobile or updato (making sure to at least flash the same filmware build or higher, or Odin won't flash it) if you use the "home csc" csc file, it should not wipe the data on the phone, and what I hope may fix the phone not booting.

First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk

Get a pit file and flash it though oden may work or not.......

yashthemw said:
First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Its an Galaxy Note 8 (SM-N950F)
The only thing i can see in the display is
https:// imgshare.io/image/odin-2.U7KCu
We dont know what firmware was beeing used Before this, it´s not custom or rooted tho. I assume its the latest official tho
I grabbed the latest from Sammobile, N950FXXU7DSJ1_N950FCKH7DSJ1_HTS
I could try the above suggestions but what about trying to flash the BL? Could it not be the BL that is cuppupt somehow?

I did try and flash the BL now but Odin software says:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems the partitions are gone, @stinka318. Next, where do i find PIT-files?

Found PIT file but it failed.
Also tried CSC flash but it fails (looks like Odin might not cennect to the device (ID:COM 0: [COM4])
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 179 M
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Driver related? i have the Samsung USB drivers installed….

https://zfirmware.com/download-samsung-galaxy-note-8-pit-file/

Seems like it's a kernel problem, or maybe the phone IMEI reported stolen?
Have you tried installing custom binaries? TWRP maybe?
Or messing with OEM unlock found in Developer Options?
Most of the for solving such problem, you have to flash the exact same firmware found on phone before the problem.

Try rooting using odin and then twrp and thenflashing a custom firmware..... That could help..... Just a thought.... Wipe everything except internal storage

https://mega.nz/#!Lk8RiKQR!FiH50HLQp1aijVkRARSPtBN6M6wFphShHsm7i6u23lw
Try flashing this via odin through AP.
Sent from my SM-N950F using Tapatalk