yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] ripee:
No amount of reading on my part will help me help you any better. I want to ask about your history of flashing on your N9005.

1. What are the earliest and most recent twrp version that work for you?

2. Are they official or have only unofficial twrps worked?

3. Have you ever re-partitioned your phone?

3. Are you on stock TW? If not, what version of stock TW did you have running when you switched over to your custom rom?

If you're on a custom rom but you came from any stock TW older than the latest official currently available, the cause is probably that your memory isn't partitioned the way that twrp expects. In that case, the easiest thing to do would be to flash the latest stock and start over. Not what you want to hear but custom builds work best coming from the latest stock.
[Galaxy Note 3 Android Development] JJEgan:
TWRP is on twrp.me or even in the AT&T section .
[Galaxy Note 3 Android Development] adrenalindj:
i know that but there is no AT&T version for hlte ;)

That's why i'm asking on how to compile TWRP ;)
[Galaxy Note 3 Android Development] JJEgan:
Sorry i know nothing about the AT&T models .

May help from twrp.me link.

https://xdaforums.com/t/dev-how-to-compile-twrp-touch-recovery.1943625/#post-32965365

Back of my mind AT&T does not use twrp but safestrap (could be wrong )
[Galaxy Note 3 Android Development] adrenalindj:
Yes AT&T uses Safetrap.

But, the phone is an HLTE (N9005) with an AT&T screen (N900A) so there is no problem with bootloader.

The thnig is to find what comes from AT&T screen in the kernel i think.

I already tried to compile TWRP (with the help of the documentation) with no success : i don't know where to start. I can compile the kernel but i don't know what it is needed for TWRP itself.

Instead, I've followed the lineageos documentation to compile their ROM with their recovery.

I've activated some options in the kernel (CONFIG_MACH_HLTEATT) to see if it adds support for AT&T but no luck for now.

And I don't know what to look or activate.

My last attempt will be to find what defconfig and corresponding options/code is supported in the kernel used in TWRP 2.8.7 because it's the last release phone can install without problem (except the ashyx version).
[Galaxy Note 3 Android Development] Josantium:
I'm running a N900T, and am in the same boat as Chris as far as experiencing extreme difficulty and frustration trying to flash TWRP and most custom ROMs.

1. 2.8.7 is the earliest build I've tried. It's also the latest official build that has worked for me. Ashyx's custom 3.2.1.0 build has also worked. These are the only two builds that have worked. Nothing in between has worked.

2. 2.8.7 was official. The 3.2.1 build was unofficial.

3. I have never repartitioned my phone outside of flashing stock ROMs to it.

4. I'm assuming that "TW" means "TWRP". No, I'm running Ashyx's custom unofficial v3.2.1 TWRP, which is what I used to flash Lord Eko's RR 5.8.3, the only custom ROM that will function on my phone.

Like Chris, I've also flashed a middle KitKat and the latest Lollipop stock ROMs from Samsung multiple times, and thereafter tried to flash a standard TWRP build, to no avail. It seems that not even reverting to total stock fixes the issue.

I think I speak for both Chris and I when I say that this has been an incredibly baffling and frustrating situation. It's as if there is some underlying aspect of our phones that is different from others' devices. Any help in identifying and correcting this would be very, very appreciated.
[Galaxy Note 3 Android Development] ripee:
By TW I meant TouchWiz, but ashyx must have deleted his hlte repos because I can't find them, otherwise I'd see what he did and adapt my build accordingly.
[Galaxy Note 3 Android Development] Josantium:
Ahhh - gotcha. I was running TW 5.0 - the latest stock Lollipop ROM. As for the one working build of 3.2.1.0 that Ashyx made, I've attached it here for you! :)
[Galaxy Note 3 Android Development] ripee:
Thanks but this doesn't help me at all. I need the source code. :P
[Galaxy Note 3 Android Development] Josantium:
[MENTION=4899305]ashyx[/MENTION]

HELP!!! :D
[Galaxy Note 3 Android Development] fad19:
I am using Twrp 3.2.1-0 on N900W8. Backing up Rom gets stuck and automatically reboots
[Galaxy Note 3 Android Development] ashyx:
No github source as it was only a fix up build and not something I plan to continually support. Seems you have that covered.

No real magic. Removed/changed a few flags, but I guess what got it booting was the stock kernel.
[Galaxy Note 3 Android Development] ripee:
Sorry but that's a non answer... which flags did you change?
[Galaxy Note 3 Android Development] kramer04:
the links in OP are wrong. when you click on download it shows twrp 3.2.1-0 not 3.2.1-1
[Galaxy Note 3 Android Development] denis28381:
Can't use aroma
[Galaxy Note 3 Android Development] Eleo:
You cannot. It is explained in many posts in thread. Try searching "aroma" and find those to see the answer why.
[Galaxy Note 3 Android Development] ripee:
The test build is 3.2.1-0, the official build will be 3.2.1-1.
[Galaxy Note 3 Android Development] sarjen iceman:
I'm confused here

So you are saying that test build and V4 is not the same?

Need to try test build or just wait official release from TWRP?
[Galaxy Note 3 Android Development] ripee:
V4 code was submitted to TeamWin and it's what the test build is made from. Flash it to see if TeamWin's build server made a twrp build that works the same as mine. The version will automatically be bumped up in the official build because there already is an official 3.2.1-0.
[Galaxy Note 3 Android Development] joko3b:
I just flash this TWRP, but in my N9005 stuck when installing C9 Pro Port ROM.
[Galaxy Note 3 Android Development] stonedead:
You need twrp 2.8.7 for that as twrp 3.0 and higher version did not support aroma installer..
[Galaxy Note 3 Android Development] Donskjr:
Works on my N900T. Backups are a lot faster than the official TWRP. Thanks!
[Galaxy Note 3 Android Development] ripee:
As soon as hltechn is ready for official support, I'll ask TeamWin to build 3.2.1-1 for hlte and hltechn.
[Galaxy Note 3 Android Development] chris8189:
I wish I knew what was wrong with my device that is preventing it booting this TWRP as well as the official, and also certain ROM's.
[Galaxy Note 3 Android Development] ripee:
Did you provide the logs and screenshots of what exactly happens when you try flashing it, like I asked? I don't have time to dig through bigbiff's thread, sorry. As much as I'd like to help any way I can, your issues are in the minority, sorry.
[Galaxy Note 3 Android Development] chris8189:
I'm aware they're in the minority. I will provide you the logs hopefully tomorrow when I get the chance to.
[Galaxy Note 3 Android Development] NLhardcore:
Works

Now it works for me!
[Galaxy Note 3 Android Development] chris8189:
[MENTION=6005084]ripee[/MENTION] As mentioned, I have uploaded the screenshot of Odin flashing your TWRP version. It just looks as though it has successfully flashed it, but for whatever reason it bootloops.

Chris
[Galaxy Note 3 Android Development] ripee:
Sorry if I asked this before, but I'm just trying to narrow it down now that you provided this Odin info: Can you flash 3.2.1-1's IMG file from within an older twrp? If it flashes, does it also bootloop? Does the older twrp report any errors?
[Galaxy Note 3 Android Development] chris8189:
I had a go and flashed known working twrp-2.8.7.0-hlte-4.4 via Odin, booted into it and then pushed your TWRP version IMG file to the device, via ADB. I then proceeded to flash the IMG file, however, much like Odin, showed a 'successful' flash. I took the screenshot from within TWRP of the flash page for you to see. I then restarted into recovery after the flash and the phone went into a continuous bootloop trying to boot into recovery.

Chris
[Galaxy Note 3 Android Development] ripee:
Like ashyx said, it has something to do with the settings in my device tree... too bad I have no idea which. I'll take a look at all the older branches and anyone else's trees to work it out, no promises how long it'll take or if I can fix it, but I've fixed similarly tedious bugs in my other twrps so there's always a chance.
[Galaxy Note 3 Android Development] chris8189:
Thank you :)
[Galaxy Note 3 Android Development] Dasy Den:
HlteCHN can't not mount the efs and modem

Thanks for the dev. Before I flash 3.2.1 or hltechn 3.2.0 . I found the twrp can't not mount the efs and modem. So I can't recovery the modem and efs backup. Hope to fix it. Thx
[Galaxy Note 3 Android Development] ripee:
Why do you want to mount the EFS and Modem partitions?
[Galaxy Note 3 Android Development] bigbiff:
You should only need them as emmc in the TWRP fstab to backup. Mounting allows bad things to happen to the partition.
[Galaxy Note 3 Android Development] chris8189:
[MENTION=6005084]ripee[/MENTION] Just wondering if you have found the time to look at older builds for comparison with yours, and if anything may have jumped out that may be different?

Chris
[Galaxy Note 3 Android Development] ripee:
Working on it. Better yet, can you please contact whoever it was who built the lastest version that works on your phone and ask them for their sources.
[Galaxy Note 3 Android Development] chris8189:
Great, thanks for the update! [MENTION=4899305]ashyx[/MENTION] could you please provide [MENTION=6005084]ripee[/MENTION] with the source code for the working TWRP 3.2.1-0 LL file that you made. Much appreciated both of you.

Chris
[Galaxy Note 3 Android Development] ripee:
ashyx mentioned already that he never used a dedicated device tree. I just can't figure out what's causing chris8189's problem with my build.

Edit: Try this, I just changed the cache partition size because it was different in almost every branch of the device tree.

twrp-3.2.1-0-hlte.img

twrp-3.2.1-0-hlte.tar
[Galaxy Note 3 Android Development] chris8189:
Just tried flashing the image file in working version of TWRP, and it flashed 'successfully' but bootloops when trying to boot into it. So I'm guessing its not the cache size.

[MENTION=8735415]Josantium[/MENTION] - Can you also please confirm if the build that [MENTION=6005084]ripee[/MENTION] just uploaded to his previous post is working for you or not. I know you have the same problem as I do.

Chris
[Galaxy Note 3 Android Development] Huy Hyner:
You can try 3.0.2.0 , it does support AROMA rom installer and preety smooth in swiping and selecting actions
[Galaxy Note 3 Android Development] Eleo:
After 3.0.0.x as I recall there is no aroma support on N9005/HLTE. Latest was 2.8.7.0. Please check
[Galaxy Note 3 Android Development] AdhibH12:
I'm facing the same problem that [MENTION=7215433]chris8189[/MENTION] and [MENTION=8735415]Josantium[/MENTION] are facing. Not able to boot the latest versions of twrp and roms. I'm using twrp 2.8.7 and Lord Eko's RR rom as it's the only nougat rom that works on this device. Also having a hard time getting my Jio (LTE only) sim to work.
[Galaxy Note 3 Android Development] rayman95:
I confirm, made a full wipe and backup and restore with last twrp and have no issues at all....

Good job....:good:
[Galaxy Note 3 Android Development] ripee:
I use the dtb.img file from android-6.0 branch, but I used the zImage file from the 7.1 branch. Please try version 3.2.1-1 for which I used the 6.0 zImage, courtesy of jcadduono:

twrp-3.2.1-1-hlte.img

twrp-3.2.1-1-hlte.tar

If most people are reporting no problems with 3.2.1-0, but you three are, I can't help but wonder if you three flashed the same set of custom images in the past since coming from stock, ie. same CWM, twrp, roms, add-ons, etc. The only way to eliminate the possibility of a hardware problem is to start from scratch: re-flash stock, factory reset, let it finish the setup wizard, then re-flash twrp 3.2.1-0 and go from there with your chosen rom, gapps, and add-ons.

I'm sorry that I can't help you any more, I'm still learning how to develop.
[Galaxy Note 3 Android Development] bigbiff:
My best guess is they never had their bootloader upgraded that required the new DTB to define the hardware to the kernel. Either that or they got some random sample of a device that had different hardware requirements that are described in [MENTION=5672995]jcadduono[/MENTION]'s DTB update.
[Galaxy Note 3 Android Development] piroxi:
Same as you bro! No TWRP working above 2.8.7.0

Thanks for recommending Lord Eko's RR rom. It's gonna make me crazy !!!
[Galaxy Note 3 Android Development] kramer04:
If it can help.

I use BL N9005XXSGBQE1 and CP N9005XXUGPQB1. Never had any issues using TWRP 2.8.7.0-4.4 to 3.2.1-0 hlte.

Actually I am on 3.2.1-1 to test it. No issues.

:svetius:
[Galaxy Note 3 Android Development] Imprezzion:
I use a N9005 with the QD1 loader cause basically I am too lazy to upgrade it to QE1 and the QB1 Nordic modem and all twrp versions have been working fine for me.
[Galaxy Note 3 Android Development] piroxi:
Not working too :crying:
[Galaxy Note 3 Android Development] ripee:
For those of you for whom my twrp doesn't work, perhaps the most obvious thing to try is to update your bootloader to the one in my BasketBuild.
[Galaxy Note 3 Android Development] piroxi:
Downloaded this "N9005XXSGBQE1_N9005XXUGPQB1.tar" . How should I flash? As BL ??

Thanks in advance!!
[Galaxy Note 3 Android Development] Eleo:
Read this post
[Galaxy Note 3 Android Development] rayman95:
Just a question, is it better to have BL+CP from 1 firmware than mixed????? BL from Italy QE1 and CP from Nordic.....
[Galaxy Note 3 Android Development] ripee:
Makes no difference, only the CSC is country/carrier-specific. BL (bootloader) and CP (modem) are not.
[Galaxy Note 3 Android Development] nikonant7:
Any version newer than 2.8.7.0 does not work on my hlte too. It cause bootloop on the Samsung Galaxy Note 3 logo.
[Galaxy Note 3 Android Development] Eleo:
Wow

I couldnt read question. I see only question marks:laugh::laugh:

Jokes aside, please use "a sign at a time". It can be reported and removed because of this. No need for drama or trolling

;)

Back to topic: Exactly NO difference at all. As long as you have correctly assigned BL and CP, where CP contains both modem.bin and NON-HLOS.bin, and both files are for same device model as yours, there is no difference.

Mine is QE1+QB1 too.
[Galaxy Note 3 Android Development] chris8189:
Just to confirm guys, I am running a very new Nordic baseband and bootloader on my hlte Note 3 (see attached screenshot). I am telling you that this does not make a difference at all. Anything higher than TWRP 2.8.7 will not work, period. [MENTION=6005084]ripee[/MENTION] In have already tried your baseband and bootloader in your basketbuild, and this also does not allow me to successfully boot up your TWRP versions, or the official ones on the TWRP site.

I can only assume that there was a certain batch of N900's that had slightly different hardware in them than the rest.

Chris
[Galaxy Note 3 Android Development] piroxi:
Me too. Exact same scenario. CP + BL alredy updated, no way to install twrp over 2.8.7.0

As I know, there are many people with same problem.

It would be great if someone could help us.
[Galaxy Note 3 Android Development] ripee:
Whatever workaround that ashyx used may or may not be the proper way of doing things from TeamWin's perspective. Not that I'm an expert, but I try to keep my code as simple as possible which enabling all recent and relevant functionality and ensuring that TeamWin's Jenkins builder can build it, not just me in my build environment.

As I have no idea what else to change in my source code, I cannot help you unless someone directs me to a source whose build does work. Then and only then could I compare it with my source and make any necessary changes. If, however, your problem is hardware-related, then no one can help you.

And what is this obsession with Nordic bootloaders and modems? Like I've said before, it makes absolutely no difference from which country/carrier they come from! Many countries/carriers share the same versions of one or both!
[Galaxy Note 3 Android Development] svbarbosa:
I am the one to blame.

After a lot, and I really mean a lot, of testing with several modems, I found out that the one that provides the quicker GPS fix and keeps the fix stable is the Nordic modem.

This info is in my Rock Stable thread and in a few scattered posts.

Since Nordic is THE best modem, I use the Nordic BL, although some pick the newest BL I believe from Italy firmware.

The truth is that either BL works fine.
[Galaxy Note 3 Android Development] ripee:
Good to know, but I've always been in the habit of flashing the latest of each on the devices I support because it always helps avoid stability issues if you're flashing the latest builds regularly, particularly the bootloader. My own Galaxy Tab S2 2015 has had random reboots until I updated its bootloader, then they stopped, so that's why I recommend it.

As for TWRP, like I said, I'd need to see other people's source code before I could try anything that I haven't tried yet. My hlte twrp code is derived from what works for other phones and tablets, so I stick to what works. Each model is different so there are of course changes, sometimes major, but in the case of the Note 3 N9005, if mine doesn't work on your device, all I can do is apologize for the inconvenience. :(
[Galaxy Note 3 Android Development] chris8189:
[MENTION=6005084]ripee[/MENTION] - Since TWRP 2.8.7 works on our devices, would it be possible for you to compare the source code of 2.8.7 against 3.x.x? That might provide some clue.

Chris
[Galaxy Note 3 Android Development] ripee:
If you tell me which branch was used to build it.
[Galaxy Note 3 Android Development] chris8189:
The version I'm referring to is the official 2.8.7 4-4 on the twrp.me site. Maybe [MENTION=2638973]bigbiff[/MENTION] can give you the branch?
[Galaxy Note 3 Android Development] ripee:
It's publicly accessible.
[Galaxy Note 3 Android Development] chris8189:
OK, so then it will be easy to compare the differences.
[Galaxy Note 3 Android Development] boomyi:
where is South Korea version? not update?
[Galaxy Note 3 Android Development] ripee:
Included in unified hlte.
[Galaxy Note 3 Android Development] boomyi:
?? where?

where is Korea version?
[Galaxy Note 3 Android Development] boomyi:
South Korea ver update 3.0.0 ver last there not update last version
[Galaxy Note 3 Android Development] JJEgan:
3.2.1.1 is on the TWRP.me site

twrp-3.2.1-1-hlte.img.tar	10.2M	2018-02-26 19:10:25 EST

Americas, Europe & Korea (SM-N9005/hltexx, SM-N900K/hltekor, SM-N900L/hltekor, SM-N900P/hltespr, SM-N900R4/hlteusc, SM-N900S/hltekor, SM-N900T/hltetmo, SM-N900V/hltevzw, SM-N900W8/hltecan):
[Galaxy Note 3 Android Development] boomyi:
no

no i flash before erro bootloader different
[Galaxy Note 3 Android Development] JJEgan:
What model do you have.

Use Phone Info to check.
[Galaxy Note 3 Android Development] boomyi:
i have sm n900s but not update hltekor ver
[Galaxy Note 3 Android Development] JJEgan:
Try twrp forum as posted in OP
[Galaxy Note 3 Android Development] Huy Hyner:
Probably because of differences in variants. Mine is N900L / hlteskt but since it is less-supported than the official International N 9005 so I think that yours also supports this one?
[Galaxy Note 3 Android Development] ripee:
Unfortunately there are no reliable kernel sources for the hlteskt, so I'm unable to update my source with it. Using an older kernel with a newer codebase doesn't work.
[Galaxy Note 3 Android Development] romanom82:
Hello, my note 3 was broken and unused for almost 2 years.

Yesterday i replaced the LCD screen. Everything is working, so i tried to update it, but without success.

Im trying to use RR 7.1.2 from this thread: https://xdaforums.com/galaxy-note-3/general/aosp-nougat-holy-grail-hlte-rock-stable-t3630301

As i can see, many people has the same problem. I can´t update TWRP above 2.8.7 and because of this we cannot install RR ROM.

If its help, here my note 3 info:

SM-N9005

hltexx / cm_hlte

Country: Brazil

Model: ZTO (SM-9005ZKQZTO)

Bootloader: N9005XXSGBQD1

Baseband: N9005XXUGPQB1

Sorry about my poor english.
[Galaxy Note 3 Android Development] piroxi:
Hi bro!

As I know, there is no solution and nobody can help us.

There is a lot of n9005 users with same problem.

If you discover something, tell us please!
[Galaxy Note 3 Android Development] JJEgan:
Can you use another TWRP recovery or CWM/Philz recovery to flash .

Repeat try twrp.me forum .
[Galaxy Note 3 Android Development] piroxi:
Sorry, not found that forum.
[Galaxy Note 3 Android Development] boomyi:
u means sm n900s not work?? or oreo not work sry my English not perfect
[Galaxy Note 3 Android Development] ripee:
Yes, I can't build for hlteskt because there are no good sources.
[Galaxy Note 3 Android Development] boomyi:
sry for hear that South Korea is not open mind ti developer
[Galaxy Note 3 Android Development] ashyx:
Why not just get someone to create a backup with twrp or a raw image of the ROM and post it?
[Galaxy Note 3 Android Development] romanom82:
I dont know what happened, but now its working for me.

I used this TWRP (TWRP_3.2.1-1_sm-n9005_lzma_020218.tar) on Android File Host and flashed with odin V 3.13
[Galaxy Note 3 Android Development] ripee:
You don't know what happened? You used a build created from different sources.
[Galaxy Note 3 Android Development] nil2009:
I tried flashing on my note 3 n900l but the result was unable to boot into recovery and switch to download mode.
[Galaxy Note 3 Android Development] JJEgan:
Usual is you flashed version for not your model .
[Galaxy Note 3 Android Development] Spaghetti Papi:
All working fine here on my hlte ?

Also this is the first recovery I've tried on this phone that correctly updates the LineageOS ROM with their automatic method (so without having to manually select the file in the recovery). I gotta say I'm quite surprised!

Thanks for the very good job!
[Galaxy Note 3 Android Development] ripee:
[MENTION=7215433]chris8189[/MENTION] and everyone else for whom my build doesn't work, has/does build 2.8.7 allow for automatic rom updates, like Spaghetti Papi described above? I realize that current rom versions aren't compatible with twrp 2.8.7 but I'm asking about your past experience. I'm asking because if any unofficially supported modifications would need to be made to my source, automatic rom updates may get broken.

I'll take another look at the omni-4.4 branch from which 2.8.7 was built and run another build this weekend.
[Galaxy Note 3 Android Development] ripee:
3.2.1-2

twrp-3.2.1-2-hlte.img

twrp-3.2.1-2-hlte.tar

I used the official LineageOS mkbootimg.mk file from the android_hardware_samsung to package the img file and took out an exFAT-related entry which is absent from haggertk's code in the lineage hlte-common repo. Perhaps a possible cause of the problem was using the old non-standard way of making the twrp file at the very end of the compilation process.
[Galaxy Note 3 Android Development] piroxi:
Alredy flashed:

can't enter recovery, goes directly download mode.

Normal boot works.
[Galaxy Note 3 Android Development] ripee:
ok thanks, i'll revert.

Edit: previous packaging method is back, same links.
[Galaxy Note 3 Android Development] piroxi:
Thanks in advance for your time & disinterested work.

Dreaming one day will be able to install Oreo on my N9005 !!!
[Galaxy Note 3 Android Development] romanom82:
desinterested ?
[Galaxy Note 3 Android Development] svbarbosa:
I believe what he meant is "not looking for any monetary / material compensation".
[Galaxy Note 3 Android Development] chris8189:
Yes, I can confirm that 2.8.7 does allow for 'OTA' updates.
[Galaxy Note 3 Android Development] rayman95:
Chief, is this version is an update for those who haven't problems to flash twrp or is it for those who have bootloop problems????? I'm already on 3.2.1-1 version...

Thanks..
[Galaxy Note 3 Android Development] ripee:
For those having problems. The official build works for most people so this one has nothing in it that would make it work any better than 3.2.1-1.