I just got a T-Mobile Galaxy Note 4 from a friend of mine and there has been some serious reboots/random reboots on it. It was on 5.1.1 last I checked.
Issue:
-On stock battery, it still reboots. Using Anker right now and worked for a few minutes
-When I install an app or disable an app, it freezes then reboots--- when rebooted, it doesn't pass the note 4 logo, just keeps looping
Here's what I've done so far:
-Looked all over google and XDA threads (no bueno)
-Turned off Reactivation
-Deleted Cache/FOomat Data
1. Reflashed 5.1.1 firmware using odin= failed emmc: ABOOT
2. Reflashed using Kies 3.X via Emergency update/initialize. Waited a few minutes to place battery. It booted up!
2a. Ok, so it was working. BUT every time I install an app or disable an app, it freezes and I end up having to reflash via Kies.
Here's what I'm planning to do next.
-When my sim unlock code arrives, I'll unlock it, then the moment it is unlocked I'll flash TWRP and CM13, which I did before hand-but wouldn't boot for some reason... but maybe this time i'll have some luck
-I've only been able to flash using odin with the CF-Auto root, but not the AP file for 5.1.1 or 5.0.1, or NK4 4.4. (I'm downloading the oldest KK version to see if that works later)
What could possibly be the problem?
-Maybe failing hardware?
-Write issue?
-Is it the battery? but I've tried a new stock, and a new anker? loose wiring?
-T-mobile OTA update? Samsung Update?
I can't return it to Samsung or T-mobile since my friend gave it to me, his AT&T version works fine, just not this...
Calling all Note 4 Devs support out there! Please help, I'm thoroughly lost as a lvl.70 Android modder/enthusiast.
I'm having same issue and I've done pretty much the steps you've done. My issue is even more cuz I successfully flashed back to latest DOK2 my device was at 72 percent but kept rebooting at setup screen . so I left it alone for 2 weeks . now I saw yesterday they had ported MM so I rooted odined latest twrp and installed MM that took so long to boot it drained my 72% . now the device wont charge even turned off .
Sent from my LG-H901 using XDA-Developers mobile app
Might want to search for the Note 4 .pit file to flash along with Odin stock firmware. Flash BOTH pit and DOK2 tar files in Odin then when it completes boot to recovery and wipe both data cache then reboot. Hope this helps
EDIT
Here http://forum.xda-developers.com/not...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
Sent from my SM-N910T using XDA-Developers mobile app
Related
I was installing the DA Statusbar mod. Before I did that I back up my phone using CWM and Titanium Backup.
installed with no problems, I then rebooted. Home screen froze for a second and then showed me that my system.ui crashed. It kept doing that for a good 5 minutes. I decided to go back into CWM and restore my last saved state. I recieved an error installing the back ups (I have made 5 so far).
Now I don't really know what to do. I know I have to basically start from the beginning via flashing stock rom on odin. But how would I go about doing that? I can't seem to find the thread that explains this. =/
Thanks in advanced
SOLUTION HERE
You need to be much more specific. What's your recovery version? How did you backup/restore? Have you done this before? What's the error?
Use the unified tool kit to flash the stock rom.
I strangely cannot find a thread for the 9305 for stock roms =\
The stock firmware can be found on sammobile
Sent from my GT-I9305 using xda premium
To shorten the question and answers... If you could still boot to Download mode.
Flash your stock original firmware trhu Odin on your pc or download an exact model for your phone in SamMobile. From there you start a new... Root then re flash the cwm and so on...
If I understand this right you can boot to cwm and you can boot into the phone but the systemui fcs.
You can do a couple things here without having to reflash anything through odin. If you have your original systemui on the phone somewhere you can try and navigate to it with a root explorer then copy it into your system/app reboot and it should be as before, this can be tricky with constant fc's.
If you have a zip which has a systemui in it you can flash that in cwm and should fix the problem.
If you have a custom rom on your phone you can boot into cwm and flash it.
The fact that you have access to cwm and the phone boots but the systemui constantly fc's making the phone unusable means you have more options and quicker ways to get your phone working then going back to scratch and flashing a rom through odin
Sent from my GT-I9305 using XDA Premium HD app
Solution.
Basically I got stuck at the samsung boot logo for ages.
I am running CWM v5.5.0.4. I have done this before, sorry I wasn't specific, I was trying to multitask. I've attached a screenshot of my phone info for everyone to see.
1. I wiped data/factory reset.
2. Wiped cache partition.
3. Wiped Dalvik Cache
4. Battery Stats
Rebooted, still no luck.
I went into Download mode.
Opened Odin.
Downloaded " Param_Bin_I9305.zip - 612.14 KB" located in this post
Followed the instructions in that post.
rebooted.
Thought it didn't work but my capacitive buttons lit up. SUCCESS!
Saw my homescreen, I thought I would have needed to root again but I managed to get into CWM after rebooting.
I downloaded root checker....I saw that I still had root access.
Installed Pandoriam v6.
Now I am back to normal.
My CWM backup didn't save me, I don't really know why. Maybe I was using it wrong? The thing is It's worked with me in the past, but not on this device.
Is there anyone that could shed light on that issue? I'll try and back it up again. Do I need to repeat the backup more than a few times to register it to the device?
Not sure if this is the right place or not but seems to be a similar situation.
I have a month old S3 LTE that came with 4.1.2 . It has not been rooted or had anything done to it at all.
I found a thread that shows you how to unlock it but was not getting the final option . This I understood was because some of these phones needed to be downgraded .
I saw a procedure using odin and looked for a similar rom on Sammobile but could not see any for Orange UK so picked a random 4.1.1 Rom and flashed it.
This left me with a glowing Samsung boot screen so I tried another ROM and another ROM and finally when giving up choose a current 4.1.2 Rom for EE but that too is stuck at the same place.
Can you help me work out where I am or have been going wrong please?
The Phone is from Orange UK ( EE ) but there was no branding on it .
i also neglected to note the Rom that was on it
if you read the guides you will find out that you need to factory reset after flashing
Unfortunately as the phone is sitting at a glowing Samsung logo, I cannot factory reset. In fact I cannot do anything except keep throwing Roms at it, unless you have any other suggestions?
Sent from my GT-I9100 using xda premium
You can't get into recovery by pressing volume up, power and home?
Sent from my GT-I9305 using xda premium
did you try pulling your battery then trying recovery mode?
Sent from my GT-I9305 using xda app-developers app
thx natthewife
Pulled the battery . held volume up and home and dropped the battery in . Straight into recovery . ! All done now . Can hand over to my son so he can scratch it up drop it down the toilet or lose it on the bus . !
thx again
I rooted and installed CWM and Cyanogen 10.1.3 on by brothers Note, GT-N7000. He didnt enjoy it as some unexpected errors were coming up sometimes. Luckily i found the official Rom 4.1.2 N7000DDLSC_INU.zip through sammobile. Now My questions are:-
1. What must i do to completely remove cyanogenmod and clock work recovery.
2. Do i need some additional files like, kernel or bootloader or phone or csc (or will just all this zip to pda will install it)
3. What else should i take care of?
Please advice i want to completely return to official state
nothing much.. just the rom file you downloaded in tar.md5 format. Boot into recovery and factory reset the phone. then boot into download mode and flash the new rom..
But will that remove clock work mod.?
And will my device get recognised in kies?
Sent from my GT-I9500 using xda app-developers app
Yes
Now there's another panga. The phone received the files properly fine through doing but not installing after booting
Gets shut down at logo. This I tried it 2.
Sent from my GT-I9500 using xda app-developers app
Kindly elaborate... Did you factory reset prior to using Odin?
Ok.
I went into cwm.
1 I factory reset. Wiped the data
2 wiped catche
3 wiped dalvic catche
4 went into download mode
5 with Odin 1.85 recognised device installed official rom.
The progress was shown in both phone and Odin. Factoryfs, kernel, hidden and catche shown to be successfully copied.
Only the auto reboot was selected
After device restated it shouted the Samsung logo. Without triangle
I thought it was a success.
Then I saw green Android logo with install process which seemed to have successfully completed on the phone.
but then just as the Samsung and a ring revolving screen came up, insured of booting up the device got shut down.
I thought it will reboot ok but it didn't. I tried restating several times but it kept getting shutdown.
I then flashed the official firmware again but this time after Odin transferred all the files on the phone, the green android logo is not able to complete the installation in the middle of it the phone is restating showing the battery charging logo, then the green bot trying to install then again it restarts.
To sum up
I note
Sent from my GT-I9500 using xda app-developers app
Sorry I posted by mistake
To sum up I I now am stuck in a loop where connecting the cable starts showing the battery charge logo, starts the device shows android logo with progress in the belly and a progress bar at the bottom restarts again allowing the battery logo again the Android thing and so on in a loop.
Please advice
Sent from my GT-I9500 using xda app-developers app
killachandra said:
I rooted and installed CWM and Cyanogen 10.1.3 on by brothers Note, GT-N7000. He didnt enjoy it as some unexpected errors were coming up sometimes. Luckily i found the official Rom 4.1.2 N7000DDLSC_INU.zip through sammobile. Now My questions are:-
1. What must i do to completely remove cyanogenmod and clock work recovery.
2. Do i need some additional files like, kernel or bootloader or phone or csc (or will just all this zip to pda will install it)
3. What else should i take care of?
Please advice i want to completely return to official state
Click to expand...
Click to collapse
Not sure if you have any other strong reason to go back to pure stock. Otherwise the easiest way is to install a stock base custom rom using PhilZ kernel and rom.zip. Sweet rom 10.5 is very good. Fast and stable.
Install purestock rom via odin is a pain and can cause lots of problems due to poor cable connection.
Sent from my phone.
killachandra said:
Sorry I posted by mistake
To sum up I I now am stuck in a loop where connecting the cable starts showing the battery charge logo, starts the device shows android logo with progress in the belly and a progress bar at the bottom restarts again allowing the battery logo again the Android thing and so on in a loop.
Please advice
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Did you have enough battery before flashing? Power off the phone.. Then connect it to ac charger for couple of hours and then remove the charger and start the phone.
I do believe I had more than 80%on the 1st attempt but I can't say that about this morning.
Any ways I did put it on charge today. Nearly two hours. Since it was looping on the battery and installation thing I put it on download mode. But now after removing from download mode is not even starting on download mode. I feel is further damaged. Any other software to interact with the phone or any other options I might have left
Sent from my GT-I9500 using xda app-developers app
If it is not the batery then software does not help. There is a tool name usb jig which can help put phone to DL mode.
Sent from my phone.
Thanks people for all the support. I think I will take it to the Samsung people as it is getting a little scary for my brother to trust me with this
Sent from my GT-I9500 using xda app-developers app
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck
[UPDATE] .after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
jthornton71707 said:
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Click to expand...
Click to collapse
if you have a att note 3 you might be screwed both the firmwares you list are not for our phone your best bet would be to go to a best buy or att service center and seee if they can reflash your phone
Is there a tar for the AT&T firmware? I've searched but this was all I could find.
jthornton71707 said:
Is there a tar for the AT&T firmware? I've searched but this was all I could find.
Click to expand...
Click to collapse
Yeah, it seems that the N900XXUDNA6 is not for the US Variant
"N900XXUDNA6 Android 4.4.2 KitKat official firmware update for Galaxy Note 3 SM-N900 is now rolled out by Samsung. This is the first KitKat official firmware for Galaxy Note 3 SM-N900. The firmware update rolled out in various countries including Sri Lanka, Nepal, Indonesia, Singapore, Vietnam, Kazakhstan, Ukraine, Russia, Thailand and India"
The DNA6 would be for the SM-N900 Exynos CPU devices, not the SM-N900A Snapdragon. That is probably your problem (In addition to trying to roll back to JB from KK)
Unfortunately, I dont know of any stock KitKat firmware. There is MI9 on Samfirmware's site, but that is JB not KitKat
jthornton71707 said:
Is there a tar for the AT&T firmware? I've searched but this was all I could find.
Click to expand...
Click to collapse
sorry.
B_I_N_G_E said:
sorry.
Click to expand...
Click to collapse
So after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
jthornton71707 said:
So after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
Click to expand...
Click to collapse
You could try to stop the boot, go back into Recovery and wipe cache, and wipe all data. I had an experience with my last device (SGSIII) that would boot loop sometimes when flashing back to a stock ROM.
Other than that, I dont have any other ideas
Just Googled the "SW REV CHECK FAIL" FUSED 3 BINARY 2", from what I found the Fused 3 means you were on Kit Kat, and Binary 2 basically means you are trying to downgrade to JB
It wont let me even boot into recovery. I hold the buttons and it boots back up saying "booting into recovery" like it is, then it just boot loops again.
jthornton71707 said:
It wont let me even boot into recovery. I hold the buttons and it boots back up saying "booting into recovery" like it is, then it just boot loops again.
Click to expand...
Click to collapse
The only other things I saw on that, suggested to users(on a different Samsung device) to use a jig to get it back into recovery. I am not familiar enough with the N3 yet to know if a jig will work on our devices. My guess is you messed up the bootloaders
Edit** I think that since things are so locked down that your best bet might be to try what jerrycoffman45 suggested a few posts ago
jerrycoffman45 said:
if you have a att note 3 you might be screwed both the firmwares you list are not for our phone your best bet would be to go to a best buy or att service center and seee if they can reflash your phone
Click to expand...
Click to collapse
My local at&t and best buy aren't very helpful for anything at all. ill keep googling ive been at this for 2 days now
There is no firmware to download for 4.4.2 yet so you are stuck till there is or do what I suggested you could also do a warranty exchange by calling att and you can't just go to any att store it has to be a service center
Sent from my SAMSUNG-SM-N900A using Tapatalk
---------- Post added at 05:40 PM ---------- Previous post was at 05:25 PM ----------
This might get you running
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my SAMSUNG-SM-N900A using Tapatalk
jthornton71707 said:
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck
[UPDATE] .after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
Click to expand...
Click to collapse
Still need help?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
only fix I know
as far as I have searched, the only current fix to get to use your phone is
GUIDE/ROM[4/1][AT&T][NC2_Bootloader][ N900AUCECMGL KITKAT][Stuck Download-Mode FIX]
i tired rooting my t-mobile s6 [SM-G920T] running on 5.1.1 last night with the method outlined by the following thread:
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
it took me a few attempts, but i thought i finally got root... it turns out my digitizer's x-axis somehow got messed up during some process [when i touch the right side of the screen, it selects left, and vise-versa]
now i can't even turn on my phone... when i try, the splash screen simply tells me "kernel is not seandroid enforcing" and "custom binary blocked by FRP lock"
i tried taking it back to the t-mo store since i just got the phone yesterday, but "no exchanges on rooted devices...":crying:
is there any way for me to fix my problem? please advise, thank you.
Try Odin my friend or smart switch..
Sent from my SM-G920T using XDA Free mobile app
since i upgraded to 5.1.1 before i attempted all this, i need the G920TUVU2COF6 md5 file... i was using the 5.0.2 version: G920TUVU1AOCG
maybe that is why it kept failing... i am downloading the right version right now and will give it a try.
i really hope it works... if not, i don't know what else i can try
You flashed twrp recovery for the G925T edge.
Try this before doing anything else. If it works, thank edgarf28.
The next time you flash something, double check that it is correct for your phone before flashing :good:
sublimaze said:
You flashed twrp recovery for the G925T edge.
Try this before doing anything else. If it works, thank edgarf28.
The next time you flash something, double check that it is correct for your phone before flashing :good:
Click to expand...
Click to collapse
i tried that, but no success...
i was able to odin the 5.1.1 file, but the digitizer was still messed up.
but now with a bootable stock rom, i took the phone into the store and they exchanged it for me in 15 minutes.
Was it booting into odin? These situations are weird because if odin reads and the phone at least boots to Samsung screen I try and have succeeded on all occasions at un-soft-bricking.
i was able to put the phone into download mode... since i updated to 5.1.1 before i began the root process, i had to use the G920TUVU2COF6 md5 file instead of the G920TUVU1AOCG in odin to restore.
dnaL0R said:
i was able to put the phone into download mode... since i updated to 5.1.1 before i began the root process, i had to use the G920TUVU2COF6 md5 file instead of the G920TUVU1AOCG in odin to restore.
Click to expand...
Click to collapse
you can recover your phone using stock G920TUVU2COF6, i recovered my phone from same issue.
Hey guys hopefully someone can help me out. I have a friend that has a note 4 that seems to have a mind of its own. It gets to the note 4 screen hangs and then reboots. Ive tried the following:
Kies upgrade and initialization
Odin stock lollipop
odin twrp 2.6.1 recovery
The note takes all of those with no errors. When the note reboots it hangs and then reboots over and over. I tried to get to recovery but hangs just like it does when its booting and restarts. Also unable to get to safe mode. But does get to download mode no problem. Any Ideas?
If you have twrp, have you wiped
System
Data
Dalvik
Cache
Internal?
Sent from a dorito
re: factory reset
svtthis said:
Hey guys hopefully someone can help me out. I have a friend that has a note 4 that seems to have a mind of its own. It gets to the note 4 screen hangs and then reboots. Ive tried the following:
Kies upgrade and initialization
Odin stock lollipop
odin twrp 2.6.1 recovery
The note takes all of those with no errors. When the note reboots it hangs and then reboots over and over. I tried to get to recovery but hangs just like it does when its booting and restarts. Also unable to get to safe mode. But does get to download mode no problem. Any Ideas?
Click to expand...
Click to collapse
Go into twrp recovery and do a factory reset then reboot the phone..
Thanks guys for the replies I've tried both and the phone still reboots. Any other ideas?
Which model was it? The newer T3 or the original T? If the newer T3, make sure you are flashing dog1 firmware.
Sent from my SM-N910T3 using Xparent Skyblue Tapatalk 2
Its the N910t t mobile variant not sure if its the new one or not. How do I find out?
What stock firmware did you flash?
Sent from my SM-N910T3 using Xparent Skyblue Tapatalk 2
stock lollipop 5.01 cod6
Were you upgrading from kit Kat? Where did you get the firmware from? I'm not sure why you are rebooting...trying to figure it out.
Maybe try upgrading TWRP to a more recent version.
Sent from my SM-N910T3 using Xparent Skyblue Tapatalk 2
Same...
svtthis said:
Its the N910t t mobile variant not sure if its the new one or not. How do I find out?
Click to expand...
Click to collapse
WHAT
svtthis said:
Hey guys hopefully someone can help me out. I have a friend that has a note 4 that seems to have a mind of its own. It gets to the note 4 screen hangs and then reboots. Ive tried the following:
Kies upgrade and initialization
Odin stock lollipop
odin twrp 2.6.1 recovery
The note takes all of those with no errors. When the note reboots it hangs and then reboots over and over. I tried to get to recovery but hangs just like it does when its booting and restarts. Also unable to get to safe mode. But does get to download mode no problem. Any Ideas?
Click to expand...
Click to collapse
Try odin flashing twrp and then booting into recovery and flashing a ROM
Sent from my SM-N910T using XDA Free mobile app
Edit still not fixed. I took it to a repair shot and they changed out the power button and that still didn't fix the problem.
I use to think it was a hardware issue but now I think its a software issue. When I got the phone it had knox 0x1(3) so I think someone messed up the software on the phone and its restarting because its unstable.
Here is what I tried to do so far and nothing has changed still reboots either half way during boot or once booted all the way just restarts by itself.
Odin stock cod6 firmware (fails)
Kies firmware recovery
Odin twrp 2.8.7 with root and pop rocks rom.
twrp recovery wipe and factory reset
Nothing works
Are you sure it isn't the t3 variant? Normal note 4 n910t roms will not work on it.
Try a different battery i had the same problem with and s3 couple years ago phone will power on and die during boot i though it was because it was rood and had a custom recovery I had a back up from TWRP I did a restor and didn't fix any so i flash the latest official firmware from samsung and still had the problem then I decided to switch the battery from an other s3 and the then it got fix and the other s3 star doing the shot off act is worth trying
Also if the phone was running fine before what was is on so you can tell what model you have and how long you friend had it the SM-N910T came with 4.4.4 and so far can only be update to 5.0.1 officially and a SM-N910T3 is a much more recent variant and it came out the box with 5.1.1 and the box should show SM-N910T3 so if he had it with 4.4.4 or 5.0.1 before any root or custom rom is a SM-N910T and if you didnt flash the bootloader for lollipop and still on 4.4.4 you may get problem like those too
ensure you are on Either T3 or T there are two models of this phone now. ...
Some things I noticed wasn't asked.
Have you tried a new sim card?
Is there a MicroSD Card in it? Take it out and see what happens?
Those may seem unrelated but I have had those symptoms with other devices because each of those.
Also when using ODIN, try different usb ports if a flash fails the first time. I've been in your position before and such a seemingly simple thing made all the difference.