Database Users

Cannot install any custom ROM

Hi,
I've got a SM-T531 tablet and I hate the official ROMs. They're bloated and ugly. I searched around and found 2 custom ROMs which I would love to try out. I have flashed ROMs on my previous devices but never had any issues. Here's what I have done:
First I have flashed CF-Autoroot using Odin and it was successful. I could install apps with root permission, it was all good.
Then I wanted to install a custom ROM. I followed the instructions in this link:
http://forum.xda-developers.com/tab-4/development/rom-blisspop-3-1-t3084757
I downloaded the latest TWRP:
https://www.androidfilehost.com/?w=files&flid=40746
The ROM:
https://www.androidfilehost.com/?w=files&flid=40978
GApps (I downloaded the SOKP-Mini-Gapps.L5.1.1-R-1.0-20150801.zip file):
http://downloads.sonic-developers.com/gapps/
Then used ODIN to flash the TWRP file, it was successful. Next I used the "Home+Volume Up+Power" to go to the recovery mode. After that I cleaned (Factory Reset) and used the "Install ZIP" to flash the ROM and then GApps. All finished without any issues.
But when I reboot I get the following error (same colors):
kernel is not seandroid enforcing
set warranty bit : kernel
Click to expand...
Click to collapse
It stops there and never goes to any boot screen. Just freezes.
It's the same with the ROM mentioned in the following link:
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
Note: When I flashed the stock firmware, the tablet boots perfectly fine. But when I try to install custom ROMs I get this.
I have never seen this error before. What am I doing wrong?
I would appreciate any kind of help. Thanks in advance.

Believe it or not, "kernel is not seandroid enforcing set warranty bit : kernel" isn't an error, it's just what shows up whenever you boot after flashing a custom rom. It's perfectly normal.
You messed something else up. In order to successfully flash a custom lollipop rom, you have to update to official lollipop first. Go to this thread: http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844 and download any of the SM-T531 files and flash it through Odin. Then root with this method: http://forum.xda-developers.com/showpost.php?p=61421937&postcount=4
Second, use BlissPop, which is current, not the other cyanogenmod you linked to, which is out of date and no longer supported. Just to be safe I'd also recommend trying TK Gapps: http://forum.xda-developers.com/android/software/tk-gapps-t3116347

Thanks for the quick reply. Quick and at the same time, very informative. Let me download these, flash them and then get back to you. Hopefully it will solve my problem.

Thanks again. I did what you suggested and everything's working perfectly. Thanks again.

Lg g2 no os at all

Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)

If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC

Spumpkin said:
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
Click to expand...
Click to collapse
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk

renzo090513 said:
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
cm11 => jb bootloader
cm12, cm12.1 and cm13 => kk bootloader

klemenSLO said:
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Click to expand...
Click to collapse
The current version is 2.8.7.3. Should I try other versions?

Did you solve the issue? Or is it still not allowing you to get into your F/W?

staylecrate said:
Did you solve the issue? Or is it still not allowing you to get into your F/W?
Click to expand...
Click to collapse
Hi!
I tried to install TWRP version 2.6.6.3, but it fails to flash it so I'm stuck with the version 2.8.7.3. All I'm able to enter is just the recovery mode. I can't enter the download mode so I can't flash the stock firmware.
Currently I'm out of ideas. I can't flash any OS, the TWRP fails everytime and creates errors.

Try flash bumped kernel like lp dorimanx then flash bumped bootstak then lp rom like cloudy or stock. Or google this: lg g2 unbrickable now xda ...that work for me

What ROM can I install on my NEO?

Hello,
do you know if I can install the following ROM downloaded from this site (CM13):
http://www.cyanogenmods.org/forums/...od-13-marshmallow-rom-gt-i9300i-i9301i-i9301q
Otherwise do I have to install only ROMs that came from cyanogenmod.org (CM 12.1)?
https://webcache.googleusercontent.....org/?device=s3ve3g+&cd=1&hl=it&ct=clnk&gl=it
(I used a cached link because at the moment the site is offline)
Thank you.

tramsss said:
Hello,
do you know if I can install the following ROM downloaded from this site (CM13):
http://www.cyanogenmods.org/forums/...od-13-marshmallow-rom-gt-i9300i-i9301i-i9301q
Otherwise do I have to install only ROMs that came from cyanogenmod.org (CM 12.1)?
https://webcache.googleusercontent.....org/?device=s3ve3g+&cd=1&hl=it&ct=clnk&gl=it
(I used a cached link because at the moment the site is offline)
Thank you.
Click to expand...
Click to collapse
CM 12.1 Official
Download: https://dl.dropboxusercontent.com/u/17361181/cm-12.1-20161031-NIGHTLY-s3ve3g.zip
CM13 is not stable to normal use.

Mr.gRisáK said:
CM 12.1 Official
Download: https://dl.dropboxusercontent.com/u/17361181/cm-12.1-20161031-NIGHTLY-s3ve3g.zip
CM13 is not stable to normal use.
Click to expand...
Click to collapse
Thank you for your reply. I tried several ways to flash Cyanogen to my (non rooted) phone but none worked!
I first followed this guide and I tried to flash it using Android recovery, but I get the following error:
E:footer is wrong
E:signature verification failed
Then I tried to follow this guide, both from Windows 7 and Linux, but the terminal hangs on <waiting for device> message when i run fastboot command, from both operating systems. Here I tried to install several drivers (Samsung, Google and so on...) and even tried to follow all the possible ways, including linux settings, to get rid of that error: none worked.
Finally, I tried this guide and I flashed several files: latest TWRP version, some old TWRP versions and even CWM recovery. None worked. The flash is done with no errors, but when I try to go in Recovery Mode I always get the Android recovery.
What the hell is wrong with my phone?
Thank you!

tramsss said:
Thank you for your reply. I tried several ways to flash Cyanogen to my (non rooted) phone but none worked!
I first followed this guide and I tried to flash it using Android recovery, but I get the following error:
E:footer is wrong
E:signature verification failed
Then I tried to follow this guide, both from Windows 7 and Linux, but the terminal hangs on <waiting for device> message when i run fastboot command, from both operating systems. Here I tried to install several drivers (Samsung, Google and so on...) and even tried to follow all the possible ways, including linux settings, to get rid of that error: none worked.
Finally, I tried this guide and I flashed several files: latest TWRP version, some old TWRP versions and even CWM recovery. None worked. The flash is done with no errors, but when I try to go in Recovery Mode I always get the Android recovery.
What the hell is wrong with my phone?
Thank you!
Click to expand...
Click to collapse
What version of S3 Neo do you have ?
I9300I , I9301I ??
Maybe try install original samsung rom with odin and then install again TWRP with odin.

My phone is I9301I.
If i follow your hint, can I flash the latest version among these?
Do you have any other suggestion for flashing the whole ROM with Odin?
(it would be my first time...)
Thank you in advance for your support!

tramsss said:
My phone is I9301I.
If i follow your hint, can I flash the latest version among these?
Do you have any other suggestion for flashing the whole ROM with Odin?
(it would be my first time...)
Thank you in advance for your support!
Click to expand...
Click to collapse
For first time You must register on sammobile (official samsung site).
And try download original ROM from: https://www.sammobile.com/firmwares/database/GT-I9301I/ (official site) and just select your country.
http://odindownload.com/download/Odin3_v3.12.3.zip <--- odin
https://www.youtube.com/watch?v=UBU4MFYiu_I <---- Instruction how to use odin
If everything going to be okey try again install cm12.1
TWRP with odin ---> https://forum.xda-developers.com/showpost.php?p=56085899&postcount=2 2nd Method !
1. Download the ROM = https://dl.dropboxusercontent.com/u/17361181/cm-12.1-20161031-NIGHTLY-s3ve3g.zip
2. Download GAPPS = http://opengapps.org/ my best opinion is ARM 5.1 PICO
3. Transfer the zip files to your SD card
4.. Reboot to recovery mode ( Vol UP + Home + Power )
5. Wipe data / Factory Reset
6. Install CM zip and GApps zip
7. Reboot to system
Enjoy! :fingers-crossed:

I'm downloading the file I9301IXCUAPH1_I9301IITVAOL1_ITV.zip from your link (I have registered an account).
Meanwhile, please tell me: isn't the link I posted before safe?

Mr.gRisáK said:
For first time You must register on sammobile (official samsung site).
And try dowonload from: https://www.sammobile.com/firmwares/database/GT-I9301I/ official site just select your country.
http://odindownload.com/download/Odin3_v3.12.3.zip <--- odin
https://www.youtube.com/watch?v=UBU4MFYiu_I <---- Instruction how to use odin
If everything going to be okey try again install cm12.1
TWRP with odin ---> https://forum.xda-developers.com/showpost.php?p=56085899&postcount=2 2nd Method !
1. Download the ROM = https://dl.dropboxusercontent.com/u/...TLY-s3ve3g.zip
2. Download GAPPS = http://opengapps.org/ my best opinion is ARM 5.1 PICO
3. Transfer the zip files to your SD card
4.. Reboot to recovery mode ( Vol UP + Home + Power )
5. Wipe data / Factory Reset
6. Install CM zip and GApps zip
7. Reboot to system
Enjoy! :fingers-crossed:
Click to expand...
Click to collapse
All went fine! Thank you sooo much!
PS: CM12.1 has wrong link.

tramsss said:
All went fine! Thank you sooo much!
PS: CM12.1 has wrong link.
Click to expand...
Click to collapse
Sorry my fault! :crying:
Now works :highfive:
You are welcome ! :fingers-crossed:

Rooted, Custom Rom a huge fail

Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?

Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke

mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.

Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?

Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.

Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.

AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp

AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.

AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes

[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)