Develop Bugs

Messed Up OnePlus 3 (NEED HELP PLEASE)

Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!

You should try Fastboot EDL. search Google. Good luck

scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app

Try reflashing stock firmware with fastboot.

fast69mopar said:
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Windows wont install the drivers on the thread so i cant proceed and the next available date for Oneplus tech is July 24th this is so urgent....any other options?

Nv1dia said:
Try reflashing stock firmware with fastboot.
Click to expand...
Click to collapse
I cant because says flashing isnt allowed

scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Anybody?? Please help

scottwitha5 said:
Anybody?? Please help
Click to expand...
Click to collapse
Update: I followed the Mega Unbrick Guide for a hard bricked Oneplus 3, and now instead of even starting android, this appears, and I cant get into recovery or flash anything because it isnt allowed....please help me

I think your error was to relock the bootloader because if it was still unlocked, you could still reflash the boot.img (but your relocked your bootloader)

Solving it.
Don't worry I shall help you.
This happened to me too.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
To get the drivers and adb along with twrp and root use this toolkit.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Get the Oneplus drivers through this too.
It's not very complicated but ask me for any help.
Use the Method 2 in the Mega UnBrick Guide and download the stock image on to it.
You will lose data all of it.!
Make it boot.
Then tick OEM unlocking
Unlock bootloader through the toolkit.
flash twrp and root done..!!.
You messed up when you ticked off OEM unlocking and fastbooting it.

various issues with google variant

I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?

I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.

stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:

I agree. I got it used tho which is an issue.

Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.

stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.

Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.

Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?

stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.

Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.

I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.

MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:

stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.

smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.

Honor 7X L21 99% Factory Reset Lowlevel

Regarding to title, I was trying to flash a custom rom on my Honor 7X but apparently with the crazy amount of idk twrp recoveries and failed flashes, the phone (totally empty with both system and data) decides to factory reset lowlevel after i try to fastboot oem relock bootloader and it stays stuck at 99%. Any troubleshooting tips would be great.

Well, am experiencing similar problems.
I was on rooted Stock, when I got a System update available prompt.
I uninstalled Magisk, Flashed stock recovery and did a Factory reset from the Stock recovery.
It booted up, but there was no Keyboard installed. I think, I had uninstalled the pre-installed one when I was rooted.
I couldn't get past the Setup Wizard, as the FRP was Locked and there was no way of typing the password.
I tried to flash the system.img from fastboot but it gave me 'Remote: command not allowed' error. (Even for flashing recovery)
I google'd a bit and ended up on a solution as to relock the bootloader, Turn on OEM Unlocking and lock the bootloader again.
I relocked the bootloader, it did a 'Low-level factory reset' and now the phone is even bootloop. (it boots into eRecovery from the Honor/Huawei logo)
I tried the 'Download latest version and recovery' from eRecovery. It's giving me 'Package verification failed' error.
'dload' method never worked for me, and it is still the same.
Any solution/suggestion?

Bootloader relock with empty system is a definite hard brick.
I think you may need to ues dload method and flash a service rom to get back up and running.

dload says software install failed, any ideas? @mrmazak

apparently now its back to usual after leaving it stuck at 99% overnight until the battery dies out, could go back to fastboot and stuff

How far did it get? Stop and fail at 5% happens when update not found or not correct update.app.
Of it loads higher that 5% then fails , that's probably not gonna be able to fix it.
We have only found 2 service roms. Both are bnd-l21c432 one is Nougat one is Oreo. Both have been used on other versions of honor 7x. But after it runs you need to run hurupdater or hwota with correct model / region fullOTA.

Samsung j610fn stuck in bootloop even after nand erase and pit flash, please help !

Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.

stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.

stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk

Try to flash latest rom

Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done

alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk

Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.

alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk

Unable to boot phone once TWRP installed?

Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.

KiwiNote+ said:
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
Click to expand...
Click to collapse
i am guessing try ADB commands see this link! https://www.koskila.net/how-to-use-twrp-to-flash-an-android-device-that-refuses-to-boot-to-twrp/

Many N975 users have reported this issue and I have forwarded concerned to ian as well. What I believe is formatting on latest (last few) twrp causing issue.
If you have N975/N976 then, visit xda My rom thread - Download area - you will find a folder "for stock rom & bootlooped device" download instructions and follow it, I have wrote guide with or without flashing my rom
Edit :
here is direct link, you will find all required file
https://www.mediafire.com/#0urfw8g1gx630
This guide is stop solution to root/root with twrp/fix Samsung roll back bootloop everything. And yes you don't needs to patch anything yourself, all files available are ready to use

Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.

KiwiNote+ said:
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
Click to expand...
Click to collapse
Yes, As I said issue is related to newer TWRP only. If you use old TWRP, camera will not work. My above link guide is for latest base and you can get latest TWRP only (Included package are having latest available TWRP & Kernel)