Database Users

[Q] Stuck in boot animation when loading ROMS [SOLVED]

Just purchased a Razr M coming up from a Droid X2. First thing I did was head over here to grab a ROM to escape the Verizon bloatware.
So here is where I'm at right now.
-Rooted with MotoFail2Go and replaced the SU & Superuser.apk since original program wasn't rooting
-Root confirmed with Root Checker
-Installed SafeStrap3 3.12 with elevated permissions.
-Installed recovery
-Rebooted into SS3, backed up current state as a CYA precaution and partitioned a ROM slot to test drive a ROM
-ROM (ECLIPSE) installs successfully, reboot system.
-Boot animation comes up for a bit and I figured ok I'll just let it do what it has to do to set itself up for the first time. 30 min and still stuck on boot animation
-Cleared partition and tried again and same result.
-Cleared and tried with a different ROM (BDH) and again same result.
Not finding any solutions online or users with similar experiences. Wondering if anybody had any input here.
*Edit- I just do want to note that it is a stock out of box device. Ive tried taking the updates before rooting but I get about 25% in and it fails.
**EDIT 2- Loaded the 4.1.1 update posted here that was failing. ROM booted up with no issues.

[Q] Flashing 4.3plus then Freezing

My Tegra Note 7 came with Android 4.2. I unlocked, rooted, and installed CWM via the instructional videos over at rootjunky.com. Then through CWM I installed De-Odexed Stock Rooted 4.3plus from this thread: http://forum.xda-developers.com/showthread.php?t=2627671
Once the install finished and I rebooted the device (the reboot took maybe 30-45 seconds) I came to the setup "Welcome" screen. It is here that the Tegra Note froze. I thought it may be because it takes upwards of ten minutes for the first boot to complete/install but 30 minutes later the screen is still frozen.
When I do a hard reboot a few times I'm able to make it through the welcome and setup screens and the device appears to work just fine. I'll be able to install apps, run the stylus software, etc but then every 5 or 6 minutes (maybe shorter, maybe longer) the device freezes again and I must do another hard reboot. This happens repeatedly. And I still can't use the device for more than a few minutes.
Any ideas/suggestions?

onyxkhan said:
My Tegra Note 7 came with Android 4.2. I unlocked, rooted, and installed CWM via the instructional videos over at rootjunky.com. Then through CWM I installed De-Odexed Stock Rooted 4.3plus from this thread: http://forum.xda-developers.com/showthread.php?t=2627671
Once the install finished and I rebooted the device (the reboot took maybe 30-45 seconds) I came to the setup "Welcome" screen. It is here that the Tegra Note froze. I thought it may be because it takes upwards of ten minutes for the first boot to complete/install but 30 minutes later the screen is still frozen.
When I do a hard reboot a few times I'm able to make it through the welcome and setup screens and the device appears to work just fine. I'll be able to install apps, run the stylus software, etc but then every 5 or 6 minutes (maybe shorter, maybe longer) the device freezes again and I must do another hard reboot. This happens repeatedly. And I still can't use the device for more than a few minutes.
Any ideas/suggestions?
Click to expand...
Click to collapse
I am having the same issue my Tegra Note keeps freezing after flashing either update, I only did this because the ota update was not hitting but now the tablet is unusable

Fixed
RimanX said:
I am having the same issue my Tegra Note keeps freezing after flashing either update, I only did this because the ota update was not hitting but now the tablet is unusable
Click to expand...
Click to collapse
I was able to finally fix mine and stop the freezing and locking up. What I had to eventually do was reflash the stock 4.2.2 image, reflash the stock recovery and then update as usual OTA and now I have an updated EVGA TN7 fully functional. Thankfully this forum helped a lot by having the resources needed to fix the issue.

RimanX said:
I was able to finally fix mine and stop the freezing and locking up. What I had to eventually do was reflash the stock 4.2.2 image, reflash the stock recovery and then update as usual OTA and now I have an updated EVGA TN7 fully functional. Thankfully this forum helped a lot by having the resources needed to fix the issue.
Click to expand...
Click to collapse
How did you flash the 4.2.2 image and the stock recovery?

Freeje said:
How did you flash the 4.2.2 image and the stock recovery?
Click to expand...
Click to collapse
Have to get into the bootloader which for some reason mine is still just a blank black screen even though it says it's unlocked. I used a program called Quick Boot which is mentioned in one of the tut videos, it took a while because of the freezing but once I had it installed I used it to boot back into recovery and bootloader. I did this because the method of holding down power and vol up was not working.
I also noticed that as long as you are moving the screen around with your finger on any screen it would not lock up. I used this to transfer the stock image and recovery over from my computer using the usb.
Once in bootloader you use fastboot to flash. ex. fastboot flash recovery stock_recovery.img from the windows cmd prompt.
I had CWM recovery flashed when this first started so I used Quick Boot to go into recovery to flash the stock 4.2.2 image first to even see if it would help the freezing and once it did I went back and did the above to flash stock recovery so I could let the tablet update using OTA updates.

RimanX said:
Have to get into the bootloader which for some reason mine is still just a blank black screen even though it says it's unlocked. I used a program called Quick Boot which is mentioned in one of the tut videos, it took a while because of the freezing but once I had it installed I used it to boot back into recovery and bootloader. I did this because the method of holding down power and vol up was not working.
I also noticed that as long as you are moving the screen around with your finger on any screen it would not lock up. I used this to transfer the stock image and recovery over from my computer using the usb.
Once in bootloader you use fastboot to flash. ex. fastboot flash recovery stock_recovery.img from the windows cmd prompt.
I had CWM recovery flashed when this first started so I used Quick Boot to go into recovery to flash the stock 4.2.2 image first to even see if it would help the freezing and once it did I went back and did the above to flash stock recovery so I could let the tablet update using OTA updates.
Click to expand...
Click to collapse
From where did you get the 4.2.2 image that you can flash from stock recovery? I have a problem of getting the 4.3+ installed since I flashed the CWM recovery. I tried flashing a stock recovery but failed every time. My question is, would flashing an earlier ROM such 4.2.2 enable me to get the 4.3+ update or do I still have to flash a stock recovery?

Got the same error after flashing 4.3 or 4.4.2 manually (since OTA halts with an error).
How to get rid of it?
Thanks!

4.3/4.4 crash. I fixed mine finally! 4.4 working great, no crashing!
astuermer said:
Got the same error after flashing 4.3 or 4.4.2 manually (since OTA halts with an error).
How to get rid of it?
Thanks!
Click to expand...
Click to collapse
I had the exact same problem as you... I finally got it working, up to date with 4.4 CWM recovery, rooted and sd card fix. All working great... but here's some history...
I had the same bootloader that never worked from Power on/Vol Up, but would work after an adb reboot into fastboot. (blank screen only)
I was on stock 4.2.2, then unlocked bootloader, then updated to 4.4 using Supertool 2.2, Root, Sd card fix, but stock recovery still. All installed fine, but I had the crashing problem. Factory reset, and reinstall.. didn't solve the problem.
So I went back to 4.2.2 using the "temp" cwm recovery (using the root option to get in the cwm recovery, but I flashed the 4.2.2 file from root junky web page instead of rooting)
So here I was at 4.2.2 stock (from rootjunky web site), and stock recovery. Still not bootloader screen from Power.Vol up.
4.3 OTA would not work (dead droid with red triangle,error),
So I used supertool 1.5, installed CWM recovery, then I installed 4.3. It worked and rooted automatically, but I still got the crashing, and no bootloader by Power/VolUP. 4.4 OTA wouldn't work even when I put stock recovery back.
Here's where I got it to work from 4.3 stock (with crashing still happening, blank bootloader):
So now I used Supertool 2.2 to flash its version of CWM recovery (I had to keep touching the screen to keep it from crashing until CWM was installed and rebooted).
I did NOT use Supertool 2.2 to flash 4.4 as it contains the OTA 2.1 with it!!! (We don't want that yet! You'll se why below) I copied the 4.4 file at rootjunky: "Stock-4.4.2-TegraNote7.zip, February 22nd 2014 460 MB" onto the internal sd card (NOT the external sd card)
I used adb commands to reboot tablet into cwm recovery (had to keep touching screen until it rebooted into recovery so it wouldn't crash). Then I flashed the above 4.4 file. Install went fine. Of course I I still had crashing with 4.4 stock again. However, I noticed that the OTA 2.1 update appeared! I tried to update, but of course it wouldn't with CWM installed. So I reflashed recovery back to stock using supertool 2.2
Guess what happened next? The OTA 2.1 downloaded, flashed and worked! This was the first time I was ever able to get ANY OTA update to work! The key was to flash a stock 4.4 that didn't contain the OTA 2.1, and have stock recovery (from supertool 2.2) first in order to allow the OTA 2.1 to install!
Guess what works now? 4.4 works with NO CRASHING! and my bootloader finally works by holding Vol Up and Power ON and fully function menus,etc..!!! The tablet runs beautiful! The 4.4 had no root, or sd card fix applied, and stock recovery, but it DID lock the bootloader!
So now I used supertool 2.2 to unlock the bootloader (which I could now do because my bootloader had working menus, and could be accessed by Power/Vol Up). Keep in mind that this does a factory reset and wipes user data. (I had not wiped ANY user data right from 4.3 up until now!)
After the bootloader unlock/factory reset, I then used supertool 2.2 to: install CWM recovery, install root, install sd card fix.
Now I have an EVGA Tegra Note 7 with a fully functional bootloader, 4.4 Kit Kat, CWM recovery, root, sd card fix. All running great with NO crashing!
This is what worked for me... proceed with caution and know what your are doing first. Good luck!

4.4.2 Freezing- FIXED!
TerryRed said:
I had the exact same problem as you... I finally got it working, up to date with 4.4 CWM recovery, rooted and sd card fix. All working great... but here's some history...
I had the same bootloader that never worked from Power on/Vol Up, but would work after an adb reboot into fastboot. (blank screen only)
I was on stock 4.2.2, then unlocked bootloader, then updated to 4.4 using Supertool 2.2, Root, Sd card fix, but stock recovery still. All installed fine, but I had the crashing problem. Factory reset, and reinstall.. didn't solve the problem.
So I went back to 4.2.2 using the "temp" cwm recovery (using the root option to get in the cwm recovery, but I flashed the 4.2.2 file from root junky web page instead of rooting)
So here I was at 4.2.2 stock (from rootjunky web site), and stock recovery. Still not bootloader screen from Power.Vol up.
4.3 OTA would not work (dead droid with red triangle,error),
So I used supertool 1.5, installed CWM recovery, then I installed 4.3. It worked and rooted automatically, but I still got the crashing, and no bootloader by Power/VolUP. 4.4 OTA wouldn't work even when I put stock recovery back.
Here's where I got it to work from 4.3 stock (with crashing still happening, blank bootloader):
So now I used Supertool 2.2 to flash its version of CWM recovery (I had to keep touching the screen to keep it from crashing until CWM was installed and rebooted).
I did NOT use Supertool 2.2 to flash 4.4 as it contains the OTA 2.1 with it!!! (We don't want that yet! You'll se why below) I copied the 4.4 file at rootjunky: "Stock-4.4.2-TegraNote7.zip, February 22nd 2014 460 MB" onto the internal sd card (NOT the external sd card)
I used adb commands to reboot tablet into cwm recovery (had to keep touching screen until it rebooted into recovery so it wouldn't crash). Then I flashed the above 4.4 file. Install went fine. Of course I I still had crashing with 4.4 stock again. However, I noticed that the OTA 2.1 update appeared! I tried to update, but of course it wouldn't with CWM installed. So I reflashed recovery back to stock using supertool 2.2
Guess what happened next? The OTA 2.1 downloaded, flashed and worked! This was the first time I was ever able to get ANY OTA update to work! The key was to flash a stock 4.4 that didn't contain the OTA 2.1, and have stock recovery (from supertool 2.2) first in order to allow the OTA 2.1 to install!
Guess what works now? 4.4 works with NO CRASHING! and my bootloader finally works by holding Vol Up and Power ON and fully function menus,etc..!!! The tablet runs beautiful! The 4.4 had no root, or sd card fix applied, and stock recovery, but it DID lock the bootloader!
So now I used supertool 2.2 to unlock the bootloader (which I could now do because my bootloader had working menus, and could be accessed by Power/Vol Up). Keep in mind that this does a factory reset and wipes user data. (I had not wiped ANY user data right from 4.3 up until now!)
After the bootloader unlock/factory reset, I then used supertool 2.2 to: install CWM recovery, install root, install sd card fix.
Now I have an EVGA Tegra Note 7 with a fully functional bootloader, 4.4 Kit Kat, CWM recovery, root, sd card fix. All running great with NO crashing!
This is what worked for me... proceed with caution and know what your are doing first. Good luck!
Click to expand...
Click to collapse
@TerryRed:
You saved my bacon! I was having a similar issue with a totally borked root attempt... I was frustrated with repeated attempts to recover from the freezing issue. I followed your instructions and recovered the Tegra. Like you, I discovered that if I continually the device active by tapping and moving the screen, I could use the device. My idle limit was about 5 seconds, though.
In a nut shell, and while pretending to be a poor excuse for DJ 'scratching' (or do they call them 'controllerists' now?) I:
* Made sure ADB Debugging was enabled
* Copied the 'Stock-4.4.2-TegraNote7.zip' archive to the device's internal storage
* Ran SuperTool 2.2 and ONLY flashed the stock recovery
* Rebooted
[Resume silly DJ motions, while frantically setting up WIFI]
* Checked for, and downloaded the OTA update manually [OTA FOUND!!!]
* Waited the agonizing 10 second countdown for the device to initialize the installation
* Let Android do it's thing
!! SUCCESS !!
Thank you, and all of the guys here at XDA who donate their time, talent, and valuable info that help us mere muggles free our devices and take them to new heights.

I bricked my while trying to get back to 4.3 and I really hope that this will still help me after all I've already done. Wish me luck(

Bricked as well
OrangeCalculator said:
I bricked my while trying to get back to 4.3 and I really hope that this will still help me after all I've already done. Wish me luck(
Click to expand...
Click to collapse
So yours bricked as well???
I had the same problems:
- Bootloader not working as expected (only black screen).
- After CWM and flashed 4.3 constantly freezing.
- OTA not working (it said something like "This is not Tegra Note, it is Tegra Tab")
So being desperate I flashed a deodex 4.3 from RootJunky's web.
Since then tablet in boot-loop and still no way to get into Recovery.
I can only access APX mode, but I am not sure, how to use it.
Any help appreciated.
Jaro

NVflash unbricked
jardam.cz said:
So yours bricked as well???
I had the same problems:
- Bootloader not working as expected (only black screen).
- After CWM and flashed 4.3 constantly freezing.
- OTA not working (it said something like "This is not Tegra Note, it is Tegra Tab")
So being desperate I flashed a deodex 4.3 from RootJunky's web.
Since then tablet in boot-loop and still no way to get into Recovery.
I can only access APX mode, but I am not sure, how to use it.
Any help appreciated.
Jaro
Click to expand...
Click to collapse
So, to fix the boot loop it is as simple as it can be. I can't believe I didn't find that earlier. (BTW I didn't find a clear answer in the forum until today, thanks to hacktrix2006)
Just download the NVflash and the image mentioned in post #2 in following thread. Follow the instructions to switch tablet into APX mode, install the driver and start the flashing. Flawlessly done. No problem. Got rid of the Chinese OS (not supporting Google).
Really cool!

Just in case anyone still has these issues I'm going to post how I found a way to resolve them. I had all the problems mentioned in the previous posts and more besides. The inability to apply OTA updates, the device would freeze after 5 seconds of inactivity, endless boot loops, failed recovery partitions etc etc etc.
I tried a butt load of different solutions but none worked for me. What did work is described below. Others have already mentioned that Advent has a stock rom recovery utility, however, even after flashing that my problems still remained. So I downloaded the Advent stock recovery util and documentation and modified it slightly to the latest Android release for the Tegra Note 7.
Do as follows:
1 - Go here and download both the Advent Vega Tegra Note Factory Image (4.3) util and the documentation.
2 - Extract the Advent Factory Image zip file (as described in the documentation) somewhere on your pc.
3 - Inside the extracted folder you'll see a bunch of files. The three files we're interested in are the "recovery.img", "system.img" and "boot.img". Select all three and delete them.
4 - Now download the Tegra Super Tool utility here. At the time of this post the latest version is 2.5.
5 - Extract the downloaded Supertool to a new folder on your pc.
6 - Inside the extracted folder there are another bunch of files. Again, we're only interested in three of them. You're going to rename three of the files and use them to replace the three files you deleted earlier. At present their names are "4.4.2-2.5recovery.img", "4.4.2-2.5boot.img" and "4.4.2-2.5system.img.ext4". The filenames will obviously change as time goes by, but a little common sense goes a long way at this stage. So "4.4.2-2.5recovery.img" is renamed to "recovery.img", " 4.4.2-2.5boot.img" is renamed to "boot.img" and "4.4.2-2.5system.img.ext4" is renamed to "system.img". Once you've renamed them, copy them into the folder for the Advent Vega Tegra Note Factory Image which you extracted in step 2.
7 - Now go and read the documentation for the Advent Vega Tegra Note Factory Image util. Just take your time and follow it to the letter. It'll tell you how to put your Tegra Note 7 into it's APX mode, install windows drivers for it and begin the recovery of your device. It's mostly an automated procedure and fairly simple to follow as long as you follow the documentation.
This method brought my Tegra Note 7 back when it had several of the problems mentioned earlier in this thread, all at the same time.
Hope it helps someone.

Flashing a stock rom causes bootloop.

As above. While the phone technically works I cannot flash the latest stock rom (the set about unlocking, rooting, installing a custom recovery) as it loops....ive dropped back to the original stock image (4.4.4) which boots fine....I then went back up to LMY47V which loops and currently downloading KTU84 to see if that works....now just to add to all of this I was given the phone with a cracked screen which ive replaced but it came to me dead so I don't know the previous history....and thought that the advent of me fitting the screen caused it which I doubt....but the thought was there.....
The only other option if KTU84P doesn't work is to drop back to 4.4.4 and go up gradually......
Anyone else had this...?

Well, so far, nothing works apart from the stock image (tried a few other stockers) but nothing - tried installing custom recovery TWRP 3.x which installs fine....just wont boot...

Try stock flashing using Nexus root kit and check Soft bricked radio button
Sent from my Nexus 4 using Tapatalk

I'm using the Nexus Root toolkit - is that the one youre talking about ( as I cant see the "softbricked radio button") - ive got "Softbricked/bootloop" but tried that which didn't work....

I did try the original 4.4.4 image (the first one) which does boot. And then tried manually flashing the radio separately but that didn't work (but TBH I'm not sure that I did it correctly) - so, do you think its a radio issue - the reason it wont boot??

Yes, that will be the right radio button. There is only one for stock flash section. Which radio are you flashing? If its Nexus LTE zip then it's only for Lollipop ROMs 5+. Try flashing latest Lollipop stock and if it boots then flash radio. That's what I did.
If not then back to KK.
Sent from my Nexus 4 using Tapatalk

Try this: flash the latest stock ROM using fastboot commands and, after flashing the last partition, flash the userdata.img file, use the buttons to boot directly to recovery from fastboot, perform a factory wipe, and reboot.

Ok - thanks for that - haven't done the fast boot commands for a while...! ill try it now....
The other thing I noticed was the battery is draining really fast (while in bootloop) the back of it is very hot....so much so that plugged into the laptop wasn't enough to keep it running - had to transfer it to a charger....

Looking at my file I downloaded from google... (I was just about to start) I noticed I don't have the radio firmware? so, all this time while ive been reflashing and trying different images from google (stock images) ive not been flashing the radio firmware - I thought they would have included that!! am I right in thinking that's why its been bootlooping as the radio firmware is at stock (the reason why only the original base image boots)??

Well, while I was installing I flashed twrp3 as the recovery and used that when I went in to manually reset it gave me the error "cache invalid argument" - would that have any bearing??

Well, tried that and it sat there....thought id try jumping ahead a little....flashed a cm13 nightly along with a radio firmware file (a .zip) using twrp...but still the same....missing something somewhere....

I presume you have NRT installed and tried; it downloads and extracts factory images before flashing. If you are flashing latest official stock lmy48t check contents of the downloaded image. Should be
cd C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Factory_Images\occam-lmy48t-factory-416938f1
dir /b
bootloader-mako-makoz30f.img
flash-all.bat
flash-all.sh
flash-base.sh
image-occam-lmy48t
image-occam-lmy48t.zip
radio-mako-m9615a-cefwmazm-2.0.1701.07.img
Batch file that NRT runs is flash-all.bat; third line is radio flashing
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
fastboot reboot-bootloader
fastboot -w update image-occam-lmy48t.zip
Executing fastboot commands manually should achieve same result

Yep - using the wugfresh stuff tried it about a dozen times with different stock images....never had a problem like this before....

tried as you said - tried to flash manually and also tried using the bat file....still the same - flashed back to jdq39 and it boots straight back up...weird....

Can I ask silly question? Was bootloader unlocked?
Sent from my Nexus 4 using Tapatalk

If the bootloader was not unlocked, no ROM could be flashed to the phone.

Exactly. So if all fastboot commands in flash_all.bat run error free phone should boot OK. NRT runs log in a separate window so any error is easily noticeable. The only thing that comes to mind is how long it takes to boot after rom flash; I think mine took close to 20 min of bouncing balls before I saw Android logo. So may waiting for longer time will resolve it.

Yep - unlocked the bootloader (and relocked it) hoping that would shift it into life!! but no...
Ive tried the waiting game....left it on at the office at the end of the day, came back in the next day to see it still "trying to boot..."

Came across a procedure on how to pull log during bootloop. Check it out if interested. I haven't tested it. http://forum.xda-developers.com/general/xda-university/universal-test-rom-build-didnt-boot-t3258818
Sent from my Nexus 4 using Tapatalk

Yep - will do - just for the record I reflashed back to 4.2.2 relocked, booted, let the phone download a 4.3 update and flash...totally stock....just sat there.....just had a look at that link (looks promising) so I'm going to go back upto the latest build and then install twrp then flash the file to see if I can see whats going on behind....

Unable to install custom ROM - reverts to stock

Hi all - Im hoping someone can help with what I suspect is an easy issue, and me just being a bit dense.
Note 4 N910F (international)
Today, I had the motherboard replaced after eMMC failure, phone wouldnt turn on. My phone went away with Kitkat, it's come back with Marshmallow.
Now would like to re-root and re-rom to how I had it.
I've TWRP'ed successfully.
I used CF Auto Root and it worked fine, then tried to install Super SU via recovery image zip file. It sometimes says that there is no binary installed when I'm back in the Android OS.
My ROM of choice is http://forum.xda-developers.com/note-4/snapdragon-dev/rom-n910f-stock-odexed-bloated-rom-v1-t3216390 as I have used this for the past year without any issues, and had it setup as I liked it (KitKat).
I use ODIN (with phone in download mode) and installed the bootloader and the modem, then restart the phone in recovery mode, and install the ROM tried both "Download v5 ROM" and "Full Un-Debloated Stock N910FXXU1DPE1 ROM (DeKNOXed, DeOdexed, Rooted)" which I have copied to my SD Card. Neither works, one ends up in German language phone setup.
/System /Data /Cache /DalvikCache /AndroidSecure is cleared.
Phone rebooted...
....ends up back with Marshmallow after 5 minutes at the animated "Samsung" screen.
Any ideas where Im going wrong, please?

So.. about me being dense..
Yeah - I've been installing a Marshmallow ROM, then getting confused why my phone was "reverting to stock" with a Marshmallow ROM.
Obviously, that WASN'T the ROM I've been using for the past year...
derp.

[Bootloop] N9005 not booting after frame (display) replacement

Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon

Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .

I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.

Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.

I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??

Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...

What happens when you flash correct stock rom via Odin ??

I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.

AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .

I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.

AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.

Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.

after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)