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

[SOLVED] Need help after "Nand erase all"!

Hi guys!
It was a stupid move for me to check Nand erase all option, but i did it!
At first i was not able to go in to recovery menu, only in to donwload mode.
I flashed only a.pit file via Odin 3.09 and then i was able to get in to the Recovery mode - ClockworkMod Recovery v6.0.4.7.
When i tried to wipe data/factory reset or to install zip i am gettinf error messages "Error mounting /data" or "Error mounting /sdcard/.android_secure"
Then i tried to flash the stock 4.4.2 firmware via Odin, but i am getting FAIL message on the NAND WRITE step.
What i have to do now, to get back my phone in working order ?
Thank you in advance!

If it was me I would just flashed 4.2.2 firmware MDM (which have no bootloader files)
then 4.4.2
But this is just my opinion
so many times I fix my phone with this
but Knox on my phone was tripped
Currently Knox is 0x0 on my phone and all official and do not bother with custom ROMs because it makes no sense (they do not offer anything except headaches)

gsmconn said:
If it was me I would just flashed 4.2.2 firmware MDM (which have no bootloader files)
then 4.4.2
But this is just my opinion
so many times I fix my phone with this
but Knox on my phone was tripped
Currently Knox is 0x0 on my phone and all official and do not bother with custom ROMs because it makes no sense (they do not offer anything except headaches)
Click to expand...
Click to collapse
I can't flash it, because i am getting only:
Code:
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE!!!!
I have managed to flash new rom. I just checked again Nand erase option, this time with PIT and firmware in odin and it got passed!
But now i am in bootloop! The device is loading to the Samsung logo and it is freezing on it for a minute or two, then it is turning off.
Also i can't access the recovery!
UPDATE 2!!!
Finally, everything is fine runing!
I have flashed a stock recovery and i was able to get in to it and to wipe /data and /cache and i've got out of the bootloop!
So to summ it:
1. You have to download a propriet PIT file and firmware.
2. In Odin you have to load both of them and to check this options: Autoreboot, F.Reset Time and NAND ERASE ALL! Yes, you have to check Nand erase all, again!
3. If you got stuck in bootloop after the above steps, you have to get in to recovery and delete /data and /cache!

[SOLVED] Recovery is not seandroid enforcing SM-G900F

So I tried rooting for the first time today, and after trying it (and failing) it shows this message briefly with the "Samsung Galaxy S5" startup screen, then turns off again. Then, I noticed I had used a CF Auto Root for 4.4.2, when I was running 5.0. I downloaded one for 5.0 and ran it with Odin. After that I get the same screen, but it stays on that screen forever. It says "Recovery booting... Recovery is not seandroid enforcing. Set warranty bit: recovery" In the top left corner.
Anyone know a fix for this? Not being able to use your phone is kind of sad

Flash a stock ROM from sammobile . com with ODIN, instructions under the download on their site

*Detection* said:
Flash a stock ROM from sammobile . com with ODIN, instructions under the download on their site
Click to expand...
Click to collapse
It fails when I try to flash it!
In Odin it says:
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says:
"Volume size is too mig 61440 < 122880
ODIN: Invalid ext4 image"

Flash the PIT file for your model S5 along with the ROM (Together)

*Detection* said:
Flash the PIT file for your model S5 along with the ROM (Together)
Click to expand...
Click to collapse
This doesn't work either, it gives me "Fail (size)" instead of ext4 now.

Burgermis said:
This doesn't work either, it gives me "Fail (size)" instead of ext4 now.
Click to expand...
Click to collapse
Could all of this be because I forgot to turn USB Debugging on? Or would that have made no difference?

Same Problem
I have the same problem with you yesterday. What I did is flash a TWRP Recovery that is compatible with my SM-G900F model I downloaded it on the TWRP site and I choose the KLTE version. And BOOM it fixes the problem Tell me if still stuck on it.

ginofakes said:
I have the same problem with you yesterday. What I did is flash a TWRP Recovery that is compatible with my SM-G900F model I downloaded it on the TWRP site and I choose the KLTE version. And BOOM it fixes the problem Tell me if still stuck on it.
Click to expand...
Click to collapse
I tried this as well, but it did not work for me.
What did work though was trying out a bunch of different PIT files with the Stock ROM until it eventually worked!
Thanks for your guys' help!

It would have worked first time if you'd used the correct PIT file for your specific model S5 first, maybe you are mistaken on which model it is, check under the battery and in the Settings > About screen

*Detection* said:
It would have worked first time if you'd used the correct PIT file for your specific model S5 first, maybe you are mistaken on which model it is, check under the battery and in the Settings > About screen
Click to expand...
Click to collapse
I did use the correct one, with the correct amount of gigs as well, I don't know why it didn't work.

Soft-bricked my S4?

Hi there,
I have the Samsung Galaxy S4 SPH-L720 Sprint (on RingPlus). I just installed Cyanogenmod on a Moto E and loved it, so figured I would install the S4 Sprint version on my S4. I have a feeling I didn't wipe the cache before doing so, because the S4 had a different recovery software (as opposed to TWPR which I was more familiar with). After rebooting I went through the whole "new phone" setup and it looked like the stock Android. So, like an idiot I decided to try installing TWRP so it would be more familiar to then install Cyanogenmod. I saw a few people recommend RASHR as the easiest way to install TWRP. So I used it and happily clicked ok when it asked if I would like to reboot into recovery.
It rebooted and hung with:
Code:
RECOVERY BOOTING.....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
After rebooting again and again I got the same message. Then I read that flashing a stock ROM might do the trick. So I did the vol down, home, and power to get to the screen warning about damaging the OS, etc. Volume up selects the option to continue which does allow me to get to the "Downloading..." screen.
The upper left displays:
Code:
ODIIN MODE
PRODUCT NAME: SPH-L720
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
I plugged it in via USB (have tried several different USB cables and 2 different computers) it is recognized in Oden. But after selecting AP and choosing the ROM and clicking "Start" it hangs. I have tried a few ROMS now, which in retrospect was probably not wise, but I saw post after post saying, "just install a stock ROM". I've also tried installing TWRP and CWM via Odin and get the same hang. It hangs with Odin reading:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720_OD2_Pre-Rooted_Firmware.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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
And the phone reading "Downloading... Do not turn off target!!" with a tiny blue progress bar (maybe equivalent to 2%) that sits still indefinitely. The upper left on the phone adds the line:
Code:
START [224, 1440]
after the eMMc BURST MODE line. It is the same progress and same "START [224, 1440]" no matter what ROM or file I'm trying to add via Odin. I simply have to hold down the power key for several moments before it shuts down. I let it sit for 45 minutes with zero difference in progress.
What I didn't realize was that if I choose "cancel" (volume down) in the download confirmation screen it would reboot not in the recovery mode. I was thrilled to see the animated Samsung logo appear but after another 45 minutes of watching the logo continue animating with no boot progress I realized this wasn't going to get me anywhere.
I read that I can use Kies to do a recovery, but it requests a Serial Number, which is nowhere to be found on physical phone... Only the ESN and HEX numbers (and model number, etc.) Looking online everyone tells me to find it in my settings... which I can't access of course.
Since I can communicate via Odin, I still have hope... but it's running thin. What should I try? I'm using Window 10 64bit if that means anything.
Thank you for your help!
-Stephen

Also, I found other forum posts that said I just need to wipe the cache and format to factory, but I can't do that since I can't get to a recovery screen. And finally, I read that the Partition could be jacked up, but I don't even know where to start with that...

You will be fine. Nothing wrong with your phone.
Here you have TWRP.
http://forum.xda-developers.com/showthread.php?t=2262999
1. Flash it using Odin. Uncheck auto-reboot before flashing in Odin. If it fails, then try all the usb ports on your pc.
2. Boot into recovery. Wipe /system, /data and /cache.
3. Flash the rom you want.
If you want CM 12.1 then this is a good choice to flash:
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
ps this is the section for you phone:
http://forum.xda-developers.com/showthread.php?t=2262999

Lennyz1988 said:
You will be fine. Nothing wrong with your phone.
Here you have TWRP.
http://forum.xda-developers.com/showthread.php?t=2262999
1. Flash it using Odin. Uncheck auto-reboot before flashing in Odin. If it fails, then try all the usb ports on your pc.
2. Boot into recovery. Wipe /system, /data and /cache.
3. Flash the rom you want.
If you want CM 12.1 then this is a good choice to flash:
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
ps this is the section for you phone:
http://forum.xda-developers.com/showthread.php?t=2262999
Click to expand...
Click to collapse
Thank you! What was I doing wrong? I always had Auto-Reboot enabled. Was that it? I also looked at my downloads and see that I was downloading the .img instead of .tar for twrp-2.8.4.0-jfltespr (but I tried other roms that were .tar which also hung). I tried a different USB port this time too (a port I've never used until now). I got it the first try. I had to do a factory reset before it would wipe anything (it complained about not being able to mount the different directories).
Now I need to do some reading into making backups.
Thank you again, I really appreciate it.
-Stephen

If you flash a custom recovery such as TWRP via Odin and you use auto-reboot, the custom recovery will sometimes be overwritten by stock recovery at reboot.

stephenphone said:
Thank you! What was I doing wrong? I always had Auto-Reboot enabled. Was that it? I also looked at my downloads and see that I was downloading the .img instead of .tar for twrp-2.8.4.0-jfltespr (but I tried other roms that were .tar which also hung). I tried a different USB port this time too (a port I've never used until now). I got it the first try. I had to do a factory reset before it would wipe anything (it complained about not being able to mount the different directories).
Now I need to do some reading into making backups.
Thank you again, I really appreciate it.
-Stephen
Click to expand...
Click to collapse
It's possible. Odin is not the most forgiving program there is.
Keep in mind that 2.8.4.0 is outdated and you should update it to the latest version. You will run into issues with Lollipop roms.
Here is the latest. You can just flash it in your recovery.
https://www.androidfilehost.com/?fid=24052804347763625

Note 4 - Not able to flash system

So, I purchased a damaged Note 4 and took the motherboard and put it in a Note 4 with broken motherboard. When booting up the phone the first time there was only TWRP and no system so I tried flashing it with original firmware but it failed. After this I've tried downloading ROMs and flashing through TWRP but it did not work. Recently I tried to follow this guide:
https://forum.xda-developers.com/no...ebrick-img-t3488114/post69489251#post69489251
To reinstall the firmware on the phone and I've managed to flash boot, recovery and PIT(different flash) but it fails every time when flashing system. On the phone I had error message:
[9] eMMC write fail: SYSTEM
ODIN : flash write failure
and in Odin it said:
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
I've tried several times, changed the cable, different USB-ports, re-installing drivers, tried Odin 3.07 and 3.09 but get the same error every time. Also tried emergency reset through Smart Switch but it didn't worked either.
Now I've tried to install TWRP and if I try to boot into it I get directly to Download Mode and the to text says:
Could not do normal boot.
ddi: mmc_read failed
I have tried eveything I can think of and have had no success so far. Anybody who gan give some pointers on how to approach this? Or could it be hardware fault and I should just scrap the device? It's the European version, SM-N910F.
Thanks in advance!
Edit: If somebody gives me the solution that helps me get the phone working I can donate $25 through PayPal as thanks for the help

Ahh, the infamous eMMC memory error. It sometimes appears when flashing TWRP and a custom rom, but then never appears when flashing a stock rom. However, if it appears when flashing stock, then I'm sorry to say but it's a fatal hardware error: your memory is on its way out. Your only solution is to either replace the board or get a new device.

As the dude above implies. eMMC is destroyed. Note 4 and galaxy s3 had these problems... it's hardware based unfortunately...
Sent from my SM-G955F using Tapatalk