yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] HughesNet:
That is integrating. I thought nothing of it but before putting the SD in my phone I formatted it exfat because it was stock and I knew Samsung had released their 64gb exfat code so I figured needing fat32 was a thing of the past. I notice right away though that twrp 2.6.3.0 wouldn't mount an exfat card so formatted it back to fat32 right away.

Long story short I started out with a freshly formatted SD that is fat32 and I wonder if that may be part of why I have had zero trouble. Has anyone having the restore bootloop tried it with no SD card yet?
[T-Mobile Samsung Galaxy Note 3] Warrior1975:
I didn't finish reading it all, but skimmed the end. People are taking their so cards out rebooting, turning airplane mode on, reboot with so card, shut airplane mode off and it seems to be working. Or something ridiculous along those lines.

sgh-TWEAKED-889©

---------- Post added at 11:33 PM ---------- Previous post was at 11:31 PM ----------

Yes, I tried without sd, no sim, sim no sd, sd no sim, etc. Nothing.

sgh-TWEAKED-889©
[T-Mobile Samsung Galaxy Note 3] ArborRes:
Thank you for this wonderful recovery!

Installed the 2.6.3.1 version without an issue and will upgrade when the next version supports exFAT again.

A T-Mobile GN3 running the AT&T LTE network, rooted, TWRP installed and nandroid backed up fully.

With the Gear working seamlessly with this fantastic smartphone, my digital life is wonderful once again. :)
[T-Mobile Samsung Galaxy Note 3] Warrior1975:
Just watch your recovery. A few have had no issues like you posted but restored a nandroid and had endless bootloops. Just an FYI if you haven't read the issues some are having.

sgh-TWEAKED-889©
[T-Mobile Samsung Galaxy Note 3] zmore:
With desktop linux, SELinux in "enforcing" mode also causes headaches when you stray too far off the reservation doing stuff like installing 3rd-party packages from unknown repositories, installing from source, moving apache htdocs basedirs, or mucking about as root without understanding security contexts (and Linux noobs just disable it at that point, rather figuring out how to fix it (restorecon, new policy module exceptions, etc).

The SELinux situation will probably be similar with Android, which is a shame, because its access control is very fine-grained and great for improving real security. I imagine a lot of people will be happier using kernels w/o selinux (or just in permissive mode), even at the expense of security

I will say, though, that selinux problems have never put my desktop computer into a bootloop before (well, except for that one time... when I preserved /boot instead of reformatting and it was incorrectly labeled after a Fedora reinstall :))
[T-Mobile Samsung Galaxy Note 3] AliKingKong:
The Problem is IndexService!!

IndexService kept popping up on my phone with error messages....It would freeze my phone randomly for no reason. I noticed that it stopped when i took out my sd card. After rooting, i deleted IndexService totally, and I was able to use my phone again without challenges. Get rid of IndexService and that may stop the bootloops.

---------- Post added at 01:50 AM ---------- Previous post was at 01:37 AM ----------

The reason why you guys are in bootloop is because of IndexService; it explains why you couldn't restore your phone even when booting stock with Odin. What you need is a stock tar file with IndexService removed. I have a strong reason to suspect that IndexService is the culprit behind the bootloops and phone freezing.

Can anyone compile a stock tar with IndexService removed?
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
I don't know if it really is related to IndexService - or if the problem is with some people installing a SD Card that is filled with data?

http://forums.androidcentral.com/sa...-stopped-screen-freezing-every-2-minutes.html

When I first setup my phone - I didn't have the SD Card installed & haven't had any freezing or bootloops - When I did install the 32 Gig SD Card it was formatted to Fat32 - I've downloaded roughly 80 apps from the playstore without issues.

Stock - Non Rooted - hltecan
[T-Mobile Samsung Galaxy Note 3] AliKingKong:
Im quite certain that IndexService is the culprit. My phone was doing the same thing people posted in most of these threads until i deleted Indexservice. There is something horribly wrong with it...the thread you mentioned described overheating, which i also experienced, and the bootloops also. The error messages and the freezing all seem to be associated with it.

We need a stock tar with Indexservice removed; then we could have people who are in bootloop flash it in Odin to see if that ends the bootloop.
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
I don't think that you've found a solution to the problem - at best I think that perhaps you've found a temporary patch or workaround.

In the link that I posted - the people who were having trouble - had installed SD Cards with data already on them - You'll note that one person posted that after they let IndexService run through - that problem was no longer an issue.

Another example would be - if you disabled Media Scan on startup to "fix" a problem there - It's not actually a fix at all - just a temporary solution.

There's something about how individuals are setting up their devices & the unique ways that they are bringing together a combination of processes that are most likely the cause of the issues - You have to note that not everyone is being affected - but IndexService is in every device (with the exception of yours) - IMHO.
[T-Mobile Samsung Galaxy Note 3] turilo:
Where can I locate the indexing service to remove? Curious on trying this thanks
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Here's yet another link - This time from AndroidCentral - Read it.

It definitely seems that there's two common issues - 64 Gig cards & SD Cards with existing data.

The more I read - the less I believe that IndexService is the culprit.

http://forums.androidcentral.com/sa...-stopped-screen-freezing-every-2-minutes.html
[T-Mobile Samsung Galaxy Note 3] turilo:
This might be true but I formatted my 64GB sd card in the Note 3 and still get the bootloop :/ very frustrating. Maybe I'll try a 32gb when I get home

EDIT: I've actually tried it with no sd card in the phone with same bootloop issue
[T-Mobile Samsung Galaxy Note 3] liveforphysics:
I first tried the most recent 2.6.3.2. Flashing anything only results in recovery bootloops.

Switched to 2.6.3.0. Same issue.

Switched to 2.6.3.1. This allows me to successfully backup and restore. It can even restore a backup to escape out of a bootloop. However, flashing DarthStalker results only in bootloops.

This has been tried with SD card, with no SD card, with SIM, with no SIM, pre-unlocked and post SIM unlocked. All result in bootloops when I flash a ROM, but TWO 2.6.3.1 is able to successfully backup/restore.
[T-Mobile Samsung Galaxy Note 3] AliKingKong:
It's a system app running in the background. I used "Root App Delete" to delete the app after I rooted. It made a world of difference for me.

---------- Post added at 11:48 AM ---------- Previous post was at 11:41 AM ----------

How did you install recovery at first? With the Playstore App, or did you use Odin to flash a tar?
[T-Mobile Samsung Galaxy Note 3] cwalker0906:
Did you manually format system in recovery before flashing. I'm on 2.6.3.0 and flashed with no problems
[T-Mobile Samsung Galaxy Note 3] turilo:
i used odin to install the recovery first time
[T-Mobile Samsung Galaxy Note 3] Warrior1975:
I used goo

sgh-TWEAKED-889©
[T-Mobile Samsung Galaxy Note 3] AliKingKong:
Indexservice is only triggered with the installation of an SD card. Before I put in my card, I had no problems whatsoever.

It would account for the numerous problems people are having with stock and recovery software.
[T-Mobile Samsung Galaxy Note 3] Warrior1975:
I definitely had an sd card when I installed twrp, backed up, and restored. I did try restoring without it, to no avail, but the damage could have been done already.

sgh-TWEAKED-889©
[T-Mobile Samsung Galaxy Note 3] chrisa887:
This is what I did and hadn't had any problems m.youtube.com/watch?v=ymbVHR3F_O8&desktop_uri=%2Fwatch%3Fv%3DymbVHR3F_O8 but I haven't restored yet, couple people have and had no problems
[T-Mobile Samsung Galaxy Note 3] AliKingKong:
Did you have an SD card in your phone when you installed Recovery?
[T-Mobile Samsung Galaxy Note 3] chrisa887:
Yeah

I been flashing stuff but haven't made a backup or restored a backup so I not sure if mine will mess up
[T-Mobile Samsung Galaxy Note 3] siraltus:
Heads up: if you found 2.6.3.3 on the goo.im server, don't flash it - it doesn't boot.
[T-Mobile Samsung Galaxy Note 3] chrisa887:
has anyone tried this?

http://howtorootmobile.com/stuck-in-android-boot-loop-tips-to-fix-recover-from-boot-loop/
[T-Mobile Samsung Galaxy Note 3] liveforphysics:
After trying to flash the original Darthstalker V1 many dozens of times in various ways and only yielding bootloops, I downloaded the new Darthstalker V2, and POOF!! First try it works! Doing nothing differently than I had done before with V1.

Woot!!! Finally!!! No Carrier ID, no Knox, and a happy smiling users face. :)
[T-Mobile Samsung Galaxy Note 3] mocsab:
Sure wish I had read this before I tried - LOL - I found out the hard way - went back to 2.6.3.2

it's always something! :)
[T-Mobile Samsung Galaxy Note 3] lm that guy:
So which version actually works with flashing roms?
[T-Mobile Samsung Galaxy Note 3] chrisa887:
2.6.3.1
[T-Mobile Samsung Galaxy Note 3] akapaul26:
What do you mean no Knox. Don't rooting trigger Knox?

Sent from my SM-N900T using Xparent BlueTapatalk 2
[T-Mobile Samsung Galaxy Note 3] Warrior1975:
Yes, but there is a stock deodexed rom that is Knox free, along with Darth

sgh-TWEAKED-889©
[T-Mobile Samsung Galaxy Note 3] zoth:
I only trust the ones via Goo Manager App. :good:
[T-Mobile Samsung Galaxy Note 3] akapaul26:
I guess I don't understand what exactly that means. ... Anyway this is the twrp thread so I'll direct my question somewhere else. ..

Sent from my SM-N900T using Xparent BlueTapatalk 2
[T-Mobile Samsung Galaxy Note 3] zoth:
Agree!
[T-Mobile Samsung Galaxy Note 3] Warrior1975:
Sorry if I wasn't clear. Yes, rooting triggers knox. There is a stock deodexed ROM, along with Darth stalker ROM, but are "knox free", but I dont believe it's 100% knox free. From my limited understanding, there are a couple of knox pieces still in the ROM, but the security check for installing unknown or possibly malicious apps are gone. You will still have the knox flag though.

That's my understanding.

sgh-TWEAKED-889©
[T-Mobile Samsung Galaxy Note 3] siraltus:
Many people don't fully understand what KNOX is yet so they can't properly explain it. There are two parts to KNOX:

The KNOX secure boot mechanism is in the bootloader and a hardware chip in the phone. This checks whether bootloader, recovery, or system binaries are genuine (signed with the phone's unique X.509 certificate and unmodified) on every boot. This is the part of KNOX that you cannot remove. You also shouldn't care about it except for the KNOX WARRANTY VOID bootloader flag that gets set once you boot (not flash, but actually boot) a modified image in one of the monitored partitions (boot, recovery, system) at least once. Samsung may or may not deny you warranty service if they see that flag tripped. We don't know yet.

The KNOX software layer in the Android operating system that blocks you from running apps that need root - that's the part that has been removed from this ROM so it no longer interferes and you can run whatever apps you want.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Yes, and not to mention from what I understand they are using SELinux to enforce permission checking, trusted applications that run, and libraries that processes can use from the system partition. I really want to start reading all the Knox documentation shortly.
[T-Mobile Samsung Galaxy Note 3] siraltus:
Yes, you are right. I didn't want to write 50 pages explaining the KNOX SELinux enforcement mechanism. :) They do use SELinux in Enforcing mode to stop apps they don't like from running and such.

But you can grab the kernel source files from Samsung and rebuild the kernel with SELinux set to permissive - some guy in the general Note 3 forum just did that.

Read the KNOX white paper: http://www.samsung.com/global/busin.../Samsung_KNOX_whitepaper_April2013_v1.1-0.pdf

I found it very useful in understanding what exactly is happening on my phone (and why the KNOX WARRANTY VOID flag gets set, for example).
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
bigbiff - Could you explain what the difference is between the hltecan.tar and the hltecan.image.tar is?
[T-Mobile Samsung Galaxy Note 3] siraltus:
Typo in the filename. They're the same thing. The tarball (.tar archive) actually contains the .img file.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
I believe Dees_Troy built one, and he used a different naming convention. I use .img.tar for my odin files.
[T-Mobile Samsung Galaxy Note 3] janjannsen99:
Canadian
[T-Mobile Samsung Galaxy Note 3] janjannsen99:
Canadian version note 3 possibly...

Tolte

Toltecan
[T-Mobile Samsung Galaxy Note 3] bigbiff:
We have a separate folder for Canada under hltecan.
[T-Mobile Samsung Galaxy Note 3] janjannsen99:
That's whati told them
[T-Mobile Samsung Galaxy Note 3] shaggyskunk:
Kinda knew that it was Canadian - when I was posting about hltecan ;)
[T-Mobile Samsung Galaxy Note 3] OGWisdom:
I don't believe the sd card being installed has anything to do with the index service. While still in the store activating my note 3, I had the rep install my 64gb sd while he was putting in the new sim. I have NOT removed the card since then and have successfully rooted and flashed a custom rom. Now, I also know that it is a known issue with restoring at the current moment. SO, I knew when I flashed the custom rom, that I would be on till the issue was squashed. Its all about making smart choices. People are sitting here rooting and flashing and have not much knowledge about what they are doing and that is why all the messed up devices. OK, maybe the first couple of people it was a surprise to, but we the community have known about this issue since the first recovery arised. So, why would you flash something you knew you weren't going to keep and then try to restore a backup?
[T-Mobile Samsung Galaxy Note 3] jdidtht:
Ogwisdom what's up bro.. I couldn't agree more. They have one rom and they don't have all the tools yet to be 100% successful every time but they insist on risking it.. good to see you here
[T-Mobile Samsung Galaxy Note 3] shin lucifer:
+1.

However there are few who had boot loop problem after they rooted the device. It ran fine few days and Boot loop started, after they tried to restore things using Titanium Backup. I am leaning more and more towards, Samsung did some thing crappy hardware/software wise. So that any thing that get some mismatch, it goes haywire. After my last N3 went to hell, i didn't even bother rooting my new N3. Not until i am 100% sure that rooting will no way put my device in boot loop.

Read every thing from Post 1 to Post X about Subject Y. Before you endeavour on Subject Y's journey.
[T-Mobile Samsung Galaxy Note 3] turilo:
I'm on my second note 3 haven't rooted it at all yet, and I get bootloops just with regular apps from playstore :/
[T-Mobile Samsung Galaxy Note 3] chrisa887:
What apps
[T-Mobile Samsung Galaxy Note 3] shin lucifer:
Dang... Not to derail this thread. However, please let us know what app caused it?
[T-Mobile Samsung Galaxy Note 3] jdidtht:
Idk if I believe that..
[T-Mobile Samsung Galaxy Note 3] chrisa887:
What app did you download to bootloop? Maybe I try to see if it makes mine
[T-Mobile Samsung Galaxy Note 3] turilo:
Read up http://xdaforums.com/showthread.php?t=2467005

[Q] Reboot cycle after restart help
[T-Mobile Samsung Galaxy Note 3] les_garten:
It's not unreasonable to ask what apps though is it?
[T-Mobile Samsung Galaxy Note 3] turilo:
No not at all, it was in response to the other psychics comment. As for apps some that I found seemed to be be paid version of helium and paid version of ninjasms. There were more but I can quite remembe. I'm going to redo my phone without an sd card again and see what happens
[T-Mobile Samsung Galaxy Note 3] JT man:
Bigbiff , Restore from bootloops:

1. Load Odin

2. Download FW for the phone from Sammobile

3. Extract files using 7zip

4. Open Odin

5. Deselect Reboot and Reset Time in Odin

6. Flash the following images one at a time: cache.img, boot.img, system.img

7. Pull the battery and replace

8. Hold home, volume up and then power to boot stock recovery

9. Update.zip will flash

10. Pull the battery and replace

11. Hold home, volume up and then power to boot stock recovery

12. Factory Reset

13. Boot into android and hopefully everything is fixed

Odin isn't seeing those files after extract, do I need to rename them?
[T-Mobile Samsung Galaxy Note 3] Warrior1975:
Odin only recognizes .tar and .pit files I believe.

sgh-TWEAKED-889©
[T-Mobile Samsung Galaxy Note 3] JT man:
So confused about the second post in the OP then, didn't say anything about renaming:what:
[T-Mobile Samsung Galaxy Note 3] slice2011:
Thanks biggbiff for your hard work on this worked flawlessly on my n3.
[T-Mobile Samsung Galaxy Note 3] mocsab:
I have seen some conflicting posts regarding which is the most stable version of TWRP right now - some say it is 2.6.3.0 some say 2.6.3.2

Is there some some concensus that one or the other is safe? (as long as you don't restore? Or has the restore issue been corrected?)

I lost two phones to unending bootloops - the second one I didn't even try to restore - just rooted and tried flashing a rom - (however, I had mistakenly installed 2.6.3.3 after downloading it from the TWRP web site - and when it wouldn't boot into recovery - I flashed the earlier, 2.6.3.2 version - then when I tried to install Darthstalker - I went into the unending bootloops and colud not correct, even tried using odin to return to stock. didn't work.

SO - I am obviously being very cautious - just trying to stay on top of things - and wondering what the concensus is right now for which recovery is 'stable" if any?

Also - anyone heard anything on CWM?
[T-Mobile Samsung Galaxy Note 3] Warrior1975:
I've read 2.6.3.1. Honestly, I'm waiting for more stable recoveries at this point. Just too risky.

sgh-TWEAKED-889©
[T-Mobile Samsung Galaxy Note 3] Tiffany84:
I think your going to get a split decision on which is more "stable". It seems to me like it's still such a mystery that nobody really knows what's causing it or how to prevent it so if someone mods there phone and didn't have your issues there probably going to say the recovery or the version they're using is the best. The developer of Darth Stalker recommended 2.6.3.1 and I decided to give that rom a try so I used that version of TWRP and haven't had a single issue so far. But that's not saying that it will work for you. Can't wait until it gets sorted out but if there's something I have faith in its the developers on this site figuring it out. Don't know nothing about CWM. I'm a TWRP girl:p
[T-Mobile Samsung Galaxy Note 3] Negan:
Ok guys for those of you that want to try biffs method and running into problems not being able to flash an .img via odin I have a method that will create a flashable ext4 format .tar.md5 file.

First install linux as the following needs to be done via terminal. But it may also be executed via a terminal in windows if you have it installed properly. Linux is highly recommended though. (Personally I dual boot mint cinnamon and windows)

Download firmware and put it in a new folder.

Remove the .md5 so you can extract it.

So as stated you need the cache.img, boot.img and the system.img.

So the following process is the same for all three:

I recommend extracting the 3 files to the root of the folder or wherever you want then right click and open terminal.

We need to tar it then md5 it and then mv it.

So starting with the cache for simplicity sake run this command:

ext4 $ tar -H ustar -c system.img.ext4 > s4img.tar

That will create a tar but we aren't done yet so don't try to use it.

Next we need to md5 it so run this:

ext4 $ md5sum -t s4img.tar >> s4img.tar

Now we've md5sum it, we need to mv it so run this:

ext4 $ mv s4img.tar s4img.tar.md5

This will take a few minutes so give it time. Realize the system.img is usually over 2g and the cache.img is about 300 mb so those 2 will take a bit.

If you excecute the commands properly you will have 3 odin flashable tar.md5 files. You can rename them afterwards to whatever you want but do not change the file extension. You can also rename it in the second command so instead of typing s4img.tar you could write cache.tar so you don't get confused about which file is which.

Take your time and this will work. As for the overall outcome of the bricklooping I hope it fixes it.

sent from my Note 3

respect,teach,coach,say thanks and have fun...

●●●The Jedi way●●● ? ? ?
[T-Mobile Samsung Galaxy Note 3] Naddict:
Thread cleaned. Keep the childishness out of development, be respectful of others always, and XDA will be a better place for it. Thank you for following the rules.
[T-Mobile Samsung Galaxy Note 3] bigbiff:
Sorry I forgot about the tar requirement for Odin. You guys can try the heimdall windows frontend. Otherwise use these steps. I guess I could do it and post them to my goo directory shortly. I never have luck with the md5 on tar, so I will leave it off.
[T-Mobile Samsung Galaxy Note 3] mocsab:
Thank you - your comments are helpful - I used 2.6.3.1 on my original note and come to think of it, didn't start having issues until I updated TWRP and at one point updated to 2.6.3.3 (which turned out to be a mistake that I think led to my phone's problem) But that's just it - I think -

It is so frustrating - I have never seen this many phones having this many issues - even brand new phones - I have always been amazed at the resilience of Samsung phones - at least the ones that I have used. Them seemed totally unbrickable almost. You could do just about anything to them and if it bricked up - you could always flash Odin to stock and start over - not so much like that anymore...least not with the NOTE3 anyway. I am really curious how many Note 3's got returned to TMOBILE or wherever because of this issue with Bootloops - I am sure it is in the hundreds - could it be in the thousands..?

anyway - thanks again "Tiffany the Twrp Girl" :)
[T-Mobile Samsung Galaxy Note 3] bigbiff:
It's all because of selinux and restoring/setting contexts properly. We are trying to fix it now. I am also uploading my tar images to goo. When I am done I will post back to see if someone can test. This always fixes bootloops for me.
[T-Mobile Samsung Galaxy Note 3] Negan:
Yeah no worries man. I know this method will work because although I'm not bootlooping I am trying desperately to help others in my how to root Canadian models thread which has turned into a general help thread now! But that's fine by me. As long as I can help contribute and help I could care less if it goes off topic in regards to helping.

Anyway before Sammobile released the Canadian firmware I extracted the boot.img and system.img via terminal emulator and created a .tar to toss in the kitchen. I also used those .img to make into a flashable .tar.md5 and they did work well the boot.img did. So it occurred to me to try in ext4 format and now since the stock firmware is out I'm redoing using it as it contains the stock recovery which is key to this hopefully working.

And guys to reiterate naddicts comments keep it clean guys. I understand a lot of you are stressed over the problem but keep it cool and no more flaming. No need for it at all. Ignore and report aka take the high road. Remember it's a development thread.

We will get this problem solved come hell or high water.

As I said I welcome any questions in regards to the bootloop in my thread as I'm not certain if biff wants this thread to turn into a q and a.

Cheers guys!

sent from my Note 3

respect,teach,coach,say thanks and have fun...

●●●The Jedi way●●● ? ? ?