one of the tablets roms was haveing sound issuses with dead trigger 2 so i decided to install another rom (cm12) and it seems to be in a boot lap and cant get into fire os recovery by holding switches is there fix for that?
Nightmare-Rex420 said:
one of the tablets roms was haveing sound issuses with dead trigger 2 so i decided to install another rom (cm12) and it seems to be in a boot lap and cant get into fire os recovery by holding switches is there fix for that?
Click to expand...
Click to collapse
Likely not. If CM 12.1 was installed incorrectly it can bork access to stock recovery. If so there is no known recovery at this time.
Quick test:
- untether device
- long press power (20+ sec) to insure device is powered off
- press and hold key closest to headphone jack (vol-up)
- while continuing to hold <vol-up> press and hold <power>
- release both buttons when screen comes on
What happens next?
ah dang that sucks and i think it was the xposed framwork that bricked it becuase i did it to the other tablet and it bricked but was able to recover and start fresh, howcome dose cm12 screw recovery while other firmwares don't and how do you get xposed installed without it causeing a brick?
now i was able to get into recovery and flash 5.1.2 back but now i cant seem to be able to get root back with kingroot giveng error 592 once and then other error (chinese text) i tried re-installing the 5.1.2 again an additional like suggested if kingroot fails.
Nightmare-Rex420 said:
now i was able to get into recovery and flash 5.1.2 back but now i cant seem to be able to get root back with kingroot giveng error 592 once and then other error (chinese text) i tried re-installing the 5.1.2 again an additional like suggested if kingroot fails.
Click to expand...
Click to collapse
- assuming you didn't register with Amazon when device initialized
- try different builds of KingRoot, in particular 4.8.5, 4.9.2 and 4.9.6
- avoid version 5.x; difficult to uninstall and/or replace KingUser with SuperSU
- patience is a virtue: http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70077755
- some individuals report trying "dozens of times" before finding joy
Related
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.
YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?
Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.
Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.
Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.
I currently am trying to install CM12.1 onto my Amazon Fire 7, but unfortunately, it looks like I may have messed up in the process (I am stuck with the Amazon logo re-looping every ~15-20 seconds). I am able to go into the safe recovery mode, so I assume I haven't bricked the device completely, but I was wondering, what exactly is the best way to flash CM12.1 onto this device?
There seems to be an excessive amount of information, but very little organization, so would love to hear what the "best" steps would be to get CM12.1 on this bad boy.
I don't have the device yet but from what i read you need to tell us more info like what was your amazon v. 5.0.1 or 5.1.1 and how you install cm by TWRP or flash fire
Sent from my iPhone using Tapatalk
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
shabuboy said:
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
Click to expand...
Click to collapse
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
darkgiant said:
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
Click to expand...
Click to collapse
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Just follow the instructions to install CM 12.1 and wait for it to boot.
Ownster said:
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Click to expand...
Click to collapse
Yeah, so I just found that out few seconds ago. I tried to flash and install CM, but after the reboot, it just goes back to the FireOS "Optimizing system storage and applications..." screen, no idea what I am doing wrong...
I am also wiping everything too before I flash the CM and GAPPS zip files
darkgiant said:
I am also wiping everything too before I flash the CM and GAPPS zip files
Click to expand...
Click to collapse
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
abacabie said:
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
Click to expand...
Click to collapse
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
Click to expand...
Click to collapse
Glad it worked well for you. Not everyone has been so fortunate. One persons favorable experience does not equate to everyone. Some of those impacted are veteran users who 'lost' devices testing out code and techniques that you are now benefiting from.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
He's talking about how his device got buggered from a dirty Rom load. In his case and for a few others, they've lost the option to sideload back to stock.
Anyway here's the bare minimum process, since it sounds like you've gone through the details parts of Rom loading before.
#1 restore to stock rom 5.1.1
#2 install SuperSU/Root
#3 install flashfire
#4 install CM/SlimLP and Gapps (pico, micro, mini) of your choice, and your done.
When I put CM on my 5.1.1 Fire device, I installed flashfire.apk manually, used open Gapps pico, and the CM 12-30-2015 image.
abacabie said:
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
Click to expand...
Click to collapse
Gotcha, didn't know there was level of increments the relooping represented. Well either way, hopefully something gets developed to all the "hard-bricked" users.
i have absolutely no clue what i am doing here, i tried to reboot my tablet into TWPR menu
but i could not figure it out it has TWRP, and RR rom and root
i held the power button down and did reboot recovery and i did not get TWRP menu
so rebooted it and then i chose bootloader, and now all i get is a black screen that says fastboot..
holding power and it won't reboot it wont turn off or do anything
how do i fix this ****?
how do i get to the twrp menu screen?
how do i create a backup of my system to the SD card?
i want to try an experimental APK but i want to make sure i can recover if it messes up my tablet
but 1st how do i fix this?
gdroid666 said:
i have absolutely no clue what i am doing here, i tried to reboot my tablet into TWPR menu
but i could not figure it out it has TWRP, and RR rom and root
i held the power button down and did reboot recovery and i did not get TWRP menu
so rebooted it and then i chose bootloader, and now all i get is a black screen that says fastboot..
holding power and it won't reboot it wont turn off or do anything
how do i fix this ****?
how do i get to the twrp menu screen?
how do i create a backup of my system to the SD card?
i want to try an experimental APK but i want to make sure i can recover if it messes up my tablet
but 1st how do i fix this?
Click to expand...
Click to collapse
Clean up the language.
- no TWRP (custom recoveries) on this device
- to exit from fastboot untether and long press power until it turns off
- start with the forum index and read what you can/can't do with this device and how to accomplish it
Davey126 said:
Clean up the language.
- no TWRP (custom recoveries) on this device
- to exit from fastboot untether and long press power until it turns off
- start with the forum index and read what you can/can't do with this device and how to accomplish it
Click to expand...
Click to collapse
yes got it to reboot by holding volume and power finally ,it did not work the 1st few tries for some reason
i know i was in the TWRP screen before when i flashed the rom and xposed but now i forget how to get back to it now
so what happens if i mess up my system with an experimental APK, i am trying to add miracast
if it messes up something then will i be able to recover? or would i have to make a backup with TWRP 1st?
gdroid666 said:
yes got it to reboot by holding volume and power finally ,it did not work the 1st few tries for some reason
i know i was in the TWRP screen before when i flashed the rom and xposed but now i forget how to get back to it now
so what happens if i mess up my system with an experimental APK, i am trying to add miracast
if it messes up something then will i be able to recover? or would i have to make a backup with TWRP 1st?
Click to expand...
Click to collapse
Clean up thread title...go from there. Miracast won't work on this device.
Davey126 said:
Clean up thread title...go from there. Miracast won't work on this device.
Click to expand...
Click to collapse
sorry i can't edit it, it won't let me
also i have looked around and i found this .apk
http://cord-cutters.wonderhowto.com...rooted-android-device-running-kitkat-0156212/
(it says kitkat but there was a thread on here on it and it said kitkat or above)
https://www.androidfilehost.com/?fid=95784891001616583
and i searched and searched but i have not found any reports of it ever being tried on the 2015 5th gen fire 7
i can only seem to get to the thread in google cache ,and there are only reports of it being tried on the HD fire 7 and all posts end around 2014 so i am not sure if it will work, but what is the worst thing that could happen if i try this? with no backup and TWRP installed? could i still revert everything back?
have you ever heard of anyone trying this specific .apk on this device before?
gdroid666 said:
sorry i can't edit it, it won't let me
also i have looked around and i found this .apk
http://cord-cutters.wonderhowto.com...rooted-android-device-running-kitkat-0156212/
(it says kitkat but there was a thread on here on it and it said kitkat or above)
https://www.androidfilehost.com/?fid=95784891001616583
and i searched and searched but i have not found any reports of it ever being tried on the 2015 5th gen fire 7
i can only seem to get to the thread in google cache ,and there are only reports of it being tried on the HD fire 7 and all posts end around 2014 so i am not sure if it will work, but what is the worst thing that could happen if i try this? with no backup and TWRP installed? could i still revert everything back?
have you ever heard of anyone trying this specific .apk on this device before?
Click to expand...
Click to collapse
- have not heard of anyone trying linked apk on this device
- in general custom roms on Amazon devices do not support miracast (multiple devices/multiple roms)
- if you can access the stock recovery menu via <power>+<vol-up> recovery is possible (reload FireOS)
- unlikely a straight apk install will bork the rom; more likely it simply won't work
Davey126 said:
- have not heard of anyone trying linked apk on this device
- in general custom roms on Amazon devices do not support miracast (multiple devices/multiple roms)
- if you can access the stock recovery menu via <power>+<vol-up> recovery is possible (reload FireOS)
- unlikely a straight apk install will bork the rom; more likely it simply won't work
Click to expand...
Click to collapse
yup you are right it dod not work the app gave a message right away about not having some file for audio something t other i forget ,just uninstalled th eapk and no damage done
So I bricked my new Fire and I'm trying to figure out what went wrong. It came with 5.1.3 and I successfully downgraded to 5.1.2 and was able to root with Kingroot. Unfortunately SuperSU-Me never worked to replace King with SuperSU and I was unable to replace it manually. I tried multiple times, reflashing a clean image of 5.1.2 each time. Today I was going to give it another shot and started by reflashing the image I flashed a dozen time yesterday, both ADB and the tab said it was successful. I rebooted and its hard bricked. The screen and backlight never come on but if plugged into a computer you hear the usb connect and disconnect sound. Will not boot into recovery or fastboot.
Is this just a fluke or is there anything that may have happened? I just don't want a repeat... I like learning from mistakes but I don't have any ideas or anything to go on.
PIYIRIO said:
So I bricked my new Fire and I'm trying to figure out what went wrong. It came with 5.1.3 and I successfully downgraded to 5.1.2 and was able to root with Kingroot. Unfortunately SuperSU-Me never worked to replace King with SuperSU and I was unable to replace it manually. I tried multiple times, reflashing a clean image of 5.1.2 each time. Today I was going to give it another shot and started by reflashing the image I flashed a dozen time yesterday, both ADB and the tab said it was successful. I rebooted and its hard bricked. The screen and backlight never come on but if plugged into a computer you hear the usb connect and disconnect sound. Will not boot into recovery or fastboot.
Is this just a fluke or is there anything that may have happened? I just don't want a repeat... I like learning from mistakes but I don't have any ideas or anything to go on.
Click to expand...
Click to collapse
- there is always a risk associated with flashing (reloading/sideloading FireOS) sensitive bootloader components as a single flipped bit can/likely will brick the device; flakey usb cables are a common culprit
- avoid KingRoot builds >4.96 as removal can be problematic
- recommend using the latest 5th gen SuperTool to transition from KingUser to SuperSU after rooting; SuperSume is increasing ineffective, especially on more recent versions of FireOS and/or KingRoot (not sure which).
This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
saywhhaa33 said:
This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
Click to expand...
Click to collapse
First of all you have entered wrong model no here note 5 model no should be SM-N920xx
1)Have you enabled Oem unlocking from developers option before flashing twrp and cf-autoroot using odin? If not then you done a mistake!!
2) Have you tried to flash latest stock firmware using odin with latest usb drivers installed on you pc and proper odin flashing guide?(Flash latest 6.0.1 for your device with latest usb drivers installed on pc and connect phone to main usb port using original usb cable) After flashing stock rom if your facing bootloop then you can try reset through stock recovery (Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
3)If you can boot into twrp recovery normally then flash any custom rom suitable for your device i.e. for sm-n920p..Custom roms are pre-rooted so no need to flash cf-autoroot..Flash custom rom, if you successfully boot up the rom( It's difficult to boot custom rom though if you haven't enabled oem unlocking you will face custom binary is blocked by frp protection),then enable oem unlocking from developers option and try flashing stock rom again
4) Next option for you is download Samsung smart switch for pc, install latest usb drivers on your pc, connect your phone to pc in download mode(Press volume down+power+home button simultaneously),in smartswitch select emergency software recovery, it will ask you imei,model no and serial no which you can find either on box or back panel of your phone,smartswitch will detect latest stock firmware for your device, hit update now,give some time until update complete..Your device will be automatically reboot..If even you face bootlopp, then goto stock recovery(Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
**IF SUGGESTION IN SECOND POST HELPS YOU THEN ITS DONE, AVOID NEXT SUGGESTIONS**
Are you sure you can't install cf auto root again to solve it? IF not...
I did a search and got hits for twrp for N910P. Get it loaded, get it wiped and have another shot at success. Next way to get rid of the persistent rooter gone rogue, load up a factory BL + AP. If that doesn't work download another version and try again.
I've enabled OEM unlocking, flashed latest stock AP...BL.. And so on, factory reset in both factory and TWRP. I have also tried flashing CF Auto root again to see if that would fix it also custom ROMs bootloop except for CM13 and Lineage OS- Which is weird because the ROMs are for the SM N920C model and I'm and Sprint model, So I don't understand that. Weird!! Everything recognizes me as SM N920C except when I am in download mode. Also, having no imei or any back ups make its even harder since my computer completely crashed on me because I am unable to use Samsung smart switch due to the wrong model and null imei. So I'm completely stumped with this issue. Not sure if its a corrupted partition or folders not being in the correct folder locations along with wrong permissions, I've literally stressed everything to my knowledge about this and I'm all out of what issues this could be related to