Just got my used t-mobile note 2 on monday.I am having issues with the phone where the screen will start scrolling on it's own and keep trying to launch media hub or the weather widget and then the screen eventually freezes and won't respond.I have downloaded the emmc program and my phone doesn't have the defective chips.I have done 2 factory resets and the problem still persists and happens as it is being reset.Any one know what could be going on?If i leave the sim out the phone works fine though.
Best guess water damage. Check the tabs. Also get a new sim.
travispittman said:
Best guess water damage. Check the tabs. Also get a new sim.
Click to expand...
Click to collapse
Did another factory reset but before that deleted some apps i had downloaded and made sure to disable samsung media hub,gps and the weaqther widget and so far the phone has been fine.
Is it factory rom and kernel or has it been messed with? I originally bought an s4. Connected it to a shady charger and changed the polarity of the board. It was hard to get to take a charge and wouldn't hold a charge for very long. Went to have it looked at by a tech. Before he knew what I was there for he offered to trade me for a note 2. He looked my phone over and we swapped. Usually when people get rid of a phone it is not because they upgraded but because something is wrong. I dislike buying used for that reason. I have had ppl try and pass off water damaged stuff and all kinds of randomness. I always boot reboot and reboot and used phone before buying, Keep them there as long as possible to see if something is wrong. Ask a lot of questions. Usually when you purchase a used phone especially an expensive one such as the note2 you want to get what you are paying for and not duped into paying a lot of money for some ones broken mess.
It's factory original rom and kernel.
same here
dukenukems said:
Just got my used t-mobile note 2 on monday.I am having issues with the phone where the screen will start scrolling on it's own and keep trying to launch media hub or the weather widget and then the screen eventually freezes and won't respond.I have downloaded the emmc program and my phone doesn't have the defective chips.I have done 2 factory resets and the problem still persists and happens as it is being reset.Any one know what could be going on?If i leave the sim out the phone works fine though.
Click to expand...
Click to collapse
This may seem silly, but have you tried to clean the screen with a microfiber cloth? This same problem happened to me (except the weather widget part), and after a spray n' clean, it all got fixed.
Well huys i was able to root my phone pretty easily but am still on the stock rom it came with.Will using other roms and stuff be a bit easy for me to install or will it be tough since this is my first rooting adventure.
dukenukems said:
Well huys i was able to root my phone pretty easily but am still on the stock rom it came with.Will using other roms and stuff be a bit easy for me to install or will it be tough since this is my first rooting adventure.
Click to expand...
Click to collapse
It's simple as long as you have the ability to read through threads prior to flashing. 98% of problems with custom software installs is due to lack of patience by the flasher. Read alot, flash a little is a safe way to get started.
Hastily spouted for your befuddlement
I've rooted it and have tryed 2 different roms already.Just sad that my note 2 still has the screen lock up allthough using spen remains fine.
Well guys my hone had started to lovk up even at the boot screen and didn't want to respond to the spen either so i went into recovery mode and dids factory reset with cwmr but after i rebooted my phone it was stuck in infinite boot loop.Just reflashed phone with it's stock rom image from this site using odin but my phone will only boot to the t-mobile 4glte screen and won't go any further.I have gone back into recovery mode and factory reset but still the same problem.Is my phone bricked?
dukenukems said:
Well guys my hone had started to lovk up even at the boot screen and didn't want to respond to the spen either so i went into recovery mode and dids factory reset with cwmr but after i rebooted my phone it was stuck in infinite boot loop.Just reflashed phone with it's stock rom image from this site using odin but my phone will only boot to the t-mobile 4glte screen and won't go any further.I have gone back into recovery mode and factory reset but still the same problem.Is my phone bricked?
Click to expand...
Click to collapse
Not sure if I am allowed to post links to other sites, but check out: galaxynote2root.com. max has a tutorial for almost everything! Also did you do a full wipe? Whenever installing a new ROM if you get stuck in a boot loop go back to recovery and do a wipe again, also wipe cache, and dalvik as well. Hope this helps!
Flashed thw original rom image with odin but the original will jsut hang at the tmobile splash screen and never fully boot.I was able to flash the phone with twrp with odin and was able to use twrp from my phone to reinstall the jedix20 rom which does install and been working since.No matter what i do with the original factory image it will always refuse to boot past the tmobiole splash screen.
Related
So I was rockin' my 4.1 rom earlier and listening to music when my headphone cord got stuck on my chair and my phone fell off my desk to the ground. Everything was still going but my touch screen stopped working. I hit the unlock (power) button and it would show the correct unlock screen but I could not slide to unlock.
I pulled the battery and ever since then my phone would not boot. Stuck in boot loops, etc. I tried restoring from Nandroid (even back to my 4.0.4 image) and it would get stuck on unable to load /data at the end. I eventually went back and installed Nexus Toolkit 7.0 on my home pc and proceeded to load the stock 4.0.2 back on and root. However, it still is stuck in a boot loop. I'm now at a loss of what to do. My sd card has already been wiped and my phone is still not booting.
I'm at your mercy if anyone can give me any direction - please!
jedil1c1ous said:
So I was rockin' my 4.1 rom earlier and listening to music when my headphone cord got stuck on my chair and my phone fell off my desk to the ground. Everything was still going but my touch screen stopped working. I hit the unlock (power) button and it would show the correct unlock screen but I could not slide to unlock.
I pulled the battery and ever since then my phone would not boot. Stuck in boot loops, etc. I tried restoring from Nandroid (even back to my 4.0.4 image) and it would get stuck on unable to load /data at the end. I eventually went back and installed Nexus Toolkit 7.0 on my home pc and proceeded to load the stock 4.0.2 back on and root. However, it still is stuck in a boot loop. I'm now at a loss of what to do. My sd card has already been wiped and my phone is still not booting.
I'm at your mercy if anyone can give me any direction - please!
Click to expand...
Click to collapse
Try restoring using ODIN
the process wipes all data, but since you said its already wiped that shouldnt be a problem for you.
IF it still doesnt work, then it isnt software, but rather hardware, and you should probably go get that fixed
good Luck
Return To Stock Using Odin:
http://forum.xda-developers.com/showthread.php?t=1620036
I have Verizon GN, can I still use ODIN?
jedil1c1ous said:
I have Verizon GN, can I still use ODIN?
Click to expand...
Click to collapse
Yes you can still use ODIN,
as ODIN is software for samsung phones,
just make sure you use the zerizon file ratehr than the sprint..
or there could be dragons ahead
but there will always be a way to return to stock
Although, i would use this, because it is mostly aimed towards Verizon Users..
http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-gsm.html
Sorry for assuming you had sprint..
I dont know what was going on in my head
I found the correct VZW version within XDA... thanks for the tip... I actually have it running right now (fingers crossed).
Good Luck,
hopefully you get your phone back online
Wolfbeef123 said:
Good Luck,
hopefully you get your phone back online
Click to expand...
Click to collapse
Unfortunately, even after using ODIN I'm stuck in the boot loop. It must be busted hardware. Guess I will have to use the Samsung warranty service. Stink.
jedil1c1ous said:
Unfortunately, even after using ODIN I'm stuck in the boot loop. It must be busted hardware. Guess I will have to use the Samsung warranty service. Stink.
Click to expand...
Click to collapse
If you got your phone from Verizon, try them first. Easier than dealing with Samsung directly
harveydent said:
If you got your phone from Verizon, try them first. Easier than dealing with Samsung directly
Click to expand...
Click to collapse
I actually bought it through Amazon and called them and they said go to Verizon even without the purchased insurance.
My phone looks mint though so I'm very hopeful that I will receive service from the Verizon store.
Does the lock icon show while looping? You might think about a shot in the microwave for 3 seconds (don't take me seriously.....well maybe)
good day.
chopper the dog said:
Does the lock icon show while looping? You might think about a shot in the microwave for 3 seconds (don't take me seriously.....well maybe)
good day.
Click to expand...
Click to collapse
I did flash lock it with ODIN... so the unlock icon does not show. It boots to the animation and then restarts after it shows for 5 seconds. I think the touch screen is malfunctioning and causing it to reboot.
Can you turn it off and then turn it on while holding volume down and up at the same time (i.e., can you boot into fastboot/bootloader?)
If so... it's not over yet.
However, if you dropped it it's probably hardware. But if you can get into the bootloader, at least you can lock it before bringing it in.
looks like your nand chip failed. had the same problem with my S2 and even a JTAG didnt fix it, had to send it to warranty to have the board replaced
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
I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.
machdown said:
I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.
Click to expand...
Click to collapse
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.
BCSC said:
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.
Click to expand...
Click to collapse
I entered download mode and dont see flash counter anywhere. I got the warning screen were you have the option to restart or download.
Ya I entered recovery and did a factory reset but nothing. Really cant do anything with charging port broken.
I sent it in anyways for repairs. Hopefully they just replace it
I'm having the same problem with my Gs3 with CM10 4.2.2 running. Thought this would help.
Sent from my SPH-L710 using xda app-developers app
Ok, so I got this phone from a friend who took it out of the box brand new and it wouldnt boot up. It would show the logo briefly and then just shut down.
So I thought I'd try to get into recovery and wipe + factory reset the phone. However I do get to this 3 option screen (recovery, fastboot, normal) but no matter what I choose it just shuts the phone down after a few seconds.
Then I thought I's just flash the phone. All appears to wor well and the flash is successfull. However the phone just won't boot.
I tried flashing different recover's, but they also never start, I always end up with the same 3 option screen as mentioned above.
So I thought maybe the flash wasn't successfull although it says so. So I tried to put in a custom logo. Now I must have screwed up making a bootup logo because the phone then went blank on me. So I flashed back another version custom ROM and it came back to its initial state again. Then I performed various types of formats on the phone. And yes, it would 'play dead' nicely as one would expect. After that a reflash would yet again bring it to its initial state.
I tried Philz and TWRP recoveries. Oldest and latest stock ROMS but this thing is driving me insane.
None of the other peoples complaint seem to match this phone's issue. Does anyone have a suggestion of what I could still try to get this phonne to boot ??
Took out battery already
Might want to add that I did open the phone up already and disconnected the battery a few times. No luck or difference afterwards either. It's like the phone lost its way and doesn;t know where to start loading its OS or anything from anymore.
RMA it, this sounds like a hardware failure.
BlueFlame4 said:
RMA it, this sounds like a hardware failure.
Click to expand...
Click to collapse
Just wanted to say thanks for your response.
I had quietly hoped that someone else may give me better news. However I appreciate you confirmed my suspicion.
BlueFlame4 said:
RMA it, this sounds like a hardware failure.
Click to expand...
Click to collapse
That's exactly what this sounds like. Hardware failure...could be that the initial settings for the phone weren't properly inputted or the board is just one from the many that failed. Had a previous brand phone Cubot and ThL that brought me the same 3 options and could never choose any since the phone shut off too quickly. Do as suggested and RMA it.
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.