yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] ripee:
The N9005 shouldn't have a locked bootloader. Try flashing twrp-3.3.1-0-hlte.tar in Odin (AP button), if it flashes, then no problem.

Be sure to pull the battery as soon as it vibrates when twrp is finished flashing, to avoid the stock rom's reflashing stock recovery as a safety measure immediately after Odin flashes twrp.

Then boot into twrp, wipe everything except internal storage, and flash the rom, gapps, and Magisk. Then wipe cache and dalvik and reboot system.
[Galaxy Note 3 Android Development] Wishh09:
Thank you sir. I will do it in my free time. Cause it's suddenly my note 3 signal is gone. I mean no signal even the wifi it's not working i don't why i already reformat my phone but nothing happened. Maybe if i flash custom rom it will back in normal.
[Galaxy Note 3 Android Development] ripee:
Also, flash the N9005 bootloader and modem file in my .BL_CP google drive folder, in Odin. It may help with the signal and stability.
[Galaxy Note 3 Android Development] Wishh09:
Where can i find that file sir? Im really confused about my note 3 its suddenly the signal not working also my wifi. What do you think the problembsl sir is it only software issue or hardware??
[Galaxy Note 3 Android Development] stefanct:
I am back and want to finish the job... I was able to build twrp-7.1 instead by just changing...

repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-7.1

I then tried to build the kernel from source (the minimal twrp repos have a pre-built one in the repo) and was hoping to reproduce the same behavior (as observed by the serial out) as with the pre-built kernel. Unfortunately, there is no documentation on which configuration or commit is used for any of the pre-built kernels. The only information I could find is the repository and branch of the kernel (bottom of the readme).

The most annoying issue was the missing kernel configuration (and non-helpful IRC channels). I ended up compiling the current top of the cm-14.1 branch (92e20731) with...

export PATH=/usr/lib/android-ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/:$PATH
make lineage_hlte_bcm2079x_defconfig
make -j5 zImage

I used that instead of the pre-compiled kernel to build the twrp recovery image and then something very unexpected happened: this recovery image is able to boot with the after-market display without any problems!?

So it would be even more interesting what configuration and commit was used to compile the kernel because apparently something happened between that and now... and we should actually be able to get newer custom roms to work with note3s that had their displays changed!
[Galaxy Note 3 Android Development] stefanct:
ping [MENTION=6005084]ripee[/MENTION], just in case it is not obvious enough that I need your answer... ;)

I've been trying slapping that debug kernel of mine onto the newest lineageos image of [MENTION=6561802]jprimero15[/MENTION] but was unsuccessful ("Failed to fstab for first stage mount" etc. and auto-reboot to download mode. I guess re-packing boot.img did not work correctly or there is some incompatiblity).
[Galaxy Note 3 Android Development] ripee:
Who are you telling to ping me? It seems the kernel's cm-14.1 had been updated since I used it to prebuild the twrp kernel. To save us both some time, if you have your zImage file available, please send it to me and I'll update the teamwin source repo.
[Galaxy Note 3 Android Development] stefanct:
That "ping" was not an imperative but I was simply stating that I actually am pinging you. :)

Yes, there indeed were updates... and nobody making custom images was using them apparently because none of the images work with replacement displays because of that! (It makes me wonder what else would actually work if the android community would be... let's call it "less fragmented").

I am not here so save time... kind of the opposite if we are honest: in that case I would not bother with old hardware but simply write it off. :)

However, I dug further... I remembered that the kernel tells me which version it is based on at startup anyway... so I was able to determine that you were using 450ae2e (which is only a few commits newer than the lineage-15.1 branch). I bisected the commit that makes the display work later in the cm-14.1 branch and it is bef6e7a724a. More specifically, it is the following change that looks completely unrelated to the display or SoC driver. It is in net/bluetooth/Makefile

-obj-$(CONFIG_BT_HIDP) += hidp/
+#obj-$(CONFIG_BT_HIDP) += hidp/

I.e. disabling compilation of bluetooth HIDP (human interface layer) fixes booting with a non-standard/after-market note 3 display (at least in twrp)! Amazing... and I still can't comprehend it but I have tested it quite extensively. This change might simply be masking a bug but in the end that does not matter too much.

I'll test tomorrow if I am able to get any of the custom roms to boot with this change/kernel. I'd like to avoid building a whole image myself though...

If so I'll try figuring out which/if more kernel updates would work and post a working kernel at the end. In the worst case (if you don't beat me to it) I'll build and post the current cm-14.1 one.

I want to look further though because I want to actually use that phone and after all, these branches are all kinda ancient... and probably include more security (and other) issues than I would like in any of my devices.
[Galaxy Note 3 Android Development] ripee:
Yes well, I haven't had cm-14.1 synced down to build from in years. Anyway, if I wrote off all my old phones, there would be no TWRP updates from me. If that small comment in /net/bluetooth/Makefile is all it takes, it won't be a problem to run a kernel build with just that small change. All the more reason to use a prebuilt kernel, so it stays working into the future.

By all means dig deeper into this, as I see you're on a good path.
[Galaxy Note 3 Android Development] stefanct:
Yes, the disablement of bt-hidp is enough. I have checked on top of the commit you used (450ae2e) and that worked as well. I have also tried the HEAD of LOS-16.0 (9fc6b38) and it works as well. Since it is the newest one I have prepared a patch for your repo that adds that one (or is there any reason to not use that but cm-14?). Unfortunately, twrp's gerrit does not send me a confirmation email so I can't push the change for review for now.

Unfortunately, I was not that lucky with the LOS-16.0 nightly build ROM although the kernel is the same as mentioned above. There are some warnings in the boot log but eventually system_server reboots intentionally at some point. I have not found out why and it is also off-topic here. I will probably open up a new thread regarding LOS development on hlte in the next days.

Attached is a twrp boot log with the LOS-16.0 kernel. As can be seen - at least for twrp - the NV missing warnings are benign.
[Galaxy Note 3 Android Development] stefanct:
Another small update, still in this thread, I changed back to my original display for testing (to see if LOS boots with that and to gather logs for comparison) and I noticed that brightness control works fine in twrp with it... that did not work with the replacement display. (The screen timeout does not work with either... no idea why).
[Galaxy Note 3 Android Development] Rukbat:
Nothing yet for the 900A? Or will one of the other ones work on that phone? (I'm running Safestrap now, but running real TWRP would be nicer. Either way, a zip or a tar would be fine.))
[Galaxy Note 3 Android Development] chris8189:
It's gone very quiet on here..
[Galaxy Note 3 Android Development] stefanct:
I am waiting for bigbiff to sort out some mail/isp problem so that i can push my changes (the updated kernel) to twrp's gerrit. Additionally, I am also working on getting the twrp app to not crash android if it is installed on android 9 (which you should simply not do - that's what I apparently did wrong all the time...). So there is some progress just not very visible...
[Galaxy Note 3 Android Development] Rukbat:
The solution to the Android 9 problem, unless the new version of TWRP has some major improvements, is to keep using 3.3.0.0. But not being able to back up at all is a major risk. (Are the changes a fix to the backup failure? [I hope.])

(I even tried flashing the November ROM [the last one I got a good update from], but booting crashed into the old recovery. [NP, though, I flash without wiping.])
[Galaxy Note 3 Android Development] stefanct:
3.3.1 works fine - you just should not install the twrp app (as mentioned in the LOS install guide). The reboot you are seeing is only because of the twrp app tripping zygote.

Or at least, installing with it... dunno about any backup/restore problems.
[Galaxy Note 3 Android Development] Rukbat:
Hmmm - wrong thread, I guess. Ignore me. (The Pixel 2 is only up to 3.3.0.0, and it doesn't back up with the January update, so I'm subscribed to that thread too.)
[Galaxy Note 3 Android Development] chris8189:
Yes, wrong thread ;) This thread is for the Samsung Galaxy Note 3 hlte

Chris
[Galaxy Note 3 Android Development] Rukbat:
Which I also run, which is why I'm subscribed to both threads, this and Pixel 2 TWRP.
[Galaxy Note 3 Android Development] rayman95:
thanks for the update...:good:
[Galaxy Note 3 Android Development] mhmdsami45:
i need download link version hlte
[Galaxy Note 3 Android Development] Eleo:
As it always has been, check twrp website
[Galaxy Note 3 Android Development] mhmdsami45:
right. i checked twrp website but i don't found last update 3.4.0
[Galaxy Note 3 Android Development] Robby68:
https://dl.twrp.me/hlte/

tried now, there are all versions ;)
[Galaxy Note 3 Android Development] Eleo:
He obviously didn't even check the website. Just waits to be spoonfed by somebody. As always.
[Galaxy Note 3 Android Development] smuffiy:
Sorry for crossposting. I have troubles with any TWRP > 3.x, maybe someone has an idea?

https://xdaforums.com/galaxy-note-3/help/samsung-note-3-n9005-twrp-3-x-bootloop-t4124585
[Galaxy Note 3 Android Development] Robby68:
Probably you are on kitkat firmware, like me one year ago.

Update the firmware by Odin and reinstall Twrp
[Galaxy Note 3 Android Development] smuffiy:
hmm why would the recovery system care for the os?

fwiw I updated the firmware to the latest official version (android 5.0) and then retried.

same result: with TWRP 2.8.7.0 I can flash and get into recovery mode. TWRP 3.x I can flash and they will bootloop

TWRP 2.8.7.0 I get the message

"Recovery booting...

recovery is not seandroid enforcing

Set warranty bit: recovery"

=> TWRP recovery mode

TWRP 3.x

"Recovery booting...

Set warranty bit: recovery"

=> bootloop
[Galaxy Note 3 Android Development] Eleo:
Did you read posts in previous pages in this thread? You might find some interesting news about your issue.
[Galaxy Note 3 Android Development] Robby68:
i try to explain better:

until 2019 i used the Temasek's rom CM11 on N9005XXUGNG1_N9005ITVGNG1_ITV firmware 20140728 (4.4.2) "No Brand" and TWRP-3.0.0-0-hlte

And then i tried to flash a lot of recent roms, Oreo and Pie based

result: too many problems like freeze and bootloop

So i flashed latest firmware N9005XXSGBRI2_N9005ITVGBRI1_ITV 20181011 (5.0) "No Brand" and, after first boot, i flashed the TWRP-3.3.1-0-hlte.img.tar using Odin

result: no freeze and no bootloop
[Galaxy Note 3 Android Development] Eleo:
So far we had some users who were unable to flash newer (3+) twrp as well, since march 2019 on this thread. I am not sure what they have in common, but [MENTION=10921615]smuffiy[/MENTION] should check them out
[Galaxy Note 3 Android Development] smuffiy:
I found a possible reason: LCD and Digitizer may have been replaced. I am not sure though. Could this be a reason why TWRP is not working properly?

---------- Post added at 05:03 PM ---------- Previous post was at 04:16 PM ----------

this worked for me finally! And it looks like linageOS can be installed too... I will update

---------- Post added at 05:43 PM ---------- Previous post was at 05:03 PM ----------

lineageOS and google apps could be installed without issues. I was stuck on the bootsequence quite a bit but now I am in the OS :)
[Galaxy Note 3 Android Development] smuffiy:
tell me your thoughts please, I am really curious
[Galaxy Note 3 Android Development] liamotoub:
Hello, I have the Galaxy Note 3 N9005 LTE with Snapdragon, updated to Android 9.0/Lineage OS 16.0.

I installed the latest TWRP 3.4.0-1 released on July 26, unfortunately the FDE decryption still doesn't work...

I have the following error messages: "failed to mount storage" "decrypt failed" "pattern failed, please try again".

Anyone got it working? The decryption with Android 7/Lineage OS 14 works well, with older TWRP.

note: someone with a fairphone managed to get an older TWRP decrypting the new android 9 data partition https://forum.fairphone.com/t/custom-twrp-3-2-3-to-decrypt-android-8-9-encryption/50192

unfortunately I am not able to understand the changes he made in order to try on my samsung phone too.
[Galaxy Note 3 Android Development] Jack22140:
Pls am new which open is best for flashing custom rom

I'm on Samsung Galaxy Note
[Galaxy Note 3 Android Development] JJEgan:
NO best depends upon the model and what you are flashing . Need to read roms instructions and thread .
[Galaxy Note 3 Android Development] zfk110:
Hi, I was trying to restore the TWRP backup but it wont restore the backup, Im on newer TWRP build and using on my g900v

I made the backup for data, system and boot

but when I restore it just stuck by Crdroid logo

it store the whole backup without any error codes

I used to use Oreo build and Nandroid it worked all the time

this is the twrp im using right now twrp-3.5.0_9-0-klte.img.tar on my S5 G900v running this rom

https://xdaforums.com/t/rom-klte-10-luisrom-android-10-based-on-crdroid-v6-x.4050529/
[Galaxy Note 3 Android Development] IcemanSR:
ops wrong topic
[Galaxy Note 3 Android Development] lacoongame:
Bug report​

WHAT STEPS WILL REPRODUCE THE PROBLEM?​

When performing "TWRP Backup"

WHAT IS THE EXPECTED RESULT?​

Backup completed in less than 10 minutes

WHAT HAPPENS INSTEAD?​

Regardless of backup operation

1-1. Unadjustable brightness

1-2. Unadjustable screen on time

1-3. Automatically turns on screen even if screen is turned off manually

1-4. Battery percentage does not decrease

1-5. The year is fixed in 1970

Regarding backup operation

2-1. It always takes about 30 minutes (compress mode)

2-2. the fever is severe.

ADDITIONAL INFORMATION​

All the hltekor models I've ever used have the same symptoms.

It has gotten worse since it was updated to version 3.x.
[Galaxy Note 3 Android Development] JJEgan:
Must admit never ever had any of those problems on hlte device.

hltekor at a guess thats the problem the korean version .

Worth looking at the twrp.me forum .
[Galaxy Note 3 Android Development] r0mushii:
seconded this. at first i thought it's just a common issue on the entire note 3 hlte variants due to the limitations mainly from the recovery partition(also the reason why aroma support got canned), but i guess it's an isolated issue only on hltekor.

last version of twrp 2.x doesn't have this issue excluding the 1970 and screen always wake. i'm still using 3.3.1-0 due to later versions having issues with restoring backups(device refuses to boot after restore, backup process gets stuck most of the time, etc). but at least it does it's job as a recovery tool, albeit very slowly and laggy, from abominably slow r/w speeds to the very laggy ui.
[Galaxy Note 3 Android Development] lacoongame:
I already reported a bug on twrp site.

Thank you for your answer!
[Galaxy Note 3 Android Development] lacoongame:
Thank you for the detailed explanation.

I'll have to use the old version as a temporary measure.
[Galaxy Note 3 Android Development] Tweakforce_LG:
Any update on "1-3. Automatically turns on screen even if screen is turned off manually". I find this really important to prevent burn in when doing adb backups as those often take a very long time.
[Galaxy Note 3 Android Development] adrenalindj:
Sorry for ressurecting this topic but im trying to "revive" my old hlte

I've changed the screen also and encountered all the problems of bootlooping and TWRP flashing.

I've flashed TWRP built by ashyx and i can boot in recovery but no way to flash a ROM.

Which lineageOS version dis you flash and worked ?

Is there a TWRP version that for these "repaired" devices and allowing to flash a recent lineageos rom ?

Thanks in advance.

@ripee Did you find a way to support "screen repaired" devices ? (find the difference with ashyx biuld)
[Galaxy Note 3 Android Development] adrenalindj:
@ripee I just disassembled the repaired screen to see it labeled SM-N900A. It's seems to be a screen for AT&T variant.

Is there a TWRP for this variant ? Or a guide to compile it myself ?
[Galaxy Note 3 Android Development] earth999:
thanks your work!

I want to know,. can this twrp3.2.1-1 install MagMa-NX. VX1?
[Galaxy Note 3 Android Development] Eleo:
It is still the same aroma installer. So, no. It canNOT.
[Galaxy Note 3 Android Development] Jenvoi:
Hello, I'm sorry but your link seems to be not avaible. Can you check it out please.

---------- Post added at 01:49 PM ---------- Previous post was at 01:45 PM ----------

.

Once again. Sorry but your link seems to be not avaible. Can you check it out. Thank you.
[Galaxy Note 3 Android Development] rayman95:
No issues with both....change browser...or look in op...

---------- Post added at 01:57 PM ---------- Previous post was at 01:49 PM ----------

No issues for me on fat32 non encrypted ...the recovery seems snapier..... Good job....look on my signature for details...
[Galaxy Note 3 Android Development] sarjen iceman:
Is current link in the op is v4?

Finally I successfully flash 3.2.1.1

Normal procedure using TWRP method in the op work fine.

Just don't use the TWRP app to flash it.

My first attempted was failed with using app.

Anyway thanks.
[Galaxy Note 3 Android Development] ripee:
Yes, as I mentioned yesterday, I renamed v4 to the standard twrp name, so the OP link now points to that which was v4. I submitted it to bigbiff yesterday for official support. He will run a test build on TeamWin's Jenkins builder to demonstrate that my code can be built automatically by TeamWin, and to make sure that their build is equal to mine. When the test build is proven to be good by you faithful Note 3 users, I'll give bigbiff the green light to cook an official build, which will be available in the TWRP app ;)

Edit: bigbiff has given his blessing to my TWRP for the Note 3 :) He asked me about whether the 3.2.1-0 builds for the Korean and Japanese variants are stable or if they'd also benefit from an update. It looks like the hltekor variant uses the same kernel config as the unified Americas & Europe hlte build, so I consolidated it into hlte. Since it makes the most sense to build TWRP along the lines of LineageOS, in terms of variant compatibility (since LineageOS serves as the basis for most other roms), the only other geographic variant is hltechn, which uses a different kernel config. The Japanese hltekdi isn't (yet) officially supported by any custom rom. kbc-developers have all the repos necessary for building hltekdi, however they are not a reliable source since they do not release their own rom.

Therefore, we'll have two separate builds for the Note 3 on twrp.me: hlte and hltechn.
[Galaxy Note 3 Android Development] kraken77:
Hi can you have a look into this recovery..i try it on my j5 and it boots aroma perfectly..i dont know what they made to make aroma installer working..hope you can make it..

https://xdaforums.com/galaxy-j5/development/recovery-recovery-pro-galaxy-j5-2015-t3728264
[Galaxy Note 3 Android Development] Imprezzion:
It won't restore modem from a backup. Modem is mounted exclusively read only. Seems to be a more general issue with twrp.
[Galaxy Note 3 Android Development] chris8189:
[MENTION=6005084]ripee[/MENTION] I am very sad to say that your recovery does not work on my device. I'm nearly at the point of buying another phone. I don't know why others are having no issues at all and I am.

Chris
[Galaxy Note 3 Android Development] Eleo:
Thanks for your detailed information Chris! It will surely help dev to find a fix for you

:good:

Jokes aside, please provide at least some info about your device

;)
[Galaxy Note 3 Android Development] stonedead:
Actually, this twrp project started from his issue in original development thread. OP been called to help him in original thread, i believed he already provide enough info..
[Galaxy Note 3 Android Development] Eleo:
Well, ok.
[Galaxy Note 3 Android Development] sarjen iceman:
May I know which method you flash?

Odin or TWRP recovery?

V4 should be fine ...as I said before my first attempted was fail and stuck in download mode recovery.

Then I installed back 3.2.1 using Odin 3.10.7

I did not try until V4 released and yesterday it was fine with TWRP recovery method.
[Galaxy Note 3 Android Development] ripee:
The reason why this TWRP is compatible with Aroma is because it's built from an unofficial android_bootable_recovery source. The problem with using such a source is that builds compiled from it could never become official. I understand that some people don't care about official builds, I personally care most about properly functioning builds, but there is the element of a "stamp of approval" once a build becomes official that makes development worthwhile as well as giving users peace of mind that they won't brick their devices.

That said, I have no idea how to implement Aroma compatibility, but even if I did, I would be reluctant based on the above reason. Whether or not Aroma is stable on that J5 TWRP is another matter, but it takes two to tango. If Aroma development had stopped over 6 months ago, then no matter how well TWRP is adapted for compatibility, every future version of TWRP is bound to become less and less stable with Aroma.

If TeamWin implements Aroma compatibility into their official sources, then of course it would become compatible then. Given TeamWin's reputation and collective expertise that exceeds my own by many orders of magnitude, only official Aroma support would be reliable enough to be considered official.

Off the record, I never understood the appeal of Aroma. Isn't it a pain in the butt to tap through all those menus? A gapps-config file tells the installer exactly what the user wants to include and remove with no input required.
[Galaxy Note 3 Android Development] sarjen iceman:
Hi [MENTION=6005084]ripee[/MENTION]

The thread was edited to pre-official

So your current download link still V4 or new update?
[Galaxy Note 3 Android Development] chris8189:
I flashed it with Odin several times and it failed and also through a working TWRP recovery that I have.
[Galaxy Note 3 Android Development] ripee:
I linked the latest Odin in the OP because the Note 3 is a new enough device to be compatible with it. Please paste the log from Odin when you attempt to flash the .tar file. Use the "AP" button in Odin to do so. ;)
[Galaxy Note 3 Android Development] Eleo:
For ROMs that are 1.5-1.9 GB in size (like port TW/MIUI and etc ROMs), we have about 9-10 different pages with about 200+ options having "mark all you want to be installed/debloated", "select one of the options below" and etc (options for apps, csc, systemUI, debloater and etc). At these times you would rather have aroma installer than make a config file (and expect each users to build config file for themselves).
[Galaxy Note 3 Android Development] chris8189:
[MENTION=6005084]ripee[/MENTION] if you read the last few pages of the normal TWRP thread, you will realise how much trouble I've been having flashing TWRP, as well as [MENTION=8735415]Josantium[/MENTION]

The build you've posted in this thread is unfortunately no different. It doesn't work on my device (N9005). I always use the AP button in Odin when flashing recoveries. I will do it again, just to get you a log from Odin.

Chris