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] Everything except WiFi is working. S4 I-9505

Model number
GT-I9505
Android version
4.3
Baseband version
I9505XXUEMJ7
Kernel version
3.4.0-1765174
[email protected] #1
Tue Oct 15 16:14:54 KST 2013
Build number
JSS15J.I9505XXUEMJ7
SELinux status
Enforcing
SEPF_GT-I9505_4.3_0010
Secure boot status
Type: Samsung
So, i just bought this device from a friends friend who hasn't used it for a few months and even when i got it, it was 4.2 and WiFi was not working. But the problem is that i can't switch it on. When i try and press to switch it on, it doesn't do anything. Even in the notification bar, i can't turn it on.
So, what is the safest thing for me to do and fix this and is it even fixable?
The device is not rooted or flashed in any way. It's plain stock.
If somebody could reply with a step by step procedure to fix this, i would be really greatfull.

re: no wifi
nikolanicic said:
Model number
GT-I9505
Android version
4.3
Baseband version
I9505XXUEMJ7
Kernel version
3.4.0-1765174
[email protected] #1
Tue Oct 15 16:14:54 KST 2013
Build number
JSS15J.I9505XXUEMJ7
SELinux status
Enforcing
SEPF_GT-I9505_4.3_0010
Secure boot status
Type: Samsung
So, i just bought this device from a friends friend who hasn't used it for a few months and even when i got it, it was 4.2 and WiFi was not working. But the problem is that i can't switch it on. When i try and press to switch it on, it doesn't do anything. Even in the notification bar, i can't turn it on.
So, what is the safest thing for me to do and fix this and is it even fixable?
The device is not rooted or flashed in any way. It's plain stock.
If somebody could reply with a step by step procedure to fix this, i would be really greatfull.
Click to expand...
Click to collapse
If that was my phone and I did not want to root it this is what I would do.
Download Ktoonsez International 4.3 kernel:
http://ktoonsez.jonathanjsimon.com/sgs4/TW/KT-SGS4-JB4.3-TW-INTL-12.22.2013.zip
Then rename the file to "update.zip" and copy it from computer to the phone's
internal sdcard.
Before anything else, use the file manager which is in your app drawer just
to be sure that the filename is "update.zip".
(it cannot be anything else unless you root the phone)
Once you are sure of the filename, reboot the phone into the stock recovery mode
and select the option "flash update.zip" or the wording might be "install update.zip".
If you cannot find update.zip it means that you have re-named it wrongly
or you have not copied it to /sdcard.
It cannot be in some folder, it must be in the root of your sdcard.
If worst came to worst and it was my phone and the above did not work
I would simply root the phone and flash a custom recovery after that it
would be a very easy fix.
Good luck!

Misterjunky said:
If that was my phone and I did not want to root it this is what I would do.
Download Ktoonsez International 4.3 kernel:
Then rename the file to "update.zip" and copy it from computer to the phone's
internal sdcard.
Before anything else, use the file manager which is in your app drawer just
to be sure that the filename is "update.zip".
(it cannot be anything else unless you root the phone)
Once you are sure of the filename, reboot the phone into the stock recovery mode
and select the option "flash update.zip" or the wording might be "install update.zip".
If you cannot find update.zip it means that you have re-named it wrongly
or you have not copied it to /sdcard.
It cannot be in some folder, it must be in the root of your sdcard.
If worst came to worst and it was my phone and the above did not work
I would simply root the phone and flash a custom recovery after that it
would be a very easy fix.
Good luck!
Click to expand...
Click to collapse
I've tried doing that, i've placed the "update.zip" on both my external sdcard and internal phones memory.
When i click to go update it displays no package is anywhere to be found.
God damn it.
Any other options ? :/

nikolanicic said:
Model number
GT-I9505
Android version
4.3
Baseband version
I9505XXUEMJ7
Kernel version
3.4.0-1765174
[email protected] #1
Tue Oct 15 16:14:54 KST 2013
Build number
JSS15J.I9505XXUEMJ7
SELinux status
Enforcing
SEPF_GT-I9505_4.3_0010
Secure boot status
Type: Samsung
So, i just bought this device from a friends friend who hasn't used it for a few months and even when i got it, it was 4.2 and WiFi was not working. But the problem is that i can't switch it on. When i try and press to switch it on, it doesn't do anything. Even in the notification bar, i can't turn it on.
So, what is the safest thing for me to do and fix this and is it even fixable?
The device is not rooted or flashed in any way. It's plain stock.
If somebody could reply with a step by step procedure to fix this, i would be really greatfull.
Click to expand...
Click to collapse
Do a Internal Memory Card Backup and then:
Wake your Samsung Galaxy S4
Navigate to and tap on Settings.
Go to Accounts
Tap Backup & reset.
Select Factory data reset.
You will see a warning – read it and tap Reset phone.
Now tap Erase everything.
Let the phone finish the process (will reboot too)
Try if u have WIFI now

Joku1981 said:
Do a Internal Memory Card Backup and then:
Wake your Samsung Galaxy S4
Navigate to and tap on Settings.
Go to Accounts
Tap Backup & reset.
Select Factory data reset.
You will see a warning – read it and tap Reset phone.
Now tap Erase everything.
Let the phone finish the process (will reboot too)
Try if u have WIFI now
Click to expand...
Click to collapse
Nope, still not working.

nikolanicic said:
Nope, still not working.
Click to expand...
Click to collapse
Try this WIFI FIX:
Use it with care!!!
1. Go to Download Mode
2. Open Odin
3. Select this FILE as PHONE/CP and click START
4. Ur phone will reboot automatically when the process finish
5. I think this will work

Joku1981 said:
Try this WIFI FIX:
Use it with care!!!
1. Go to Download Mode
2. Open Odin
3. Select this as PHONE/CP and click START
4. Ur phone will reboot automatically when the process finish
5. I think this will work
Click to expand...
Click to collapse
Is this going to work even without rooting my device ?
I've tried what you suggested but i can't get ODIN to see my device unless it's powered on.
PS. This is what i have:
"Android system recovery <3e>
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache"

nikolanicic said:
Is this going to work even without rooting my device ?
I've tried what you suggested but i can't get ODIN to see my device unless it's powered on.
PS. This is what i have:
"Android system recovery <3e>
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache"
Click to expand...
Click to collapse
U are in STOCK RECOVERY Mode. U have to go DOWNLOAD MODE: HERE

Joku1981 said:
U are in STOCK RECOVERY Mode. U have to go DOWNLOAD MODE: HERE
Click to expand...
Click to collapse
I have done everything you've said in the tutorial...
Output from ODIN:
"<ID:0/016> Added!!
<ID:0/016> Removed!!
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> NON-HLOS.bin
<ID:0/017> NAND Write Start!!
<ID:0/017> Transmission Complete..
<ID:0/017> Now Writing.. Please wait about 2 minutes
<ID:0/017> Receive Response from boot-loader
<ID:0/017> RQT_CLOSE !!
<ID:0/017> RES OK !!
<ID:0/017> Removed!!
<ID:0/017> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
"
The phone started but i'm still unable to switch the WiFi on.
Damn it.

nikolanicic said:
I have done everything you've said in the tutorial...
Output from ODIN:
"<ID:0/016> Added!!
<ID:0/016> Removed!!
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> NON-HLOS.bin
<ID:0/017> NAND Write Start!!
<ID:0/017> Transmission Complete..
<ID:0/017> Now Writing.. Please wait about 2 minutes
<ID:0/017> Receive Response from boot-loader
<ID:0/017> RQT_CLOSE !!
<ID:0/017> RES OK !!
<ID:0/017> Removed!!
<ID:0/017> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
"
The phone started but i'm still unable to switch the WiFi on.
Damn it.
Click to expand...
Click to collapse
im having the same problem

Misterjunky said:
I would simply root the phone and flash a custom recovery after that it
would be a very easy fix.
Click to expand...
Click to collapse
Any custom recovery you'd suggest ?

One fun night
Well, this has been a fun night for me... It's 5:40AM at the moment while i'm writing this post. Take into consideration that i've had 0 experience in android phones before i've started flashing my Galaxy S4 a few hours ago.
So, first off, i've tried installing just the WiFi fix, had no luck. After that i've had trouble while instaling a custom rom (I9505XXUEMJ7-PRE-ROOTED-KNOX-FREE-ODEX-FULL.tar.md5) and i soft-bricked my phone. After that i've read that changing the USB port might solve the problem with ODIN so i've done that and it really fixed later. Had trouble with partitioning so i've had to find out what a PIT file was and where to download it. I flashed "I9505XXUEMJ7-PRE-ROOTED-KNOX-FREE-ODEX-FULL.tar.md5" (found it on the forums) and flashed the "WiFi fix", no luck. I've then came back to this thread and seen that Misterjunky told me to install a custom kernel and custom recovery mode. I've installed the kernel he suggested and i've installed Phillz recovery mode.
Now, what really bothers me and is SERIOUSLY getting on my nerves is THE WIFI IS STILL NOT WORKING AND I STILL CAN'T TURN IT ON!
I'm seriously bothered by this and i'm seriously going to trash it if i continue messing with it.
Someone please help me or i'll go insane.

try :download Samsung Kies3(for drivers) and Odin 1.85, port must indicate yellow box on odin when you connect your device in download mode,next try again wifi fix files on PHONE box and wait on pass green box,try even fiev times . On mine S4 work . Good luck

The problem might be cuz u are using the new bootloader (knox)... if u ar eusing that, follow the steps:
You need to install Triangle away (from google play, or just search it on google/xda) to wipe the BINARY counter. After this you will need to reflash the official samsung ROM via Odin and wipe data after installing.
Crossed fingers for you.

flashed everything tried everything wifi won't turn on
I flashed most stock firmwares out there then flashed the modem twice, then reflashed wifi fix twice. Wifi doesn't turn on. A few days ago I managed to fix it so I don't think it's hardware, or maybe now it is. Even tried custom roms and kernels. Anyone anywhere has any idea? Please

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

ROOT Samsung Galaxy Tab S5e SM-T725

i search a Root for the Samsung Galaxy Tab S5e SM-T725 , for install a Mod PlayStore .....

Are you asking if there is root for the Tab 5se yet?

yes ... is there a root for the tab S5e?

Yes, there is root for the S5e, it is complicated atm...
https://forum.xda-developers.com/galaxy-s10/development/magisk-root-galaxy-s10-series-t3918699
DerZero said:
yes ... is there a root for the tab S5e?
Click to expand...
Click to collapse

I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?

DerZero said:
I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?
Click to expand...
Click to collapse
I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:
https://topjohnwu.github.io/Magisk/samsung
More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.

nsx2brz said:
I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:
https://topjohnwu.github.io/Magisk/samsung
More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.
Click to expand...
Click to collapse
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.

AHE_XDA said:
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
Click to expand...
Click to collapse
A few caveats with XAA:
For 'OEM Unlock' to show, you must be connected to WiFi to unlock the Bootloader.
And if you 'Factory Reset' after unlocking it, it disappears completely.
If you change the date, time or year, it doesn't return until you reconnect to WiFi.

Interesting, just got mine today tempted to try this.
---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------
AHE_XDA said:
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
Click to expand...
Click to collapse
Please let us know how it went!

I've managed to unlock the bootloader.
I'll post a few pictures in a moment.
Note: This is for the SM-T720.

AHE_XDA said:
I've managed to unlock the bootloader.
I'll post a few pictures in a moment.
Note: This is for the SM-T720.
Click to expand...
Click to collapse
-----
I've patched the AP file but keeps failing when Odin attempts to write 'Modem':
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
For those curious; I'm on the latest version of Odin and running stock XAC firmware.
That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.
But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.

Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...
AHE_XDA said:
-----
I've patched the AP file but keeps failing when Odin attempts to write 'Modem':
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
For those curious; I'm on the latest version of Odin and running stock XAC firmware.
That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.
But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.
Click to expand...
Click to collapse

nsx2brz said:
Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...
Click to expand...
Click to collapse
Do you happen to have the URL for the thread?
I'm apt to try this again in a week or two.

best would be a root of CF-AUTOROOT or a TWR and a ROOT.ZIP -.-

https://forum.xda-developers.com/ga...ragon-root-waiting-discussion-t3919024/page24
Post #235 is where is says what worked. Good luck! I probably won't have time to try mine until next month.
AHE_XDA said:
Do you happen to have the URL for the thread?
I'm apt to try this again in a week or two.
Click to expand...
Click to collapse

I have Magisk working on my Tab S5e (have had it working since the day after it launched). I was going to post instructions, but we still don't have a Tab S5e forum to post em in.

PewPewK said:
I have Magisk working on my Tab S5e (have had it working since the day after it launched). I was going to post instructions, but we still don't have a Tab S5e forum to post em in.
Click to expand...
Click to collapse
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.

btonetbone said:
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
Click to expand...
Click to collapse
Yeah, sure. I wrote this in an e-mail to someone who messaged me regarding rooting the Tab S5e, but it's a tad bit old. Regardless, I'll paste it verbatim here:
Because my installation process was hardly linear (I ran into many problems along the way), I can't guarantee that these are exclusively the exact steps you would need to take to get it working. But I think this should be a compilation of all the final (working-ish) steps I took.
(1) Setup tablet for first time, go to settings, enable developer mode, and flick the OEM Unlocking switch.
(2) Turn off the Tab S5e and boot into Download Mode by holding Power and Vol Up + Vol Down. Then hold up on the Vol Up button (not just a quick press) as it says to enter Bootloader Unlocking Mode. Follow the instructions there to fully unlock the bootloader.
(3) The tablet will be formatted at this step. After the bootloader is fully unlocked, make sure you boot back into the Tab S5e and perform the set up again. Enable developer options and make sure that the OEM Unlocking switch is turned on. Yes, again. This step is necessary apparently due to some changes Samsung made with their new VaultKeeper service? If you don't you may soft brick the device.
(4) Install @ianmacd's Magisk Manager application on your Tab S5e. Download is here. [Update: TopJonWu's official Magisk build should now work fine.]
(5) Download the latest Tab S5e firmware build. I found my copy here. Extract from it the AP file. Transfer this file to your Tab S5e.
(6) Back in Magisk Manager, go to settings and look for "Update Channel." Here's where I'm a little uncertain of what I did that finally got it to work, so I'll recommend two steps...
(7a) Select the ianmacd update channel and return to the home screen of Magisk. [Update: This shouldn't be necessary anymore, especially if you installed the official Magisk Manager earlier.] Click install, then choose the patch file option. Locate the AP file you transferred earlier and wait for it to finish creating a "magisk_patched.tar" file. Transfer this file to your computer and rename it "magisk_patched_ianmacd.tar," then delete the old magisk_patched on your device.
(7b) Do the same for the Canary (debug) update channel. Patch the AP again, and locate the patched file, copy it to your computer, and rename it to something clear.
(8) This is an odd step I had to follow to avoid errors flashing. It turns out of the several times I tried making the patched images, I almost always inevitably had some file in the archives getting corrupted. So open up both magisk_patched.tar's and test them for errors. I did this in 7-Zip, but there's probably ways to do it in WinRAR, too. If it gives you any error, take a note of which file it failed on because that guarantees your flashing will fail in later steps. In fact, the reason I recommended doing two different methods for patching magisk above was because the first ianmacd patch I tried had a corrupt recovery.img. What I ended up doing to fix it was extracting a working (non-error checking) recovery.img, vbmeta.img, and boot.img from the two different patched Magisks and then recombined them myself into my own Magisk tar. I also kept the meta-inf folder in there for good measure, though I don't think it's necessary? So in the end, I had what I called a "magisk_patched_lite.tar" that contained exactly three images: recovery.img, vbmeta.img, and boot.img, along with the meta-inf folder and ensured 7-Zip did not return any errors on the archive.
(9) Reboot the tablet to Download Mode. Press Vol Up to start. Attach the Tab S5e to your computer, and start Odin (I used v3.13.1_3B_PatcheD).
(10) Put some working archive of the patched magisk in the AP slot and uncheck "Auto Reboot." I don't know if the 'lite' version is sufficient for your first flash, but I suspect that it is (it would not be sufficient if you're pre-patching an updated firmware for the Tab S5e). Let Odin rip and see if you get any errors.
(11) Assuming Odin was successful, hold Power and Vol Down to exit Download Mode, then immediately switch to Power and Vol Up once the screen shuts off. Continue holding these until you are greeted with Recovery mode.
(12) Use the volume keys to select Factory Reset/Wipe Data. Execute that to make sure the tablet is properly formatted.
(13) Use the reboot into system option at the top of recovery. Hold Power and Vol Up until the "Bootloader is Unlocked" warning screen shows up, then release.
(14) If you're lucky, you should eventually see a red warning message about not having Samsung software installed. That's a good sign. My tablet fumbled around these steps and looked like it was gonna bootloop for a while? But eventually, it ran its course and booted.
(15) You hopefully have root installed now. Set up the tablet one last time, install the ianmacd Magisk Manager again and open it up. If it says Magisk is installed, great job, otherwise... I don't know where the issue is because this rooting sequence is way more complicated than for other devices! At some point, I think after a reboot, Magisk Manager asked if it could do some additional setup stuff. Obviously let it do that.
Click to expand...
Click to collapse
I updated a few steps that have changed since writing that up originally. Since the Tab S5e hasn't seen a software update yet, I'll also upload my (hopefully) working copy of the flashable patched_magisk_boot.tar that you can flash in the AP slot in Odin. No guarantees it works, but I can't imagine why it wouldn't. In theory, you should be able to skip several steps above and simply OEM (bootloader) unlock the device, then flash this in Odin.
Also important! Fundmentally, this version of root works very differently from what you may be used to. See here for detailed information. Normally root is installed onto the boot partition, but Samsung did some ****y stuff this generation to be "compliant" with Google's new rules, but still do things in their own special way, so now to achieve root Magisk has to live on the recovery partition.
Magisk living on the recovery partition means that in order to boot with Magisk enabled, you have to boot into recovery. So to boot with root, hold power and vol up until you see the "bootloader is unlocked" warning screen, then release. If you hold Vol Up, you will be taken to recovery, which will boot the system partition with root enabled. Otherwise, your tablet will boot the system partition without root. So if you do not do this step, root will not work (i.e. you'll boot into system without Magisk).
Hope this helps you achieve root.

Great Instructions.
The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.
PewPewK said:
Yeah, sure. I wrote this in an e-mail to someone who messaged me regarding rooting the Tab S5e, but it's a tad bit old. Regardless, I'll paste it verbatim here:
I updated a few steps that have changed since writing that up originally. Since the Tab S5e hasn't seen a software update yet, I'll also upload my (hopefully) working copy of the flashable patched_magisk_boot.tar that you can flash in the AP slot in Odin. No guarantees it works, but I can't imagine why it wouldn't. In theory, you should be able to skip several steps above and simply OEM (bootloader) unlock the device, then flash this in Odin.
Hope this helps you achieve root.
Click to expand...
Click to collapse

btonetbone said:
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
Click to expand...
Click to collapse
netjetman said:
The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.
Click to expand...
Click to collapse
Yep, good point. I forgot to include that because in the original e-mail thread, it was already known and implied. But I'll add it to the post here so folks will catch that. Annoying for sure, but at least it works.