Database Info

Help with TWRP

Hi,
I am trying to install TWRP onto my S6, however everytime in Odin it fails.
I've done a fresh wipe of my phone, got Odin v3.10.7 installed on my pc with twrp-2.8.7.2-zeroflte.img.tar and twrp-3.0.2-0-zeroflte.img.tar (tried both incase the newest one didnt work.)
I put my phone into Download Mode and the plugged it into my laptop, and then chose the correct file under the AP section of Odin.
<ID:0/004> Added!!
<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> 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> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I notice in the top left it says in green letters: Custom Binary(RECOVERY) Blocked By R/L
Tried restarting my phone etc but nothing seems to change it.
Can someone help?
Cheers

Okay so I managed to get Odin to work for the TWRP file - however it hasn't changed anything in my recovery menu...
I read on https://twrp.me/devices/samsunggalaxys6.html that I need to disable Fastboot as it wipes over the TWRP when booting... so after googling how to do that, people say to go into power settings and turn it off. But there are no settings for it.
How can I disable fastboot so that the TWRP will stay installed?

craigsup said:
Okay so I managed to get Odin to work for the TWRP file - however it hasn't changed anything in my recovery menu...
I read on https://twrp.me/devices/samsunggalaxys6.html that I need to disable Fastboot as it wipes over the TWRP when booting... so after googling how to do that, people say to go into power settings and turn it off. But there are no settings for it.
How can I disable fastboot so that the TWRP will stay installed?
Click to expand...
Click to collapse
No official TWRP is compatible with the MM bootloader on the S6 yet. I imagine this is your issue?

2ZE said:
No official TWRP is compatible with the MM bootloader on the S6 yet. I imagine this is your issue?
Click to expand...
Click to collapse
So how can anyone root their S6 with 6.0.1?

craigsup said:
So how can anyone root their S6 with 6.0.1?
Click to expand...
Click to collapse
I used CF-AutoRoot to get the initial root, then flashed a custom 3.0.2.2 TWRP (available from the official TWRP thread... Look for the idlekernel link). Works great
Bigbiff seems to have an official MM version in the pipeline, so just flash that when it's released in the next month or two
Oh, and you can just flash a custom kernel that comes with a root

2ZE said:
I used CF-AutoRoot to get the initial root, then flashed a custom 3.0.2.2 TWRP (available from the official TWRP thread... Look for the idlekernel link). Works great
Bigbiff seems to have an official MM version in the pipeline, so just flash that when it's released in the next month or two
Oh, and you can just flash a custom kernel that comes with a root
Click to expand...
Click to collapse
So if I use CF-AutoRoot that will modify the recovery menu so that I can use any ROM I want?
I want to use http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423
So I'd use CF-AutoRoot and then in the new recovery menu select the zip files from the above link?

craigsup said:
So if I use CF-AutoRoot that will modify the recovery menu so that I can use any ROM I want?
I want to use http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423
So I'd use CF-AutoRoot and then in the new recovery menu select the zip files from the above link?
Click to expand...
Click to collapse
CF-AutoRoot only installs a temp recovery to flash SuperSU. It then reinstates the stock recovery, so no.
Root it with CF-AutoRoot, flash the custom TWRP that currently works with MM, make a back up, then go mad

Need some Serious help...

Hi peeps.
Ive really messed up my phone trying to root it...
Ive deleted the OS by accident. Ive downloaded a couple off the internet:
G920FXXU3DPFA_G920FTEF3DPF1_G920FXXU3DPF1_HOME.tar.md5
G920FXXU1AOCV_G920FTEF1AOC1_G920FXXU1AOCW_HOME.tar.md5
when i try to install either of these on Odin3 they just Fail.
I can access the download part and 'team win recovery project' on my phone
for some strange reason my pc now also says my phone is SM-G920S. But its a SM-G920F
From ODIN:
<ID:0/004> 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/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> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im really stuck ive been trying for hours and gotten no where

Kevin12121 said:
Hi peeps.
Ive really messed up my phone trying to root it...
Ive deleted the OS by accident. Ive downloaded a couple off the internet:
G920FXXU3DPFA_G920FTEF3DPF1_G920FXXU3DPF1_HOME.tar.md5
G920FXXU1AOCV_G920FTEF1AOC1_G920FXXU1AOCW_HOME.tar.md5
when i try to install either of these on Odin3 they just Fail.
I can access the download part and 'team win recovery project' on my phone
for some strange reason my pc now also says my phone is SM-G920S. But its a SM-G920F
From ODIN:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1101)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
boot.img
NAND Write Start!!
cache.img
cm.bin
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Im really stuck ive been trying for hours and gotten no where
Click to expand...
Click to collapse
What version of Android were you running? Was it a stock ROM or a custom ROM? Also, where did you download the stock firmwares from?
Also, when you boot to download mode what does it say your device model is?
If you can still access TWRP, boot to your recovery, connect your device to your PC with the USB cable and then download a custom ROM for you device and then transfer the downloaded ROM to your internal storage. Or, you can save a downloaded ROM to a USB OTG device and use TWRP to mount the OTG device so you can flash a ROM.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
What version of Android were you running? Was it a stock ROM or a custom ROM? Also, where did you download the stock firmwares from?
Also, when you boot to download mode what does it say your device model is?
If you can still access TWRP, boot to your recovery, connect your device to your PC with the USB cable and then download a custom ROM for you device and then transfer the downloaded ROM to your internal storage. Or, you can save a downloaded ROM to a USB OTG device and use TWRP to mount the OTG device so you can flash a ROM.
Click to expand...
Click to collapse
Hi, thanks for the response, i was on the most up to date version of marshmallow 6.0.1. i downloaded the 2 firmwares mentioned above from random sites i found i cant remember. both are similar size 1.8GB Zipped.
Im currently downloading another from samsung updates site but its going to take 8 hours to download
When in download mode the model is SM-G920F
Ill have a look for custom roms now...

i downloaded alliance rom. installed it successfully. but my phone just opens up twrp....
Im having a nightmare

Kevin12121 said:
i downloaded alliance rom. installed it successfully. but my phone just opens up twrp....
Im having a nightmare
Click to expand...
Click to collapse
When you installed Alliance ROM, did you perform your "WIPES" in TWRP?
Do this:
Boot to recovery
Select - Wipe
Select the check boxes for:
Dalvik Cache
System
Data
Cache
Do not select Internal Storage because that is where your ROM will be saved unless you are transferring the downloaded ROM from your PC to your device.
Try these steps and let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
When you installed Alliance ROM, did you perform your "WIPES" in TWRP?
Do this:
Boot to recovery
Select - Wipe
Select the check boxes for:
Dalvik Cache
System
Data
Cache
Do not select Internal Storage because that is where your ROM will be saved unless you are transferring the downloaded ROM from your PC to your device.
Try these steps and let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah i done the wipes, Tried it again but this time ticked all the boxes and transfered the rom back.
Now the screen just stays on the start up 'Samsung galaxy S6. Powered by android'
I dont get it...

Kevin12121 said:
Yeah i done the wipes, Tried it again but this time ticked all the boxes and transfered the rom back.
Now the screen just stays on the start up 'Samsung galaxy S6. Powered by android'
I dont get it...
Click to expand...
Click to collapse
Okay, now that the ROM attempts to boot, go back to recovery and select Wipe - Factory Reset and attempt to boot again.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Okay, now that the ROM attempts to boot, go back to recovery and select Wipe - Factory Reset and attempt to boot again.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Still nothing... ill wipe it completely and try again and leave it on the startup screen to see if it loads

fast69mopar said:
Okay, now that the ROM attempts to boot, go back to recovery and select Wipe - Factory Reset and attempt to boot again.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried a different rom, TyrannusRomV28.1.
Now i get past the first samsung bit i mentioned earlier, now its just got samsung on the screen pulsing...

Kevin12121 said:
I tried a different rom, TyrannusRomV28.1.
Now i get past the first samsung bit i mentioned earlier, now its just got samsung on the screen pulsing...
Click to expand...
Click to collapse
How long did you let it sit and attempt to boot. The installation instructions say it will take around 10 minutes to boot. It will take this long because the ROM is deodexed.
Sent from my Nexus 6 using XDA-Developers mobile app

Hey there @Kevin12121
If I am to understand correctly....you are saying you deleted the OS . You probably did this with TWRP. Why not flash another rom like XtreStoLite 3.3.1.. I don't think Alliance will work due to bootloader . If Odin fails then you probably downgrading.

fast69mopar said:
How long did you let it sit and attempt to boot. The installation instructions say it will take around 10 minutes to boot. It will take this long because the ROM is deodexed.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey, I left it like that over night and when i got up today it was working!
Thanks for your help! i thought id completely bust my phone! :good::good::good::good:

yasteellutch said:
Hey there @Kevin12121
If I am to understand correctly....you are saying you deleted the OS . You probably did this with TWRP. Why not flash another rom like XtreStoLite 3.3.1.. I don't think Alliance will work due to bootloader . If Odin fails then you probably downgrading.
Click to expand...
Click to collapse
Yes thats what i did... deleted it on TWRP. I used tyrannus rom and thats worked! Panic over, Thanks for you help!:good:

Kevin12121 said:
Yes thats what i did... deleted it on TWRP. I used tyrannus rom and thats worked! Panic over, Thanks for you help!:good:
Click to expand...
Click to collapse
Np

Kevin12121 said:
Hey, I left it like that over night and when i got up today it was working!
Thanks for your help! i thought id completely bust my phone! :good::good::good::good:
Click to expand...
Click to collapse
Hey man. I'm glad it's working. Deodexed ROM's take longer to boot than an Odexed ROM. I've seen some ROM's take almost 30 minutes to boot on my Galaxy S5 SM-G900P. It can get a little scary if you don't know that is what is happening. Good job on your patience.
Sent from my Nexus 6 using XDA-Developers mobile app

[SM-G920F] Stuck on Samsung Logo Powerd by Android After Crash

Device: SM-G920F
ROM: NanoROM-5.6.0~beta2-20160916-920.5FD-PDP
Android-Version: 6.0.1
Based On TouchWiz
I dont know which information i should give to my device
Problem:
Hello im not so new i read a lot here and at this problem its the same.
I have the same problem as this guy but there is since a few months no updates and not so detailed device info
Last evening my phone crashed i used Chromecast-app/webcasterapp and chrome at this moment.
Ive got 2 new apps Chromecast-App and FireTV app.
So sinced it crashed i thought it just reboots but it was stuck since half an hour.
iv tried a Hard reboot and tried to reboot into Recovery but it just stucks on the "Samsung Galaxy S6 Powerd by Android" screen
i just can boot into Download / odin mode
What ive tried:
Flash over Odin3_v3.12.3:
TWRP 3.0.2.0 (No Errors)
G920FXXU2BOFJ_G920FOXA2BOFJ_XEF(4File)_ChoiMobile.VN (Not Matching Version Error)
BL-6.0.1-G920FXXU4DPHB (No Errors)
2016-09-19-6.0.1-PHN-G920FXXU4DPIL-4teilig (*4 Files; No errors )
Flashing Over Odin_v3.10.0 just stucks on Writing Nand
Flashing Orginal Over Smart Switch ends With no Errors
I don´t know which version is the right ;( i just know its an G920FXX but is there so much diffrent ?
If you need any more information please tell me

Update
I just noticed that i dont have a charging screen at all
Nobody got a clue or an Idea what i could try else ?

I would say this:
1. Reflash TWRP with ODIN.
2. Download stock rom from sammobile for your particular device.
3. Enter recovery, wipe and install the stock rom.
Had same issue as you, trial and error got me the solution
Do not try to flash rom in ODIN

I tried to flash twrp-3.0.2-1-zeroflte.img.tar so many times odin -> pass
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> recovery.img
<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)
Click to expand...
Click to collapse
but then when i try to enter twrp there is no just this stupid screen
i hate it when developers give no usable error messages :crying:

tr1g4d0n said:
I tried to flash twrp-3.0.2-1-zeroflte.img.tar so many times odin -> pass
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> recovery.img
<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)
but then when i try to enter twrp there is no just this stupid screen
i hate it when developers give no usable error messages :crying:
Click to expand...
Click to collapse
Are you holding down the button combination long enough to get into recovery?

Usually if a phone is stuck at logo, in 90% of cases DRK is messed up, but it will only show in stock recovery.
If knox is triped, try flashing custom kernel e.g. CF autoroot, which will bypass the problem, or it can be fixed with a box.
If it is not, I don`t know how to fix it.
You can try emergency initialization via Smart Switch with sn of the phone and see what happens on stock fw. (you can check my threads, I made a guide for SS initialization)

MossadPhil said:
Are you holding down the button combination long enough to get into recovery?
Click to expand...
Click to collapse
I holde it up to 2 Minutes so i think yes i do
and i often use recovery so i think i push it right
brenner650 said:
Usually if a phone is stuck at logo, in 90% of cases DRK is messed up, but it will only show in stock recovery.
If knox is triped, try flashing custom kernel e.g. CF autoroot, which will bypass the problem, or it can be fixed with a box.
If it is not, I don`t know how to fix it.
You can try emergency initialization via Smart Switch with sn of the phone and see what happens on stock fw. (you can check my threads, I made a guide for SS initialization)
Click to expand...
Click to collapse
as you can see at my first post i tried the initialization via smart switch and stock rom flashing
but i will try the custom kernel and CF autoroot when i find it on xda
could you explain me what DRK is and what you mean with "or it can be fixed with a box." what is a box?
Thanks anyway :good:

tr1g4d0n said:
as you can see at my first post i tried the initialization via smart switch and stock rom flashing
but i will try the custom kernel and CF autoroot when i find it on xda
Click to expand...
Click to collapse
CF auto root: https://autoroot.chainfire.eu/
tr1g4d0n said:
could you explain me what DRK is and what you mean with "or it can be fixed with a box." what is a box?
Thanks anyway :good:
Click to expand...
Click to collapse
I think some people here with more technical expertise than me, can answer that question more precisely, or you can try google it, and box is a professional repair tool, like Octopus/Octoplus, Z3X, etc. mostly used by 3rd party repair shops.

so the last days i tried to flash many different versions of samsung stock: rom, kernel, bootloader; and i have tried to flash auto root and twrp custom rom
nothing helped =(
now i try octopus/plus samsung

Download kies - samsung firmware updater ( google for it ) and install the latest firmware, this in most of the cases rezolves any software related problem.
After that you can root again and install witch custom rom you want.

The last day´s i tried almost everything. Nothing helped =(
Now my last hope is the warrenty. If the bill is smaller as 100€ i will pay it otherwise i will buy the Nexus 5x
Thank you very much for each advice !

MossadPhil said:
I would say this:
1. Reflash TWRP with ODIN.
2. Download stock rom from sammobile for your particular device.
3. Enter recovery, wipe and install the stock rom.
Had same issue as you, trial and error got me the solution
Do not try to flash rom in ODIN
Click to expand...
Click to collapse
OK, so how do I flash the firmware from sammobile since it's a tar/md5 and wont flash in twrp?

ivyhole said:
OK, so how do I flash the firmware from sammobile since it's a tar/md5 and wont flash in twrp?
Click to expand...
Click to collapse
You only flash TWRP with ODIN.
Last line of my message said do not try to flash rom with ODIN. ????

Galaxy s7 stuck in bootloop and can't flash stock/recovery and unable to recover

Hey guys, hoping I can get some assistance on my phone which I've hit the limits of my knowledge on. Basically after rooting and trying to go back to custom I think I've corrupted my recovery as well as boot partition as the phone is boot looping and I'm getting the following message when trying to load the recovery:
Recovery is not seandroid enforcing
I've tried using ODIN to flash stock firmware as well as TWRP however as soon as I tell ODIN to start it reboots the phone and then disconnects and fails. I've even unticked "Auto-Reboot" under options however this makes no difference.
I just want to get my phone booting again and am sure if I can just restore and replace the recovery partition I can get the phone working again but am unsure what else I can do at this point?
I'm unable to connect via ADB or Fastboot as the device reboots before I get that far but I know my pc is seeing the phone in download mode. I've tried multiple USB cables including an official Samsung cable and has made no difference. I've tried ODIN 3.12 and 3.10.
ODIN 3.10 states the following logs:
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and ODIN 3.12 shows:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003>
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
If I could find a way to install the recovery files then I should be set to finish this off but my Google-Fu is failing me and I'm unable to find a solution to this issue now.

Hi,
Is your phone an original Samsung?
Maybe you get a fake. Where did you get it? Check your phone model number (sm-g.......)

It's official, got the box and everything.

Seriously wish you guys would take your time when this happens do you have the right twrp recovery? just flash that in odin then put a custom rom on your phone zip file sd card then once you have a custom rom on then go into download mode on your phone then flash all the file from stock rom in odin

How can I flash the recovery when the phone reboots as soon as I click start and it fails? Or are you saying its doing that because the TWRP isn't the correct version?

Outcast6 said:
How can I flash the recovery when the phone reboots as soon as I click start and it fails? Or are you saying its doing that because the TWRP isn't the correct version?
Click to expand...
Click to collapse
use this version
twrp-3.0.2-4-herolte.img download that file dont unpack it just place it in ap section of odin make sure your phone is in download mode! once that is done put a custom rom on your phone after that just flash all the files from a stock rom dont delete anything off your phone just put in download mode again!
---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------
dan110000 said:
use this version
twrp-3.0.2-4-herolte.img download that file dont unpack it just place it in ap section of odin make sure your phone is in download mode! once that is done put a custom rom on your phone after that just flash all the files from a stock rom dont delete anything off your phone just put in download mode again!
Click to expand...
Click to collapse
if your not using that version of twrp then most proberly that is why its failing
---------- Post added at 12:53 AM ---------- Previous post was at 12:50 AM ----------
dan110000 said:
use this version
twrp-3.0.2-4-herolte.img download that file dont unpack it just place it in ap section of odin make sure your phone is in download mode! once that is done put a custom rom on your phone after that just flash all the files from a stock rom dont delete anything off your phone just put in download mode again!
---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------
if your not using that version of twrp then most proberly that is why its failing
Click to expand...
Click to collapse
press the power button volume down and home key all at same time before it can reboot

Update:
I tried the suggested version of TWRP, then flashed an S7 ROM, rebooted into download mode and flashed stock and now have a fully working phone again!
Thanks dan110000 you really saved my bacon there!
Sometimes it's the little things that can catch you out when you spend so long making things too complicated.

this process isnt working for me with the new BL fused 6 error. I tried to flash Unlocked OS Stock rom and it sent to recovery boot and no recovery installed. I flashed the Correct most recent stock os for phone which is G930p it successfull flashed but still in a recovery boot loop with no recovery installed. The FRP lock is off and secure boot is enabled. BL is not unlocked. When i go to flash in odin it says unsupported dev type

Note 10.1 GT-n8010 stuck in bootloop, no recovery mode, unable to flash stock ROM

Hey there,
my Note 10.1 GT-n8010 bought in 2012 has been soft bricked for years but here I am giving it another try. Because of that, I have no memory of what software version was on the device, but I know it was rooted. The recovery mode is not working as the android logo with red triangle shows up, but I am able to go into download mode which says that: current binary and system status are both custom. I've tried flashing different stock ROMs from SAMMOBILE, starting with XEO (as it is my region) for 4.4.2 and 4.1.2 , but it didn't work. Every time I get sboot.bin FAIL in odin. I've also tried to install TWRP recovery and to root the device in order to unlock bootloader but then I get recovery.img fail in odin. So my main question is: what is causing sboot.bin to fail? I've read that flashing the most recent ROM usually makes this problem go away, but not in my case. Any advice would be greatly appreciated, thanks.

sboot wrong firmware for model or and older bootloader.
You need a rom firmware with the same bootloader.
Bootloader has never been locked.

JJEgan said:
sboot wrong firmware for model or and older bootloader.
You need a rom firmware with the same bootloader.
Bootloader has never been locked.
Click to expand...
Click to collapse
Could you point me in a direction of how to look for a correct ROM? On sammobile there are only two versions of ROMS for my region - 4.4.2 and 4.1.2 and none of them worked. Should I go through every possible region and hope for the best? How do I know that a ROM has the same bootloader? Since I can't turn on the device and find out the specifications of my system, is this just a guessing game? Thanks for taking the time to help me, by the way.

Was the Note purchased in your region ??
I would start with the oldest firmware any region a nd work through them.
Just make sure 16 or 32 gb is as your model.
Sammobile.
Updato.com.
Samsung-updates.
Are firmware sources.

I am also unable to revive my N8000, I can only go in download mode to flash.
Could you tell me when flashing a recovery with odin if the bootloader version matter ? I don't get that ? for me recovery are self loading no ?

No and no.
Suggest flash stock rom via Odin .
Fails post fail points in Odin

Galaxy note 10.1 (GT-N8000) cant get into recovery mode
JJEgan said:
No and no.
Suggest flash stock rom via Odin .
Fails post fail points in Odin
Click to expand...
Click to collapse
Sauces, my name is Caterina and I too have a problem with my Galaxy note 10.1 and looking for solutions on the internet I came to your forum. I hope you can help me. Let me explain: my tablet, while I was using it, froze without a reason and a few seconds later it restarted, remaining stuck on the word "samsung". You can't turn it off because if I press "power" it restarts. The only way to turn it off is to attach it to the charger. It does not go into recovery mode but only in odin mode. I tried to install a firmware download with SamFirm but it doesn't work. I tried with "dr. Phone" and nothing; with "reiboot for android" and nothing; I tried to install adb but if I type adb devices on the promt it doesn't find me the tablet despite the drivers are correctly installed (in fact odin if I connect in tablet via usb I recognize it). Usb debug is not active nor can I activate it since I cannot log in. The tablet is connected as an MTP. The twrp doesn't let me install it (I downloaded it from here https://forum.xda-developers.com/galaxy-note-10-1/orig-development/recovery-twrp-3-2-3-t3895276/ page4) but I didn't even understand what to do exactly. I downloaded the * .tar.md5 file and changed the extension to * .tar but nothing; I inserted the * .tar file in "AP"; I downloaded the img iso file but I don't know where to put it. I'm desperate. Help me to solve. One last thing, it's not possible to download the firmware from sammobile because you need a premium account and it's not the I. If any of you can download it could you alleviate it? Thanks in advance.

Install TWRP 2.8 * from TWRP thread or twrp.me .
Or try Philz recovery from this forum .
<I tried to install a firmware download with SamFirm but it doesn't work.>
What does not work mean what errors in Odin ??
What firmware .
Firmwares samsung-updates or updato .com .

JJEgan said:
Install TWRP 2.8 * from TWRP thread or twrp.me .
Or try Philz recovery from this forum .
<I tried to install a firmware download with SamFirm but it doesn't work.>
What does not work mean what errors in Odin ??
What firmware .
Firmwares samsung-updates or updato .com .
Click to expand...
Click to collapse
Hi and thanks for checking with me. I tried twrp 2.8.6.0 downloaded from twrp.me. I also tried previous versions for the GT-N8000 but to no avail. Clearly, since the models gt-n8010 and n8013 are not compatible with mine, is it possible to try the twrp for the p4notewifi or would I send the tablet in brik? Could you please send me the link to the recovery philiz please? However I also tried CF-auto-root and nothing. I state that I have never developed the root before and not so without root permissions I can share a non samsung firmware. Maybe that's why the recovery has been modified, not so. In any case, if there was a way to root now I would do it. I only care about saving the tablet and making it work.
This is after used twrp-2.8.6.0-gt-n8000.tar
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1303)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 8 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------- Post added at 04:47 AM ---------- Previous post was at 04:44 AM ----------
JJEgan said:
Install TWRP 2.8 * from TWRP thread or twrp.me .
Or try Philz recovery from this forum .
<I tried to install a firmware download with SamFirm but it doesn't work.>
What does not work mean what errors in Odin ??
What firmware .
Firmwares samsung-updates or updato .com .
Click to expand...
Click to collapse
However with the original firmware downloaded with both Samfirm and Samobile the error is sboot.ini fail. The versions of odin I tried are 3.13; 3.09 and 1.85.

JJEgan said:
Install TWRP 2.8 * from TWRP thread or twrp.me .
Or try Philz recovery from this forum .
<I tried to install a firmware download with SamFirm but it doesn't work.>
What does not work mean what errors in Odin ??
What firmware .
Firmwares samsung-updates or updato .com .
Click to expand...
Click to collapse
With Phliz touch 6.48.4 n8000.tar.md5 I have this
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1303)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 7 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help me!!!!

Sboot fail is due to flashing a firmware that has older bootloader than the one on the tablet.
Flash later firmware.
Try latest firmware.
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Usual rule of thumb with Odin is try another USB cable and ports on your computer. Normally the ones off the back side of a laptop/computer are the best to use since they are right off the motherboard. Odin is 100% connection sensitive. Always has been.

JJEgan said:
Sboot fail is due to flashing a firmware that has older bootloader than the one on the tablet.
Flash later firmware.
Try latest firmware.
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Usual rule of thumb with Odin is try another USB cable and ports on your computer. Normally the ones off the back side of a laptop/computer are the best to use since they are right off the motherboard. Odin is 100% connection sensitive. Always has been.
Click to expand...
Click to collapse
Hi JJEgan, I tried them all but I just can't bypass the boot problem that prevents me from flashing firmware with odin. I wanted to try with the pit but since I know it could damage my tablet I wanted to know from you a site where to download a functional pit, suitable for my galaxy note gt-n8000. On the internet I found several but we know several versions: 4.04, 4.12 etc. and I don't know if it should match the pit version with the version of the rom I'm going to download. If I download the Italian Rom (since I am Italian) will I have to use an Italian pit or if the pit is of a given nationality, will the Rom also be of the same nationality? In odin, if I put the pit and pda, do I have to tick only the auto reboot and F. reset time boxes or even the re-partition box? Generally I know that the re-partition should never be selected but I read (but I'm not sure) that the inclusion of the pit involves selecting the distribution. Waiting for you to reply cordially.

No idea sorry PITs are model and 16 or 32 gb not countries .
I dont know about flashing PIT ,
But all questions have beeen answered already in the forum .
PIT is part of the firmware .

JJEgan said:
No idea sorry PITs are model and 16 or 32 gb not countries .
I dont know about flashing PIT ,
But all questions have beeen answered already in the forum .
PIT is part of the firmware .
Click to expand...
Click to collapse
Mine is a 16GB model. I found several pits but I didn't understand how to use them and, since the procedure is risky, I wanted to be sure to flash the right one and to operate correctly. Don't you know how to address me to some page where they talk about it? But do you think my tablet is recoverable? Believe me, it seems to me that whatever I do is not successful. Yet I thought that in the case of soft bricks something could still be done but I'm starting to lose hope. In any case, thank you for your time and wish you a good day.

Don't you know how to address me to some page where they talk about it
No sorry apart from the forums SEARCH .
and see
https://forum.xda-developers.com/galaxy-note-10-1/help

Looks like Odin cannot write the recovery, this leads me to assume that this is a faulty MMC which seems to be a rather common issue. I don't think that this is a recoverable issue unless you solder a new MMC.
For the recovery part, try this:
1) turn on the tablet
2) wait for a reboot
3) immediately after the screen goes black, press and hold power only, you will see the logo come up and then vanish quicker than before
5) as soon as it vanishes, release power and immediately press and hold it again and also press and hold volume up at the same time
6) after the Samsung logo appears again, release the power key but not the volume up
I found this to sometimes help with a boot loop. If this does not work, you are probably out of luck. The Samsung logo disappearing basically tells you that the partition (either boot or recovery) could not be loaded into RAM for the kernel to be started. The BL2 then panics and restarts the device.