yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] ripee:
If twrp 3.2.1-0 built from the cm-12.1 branch flashes successfully, that's one step closer from where you were before. I will re-build my device tree and see about using the cm-12.1 settings.
[Galaxy Note 3 Android Development] ashyx:
Isn't this down to the same issue, the kernel?

If these kernels cannot boot TWRP then they're unlikely to boot the rom neither.
[Galaxy Note 3 Android Development] chris8189:
Well what I am saying is that our phones did indeed boot your LL version of TWRP, but they failed to load the latest ROM's.
[Galaxy Note 3 Android Development] ashyx:
That's what I'm getting at. TWRP that does not boot seems to be using the same non stock kernel as the unbootable ROMs.

Which non stock ROMs boot?
[Galaxy Note 3 Android Development] chris8189:
Lord Eko's Resurrection Remix
[Galaxy Note 3 Android Development] ashyx:
Then in theory TWRP should boot with that kernel.
[Galaxy Note 3 Android Development] chris8189:
The only TWRP newer than 2.8.7 that I have managed to boot successfully is your LL version. Even running Lord Eko's Resurrection Remix, flashing the newer TWRP's did not work.
[Galaxy Note 3 Android Development] ashyx:
You misunderstand. I'm assuming ERR is nougat?

If the kernel in the boot image can boot this ROM then there's no reason it shouldn't boot TWRP.

Basically what needs to be done is compile TWRP with this kernel. If someone can provide the boot.img from this ROM?

Also you could try booting one of the unbootable ROMs with the boot.img from ERR.

Just back it up and restore it after installing one of the other ROM's
[Galaxy Note 3 Android Development] ripee:
I rebuilt hlte 3.2.1-2 yet again with the zImage that I extracted from stock 5.0 N9005XXSGBQD5 and attached them for reference.

Same links in the OP.
[Galaxy Note 3 Android Development] rayman95:
just update from 3.2.1-1 by recovery but can't boot at all or enter in recovery anymore, even after removing battery.... still continual reboot with recovery screen.....

had to remove battery, start in dl mode and flash anterior version by odin...
[Galaxy Note 3 Android Development] ripee:
Oh well, because Eko's RR kernel is the same msm8974 from lineage 14.1 and 15.1. If ashyx managed to get the old LL kernel working, perhaps we'd need to build the zImage from the cm-12.1 branch using the old kernel that was used back then, kernel_hlte.
[Galaxy Note 3 Android Development] chris8189:
I tried that and it worked! I downloaded Vidwhal's newer Resurrection Remix ROM and swapped the boot.img file contained within the zip with Lord Eko's Resurrection Remix boot.img file. Then transferred the Vidwhal's 'modified' zip, along with the latest 7.1 gapps to the phone and flashed it in [MENTION=4899305]ashyx[/MENTION] LL TWRP.

The phone booted Vidwhal's ROM...however it came with errors, such as the camera wasn't working, a notification saying 'Bluetooth Share keeps stopping' error message. But the phone was 'usable'.

Well this is certainly a step in the right direction. It is most definitely the kernel that is the issue here.

When you say just back it up and restore it after installing one of the other ROM's, what do you mean exactly? I now have a semi-functioning phone running one of the later RR ROM's, albeit with Lord Eko's boot.img file.

Chris
[Galaxy Note 3 Android Development] chris8189:
Here you go. Lord Eko's boot.img from his Resurrection Remix Nougat 7.1 ROM attached.
[Galaxy Note 3 Android Development] ripee:
hlte 3.2.1-2 with Lord Eko's kernel

twrp-3.2.1-2-hlte.img

twrp-3.2.1-2-hlte.tar

I extracted zImage from Lord Eko's boot.img.

source: https://github.com/ripee/twrp_android_device_samsung_hlte
[Galaxy Note 3 Android Development] rayman95:
Who should try this, only those with recovery problems?????
[Galaxy Note 3 Android Development] chris8189:
Nope, sorry. Just tried flashing it and it boot loops....

---------- Post added at 11:57 AM ---------- Previous post was at 11:11 AM ----------

Yes
[Galaxy Note 3 Android Development] ripee:
This proves my point: Lord Eko uses the same msm8974 kernel as lineage does. So I see the only way to build a working twrp for you unlucky ones is to integrate twrp code into the cm-12.0 or 12.1 branch, which defeats the purpose of a dedicated twrp device tree that could be used for future twrp versions.
[Galaxy Note 3 Android Development] chris8189:
OK. So let's say you, or another dev does integrate twrp code into the cm-12.0 or 12.1 branch to allow us a working twrp, will this working twrp allow us to flash the latest Oreo ROM's etc, just like all of the 'lucky' ones with this device who already can?

Chris
[Galaxy Note 3 Android Development] ripee:
Theoretically, it should, since the twrp branch we'd be using is android-8.0 or 8.1, which corresponds to 3.2.1.
[Galaxy Note 3 Android Development] chris8189:
Great. I'll throw some coins your way if this works out, for all of the effort.

Chris
[Galaxy Note 3 Android Development] ripee:
Ok, I rebuilt 3.2.1-2, same links as above, this time using Lord Eko's zImage-dtb file and the msm8974 kernel source, which is how twrp is designed to be built given that it's already integrated into the hlte-common cm-14.1 branch.

twrp-3.2.1-2-hlte.img

twrp-3.2.1-2-hlte.tar
[Galaxy Note 3 Android Development] chris8189:
Nope, sorry. Not booting,. Does a boot loop.

Chris
[Galaxy Note 3 Android Development] ripee:
Oh well. I have no idea how your phone is different from the others that twrp as integrated into lineage code does not work for you.

I blame your phone, sorry.
[Galaxy Note 3 Android Development] chris8189:
Great. No Oreo for my Note 3 then...or for those other 'unlucky' ones for that matter.

Is that upload of yours basically TWRP code integrated into the CM-12.0 - 12.1 branch as you stated before?

I was ready to send you a donation over, thinking you'd sort it.
[Galaxy Note 3 Android Development] ripee:
I'm sorry, do I owe you something?
[Galaxy Note 3 Android Development] chris8189:
Of course not. I just had my hopes up that I'd be running Oreo on my hlte, after you had seemingly figured out what the root cause of the problem was.
[Galaxy Note 3 Android Development] wazer1337:
I just updated my 9005 hlte version, no problems at all.
[Galaxy Note 3 Android Development] chris8189:
Using the above posted recovery from [MENTION=6005084]ripee[/MENTION] ?

Can anyone else who is regarded as having an 'unlucky' device confirm successful flashing of this TWRP? [MENTION=1488698]rayman95[/MENTION] [MENTION=8735415]Josantium[/MENTION] [MENTION=9202340]eager123[/MENTION] [MENTION=8488676]InfinityBlaze[/MENTION]
[Galaxy Note 3 Android Development] eager123:
I haven't tried yet. I will though next weekend. (btw, where is the actual link to the build? the ones above are dead unfortunately :rolleyes:)
[Galaxy Note 3 Android Development] rayman95:
I'm not concerned, hopefully for me...I have no issues with Twrp......
[Galaxy Note 3 Android Development] rayman95:
flashed last version xithout issues, thank's chief......
[Galaxy Note 3 Android Development] chris8189:
Luckily I still had it saved to my laptop. Here it is.
[Galaxy Note 3 Android Development] ripee:
???

Try 3.2.2, linked in the OP.
[Galaxy Note 3 Android Development] chris8189:
Just tried that, and still boot looping. Interested to see if the same applies for [MENTION=9202340]eager123[/MENTION]

By the way, I have uploaded the only working TWRP higher than 2.8.7 that [MENTION=4899305]ashyx[/MENTION] built a while back. It loads and works without any problems, however if I use it to flash an Oreo ROM, the phone will not boot the ROM, even though this TWRP seems to successfully flas it to the phone.

Chris
[Galaxy Note 3 Android Development] ashyx:
The issue isn't TWRP it's the kernel being used. Which is why certain Oreo roms won't boot either. The kernel just isn't compatible with some of these devices for some reason. [MENTION=7215433]chris8189[/MENTION] proved this by using a kernel from another rom and it booted the previously non booting rom.
[Galaxy Note 3 Android Development] chris8189:
So, basically for us unfortunate ones, we need a custom kernel making?

Anything else that I can do to help I will do my best.

Chris
[Galaxy Note 3 Android Development] ashyx:
Lineage and the likes already use custom kernels. However some just don't boot some do.

Seems there's something the way Lord Eko builds his kernel that makes it work.

Which versions of nougat are these roms based on?
[Galaxy Note 3 Android Development] chris8189:
Lord Eko's ROM is based on Nougat 7.1.1

[MENTION=5316466]Lord Eko[/MENTION] can we please request your help regarding this.
[Galaxy Note 3 Android Development] Lord Eko:
actually i am not working anymore on Note 3, anyway our device tree is way different now....

for example kernel source is the generic msm8974 one [LineageOS/android_kernel_samsung_msm8974] and many resources are moved out from device tree.

see this
[Galaxy Note 3 Android Development] chris8189:
OK, thanks anyway mate. Just thought I'd ask.

Chris
[Galaxy Note 3 Android Development] ripee:
This is what I was talking about when I mentioned that building a kernel from the old kernel_hlte source may not work. Building it would require the syncing of the cm-12.1 branch and compiling only of the kernel file or zImage-dtb, which is what I used from when I built from the cm-14.1 branch using the newer msm8974_kernel.

Since twrp recovery branches are backwards compatible, in theory there should be no problem building twrp on the back of an older kernel, but the end result is likely to be the same: you would be able to flash the older kernel twrp, and even an Oreo rom, but it may still refuse to boot.

Can you by any chance post your board specs, such as screenshots of every page in DevCheck on the Play Store?
[Galaxy Note 3 Android Development] chris8189:
Sure. Screenshots below as requested. You can see that I'm running Lord Eko's kernel and Vidwhal's Resurrection Remix, which he built with the newer msm8974 kernel, which doesn't work on my device.

Chris
[Galaxy Note 3 Android Development] ripee:
You are using that kernel, but you're also using an older twrp. What version are you on now and what was the oldest twrp you had first flashed when you migrated to custom roms?
[Galaxy Note 3 Android Development] ashyx:
TWRP recovery sources are backwards compatible with older kernel versions but not the branch it's built in.

Older kernels will run into versioning issues if recovery is built in a newer branch.

For instance, a 5.1.1 kernel can be built into twrp 3.2.1.0 sources, but would need to be built using the lollipop branch or even kitkat branch.

So attempting to build the latest twrp with a lollipop Kernel in MM or NN branch is likely to not boot.

Obviously this is without patches to the kernel source.
[Galaxy Note 3 Android Development] chris8189:
When I migrated to custom ROM's, I had TWRP 2.8.7 flashed. This flashed Lord Eko's Nougat 7.1.2 Resurrection Remix no problem. At the moment, I have ashyx's TWRP flashed, which is 3.2.1-0
[Galaxy Note 3 Android Development] chris8189:
I've just had a bit of messing about, and had a go at flashing [Kernel][8.1] Lolz-Kernel For note 3(SD) (custom Oreo kernel) and Vidwhal's Oreo 8.1 ROM again. Without any luck unfortunately. Both the custom kernel and Oreo ROM flashed fine in TWRP, but because they were obviously built using the new msm8974_kernel and not kernel_hlte, the phone would not boot the ROM.

So to conclude, it is something about my phone's board / architecture that only permits the use of the old kernel (kernel_hlte).

Chris
[Galaxy Note 3 Android Development] ripee:
To all the "unlucky" users:

Can you please provide us with the CSC country/carrier code of your phone? I'm just curious to see if there's a pattern in the units that aren't booting with the msm8974 kernel.
[Galaxy Note 3 Android Development] ashyx:
It's odd, because it's the bootloader which initalises the hardware and then boots the kernel.

However from what I can gather booting and non booting devices are using the same bootloader so can't see it being a hardware issue.

It would be interesting to see the partition layout of both devices.

ls -laR /dev/block

cat /proc/partitions
[Galaxy Note 3 Android Development] chris8189:
As requested [MENTION=4899305]ashyx[/MENTION]

Chris
[Galaxy Note 3 Android Development] ashyx:
Just need someone with a working device to post theirs for comparison.
[Galaxy Note 3 Android Development] chris8189:
[MENTION=1488698]rayman95[/MENTION] - Could you please post yours for comparison.

Thanks.
[Galaxy Note 3 Android Development] Al-Bcherrany:
Flashed latest TWRP, works perfectly thumbs up :fingers-crossed:
[Galaxy Note 3 Android Development] chris8189:
That's great. Could you do me and [MENTION=4899305]ashyx[/MENTION] a favour and run a command line in shell so that we can see the partition layout of your device, then upload the information here. The two commands you need to run, while the phone is connected to your laptop running TWRP is as follows;

ls -laR /dev/block

cat /proc/partitions

Appreciate it.

Chris
[Galaxy Note 3 Android Development] rayman95:
done, but can't copy it..if i copy log it say that it's in sd/recovey but can't find it...
[Galaxy Note 3 Android Development] Al-Bcherrany:
Hello Chris, the first command didn't work but the second one did.. Dk just check it if that's it
[Galaxy Note 3 Android Development] chris8189:
Thanks, appreciate it. All you have to do is highlight all of the text in command prompt and then paste it into a notepad file. Then upload the notepad file here.

Chris
[Galaxy Note 3 Android Development] svbarbosa:
My hlte N9005 has no boot problems.

.
[Galaxy Note 3 Android Development] chris8189:
Thank you for that! Appreciate it.

---------- Post added at 11:05 PM ---------- Previous post was at 10:58 PM ----------

That's it, thanks!

The other command should work if you cut and paste the text from my post. I had the same problem initially, but it worked when I cut and paste the text in [MENTION=4899305]ashyx[/MENTION] original post on the previous page of this thread.
[Galaxy Note 3 Android Development] DJ KELL-E:
I have a T-Mobile Note 3 and I tried to install an updated oreo rom through the newest twrp, but it kept failing. So I flashed Philz touch recovery to clean the system to clean install a rom. Then I flashed twrp 2.8.7.0 zip file for the hlte in Philz touch recovery. And now recovery won't boot and its stuck in a bootloop. But I can enter download mode but I can't get it to be recognized by any computer. I've tried several cables but still nothing. I'm not sure if USB debugging was enabled before my stupid mistake. Is there any hope? Or am I out of luck. Any help will be appreciated, my father's health hasn't been good lately and I really need my phone to be dependable.
[Galaxy Note 3 Android Development] JJEgan:
This is Not the TMobile forum are you flashing TWRP for correct model .

TWRP version depends upon the rom .

See previous reply re USB debugging not needed .
[Galaxy Note 3 Android Development] DJ KELL-E:
Yes I flashed the correct one for my model. When I formatted system in Philz recovery, then flashed twrp 2.8.7.0-hlte-4.4.zip from twrp website, recovery won't boot. My charging port went out a few weeks ago, and I ordered one off of Amazon, I replaced it but it only charges and won't show up on PC. Could the charging port be faulty? Or is it something I did with flashing. Thanks for your time and help
[Galaxy Note 3 Android Development] rayman95:
the cable can be the culprit, some are only charging...
[Galaxy Note 3 Android Development] DJ KELL-E:
I have an S3 that connects with every cable. Even bought a new cable and still won't recognize it. Uninstalled Samsung drivers, reinstalled. I don't know what to try. Really don't want to have to buy a new phone. My note 3 has been the best phone ived owned. Even had it repaired from water damage last year.
[Galaxy Note 3 Android Development] LariatSoup:
I'm struggling to update my Note 3 to any TWRP 3.x from version 2.8.7. Booting into my current recovery setup I get three messages

RECOVERY BOOTING

RECOVERY IS NOT SEANDROID ENFORCING

Set Warranty Bit: recovery​

When I flash anything higher using

heimdall flash --RECOVERY twrpimage.img

I only have

RECOVERY BOOTING

Set Warranty Bit: recovery​

I've tried flashing stock using

sudo heimdall flash --APNHLOS NON-HLOS.bin --MODEM modem.bin --SBL1 sbl1.mbn --DBI sdi.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --HIDDEN hidden.img.ext4

But still have the same issue, unfortunately. I've also flashed the recommended Nordic and Italian BL and CP files, but that doesn't seem to help matters either. Flashing any images from within TWRP itself produces an ERROR=1 message when TWRP runs dd, and none of the newer ROMS I've attempted to flash have taken (Lineage, Viper, RR).

Any ideas on what I should try next?
[Galaxy Note 3 Android Development] JJEgan:
RECOVERY IS NOT SEANDROID ENFORCING

Set Warranty Bit: recovery

Yes that's valid .

TWRP flash tar file through Odin is the usual method .Or TWRP flash TWRP zip.

See multiple identical posts .
[Galaxy Note 3 Android Development] LariatSoup:
Sorry, but this isn't my issue, as I expressed in the original post. I was just providing the "Set Warranty Bit: recovery" and related messages for background in case they were relevant. My issue is that I am unable to flash newer versions of TWRP either from within TWRP or via heimdall.
[Galaxy Note 3 Android Development] JJEgan:
Not able to flash twrp zip ??

I am unable to search for your question.

Long running posts on same subject.
[Galaxy Note 3 Android Development] LariatSoup:
The issue is that flashing any 3.x twrp image just causes a bootloop (via heimdall/ODIN). When I flash using a twrp zip file (I have to create my own zips from the images on the twrp website, as there are no 3.x zips available on there) I get the same result. Strangely, I also get the boot loop when flashing twrp-2.8.7.0-hlte-4.3.img. It's only twrp-2.8.7.0-hlte-4.4.img that takes.

Flashing images from inside twrp gives ERROR=1.
[Galaxy Note 3 Android Development] JJEgan:
See multiple identical posts .

poster CHRIS8189 kicked it off .
[Galaxy Note 3 Android Development] LariatSoup:
Sorry about that! I completely missed this. Obviously the issue isn't fixed, but CHRIS8189's posts ended up sending me to the Lord_Eko RR rom, which is working wonderfully so far.
[Galaxy Note 3 Android Development] chris8189:
[MENTION=9327710]LariatSoup[/MENTION] - The last fifteen or so pages of this thread have been exactly about the issue that you are having. As [MENTION=3095420]JJEgan[/MENTION] states, I was the one that originally raised the subject. It seems that some of us with these phones are unable to flash the later TWRP's, due to some fundamental issue with the kernel on our phones. At this moment in time, the matter still remains

UNSOLVED

.

Chris
[Galaxy Note 3 Android Development] chris8189:
[MENTION=4899305]ashyx[/MENTION]

I have been inactive for a few weeks as I've been away on holiday, so haven't really had the chance to contribute anything on here. So now I'm back, I have now had the chance to firstly take a look at the partition text files that [MENTION=3342533]svbarbosa[/MENTION] and [MENTION=7421535]Al-Bcherrany[/MENTION] kindly uploaded at my request.

I have used snip tool on my PC and created a JPEG image that shows only the lines that differ between mine, svbarbosa's and Al-Bcherrany's. They start to differ toward the bottom of the list of partitions, starting at number 25.

Now I don't know what to make of this myself. These partitions and numbers relating to their size mean nothing to me, but maybe you can help.

Thanks as always.

Chris
[Galaxy Note 3 Android Development] chris8189:
And now with the devblock files.

I have saved a copy of [MENTION=3342533]svbarbosa[/MENTION] dev block file in text format, and have re-uploaded it to this post, as well as my own dev block text file. I have cross compared them myself, and again, there are differences, but again, the numbers and text mean nothing to me so I don't know how to interpret the data. Could I also kindly ask you take a look at these as well.

Thanks,

Chris
[Galaxy Note 3 Android Development] LariatSoup:
I will take a look! Unfortunately, I don't have much Android dev knowledge and so the chances of me being able to figure this out are minimal. I will post feedback soon.

On an unrelated note. I tried the Resurrection Remix 5.8.2 build that you mentioned. Unfortunately, whilst it was working well for the first two times I booted it up, I get stuck in a bootloop after that. This seems to be an issue with some phones and RR, but I'm not sure what to switch to due to our "unique" situation. Have you experienced any similar issues? I flashed stock and tried reloading RR with the same issue.
[Galaxy Note 3 Android Development] chris8189:
Hi,

I can confirm that I have never experienced any issues flashing Lord Eko's v5.8.2 build of RR. I have flashed it time and time again, without issue.

I also appreciate you taking the time to look into the differences between my dev block and partition, compared with the others.

Chris
[Galaxy Note 3 Android Development] LariatSoup:
I see! Which version of magisk did you flash with it?
[Galaxy Note 3 Android Development] ashyx:
If these are the only differences I can't see these having any relevance.

mmcblk0p25 is the hidden (preload) partition. Usually contains mostly useless stuff like permanent apps. Can be wiped and won't cause an issue.

mmcblk0p26 is the user data partition, only minor differences there in the size, not sure why though?

mmcblk1/mmcblk1p1 is the micro sd card.

The only real difference is the mmcblk0rpmb partition. This partition contains some data that cannot be overwritten (keys etc) Seems strange that there is a difference in size, which says to me they contain different data.
[Galaxy Note 3 Android Development] chris8189:
Magisk v16.

---------- Post added at 09:11 AM ---------- Previous post was at 09:06 AM ----------

Thanks [MENTION=4899305]ashyx[/MENTION]

As you correctly point out, mmcblk0rpmb (the eMMC partition) is the most noticeable difference. Mine being '4096' in size, where svbarbosa's and Al-Bcherrany's both being '512' in size. Pretty alarming! Could this be the root cause of the problem, where upon trying to boot TWRP recovery, the kernel is trying to read the mmcblk0rpmb eMMC partition, and times out, due to its size, causing the boot loops? Just a theory. Would there be a way to repartition it to 512 in size like theirs, or would it be easier to ask [MENTION=3342533]svbarbosa[/MENTION] or [MENTION=7421535]Al-Bcherrany[/MENTION] to create a TWRP backup of their device, freshly wiped and upload it here, and then I can transfer their backup to my device and restore their backup in TWRP, which would effectively sort out all of the partitions out on the phone? I don't know if this is possible though.

Or, could it be possible that the partition table is corrupt or, given that this device is now over 4 years old, the internal storage chip that holds all of the eMMC and partitions has failed? Maybe Samsung plants a used time trigger into their chipsets to fail after a period of a few years?

Chris
[Galaxy Note 3 Android Development] Chinaboy5216:
TWRP 3.2.3.0 HLTECHN RRO 6.1.0 [MENTION=942201]vidwhal[/MENTION] flash ok (coming from TWRP 3.2.2.0 HLTE)

After flash rebooted to TWRP
[Galaxy Note 3 Android Development] Muhammad Zubair:
need 2.8.7.0

Help...

Hello guys

I have installed version 2.8.7.0 on my galaxy note 3 verizon (SM-N900V) 5.0 lollipop for this rom and its file name was twrp-2.8.7.0-hlte-4.4. it got flashed in a minute.

Later on when i restart into recovery it shows an error something like "recovery is not seandroid enforcing. ..."

Then me have to install stock firmware using odin .

2 times i have faced this problem

Infact i would like to install aryamod port s7edge rom in galaxy note 3 sm-N900v

I NEED 2.8.7.0 TWRP FOR THIS ROM,

I HAVE ROOTED MY PHONE TWO TIMES