yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
It doesn't matter which version you are using. TWRP makes a recovery for each bootloader. Each recovery for 4.3 and 4.4 are on version 2.7.0.0 you just have to go to the TWRP page and you will find all the info.

First off I recommend you ODIN the official update via ODIN which flashed fine with all versions of ODIN....1.85, 3.07 or 3.09 and then once the flash is completed then reboot the phone to make sure that the phone boots. Once it boots then all you have to do is ODIN flash the TWRP 2.7.0.0 tar file and you are good. Then all you have to do is flash a rooted ROM and you have root back. If you want to stay stock all you have to do is ODIN flash chainfire auto root for the n9005 and it will inject root with no problems.

Staying on the 4.3 bootloader cause issues because custom ROMs dont typically have a kernel during the flash so I you need to find a 4.4 kernel that doesn't make your phone go crazy. Biggest issues were wifi calling and what not
[T-Mobile Samsung Galaxy Note 3] BenGentle:
To clarify, you recommend Odining what official update?

By the time you posted, I already Odin flashed openrecovery-twrp-2.7.0.0-hltetmo-4.3.img.tar using Odin3 v1.85 and everything appears normal. Your mention of losing root threw me off balance a little but I still have my root (CF-Auto-Root)!

The 4.3 bootloader means Android 4.3, right? There's no way I'm going to the 4.4 bootloader (is that the same as Android 4.4.2?) because TWEAKED doesn't support it yet. I've made one backup via your TWRP 2.7.0.0 hltetmo 4.3 using my untouched bootloader and found TWRP couldn't access USB-something-something, but viewed the backups and it was listed so I feel like it worked. I'm putting TWEAKED back on plus TWEAKED's mini-update also at this time.

This is the order in which I'm fixing her up:

1) Firmware :good:

2) Root :good:

3) Recovery :good:

4) ROM

5) Theme

6) Launcher

I want to get ColonelX in there somewhere but don't know enough yet. I see in TWEAKED that no kernel is flashed by default so can I expect TWRP issues?
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
First - Give yourself a Big pat on the back!!

There IS NO BENEFIT to flashing the kitkat bootloader! None!

Flash whatever Rom you want.. Like I said before - on my Note 2, which came with whatever os (don't remember) it's running kitkat Roms.

My skyrocket, which came with gingerbread - was running jellybean & is now running kitkat.. I never flashed a bootloader on either of them. My Nexus 7 same thing - it's running kitkat - Never updated the bootloader.

My Note 3 came with jellybean - Now it's running kitkat - Never updated the bootloader... Get my point?

?
[T-Mobile Samsung Galaxy Note 3] bigbiff:
I only updated to see if it would fix my LTE crash. It didn't :(
[T-Mobile Samsung Galaxy Note 3] iZack187:
Unfortunately... I am not technical enough to fully comprehend that sentence on my own...

In my head, flashing a kitkat bootloader equals being "future-proof", would I be wrong?

Also, if you claim there are no benefits, would you say there is also NO HARM in flashing? None? lol

Again, in my very limited programming knowledge, I understand that Google is aiming to go the way of the ART instead of DALVIK as a runtime for Android 5.0 and that would somehow completely change the way apps are developed, would that also affect the bootloader in the future or does that have nothing to do with it?

Thank you
[T-Mobile Samsung Galaxy Note 3] antiochasylum:
I wouldn't say COMPLETLY change how they are developed, just small changes.

ART is a runtime. Simply that. It has nothing to do with your bootloader.

The only benefit in updating a bootloader is sometime Samsung does shady crap and ties something to it. On the Note 2 it was wifi. It wouldn't work unless you had an updated boot loader.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
ART runs just fine on the 4.3 bootloader.. Just fine ;)

---------- Post added at 05:16 PM ---------- Previous post was at 05:07 PM ----------

Yes - Shady stuff like locked bootloaders - And other nefarious schemes concocted by manufacturers and carriers alike...

And - No - I'm not burning up in my aluminum foil suit and hat...

Devs figure out ways to get the job done - And then the manufacturers and or carriers release a "patch" or something to close down the accessibility of the devices...

If you're happy with stock TW.. Then there's no issues - but at some point, xda would become irrelevant to you.

The first lemming over the cliff didn't gain any advantage - lol ?

---------- Post added at 05:51 PM ---------- Previous post was at 05:16 PM ----------

One more point - unless you have the SM-N900W8 - If you update the bootloader - There's no going back... There - I'm finished with my caffinated rant about bootloaders ?
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
First of all, is there not a benefit of upgrading? Why don't you provide more information instead of going against the grain.

Anyway there are no special features of the new bootloader. The whole point of what I said earlier is because there are so many questions, bootloops, softbricks and a lot of repeated answers to the same questions.

If you do an official update from your phone which for example kitkat ROM thats on Sammobile or in your respective forums for your device under your phones Android Development section, this will ensure your phone is properly partitioned to run KitKat and with that comes the correct kernel for your device. If your phone doesn't have the official kitkat update then this does not apply.....Staying on the 4.3 bootloader gives you zero advantage except you can run 4.3 roms and if that's what you want to do then don't worry about kitkat makes no sense.

There are extra steps for someone who wants to run kitkat on the 4.3 bootloader such as finding a kernel for your phone to be able to boot because the custom ROMS do not flash a kernel so you have a 4.3 kernel on a 4.4 Rom unless dev decided to bake the kernel in.

Stop trying to act tough like you are a rebel because you stayed on the 4.3 bootloader. Put out useful information instead of trying to have a pissing contest. If you intended on running kitkat there is definitely an advantage to upgrading the bootloader because that means you used the official kitkat release for your phone which solved a lot of bootloops and wifi calling issues that people were having as opposed to those who were just flashing the 4.4 Roms on their 4.3 bootloaders and not ODIN flashing the official firmware that updated the bootloader.

Anyway hope that answers some questions
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
http://xdaforums.com/wiki/Bootloader

http://www.addictivetips.com/mobile...-bootloader-on-android-phones-complete-guide/

http://m.androidcentral.com/what-is-android-bootloader

The Bootloader has a single purpose - It's designed to Boot a specific device - with specific hardware - It either works, or it doesn't - There's no software reason to "update" it - There's no hardware reason to "update" it, unless the device is not functioning properly.
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
You again are missing the point, I said ODIN flashing the official update means you updated the bootloader which is the advantage and I do remember saying one bootloader doesn't have any advantage over the other one, however the official ROM updates partitions and ensures phone was partioned properly and if what you were saying was the case then you should be able to flash and have zero issues or bootloops. Hence why I said extra steps like getting a kernel to boot or did you miss that?

Edit..I forgot to mention unless you are familiar with bootloaders which most people aren't and you forget to flash a kernel your phone won't boot and it's easy to overlook....there's ZERO benefit to staying on an older bootloader unless you still want to run a 4.3 ROM if you don't like 4.4
[T-Mobile Samsung Galaxy Note 3] XxLostSoulxX:
2.7 won't flash super user properly so yeah I'd rather have cwm.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
What do you mean it doesn't flash properly? I have flashed it a dozen times with no issues.
[T-Mobile Samsung Galaxy Note 3] XxLostSoulxX:
I flashed super su 1.93 10 times. I would reboot after open faux clock or no root access. Opened su said no binary installed and it wouldn't install it from the app said it couldn't.

I flashed Philz recovery, flashed su and bam it worked.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Post /tmp/recovery.log so I can see if there are any errors while flashing. Like I said I have had to flash it quite a few times because Samsung update kept nuking the su binary. It always came back after flashing in TWRP.

I finally froze fota to stop it from happening.
[T-Mobile Samsung Galaxy Note 3] jaleroca:
I updated to 2.7 so now I can't reboot into recovery. I'm assuming that in order to install 2.7 I would have to do this via odin? I am still currently using 4.3. I haven't updated to a 4.4 rom yet. If not, what is the best way to update to 2.7? I did once by just flashing the zip and it froze on me at the recovery screen. So now I can't reboot into recovery.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Did you flash the correct zip file for your bootloader?

You should still be able to get it into Download Mode - Use Odin to flash the correct img tar file - or the last one that worked for you.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Make sure you flash the 4.3 bootloader version of TWRP.
[T-Mobile Samsung Galaxy Note 3] LillieBennett:
Clearly, lots of confusion over which bootloader version to flash.

SM-N900V DE
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Confusion - or Reading...
[T-Mobile Samsung Galaxy Note 3] bigbiff:
I reuploaded hltecan for 4.3 and 4.4 based on the hlte kernel and dtb. Can you test them out for me?
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Edit: I tested 2.7.0.0 hltecan 4.3 I Wiped System & Caches - Flashed Rom & Gapps.. Didn't have the chance to test backup or restore as of yet.
[T-Mobile Samsung Galaxy Note 3] jaleroca:
I flashed the wrong one.

---------- Post added at 06:16 PM ---------- Previous post was at 05:26 PM ----------

Is there a way to install the right one after the wrong one was flashed? I know I'm gonna face the same problem because it wont go into recovery
[T-Mobile Samsung Galaxy Note 3] bigbiff:
It will overwrite the recovery partition each time you install any recovery including stock because the image is a bit for bit copy of the entire recovery partition.
[T-Mobile Samsung Galaxy Note 3] jaleroca:
I just tried to flash the correct one and because I flashed 4.4 bootloader I cant enter into recovery. Thats my problem. Is there any way to flash the correct one
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Pull the battery - Boot into Download Mode and flash the correct img tar file with Odin.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Assuming the following

1. You have the T-Mobile Note3 (according to your signature this is true)

2. You flashed the 4.4 bootloader properly

3. Therefore you need to flash in Odin the following image: http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.0-hltetmo-4.4.img.tar
[T-Mobile Samsung Galaxy Note 3] jaleroca:
Success.
[T-Mobile Samsung Galaxy Note 3] iZack187:
Just flashed your new 2.7.0.0 v4.4 on top of the brand new 4.4 Canadian roms and so far it's looking good! (Both previous versions were getting me stuck at recovery boot)

Successfully flashed some custom roms, tried a basic backup/restore also successful.
[T-Mobile Samsung Galaxy Note 3] iakeco:
Boot into download, then you would be able to run the rom you have installed. Then go to rom toolbox and you can install the correct version of TWRP.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Good to hear ;)
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
bigbiff - FYI - While I was able to use hlte 4.3 2.7.0.0 to backup to my 64gb (exfat) external sd - I tried to backup using hltecan 2.700 4.3 to the external sd card & it failed as soon as I swipe.. I did go to Advanced to save the recovery.log - but when I rebooted, the recovery.log was 0 bytes.

There must be a subtle difference between the two...

hltecan 2.700 4.3 was successful in backing up to the phone sd.

Thanks
[T-Mobile Samsung Galaxy Note 3] bigbiff:
OK, I might need to update the device configs for selinux permissive.
[T-Mobile Samsung Galaxy Note 3] mscion:
bottom line...

Hi. I'm on Tweaked rom. I've spent quite a bit of time customizing it to my liking and it will probably remain my daily drive until I get a Note 4 or what ever.. However, that does not mean that I don't want to check out kitkat to see what's up with it. I would like to, it possible, seamlessly go, back and forth from Tweaked to a stock deodexded kitkat rom that I tinker with. So what is the bottom line? Can I use the updated TWRP, in OP, flash stock deodexed kitkat and then flash, say wootens kernal (or what ever is suggested best for this). Then, once I've, say, done an initial set up of kitkat do a full backup so finally I can use TWRP to go back and forth between Tweaked and Kitkat like I currently do to go between my backups of Tweaked and stock deodexed 4.3 rom? Am I missing some crucial steps here? Anyways, I've read a bit on these threads and find myself confused about whether this is doable. Thanks for your help!
[T-Mobile Samsung Galaxy Note 3] bigbiff:
If you are still on the 4.3 bootloader, as long as you use a kitkat kernel that works on it, you can use the 4.3 bootloader version of TWRP 2.7 to backup and restore.
[T-Mobile Samsung Galaxy Note 3] mscion:
Great. That is what I thought but manged to confuse myself. When I do a full back up (everything x'd on the back up menu .i.e., Boot, Recovery, System, and so forth) does the kernel get backed-up too? That is where does the kernel reside? If it is not backed up, then presumably I would need to flash the appropriate kernal (if needed) after I restore the rom as I should also not mix up the kernels. Anyways. I'm trying to look before I leap! Thanks again!

EDIT: Unfortunately I confused myself some more about where the kernel is. And here I thought google is my friend! Or, more likely, I'm my worst enemy! lol... Anyways, some say it is in boot and I also read about some folks saying something about it being split around. This I don't get! But, hopefully, if I back up everything I should be ok. Correct?
[T-Mobile Samsung Galaxy Note 3] bigbiff:
If you backup boot, that is the partition that contains your kernel and ramdisk for your running Android rom.
[T-Mobile Samsung Galaxy Note 3] Shane818:
Getting errors after flashing and cant fix permission

https://www.dropbox.com/s/o2rq7n1duey9yr9/recovery.log
[T-Mobile Samsung Galaxy Note 3] bigbiff:
You might want to try wiping data. I see some I/O errors when trying to open folders in your log.
[T-Mobile Samsung Galaxy Note 3] Shane818:
Thanks just did full wipe everything looks good
[T-Mobile Samsung Galaxy Note 3] siraltus:
The Fix Permissions option in Advanced screws up contexts on KitKat. I used it and then a bunch of my apps (like WhatsApp) could not write to the internal storage anymore; I had to do restorecon -Rv /data to fix it. Just an FYI.

EDIT: Using hltetmo 2.7.0.0 for the 4.4 bootloader on an SM-900T with stock rooted NB4 ROM.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Which version of TWRP are you using, 2.7.0.0 - 2.7.0.1?
[T-Mobile Samsung Galaxy Note 3] siraltus:
Using hltetmo 2.7.0.0 for the 4.4 bootloader on an SM-900T with stock rooted NB4 ROM.

When did 2.7.0.1 come out? I don't see it here: http://goo.im/devs/OpenRecovery/hltetmo
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Can you do a toolbox ls -lRZ /data > /sdcard/databefore.txt

then fix permissions

then toolbox ls -lRZ /data > /sdcard/dataafter.txt and post both logs.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
http://techerrata.com/browse/twrp2/t0ltetmo
[T-Mobile Samsung Galaxy Note 3] siraltus:
I flashed that but the version still says 2.7.0.0.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Attached.
[T-Mobile Samsung Galaxy Note 3] sshafranko:
Guys which is the best recovery version for me to use? Im currently on TMO JB 4.3. I was using one of the 2.6 versions I beleive the 2638 and I had issues restoring backups and flashing new roms. I would bootloop and afyer flashing the bootloop fix zip it would be ok. I did not restore efs. Looks like a few versions came out since then and I would like to try again but not sure which version to use. Thanks

Sent from my SM-N900T
[T-Mobile Samsung Galaxy Note 3] bdorr1105:
Use the 2.7.0.0 for 4.3 if you plan on staying with Jelly Bean and if you go to kitkat ODIN flash the official update so it updates the bootloader, then ODIN flash the 4.4 recovery and either way you go you will be fine
[T-Mobile Samsung Galaxy Note 3] iakeco:
Is this for 4.3 or 4.4

P.S. I was talking about 2.7.0.1
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
There's one for each - If you're on the 4.3 bootloader - Download the one for that - If you're on the 4.4 bootloader download the version for it.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
t0ltemo is for note2 on tmobile...
[T-Mobile Samsung Galaxy Note 3] bigbiff:
I did a diff -y on both. Only differences I saw were permission changes, those come from packages.xml from the app itself. I didn't see any contexts changed however.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Oops - Pasted the wrong link... My bad - Here's the correct one for hltetmo - 4.4 & 4.3

http://techerrata.com/browse/twrp2/hltetmo
[T-Mobile Samsung Galaxy Note 3] iakeco:
Now.. That makes sense
[T-Mobile Samsung Galaxy Note 3] siraltus:
Thanks for checking this for me. I'm really not sure what actually happened.

I made a backup, then did fix permissions, then booted up and WhatsApp couldn't download pictures anymore, turns out it couldn't write to the internal storage. And then Tresorit started crashing. So I did restorecon on /data and that fixed it. So I figured somehow contexts or whatever restorecon fixes got messed up.

If it happens again, I'll report again.

---------- Post added at 11:22 PM ---------- Previous post was at 11:14 PM ----------

Haha, no wonder flashing it failed for me - wrong device. And I didn't notice the wrong device name... I need sleep.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Yeah - I've got both devices - And accidentally posted the wrong link for the N3...
[T-Mobile Samsung Galaxy Note 3] @rbiter:
if i am using the international stock rom should i still use tmobile zip or an international zip? the reason i am asking is i've had minor problems with rebooting. i flashed an efs fix to stop that. thing is though if i reboot for whatever reason, it seems to lose the efs fix and i'll get random reboots back. the efs fix also allows me to get into the radio menu where as before i couldn't. this is very important question for me because i need stability whereas the reboots were drving me up the wall before i figured out the efs fix. not sure how to proceed. i am on 4.3 bootloader and will be downloading a 4.3 version because i don't plan on upgrading to kitkat anytime soon because google is borking up android bigtime with kitkat. and i want my efs to not corrupt. i am in dire need of making backups occasionally as my last one is from November. should i stick with tmobile recovery or is international recovery good? i need to get into radio menu occasionally to force wcdma only or lte only occasionally.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
The only difference is build.prop and the kernel between international and T-Mobile. Twrp doesn't mess with efs unless you try to restore it. Not really sure what could be messing with your efs partition.
[T-Mobile Samsung Galaxy Note 3] @rbiter:
don't know. i had issues early on. thought it was uv related but it's not because then i ran stock voltages and still got the occasional random reboot. the only one that wasn't random was when it fully charged it would reboot. that started about 3 months ago. so i should be fine with tmobile recovery? might flash international rom new but leave data partition intact.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
I am on Tmobile Note3 right now with ATT service using international rom and tmobile note3 twrp (hltetmo).
[T-Mobile Samsung Galaxy Note 3] VVerevvolf:
I foolishly flashed 27.0.0 4.4 via TWRP (zip file) when still on Android 4.3. No surprises my recovery does not work. I tried to flash back to 2.6.3.8 via Odin (tar file in PDA) but nothing happens. Phone is working fine - any thoughts on how to get a working TWRP recovery back?

BTW I do intend to upgrade to 4.4 at some point would it be easier to just flash a stock 4.4 re-root and flash TWRP 27.0.0 4.4?
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Try flashing 2.7.0.0 4.3 TWRP for now.
[T-Mobile Samsung Galaxy Note 3] VVerevvolf:
Thx for the quick response - I'll try tonight when I get access to my PC and report back.
[T-Mobile Samsung Galaxy Note 3] @rbiter:
I flashed 2.7 4.3 the other night. Accidentally factory reset when trying to get backups. Luckily I made a backup before and after flash. Flashed the backup after 2.7 recovery flash. Int'l rom is fine, efs appears to be fine, rom appears to be stable not having a reboot whatsoever yet and I am still able to get into my dialer menu. Thanks guys.

sent from my sm-9005.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Okay, I figured it all out. I had corruption of the /data partition because I was using the Hot Reboot feature in the 4-way reboot menu in Wanam Xposed. Apparently it's badly implemented (pkill vs sigterm) so the phone doesn't close open files or unmount filesystems before rebooting, causing corruption. I stopped using the Hot Reboot feature (actually I disabled the 4-way reboot menu altogether) and have been corruption-free since then.

Nothing to do with TWRP!
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Yeah, I never liked just killing dalvik vm in the middle of billions of writes it's probably doing with hot reboot.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Yeah... never doing that again... why do people even implement such a stupid feature is beyond me.... it's like screwing up your phone on purpose.
[T-Mobile Samsung Galaxy Note 3] VVerevvolf:
That worked! I now have a working recovery, Thx again!
[T-Mobile Samsung Galaxy Note 3] waywardfrantz:
I've restored to stock and then tried to flash this and I get nothing. Done every combination of stock/chainfire/twrp that I can come up with and get a little android with a red square and 6 options. I went into stock and tried the TWRP and ROM control apps which both said that they installed twrp, and even tried CWM and neither works. WTF is going on. Also did root checker and I do have root.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Have you tried odin? Make sure you boot TWRP with vol up/home/power on before android after flashing TWRP in odin. Uncheck auto reboot in Odin.
[T-Mobile Samsung Galaxy Note 3] waywardfrantz:
I've used odin 1.85 and odin 3.09, ive tried flashing CF-autoroot, open recovery TWRP, stock rom, and none of it does a damn thing. ROM control says TWRP and CWM are installed but neither will boot. IT goes to a short little weird looking recovery screen that does nothing and cant install even though it says it can.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Try a Factory Reset - use Odin again to flash TWRP - Flash a custom Rom (they all have root built in)... Just a suggestion

Also - You're flashing the correct version of TWRP for your bootloader?
[T-Mobile Samsung Galaxy Note 3] waywardfrantz:
Done that a dozen times, tried it again and still doesn't work

When I go to recovery I either get an android with the red triangle on his chest or a bootloop.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Have you tried Odin back to stock?

Edit - ok I see that you've been able to Odin to stock...

When you're trying to use Odin to flash TWRP - You are in Download mode (sorry have to ask)?

Once you've Odin to stock - Skip the CF Auto Root - Just use Odin to flash TWRP for your device and bootloader - Download a Custom Rom - Flash it (and Gapps if AOSP) And see if that works for you.
[T-Mobile Samsung Galaxy Note 3] waywardfrantz:
it doesn't.

but I think you struck on something with the bootloader, I suspect the problem is there.