Develop Bugs

[GUIDE][HOW TO][N900W8]Canadian Note 3 - KitKat 4.4.2 ROM with WIFI/BT/NFC Fix

*MEXICAN USERS, PLEASE SKIP TO PART 4*
The following is for Canadian Note 3 users - model number N900W8. Please do not attempt the following on ANY other device (including the N900T). I am not responsible for your phone or any damages, so perform at your own risk.
[PART ONE - UPGRADE FROM 4.3 TO 4.4.2 STOCK]
1. Download the following Stock TelCel (Mexican) 4.4.2 files.
http://pc.cd/7kH (AP - System)
http://pc.cd/gXH (BL - Bootloader)
http://pc.cd/K7H (PIT - Repartition)​
2. Download the following Canadian modem and CSC.
http://fs1.androidfilesharing.com/d0ed8bf1a29d2c01 (CP - Modem)
http://fs1.androidfilesharing.com/6cb078fbe8a64316 (CSC - Carrier Specific Code)​
3. Download Odin 3.09.
http://fs1.androidfilesharing.com/7625af2fbef08abc​
4. Backup important files to your computer and boot into download mode (hold HOME+VOLUME DOWN during boot).
5. Plug the phone into your computer, preferably with the cable that came with the phone.
6. Open Odin 3.09 and load the 5 files you just downloaded into their corresponding spots.
7. UNCHECK Re-Partition. Make sure Auto Reboot and F. Reset Time are CHECKED.
http://i.imgur.com/f5vVc5h.jpg​
8. Click start and wait for it to finish.
*Notes*
-This will factory reset your device.
-There has been some controversy over whether to leave Re-Partition checked or unchecked. Try unchecked first, then checked if it doesn't boot up.
-If you are having problems, try booting into recovery (hold HOME+VOLUME UP during boot) and factory resetting your device and restarting.
-If you boot and find bloatware from a different carrier or something isn't working, open the dialer and type *#272*YOURIMEI# and change your CSC to the appropriate carrier. This will factory reset your phone.
-We have the ability to revert back to 4.3 (flashing stock 4.3 rom in Odin), but the method isn't concrete. You should be ready to stay on 4.4.2 if you are going to flash it.
-If you are having issues writing to the SD Card, take a look at this thread - http://forum.xda-developers.com/showthread.php?t=2617921
__________________________________________________
[PART TWO - ROOT AND CUSTOM RECOVERY]
1. Download Chainfire's CF-Auto-Root file.
http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip​
2. Load into Odin 3.09's AP section and flash in download mode.
3. Download BigBiff's N900W8 TWRP recovery OR Chenglu's CWM recovery.
TWRP - http://techerrata.com/bigbiff/hltecan-recovery.img.tar​CWM - http://d-h.st/users/xiaolu/?fld_id=31963​
4. Load into Odin 3.09's AP section and flash in download mode.
*Notes*
-Assume this will trip Knox warranty to 0x1. Some users have reported otherwise, but just be ready for it.
__________________________________________________
[PART THREE - CUSTOM 4.4.2 ROM AND KERNEL + WIFI/NFC FIX]
1. Download your favourite custom 4.4.2 rom from the N9005 forums.
2. Download custom (N900T) 4.4.2 kernel.
Custom (CivZ) - http://www.androidfilehost.com/?w=files&flid=12054​Custom (Wootever) - http://forum.xda-developers.com/showthread.php?t=2581888​
3. Download the WIFI/NFC fix (NB7 Source)
fs1.androidfilesharing.com/2a941b72c218c505​
4. Place files on SD card. Some roms are known to wipe your internal storage.
5. Boot into TWRP Recovery and wipe system, data, cache, and dalvik cache.
6. Install custom rom, kernel, and WIFI/NFC fix, then reboot.
*Notes*
-A custom rom alone will break WIFI and NFC, follow these instructions to install a custom rom and fix connectivity.
-The stock kernel caused connectivity issues on custom roms, use CivZ's custom kernel
__________________________________________________
[PART FOUR - MEXICAN USERS]
1. Complete PART ONE using these files instead of the ones above.
http://pc.cd/7kH (AP - System)
http://pc.cd/gXH (BL - Bootloader)
http://pc.cd/dXH (CP - Modem)
http://pc.cd/K7H (PIT - Repartition)
http://pc.cd/97H (CSC - Carrier Specific Code)​
2. Complete PART TWO of this post. (Root and install TWRP)
3. Make a full nandroid backup via TWRP
4. Complete PART THREE of this post (custom rom, kernel, and fix).
5. To fix connectivity, boot into recovery and restore ONLY the EFS files and the modem from the nandroid you made and reboot.
__________________________________________________
Who should you thank?
@kirabyte - Original TelCel N900W8 4.4.2 base and links
@Chainfire - Root
@bigbiff - TWRP
@Chenglu - CWM
@civato - Custom Kernel
@Wootever - Custom Kernel
@miscom - Flashable fix base
@turilo - Help with WIFI fix and testing
@mixxy - Help with NFC fix and testing
@xBlackDroid - Signal fix method for Mexican variant
__________________________________________________
Last but not least, PLEASE read the thread in its entirety before you ask any questions.
Thank you! Good luck and happy flashing.

Oogar said:
Thought this should branch off into its own thread.
I've managed to successfully install 4.4.2 onto my Rogers Note 3. I extracted the modem and CSC from the latest Rogers 4.3 and flashed with Odin 3.09 along with TelCel (Mexican) files below.
Use the PIT, BL, and AP from this website --> http://androidmx.net/2014/01/actualiza-tu-galaxy-note-3-n900w8-a-kitkat-4-4-2/
Use the CP and CSC from here --> https://www.mediafire.com/?5ww5zzb2s501njt
There is a little bit of controversy on this...but I did NOT have re-partition checked in Odin. I would try having it unchecked first, and play around after if you have issues.
Rooted with --> http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
Flash in Odin 3.09 using AP.
Happy flashing!
Click to expand...
Click to collapse
And what kernel was used to accomplish this? And have you tried to go back to 4.3 with this procedure?

TheAxman said:
And what kernel was used to accomplish this? And have you tried to go back to 4.3 with this procedure?
Click to expand...
Click to collapse
Stock kernel, Mexican and Canadian variants are both N900W8.
I was able to flash back to stock 4.3 with Odin a couple times last night. I will do it one more time and confirm with you though.

Oogar said:
Stock kernel, Mexican and Canadian variants are both N900W8.
I was able to flash back to stock 4.3 with Odin a couple times last night. I will do it one more time and confirm with you though.
Click to expand...
Click to collapse
I am impressed, nice work. So stock kernel, and you for sure can go back to 4.3? I believe you, but, wow. Try once more please, as this could and can be bad if it has not been tested. Thank you sir for you work and info.

TheAxman said:
I am impressed, nice work. So stock kernel, and you for sure can go back to 4.3? I believe you, but, wow. Try once more please, as this could and can be bad if it has not been tested. Thank you sir for you work and info.
Click to expand...
Click to collapse
Just successfully flashed back to stock Rogers 4.3.
Flashed stock via odin, first boot was hanging so I factory reset in recovery. Works fine now.

Thanks for this bro!!

this is probably more wishful thinking than any real hope of it having happened yet - but I have to join the hordes to ask the one question - has anyone flashed on TMOBILE Sucessfully yet? (Intellectually I am sure I know the answer - but I feel compelled to ask the question just the same)..

http://forum.xda-developers.com/showpost.php?p=49524853&postcount=543
Here's how a Canadian user got his to work for more proof. You folks are so lucky & im so jealous! Key thing that he did was check re-partition

RMXO said:
http://forum.xda-developers.com/showpost.php?p=49524853&postcount=543
Here's how a Canadian user got his to work for more proof. You folks are so lucky & im so jealous! Key thing that he did was check re-partition
Click to expand...
Click to collapse
Yeah I saw this as well. I had it not work with re-partition checked, and it's worked every time since then with re-partition unchecked. Not sure what the implication of this is yet.

Oogar said:
Thought this should branch off into its own thread.
I've managed to successfully install 4.4.2 onto my Rogers Note 3. I extracted the modem and CSC from the latest Rogers 4.3 and flashed with Odin 3.09 along with TelCel (Mexican) 4.4.2 files below.
Use the PIT, BL, and AP from this website --> http://androidmx.net/2014/01/actualiza-tu-galaxy-note-3-n900w8-a-kitkat-4-4-2/
Use Rogers Modem (CP) --> http://www.mediafire.com/download/1oias85eoz8ykuh/Rogers Modem (CP).tar
Use Canadian Multi CSC-->http://www.mediafire.com/download/xn11kh614eag7ir/Canadian Multi CSC.tar (change CSC - Open dialer --> *#272*YOURIMEI# --> will factory reset)
There is a little bit of controversy on this...but I did NOT have re-partition checked in Odin.
Rooted with --> http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
Flash in Odin 3.09 using AP.
Turn off Reactivation Lock.
CWM Recovery --> http://d-h.st/users/xiaolu/?fld_id=31400
Flash in Odin 3.09 using AP.
Happy flashing!
Edit: Should note that both Canadian and Mexican variants are N900W8.
Edit 2: I flashed my sisters Note 3 with this method. Re-partition unchecked, worked perfectly. It was running stock 4.3.
Click to expand...
Click to collapse
Should this work with the tmobile n900t if I use the latest tmobile modem and csc with the methods outlined in your post?

mocsab said:
this is probably more wishful thinking than any real hope of it having happened yet - but I have to join the hordes to ask the one question - has anyone flashed on TMOBILE Sucessfully yet? (Intellectually I am sure I know the answer - but I feel compelled to ask the question just the same)..
Click to expand...
Click to collapse
I am in the process now of flashing it on tmo....hold tight.

TheAxman said:
I am in the process now of flashing it on tmo....hold tight.
Click to expand...
Click to collapse
Cant wait to hear that
Sent from my SM-N900T using Tapatalk

TheAxman said:
I am in the process now of flashing it on tmo....hold tight.
Click to expand...
Click to collapse
Remember to use a CSC from a TMO Odin rom and GL.
-Sent from my TMO Samsung Galaxy Note 3 using Tapatalk

RMXO said:
Remember to use a CSC from a TMO Odin rom and GL.
-Sent from my TMO Samsung Galaxy Note 3 using Tapatalk
Click to expand...
Click to collapse
Here's the T-Mobile CSC and T-Mobile Modem

Good luck!
@TheAxman PM me if you are having issues and want to bounce ideas back and forth

TheAxman said:
I am in the process now of flashing it on tmo....hold tight.
Click to expand...
Click to collapse
thump thump - thump thump - thump thump..thump tump thmp thm thmpthmpthmp..
be still my beating heart..... lol - can't wait to hear what happens - fingers crossed...

Oogar said:
Good luck!
Click to expand...
Click to collapse
I'm downloading the files. I found the tmobile modem in bin format, will that suffice or will I need to find the tar?
Anyone have a link?

toyanucci said:
I'm downloading the files. I found the tmobile modem in bin format, will that suffice or will I need to find the tar?
Anyone have a link?
Click to expand...
Click to collapse
Apparently you can flash a modem.bin with Odin...give it a quick google.
I didn't know this and used Cygwin64 Terminal to convert it to a .tar
EDIT: Here is the T-Mobile Modem as a .tar.
https://www.mediafire.com/?xlhlrd09l9pl0k3

TheAxman said:
I am in the process now of flashing it on tmo....hold tight.
Click to expand...
Click to collapse
So how did it go? If t-mobile can do it than AT&T user like me has a chance lol..

Walter.White said:
So how did it go? If t-mobile can do it than AT&T user like me has a chance lol..
Click to expand...
Click to collapse
It didn't boot up.. Lol
Sent from my Nexus 5 using Tapatalk

[How-To][GUIDE] Update and Root T999 JB 4.3 update - UVUENC2 Firmware

T999 JB 4.3 update - UVUENC2 Firmware
Samsung And T-Mobile have released the next update UVUENC2 for SGH-T999.
EDIT - @mrRobinson has a Root66 version of UVUENC2. That version is KNOX Free. So my recommendation is to visit his thread and using that firmware instead.
WARNING - The following steps are only for those who had accepted the previous 4.3 Update UVUEMJC or flashed it from Root66 thread.
Essentially with the newer updates to the Odin, version 3.09 makes the process pretty easy to those who are familiar. This does work even if you have custom Rom and Custom Recovery. Both of which will be destructively replaced by the new firmware. So take a Nandroid!!! Those with Stock firmware UVUEMJC, please take a Titanium Backup of all the essential stuff to external SD. You have been warned.
1. Obtain the Stock update UVUENC2 from SamMobile Link.
2. Download the CF-AutoRoot zip file for D2TMO by @Chainfire.
3. Obtain Odin 3.09 from here. Do not run Odin.
4. Take a backup of important stuff and put the phone in Download Mode.
5. Connect the phone to the PC and let the drivers install if not installed already.
6. Execute Odin as System Admin and then choose the Stock Firmware as AP (AKA PDA in prior versions).
7. Make sure F. Reset Time Option is Checked but Auto Reboot option is unchecked.
8. Complete the Odin flash process.
9 Once that's successful, make sure the phone is still in Download mode.
10. Again Click AP (AKA PDA) and choose the CF-AutoRoot zip previously downloaded.
11. Make sure F. Reset Time Option is Checked but Auto Reboot option is unchecked.
12. Complete the Odin Flash process.
13. When it is successful, Disconncect the phone and pull the Battery. Boot the phone to Stock Recovery and wipe Cache as well as Dalvik if there's an option for Dalvik. (My Phone does not have stock so don't remember)
14. Let the phone boot normally and enjoy Rooted Stock update. Profit !
You can use Root Checker App from Play store to confirm Root. If for some reason it failed, update the binaries of the Super user app. Upon launching that app, it may prompt for the same.
CREDIT - Nasirtech Tutorial from over here.

This is perfect, bro! Thanks for the guide!

Is there a flashable file for just the modem?
Sent from my SGH-T999 using XDA Premium 4 mobile app

Yes There is. @Synthetic.Nightmare Posted in this post.

Any chance we can get the boot.img or a flashable UVUENC2 kernel file? Some of us are having issues with wifi and it might be bc of the conflicting MJC kernel and NC2 modem

pp085ster said:
Any chance we can get the boot.img or a flashable UVUENC2 kernel file? Some of us are having issues with wifi and it might be bc of the conflicting MJC kernel and NC2 modem
Click to expand...
Click to collapse
Care to try this out for me?
It's the UVUENC2 boot.img & kernel modules: [REMOVED FOR NOW]
EDIT: This one works: modified UVUENC boot.img

Totally agree
Is very frustrating dont have ROOT on T999UVUENC2.
My T999 was updated from 4.1.2 to 4.3 T999UVUENC2 directly and was a big mistake I alredy loose my root and cant instal CM11 by any way since I cant disable KNOX.
Heeeelp

Solved

Synthetic.Nightmare said:
Care to try this out for me?
It's the UVUENC2 boot.img & kernel modules: UVUENC2 boot.img
Click to expand...
Click to collapse
Okay so first of all the zip file gave me an assert failed (error 7, something about writing raw file to block7) but i got round that. Second of all wifi works like a charm now but, third of all, SELinux is set to enforcing instead of permissive.
Care for a fix? haha

pp085ster said:
Okay so first of all the zip file gave me an assert failed (error 7, something about writing raw file to block7) but i got round that. Second of all wifi works like a charm now but, third of all, SELinux is set to enforcing instead of permissive.
Care for a fix? haha
Click to expand...
Click to collapse
I'll check it out. I basically just merged a 4.3 TW install script with what I use for harkness, didn't test since I tend to stick to aosp. I think I might know what I forgot to change though. Would you mind telling me the last thing the installer says (I.e. "installing modules..."), just to help me be sure?
Sent from my SGH-T999 using Tapatalk

Synthetic.Nightmare said:
I'll check it out. I basically just merged a 4.3 TW install script with what I use for harkness, didn't test since I tend to stick to aosp. I think I might know what I forgot to change though. Would you mind telling me the last thing the installer says (I.e. "installing modules..."), just to help me be sure?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It installs the modules but then gets stuck at extracting boot.img. The exact error is:
assert failed: write_raw_image("/cache/boot.img", "/dev/block/mmcblk0p7")
Does that help? :good:

Yes. That's exactly what I needed.
Went ahead and decided to just go ahead and install TW for some time just to get it working right.
This one should work. Tested and tried on the latest DanDroid.
I've repacked the ramdisk so that androidboot.selinux=permissive (you can check this via terminal by entering
cat /proc/cmdline
after "su"...without quotes), though the settings still seem to show selinux as enforcing.
[LINK REMOVED FOR ANYONE DIRECTED HERE]
EDIT:
Latest T999 boot.img with selinux permissive and init.d support by @enewman17
http://www.mediafire.com/download/v57ka148accbky8/T999_UVUENC2_boot-img_init.d.zip

That works great thanks! let me repost it for the other users that had problems with it too ok? thanks again!
Sent from my SGH-T999 using xda app-developers app

problem with UVUENC2 update
I am on T Mobile, and received the UVUENC2 update on my SGH-T999 Samsung Galaxy SIII. But I believe that resulted in my S3's wifi radio becoming unstable-- on multiple hotspot sites (including my very reliable SSID at home), it is regularly reporting that is disconnected due to "the internet connection on this wifi site is unstable/slow" when in fact, I know that is not the case, at all. What I have to do now to correct this temporarily, is to restart my S3. But it will eventually repeat this annoying (and erroneous) "unstable/slow" wifi error reporting & disconnection. Just thought I would pass this along, since I noticed this problem with mine, specifically and only after I got this update-- the wifi connection on my S3 was working fine historically, til then.

Would this work on the videotron gs3? the baseband is different

Yoddel_Hickory said:
Would this work on the videotron gs3? the baseband is different
Click to expand...
Click to collapse
No it will not. Even the bootloader is different.

Damn well thank you, i'll try something else

I updated to 4.3 UVUENC2 from the OTA upgrade I got from tmobile, but I can't flash a root66 version of this because it's not released yet.
My question is, I thought you couldn't just use CF-Auto-Root with a knox-enabled firmware? I thought the root wouldn't stick? Or am I misinformed?
I'm debating whether I should wait for root66 of UVUENC2 or just do your method...

Is this good to use on the t999L also?
Sent from my SGH-T999L using xda app-developers app

masondoctorjt said:
Is this good to use on the t999L also?
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
I suggest reading the thread title and the first post. A single search can do wonders.

[How-To][Tutorial] Downgrade Kit Kat 4.4.2 to JB 4.1.2

Hi,
I am just writing these steps to help those who want to downgrade from KK to JB due to any reason. Please use these steps at your own risk.
Some Background:
Recently I updated my Razr M to KK, it was Locked and Unrooted, but with the help of Twelroot and Motopocalypse I rooted and unlocked the BL.
Now somehow I didn't like the KK and wanted to go back to JB 4.1.2 because I was now having unlocked BL and rooted phone so it was easy but need to follow some steps to successfully downgrade to JB. So an unlocked BL and rooted with KK is must.
Prerequisite:
USB drivers for Razr M must be installed before proceeding.
Steps:
1. download the firmware file [Android 4.1.2
Blur_Version.98.30.1.XT907.Verizon.en.US] from http://sbf.droid-developers.org/phone.php?device=8
2. extract the above archive and replace the XML file with the one in attachment.
3. put the phone into fastboot mode and flash the firmware with RSD Lite (attached)
4. reboot and now you have JB 4.1.2
If you want to install root application again and also want to flash custom recovery then please follow the Post#5 [ATTACK] (thanks ATTACK)
Note : for custom recovery you will need the fastboot.exe if you don't have it then install minimal_adb_fastboot_v1.1.3_setup.exe(attached).
Put the phone in fastboot mode, copy the recovery to c:\ and execute the below command :
fastboot flash recovery [Path to recovery image]
If it help you then don't forget to press Thanks button !

Forgive my ignorance but this won't downgrade the kernel will it? I'm hoping it's possible to go from the newest OTA to the stable CM11 but I'm guessing this is new kernel JB. Either way thanks if I can't go to stable CM11 I'll stick with rooted 4.1.2.

Once you have a unlocked bootloader, you do not need to use "root programs". All you need to do is flash a custom recovery via Mfastboot / fastboot then flash SuperSU / Superuser.
In dhacker29's folder there are 2 different recoveries.
"msm8960" is for 4.1.2
"KITKAT" is for 4.4.2

ATTACK said:
Once you have a unlocked bootloader, you do not need to use "root programs". All you need to do is flash a custom recovery via Mfastboot / fastboot then flash SuperSU / Superuser.
In dhacker29's folder there are 2 different recoveries.
"msm8960" is for 4.1.2
"KITKAT" is for 4.4.2
Click to expand...
Click to collapse
thanks ATTACK, can you please point out that which recovery is specially for 4.1.2 because there are a lot of recoveries with msm8960 in Dhacker29's folder.
One more thing if you have flashable Su and busybox zip then please attach it , i will update the OP.
thanks alot.

DHACKER29's FOLDER
- LINK
JELLYBEAN 4.1.2 RECOVERIES
- CWM-6.0.4.6-swipe-moto_msm8960
- TWRP-2.7.0.0-moto_msm8960-hdpi
KITKAT 4.4.2 RECOVERIES
- CWM6049-RAZR-HD_M-KITKAT
- TWRP2710-RAZR_M-KITKAT
SUPERUSER - I'm just going to link to Chainfire's thread, Direct people to download from there.
http://forum.xda-developers.com/showthread.php?t=1538053
BUSYBOX
https://play.google.com/store/apps/details?id=me.timos.busyboxonrails

Could you go back to KK when you've downgraded to JB? Just asking this question early before the CM11 M8 release and the transition occurs.

TheForceUnleashed said:
Could you go back to KK when you've downgraded to JB? Just asking this question early before the CM11 M8 release and the transition occurs.
Click to expand...
Click to collapse
Yes.

ATTACK said:
Yes.
Click to expand...
Click to collapse
So just by flashing the KK firmware in RSD without any changes to the xml? Sorry for the noob questions, I realize how easy this phone can be bricked and I want to avoid it.

TheForceUnleashed said:
So just by flashing the KK firmware in RSD without any changes to the xml? Sorry for the noob questions, I realize how easy this phone can be bricked and I want to avoid it.
Click to expand...
Click to collapse
I see don't why you would need to. It would be just like restoring stock firmware via RSD Lite.

When I try to flash this, I get Failure on 2/20, sbl1

jrk190 said:
When I try to flash this, I get Failure on 2/20, sbl1
Click to expand...
Click to collapse
Did you replace the XML file included in attachment?
Sent from my ME173X using Tapatalk

Sure did. I can't even restore to 4.4.2, I'm stuck on a broken system with no wifi or signal. This sucks...

reply
is this sure it works? i read the feedback so,me user try it failed?

jrk190 said:
Sure did. I can't even restore to 4.4.2, I'm stuck on a broken system with no wifi or signal. This sucks...
Click to expand...
Click to collapse
Can you please post the error that is displayed in RSD Lite ?
The steps are tested by my 2 times, and there shouldn't be any problem. Make sure you have installed the correct drivers.
Please ensure that your bootloader is unlocked and shows BL unlocked status code 3 on BL screen.

I was also able to successfully flash back to JB with House of Moto via fast boot and full data wipe. It would not work with Universal or Keep Data, had to do full data wipe. Just another alternative :good:

xKroniK13x said:
I was also able to successfully flash back to JB with House of Moto via fast boot and full data wipe. It would not work with Universal or Keep Data, had to do full data wipe. Just another alternative :good:
Click to expand...
Click to collapse
I have used my method two time successfully, just follow the steps described in OP.

reply
Thanks You Its a Success Downgrade From 4.4 stock > CM11 > Stock rom 4.1 Thank you so much !!!

For those undergoing the downgrade process in RSD Lite and it takes forever for it to finish and the system ends up without data/signal, you need to RSD Lite flash again in order to regain signal. I believe the flashing was sluggish due to the jump from 4.4.2 to 4.1.2 and the many changes that were reflashed.
Sent from my DROID RAZR M using XDA Free mobile app

We have a wiener!
Thank you so much for the guide. After a lot of trial and error (mostly error), I thought that I had bricked my lovely XT907. I finally restored KitKat by flashing the 4.4.2 firmware with the edited XML file (deleting lines with "Getvar", "var" and "oem" in them), then followed your guide to the letter and found myself with a perfectly functional phone once again. No more sticky fastboot loops or audio-related crashes for me!
Lovely guide - thanks again! :laugh:
---------- Post added at 11:05 PM ---------- Previous post was at 10:59 PM ----------
What functionality does Busybox add? The description on the Play page is woefully sparse.
Thanks!

ATTACK said:
I *DON'T see why you would need to. It would be just like restoring stock firmware via RSD Lite.
Click to expand...
Click to collapse
*EDIT
I don't know why this posted as a new reply

Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2 [UNMODIFIED][Mirror]

Mirror Link to N910TUVU2DOK2_N910TTMB2DOK2_TMB [FULL STOCK ROM]
Also: BOOTLOADER & MODEM
---Downloads---
Full Untouched ROM from Sammobile
Mega: https://mega.nz/#!asRzgCYb!f8ssb_v6zDxYJ8_u1ygzpothj1arjRmMdM_opGz8QO0
Bootloader file:
Android File Host: https://www.androidfilehost.com/?fid=24269982087008410
Mega: https://mega.nz/#!atYXVJQI!KSMHRMcH4qPgoP7sxSWM0ihNMOU-eQwYISaimam5tdk
Modem file:
Android File Host: https://www.androidfilehost.com/?fid=24269982087008409
Mega: https://mega.nz/#!vlQ2VILY!NFCASlvP7Rf5kB3d2eN2sy3MC_3SLmQ945dRKB1nfzU
User: @eduardog131 provided links just to the modem and bootloader in a later post in this thread. I am simply providing the link in the OP Thanks!

OK so do we use odin

Thanks. Will we be able to root and custom recovery?

lilila said:
Thanks. Will we be able to root and custom recovery?
Click to expand...
Click to collapse
You should be able to ODIN flash TWRP then you will need to flash a custom kernel to get root, and flash Superuser.
I have not tried it yet though, so I have not verified if it works or not.

I tried flash clean rom via odin, fully bootup, reboot to download, installed TWRP recovery, then flashed superuser.zip. Bootloop.
There was this other article on the net about the 910C saying they got 5.1.1 but you have to flash back your booloader to 5.0.1.

Odin new firmware, Odin twrp, in twrp flash freeza's beastmode 1.1 for n910T/3, flash supersu. report.

poontab said:
Odin new firmware, Odin twrp, in twrp flash freeza's beastmode 1.1 for n910T/3, flash supersu. report.
Click to expand...
Click to collapse
Did it work?

poontab said:
Odin new firmware, Odin twrp, in twrp flash freeza's beastmode 1.1 for n910T/3, flash supersu. report.
Click to expand...
Click to collapse
Do you have a link for beastmode?

Rollablunt420 said:
Did it work?
Click to expand...
Click to collapse
Dunno. Left laptop at work but should since it's not enforcing. I'll know in a few hours.
sdaelr said:
Do you have a link for beastmode?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3238775
Alternatively AEL or other non enforcing 5.1.1 compatible kernel are needed for Samsung lollipop 5.1 or greater with root.

poontab said:
Odin new firmware, Odin twrp, in twrp flash freeza's beastmode 1.1 for n910T/3, flash supersu. report.
Click to expand...
Click to collapse
Yes, it works for me.
来自我的 SM-N910T 上的 Tapatalk

Ripped the BL/CP parts straight from the firmware.
Since I assume none of you want to exactly download a 1.84GB file for just a bootloader and modem upgrade (why would you go back to stock), here are the BL/CP parts!
-
[Update: 13-1-16: PIT file now available to recover from a bad brick]
[DO NOT USE UNLESS YOU NEED TO REPARTITION YOUR PARTITION TABLE, OR YOU'RE IN A BAD BRICK.]
https://www.androidfilehost.com/?fid=24369303960684492
INSTALLING THESE FILES
1. Load phone in download mode. (Vol down+Home+Power)
2. Open ODIN3 on your computer. (Make sure the Samsung drivers are installed.)
3. Load the booloader file in BL.
3a. Load the modem file in CP.
4. Hit the start button, and let the files flash.
5. If there are no error messages in the log portion of ODIN3, then you have successfully flashed and upgraded to the 5.1.1 bootloader.
NOTE: At this time, you CANNOT downgrade from the 5.1.1 bootloader, so take caution.
---Downloads:
Bootloader file:https://www.androidfilehost.com/?fid=24269982087008410
Modem file:https://www.androidfilehost.com/?fid=24269982087008409

eduardog131 said:
Ripped the BL/CP parts straight from the firmware.
Since I assume none of you want to exactly download a 1.84GB file for just a bootloader and modem upgrade (why would you go back to stock), here are the BL/CP parts!
-
INSTALLING THESE FILES
1. Load phone in download mode. (Vol down+Home+Power)
2. Open ODIN3 on your computer. (Make sure the Samsung drivers are installed.)
3. Load the booloader file in BL.
3a. Load the modem file in CP.
4. Hit the start button, and let the files flash.
5. If there are no error messages in the log portion of ODIN3, then you have successfully flashed and upgraded to the 5.1.1 bootloader.
NOTE: At this time, it is unknown if you can downgrade from the 5.1.1 bootloader, so take caution.
---Downloads:
Bootloader file:https://www.androidfilehost.com/?fid=24269982087008410
Modem file:https://www.androidfilehost.com/?fid=24269982087008409
Click to expand...
Click to collapse
Pretty cool... Can you please do the same for the T3 version?

domhall said:
Pretty cool... Can you please do the same for the T3 version?
Click to expand...
Click to collapse
Sure, when I get time at home. (That is, unless someone beats me.)

~~

Razgriz said:
DOK2 is for both versions of the TMo Note 4.
Click to expand...
Click to collapse
T3 isn't interchangeable with T firmware.

I'm gonna go on the limb here, I'm 50% certain you can't go back to COG2... Be very cautious... When I Odin'ed DOK2 the process seemed odd not sure why lol

Will say modem on DOK2 seems way more stable, I don't seem to have as many data drops, and me personally I could give two s**ts if I can go back to cog2..doesnt matter as you can still flash those roms, I'm on a DOK2 Bootloader and modem with a cog2 rom right now...by the way thanks for the bootloader and modem files man..lol..really didnt wanna go back to stock
Sent from my SM-N920T using xda app-developers app

manufan721 said:
Will say modem on DOK2 seems way more stable, I don't seem to have as many data drops, and me personally I could give two s**ts if I can go back to cog2..doesnt matter as you can still flash those roms, I'm on a DOK2 Bootloader and modem with a cog2 rom right now...by the way thanks for the bootloader and modem files man..lol..really didnt wanna go back to stock
Click to expand...
Click to collapse
Yeah, pretty much agree here. This new modem has given me a lot less data drops. I had really spotty HSPA, with it dropping so constantly. Tested it out during school today and it hasn't dropped.
-------
N910T3 BL+CP parts ripped! I also managed to acquire a PIT file for the T3...DO NOT LOAD THE PIT FILE INTO ODIN3! I HAVE IT IN CASE SOMEONE WHO HAS A SEVERE BRICK CAN USE IT!
Same instructions as before for flashing the BL+CP parts. Reference a few posts up.
Bootloader file:https://www.androidfilehost.com/?fid=24269982087009029
Modem file:https://www.androidfilehost.com/?fid=24269982087009028
PIT FILE (YOU HAVE BEEN WARNED! DO NOT LOAD UNLESS THERE IS A SEVERE BRICK.)https://www.androidfilehost.com/?fid=24269982087009027

Confirm once you load DKO2 BL you can't go back to COG2 BL

ALLDAT said:
Confirm once you load DKO2 BL you can't go back to COG2 BL
Click to expand...
Click to collapse
Lawdy.. lol how many threads have you asked this in. I answered this in another thread.

Need some help deodexing stock ROM

I'm new to making modifications on my phone and I need some help deodexing the ROM.
I've got a Note 4 from Sprint running Android 5.01. I've installed TWRP and made a backup. I've also downloaded the version of Xposed that I want to get installed. But when I tried to flash Xposed to the phone, I got a message that a deodexed ROM was required.
I know that Titanium Backup can be used to deodex apps but it doesn't work with the framework. Is there a tool or app that anyone can recommend to me for this? Or is there a deodexed version of Samsung's stock ROM that I can easily swap out with the existing ROM?
Any help would be much appreciated.

Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk

Thank you and some additional questions
samep said:
Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.

jmalmberg said:
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.
Click to expand...
Click to collapse
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk

samep said:
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?

jmalmberg said:
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?
Click to expand...
Click to collapse
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk

samep said:
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.

jmalmberg said:
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.
Click to expand...
Click to collapse
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk

samep said:
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.

jmalmberg said:
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.
Click to expand...
Click to collapse
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk

samep said:
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?

jmalmberg said:
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?
Click to expand...
Click to collapse
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk

samep said:
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you! It worked.

jmalmberg said:
Thank you! It worked.
Click to expand...
Click to collapse
Now, hopefully you have ROM picked out and on extSdCard ready to flash.
I'd backup stock ROM to extSdCard in TWRP just in case.
Follow the OP on your ROM install. Enjoy!
Sent from my SM-N920P using Tapatalk