Database Users

[PROB] Can't install recovery, Download mode (Write protection: Enable)

Hi folks,
Having searched the forums I couldn't find an answer.
The problem I'm getting is when I get into download mode. I see the normal green android icon but at the top there is a grey caption saying: Write protection: Enabled.
I've been trying to flash twrp custom recovery but odin tries to do it and at the end it tells me success:0 failed:0.
That's all strange enough as previosly I managed to root the s4 using chainfire's Autoroot.
Could anyone tell me why is this happening and how to jump over it and install TWRP recovery.
//edit
I didn't check before I rooted the device but now I can't access stock recovery.
Cheers.
Ps. the device is: rooted i9505 running XXUAMDC stock rom, network: Three UK.

Attached is a screenshot of what I mean.
Thank you.

Didn't the TWRP site suggest using GooManager to install if you're rooted? Maybe give that a shot.

My unbranded UK s4 also said write protection enabled however I've had no problem installing twrp recovery.
Flashed via odin after putting phone into download mode... Have twrp in pda and it's checked in the box next to it...
Sent from my GT-I9505 using xda premium

chalger said:
Hi folks,
Having searched the forums I couldn't find an answer.
The problem I'm getting is when I get into download mode. I see the normal green android icon but at the top there is a grey caption saying: Write protection: Enabled.
I've been trying to flash twrp custom recovery but odin tries to do it and at the end it tells me success:0 failed:0.
That's all strange enough as previosly I managed to root the s4 using chainfire's Autoroot.
Could anyone tell me why is this happening and how to jump over it and install TWRP recovery.
//edit
I didn't check before I rooted the device but now I can't access stock recovery.
Cheers.
Ps. the device is: rooted i9505 running stock rom, network: Three UK.
Click to expand...
Click to collapse
I have the same issue. I'm stock XXUAMDE with CF-ROOT.
I haven't tried to flash TWRP but I can't boot into stock recovery.
It says 'booting recovery' in blue but then just hangs.
Have you tried using Super SU app and unrooting?

Ok.
I tried using GOOmanager, it cannot find suitable recovery for my device (which is strange as you may find it through TWRP web page).
When I choose in GOO to reboot to recovery it actually gets me to stock recovery (I still can NOT get into recovery using power+home+UP)
When i try to flash TWRP using (newly discovered via GOO) stock recovery it looks like that:
There is a broken android icon (see 1st attached file) and the text
-reboot system now
-apply update via ADB
[.....]
# MANUAL MODE #
Applying Multi-CSC
Applied the CSC-Code : H3G (btw H3G is my carrier, three UK)
Successfully applied multi-CSC
when I choose the recovery file to flash I'm getting response that E:\signature verification failed
Again everything I've done with the phone was CFroot, that is it. No custom rom etc or other playing with it.
//edit
I have the same issue. I'm stock XXUAMDE with CF-ROOT.
I haven't tried to flash TWRP but I can't boot into stock recovery.
It says 'booting recovery' in blue but then just hangs.
Click to expand...
Click to collapse
I've got EXACTLY the same behaviour. I discovered GOO manager allowed me to boot into stock recovery.
Thanks for your interest.
chalger

If you're having problems check the thread here: http://forum.xda-developers.com/showthread.php?t=2266336
It's the same method I used to root my phone and flash TWRP. (I too have write protection enabled)

write protection enabled means nothing
I have the exact same thing written on mine.
I have CF-Auto-Rooted mine AND TWRP 2.5 placed on mine, both using ODIN method.
No issues at all - both work perfectly fine.

chalger said:
(I still can NOT get into recovery using power+home+UP)
Click to expand...
Click to collapse
Try using just the Vol Up+Power. Once the phone vibrates, let go of the power but keep holding the up key until you see something appear on the screen. That works on my non-rooted phone to get into recovery.

Hiya
Just for your information.
I've done factory reset, it preserved root access (which I found strange) and now I've managed to flash twrp recovery (which in my view is way too much touch sensitive )
Thanks for all the replies.

problem rooting i9505
chalger said:
Hiya
Just for your information.
I've done factory reset, it preserved root access (which I found strange) and now I've managed to flash twrp recovery (which in my view is way too much touch sensitive )
Thanks for all the replies.
Click to expand...
Click to collapse
Hi All,
Just got my galaxy s4 i9505 with baseband XXUAME2. Have been trying to root this using CFROOT via odin numerous times but each time it fails. The error message includes "write operation failed" and "No PIT partion".
I have downloaded the correct PIT file and tried again but the same problem again.
I have further tried to flash pre-rooted firmware and another stock firmware but again - nothing I do seems to work.
Have tried the factory reset as well but again does not work.
Have tried flashing using motochopper method but also does not work.
Was hoping if someone could kindly extend his/her expertise - I am completely clueless at this point..

Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.

Still failing to flash anything usin odin
artnada said:
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Click to expand...
Click to collapse
Hi i have tried the above. Same problem persists.
I do not have Kies on my pc. Have tried steps listed above as is but still no luck.
need help

Anjamil said:
Hi i have tried the above. Same problem persists.
I do not have Kies on my pc. Have tried steps listed above as is but still no luck.
need help
Click to expand...
Click to collapse
Me too i have the same problem .. any other method to flash back to original fiemware ?
cheers
Indra

problem solved
I used odin 1.85 and original usb cable that came in the
box. Problem solved am now able to flash all roms

I'm having exxcactly the same problem, but i can't boot the phone, it's just stuck on s4 screen, can someone help?
Thanks in advance.

Thanks for this. That solved my issue.
artnada said:
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Click to expand...
Click to collapse

First time i tried to install a custom recovery on my S4 I9505 LTE. With Odin.. It didn't work..
I knew about heimdall.. And i gave that a try. And it worked perfectly. The one thing that's a bit weird.. After it first worked through heimdall. I could flash any custom recovery through Odin. But I think you should give heimdall a try..
Here is a link to how to install CWM on the cyanogenmod wiki: wiki.cyanogenmod.org/w/Install_CM_for_jfltexx#Installing_a_custom_recovery_on_Galaxy_S4_.28International_LTE.29 (I can't post links yet. So i just removed the http)

i flashed modern , and, it is fail, what wrong
[/url][/IMG]
my phone have this entry : "write protection : enable"

on my phone is also 'write protected- enable' but odin and cwm work fine

[Q] Phone stuck in boot loop after upgrading to Lollipop, Help

Dear All,
I'm in need of some urgent help. I have a S4 GT-I9500 which was running Kitkat stock 4.4.2 unrooted. I noticed the Lollipop update available OTA and so I downloaded and applied it. The installation went ok but after that the phone has just not worked. It comes to the homescreen, there comes an error stating that "An application needs and update" and below that "Requested by Google Play services". The homescreen appears on the screen for less than 5 seconds and it reboots. This goes on and on making the device really hot. There was a massive battery drain as well (from 90% to 30% within 30 mins)
Now the worst part is I hadn't even backed up any of my data. Although my photos are on my external SD, contacts are synced to google but there are some application specific data (whatsapp, few games progress, etc) that I would like to save.
Please help me out. At this point, I dont even care about the lollipop as long as I can get my phone back. I'm also open to rooting it, as my warranty period is over.

OK, I booted into recovery and wiped the cache partition too. No luck.

boogey_man said:
OK, I booted into recovery and wiped the cache partition too. No luck.
Click to expand...
Click to collapse
1. Wipe system, cache and cache partition (data no atm).
2. Reboot in DOWNLOAD MODE and flash via ODIN again Lollipop firmware. You will have to download it of Sammobile.com.
3. I hope this will work :highfive:

Joku1981 said:
1. Wipe system, cache and cache partition (data no atm).
2. Reboot in DOWNLOAD MODE and flash via ODIN again Lollipop firmware. You will have to download it of Sammobile.com.
3. I hope this will work :highfive:
Click to expand...
Click to collapse
Thanks for the reply.
But won't this erase all of the data (whatsapp, few games progress, etc) I want to save ?

boogey_man said:
Thanks for the reply.
But won't this erase all of the data (whatsapp, few games progress, etc) I want to save ?
Click to expand...
Click to collapse
Read the step 1.:
- You will have "Advanced Wipe" on your custom recovery. Click only for wipe system, cache and dalvick cache. In TWRP is:

Joku1981 said:
Read the step 1.:
- You will have "Advanced Wipe" on your custom recovery. Click only for wipe system, cache and dalvick cache. In TWRP is:
Click to expand...
Click to collapse
I haven't installed TWRP. I was only using inbuilt recovery (using volume-up, menu and power buttons) until now.
Please correct me if the below steps on installing TWRP are right:
- download latest twrp for s4 from here: http://www.teamw.in/project/twrp2/191
- flash TWRP to my phone using ODIN 3.09 (Download the above file and flash using Odin in the PDA tab.)

boogey_man said:
I haven't installed TWRP. I was only using inbuilt recovery (using volume-up, menu and power buttons) until now.
Please correct me if the below steps on installing TWRP are right:
- download latest twrp for s4 from here: http://www.teamw.in/project/twrp2/191
- flash TWRP to my phone using ODIN 3.09 (Download the above file and flash using Odin in the PDA tab.)
Click to expand...
Click to collapse
1. This will void you warranty: KNOX 0x1. You dont need care if you are out of warranty.
2. The steps are you following are corrects.

Thanks. I tried it but TWRP is just not getting installed. I flashed using ODIN 3.07 and PDA, but when in restart the phone into recovery mode, it goes back to the Samsung's stock recovery and doesn't have the TWRP. Any suggestions?

Use a different USB port, and don't use a hub. Also be sure you're using the original cable, have the drivers installed, and do not have Kies installed or running.
If necessary, find a later copy of Odin. 3.09 is apparently the standard although 3.10 exists.

Strephon Alkhalikoi said:
Use a different USB port, and don't use a hub. Also be sure you're using the original cable, have the drivers installed, and do not have Kies installed or running.
If necessary, find a later copy of Odin. 3.09 is apparently the standard although 3.10 exists.
Click to expand...
Click to collapse
Right....
Now I receive the below error in ODIN:
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The COM port gets detected. Also, now the boot loop is gone and is replaced by "firmware upgrade encountered an issue" error.
Should I try downloading Kies now?

Kies wouldn't do you much good, as it would find Android 5.0.1 on your S4 and report that there was no update.
You may need to flash with a PIT file in order to correct this as your S4 after the Lollipop update may have had its partition information changed. If that doesn't work, you may have to bite the bullet and do a complete factory reset, which will cost you the data.

Strephon Alkhalikoi said:
Kies wouldn't do you much good, as it would find Android 5.0.1 on your S4 and report that there was no update.
You may need to flash with a PIT file in order to correct this as your S4 after the Lollipop update may have had its partition information changed. If that doesn't work, you may have to bite the bullet and do a complete factory reset, which will cost you the data.
Click to expand...
Click to collapse
Thanks.
Meanwhile, I've tried on another PC too, same issues. "Complete (Write) operation failed." error in ODIN there as well.
PIT file flashing is next on the list, I guess. Any pointers as to how should I start?
And BTW, I don't know how I can wipe complete data, as now there is no way to access the stock recovery. Pressing the "up+menu+power" just opens the "firmware upgrade encountered an issue" error. The boot loop doesn't happen any more. Its just a soft brick now.

Update: I've tried flashing recovery.img (from both CWM and TWRP) using Heimdall. Both were not helpful.
Code:
C:\Heimdall Suite>heimdall.exe flash --RECOVERY recovery.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to retrieve config descriptor

Right...
So I was now able to flash stock 4.4.2 along with adonis.pit. This was a PASS! in Odin. However, still the device didn't boot. Stuck on the Samsung logo.
I did manage to flash CWM recovery on it and I'm now able to boot into recovery. I'll take the backup now and then try to wipe data and flash.

Note 4 SM-N910K bootloader question. Please Help!

I just got a Note 4 (Korean variant). I plan to root it with CF auto-root and flash a ROM. I am on MM update and my build number is same as the one as in the CF auto-root so I have worries about that. However, I wanted to check my bootloader first and the dialer trick won't work so I installed adb on my laptop. When I enter the command "adb devices" my device would read and thus I proceeded with the command "adb reboot-bootloader". My phone then would ONLY Restart and when typing the command "adb fastboot-devices" nothing would appear. What am I doing wrong? Can someone please help me because it would like to know if my bootloader is locked before proceeding with rooting since my main reason of rooting is to flash a custom ROM. :crying:

AJtheAndroidNoOb said:
I just got a Note 4 (Korean variant). I plan to root it with CF auto-root and flash a ROM. I am on MM update and my build number is same as the one as in the CF auto-root so I have worries about that. However, I wanted to check my bootloader first and the dialer trick won't work so I installed adb on my laptop. When I enter the command "adb devices" my device would read and thus I proceeded with the command "adb reboot-bootloader". My phone then would ONLY Restart and when typing the command "adb fastboot-devices" nothing would appear. What am I doing wrong? Can someone please help me because it would like to know if my bootloader is locked before proceeding with rooting since my main reason of rooting is to flash a custom ROM. :crying:
Click to expand...
Click to collapse
Bootloader is not locked.
Just get twrp recovery and flash via odin.
Boot into twrp.
Then flash supersu.zip from twrp.
Thats it you will be rooted and ready to flash any rom.
Twrp N910K/S/L
https://www.androidfilehost.com/?fid=24052804347844773
Supersu.zip
https://mega.nz/#!TE1VFIQD!XoaYaXoLfMDjxvO-uYvDnxejNC-QQlYex0P_UWlDCZ0

Trex888 said:
Bootloader is not locked.
Just get twrp recovery and flash via odin.
Boot into twrp.
Then flash supersu.zip from twrp.
Thats it you will be rooted and ready to flash any rom.
Twrp N910K/S/L
https://www.androidfilehost.com/?fid=24052804347844773
Supersu.zip
https://mega.nz/#!TE1VFIQD!XoaYaXoLfMDjxvO-uYvDnxejNC-QQlYex0P_UWlDCZ0
Click to expand...
Click to collapse
So I don't have to worry about the bootloader? What should be ticked in Odin (and what version of Odin preferably)?
P. S (Out of Topic) isn't there anything to be worried about the emmc error on my Note 4 SM-N910K?

AJtheAndroidNoOb said:
So I don't have to worry about the bootloader? What be ticked in Odin (and what version of Odin preferably)?
P. S (Out of Topic) isn't there anything to be worried about the emmc error on my Note 4 SM-N910K?
Click to expand...
Click to collapse
Dont worry just follow the steps given below correctly.
1 download odin version 3.10 is stable in my opinion.
2,download Twrp & supersu.zip.( do not extract any file ) move supersu file to phone and Twrp to pc
3,open odin and go to options and uncheck autoreboot.
4,choose AP tab in odin and upload Twrp file.
5, put your device into download mode.
6 connect device in your pc and hit start.
7,once odin shows pass remove battery then insert again.
8,now boot into twrp by pressing 3 buttons (volume up+home+power)
9,in twrp go to install and search for supersu file where it's located.
10, swipe confirm to flash supersu.zip and reboot system.
Your device may reboot twice so dont worry its normal dont touch anything until it reboot to system.
Go to app drawer you will see supersu icon open it and thats it you are rooted 100% with Twrp recovery to flash custom roms.

Trex888 said:
Dont worry just follow the steps given below correctly.
1 download odin version 3.10 is stable in my opinion.
2,download Twrp & supersu.zip.( do not extract any file ) move supersu file to phone and Twrp to pc
3,open odin and go to options and uncheck autoreboot.
4,choose AP tab in odin and upload Twrp file.
5, put your device into download mode.
6 connect device in your pc and hit start.
7,once odin shows pass remove battery then insert again.
8,now boot into twrp by pressing 3 buttons (volume up+home+power)
9,in twrp go to install and search for supersu file where it's located.
10, swipe confirm to flash supersu.zip and reboot system.
Your device may reboot twice so dont worry its normal dont touch anything until it reboot to system.
Go to app drawer you will see supersu icon open it and thats it you are rooted 100% with Twrp recovery to flash custom roms.
Click to expand...
Click to collapse
BTW, I am on Marshmallow 6.0.1. Is there no problems? So sorry for my repetitive questions. :crying:

AJtheAndroidNoOb said:
BTW, I am on Marshmallow 6.0.1. Is there no problems? So sorry for my repetitive questions. :crying:
Click to expand...
Click to collapse
No problem This method works on any os 4.4.4/5.0/5.1.1/6.0.1.
Make sure to follow all steps correctly and most importantly make a backup of your whole device from twrp to microsd card before start flashing any roms or stuff just in case if anything goes wrong you will be able to restore it.

Trex888 said:
No problem This method works on any os 4.4.4/5.0/5.1.1/6.0.1.
Make sure follow all steps correctly.
Click to expand...
Click to collapse
Once I pressed start it is stucked at
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
What to do?

AJtheAndroidNoOb said:
Once I pressed start it is stucked at
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
What to do?
Click to expand...
Click to collapse
Did you got samsung usb drivers installed on your pc ?
Close odin and open again
Upload twrp file into odin
Remove battery and insert again
Boot into download mode
Hit start
If it hapoens again just restart your pc and try again

Trex888 said:
Did you got samsung usb drivers installed on your pc ?
Close odin and open again
Upload twrp file into odin
Remove battery and insert again
Boot into download mode
Hit start
If it hapoens again just restart your pc and try again
Click to expand...
Click to collapse
Wooooot! I just changed USB ports and tried again. Now I have SuperSU and custom TWRP recovery! Thank you very much, to be honest I was scared to try and doubted at first but now I know it does work. Thank you! I can now flash custom ROMs without any problems right?

AJtheAndroidNoOb said:
Wooooot! I just changed USB ports and tried again. Now I have SuperSU and custom TWRP recovery! Thank you very much, to be honest I was scared to try and doubted at first but now I know it does work. Thank you! I can now flash custom ROMs without any problems right?
Click to expand...
Click to collapse
Yes you can but make sure roms that you are going to flash are compatible with your model otherwise you will face some issues.
Dont forget to backup your current rom from twrp.
Congrats and enjoy the freedom and power of root

Screenshot of proof!
Trex888 said:
Yes you can but make sure roms that you are going to flash are compatible with your model otherwise you will face some issues.
Dont forget to backup your current rom from twrp.
Congrats and enjoy the freedom and power of root
Click to expand...
Click to collapse
Woooot! Here's a screenshot
https://imgur.com/a/NHnjd

AJtheAndroidNoOb said:
Woooot! Here's a screenshot
https://imgur.com/a/NHnjd
Click to expand...
Click to collapse
Don't forget to thanks @Chainfire for supersu root and Team win recovery project (TWRP) who made this possible.
All the credits goes to them.

G900F Recovery Boot Loop and Odin stock flash fails

Good morning guys,
I need your help. I have a SM-G900F and right now the phone is stuck in a boot loop. I can not access recovery, because that one is also stuck in a loop.
What I did
* my phone had flashed one of the roms from here https://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
* I wanted to update to LineageOS 15.1
* flashing latest twrp 3.2.3-0
* flasing LineageOS 15.1
Up to here everything was working, but then I tried to flash opengapps and reflash LineageOS. Both were working fine, but the phone was stuck in a boot loop and I could not enter recovery mode.
Things I tried to solve my issue being unable to enter recovery mode
* try different versions of twrp and odin
* try to flash stock firmware 6.0.1
Stock firmware flash fails with
Code:
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The stock firmware problem seems to be related to the CSC. I can't look up my CSC because I'm stuck, but I guess it is a DBT or DTM. But due to the flashed firmware of _alexndr the csc was probably changed and I don't know to which.
Any ideas how I can proceed?

NaTopp said:
Good morning guys,
I need your help. I have a SM-G900F and right now the phone is stuck in a boot loop. I can not access recovery, because that one is also stuck in a loop.
What I did
* my phone had flashed one of the roms from here https://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
* I wanted to update to LineageOS 15.1
* flashing latest twrp 3.2.3-0
* flasing LineageOS 15.1
Up to here everything was working, but then I tried to flash opengapps and reflash LineageOS. Both were working fine, but the phone was stuck in a boot loop and I could not enter recovery mode.
Things I tried to solve my issue being unable to enter recovery mode
* try different versions of twrp and odin
* try to flash stock firmware 6.0.1
Stock firmware flash fails with
Code:
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The stock firmware problem seems to be related to the CSC. I can't look up my CSC because I'm stuck, but I guess it is a DBT or DTM. But due to the flashed firmware of _alexndr the csc was probably changed and I don't know to which.
Any ideas how I can proceed?
Click to expand...
Click to collapse
Hi,
Could you tell me what is written when you enter download/odin mode at: "Product name" and "Reactivation lock"? Also what exact firmware are you trying to flash via odin?
One more question: what do you mean by "unable to enter recovery mode"? Did you try to force power off the phone and tried to eneter recovery by pressing "volume up + home + power"? What happened then?

Many40 said:
Hi,
Could you tell me what is written when you enter download/odin mode at: "Product name" and "Reactivation lock"? Also what exact firmware are you trying to flash via odin?
One more question: what do you mean by "unable to enter recovery mode"? Did you try to force power off the phone and tried to eneter recovery by pressing "volume up + home + power"? What happened then?
Click to expand...
Click to collapse
Yes of course.
Download mode (complete):
Code:
ODIN MODE
Product Name: SM-G900F
Current Binary: Custom
System Status: Custom
Reactivation Lock: OFF
Knox Warranty Void: 0x1
Qualcom SecureBoot: Enable (CSB)
Secure Download: Enable
UDC Start
I'm trying to flash stock firmware for Galaxy S5, Android 6.0.1 CSC DBT. From here https://updato.com/firmware-archive-select-model?record=D05FDF7EBCFB11E89F15FA163EE8F90B
and while looking up the URL I've seen that it is for G901F. Damn.. I've started to download a version for G900F right now. This one https://updato.com/firmware-archive-select-model?record=2FC456972E5B11E89F15FA163EE8F90B
Recovery mode: If I press the buttons (power+home+vol up) the blue line with "recovery booting" pops up and the phone tries to boot for some seconds and restarts afterwards (without entering recovery). I'm not sure what you mean by "force power off", but usually I'm taking out the battery and wait some time.
So let me try to download the correct stock firmware.

Here is the latest firmware for the g900f
Just place in AP section of odin
https://mega.nz/#!Nw5UBA6D!QYx2jht-Y56R3UlqfEXtq1e0QjJQRyTij8YXr5dM1Rw
You may need to factory reset in recovery mode after flashing

NaTopp said:
Yes of course.
Download mode (complete):
Code:
ODIN MODE
Product Name: SM-G900F
Current Binary: Custom
System Status: Custom
Reactivation Lock: OFF
Knox Warranty Void: 0x1
Qualcom SecureBoot: Enable (CSB)
Secure Download: Enable
UDC Start
I'm trying to flash stock firmware for Galaxy S5, Android 6.0.1 CSC DBT. From here https://updato.com/firmware-archive-select-model?record=D05FDF7EBCFB11E89F15FA163EE8F90B
and while looking up the URL I've seen that it is for G901F. Damn.. I've started to download a version for G900F right now. This one https://updato.com/firmware-archive-select-model?record=2FC456972E5B11E89F15FA163EE8F90B
Recovery mode: If I press the buttons (power+home+vol up) the blue line with "recovery booting" pops up and the phone tries to boot for some seconds and restarts afterwards (without entering recovery). I'm not sure what you mean by "force power off", but usually I'm taking out the battery and wait some time.
So let me try to download the correct stock firmware.
Click to expand...
Click to collapse
So you found it From my experience NAND Write Start and then Fail!(Auth) happen to people who tried flashing wrong firmware to their phones or sometimes Reactivation lock was ON.
With this "Recovery booting" issue hopefully it is nothing serious. I don't want to make you afraid but this exactly happened to me some time ago after routine installation of something. Unfortunately for me, my eMMc memory (flash memory) got corrupted and nothing helped - I had to replace a motherboard.
But hopefully it is not your case.
TheFixItMan said:
Here is the latest firmware for the g900f
Just place in AP section of odin
https://mega.nz/#!Nw5UBA6D!QYx2jht-Y56R3UlqfEXtq1e0QjJQRyTij8YXr5dM1Rw
You may need to factory reset in recovery mode after flashing
Click to expand...
Click to collapse
Come on, let me help him myself

TheFixItMan said:
Here is the latest firmware for the g900f
Just place in AP section of odin
https://mega.nz/#!Nw5UBA6D!QYx2jht-Y56R3UlqfEXtq1e0QjJQRyTij8YXr5dM1Rw
You may need to factory reset in recovery mode after flashing
Click to expand...
Click to collapse
Thanks. I've used your file and the flash process successful with odin. After rebooting the phone is still stuck in recovery boot loop unfortunately.
Many40 said:
So you found it From my experience NAND Write Start and then Fail!(Auth) happen to people who tried flashing wrong firmware to their phones or sometimes Reactivation lock was ON.
With this "Recovery booting" issue hopefully it is nothing serious. I don't want to make you afraid but this exactly happened to me some time ago after routine installation of something. Unfortunately for me, my eMMc memory (flash memory) got corrupted and nothing helped - I had to replace a motherboard.
But hopefully it is not your case.
Come on, let me help him myself
Click to expand...
Click to collapse
I'm still stuck in the recovery loop. Seems like I got a corrupted memory too.

NaTopp said:
Thanks. I've used your file and the flash process successful with odin. After rebooting the phone is still stuck in recovery boot loop unfortunately.
I'm still stuck in the recovery loop. Seems like I got a corrupted memory too.
Click to expand...
Click to collapse
Did you go into recovery mode and perform a factory reset/format data after you flashed the firmware in odin?

TheFixItMan said:
Did you go into recovery mode and perform a factory reset/format data after you flashed the firmware in odin?
Click to expand...
Click to collapse
The problem is that I can not access recovery. The phone shows the blue message "recovery booting" and after some seconds it restarts.

NaTopp said:
Thanks. I've used your file and the flash process successful with odin. After rebooting the phone is still stuck in recovery boot loop unfortunately.
I'm still stuck in the recovery loop. Seems like I got a corrupted memory too.
Click to expand...
Click to collapse
I didn't want to be negative and hopped that flashing stock firmware helps but unforunately it didn't.
If you still can't access your recovery you might try removing battery, putting it back after a while and trying to install from odin (as AP) TWRP recovery (for klte). After that don't try rebooting the phone (uncheck "Auto reboot option in odin as well) but take battery out again, put it back and try directly going to the recovery. Let's see ....
Edit: What @TheFixItMan already mentioned is also one of the workaround options which comes to my mind but in my opinion do that only if all other possible solutions fail (as a last resort) -> flashing PIT incorrectly may do more harm then good for the phone. For my case I tried that as well but it didn't help.
Edit2: just found a similar case to yours but unforunately without success at the end: https://forum.xda-developers.com/galaxy-s5/help/boot-loop-measures-t3559074

NaTopp said:
The problem is that I can not access recovery. The phone shows the blue message "recovery booting" and after some seconds it restarts.
Click to expand...
Click to collapse
You may have to also flash the firmware via odin with the pit file to repartition your device if you flashed incorrect firmware before
https://drive.google.com/file/d/0BzyeAt2hy6XeM3g4SWhUaWtoVWM/view
Add the above file to the pit section of odin
Put the firmware I previously posted in AP section
Tick reparation device in odin

I did not check your external links in detail nor did I flash pit file yet, because I'm in a hurry. But a brief update:
* I've flashed the stock
* let the phone normally boot to Samsung logo - which resulted in a restart
* flashed latest twrp (3.2.3)
* boot to twrp, which works
After wiping cache etc the phone did not boot the OS (still loop). Maybe I did something wrong here, but I had not much time to dive deeper into it.
Anyways, afterwards I'm not able to boot to recovery again. I need to apply the steps above (flash stock > boot > flash twrp) to get recovery working again.

Something stranged I've noticed during yesterday and today: So yesterday somehow I got back into my original state, that recovery did not boot up. I set the phone aside until today without a battery plugged in. This morning I booted the device directly into recovery and it did work again. After some tries of wiping and flashing recovery is not working again.
I guess it boils down to some hardware issue.

i also face this issue and after a lot of effort, solved it Alhamdulillah. The problem was faulty battery. I will advise you all to replace battery with new one then try to install again.

sm-g900f
TheFixItMan said:
Here is the latest firmware for the g900f
Just place in AP section of odin
You may need to factory reset in recovery mode after flashing
Click to expand...
Click to collapse
any other link for this? thank you

Clarkitoi88 said:
any other link for this? thank you
Click to expand...
Click to collapse
I don't have the files anymore but you should be able to download any Samsung firmware from https://www.sammobile.com/firmwares/ or via the power of Google

Need help in flashing TWRP

I get a second Galaxy Note 3 N900 (exynos version) and as the title said, I need help in flashing TWRP. I had go into download mode & flash the TWRP file using odin 3.14.1. The result as below :
<ID:0/004> SetupConnectjon..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start! !
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port 0
<OSM> All threads completed (succeed 1 failed 0)
Click to expand...
Click to collapse
Did it succeed in flashing TWRP ? Because after flashing the device reboot (auto reboot checked in Odin) and then I power off the devices & go into recovery mode. But the recovery is still using Samsung's stock, not TWRP.
What step did I miss ? Any help is appreciated

ayambakargoreng said:
I get a second Galaxy Note 3 N900 (exynos version) and as the title said, I need help in flashing TWRP. I had go into download mode & flash the TWRP file using odin 3.14.1. The result as below :
Did it succeed in flashing TWRP ? Because after flashing the device reboot (auto reboot checked in Odin) and then I power off the devices & go into recovery mode. But the recovery is still using Samsung's stock, not TWRP.
What step did I miss ? Any help is appreciated
Click to expand...
Click to collapse
try enter recovery directly after flash dont let your phone boot to system if it done you will loses twrp
before the device reboot in sec click the recover buttom and dont release your hand till open recovery

imtmiissa said:
try enter recovery directly after flash dont let your phone boot to system if it done you will loses twrp
before the device reboot in sec click the recover buttom and dont release your hand till open recovery
Click to expand...
Click to collapse
Got it. I unchecked auto reboot and manually got into recovery mode. I could already got into TWRP. Thanks