Develop Bugs

[Q] Stuck samsung screen even after odin stock

Hey guys hopefully you can help me. I was rooted for like 3 or 4 months now and have had not many problems or not anything I couldn't fix my self. My phone gets stuck on the Samsung Galaxy s4 screen anytime I reboot. I have tried different roms, different kernels, I even odin back to stock. I was using TWRP 6.0 then reverted back to TWRP 5.2 to see if that was causing the problem. Still have problems. I am going to re download the stock tar to see if it was a bad download but Odin checks the md5 and says it was good. Odin says passed every time also. Odin version is 3.07.
I get a error before and when trying to wipe dalvic cashe. I can wipe reg cash no problem. I think my phone is not mounting the internal storage when it reboots. I could be way off but need help asap. If I format super wipe with twrp then restart twrp and then factory reset I can install or restore a rom some times but still cant restart the phone. Any hope would be greatly appreciated.

EDIT
I wanted to edit my previous commet. LiquidSmooth seems to be running fine. So TW roms and GE roms **** up on my phone when I restart. so is it the internal systems when I have TW roms. I think it has something to do with partictions messing around maybe.
I like TW roms and want to continue to use them... Thank you

Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you

I got this problem a few days ago and found some topic including this one. You should check it out.
Well, what worked for me was Odin to stock firmware, root again, install recovery then custom rom. Now it's working fine. Try to downloading it again to see if it works. I downloaded mine from here, rooted and recovery it using this one.

TheAxman said:
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
Click to expand...
Click to collapse
+1 to what he said. I bet if you go into the stock recovery after odin flashing it will say something like cannot mount /data partition. Factory reset there, and it should fix that and make it mountable. (Its important to use the stock recovery factory reset after the odin, don't flash a custom recovery right after flashing)

This was incredibly helpful. I had the same issue. Thank you.
This is also applicable to the Verizon Wireless model.

[Q] Encryption Failed

First Yes i have searched and i found several posts but none had enough information or ended up with directing the op to the de-brick thread I feel its not bricked and I don't want to run into more problems.
Here is how it goes down
using 4.2.1 Rom
using CWRM 6.0.3.1
I tried to encrypt my phone (don't ask me why as if i could go back in time i wouldn't have tried it)
So first it would only boot to the screen that says encryption failed factory reset and try to encrypt again and has a restart button at first nothing worked even the Rom UI would crash at this point and the restart (software button) on the screen was unresponsive. I then went into recovery and tried to load a recovery and it could not mount /data as it read as it was secured. So i went and formatted it and was successful with restoring a backup Although as soon as it booted again it brought me right to that same screen?
I am going to try to start over with a new Rom installation while i wait for a reply.
I just hope i can get it done simply without Odin or connecting it to my PC as i tend to not have good luck with that. IDK whats up with my PC.
Anyway if a simple Rom install fixes it ill be happy but something is still there saying i want to encrypt it or IDK what is causing it to go to the encryption failed page when I have formatted all but /sdcard (i was afraid to unless I'm told) I know everything else is fine /system /data /cache are all replaced by the Rom so i know its OK to format them but /sdcard is all the data on the phone so I'm not afraid of losing music ringtones pictures etc if i do need to format /sdcard but i want to be told i should first
also please ask me for any in formation you may need i want to fix this and also i need to go find a Rom so also a Rom suggestion is fine too (if its going to help otherwise I'm going to find a basic 4.2.1 Touchwiz based Rom and flash that

Please Flash UVDMD5 version of Root66 via Odin.

Perseus71 said:
Please Flash UVDMD5 version of Root66 via Odin.
Click to expand...
Click to collapse
THANKS I tried flashing a fresh ROM after formatting everything now im in a boot loop and as it not bricked (soft bricked anyway) i was hoping a new route66 via Odin would be my main option.
Now as far as it goes on updating to 4.3 what file should i flash via Odin? should i use T999_UVDMD5 to get it working again then use T999_UVUEMJC to update to 4.3 (how i went from ICS to JB so would it be the same to KK ,4.3,) or can i just do a single Odin to T99_UVUEMJC so I u can be ready to use 4.3 roms. I just want to make sure because if I don't' have to use a 4.13 route 66 ROM to com back from this boot loop can I skip the step of using Odin to UN soft brick my 4.1.2 and go straight to 4.3.
I just want to know the best way to go about eventually being able to load 4.3 roms on this phone more because they are easier to find (as in more developed at this time) and to be update
I appreciate all your help and in case any ROM devs are reading this I love your work each and every one of you make this place better i wish i had the (first smarts) and second the time to mod for myself but over the years you guys are just awesome and i wish i was at any of your levels (all who post or even mod for themselves) as if i knew what you did i would not be in the predicament either and if i can fix it i will be pleased with myself as i bet most or all devs could fix this issue in 5-10 min where you can see Ive been at it days! Thanks in advance for any future help and most of all so far thank to you Perseus71 for helping me start

Never EVER flash UVUEMJC. Let's first get you back working with UVDMD5. Once that's achieved, I will get you 4.3 by another way.
For now, If you are right now on that bootloop/softbrick with just the UVDMD5, then great. If not go back to recovery, factory reset and wipe the cache and Re-flash UVDMD5 via Odin. This time, in Odin, make sure to uncheck Auto Reboot.
Once Odin has succeeded, Flash a custom Recovery such as TWRP via Odin. After that is done, reboot to recovery. Wipe Dalvik and Cache and then reboot normal.

[Q] Encryption Unsuccessful (Android 4.1)
I have partitioned my phone incorrectly. Phone is asking for a reset..
I deleted the /data and /sdcard because I formatted the internal storage and every time I reboot, I get a Encryption Unsuccessful message and it tells me to reset phone. I did but same message. What should I do??
Here's my phone: Cherry Mobile Omega HD (IQ6A) / Xolo A1000 / Alps H100
Android JB, Custom ROM, Rooted, TWRP
5"
8Gb External

Wrong Device forum Bud.

4.3 General wiping and preparatory instructions - Sprint Galaxy Note 2 L900 all ROM's

I was happy as a lark with TWRP. But 4.3 happened and it is a new process. There are variations, here is one way to get your phone and 4.3 to play nice together. I'm on Sprint Galaxy Note 2 and if you are coming to a 4.3 or 4.4 for the first time, or having trouble. Try this first! I give credits Below, but it's for all ROM's. "Google process stopped" is a common sign that this wasn't done. Or if it just hangs on the samsung screen... Btw it does seem like an eternity sometimes. Lol
General theory: skip to the next paragraph if you dont care. I've Googled and read. You should too. We are trying to clean and prepare your phone for 4.3. "Wipe" is not the same as "format. " We need to remove all the little pieces of data that may still be there from before. We need to start fresh. Also, the partitions sizes are different in 4.3. In general we need to clean.
PROCESS A is this link. Billard412 This is back to stock, completely cleaning your phone. It requires odin and a computer. If you want to try procees B alone, you can skip A and just do "process B" and see if that works. If you still have trouble, you know you need to do the full thing. Just a note, you might think it works, but then your nandroids don't restore.. Time for process A. Back to stock. It's good to do this once in a while to start fresh, also.
http://forum.xda-developers.com/showthread.php?t=2086769
Then install USE PHILZ recovery 6.07.9 (link below)
-Install philz. Some people have luck with TWRP , i didn't. I don't think TWRP works with 4.3
There is a newer Philz version, not sure all the bugs are worked out, use 6.07.9
One thing that might be confusing, the process A restore from billard recommends TWRP and I'm recommending Philz recovery. So best advice, although possibly confusing, is install TWRP, billard restore, then flash Philz. It's not any more work really. The back to stock will put you in a stock recovery. So you have to flash something. I was a TWRP fan too, but Philz has had less problems in 4.3.
1. You can follow billard 's instructions
2.there is a YouTube if you want to follow that in billards thread
or3 . Jlmancuso provided this to try and simplify the process:
a. Boot into download/bootloader mode.
b. Connect to pc and use odin to flash TWRP. Make sure you uncheck reboot and flash twrp in the pda slot.
c. Once flashed pull battery and disconnect from pc.
d. Press vol+ menu power buttons while inserting battery (yes it is difficult but can be done)
e. Now in recovery perform factory reset.
f. Flash this http://forum.xda-developers.com/showthread.php?p=36388145
g. Now reboot it will act/look weird but dont worry this is normal. It will reboot and take a long time to boot.
Now you are on stock mc2 (no knox anymore). Root using cf autoroot http://forum.xda-developers.com/showthread.php?p=33278464
Now use odin once again and flash your recovery again, this time Philz. Now you are rooted and have a custom recovery. Oh and you have a working phone again.
PROCESS B.
This is done before any ROM install and before any nandroid restore.
Preparation: BACK UP INTERNAL IF DESIRED, I WILL RECOMMEND WIPING IT in the next steps . NOT REQUIRED, BUT RECOMMENDED. You can move it to external, external doesn't need to be wiped.
In PHILZ recovery 6.07.9 (link below)
1. Mounts and Storage
Format / system​Format / cashe​Format / data​ Recommended optional. Format internal SD card
Format / data and /data /media (/sdcard) ALL INTERNEL SD CARD DATA IS LOST.​PREVIOUS IS NOT EXTERNAL, EXTERNAL IS "SDCARD1" which i would not recommend
2. Power Options > reboot recovery
3. Wipe cashe partition
4. Advanced > Wipe dalvik cashe
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
I would stick with 4.3 and Philz backed up things. Don't restore something from before. Neither a 4.2 rom or a TWRP backup. Once you know you have got this process down, then try / do those sorts of things. Philz is supposed to be able to do that, but let's keep it simple until you have this figured out.
If you want to try process B first only , it may be all you need. But if it doesn't work, do all of it.
I hope this helps - LINKS & CREDITS in next post

4.3 general wiping and preparatory instructions
LINKS
same as above Billard412 back to stock - http://forum.xda-developers.com/showthread.php?t=2086769
alternate back to stock - Rwilco http://forum.xda-developers.com/showthread.php?t=2591898
Philz Recovery Thread - http://forum.xda-developers.com/showthread.php?t=2552653
On the Philz recovery site the "L900" looks more like "l900" and is confusing - so here is a more direct link - select 6.07.9 http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900
TWRP http://teamw.in/project/twrp2/117
To get root- one option is CF Autoroot-
[SPH-L900] CF-Auto-Root
http://forum.xda-developers.com/showthread.php?t=1956180
WIFI FIX just in case. Flash in the PDA tab of Odin http://d-h.st/6qX
If you want to change modems i use this (not required / optional) - http://forum.xda-developers.com/showthread.php?t=2537713
General
I am not trying to take credit for anything. Notice how none of this is my work. Just hoping to pull together and clarify this process. Others my post different ways, and you can try other ways, but if it doesn't work, use this process exactly. It works for many. If you want to post that you tried another way and it didnt work, you are welcome to, but then my reply will be to try it this way...or i wont reply. I just had to keep typing this over and over to many, and i figured I would put out a detailed version. This works. (you know the drill, its your phone, not my responsibilty, of course)
CREDITS AND ROMS
I picked up a lot of this process from Lorjay589's thread. His OP pointed me at the Billard412 back to factory
jlmancuso has posted refined and explained this process 100 times as well.
this is for SMOOTHEST ROM, CUSTOM ROM, SYNERGY ROM, DIGIBLUR ROM, FTW ANNIHILATION, ROM AND MANY OTHERS.
therfore jlmancuso, chaz187, ianmb, digiblur, lorjay589, rwilco12, phil3759, fryingpan0613, jimmydene84, cbucz24, wwjoshdew, agent soap AND MANY OTHERS.

constructive criticism is always welcome i have a tough skin, just be nice and don't hold back to let me know. i am not that knowledgeable, this is my first thread. Just been following some 4.3 threads for a while and saw a recurring problem.

Very nice guide Cole
Sent from my SPH-L900 using Tapatalk

Reserved

Darn it I want a reservation too!!
Thanks now I have a thread to link to instead of a single post.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Very nice tutorial. U nail all that we need to do for a smooth install
Thanks
SGNote2

Any reason why we should not use the latest version of Philz Recovery version 6.15.4?

justppc said:
Any reason why we should not use the latest version of Philz Recovery version 6.15.4?
Click to expand...
Click to collapse
Some people have just had some problems when using the new version, therefore the previous version is more reliable. Better chance of everything working. Once you have your phone running smoothly using this process, you are welcome to try it. If you have problems... Revert back.
Start with post 87 of the Philz thread, if you like.
http://forum.xda-developers.com/showthread.php?t=2552653

Thanks, this resolved an issue with 'Inconsistent System UIDs"

KNOX with options A/B
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks

Dedline said:
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks
Click to expand...
Click to collapse
Process A completely wipes your phone and resets it to stock. B is just general wiping process when flashing a new rom. You shouldn't have a Rom on your phone when you are done with either. (other than the one backed on you external sd)
Head on over the the Ballard thread to read more about process A

justppc said:
Thanks, this resolved an issue with 'Inconsistent System UIDs"
Click to expand...
Click to collapse
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?

mr.pope said:
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?
Click to expand...
Click to collapse
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.

justppc said:
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.
Click to expand...
Click to collapse
alas, I have tried that as well. I finally made some headway and think I have it. I had to fix permisions for all apps using Rom Toolbox Lite Looks like that has fixed it. Flashing forward as I type.

Just a bump to keep this where everyone can see it.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Gotta try this on my note 2
K
Sent from my SPH-L710 using xda app-developers app

Just a reminder

Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!

Lyvewire said:
Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!
Click to expand...
Click to collapse
Philz is the only way to go when choosing a recovery. Twrp will not backup or restore mk4 properly and wont woek correct with 4.4 aosp either. When ypu do your first backup choose custom backup and backup everything but Efs. When that is done go back into custom backup and only backup efs (it must be done by itself). I would then suggest copying both backups to a pc or cloud storage for safe keeping.
Sent from my SPH-L900 using XDA Premium 4 mobile app

[Q] Multiple problems after flashing Stock

Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?

Reflash in Odin.
Make sure you have the correct stock rom. If you flash the "md5" you may have flashed the wrong thing. The md5 is not tge firmware, that is just the code that verifies your firmware file is not corrupted.
If your old apps were still there, you flashed the wrong thing. There is no way to flash stock firmware in odin and not wipe the data partition.

You are correct then
Yeah, I flashed a tar.md5 in Odin. It gave me a new ROM but all my apps are there. After all that, I still can't go to recovery. I tried using the terminal and ROM Toolbox to go there, both didn't work. Can I just leave it as it is and find a way to recovery or is the only way to go to bootloader and flash a correct file to get to recovery?

Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually

serio22 said:
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
Click to expand...
Click to collapse
It depends on what you ate flashing.
If you are flashing a full stock factory image it will wipe user data. If you are just flashing a system partition it won't.

Essem G said:
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Click to expand...
Click to collapse
Fkash twrp and format system, data, cache and preload and install a deodexed stock os

g7755725 said:
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
Click to expand...
Click to collapse
Also this. This gives you more control over the whole process

Skipjacks said:
Also this. This gives you more control over the whole process
Click to expand...
Click to collapse
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?

Essem G said:
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Click to expand...
Click to collapse
The first post of any customized stock rom will tell you if its deodexed. If it doesn't say it...its not.

@Essem G:
Any updates for us? I'm following this thread because I have similar problems with my WiFi not working after upgrading from 4.2.2.
Any luck getting TWRP flashed?
Also I believe that the stock firmwares do come as tar.md5's, as in the file: M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 from ShinySide's stock firmware thread.
As for the WiFi issue, from the hours of reading I've done it looks like this problem occurs when you upgrade your firmware, but it no longer matches the bootloader. Such as bootloader (Baseband) showing MDL, but Build Number showing NH7, NK2, etc. What does your show?
This thread may be of use to you when you get back to a working ROM. Good luck!

@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks

Essem G said:
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Click to expand...
Click to collapse
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery

g7755725 said:
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
Click to expand...
Click to collapse
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks

Essem G said:
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks[/Q] it should
Click to expand...
Click to collapse

@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?

Essem G said:
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Click to expand...
Click to collapse
Have you tried my gamerrom Ultimate 1 its basically stock touchwiz of if Official NK2 M919UVUFNK2 with stweaks and no bloatware here is the thread gru 1 is in.the botyom of the thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/stock-os-gamerrom-ultimate-2-touchwiz-t3078467

Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs

Essem G said:
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Click to expand...
Click to collapse
If you're trying to go back to complete stock then just Odin NK2 firmware. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508 I used the NK2 from here about 2 days ago to go back to stock.

Stuck Bootloop

I unfortunately can not provide some sort of logs but I can tell some sort of history.
So I have some rom that I installed ages ago I believe the zipfile says note4our.
Anyways I dropped my phone a couple weeks ago and noticed that my phone was slowly acting up, as in random reboots, and sometimes it would restart into download mode. Sometimes it would just hang at the very first screen that says kernel in the top left. Luckily I was able to go into recovery and clearing caches seemed to sort me out temporarily. Last night the phone randomly rebooted and has not been able to boot up at all. Just constant bzz bzz reboot lol. I am still able to go to recovery mode, however when I plug it into my computer it seems that I can't get any files on or off via a drag and drop, and I also can't use windows to move files between an sdcard mounted in the phone to the internal storage either. Which is weird since it windows can list all of my files but it can't open it either. I do not have read-only checked. When I try to move files windows says something about the device having stopped hence I can't move.
So I'm guessing there's no way for me to recover my files later? Or will my twrp backup of the just the data portion suffice? Any other things I should try before I go full nuclear and do a complete wipe and try a fresh? Normally I would use this situation to update as well but I figured I would do that after my reflash since I'm sure I would need to update my bootloader or something and I'm still trying to potentially salvage my files if I still can.
So yeah it's been over a year or so, and I need my hand held at this point. Please and thank you and I'll do my best to provide anymore information after work tonight.

That locked USB is av ***** ain't it. I've been getting that for the last couple of updates to. It wont stay locked. It just needs enough time to make sure the build stays the same. Pull the battery put put it back in and wait a few minutes. It still unlock again.
Sent from my SM-N910P using Tapatalk

@bryyando
A possible scenario may have been your SuperSU updated to systemless root in Google Play and later you factory reset? That would cause you lose root and fail to boot with existing custom kernel.
If that happened, you could flash the SuperSU zip and it should boot again. Here's an updated version of the original system based SuperSU that the ROM had:
http://forum.xda-developers.com/attachment.php?attachmentid=3969639&d=1481813000
If that doesn't work, you could try to flash the ROM without wiping data. Or you could backup data partition but I think you need to include more than one partition to make it valid (but that may only pertain to titanium backup; I'm not sure). Since recovery is working, you could include that partition.
If it comes to trying to the nuclear option, I'd recommend flashing the linked SuperSU after restoring TWRP backup of data.
Maybe one of those options works but I suspect your issue is loss of root. It's a must have with custom kernel. Otherwise, no boot.
If you do boot and recover without losing data, make a backup. Valuable time saver to have a current backup.
Sent from my SM-N910P using Tapatalk

@samep
So I totally remembered about dirty flashing while at work and proceeded to do that when I got home, before I read this thread. The phone appears to marginally do better as it is rebooting after it at least optimizes some apps... Also I for reference my ROM version is 1.1 and twrp is 2.8.7.0 lol
And just my luck my spare note 2 seems to have an emmc failure...

@samep
Managed to do a twrp backup of my data partition. Oddly enough my phone rebooted the first time, but made it the second time. For the hell of it I cleared just the caches and then did a bootup. Each time it had less apps to optimize and eventually I made it past the lockscreen, my phone alerted me to my missed messages and then would do a bootloop again. I did notice that the screen had weird pink lines on the bottom right before it vibrated and restarted. Still can't save files onto computer while connected in recovery mode. I luckily found an sdcard that should have enough memory for me to move my pictures and notes that I'm trying to save. Then I'll do an advanced wipe this time. Flash my 1.1 rom, then the supersu you provided and see if it works. If that doesn't then I'll odin up to PE1? Or whatever the new roms need and see if my phone crashes still while on stock and then go from there. Did I miss anything?

bryyando said:
@samep
Managed to do a twrp backup of my data partition. Oddly enough my phone rebooted the first time, but made it the second time. For the hell of it I cleared just the caches and then did a bootup. Each time it had less apps to optimize and eventually I made it past the lockscreen, my phone alerted me to my missed messages and then would do a bootloop again. I did notice that the screen had weird pink lines on the bottom right before it vibrated and restarted. Still can't save files onto computer while connected in recovery mode. I luckily found an sdcard that should have enough memory for me to move my pictures and notes that I'm trying to save. Then I'll do an advanced wipe this time. Flash my 1.1 rom, then the supersu you provided and see if it works. If that doesn't then I'll odin up to PE1? Or whatever the new roms need and see if my phone crashes still while on stock and then go from there. Did I miss anything?
Click to expand...
Click to collapse
Since you mentioned a ROM with Xposed framework, I hadn't considered that Xposed framework may have gotten corrupted causing the reboots. You're on an old ROM. I'd update and not worry with it.
I'd recommend backing up your data that you'd like to keep, wiping internal memory, format data and factory reset, Odin PE2 and clean install freeza's Note 4our beta 3. Kernel and ROM are based on PE2.
The ROM is here but this link points to a known issue you'll need to fix Xposed installer to update or install Xposed modules.
http://forum.xda-developers.com/showthread.php?p=67383249
But if you're not interested in Xposed at all, you may consider another ROM. I'd recommend being on the right update as you're trying to do already. You may not have noticed freeza updated to PE2 if that was your goal.
If you prefer Xposed framework and custom modules, freeza offers a quick and custom way to get there with minimum flashing.
Sent from my SM-N910P using Tapatalk

@samep
I think we might be on the right track with a potentially corrupted xposed. I did notice that some of modules would stop working sometimes. Also what may be potentially interesting is that my phone does reboot when I am in recovery mode. Although xposed probably wouldn't cause that? I do think my phone is more stable in recovery mode as it seems is running for longer periods while I'm in there vs trying to boot up in which I barely make it past the samsung boot animation. I am slowly moving folders over so I have both a twrp data backup as well as the original files, it is just taking a long time as I am not normally at home to do this. On top of that ODIN flash, I noticed that twrp has been updated to 3.0.2.0 I'm guessing I should update that as well. I adb load the img file correct? The tar is just compressed for easier download?

bryyando said:
@samep
I think we might be on the right track with a potentially corrupted xposed. I did notice that some of modules would stop working sometimes. Also what may be potentially interesting is that my phone does reboot when I am in recovery mode. Although xposed probably wouldn't cause that? I do think my phone is more stable in recovery mode as it seems is running for longer periods while I'm in there vs trying to boot up in which I barely make it past the samsung boot animation. I am slowly moving folders over so I have both a twrp data backup as well as the original files, it is just taking a long time as I am not normally at home to do this. On top of that ODIN flash, I noticed that twrp has been updated to 3.0.2.0 I'm guessing I should update that as well. I adb load the img file correct? The tar is just compressed for easier download?
Click to expand...
Click to collapse
The .img version of TWRP is for updating within TWRP or Flashify. You'd need the .img.tar version for Odin. Flash in Odin after flash of stock tar with Odin defaults. Use AP mode for both flashes in separate Odin sessions, closing Odin when done with each flash.
For TWRP flash, uncheck only the auto reboot option in Odin, once flash is started, wait until you see success, 0 failed and then pull USB cable and battery. Wait at least 1 minute and reinstall battery. You must boot directly into recovery on initial boot after TWRP flash or you lose it to stock recovery; it can restore itself if you fail to do it right.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Did you mean your phone runs longer in safe mode rather than recovery? If safe mode isn't stable, then yes, it's time to take advantage of the update. I think you're doing the right thing.
Sent from my SM-N910P using Tapatalk

I have not tried or was aware of safe mode. I meant that the phone would sometimes reboot while in recovery mode as well.
samep said:
The .img version of TWRP is for updating within TWRP or Flashify. You'd need the .img.tar version for Odin. Flash in Odin after flash of stock tar with Odin defaults. Use AP mode for both flashes in separate Odin sessions, closing Odin when done with each flash.
For TWRP flash, uncheck only the auto reboot option in Odin, once flash is started, wait until you see success, 0 failed and then pull USB cable and battery. Wait at least 1 minute and reinstall battery. You must boot directly into recovery on initial boot after TWRP flash or you lose it to stock recovery; it can restore itself if you fail to do it right.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Did you mean your phone runs longer in safe mode rather than recovery? If safe mode isn't stable, then yes, it's time to take advantage of the update. I think you're doing the right thing.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse

samep said:
The .img version of TWRP is for updating within TWRP or Flashify. You'd need the .img.tar version for Odin. Flash in Odin after flash of stock tar with Odin defaults. Use AP mode for both flashes in separate Odin sessions, closing Odin when done with each flash.
For TWRP flash, uncheck only the auto reboot option in Odin, once flash is started, wait until you see success, 0 failed and then pull USB cable and battery. Wait at least 1 minute and reinstall battery. You must boot directly into recovery on initial boot after TWRP flash or you lose it to stock recovery; it can restore itself if you fail to do it right.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Did you mean your phone runs longer in safe mode rather than recovery? If safe mode isn't stable, then yes, it's time to take advantage of the update. I think you're doing the right thing.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I won't say that's terminal. There's been two occasions that I had to flash TWRP again because it was buggy but the phone was otherwise fine after that.
It's possible you have more than one partition corrupted. I wouldn't worry unless you have trouble flashing with Odin.
Hopefully once you're done with Odin and flash the new ROM, you're back to normal.
Sent from my SM-N910P using Tapatalk

Seem to be having problems with ODIN, hangs when I load up the tar for a bit and then when I hit run it says 0 succeed 0 fail. Are there separate drivers I need as well?

bryyando said:
Seem to be having problems with ODIN, hangs when I load up the tar for a bit and then when I hit run it says 0 succeed 0 fail. Are there separate drivers I need as well?
Click to expand...
Click to collapse
You need the Samsung driver. Google Samsung SM-N910P support and you should find it. Like this:
http://www.samsung.com/us/support/owners/product/galaxy-note-4-sprint (scroll down to driver and agree to terms to download)
On your tar, verify the md5 against the zip. If good, extract the tar.md5 from it. When you load that into Odin AP slot, expect about minute delay to verify it. I usually wait before plugging my USB in to download for that reason. You shouldn't try to start the download before it's ready.
When you plug-in in download mode, also verify your phone is added (highlights when added) in the COMM window.
Sent from my SM-N910P using Tapatalk

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/a/d1EyB
This is what I got, and same thing. Doesn't really get past the powered by android screen. Maybe sometimes it shows the sprint logo. Guess my phone is dead?

@samep
There was this too.

bryyando said:
@samep
There was this too.
Click to expand...
Click to collapse
So it flashed and booted?
I didn't see the whole Odin log to verify your phone was added as COM. You should see a progress bar lb the phone screen and some warning like writing; do not disconnect.
Sent from my SM-N910P using Tapatalk

Here's what it said about my twrp install, except it never boots up...

Yeah the rom tried to boot but then it would just get into a bootloop again.

bryyando said:
Yeah the rom tried to boot but then it would just get into a bootloop again.
Click to expand...
Click to collapse
Did you factory reset? If not, try that in stock recovery now and reboot.
Sent from my SM-N910P using Tapatalk

Tried it again,
Did a factory reset but still bootloop. Was able to get into recovery mode tho
samep said:
Did you factory reset? If not, try that in stock recovery now and reboot.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse

bryyando said:
Tried it again,
Did a factory reset but still bootloop. Was able to get into recovery mode tho
Click to expand...
Click to collapse
You did the wipes I suggested in post #6? I've seen that happen when internal memory isn't wiped for users with CM coming to back to stock. I've seen it happen with nand erase all for some users but you didn't do that, did you?
When that happens for those doing just the nand erase all without tar and PIT with repartition, the Odin flash doesn't take right. Just boot stock recovery, factory reset and wipe cache partitions and power down , pull battery for at least 1 minute and reinstall, boot to download mode and flash stock tar with Odin defaults. Let it auto boot.
Even if you didn't have CM, I'd consider that before proceeding. I'd even flash TWRP and wipe internal memory if that was skipped as a prep in the previous stock tar flash. I'm not sure if stock recovery factory reset is any different than TWRP but it seems to have made a difference for some users that had flash issues with Odin in the past so consider that before wiping with TWRP.
Try stock tar prep and install without PIT or repartition or nand erase all (Odin defaults only). Hopefully that helps to boot. I'd need to know if you already wiped internal memory before suggesting the PIT. There is s thread with links already posted but it's less of a last ditch effort fix but rather more of a diagnosis for hardware failure. Small chance it works so most likely a bad flash or corruption only fix. Most of these failures seem to indicate hardware failure, IMO. Dropping it hard enough could possibly damage hardware or corrupt. I don't know as fact but I'd think either is possible. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk