Database Info

Please Please Help. Unusual FAIL in ODIN. Softbrick.

Hey folks,
I was trying to root my never before rooted s6 today (64 gb 920 I) using the uni-kernel method using odin for 5.1.1. I put the kernel into AP, and it failed after some seconds thus resulting in the blue screen which says "error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software."
I tried that and smart switch didn't recognise my device (maybe because USB debugging wasn't on).
Thus I downloaded a stock recovery for my device and I thought I would flash it via ODI. Things go well and the progress bar is 3/4th of the way through on my device and it suddenly says FAIL (shown below). I've tried with ODIN 3.10.6 and with 3.10.7 with the same results
<ID:0/003>Get PIT for Mapping
<ID:0/003> Firmware update Start!!
<ID:0/003> cm.bin <ID:0/003>
sboot.bin
<ID:0/003>NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) Operation failed.
<OSM> All threads completed. (succeed 0/failed 1)
What's unusual about this (to the best of my knowledge through forum search. I could be wrong and this could be common. If so I apologise) is that I've seen help threads about Odin failing at hidden.img or NAND Write Start but not during system.img. Does the fact that it's failed during system.img in particular tell us something?
Also, I can't access stock recovery, just the download section.
No clue why it's doing this. I would appreciate any help possible.
Thanks so much in advance. This means a lot.

Your current phone's firmware CSC should be same or within the region CSC of your downloaded firmware.
Hidden.img do have different partition size per Country/region. If you flash a not supported firmware, it will fail.
I.e., if your from France, just download the France firmware.so that you wont need to flash a pit file for your phone.
You can Search here at forum with keyword galaxy s6 pit file.
Or probably, your pc <> phone connection is unstable. Be sure it is connected properly, the usb cable should be in good performance etc.

I had the same happening. Don't sweat it really, no need to use that Smart Switch thing, Odin should still see the phone anyway, so just go ahead and flash a different image from Sammobile, possibly use one for your country and you'll be good.

[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.

[Help] Samsung Galaxy S7 (SM-G930W8) bricked by Nougat update?

UPDATE: I wasn't able to fix it and ended up having to send it in to Samsung. There was something wrong with the motherboard and they fixed it pretty quickly. It only took about a week to get it back.
Phone: Samsung Galaxy S7
Phone Model: SM-G930W8
Carrier: Sasktel (Canada)
My girlfriend's phone started spontaneously bootlooping this morning. The timing seems to correspond with the release of Nougat in our area. My assumption is that the update got rolled out to her phone and has somehow softbricked it.
I tried booting into recovery and selecting "Wipe data/factory reset" but I keep on getting the following message:
-- Wiping data. . .
E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset Done. . .
Data wipe failed.
-- Applying Multi-CSC. . .
Applied the CSC-code : BWA
Successfully applied multi-CSC
-- Set Factory Reset done. . .
Successfully verify for dmverity hash tree
-- Start Factory Reset. . .
-- Wiping Data. . .
Formatting /data. . .
E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset done. . .
Data wipe failed.
Click to expand...
Click to collapse
I've tried choosing "Wipe cache partition" but that doesn't seem to have an effect on the issue.
Next I tried to use Odin to flash the firmware from here
I tried flashing G930W8VLU2BQB6 (Android 7.0) as well as G930W8VLU2APK3 (Android 6.0.1) via Odin v3.11. Here is the log from Odin:
<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.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After the phone restarts it goes straight to the Android Recovery screen. If I choose the "Reboot now" option the phone will boot to a black screen. I'm able to adjust volume and the soft keys light up but I can't do anything but click the reset button at the bottom. The black screen message says:
Device storage corrupt
The data partition has been corrupted. You need to reset your device to factory default settings. This will erase all your data.
Click to expand...
Click to collapse
Then there's a button at the bottom that says "RESET". After rebooting the phone goes to a blue screen with an android logo and the phone just says "Erasing". After a few minutes I get an error screen of a dead Android guy on a blue background with a big yellow triangle with an exclamation mark above him. Then the phone reboots and I just get the same error message from above that says
E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
E: Data wipe failed
Click to expand...
Click to collapse
I've also tried installing TWRP via Odin but I get the following message on the phone:
Custom Binary(RECOVERY) Blocked by FRP Lock
Click to expand...
Click to collapse
Here is the log from Odin:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
So yeah, I'm completely stumped and any help would be greatly appreciated.

BloodAudible said:
Phone: Samsung Galaxy S7
Phone Model: SM-G930W8
Carrier: Sasktel (Canada)
My girlfriend's phone started spontaneously bootlooping this morning. The timing seems to correspond with the release of Nougat in our area. My assumption is that the update got rolled out to her phone and has somehow softbricked it.
I tried booting into recovery and selecting "Wipe data/factory reset" but I keep on getting the following message:
I've tried choosing "Wipe cache partition" but that doesn't seem to have an effect on the issue.
So yeah, I'm completely stumped and any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi mate
When you flashed with odin what did you use CSC or home_csc file?
CSC will factory reset and should and should clean all your partitions, if you flash a differnt CSC than the one you have you may have to check re-partition option under PIT (odin) , check here
Factory reset before you flash...

MAX 404 said:
Hi mate
When you flashed with odin what did you use CSC or home_csc file?
CSC will factory reset and should and should clean all your partitions, if you flash a differnt CSC than the one you have you may have to check re-partition option under PIT (odin) , check here
Factory reset before you flash...
Click to expand...
Click to collapse
I tried using both CSC and home_csc but the result is the same. I've tried checking re-partition under options as well. I'm not sure what you meant by PIT.
Factory reset doesn't work as per my original error.

try to flash 6.0.1 with pit file and make repartition in odin

AntonPres said:
try to flash 6.0.1 with pit file and make repartition in odin
Click to expand...
Click to collapse
Will try this once the (very slow) download finishes. Are PIT files specific to versions of Android or is it just per model? I found a PIT file here

BloodAudible said:
I tried using both CSC and home_csc but the result is the same. I've tried checking re-partition under options as well. I'm not sure what you meant by PIT.
Factory reset doesn't work as per my original error.
Click to expand...
Click to collapse
AntonPres said:
There is only one pit for g930w8 model, so no need to worry about csc version. If you need fast download link for firmware (google drive link) you can check here: https://simunlockremote.com/galaxy-s-series-firmware/
Click to expand...
Click to collapse
Hi mate
PIT = Partition Information Table , it has the information need to format all partition , CSC file contains the right partition

yes, but as you can see on pit list you can notice that pit files are for specific csc

AntonPres said:
yes, but as you can see on pit list you can notice that pit files are for specific csc
Click to expand...
Click to collapse
That is right , as I said the CSC has the right PIT table also what is said in the link i posted
Same information different words
6. Installing another country CSC or a network CSC will usually need the system partition size changing.
For this select PIT and this setting
If you are installing a multi csc firmware, and your existing CSC is in that firmware, then DO NOT select Re-partition.
You can check if your firmware is multi-csc by installing this app:

AntonPres said:
There is only one pit for g930w8 model, so no need to worry about csc version. If you need fast download link for firmware (google drive link) you can check here: https://simunlockremote.com/galaxy-s-series-firmware/
Click to expand...
Click to collapse
Thanks for the link. Finding links for these firmwares is brutal.
I downloaded this one and flashed it but I'm still stuck in the same loop. It always ends up on the blue screen that says "installing system update" then it will change to "Erasing" before ending up with the dead android and exclamation point. And then it boots to Recovery and says Data wipe failed. Any other ideas? Recovery does say Android version 6.0.1 again, but same issue as before.

If flash didn't helped your phone might have motherboard issues

AntonPres said:
If flash didn't helped your phone might have motherboard issues
Click to expand...
Click to collapse
I've asked for help in a few places and everyone seems to come to that conclusion. What a bummer. She only got the phone back in December.

Many s7 models have been reported with motherboard issues, looks like samsung have made some mistakes

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.