Database Users

T320XAR1ANK1 Extracted Stock Firmware

I usually do this for the Note 3 I have, and it comes in really useful for devs, those running other roms, etc, that just want to upgrade the modem/wifi, bootloader, and CSC without messing with everything else. It's also handy to replace the stock kernel if you need it for whatever reason (towelroot anyone? ). Since I recently picked up a Tab Pro 8.4 from swappa, I did this for mine to do the upgrade, and thought I'd be nice and go ahead and share the extracted parts for everyone else to enjoy.
Here's the MODEM+NON-HLOS (both together and as separate files), Bootloader, Kernel, CSC, and Recovery I extracted from the new T320 1NK1 Firmware. In desktop Odin 3.09, Kernel and recovery would go in AP. Modem + NON-HLOS goes in CP, Bootloader in BL. If you flash the bootloader separately, make sure to tick the box that says bootloader update.
Bootloader:
CSC: http://www.mediafire.com/download/dje1u61d8pk8dou
Kernel: http://www.mediafire.com/download/bi2jsdcub9c9k82
Modem + NON-HLOS (Combined): http://www.mediafire.com/download/3x5bela3la8mllh
modem.bin: http://www.mediafire.com/download/oatak8vgg5vdlu5
NON-HLOS.bin: http://www.mediafire.com/download/xuaar11efato1j7
Recovery: http://www.mediafire.com/download/206e1b2g1uact6s
Full Stock Image T320UEU1ANK1-T320XAR1ANK1: http://www.mediafire.com/download/ul9d01zlrq3dl72/T320UEU1ANK1_T320XAR1ANK1_HOME.tar.md5
If you have trouble getting the bootloader and/or Modem to stick, install "Triangle Away" by @Chainfire and follow the directions to reset your counter (even if it says zero), then boot into download mode, and re-flash them with Odin and they should stick (WARNING: Triangle Away WILL TRIP KNOX).
NOTE: It has also been noted by several people that booting directly into download mode from a powered-off device and flashing the BL/Modems will make them stick as well.
To verify, you can download "Phone Info - Samsung" and make sure that all applicable items say either T320UEU1ANK1 or T320XAR1ANK1 (Bootloader,, PDA and CSC). NOTE: Not all functions of this app work for our tablets, but most do.
Triangle Away by @Chainfire: https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Phone INFO ★Samsung★ by @vndnguyen: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Mobile Odin Pro: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
Enjoy, and as always, slap that Thanks button!

I'm planning on rooting and going back to an old Kernal. After rooting, I am going back to the NK1 kernal but I'm on T320UEU1ANK1. Can I go back to NK1 kernal using the T320XAR1ANK1 kernal you your post or do I have to find the T320UEU1ANK1? I know you have the full T320UEU1ANK1 image but I just to ODIN T320UEU1ANK1 kernal.
Thanks in advance.

Deca4 said:
I'm planning on rooting and going back to an old Kernal. After rooting, I am going back to the NK1 kernal but I'm on T320UEU1ANK1. Can I go back to NK1 kernal using the T320XAR1ANK1 kernal you your post or do I have to find the T320UEU1ANK1? I know you have the full T320UEU1ANK1 image but I just to ODIN T320UEU1ANK1 kernal.
Thanks in advance.
Click to expand...
Click to collapse
You can use the kernel in my post.
Sent from my leanKernel 3.16 powered stock 4.4.2 SM-N900T

Thank you!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

Just a question but I believe it does not affect root, if I were to install the modem/firmware I would not lose root correct? Also, if you were to flash the whole package, does towel root or manual root (think I used Hashcode script vs towel root) does the new firmware allow root access? I don't believe these devices are as locked down as a carrier device, but just wondering! When people refer to firmware and modem, what part is the firmware on this actually? I see the modem, but is firmware part of the NON-HLOS or what ?Thanks!
Edit: Seeing another thread, seems CF Auto-Root will still work, answering my above questions, thanks and sorry for not fully researching first!

bigmike35 said:
Just a question but I believe it does not affect root, if I were to install the modem/firmware I would not lose root correct? Also, if you were to flash the whole package, does towel root or manual root (think I used Hashcode script vs towel root) does the new firmware allow root access? I don't believe these devices are as locked down as a carrier device, but just wondering! When people refer to firmware and modem, what part is the firmware on this actually? I see the modem, but is firmware part of the NON-HLOS or what ?Thanks!
Edit: Seeing another thread, seems CF Auto-Root will still work, answering my above questions, thanks and sorry for not fully researching first!
Click to expand...
Click to collapse
My Tab Pro 8.4 (Wifi) shipped with the latest firmware already installed. I didn't want to use CF Auto-Root because it trips the Knox flag, so I flashed this kernel (http://forum.xda-developers.com/showthread.php?t=2786800) and then was able to use TowelRoot, which doesn't trip Knox.

Nice job. I upgraded using the full image, downgraded the kernel, rooted my T320, restored your kernel. Very simple and all worked great. Thanks for this.

@toastido Could you give me a link to Kernel BNI1 (Portuguese version) plz?
Thanks in advance.

I337UCUGOC3 bootloader locked, want to update to I337UCUGOK2 to unlock bootloader

I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help

Once the bootloader is locked, it will always be locked until someone finds a way to unlock it. Updating the bootloader will not allow it to be unlocked.

cybercuate said:
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Click to expand...
Click to collapse
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.

help... I want to RMA it
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.

cybercuate said:
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
Click to expand...
Click to collapse
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.

Trying Odin-Stock NB1
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
sway8966 said:
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Click to expand...
Click to collapse
Thanks. I'll try Odin it with the stock rom from your link. I'll post news here when it finish flashing

1st part - Success
I'm on 4.4.2 NB1, flash counter back to normal but still bootloader locked
Now I have to go back to OC3 to RMA it.
OTA does nothing, smartswitch shows no updates neither kies.
I'll have to Odin it back to OC3
Can I have some help?

And Success. I'm back on stock OC3 no root.
time to RMA
- camera still doesn't focus
- boot screen is back to normal but when in odin mode the counter shows 0x1
- sometimes shows "sim card could not be detected" or similar messages and force me to restart the phone (just happend 2 times until now, never happend before)
I followed this thread
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Post 2
Thanks to sway8966

On PD1 rooted rom, but still on OC4 bootloader help.

So i have spent the last 4-5 hrs trying to get this phone to work for my brother and i am stuck at the moment. Need some help
Ever since OC4, i never updated the bootloader, only the ROM. phone was in OK3....I followed the thread for unlocking the bootloader, and gained the MODE: Developer.
I tried to follow the thread for muniz and got the files i needed.
Once i got MM up, noticed that WIfi, capacitive buttons wouldnt work. So i reverted back to PB1 downgrade.
i once again followed the steps and got MM back into the phone, but still the same problem as above.
Here is how the phone is currently:
Bootloader screen: " Current binary custom,system status custom, reactivation off, qualcomm secureboot enable (CSB), AP SWREV S1,T2,R1,A1,P1 and MODE: Developer, UDC Start
Recovery : Currently it boots to TWRP 3.0.2-2
Once booted into android, i used Samsung Mobile Info.
Build Number: MMB29M.G900VVRU2DPD1
Kernel version: 3.4.0-8025411
PDA: G900VVRU2DPD1
CSC: G900VVRU2DPD1
Baseband: G900VVRU2DPD1
Bootloader: G900VVRU1BOC4
So, can i just update the bootloader to MM, unlock it, re root, and fix? DO i have to revert once again to PB1?
I need some direction as to how get bootloader to PB1 or PD1...
Thanks

Exact same problem here. I've been struggling with this for about a week now. PD1 bootloader will NOT flash in Safestrap or FlashFire. I even tried TWRP for the heck of it.
Sent from my SM-G900V using XDA-Developers mobile app

I had the same problem that I could not get the buttons to work over several days several and several different methods, each time having to ODIN back to PB1. Two of the times I even had to go find a flash file for firmware because the ODIN did not restore the bootloader back to PB1. When I did finally get it to work I followed the information in the OP for unlocking the BL that I will paste below the main thing being place the ROM on the phone storage not the SD as the files flashed below use the TWRP that doesn't see SD cards
Download these 2 files and place on phone And A Custom Rom
PB1_Flashfire_Prepare.zip https://www.androidfilehost.com/?fid=24572369242686444
PD1_Firmware_With_Dev_Aboot_Twrp_Recovery_Image_Flashfire_Only.tar.zip https://www.androidfilehost.com/?fid=24572369242686471
Reboot to TWRP and flash PB1_Flashfire_Prepare.zip
Reboot
Open Flashfire (It will be installed by the zip you flashed in TWRP) grant supersu permission
Goto Flashfire Settings check box to Flash bootloaders and uncheck box for Emulate framebuffer
Goto Actions
Now add Flash firmware package and choose PD1_Firmware_With_Dev_Aboot_Twrp_Recovery_Image_Flashfire_Only.tar.zip
Now manually check on all the partions to flash. Check them all make sure to scroll down. Now click check mark at top right for ok
Now on the warning dialog that pops up about splitting protected partitions select no
Now in the actions dialog box where it says reboot change that to recovery
So it should look like this
Flash firmware package
Primary Bootloader
Secondary Bootloader
Etc........
EverRoot
EverRoot Disabled
Reboot
Recovery
Click FLASH
When finished phone will reboot to TWRP
Wipe Data, Wipe Cache, Wipe System
Install Custom Rom
For the custom rom I used the one from here labeled G900V_PD1_Stock_Rooted_ROM.zip http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and the ROM took short of a min to boot past the samsung screen then roughly 8-10 mins to boot past the red Verizon screen.
Of course once it reboots and your up and going on the new rom you'll have to flash TWRP I used 3.0.0.0
Hope this helps.
---------- Post added at 03:22 PM ---------- Previous post was at 03:06 PM ----------
Oh and if you make a Nandroid backup before you try PD1, you can always ODIN flash TWRP and then just restore your previous rom (that's what I kept doing after the first 2 total losses)
TWRP https://www.androidfilehost.com/?fid=24459283995310730

Thanks ecen92!! i saw your message a bit late, but i did go back at it with a fresh mindset last night and got it working!!
Here is how i did:
So, after many reading between the lines, something about bootloaders not flashing if the kernel and firmware dont match... anyways, since i was on OC4 i almost went back to a OC4 full tar, but couldnt find it... Glad i didnt.
So i decided to see if i could restore to PB1 fully, and start from there....
I flashed the PREPARE YOUR PHONE FOR ROOT from here http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
But after it finished, now i was in PB1 but still with OC4 bootloader.... something told me to redo it.... so i did.. i RE DID the above flash again!!! and once completed i was on a full PB1 with locked bootloader.
The trick for me was that i HAD TO FLASH THE PB1 FULL TAR 2X IN A ROW!
From there i did the working root method found on the same thread http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
After i gained root, i then unlocked the bootloader based on this steps http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
After unlocking the bootloader, then i followed the instructions labeled in light blue called "Upgrade To PD1 Rom With PD1 Unlocked Bootloader From 5.0 TW Rom With PB1 Unlocked Bootloaders" (annoying a** color to see)
After which i was then on PD1 rom rooted, PD1 unlock bootloader and no more problems with wifi, capacitive buttons not responding, etc.
Hope i can help anyone else stuck with this problem.

Good to hear you've got it all working! :good:

I will make a post for those confused that still dont know how to properly update to PF4 rooted using this post http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
The initial instructions for rooted arent too clear. I have asked for clarification from the source and others, and my questions have fallen on deaf ears.
I had my brothers phone on PD1 rooted/unlocked, and by flashing the rooted version on the OP followed by stock PF4 bootloader, bricked the software. (The msg that it cant boot) and after D-king around for 4 hrs, i finally got it.
Anyways here is the steps i did ( i dont own steps, just trying to copy paste info to paint a clear picture)
Had to flash the PB1 full tar on ODIN
Then i had to root the PB1 as mentioned here. http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
After root i had to unlock bootloader. http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
I used Method 2: Unlocker via Safestrap Samsung_Bootloader_Unlocker.zip in safestrap or flashfire
After this i verified i was on PB1 rooted and unlocked.
From there i went to Flashfire and flashed G900V_PF4_Stock_Rooted_ROM.zip (For "Unlocked" Bootloaders Only!) as posted on the OP
This placed me on PF4 ROM and firmware, but with a PB1 unlocked bootloader. (This is where the back button, recents and wifi dont work)
I then flashed TWRP 3.0.0 via ODIN
From there i followed the "If You Already Have Bootloader Unlocked And On A Samsung TW Rom" found here http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
In case instructions changed, like it has on the past, they are:
In TWRP Flash TWRP_Prepare.zip
Reboot to Download Mode
In Odin Under AP slot load PB1_Firmware_Only_NK2_Kernel.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
When finished on reboot watch for Safestrap Splash Screen and enter Safestrap
Now goto Power Menu/Reboot Menu and reboot to Download Mode
Make sure in download mode the current binary is Official. If it is not reflash In Odin Under AP slot load PB1_Firmware_Only_NK2_Kernel.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit
Click Start on reboot enter Safestrap reboot back to download mode and make sure binary status is Official
If Binary Status is Official Pull battery restart and enter SafeStrap
Flash: SafeStrap_PF4_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull Battery enter download. Flash via ODIN TWRP 3.0.0 as the previous flash will install 3.2 which doesnt see the SD card.
There u go, thats it, this will have you on a rooted/unlocked PF4.

Really old modem and bootloader, what are my options from here?

It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?

beerindex said:
It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?
Click to expand...
Click to collapse
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220

mattzeller said:
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220
Click to expand...
Click to collapse
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?

beerindex said:
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?
Click to expand...
Click to collapse
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220

mattzeller said:
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:

beerindex said:
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:
Click to expand...
Click to collapse
Feel free to post back here or PM me if you have any more questions or problems, it wouldn't be the first time walking someone through the process via pm here or other methods
Sent from my SCH-R220

Installing TWRP on Galaxy S4 GT-I9515 (Value Edition)

Hello everyone,
I was thinking about installing Lineage OS on my Samsung Galaxy S4 GT-I9515 (Value Edition) currently running Stock Android Version 5.0.1 without root.
Is the version of Lineage OS and TWRP I found at https://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-cm14-1-galaxy-s4-jfvelte-gt-i9515-t3534552 appropriate for that purpose?
Now, my confusion arises from the fact that different guides seem to give incomplete or even contradictory instructions on how to approach that. As a first step, I need to install a custom recovery, such as TWRP:
Does this require my device to be rooted?
Some guides apparently require my bootloader to be unlocked; Is this necessary? If so, how do I do that?
Other guides suggest that I use Odin. Is this the correct approach? Does my bootloader need to be unlocked for that method? Is a root required?
Anything else I should pay attention to?
Thank you very much in advance

You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin

Not able to root S4 GT-I9515
TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
I tried to flash CF-Auto-Root on my phone after completing the flash till reset on odin phone gets restarted and is showing following messages on top left corner on the samsung s4 logo screen
recovery booting....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
it is not going any further than this please help.

TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
the twrp file bricks the phone

raffux3 said:
the twrp file bricks the phone
Click to expand...
Click to collapse
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google

TheFixItMan said:
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google
Click to expand...
Click to collapse
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)

raffux3 said:
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)
Click to expand...
Click to collapse
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that

TheFixItMan said:
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that
Click to expand...
Click to collapse
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always

raffux3 said:
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always
Click to expand...
Click to collapse
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)

TheFixItMan said:
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)
Click to expand...
Click to collapse
I have re-installed the usb drivers and odin works fine finally. I will try to root and install twrp again...thank you for support