Database Info

[Help] I soft bricked my phone, i am desperate.

I am so lost as to what to do next, i really need guidance.
I am offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work ASAP.
So i was attempting to root my phone [GALAXY S6 - SM-G920F]
Got the file from: https://autoroot.chainfire.eu/ which should've matched my Phone.
First attempt failed, got back into my phone everything is fine. Tried the same thing again, failed this time i get this message:
An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." The logs for the times it has failed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Tried connecting with Kies and Smart switch, none can find the device just keeps buffering and for smart switch it just say it's not supported. I am able to get into downloading mode, but that's it.
Got newest Kies, odin 3 v.10.7.exe however on my first go i noticed i had odin3 v.10.6 but now i got the latest i believe. After reading around i decided to try to fix it back to normal, so i downloaded my countries [sweden] firmware this one: http://www.sammobile.com/firmwares/confirm/57869/G920FXXU3COI9_G920FVDS3COI6_VDS/
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004>
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
And now i am here, i am truely nervous that i wont be able to get it to work.
Please Xda your my only hope. All i wanted was to free up space on my phone.. That's it.. :crying:
Ps. Worth mentioning, sometimes my usb is not recongnized and it flickers on and off (connectiong) but seems
to be fine most of the times and during the odin trials.

To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted

Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
I just begain with youtubing easy way to root and i just said download odin, get the right firmware plug in an click odin.
That has failed and it's bricked, however i have tried to get my countries firmware, it didint work and produced my last log that i posted.
I am downloading another one there is two for Sweden however the other one says Sweden tre which is an operator over here and not one that i use so i doubt that will work?
i will attempt to download it but it takes 3h due to the limited speed at sammmobile.
So summarize, the sweden firmware from sammobile failed ;_;
What i do is, put phone in download mode, open odin, get the AP [Sweden from sammomobile] it finds it and press start, quickly after it says failed and i am back to square one.
I was reading the link you gave me about the pit files, it appears the error could be related to me having the wrong firmware?
I am seriously offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work.

There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.

blud7 said:
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
Click to expand...
Click to collapse
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.

If you were on 5.1.1, then get 5.1.1
You can try the file you dl before. Just uninstall Kies before using Odin.

WaDoDem said:
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
Click to expand...
Click to collapse
You dont need to download another rom dude...the problem is your usb dont get recognized and after a while it will disconnect...it happened to me aswell...searched on youtube did an easy fix and then i flashed stock rom with odin and joined marshmallow beta...
Tldr: search on youtube a fix for usb not recognized...i dont have a link sorry you have to search it by yourself its an easy fix..

Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help

anthonyrv03 said:
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
Click to expand...
Click to collapse
You're fine with either.

@WaDoDem
First of all, calm down. Believe me it's harder than you think to brick S6 in a not fixable way
If Odin doesn't flash official roms or you just cant suffer a slow a** download speed from SamMobile :
1. Press and hold all of 4 buttons on your device. (Volume up + Volume Down + Home + Power) your device will reboot.
2. As soon as device reboots release volume up and hold other 3 three. (Power + Home + Volume Down). Your device should boot into downloading mode.
3. Download this :
https://dl.twrp.me/zeroflte/twrp-2.8.7.2-zeroflte.img.tar.html
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes, hold Power+Home + Volume Up. Now your device will boot into TWRP recovery.
5. Wait for drivers to be installed. Your pc should show phone's internal storage as connected device. If not, go to TWRP Mount section and enable MTP mode. (Or if it's enabled, disable and re enable it )
6. Download this rom :
http://forum.xda-developers.com/gal...rom-2013266107-arrow-rom-v1-0-0-fast-t3212318
And this kernel:
http://forum.xda-developers.com/gal...nified-development/kernel-vindicator-t3156281
Then put them on your phone.
7. Wipe system,data,cache and dalvik cache from twrp.
8. Install Arrow Rom first and then flash Vindicator Kernel.
9.Reboot, first boot can take up to 15 minutes
10.Continue celebrating new year [emoji14]
Sent from my SM-G920I using Tapatalk

sometimes if odin not working i restart my computer and put my mobile in downloadmode again and than i try again,most of the time it worked.....

If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)

4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes said:
Odin cant find the tar file.
I got odin 3V3.10.7 in options auto reboot and f. reset time are all bocked in is that right?
On files to download i am able to do, ap,cp,csc,bl neither of those help to find the recovery image that i am supposed to start?
Click to expand...
Click to collapse

Damientju said:
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
Click to expand...
Click to collapse
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.

WaDoDem said:
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
Click to expand...
Click to collapse
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone

Damientju said:
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Click to expand...
Click to collapse
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.

WaDoDem said:
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
Click to expand...
Click to collapse
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know

[email protected] said:
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
Click to expand...
Click to collapse
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!

yes
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
WaDoDem said:
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Click to expand...
Click to collapse
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.

sd_N said:
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
Click to expand...
Click to collapse
I just downloaded and tried the pit that above user posted.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
It's a Galaxy s6 32GB.

Boot loop - verity verification failed

I have tried to installed marshmallow via Odin on my galaxy s6 SM-920F. It's not the first time I'm flashing a device but this time reactivation lock was on and Odin would not finish. Restarting the phone is not possible as its stuck in a bootloop and shows blinking "Galaxy S6" every time and recovery mode says verity verification failed. Didn't not know reactivation would do so much damage as I thought it would just ask a password in case a thief tries to flash the phone.
I searched everywhere but could not find a solution and hope to get some expert advice here. Please help

Get the phone into Download mode and flash the ROM again?

Flashing again won't help because of reactivation lock and there is no way I know I can disable that without entering the phone itself.

Eek. Tried flashing the original firmware you were running prior to trying to upgrade and doing a factory reset?
Might let you log back in and disable the lock.
Sent from my SM-G920I using Tapatalk

Already tried reset or reinstalling current version. The lock won't let it happen. Upon restart the phone is stuck in a loop.

heetesh22 said:
Flashing again won't help because of reactivation lock and there is no way I know I can disable that without entering the phone itself.
Click to expand...
Click to collapse
Reactivation Lock prevents only custom (not Signatured by Samsung) images to flash. So, you should able to flash stock ROM.
Did you try SmartSwitch?

heetesh22 said:
I have tried to installed marshmallow via Odin on my galaxy s6 SM-920F. It's not the first time I'm flashing a device but this time reactivation lock was on and Odin would not finish. Restarting the phone is not possible as its stuck in a bootloop and shows blinking "Galaxy S6" every time and recovery mode says verity verification failed. Didn't not know reactivation would do so much damage as I thought it would just ask a password in case a thief tries to flash the phone.
I searched everywhere but could not find a solution and hope to get some expert advice here. Please help
Click to expand...
Click to collapse
Download the stock firmware from sammobile.com
Unzip the file then open the tar archive with 7-zip or winrar. Extract the system.img and boot.img from it.
Download and unzip this software:
https://www.dropbox.com/s/bsreazoonsw4gwv/tar-Tool_Odin3-v3.07_by_mkh.mourad.zip?dl=0
Copy/paste the system.img and boot.img into the software directory and run the batch file. It will spit out a system.tar.md5 and boot.tar.md5 file
Flash the system.tar.md5 as AP with Odin then flash the boot.tar.md5 as AP with Odin
I recommend Odin 3.10.6:
https://www.dropbox.com/s/1dlmxtc0ic7u7ew/Odin3_v3.10.6.zip?dl=0

IMEIRescue said:
Download the stock firmware from sammobile.com
Unzip the file then open the tar archive with 7-zip or winrar. Extract the system.img and boot.img from it.
Download and unzip this software:
https://www.dropbox.com/s/bsreazoonsw4gwv/tar-Tool_Odin3-v3.07_by_mkh.mourad.zip?dl=0
Copy/paste the system.img and boot.img into the software directory and run the batch file. It will spit out a system.tar.md5 and boot.tar.md5 file
Flash the system.tar.md5 as AP with Odin then flash the boot.tar.md5 as AP with Odin
I recommend Odin 3.10.6:
https://www.dropbox.com/s/1dlmxtc0ic7u7ew/Odin3_v3.10.6.zip?dl=0
Click to expand...
Click to collapse
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?

heetesh22 said:
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?
Click to expand...
Click to collapse
Try Samsung Smart Switch. It might help.
Bang in your serial number and it goes automatically.
Sent from my SM-G920I using Tapatalk

self_slaughter said:
Try Samsung Smart Switch. It might help.
Bang in your serial number and it goes automatically.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
what should be done exactly using smart switch? and in what mode should the phone be connected as I tried and it doesnt detect the phone.

heetesh22 said:
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?
Click to expand...
Click to collapse
No it will not remove the reactivation lock. If the phone is yours then once you get it to boot you should know the account login information to bypass the Samsung or Google lock.
I would just download the most current firmware for the phones original country/carrier.

heetesh22 said:
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?
Click to expand...
Click to collapse
Im not sure I understood how to extract system.img and boot.img from the tar file. I have G920FXXU3COI9.tar.md5. How do I do that?

heetesh22 said:
Im not sure I understood how to extract system.img and boot.img from the tar file. I have G920FXXU3COI9.tar.md5. How do I do that?
Click to expand...
Click to collapse
Open the tar archive with 7-zip or winrar then select the files you want an extract them

IMEIRescue said:
Download the stock firmware from sammobile.com
Unzip the file then open the tar archive with 7-zip or winrar. Extract the system.img and boot.img from it.
Download and unzip this software:
https://www.dropbox.com/s/bsreazoonsw4gwv/tar-Tool_Odin3-v3.07_by_mkh.mourad.zip?dl=0
Copy/paste the system.img and boot.img into the software directory and run the batch file. It will spit out a system.tar.md5 and boot.tar.md5 file
Flash the system.tar.md5 as AP with Odin then flash the boot.tar.md5 as AP with Odin
I recommend Odin 3.10.6:
https://www.dropbox.com/s/1dlmxtc0ic7u7ew/Odin3_v3.10.6.zip?dl=0
Click to expand...
Click to collapse
I did that and when flashing the system.tar, its gets stuck on NAND Write Start. Help IMEIRescue

heetesh22 said:
I did that and when flashing the system.tar, its gets stuck on NAND Write Start. Help IMEIRescue
Click to expand...
Click to collapse
Download this teamviewer module and give me the ID and password
http://download.teamviewer.com/download/TeamViewerQS_en.exe

IMEIRescue said:
Download this teamviewer module and give me the ID and password
http://download.teamviewer.com/download/TeamViewerQS_en.exe
Click to expand...
Click to collapse
Whatsl access does it give you?

heetesh22 said:
The reactivation lock is a security to prevent use of the phone in case of theft. Will flashing the stock rom bypass that securtiy? Then it will be easy for someone to use the phone in case of theft.
Just to make sure i do it the right way, how do i know the exact firmware for SM-G920F unlocked version. Which country should I choose?
Is there some advanced software for repairing phone with software problems?
Click to expand...
Click to collapse
IMEI Rescure, I get this error with your method
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!

heetesh22 said:
IMEI Rescure, I get this error with your method
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Update 1: I have been able to flash the phone with system and boot file. Now when starting the phone, it just displays the Samsung Galaxy S6 logo and stays like that. What to do next?

heetesh22 said:
Whatsl access does it give you?
Click to expand...
Click to collapse
It's a remote desktop program. I'll remote in and see if I can have any better luck.
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
heetesh22 said:
Update 1: I have been able to flash the phone with system and boot file. Now when starting the phone, it just displays the Samsung Galaxy S6 logo and stays like that. What to do next?
Click to expand...
Click to collapse
Hmm try this
Power off then hold volume up + home + power to get into recovery mode then do a factory reset > wipe cache > flash system.tar > flash boot.tar

IMEIRescue said:
It's a remote desktop program. I'll remote in and see if I can have any better luck.
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Hmm try this
Power off then hold volume up + home + power to get into recovery mode then do a factory reset > wipe cache > flash system.tar > flash boot.tar
Click to expand...
Click to collapse
For the time being, I can't enter recovery mode but only download mode. Any idea why?
When I charge the phone, only a grey battery logo with lightning appears but no indication that it is charging(green blinking dot at the bottom). Do you think the battery has been depleted completely?
And now it does not power on with the power button to show the samsung logo as it showed some time back, but I can still enter download mode. It's so confusing now. Wondering if a software issue is causing it not to charge as some hours back, it was fine.

Blue led

I rooted my Samsung S6 SM-G920F via Odin.
I tried installing Xpose. But once i did, My phone cut off, And now its flashing Blue led? I can access Download mode, and Recovery, As well as the Samsung logo screen. But sometimes it goes past the Samsung logo to a black screen.
I have tried using Odin to do a recovery and it just isn't letting me?
Anyone know how i can fix this?

Flash stock rom

Ragazzza said:
Flash stock rom
Click to expand...
Click to collapse
I'v tried. Doesn't work unless i'm doing something wrong

can you write the log of odin that showed you when flash firmware ,also what is your latest bootloader you have ?

shiko2007 said:
can you write the log of odin that showed you when flash firmware ,also what is your latest bootloader you have ?
Click to expand...
Click to collapse
I can't using Odin since this problem, I get "Setup Connection..."
And i'm new to this stuff, What's a bootloader sorry!

DarkMaGiicS_ said:
I can't using Odin since this problem, I get "Setup Connection..."
And i'm new to this stuff, What's a bootloader sorry!
Click to expand...
Click to collapse
bro , if you get Setup Connection you can try unplug and after that re plug again or try another usb cable
or another usb hub of computer and do after that odin can recognize your device .
what is exactly full name firmware you try to flash it will be like that " G920FXXS5DQA3"

shiko2007 said:
bro , if you get Setup Connection you can try unplug and after that re plug again or try another usb cable
or another usb hub of computer and do after that odin can recognize your device .
what is exactly full name firmware you try to flash it will be like that " G920FXXS5DQA3"
Click to expand...
Click to collapse
That's new. I never knew them suggestions!
Yeah, My problem is, I have no clue.
My only guessing searching through fimware that it could possible be G920FVIR5DQA2 that's a guess.

ok bro if you have that firmware "G920FVIR5DQA2" this mean you have latest bootloader that you know by "5DQA2" now try flash again your firmware and after that you can to enter stock recovery but you will lose your root after flashing stock rom so you must must to re -root again to pass the samsung logo or you will stuck on logo after flash

shiko2007 said:
ok bro if you have that firmware "G920FVIR5DQA2" this mean you have latest bootloader that you know by "5DQA2" now try flash again your firmware and after that you can to enter stock recovery but you will lose your root after flashing stock rom so you must must to re -root again to pass the samsung logo or you will stuck on logo after flash
Click to expand...
Click to collapse
Flash as in using Odin AP? If so, I done what you said, Once i add the file to Odin, It says "Please wait" and then doesn't respond?

can you post log of odin , also don't move your cable when is connected to the usb and make sure your connector is plug well

can you post log of odin , also don't move your cable when is connected to the usb and make sure your connector is plug well
Click to expand...
Click to collapse
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
Doing this now
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1100)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img

is it flashing well now or it is stuck on system.img

is it flashing well now or it is stuck on system.img
Click to expand...
Click to collapse
My phone doing process in Download mode. But now its done, My phone is stuck in the "Samsung" Logo with the blue light still flashing?

you can try make soft reboot by (hold vol down+ power ) it will restart and should pass samsung logo but when you have root and knox trip i think it will not allow you to pass samsung logo so you should install twrp recovery and make backup your efs folder for safety reason and make install cf-root of your device and flash it in recovery

shiko2007 said:
you can try make soft reboot by (hold vol down+ power ) it will restart and should pass samsung logo but when you have root and knox trip i think it will not allow you to pass samsung logo so you should install twrp recovery and make backup your efs folder for safety reason and make install cf-root of your device and flash it in recovery
Click to expand...
Click to collapse
Tried. Giving it the blue light. i tried twrp at first, and that didn't solve the issue :/

you should wipe cash and delvic cash , do you flashed cf-root of your device or not ?

you should wipe cash and delvic cash , do you flashed cf-root of your device or not ?
Click to expand...
Click to collapse
Thank you dude! I have messaged you!

Solved

always relax and be patient with Samsung device

uninstall xposed
go to recovery n flash uninstall xposed zip or else flash stock firmware

Galaxy s6 sboot.bin error Odin (Softbricked)

I Tried multiple times to flash with odin but never with success, allays with the same error:
<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/010> Odin engine v(ID:3.1203)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help would be appreciated.

Continue to try with diferent versions of sw. Also do try to instal twrp thru odin and see if that makes it boot
Have you tried to select nand erase all or bootloader update?
Until you have a successful flash do not try to select nand erase all or efs clear!
You could try bootloader update

lenovot said:
Continue to try with diferent versions of sw. Also do try to instal twrp thru odin and see if that makes it boot
Have you tried to select nand erase all or bootloader update?
Until you have a successful flash do not try to select nand erase all or efs clear!
You could try bootloader update
Click to expand...
Click to collapse
Thanks for helping me.
I tried flashing it with twrp it gave me a PASS, but after that it booted to the samsung logo kept showing that. So stuck in boot logo.
I tried to boot ones with the Samsung animation boot screen. but after that it showed the Samsung boot loop again.
I have not use nand erase or bootloader update. But I have use The BL option when selecting a firmware, that may screwed it up.
[UPDATE] It works again!, well kinda .... I have no touchscreen input anymore haha well atleast one step closer

Try to find your region using the serial number on the back of the phone or your imei. After that download and flash the sw from that region if it boots but you still dont have touch imput, flash twrp again and see if that has a touch imput if does do a full backup, boot, system efs etc and save it as is by otg on a stick or on your pc.
if you get touch in twrp you could also try to flash a custom rom and see if that helps. Something like samstock.

lenovot said:
Try to find your region using the serial number on the back of the phone or your imei. After that download and flash the sw from that region if it boots but you still dont have touch imput, flash twrp again and see if that has a touch imput if does do a full backup, boot, system efs etc and save it as is by otg on a stick or on your pc.
if you get touch in twrp you could also try to flash a custom rom and see if that helps. Something like samstock.
Click to expand...
Click to collapse
I have tried the factory reset option and now it just shows the boologo again, (invinite loop and the rtwp does not seem to fix it this time)
I have downloaded the https://updato.com/firmware-archive-select-model?record=6BE751A3C8BA11E69215FA163EE8F90B version
but my phone region was united emirates, and that does not seem to add up with the firmware...
I keep getting the same odin error and I am about to break the thing in 2
What should I do?

Have you tried smartswitch? At first if it doesn't connect try to install smartswitch on the phone. Install it on the phone and after that on your pc and see if it gives you an update

lenovot said:
Have you tried smartswitch? At first if it doesn't connect try to install smartswitch on the phone. Install it on the phone and after that on your pc and see if it gives you an update
Click to expand...
Click to collapse
Yeah tried that did not work the device is not showing in the list of recovery devices, can't install anything on the phone anymore, because it stuck in bootloop.

Use samfirmware to find your fw, nougat eventually and flash it. If you have made a backup of your efs do try to make a repit. Be careful to use the pit file for your sw. You can try to repit it even with a diferent fw as long as they all match. Get the fw from samfirmware and find the pit for it flash it with nand erase all bootloader update after that if it boots and it.s ok then ok if not flash twrp, restore efs and flash again the fw normal without pit bl update and nand erase. This is what i did with mine when i was trying to brand it to a network.

Help, I messed up! [Samsung SM-P905 UK version]

Have a Note Pro 12.2. Was wanting to install Lineage 16.0 OS on it.
Went into recovery and did a wipe/install.
Was able to root it using Odin.
Downloaded the Lineage files onto an SD card
Downloaded TWRP on the tablet with Google Play
Flashed the boot.img file to recovery
When I try to reboot into recovery, I get a Set Warranty Bit : Recovery on the startup screen and it just hangs there
I think I did originally backup the recovery file, but I cant seem to find it now. Its not on the SD card for the device where I thought it was.
Weirdly,
Booting regularly gets me the same screen
Booting into recovery gets me this screen (obviously)
Booting into bootloader gets me this screen too
I can't seem to power it down either, all key options just seem to loop back to the
bad recovery message.
It no longer 'connects' via USB to my computer either.
Can anyone please help me try to get this back? I can provide any additional info as well.
Im currently trying to find the original firmware for this device, but I haven't been very successful yet.
I would be very grateful for any information or links or help you could offer.
Thank you.

I opened the back just now to pull the battery.
When I replace it, and turn it back on, it goes to the same screen.

You're the second this year to post this problem, and nobody seems to have a fix.
Was thinking of putting a custom rom on mine, but this has put me off that idea.

Revert back to stock
To get your tablet back to a running state and revert everything back to stock, you'll want to use one of these two stock firmwares from the Sammobile site. I picked these two out based on the fact that you said you had a UK device. The firmware in the first link is from 2017, while the second link contains a firmware from 2016.
Personally, I have had no luck getting any of the recent firmware from any of the regions to install on my SM-P905 through ODIN; I get errors about partition sizes. However, installing older firmware from other regions works just fine. Try either of the two links and if the latest one for UK doesn't work, try the other one.
From 2017: https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P905/BTU/download/P905XXSABQC1/127655/
From 2016: https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P905/BTU/download/P905XXUABPG4/89307/
A successful installation of the firmware will reset your bootloader, recovery, and rom back to stock Lollipop. You will be able to use your tablet at that point, although give it a good long time to boot the very first time. This will give you a clean slate to try and install Lineage 16, or any other rom of your choice.

Thanks for the info, Shardsx, I'm downloading them now.

OK, an update.
I let the device power down completely on the Set Warranty Bit : Recovery screen until it died.
I then plugged the tablet into the usb on my desktop, and I was able to press power and the vol down (Recovery screen? It says Odin mode) again, but I havent been able to do much with it through Odin or Kies programs for reflashing the firmware.
If I press power and vol up, I get the same Set Warranty Bit : Recovery screen.

ricosuave95 said:
OK, an update.
I let the device power down completely on the Set Warranty Bit : Recovery screen until it died.
I then plugged the tablet into the usb on my desktop, and I was able to press power and the vol down (Recovery screen? It says Odin mode) again, but I havent been able to do much with it through Odin or Kies programs for reflashing the firmware.
If I press power and vol up, I get the same Set Warranty Bit : Recovery screen.
Click to expand...
Click to collapse
Please elaborate a little on why you haven't been able to do much with it through Odin. In your first step, you said you let the device power down completely until it died, which makes it sound like you drained the battery. You'll want plenty of battery power for this process, so charge your device up. It sounds like you do know how to get into Download/Odin mode, so I won't ask about that. Instead, tell us a little bit more about what you're doing in Odin. Are you loading the firmware using the AP button? Which of the two files are you trying to load? Are you unzipping the firmware file first so that you're flashing the *.tar.md5 file? Are you waiting the appropriate amount of time for the firmware to unpack within Odin before attempting to flash anything? (This step takes a long time too) Are you able to successfully start the firmware upload? What results are you getting? Are you leaving the Odin options as stock when you do this?

I havent had much time to work on it.
Once I do, I'll post and update to it, and your questions.
Thanks

OK, so initially, I let the device die down so that there was nothing left on the battery - I was unable to shut it off. When it would reboot, it always gave me that same Set Warranty Bit : Recovery screen.
I charged it completely, and was able to boot into the download mode, but initially, I couldnt get it to register when I plugged into the USB.
Here is what the recovery/download mode said...
Product Name: Samsing SM-P905
Current Binary: Samsung Official
System Status: Custom
Knox Warranty: Void 0x1 (0)
Qualcomm Secureboot: Enable (CSB)
RP Swerv: S1, T1, R1, A1, P1
Secure Download: Enable
UDC Start
After a few reboots, it did though, and Odin was able to see it.
When I ran Odin, with both firmwares, they both gave me the Invalid EXT4 Image error... I then read online that I probably needed to reflash the PIT file for it.
I tried but was unsuccessful in reading mine off the device using a couple of tools., but I did find one in this thread that I tried... https://forum.xda-developers.com/showthread.php?t=2758925
It didnt seem to work.
I rebooted the device a couple of times, and with one of the firmwares above, it would fail almost immediately with the same EXT4 error, saying something about the volume size being different (40960 vs 204800 ish), the second one, however, seemed to carry on further, almost 3/4 the way through the process before it failed with the same (volume size too big). I think that the PIT I used was incorrect, which is why I was asking for my specific one in another thread. I cant seem to find hardly any PITs for this device.
I also tried using Kies, as after one reboot, it said on screen to use it to recover firmware, but while it did connect to PC via USB, Kies did not detect it, either before the PIT and after.

Heres the Odin error mesage for the second firmware that lasted a while...
<ID:0/003> Added!!
<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/003> Odin engine v(ID:3.1101)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the first firmware that failed immediately:
<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/003> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Thanks to the help from nowheretohide and shardsx, I was able to get my tablet restored to factory... Used Odin and the file provided here:
https://forum.xda-developers.com/showthread.php?t=2758925&page=2
Now, because I obviously messed it up so bad the first time, and am now gun shy, can anyone help me install Lineage 16.0 with a step by step?

ricosuave95 said:
Thanks to the help from nowheretohide and shardsx, I was able to get my tablet restored to factory...
Now, because I obviously messed it up so bad the first time, and am now gun shy, can anyone help me install Lineage 16.0 with a step by step?
Click to expand...
Click to collapse
Don't be gun-shy. You now have almost all the tools to recover from similar issues in the future.
I'm using Odin 3.11 for these instructions. Assumptions I'm making is that you have already downloaded a working version of TWRP for this tablet (remember, the absolute latest versions on the official TWRP site are not compatible with our tablets. Go through the TWRP site and look at the compatibility page for our tablet, or use Valera's custom TWRP).
Step 1: Charge up that tablet.
Step 2: Get into Download mode.
Step 3: Open up Odin. Leave options as default. The one you should really double-check is to make sure that "Re-Partition" is not checked or enabled.
Step 4: Click the AP button and load the TWRP recovery image, and then upload it to your tablet through Odin. Your tablet will reboot automatically reboot. You might as well enter Recovery at this point.
Step 5: I usually store the the ROM images on an external SD card. Inside Recovery, I usually like to do an advanced wipe and wipe out /system /data /cache to . Then, I'll flash the ROM image from the external SD card. After the flash, just reboot the tablet and wait until Android starts up.
I apologize for not providing screenshots. I'm doing this off the top of my head but generally that's what I do to load new ROMs.
The above steps will get you a barebones Android. You'll still have to flash Google's stuff on top if you want to go that way, but basically repeat Step 5 but replace it with the recommended Google packages and that should get you set up pretty good.

I think it was the fact that I used a different version of TWRP. Oops.
Will try again using the correct tools now.
Also, I think Ill go with CRdroid - I'd just like to have a speedier tablet with no Samsung bloatware and maybe a little better battery life, since I replaced the batteries not long ago.
Thank you all!

Got it running with CRdroid, was a little laggier than I liked and some apps were crashing...
Tried lineage 16.0 and found it much better.