Develop Bugs

Help with Samsung Galaxy

I have a Sprint Galaxy S II 4G Touch, I rooted with Odin SPH-D710.EL_29CL852097_ROOTED_NODATA program. The phone worked fine. I then tried to unroot the phone using Odin v. 1.85 twith the PIT file that came with it and the Stock_EK02.Tar file. I accidently inserted the Tar file into the BOOTLOADER, PDA AND PHONE boxes. Now my phone is stuck in the Galaxy S II screen, however I can get to Odin recovery mode. Is there anyway to reclaim any usage from my phone. Please Help...

Reboot on download mode and install one of the sfhub one click roms the el29 might need good for you.
Sent from my SPH-D710 using xda premium

By reboot I mean take the battery off put it back on hold volume down and power button at the same time then when you see a choice press volume up the install the one click roms from sfhub they are great
Sent from my SPH-D710 using xda premium

RN69 said:
I have a Sprint Galaxy S II 4G Touch, I rooted with Odin SPH-D710.EL_29CL852097_ROOTED_NODATA program. The phone worked fine. I then tried to unroot the phone using Odin v. 1.85 twith the PIT file that came with it and the Stock_EK02.Tar file. I accidently inserted the Tar file into the BOOTLOADER, PDA AND PHONE boxes. Now my phone is stuck in the Galaxy S II screen, however I can get to Odin recovery mode. Is there anyway to reclaim any usage from my phone. Please Help...
Click to expand...
Click to collapse
Download the one-click option and follow the steps outlined by sfhub. It will restore your phone to a stock out of the box state.

Reboot
When I do the reboot via battery out volume down with power button, I get a screen that has ODIN MODE in red at top left. Below that in white is PRODOCUT NAME: SPH-0710,CUSTOM BINARY DOWNLOAD: NO, CURRENT BINARY: SAMSUNG OFFICIAL. Below that the green Android robot. Below that Downloading... Do not turn target off!! No other options. The only way to install is from a file from the computer... can I install the hub file from computer and do I do with odin? The Galaxy S II screen and this reboot are the only options I can get too. Your help is greatly appreciated.

RN69 said:
When I do the reboot via battery out volume down with power button, I get a screen that has ODIN MODE in red at top left. Below that in white is PRODOCUT NAME: SPH-0710,CUSTOM BINARY DOWNLOAD: NO, CURRENT BINARY: SAMSUNG OFFICIAL. Below that the green Android robot. Below that Downloading... Do not turn target off!! No other options. The only way to install is from a file from the computer... can I install the hub file from computer and do I do with odin? The Galaxy S II screen and this reboot are the only options I can get too. Your help is greatly appreciated.
Click to expand...
Click to collapse
Sfhub's program is the easiest thing you've ever done (it's saved my bacon loads of times!). You just put the phone into download mode, plug it into your PC and then run the program you downloaded from the post I originally linked.
Good luck!

I didn't get a link... I see many sfhubs downloads. I have the rooted EL29 No data downloading EL29 Stock Root. However, I have tried the one click EL29 No data root and then phone will only boot to Galaxy screen... I am new to Android OS.. I have only been familiar with Nokia since the beginning of time. Have transformed many of those... But can always go back to factory..Clicked Thanks too.... what file do I need???

Here you go:
http://forum.xda-developers.com/showthread.php?t=1433101
Also, here is a pretty easy tutorial I wrote a while back, it includes the link above:
http://forum.xda-developers.com/showpost.php?p=24158551&postcount=9980

I have download and tried to install the SPH-D710.EL29_CL852097_ROOTED-OneClick file. It failed. This is the message odin gave me:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.bin
<ID:0/005>
<ID:0/005>
<OSM> All threads completed. (succeed 0 / failed 1)
Debugging was checked before my phone bricked. I am only able to get to Odin Download mode and the Galaxy S II screen same as before.

RN69 said:
I have download and tried to install the SPH-D710.EL29_CL852097_ROOTED-OneClick file. It failed.
Debugging was checked before my phone bricked. I am only able to get to Odin Download mode and the Galaxy S II screen same as before.
Click to expand...
Click to collapse
That's not a good sign but let's try a couple of other things.
If you have Kies installed remove/uninstall it.
Download the full Samsung driver suite and install it from here:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Try the oneclick odin again. If it still fails, try your usb cable in all the different usb ports or even try a different computer too if possible. If you have access to a different cable that would be nice to try also.

I have a Sprint Galaxy S II 4G Touch, I rooted with Odin SPH-D710.EL_29CL852097_ROOTED_NODATA program. The phone worked fine. I then tried to unroot the phone using Odin v. 1.85 twith the PIT file that came with it and the Stock_EK02.Tar file. I accidently inserted the Tar file into the BOOTLOADER, PDA AND PHONE boxes. Now my phone is stuck in the Galaxy S II screen, however I can get to Odin recovery mode. Is there anyway to reclaim any usage from my phone. Please Help...
I have tried all of the above methods in this thread. I still get the same failed status with the one click file. I have tried laptops, desktops on multiple usb ports.
still getting the same fail message,posted above.
I disabled the phone with Odin3 v. 1.85.. see above. Is there any single files to flash into the BOOTLOADER, PDA AND PHONE spaces that I originally overwrote? I also ran again with the Re-Partion box clicked. Please Help!!!

When you are in download mode, tell us exactly what text is displayed on the screen there please.
---------- Post added at 12:31 PM ---------- Previous post was at 12:20 PM ----------
Also, have you tried using odin to flash just a kernel yet?

When I do the reboot via battery out volume down with power button, I get a screen that has ODIN MODE in red at top left. Below that in white is PRODOCUT NAME: SPH-0710, then below that, CUSTOM BINARY DOWNLOAD: NO, below that, CURRENT BINARY: SAMSUNG OFFICIAL. Below that the green Android robot. Below that Downloading in white. then in green: Do not turn target off!!
I tried to flash the Tar file I stated earlier but flashed it in the wrong places. What kernal/s would you suggest flashing?
Sorry for the slow responses having issues with my Samsung Transform Ultra now too. That is what I am using for my data service on PC. I did a mandatory samsung update the other day and barnacle doesn't work, can not unroot the phone and down to usb tethered connection that is to slow, but one phone at a time. I would like to get my Galaxy back. It was great.

And on PC on the Odin screen I get:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.bin
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
and a red FAIL! box

Ok no problem.
Here is a link to an Odin guide. Not very helpful but it tells you a few necessary things and it's handy to have around if you ever need to know what the buttons are:
http://forum.xda-developers.com/showthread.php?t=1274337
Right above where it says:
DO NOT USE PHONE FOR ANYTHING BUT A RADIO/MODEM - YOU WILL DEFINITELY NOT BE ABLE TO USE YOUR PHONE FOR CALLS, AND YOU MAY POSSIBLY BRICK IT - YOU'VE BEEN WARNED
it tells you what the different keys are.
Anyway, download StockCWM-EL26.TAR from here (you may have to rename it without the MD5 to work with ODIN):
http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Repack/EL26/
Open odin, load the tar file in pda, the only 2 things should be checked are reboot and PDA, click on start.
Let me know what happens.

I got this message on the PC Odin screen when I flashed the EL-26.tar:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Removed!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Added!!
Ok, Now the phone boots into a different Galaxy screen. Now boots to Samsung Galaxy S ii GT-I9100 screen and when connected to the usb cable on restart the PC explorer shows the 2 internal mmc drives then doesn't if that makes any sense.
Then in Odin Mode on the phone has changed too. ODIN MODE in red top left. Under that in white is: PRODUCT NAME: SPH-0710, under that is CUSTON BINARY DOWNLOAD: YES (2 counts), under that CURRENT BINARY: CUSTOM... THEM THE ANDROID robot then Downloading then Do not turn off target!!

Ok cool we're making progress, now do you have any flashable rom zip files on the phone? And calkulin's format all? If so, boot up with pwr/vol up key, flash format all, then rom.
Sent from my SPH-D710 using XDA
---------- Post added at 08:22 PM ---------- Previous post was at 08:11 PM ----------
I just want you to know ahead of time , if we can get it running with a ROM, I'm going to ask you to save what you need off of the phone because I'm going to ask you to do a full reset back to stock and format everything. I want to make sure you are good to go especially due to what you did in ODIN initially so maybe this won't happen again. I will give you more instructions on that later though, let's see how this goes. Tnx.

OK when I boot with volume up/power button... I get many options... from top to bottom they are: - reboot system now, - apply update from sdcard, - wipe data/factory reset, - wipe cache partition, - install zip from sdcard, - backu and restore, - mounts and storage, - advanced, - power off...
Below that at the bottom in white I get ClockworkMod Recovery v5.0.2.7 then under:
E:Can't mount /cache/recovery/commmand
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

That's fine. Do you remember if you have any roms on the phone and are they on internal or external SD?
---------- Post added at 08:51 PM ---------- Previous post was at 08:35 PM ----------
What's up with the lag again between responses? Are you tethering the pc (no high speed internet?)

Your gonna want to download a rom and copy it over to your phone if u dont have 1.. To do so while in recovery u can goto mounts and storage mount usb.. Then u can copy and paste..after that.. Factory reset twice.. The power button is he back button home button is enter button vol up goes up vol down goes dowb.. Goto advanced options in main recovery menu and wipe dalvik cache...flash a rom and reboot..once rebooted...u need to power down and boot into download mode vol - & power.. Load sfhub el29 stock rooted and let it flash...once done..shut down..flash latest modem fe10. Go into your phone update prl and profile... Shut down..goto download mode flash el26 cwm kernel and once phone shuts off innediatelt vol + & power.. Youll boot into recovery now flash the rom of your choice im assuming first one u did in recovery and flash it.. Flash gapps and kernel if need be...u can get all the newest kernels and modems from sfhubs post abd youll want to dowoad the cwm ones to flash through recovery
Sent from my SPH-D710 using xda premium

Using ODIN to install stock rom = soft bricked phone

I wanted to install (some other rom) since I had battery drain issues with Stock 4.3 so I decided to root the phone with the MrRobinson method.
1 - I installed the Samsung drivers
2 -Set the phone to USB debugging
3 - Used volume down+menu button to go into download mode.
Then plugged the phone in and waited for the drivers to load.
Then loaded Odin, went to PDA and loaded the file for Fido (my carrier).
Fido Image
Current I747MVLDMF1 (JB 4.1.2)
Mirror 1: Download root66_FMC_I747MVLDMF1.7z
Click to expand...
Click to collapse
The check sum came back okay.
I clicked start and then this is the message log from ODIN:
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried the process a dozen times with the exact same result.
On regular boot the phone goes to a screen with "Firmware upgrade encountered issue - please select recovery mode in Kies & try again"
Kies says it can't communicate with the phone.
If I press Volume up + Menu I can't get into recovery mode, I get the same error screen as regular boot.
Help?

You have the i747 from AT&T? If you do, you cannot downgrade the 4.3 bootloader. Any attempts to flash an older bootloader will brick the phone and this seems to have happened to you.
.

Sorry wasn't clear, I have tried to root following the MrRobinson method
http://forum.xda-developers.com/showthread.php?t=1739426
Uninstalled Kies
Restarted the PC
Pulled out the phone battery for 24h.
Installed the latest drivers from Samsung
Ran ODIN 3.0.7 as Administrator
Same error on ODIN as before.
Phone says:
SV REV CHECK FAIL : Fused 1 > Binary 0
Click to expand...
Click to collapse

Do you have an i747 or i747m?

i747
Update: I went and downloaded the custom ClockWork Recovery CWM-Recovery-LTE-SGS3-V5.Tar.Md5 (http://d-h.st/am8)
Flashing this file with ODIN did work
I am able to enter recovery now by pressing volume up + menu
I put TeamEpic-Root-From-Recovery-V5.Zip (http://d-h.st/Gax) on my SD card
Booted to recovery.
In recovery>choose zip from sd card> install zip> I ran the TeamEpic-Root-From-Recovery-V5.Zip
The root worked.
I then did a factory wipe from recovery. The wipe worked and my phone has rebooted.
My phone has started working again.
I am getting a message "An attempt to access a secure area on your phone has been blocked."
Everything else is working again.

You have the 4.3 bootloader with Knox? This may explain why you got errors using Odin. The fido firmware is for the i747m, not the i747.

Bricked?

I have a problem with my Tab3. When i am in download mode all i get is this. See picture.
I had a problem that the tab always reboots into recovery. So i want to flash a stock firmware. Any ideas?

same issue.
Erik1805 said:
I have a problem with my Tab3. When i am in download mode all i get is this. See picture.
I had a problem that the tab always reboots into recovery. So i want to flash a stock firmware. Any ideas?
Click to expand...
Click to collapse
i have come to a similar dead end.
came from fastdreamV6 rom and odin'd in T210RUEU0COB1_T210RXAC0COB1_HOME .tar .md5
pardon my terminology but i guess you'd say i dirty Odin'd it?> did not wipe or revert.
its where things went wroung for me
soo any ways.. looking for helpful and knowledageble people to begin trouble shooting this issue
after the install it rebooted and showed the tab3 splash screen then android package installer full screen before an OS. when the page installer screen disappeared that was the end of any responsiveness from the device.
mine always boots to black screen. no recovery , no audible/visual anything until odin mode.
always a black screen until i walk through the odin/download mode key' sequence blind
i have only half of what should look like a odin/download mode screen, the android guy has disappeared.
WIN7 does find the tab3 thats in [email protected]$$ odin mode in the device manager
odin also sees the tab3 but odin doesnt want to work to upload anything < hangs at setupconnection.. or pit mapping failed even when i have the new pit file being pushed,
ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
hemidall gives me communication conflicts
adb .. i currently have no os on the tablet as far as i can tell. maybe somebody can tell me if i can fastboot a command to push a recovery into it. but without adb-communication. i dont see it happening?
i presume i have a corrupted .pit file thats its not allowing me to replace.
OR KITKAT needs its own .pit file and i will need help aquiring one.
or its just a really bad flash alltogether. being boot.img. system img. recover img
how should i proceed if there is a way ? looking to get back to stock 4.4.2.
i can solder and make a usb jig if nessasary.
1 week later; further developments and workaround to boot here:
http://forum.xda-developers.com/gal...ably-hard-bricked-t3057440/page2#post60682636

Screen says There is no PIT partition after Firmware Install Failure

So I've been at this for a total of 9 hours now...here's the story:
Yesterday I have my trusty Note 4 on the charger, it charges fully and I unplug from the cord.
I hit the home button and the screen stays black like it was frozen.
I hit the power button, nothing happens.
I pull the battery, put it back in, nothing.
It finally goes back on and I get the Cant do normal boot:"MMC_Failed" and I'm stuck on the Odin screen.
Try to just re-flash the stock rooted ROM I was using at the time of this disaster and I kept getting the same message so I bring the phone to a Sprint service center where, when I walk in the front door and tap the power button, the phone lights right up and works. Now I look like a clown.
I leave the store and it freezes again so I try a factory reset, which sets this whole process in motion again once I set it up...freezes, "can't do normal boot" etc.
Then after someone suggested to flash the latest TWRP (3.0.0.0) and a stock firmware, I get a "system write fail" in Odin (both 3.09 & 3.10) so I try to flash the stock ROM again now I get a "No PIT File" error.
I flash the PIT file specific for my phone I got from SamMobile along with the same ROM and the phone wouldn't start.
I noticed the "system" was unchecked in TWRP so I checked it before doing anything but still no luck as of last night/this morning at 3:00am.
I wake up this morning and it goes right on with no issue just like a fresh/factory reset device.
Is there something i can do to make sure everything is ok so I don't have to go through this again?
I need this Note 4 to work.
I have been running stock OJ6 rooted ROM and that's it. No mods or anything, just root so for this to start acting up the way it did or why it happened is beyond me.
Someone recommended to install ClockworkMod so that would fix the "system" error but I'd rather see if anyone else had the same problem and how they fixed it before I attempt anything else.
Usually, any time I ever had a problem I clear the dalvik/cache, factory reset or flash firmware in Odin and everything is straight.
Thanks ahead of time for any help.

What method are you rooting with? Kernel and SuperSU version? Stock patched kernel or custom kernel?
Sounds like hardware failure but it could be unstable root with Knox fighting it and causing confusion. Knox and root don't coexist well.
When you pull battery, do you wait at least 30 seconds and use power button to drain residual power before reinserting battery? I've also noticed that power down doesn't happen so quickly as you think it should. Also, every black screen is not a power down state. Something is not quite right if you experience black screens in system booted mode but I wouldn't be so quick to pull the battery. Give it time to recover or hold power and volume up to reboot it if black screen persists on you. Battery pulls may be corrupting memory or losing data.
Edit: Philz CWM recovery has been recommended to wipe and flash when TWRP fails to do so. But it's been demonstrated that stock recovery can wipe where Philz fails to. Ultimately, I think some of the users reporting such were experiencing hardware failure so it's either randomness of successful wipe or the stronger tool demonstrating itself. Also since TWRP has been updated, it's unknown in my thinking which is the better Recovery to wipe and flash with. I prefer TWRP but thankfully haven't had the occasion of failed Odin or recovery flashes.
Your battery or power switch may contributing to the bad experience as well.
Sent from my SM-N920P using Tapatalk

samep said:
What method are you rooting with? Kernel and SuperSU version? Stock patched kernel or custom kernel?
Sounds like hardware failure but it could be unstable root with Knox fighting it and causing confusion. Knox and root don't coexist well.
When you pull battery, do you wait at least 30 seconds and use power button to drain residual power before reinserting battery? I've also noticed that power down doesn't happen so quickly as you think it should. Also, every black screen is not a power down state. Something is not quite right if you experience black screens in system booted mode but I wouldn't be so quick to pull the battery. Give it time to recover or hold power and volume up to reboot it if black screen persists on you. Battery pulls may be corrupting memory or losing data.
Edit: Philz CWM recovery has been recommended to wipe and flash when TWRP fails to do so. But it's been demonstrated that stock recovery can wipe where Philz fails to. Ultimately, I think some of the users reporting such were experiencing hardware failure so it's either randomness of successful wipe or the stronger tool demonstrating itself. Also since TWRP has been updated, it's unknown in my thinking which is the better Recovery to wipe and flash with. I prefer TWRP but thankfully haven't had the occasion of failed Odin or recovery flashes.
Your battery or power switch may contributing to the bad experience as well.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
yeah I hold the power button for like 30 seconds to a minute to make sure the charge is gone.
I just re-flashed thhhe rom but i'm gonna try to unroot if i can now that I can get into recovery again, i wasn't able to last night

broad_st_bully said:
yeah I hold the power button for like 30 seconds to a minute to make sure the charge is gone.
I just re-flashed thhhe rom but i'm gonna try to unroot if i can now that I can get into recovery again, i wasn't able to last night
Click to expand...
Click to collapse
If you're trying to boot un-rooted, you may be using stock kernel with systemless root? Why stock kernel? It's more stable in that fashion of full un-root with systemless SuperSU root.
But latest Beastmode works well; keep it updated. There was the initial release that somehow got hindered by a Samsung security update and boot looped once the update was pushed.
Anyway, if you're using systemless root, keep the SuperSU beta up to date for stability purposes. It's experimental as far as Lollipop is concerned and doesn't play well with system modifications.
Or maybe you're not using it for frequent full un-root? I'm actually testing it again with stock kernel ATM.
Sent from my SM-N920P using Tapatalk

samep said:
If you're trying to boot un-rooted, you may be using stock kernel with systemless root? Why stock kernel? It's more stable in that fashion of full un-root with systemless SuperSU root.
But latest Beastmode works well; keep it updated. There was the initial release that somehow got hindered by a Samsung security update and boot looped once the update was pushed.
Anyway, if you're using systemless root, keep the SuperSU beta up to date for stability purposes. It's experimental as far as Lollipop is concerned and doesn't play well with system modifications.
Or maybe you're not using it for frequent full un-root? I'm actually testing it again with stock kernel ATM.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Odin wasn't working, kept getting "write/fail" so I flashed the PIT file along with the stock firmware after *everything on earth* didn't work, Odin did it's thing and I got the green PASS! but still can't boot the phone regularly...I got into factory recovery just to make sure i was not rooted, did a factory reset and it doesn't reboot...I'm lost here...
my main thing was to get it to unroot so I can bring it to Sprint and let them try to fix it...but I can't boot to make sure it's running stock, I don't wanna get there and they boot it and see the phone is rooted...

Flashed PIT file and stock firmware and got the following (pass):
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> cache.img.ext4
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:

broad_st_bully said:
Odin wasn't working, kept getting "write/fail" so I flashed the PIT file along with the stock firmware after *everything on earth* didn't work, Odin did it's thing and I got the green PASS! but still can't boot the phone regularly...I got into factory recovery just to make sure i was not rooted, did a factory reset and it doesn't reboot...I'm lost here...
my main thing was to get it to unroot so I can bring it to Sprint and let them try to fix it...but I can't boot to make sure it's running stock, I don't wanna get there and they boot it and see the phone is rooted...
Click to expand...
Click to collapse
If it dus not boot try to flash repair firmware

broad_st_bully said:
Flashed PIT file and stock firmware and got the following (pass):
Removed!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:6)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
cache.img.ext4
modem.bin
RQT_CLOSE !!
RES OK !!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
Click to expand...
Click to collapse
If you've wiped everything but extSdCard and flashed the stock tar in Odin, there shouldn't be any trace of root. You're not rooted.
Did you try factory reset in stock recovery? Can't recall, but is there also a format data option in stock recovery? If so, try that too.
Sent from my SM-N920P using Tapatalk

broad_st_bully said:
Flashed PIT file and stock firmware and got the following (pass):
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> cache.img.ext4
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
Click to expand...
Click to collapse
You need a repair firmware 4 file firmware
PDA
Modem
CSC
Bootloder
Go here http://www.tsar3000.com/Joomla/index.php?option=com_content&view=category&id=55&Itemid=82 and find firmware acoding to your phone model and country region and flash via odin hit thanks if helped

waheem said:
You need a repair firmware 4 file firmware
PDA
Modem
CSC
Bootloder
Go here http://www.tsar3000.com/Joomla/index.php?option=com_content&view=category&id=55&Itemid=82 and find firmware acoding to your phone model and country region and flash via odin hit thanks if helped
Click to expand...
Click to collapse
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!

broad_st_bully said:
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
Click to expand...
Click to collapse
I'm gonna try your link. even though it seems to be working now it still reads "MMC_READ FAILED" in Odin/DL mode...gonna try and see if your fix helps, thank you.:good:

broad_st_bully said:
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
Click to expand...
Click to collapse
tried to flash that file, back where i started, it failed in Odin right away, stuck with the "firmware upgrade encountered an issue" for Kies that doesn't even work for this phone for some reason....Kies is straight trash...

broad_st_bully said:
I'm gonna try your link. even though it seems to be working now it still reads "MMC_READ FAILED" in Odin/DL mode...gonna try and see if your fix helps, thank you.:good:
Click to expand...
Click to collapse
Just press thanks buttons if help

broad_st_bully said:
tried to flash that file, back where i started, it failed in Odin right away, stuck with the "firmware upgrade encountered an issue" for Kies that doesn't even work for this phone for some reason....Kies is straight trash...
Click to expand...
Click to collapse
@broad_st_bully any luck on this issue since last post? or had you given up? I am experiencing the same issue but with the tmobile version running cmremix rooted.... at least it was...

Boot loop problem! Help me

Hello! I've a problem with my Note 4 Sprint. The phone is in a boot loop state, it reebots every time when the logo "Samsung Galaxy Note 4" is showed. I've tried everithing! When I flashed stock roms it reboots again. When I try to install custom rom it says error 7 set_perm failed. I want to say that in each custom recovery I've installed, the touch screen is misaligned and to press a button I've to touch it 1 or 2 cm up!
Sometimes after flashing a stock rom, it pass the Note 4 logo, but when on the screen there is the "SAMSUNG" logo it reboots again and again and again.... when it reach SAMSUNG logo a strange thing happen... the pixels on the screen are showed badly such as rainbow.
In the download mode the Binary status is Samsung official and the system status is custom (also with stock rom).
I don't know to do. Can you help me? I've tried JIG also.
Thank you!

Your touch is off because you've flashed wrong custom recovery. Check that and reinstall correct one. As long as you have flashed a recent stock tar, when you can get a successful boot, open dialer and dial *#2663# and select the top left option to reinstall TSP FW update (General). If that doesn't work, reinstall the stock tar and auto boot and promptly fix that with dialer code.
The recovery flash error you're getting could be caused wiping system or flashing with mounted system partition. If you do either of those, unmount system and reboot recovery before trying to flash.
The boot loop could be caused by loss of root but custom kernel is currently installed or incompatible our corrupt data. Did you install custom kernel and wipe data or previously install CM or Xposed framework before the bootloops started?
You may need to factory reset and wipe internal memory to get it to boot. Try that with custom ROM again. You typically don't have to wipe system or mount it unless you have a problem. Many custom ROMs I've seen in our forum wipe system in updater-script(s) before installing ROM.
Here's the TWRP recovery for Sprint Note 4 for Odin flashing.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Sent from my SM-N910P using Tapatalk

Thank you
Thank you for your reply. First to fix the touch, I've to boot the phone. Why flashing his stock ROM (Full, with boot, kernel ecc... ) it doesn't boot?
When I flash 5.1.1 in his stock recovery it says dm-verify verification failed, when I flash a 6.0.1 stock ROM it says dm-verify verification failed and also to install first DRK!! I've not success to downgrade the phone to 5.0.1 or 4.4.4 because Odin stop me.

kaddhuzzu93 said:
Thank you for your reply. First to fix the touch, I've to boot the phone. Why flashing his stock ROM (Full, with boot, kernel ecc... ) it doesn't boot?
When I flash 5.1.1 in his stock recovery it says dm-verify verification failed, when I flash a 6.0.1 stock ROM it says dm-verify verification failed and also to install first DRK!! I've not success to downgrade the phone to 5.0.1 or 4.4.4 because Odin stop me.
Click to expand...
Click to collapse
If you can recall the update you had on your phone before you first attempted to flash the older stock tars that wouldn't flash, I'd recommend you get that specific stock tar, verify md5 against zip if you get it from our general forum with uploads to AFH.
After verifying md5, extract the tar.md5 for Odin flash. Factory reset in stock recovery if still on it. Odin TWRP and wipe internal memory and then power down. Pull battery for at least 30 seconds while draining power circuit by gently pressing and holding power button down.
Install battery and boot to download mode. Verify your phone's display indicates that reactivation lock is off. Ensure when connecting USB in download mode that Odin indicates COM as added. Once you have md5 verified and COM added displayed in Odin log, start the flash with Odin default options.
It should boot and stock recovery shouldn't indicate dm-verity failure.
Above, I suggested the update you had before the older tar wouldn't flash because you've most likely triggered a factory reset protection condition. I wouldn't advise flashing stock tars below OG5 because the bootloader in Android 5.1 and up block downgrade to 4.4 and 5.0 lower security bootloaders. This started with OE1 do that one and OF5 may still work but differ from OG5 and up. There is a way to run KitKat but Odin won't do that and your bootloader should remain on the higher security ones to avoid issues like yours. The OG5 to OK1 custom kernel should work with the KitKat ROMs, allowing it to boot.
If the recommended steps above doesn't reset the dm-verity, Chainfire may help; flashing systemless SuperSU zip and using the SuperSU app once booted to fully un-root may clear the dm-verity failure if wiping and flashing doesn't. Warning: unless you have stock kernel, fully un-root may leave you in a bootloop state until flashing SuperSU zip again. But if it doesn't boot after stock tar, you may have to try Chainfire Auto Root for Note 4 to root (make sure you have the latest by downloading again- Chainfire Auto Root for KitKat shouldn't be used. Hopefully it boots if you've had boot issues up to this point. Otherwise, Chainfire may not help. If still not booting, factory reset and try the stock tar again. Sometimes, flashing the stock tar a second time helps.
Wiping everything but extSdCard in TWRP before flashing stock tar is another option you may consider. I think I read one poster had thought that accidentally restoring an old EFS backup had started his dm-verity issue. Take notes and share what works if you resolve it. Best wishes for success.
Sent from my SM-N910P using Tapatalk

samep said:
If you can recall the update you had on your phone before you first attempted to flash the older stock tars that wouldn't flash, I'd recommend you get that specific stock tar, verify md5 against zip if you get it from our general forum with uploads to AFH.
After verifying md5, extract the tar.md5 for Odin flash. Factory reset in stock recovery if still on it. Odin TWRP and wipe internal memory and then power down. Pull battery for at least 30 seconds while draining power circuit by gently pressing and holding power button down.
Install battery and boot to download mode. Verify your phone's display indicates that reactivation lock is off. Ensure when connecting USB in download mode that Odin indicates COM as added. Once you have md5 verified and COM added displayed in Odin log, start the flash with Odin default options.
It should boot and stock recovery shouldn't indicate dm-verity failure.
Above, I suggested the update you had before the older tar wouldn't flash because you've most likely triggered a factory reset protection condition. I wouldn't advise flashing stock tars below OG5 because the bootloader in Android 5.1 and up block downgrade to 4.4 and 5.0 lower security bootloaders. This started with OE1 do that one and OF5 may still work but differ from OG5 and up. There is a way to run KitKat but Odin won't do that and your bootloader should remain on the higher security ones to avoid issues like yours. The OG5 to OK1 custom kernel should work with the KitKat ROMs, allowing it to boot.
If the recommended steps above doesn't reset the dm-verity, Chainfire may help; flashing systemless SuperSU zip and using the SuperSU app once booted to fully un-root may clear the dm-verity failure if wiping and flashing doesn't. Warning: unless you have stock kernel, fully un-root may leave you in a bootloop state until flashing SuperSU zip again. But if it doesn't boot after stock tar, you may have to try Chainfire Auto Root for Note 4 to root (make sure you have the latest by downloading again- Chainfire Auto Root for KitKat shouldn't be used. Hopefully it boots if you've had boot issues up to this point. Otherwise, Chainfire may not help. If still not booting, factory reset and try the stock tar again. Sometimes, flashing the stock tar a second time helps.
Wiping everything but extSdCard in TWRP before flashing stock tar is another option you may consider. I think I read one poster had thought that accidentally restoring an old EFS backup had started his dm-verity issue. Take notes and share what works if you resolve it. Best wishes for success.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you again, I've tried to do what you say me. The phone is still in boot loop, when I flashed the first time CF Auto Root it stops in half of the process. And on the display of download mode it's appeared "Set Warranty Bit: cache" (yellow), while Odin shows Cache instead of Pass and the log report RQT_CLOSE !!. Can I try anything else?

kaddhuzzu93 said:
Thank you again, I've tried to do what you say me. The phone is still in boot loop, when I flashed the first time CF Auto Root it stops in half of the process. And on the display of download mode it's appeared "Set Warranty Bit: cache" (yellow), while Odin shows Cache instead of Pass and the log report RQT_CLOSE !!. Can I try anything else?
Click to expand...
Click to collapse
Which stock tar are you flashing?
Can you copy paste the Odin log? What does phone display?
The Chainfire Auto Root should only be flashed over stock recovery. Recommended after stock tar flash.
Sent from my SM-N910P using Tapatalk

samep said:
Which stock tar are you flashing?
Can you copy paste the Odin log? What does phone display?
The Chainfire Auto Root should only be flashed over stock recovery. Recommended after stock tar flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
With OG5 (5.1.1) stock:
Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone
After flash is completed, the phone display a black screen with a little robot and a progress bar. When the progress bar reaches the half, the phone reboots and on the "Samsung Galaxy Note 4" logo it continue to reboot again and it goes in bootloop...
With PC1 or other 6.0.1 stock:
Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_N910PVPU4DPC1_N910PSPT4DPC1_CL7381751_QB8794358_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> carrier.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone
After flash is completed, the phone display "Installing system update" and when the progress bar is about 30% the sentence chage to "Erasing...". Then a red sentence appear: "Device does not have DRK, please install DRK first. Press any button?". When I press a button after a minute it goes on recovery screen with these logs:
Supported API: 3
Installing package
finding update package
opening update package
verifying update package
Installing update...
Successfully installed package.
Wiping data..
Formatting /data
Formatting /cache
Set Factory reset done
Copying media files
preload checkin
Data wipe complete
(Success)
Appling Multi -CSC
Applied the CSC-code: XAS
Successfully applied multi-CSC
Set Factory Reset done
Copying media files
preload checkin
Device does not have DRK (Device Root Key), contact to SW PL
Please flash ENG binary then install DRK
When i reboot the phone it continue to boot loop...

kaddhuzzu93 said:
With OG5 (5.1.1) stock:
Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone
After flash is completed, the phone display a black screen with a little robot and a progress bar. When the progress bar reaches the half, the phone reboots and on the "Samsung Galaxy Note 4" logo it continue to reboot again and it goes in bootloop...
With PC1 or other 6.0.1 stock:
Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_N910PVPU4DPC1_N910PSPT4DPC1_CL7381751_QB8794358_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> carrier.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone
After flash is completed, the phone display "Installing system update" and when the progress bar is about 30% the sentence chage to "Erasing...". Then a red sentence appear: "Device does not have DRK, please install DRK first. Press any button?". When I press a button after a minute it goes on recovery screen with these logs:
Supported API: 3
Installing package
finding update package
opening update package
verifying update package
Installing update...
Successfully installed package.
Wiping data..
Formatting /data
Formatting /cache
Set Factory reset done
Copying media files
preload checkin
Data wipe complete
(Success)
Appling Multi -CSC
Applied the CSC-code: XAS
Successfully applied multi-CSC
Set Factory Reset done
Copying media files
preload checkin
Device does not have DRK (Device Root Key), contact to SW PL
Please flash ENG binary then install DRK
When i reboot the phone it continue to boot loop...
Click to expand...
Click to collapse
The OG5 Odin flash looks normal to me and didn't have the drk issue. That may be the one you need but did you factory reset and try to boot when it didn't boot? Did you try anything else after that before trying PC1?
What wipes have you done so far? Flashing OG5 after PC1 means you should factory reset before flashing OG5 at the very least. I usually wipe internal memory too.
Think of it this way... If you have factory reset protection blocking the Odin flash, you should get it bypassed using TWRP to wipe everything but extSdCard and powering down, pull battery and flash same stock tar that last successfully flashed. Was it OG5? The update in question could have been Odin flash or OTA and would have most likely been the last update that ran normally. Flashes since may not have taken. PC1 Odin flash doesn't seem normal because of the drk issue.
There is a factory reset protection bypass method using UTG and a downloaded file but that method is only required if you had reactivation lock enabled or and wiped system and data and tried to flash a different update and couldn't recall your Google account or original password. IIRC, flashing the same update and using the same Google account and password wouldn't require the bypass. That also requires an ability to boot to bypass anyway.
It's a theory this same factory reset protection gets activated by trying to downgrade the bootloader. The difference being an inability to flash in Odin and auto boot. I think the steps were to wipe everything but extSdCard, power down, pull battery and flash same update in Odin and use same Google account and password. Effectively, you're breaking Odin flash capability and not really flashing until you get the steps right. Once you satisfy that, Odin and OTA updates should work again.
There may be a way to get it going but I haven't seen these requirements lately: flashing parts of the stock tar and then flashing whole tar or using KIES emergency recovery to flash stock tar.
I'd suggest trying the wipes with the right stock tar first. Seems it should boot with a factory reset or factory reset and wipe internal memory. Like I said before, sometimes just flashing the stock tar again after factory reset works (flash tar, boot fails, factory reset on stock recovery, if boot fails again, flash same stuck tar again).
Sent from my SM-N910P using Tapatalk

samep said:
The OG5 Odin flash looks normal to me and didn't have the drk issue. That may be the one you need but did you factory reset and try to boot when it didn't boot? Did you try anything else after that before trying PC1?
What wipes have you done so far? Flashing OG5 after PC1 means you should factory reset before flashing OG5 at the very least. I usually wipe internal memory too.
Think of it this way... If you have factory reset protection blocking the Odin flash, you should get it bypassed using TWRP to wipe everything but extSdCard and powering down, pull battery and flash same stock tar that last successfully flashed. Was it OG5? The update in question could have been Odin flash or OTA and would have most likely been the last update that ran normally. Flashes since may not have taken. PC1 Odin flash doesn't seem normal because of the drk issue.
There is a factory reset protection bypass method using UTG and a downloaded file but that method is only required if you had reactivation lock enabled or and wiped system and data and tried to flash a different update and couldn't recall your Google account or original password. IIRC, flashing the same update and using the same Google account and password wouldn't require the bypass. That also requires an ability to boot to bypass anyway.
It's a theory this same factory reset protection gets activated by trying to downgrade the bootloader. The difference being an inability to flash in Odin and auto boot. I think the steps were to wipe everything but extSdCard, power down, pull battery and flash same update in Odin and use same Google account and password. Effectively, you're breaking Odin flash capability and not really flashing until you get the steps right. Once you satisfy that, Odin and OTA updates should work again.
There may be a way to get it going but I haven't seen these requirements lately: flashing parts of the stock tar and then flashing whole tar or using KIES emergency recovery to flash stock tar.
I'd suggest trying the wipes with the right stock tar first. Seems it should boot with a factory reset or factory reset and wipe internal memory. Like I said before, sometimes just flashing the stock tar again after factory reset works (flash tar, boot fails, factory reset on stock recovery, if boot fails again, flash same stuck tar again).
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I can try again...
I tried every firmware in this page (https://www.sammobile.com/firmwares/database/SM-N910P/SPR/) from 5.1.1 to up with the same result as logged to you ( also wiping everything but extSD ).
I let you to know about my next tries...

With OK1 firmware (the latest of 5.1.1) it remains on Samsung Galaxy Note 4... but it doesn't proceed to boot... I'm going to leave in this situation and wait to boot...

My Note 4 started shutting down at 40% battery and then boot looping. I replaced the battery, and it worked fine after that.
Examine your battery to see if it's swelling up at all. Look at the side of the phone to see if anything is bulging. Even if it isn't swelling, it could still be your battery, but that's one thing to check.
I know it sounds weird that it would be the battery, but I'm not the only one who has experienced this, and fixed it with a new battery.