Develop Bugs

Helllllpppp

I just did the regedit trick and downloaded the froyo update but when i go into the phone i just keep getting error messages about launcher not loading etc.
I have factory resent and cleaned cache but still wont work. I cant download the old updates through kies any more how do i get it back to how it was with the old software? I am stuck and freaking out lol

guess you have to flash an older FW like JM2 with Odin ... check out FAQ in this section (sticky).

I really stuffed it up now i somehow flashed a captivate rom onto it from atnt and now it wont even go past the white screen. I cant use the 3 buttons to get it into recovery mode or download mode. And the computer is not recognising the phone. Have i stuffed it for good?

try volume up + volume down + power
the AT&T / Tmobile version uses that combination
instead of Volume down + home + power

Go into recovery mode and factory wipe if you have issues such as services force quitting.

livefree2x said:
I really stuffed it up now i somehow flashed a captivate rom onto it from atnt and now it wont even go past the white screen. I cant use the 3 buttons to get it into recovery mode or download mode. And the computer is not recognising the phone. Have i stuffed it for good?
Click to expand...
Click to collapse
Captive rom onto Galaxy phone? Curious how did you do that as these two are two different phone. You are not the first one but reading from the posts from people who did the same mistake, I'd say you have bricked it. Sorry to be the bearer of the bad news

i have
I have tried all combinations of keys and it just keeps loading up with white att international phone and then that screen just flashes every few seconds and doesnt go any futher. It wont go into downloadin or recovery.

im thinking of doing the update
did you do anything eles besides the update to cause this

Look, the only possible way to brick the phone (that i know of) is to flash others phone rom(Captivate being the usual suspect) into Galaxy.
This changed the button combo to enter download mode in Galaxy (as Captivate has different combo for download mode) so it is not possible to enter the download mode and reflash. Therefore you are stuck and cant do nothing Im afraid
Just curious , why so many people flashing Samsung Captivate rom into their Galaxy?
Some other examples
http://forum.xda-developers.com/showthread.php?t=749546&highlight=captivate
http://forum.xda-developers.com/showthread.php?t=751712&highlight=captivate
http://forum.xda-developers.com/showthread.php?t=767420&highlight=bricked

ok with that said then will the JPC update work on the bell galaxy s GT-I9000M

Bobler420 said:
ok with that said then will the JPC update work on the bell galaxy s GT-I9000M
Click to expand...
Click to collapse
Since it is the same Galaxy S i9000, I'd say It'll work. But I could be wrong To be on the safe side, you could ask for other Bell Galaxy users' feedback. Dont know about Bell, but Romanian Orange users are getting their phone locked after the flash.

usualy when something wrong w/0 3 buttons
usualy when something wrong w/0 3 buttons the phone rebooting in recovery mode itself to reboot it in download mode install correct adb drivers and use command "adb reboot download"

decided
I have just decided i am going to take it to one of the local Samsung repair centres i explained it over the phone and they said they could fix it for $49.95 or they could try and push for warantee but i told them i would just pay it will take longer for them to apply for warantee get rejected and then i pay anyways.
I miss it already i had to go back to my nokia N95 which was from a few phones ago now lol

i think the benfiets can wait till the official release ryanza lagfix fix all the lag problems that i had how important is flash really use your computer

Please explain exactly where you got the rom from so we don't make a similar mistake.
I'd pay the 50 too instead of waiting weeks and weeks :\

I got
I got the original rom through samsung kies using the reg edit trick that was shown in one of the threads. After a factory reset and a cleared cache it loaded up but started coming up with all these pop ups that things wont load and need to be forced shut etc.
So i decided to just flash it back using Odin but at 12 at night and in a panicy state thinking i have stuffed my phone for good i clicked on a captivate rom without looking at the heading of the thread that a link took me to for the galaxy s.
But as i said before for 49.95 to get it fixed is easier then me trying all these other things and getting in more of a panic about doing worse things to it. I assume it will be easy for them to fix it. A friend said he had a nokia he bricked where USB wasnt connecting and the screen wouldnt come on etc and they just used a computer that does something and fixes it.

got
Just got the phone call they managed to fix my galaxy for $49 and getting it back tomorrow oh how i have missed it i had to go back to a old old phone the nokia 95 lol.

[Q] SGS2 Odin Question

During an attempt to flash a rom using odin to my rooted sgs2, odin crashed and closed before it was finished. I tried restarting odin, wouldnt see phone.
Removed battery from phone, reconnected to odin and tried using the one click odin to reflash back to stock. Also tried using odin with other roms to flash back.
Heres my problem.
When i power on the phone, it says the Galazy S2 i9100 for a few seconds, then just turns off.
I can open odin, or odin one click, plug in phone, shows me yellow w/com and added. I click start, it gets to Setupconnection and then just sits there.
I have tried
- Different roms and both one click and normal odin.
- Different usb cables
- Different usb ports
- Multiple computers
Is there any way to get past this? God i hope someone can either point me somewhere or help me out.

Reinstall Samsung Kies to your laptop or pc so the proper drivers are re-installed. Once complete with that install, plug your phone into the pc and put the phone into USB mode, hopefully the pc will recognize your phone and install the NEW DEVICE drivers after a few moments. Depending on your pc, sometimes it takes many seconds for your pc to recognize and bring up the drop down menu for the newly recognized drive. BE PATIENT. If the pc does recognize your phone, start Odin again. If Odin also see's your phone, which it now should, you should see a COM:# connection in the ID:COM box of Odin. Doesn't matter what COM # is, as long as something is there. You can now use Odin because it see's your phone. Once you start Odin flashing, make sure not to disconnect anything until you see the upper left GREEN PASS box in Odin. Once its GREEN with PASS in that box, you're finished. You can d/c your phone from the pc and the phone is probably rebooting anyway.
OFC, if your phone will not stay power'd up, all of the above is for nought. Wish I could be more helpful.
Keep in mind that I do not intend to insult intelligence but everyone has limits in experience and I always try to explain in the simplest way I can. No disrespect intended.
Good Luck!
R

Thanks for the reply,
How am i supposed to put the phone in usb mode when i cant boot it?

That does create a problem, I would do some research on a USB Jig for your phone. Search at eBay for: Samsung Galaxy S2 Epic 4G Touch USB Jig
I'm not sure if this will help a phone that will not power up but it does have its uses for Root'd phone especially using Odin to flash and to remover that nasty YELLOW Triangle that comes from ROOT ROMS that are unsign'd.
Wish I could help you further.
R

Scribes said:
Thanks for the reply,
How am i supposed to put the phone in usb mode when i cant boot it?
Click to expand...
Click to collapse
Try to put in download mode if not try a jig ... If that fails it's sprint or jtag
Sent from my SPH-D710 using xda premium

It does power on, basically shows the sgs boot logo (black backgroud w/ white text) then goes dark, but its actually still on cause it gets hot.
I can get it into download mode and i can get it into the android recovery.
Theres gotta be a way to recover with an update.zip from the android recovery via the sd card........

There you go, you have two of us saying about the same thing. Just make sure you get the correct JIG if you go that route. It's like $2.00 and arrives from China in like 2 weeks.
http://www.ebay.com/sch/i.html?_fro...e+for+Samsung+Galaxy+S2/i9100/i9000/T959/i897
---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------
humm, an idling phone shouldn't get hot. That tells me you've got something going on. I think you just progress'd passed my pay grade my friend.

Heres another thing, as i mentioned in my first post.
The boot logo says i-9100....
and this is a sprint phone, isnt it a d710?
So im gussing in my late night haze i screwed myself by loading an i9100 rom/bootloader/whatever the hell that is.

Samsung calls it: I9100
Sprint calls it: SPH710
We call it: Epic 4G Touch

I see, so thats not the problem?
Im just gonna keep posting here while i mess with this incase i trigger someones mind for a fix.
(picture was here apparently i cannot post an external link yet. Was just a picture of device manager and odin sitting at SetupConnection)
The only way to get odin to see my phone, is if i open odin, put phone in download mode, plug phone in, then uninstall the com port via device manager, reinstall it. When i rescan for hardware changes, odin goes yellow as seen in the picture, i click start, then it sits at SetupConnection all day, so im guessing its losing the connection after it finds it.
My only solution here is via usb card i think, but i cant find a signed package. Cant someone just pull theirs from a stock phone? Why wouldnt that work?

Well, if you can get Odin to work, unroot to full stock with this:
http://www.megaupload.com/?d=ISD9AOP0

Right, getting odin to work is the real problem though i think.
Stuck at SetupConnection forever
This is super frustrating... going without a phone is impossible, work emails, texts, calls, ahhhh

..and there is no way to completely reload the entire phone using an update.zip off the sd card, one that is signed?
I know i used to do that on my droid, and all though i know this is a totally different game, i still have android recovery, one would think it would be possible if the package was signed. unsigned ones just fail, but at least i can attempt to run them from there.
If someone can find a way to do that, and it works for my phone, i will paypal $50

Let me see what I can find for ya....
I have searched two different Forums for a flashable unroot to stock with NO luck. Everything I found requires Odin. Sorry Buddy.

Correct me if I'm wrong but isn't the i-9100 a whole different phone??? Looking at the specs and release date I would believe so. Sounds like he did an ics update for a phone that wasn't the Sph-d710 or something..
http://www.gsmarena.com/samsung_i9100_galaxy_s_ii-3621.php
Sent from my SPH-D710 using XDA App

not sure, all I know it by is: SPH 710
~ via My Epic 4G Touch & XDA'a app ~

Have you tried just flashing a kernel only in Odin
Sent from my SPH-D710 using xda premium

You tried flashing ICS on your phone, didn't you? B/C I'm pretty sure that's why you are seeing I9100 while booting up. If that is the case, do a search here as there are multiple people who have done this, and none of them have been able to fix it.
Sorry, your only solution is exchange at Sprint if you can, or JTAG.

help
beezar said:
You tried flashing ICS on your phone, didn't you? B/C I'm pretty sure that's why you are seeing I9100 while booting up. If that is the case, do a search here as there are multiple people who have done this, and none of them have been able to fix it.
Sorry, your only solution is exchange at Sprint if you can, or JTAG.
Click to expand...
Click to collapse
does not mean he flashed ICS when you odin a kernel that is not signed ie with CWM you will get yellow triangle and it will say i9100 too ..... so does not mean he flashed ics ... if odin sees the phone on a com port he probably didnt .... try flashing a working kernel from our phone

I did attempt to flash ICS. I could find where i got it, but it was supposedly for the Epic 4G touch, aka sprint sgs2 variant.
I am a network and systems admin, i should have known better. I jumped the gun and got ahead of myself. I have rooted and put roms on the og droid, and the droid x, samsung is a different beast all together.
However, i went in to sprint the day after i did this, they looked at it, no insurance, no replacement warranty, they didnt ask me anything, and THEY determined it was a factory defect , they had me sign a sheet that said "After researching found phone to be a factory defect and the solution from SPRINT is to replace the phone. $37.41, and 22 hours later i had a brand new SGS2 in my hand.
They hadnt sent my phone in yet. I honestly am not sure if they are going to be able to tell if i did anything to it or not, i may have just hosed the bootloader enough that odin wont connect, so they probably will have to use something like jtag in house to reflash it, or replace the chip or whatever they do. Even so, if they do see that i was messing with it, and say it voided my warranty, i have a signed receipt showing my payment and agreeing to pay for the replacement at $37.41, and that THEY determined the flaw. My brother in law is a lawyer, so i asked him, because i was curious if they would look at my phone at the service center or hub or whatever, and determine it was my fault. He assured me they could try, but it would all fall back to the employee who had me sign the agreement, so even if they dont like what i did, they are beyond doing anything about it.
I doubt they will even notice it, im sure they will try to boot it, then just flash it or however they do it.
Either way, im not worried anymore.
So...someone wanna point my idiot ass to an actual good rom, with a good method, that works for my phone? lol. I cant stand touchwiz, huge icons and cant replace them ....wtf is that all about.

***Emergency Thread*** Here To Help!

I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!

In case of emergency!

Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?

Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2

...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.

Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app

lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.

Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.

I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.

heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download

Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.

Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!

frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2

Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!

frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2

Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing

Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!

http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?

Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)

ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2

[Q] Bricked Samsung Galaxy s4. Help!

So I just wanted to flash omega rom onto my T-Mobile i9505 galaxy s4. It worked, but the wifi didn't work, and it said that I needed to flash a file through odin. I flashed the file, but an error occurred in odin. Then, I unplugged my phone, and booted it into twrp recovery. All of a sudden, it asked me for a password, which I did not set. So I hit cancel, then did a wipe of the cache and user data. I then tried to go and flash an old rom, but all of my microsd card files were not there! The folders were showing up, but not the files. Then I tried to boot my phone and it wouldn't boot at all. After trying to install a stock firmware through odin, the phone turns on for 2 seconds, then shuts off. I can't get into recovery anymore either.

First, do you mean you have a T-Mobile M919 S4 and you tried to flash an i9505 ROM?
You are able to, but I want to just clear things up.
Let me write a little something, then we'll see if we can get you back to where you want to be.
- Sometimes when things don't go 100%, you gotta take a deep breath, step away and then go over the steps you took to get to the point of where the issue started. When in doubt on what to do next, youccan read around the threads on xda and other resources. After doing a little research and you still have doubt, just ask questions by posting the issue likeyyou're doing now.
The natural reaction is to fix the issue, and to do this and that without being sure. The combination of the latter with a little panic and perhaps not enough patience, can make matters worse. I'm not saying all of the above pertains to your situation, but some of the comments may, as they have to me during certain situations. Anyway, something to keep keep in mind for the future
Now to the issues at hand.
Can you get into download/ODIN mode?
Power down the phone and pull the battery.
Wait 10s and insert the battery but Don't power on the phone.
Hold power button & volume down button at the same time until the screen turns on.
When you've read the above, let me know if you're able to get your S4 into Download/ODIN mode.

Fixed
The problem was that the phone was just completely out of battery, and I was trying to flash the stock firmware onto it but it could not boot into it because there was no battery. Charged it, and could access recovery and the phone booted! Yeah I guess I wasn't patient and made a simple mistake. OP, Please close thread thanks!

bob10123 said:
The problem was that the phone was just completely out of battery, and I was trying to flash the stock firmware onto it but it could not boot into it because there was no battery. Charged it, and could access recovery and the phone booted! Yeah I guess I wasn't patient and made a simple mistake. OP, Please close thread thanks!
Click to expand...
Click to collapse
Ah, :good: to hear.
I sometimes forget to add that step and another into my tutorial/how to posts:
- Prior to ROM installation, please make sure you have at least 50% battery charge available.
- Please check your usb cable to be in good working order.
The above are 2 reminders are a of couple of the most overlooked steps prior to flashing ROMs and other associated goodies

Note 4 either won't start, or has random reboots that make it no longer start

Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.

justintworley said:
Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.
Click to expand...
Click to collapse
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.

Trex888 said:
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.
Click to expand...
Click to collapse
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart

justintworley said:
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart
Click to expand...
Click to collapse
I suppose this is a long shot, but are you running on the original or an old battery? It's possible that a bad battery is causing the reboots. I was back and forth to the Sprint store about 4 times in one week. They first tried flashing the firmware. (Yeah, I could have done it, but I have insurance.) They sent me home and on the way my phone rebooted itself. I got a replacement Note 4, but it started getting hot, then also rebooting. They "let" me upgrade to a Note7, which I loved. I had to give it back even though it was from the new, supposedly safe batch. At this point, I couldn't even get the Note 4 to boot at all. Boot loops, or would boot into download mode. Couldn't do anything with it, except pull the battery. Got a third Note 4, but also ordered a new battery pack from Sprint. They were and still are, only $24.95, with free shipping! You get a new battery, an external charging unit and a carrying case for the battery. (You have to use your own charger.) This finally fixed the problem. I had two batteries when I ordered the new one. I'm pretty sure one of the older batteries was defective, even though it wasn't bulging. I'm still using the other one that's also older, even though it is bulging a bit. It charges and runs fine. No over-heating. So, my problem was a combination of a defective battery and a couple of bad phones. The other thing was some of the previous firmware seemed to make some Note 4s run hot or get hot while charging. Things are much better since PG1. YMMV.

I had this issue and sent my phone back to Samsung THREE TIMES, I thought I bricked my phone from custom rom.
Turns out it was my battery. Sounds dumb, but true. Strangely even with battery out, I was having issue. Once I put in new good battery issue resolved.

I had that issue on my pc and my note. I had a creepy stalker in full control of my device (which basically was a virtual machine). I could tell when I was on the right track to get rid of him because it shut me down. I can't say that's what's going on with you but it is a thing.
Sent from my SM-N910P using Tapatalk

Note 4 batteries are dying for lots of people anywhere from 18 months to just over 2 years, and the symptom is often fail to boot, boot loops, etc. As piggynuts said, it's not logical, but it's true. It happened to me, and when I replaced the battery, everything was fine.