Alright so I recently got a unlocked note 4 (N910T) and after i upgraded to marshmallow the phone began to reboot at least three times a day. I had a micro sd card in there and took it out for several days. That didn't fix it. I flashed the original rom but that still didn't fix it. So downgraded to stock 5.1.1. Doesn't reboot as much but still freezes and gets really hot. I also got a new battery just in case that the battery was the problem. I've wiped the cache partition and did factory data reset. I've tried everything but it still keeps rebooting constantly even when I'm not using the phone. Any advice because to fix rebooting and freezing it is a real annoyance.
ctbrezenski said:
Alright so I recently got a unlocked note 4 (N910T) and after i upgraded to marshmallow the phone began to reboot at least three times a day. I had a micro sd card in there and took it out for several days. That didn't fix it. I flashed the original rom but that still didn't fix it. So downgraded to stock 5.1.1. Doesn't reboot as much but still freezes and gets really hot. I also got a new battery just in case that the battery was the problem. I've wiped the cache partition and did factory data reset. I've tried everything but it still keeps rebooting constantly even when I'm not using the phone. Any advice because it is a real annoyance. It also freezes a lot
Click to expand...
Click to collapse
Try to flash firmware with pit file it will reparation and fix your internal memory incase there are some errors. download pit file from link below and use with stock firmware in odin. Make sure do wipe cacha & data factory reset just after finish flash firmware from recovery
https://mega.nz/#!yE0QkRgR!8DvGvAauRkb-2xmtH_3ZluoYwCvqNaaSOnXMLYB_CAI
Dont get his hopes up though. High chance it will not work as there might be an internal issue with the note 4
monkeyass408 said:
Dont get his hopes up though. High chance it will not work as there might be an internal issue with the note 4
Click to expand...
Click to collapse
I am experiencing the same issues with my T-mobile Note 4. It started while running my stock 5.0.1 rooted with TWRP. i've had it for a year and half working GREAT, but last Thursday the whole slow, freezing and rebooting started all of a sudden.
Do you really think that it might be something physical with the phone?
Kr1sS129 said:
I am experiencing the same issues with my T-mobile Note 4. It started while running my stock 5.0.1 rooted with TWRP. i've had it for a year and half working GREAT, but last Thursday the whole slow, freezing and rebooting started all of a sudden.
Do you really think that it might be something physical with the phone?
Click to expand...
Click to collapse
My response to this problem http://forum.xda-developers.com/showpost.php?p=68559388&postcount=90
I tried what Trex888 recommended but it didn't resolve my issues http://forum.xda-developers.com/showpost.php?p=68500780&postcount=96
I wasted many hours trying to troubleshoot with no ultimate success (monkeyass408 went thru similar issues). I'd recommend looking for a replacement device.
The note 4 will start to fall apart. Mine has and I've had it since OCT of the year the phone came out (14,15?) Battery dies randomly. I connect to charger and all the sudden it has 25% have two batteries. My camera can no longer focus. I am using this device as a backup because my s7 edge has a busted screen.
Sent from my SM-N910T using Tapatalk
I too have had this problem of interface freezes, crashes, reboots. I'm using Nova on Tekhd rom 7.4. Clearing cache and dalvik/art helped A LOT for a few days and it doesn't happen as often now, but it is depressing to see it happen at all after months of rock solid stability. It often froze with the stock music player going with screen locked so that may be related to the problem.
The way the interface reboots appeared suddenly made me suspect an app update somewhere, not failing hardware. The fact that clearing the dalvik helped supports this notion. On my phone at least everything works well including batteries (I have 3) and charging. It could be different problems for people reporting these issues, some hardware related. I have considered reformatting my 200gb sdcard, but after clearing dalvik it happens so infrequently that I haven't bothered.
Sent from my SM-N910T3 using XDA-Developers mobile app
Trex888 said:
Try to flash firmware with pit file it will reparation and fix your internal memory incase there are some errors. download pit file from link below and use with stock firmware in odin. Make sure do wipe cacha & data factory reset just after finish flash firmware from recovery
https://mega.nz/#!yE0QkRgR!8DvGvAauRkb-2xmtH_3ZluoYwCvqNaaSOnXMLYB_CAI
Click to expand...
Click to collapse
sorry to highjack but where do i put the pit file in odin? i downloaded pe3 and odin it and the phone is reboot loop hoping this will help.
swordmastr54 said:
sorry to highjack but where do i put the pit file in odin? i downloaded pe3 and odin it and the phone is reboot loop hoping this will help.
Click to expand...
Click to collapse
After flash firmware do wipe data & data factory reset from recovery it will fix bootloop issue.and in the screenshot below you can see pit file selection tab in odin.
Trex888 said:
After flash firmware do wipe data & data factory reset from recovery it will fix bootloop issue.and in the screenshot below you can see pit file selection tab in odin.
Click to expand...
Click to collapse
didnt work for me...lovely.
Edit: as soon as a posted it...it came up, wtf.
Related
anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF
Wipe and reflash?
nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...
hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...
I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.
I have stock at&t S5 and it was working fine then just went it a bootloop. Tried going into recovery and doing a factory reset and even wiped cache and it still does it. Any ideas how i can get the thing to boot up? I have called for a warranty replacement but i's rather not wait for that if i do not have to.
thanks.
lfaulkner29 said:
I have stock at&t S5 and it was working fine then just went it a bootloop. Tried going into recovery and doing a factory reset and even wiped cache and it still does it. Any ideas how i can get the thing to boot up? I have called for a warranty replacement but i's rather not wait for that if i do not have to.
thanks.
Click to expand...
Click to collapse
you did absolutely nothing prior to the bootloop?
i would use odin on a pc and odin the full stock tar (for your att s5) in AP slot.. this will wipe everything on internal memory but should work if nothing else is wrong
Sent from my SM-G900V using XDA Free mobile app
i didn't do anything out of the ordinary no. just using some apps. i got it to actually boot if the usb cord was plugged into it when it rebooted which is kinda weird. anyways, it's working now so i'll mess with it and see if it does it again.
It appears to be a battery problem. Borrowed a friends battery and didn't have the problem, so I have ordered a new battery. Hopefully that will do the trick.
I sent my phone into Samsung for a repair and they replaced the motherboard, the screen almost a whole new phone. When it was returned they had already downloaded lollipop which towelroot would not work. Found a site that showed me how to downgrade back to kitkat root, install safestrap and I could return to lollipop. I never did the lollipop part as I did not like it much. It worked great at first I was able to return back all my data. After a week it begin to act funny, not wanting to wake up from sleep and then slowly apps begin crashing and not working. I would restart my phone and things were fine. Another week apps were crashing left and right and then my data begin disappearing like my messages and the levels of my saved games. Then it begin restarting on its own 3 times during the night. I tried to reinstall the rom and re-partitioned the phone and did factory reset but it continues to periodically restart even though I have given up on reinstalling my data since it factory resets on its own. I guess I am in a very slow bootloop. Can anyone suggest what I can do? Thanks in advance
meregirljj said:
I sent my phone into Samsung for a repair and they replaced the motherboard, the screen almost a whole new phone. When it was returned they had already downloaded lollipop which towelroot would not work. Found a site that showed me how to downgrade back to kitkat root, install safestrap and I could return to lollipop. I never did the lollipop part as I did not like it much. It worked great at first I was able to return back all my data. After a week it begin to act funny, not wanting to wake up from sleep and then slowly apps begin crashing and not working. I would restart my phone and things were fine. Another week apps were crashing left and right and then my data begin disappearing like my messages and the levels of my saved games. Then it begin restarting on its own 3 times during the night. I tried to reinstall the rom and re-partitioned the phone and did factory reset but it continues to periodically restart even though I have given up on reinstalling my data since it factory resets on its own. I guess I am in a very slow bootloop. Can anyone suggest what I can do? Thanks in advance
Click to expand...
Click to collapse
When you downgrade to KitKat did you use an All-In-One Odin file which went in the AP Slot? If you did, then Flash all four Odin files for NC2 (KitKat) BL https://www.androidfilehost.com/?fid=96042739161891602 AP https://www.androidfilehost.com/?fid=96042739161891890 CP https://www.androidfilehost.com/?fid=96042739161891603 CSC https://www.androidfilehost.com/?fid=96042739161891604 Odin http://forum.xda-developers.com/attachment.php?attachmentid=3109599&d=1420980613 That will put you back on stock Kitkat and just root with Towelroot.
Rooted i747 said:
When you downgrade to KitKat did you use an All-In-One Odin file which went in the AP Slot? If you did, then Flash all four Odin files for NC2 (KitKat) BL https://www.androidfilehost.com/?fid=96042739161891602 AP https://www.androidfilehost.com/?fid=96042739161891890 CP https://www.androidfilehost.com/?fid=96042739161891603 CSC https://www.androidfilehost.com/?fid=96042739161891604 Odin http://forum.xda-developers.com/attachment.php?attachmentid=3109599&d=1420980613 That will put you back on stock Kitkat and just root with Towelroot.
Click to expand...
Click to collapse
When I downgraded I did use an all in one but later when I realized it was all bad and reinstalled the rom I did it both ways. Used an all in one and then did it with the four individual files. It still has the problem, it will be working fine then suddenly freeze and the phone will auto reboot. Is there a way to clean it all out then try to stock rom. I am concerned that there is something lingering causing this problem. I did clear the cache several times but it does not help.
meregirljj said:
When I downgraded I did use an all in one but later when I realized it was all bad and reinstalled the rom I did it both ways. Used an all in one and then did it with the four individual files. It still has the problem, it will be working fine then suddenly freeze and the phone will auto reboot. Is there a way to clean it all out then try to stock rom. I am concerned that there is something lingering causing this problem. I did clear the cache several times but it does not help.
Click to expand...
Click to collapse
After you put all four files in Odin, go to Options and check Nand Erase All (picture 1). Then Once phone reboots, power off and go into stock recovery and wipe data/factory reset, then do wipe cache partition (picture 2).
Awesome Thanks!
Rooted i747 said:
After you put all four files in Odin, go to Options and check Nand Erase All (picture 1). Then Once phone reboots, power off and go into stock recovery and wipe data/factory reset, then do wipe cache partition (picture 2).
Click to expand...
Click to collapse
Appreciate the info I will give it a go!
Did not work
Rooted i747 said:
After you put all four files in Odin, go to Options and check Nand Erase All (picture 1). Then Once phone reboots, power off and go into stock recovery and wipe data/factory reset, then do wipe cache partition (picture 2).
Click to expand...
Click to collapse
I did exactly what you said, put the files in Odin and selected the Nand Erase. It loaded rebooted, then I powered off went into recovery mode did a wipe data and then wiped cache. Turned on well, looked good but in the middle of restoring my texts and contacts through Kies it shut down restarted and now getting the same kind of messages that various apps and processes have stopped. It literally is now popping up with so many messages that one thing or another has stopped that I can not even select to restart the phone. This is crazy. I don't know what else to fix. The phone got a new motherboard so what else could be causing this craziness Any help you can provide or light on the subject is very appreciated.
meregirljj said:
I did exactly what you said, put the files in Odin and selected the Nand Erase. It loaded rebooted, then I powered off went into recovery mode did a wipe data and then wiped cache. Turned on well, looked good but in the middle of restoring my texts and contacts through Kies it shut down restarted and now getting the same kind of messages that various apps and processes have stopped. It literally is now popping up with so many messages that one thing or another has stopped that I can not even select to restart the phone. This is crazy. I don't know what else to fix. The phone got a new motherboard so what else could be causing this craziness Any help you can provide or light on the subject is very appreciated.
Click to expand...
Click to collapse
If you didn't root it yet, then do a wipe data/factory reset, then do wipe cache partition in recovery and don't restore anything with Kies and see what happens. If everything works great then, then you know it's Kies messing up your phone.
Still happening
Rooted i747 said:
If you didn't root it yet, then do a wipe data/factory reset, then do wipe cache partition in recovery and don't restore anything with Kies and see what happens. If everything works great then, then you know it's Kies messing up your phone.
Click to expand...
Click to collapse
So it is taking longer and I don't get the message that apps have stopped because there are no updated apps since I did not connect to the play store but after a while like before it is freezing and restarting. So it is back to the original problem of being a slow bootloop. Sorry it is being a pain.
meregirljj said:
So it is taking longer and I don't get the message that apps have stopped because there are no updated apps since I did not connect to the play store but after a while like before it is freezing and restarting. So it is back to the original problem of being a slow bootloop. Sorry it is being a pain.
Click to expand...
Click to collapse
Did it have any problem when you first got it back, before you did anything to it?
Hard to really know.
Rooted i747 said:
Did it have any problem when you first got it back, before you did anything to it?
Click to expand...
Click to collapse
When I first got it back it started right up and it was on lollipop. I went to restore my stuff through titanium backup but realized that I could not root it with Towelroot. I kept the phone like it was for a two days and I don't believe I had any real problems. Nothing I noticed but I did not have all my data completely back. I read up on downgrading my phone back to kitkat in order to root and it also had the option to re upgrage to lollipop and keep the root but I did not like the look and feel of lollipop so I kept it at kitkat. Although I did install the safetstrap program like suggested but never used it, could that be causing the problem? I restored my data and things were just fine for about a week. Then it slowly started having problems being difficult to wake up, then apps crashing, to data disappearing then finally restarting on its own over and over. This process of breakdown took about three weeks. I was concerned that my data could have been the problem so when I restored the ROM the first time and wiped it clean I hope that would take care of the problem but like what happened today it still begin the out of the blue restart for no reason. I would not be using the phone or anything, it would just restart on its own.
meregirljj said:
When I first got it back it started right up and it was on lollipop. I went to restore my stuff through titanium backup but realized that I could not root it with Towelroot. I kept the phone like it was for a two days and I don't believe I had any real problems. Nothing I noticed but I did not have all my data completely back. I read up on downgrading my phone back to kitkat in order to root and it also had the option to re upgrage to lollipop and keep the root but I did not like the look and feel of lollipop so I kept it at kitkat. Although I did install the safetstrap program like suggested but never used it, could that be causing the problem? I restored my data and things were just fine for about a week. Then it slowly started having problems being difficult to wake up, then apps crashing, to data disappearing then finally restarting on its own over and over. This process of breakdown took about three weeks. I was concerned that my data could have been the problem so when I restored the ROM the first time and wiped it clean I hope that would take care of the problem but like what happened today it still begin the out of the blue restart for no reason. I would not be using the phone or anything, it would just restart on its own.
Click to expand...
Click to collapse
Safestrap will keep your stock recovery from booting up if Kies needs it to. After you had Safestrap on it did you use any Odin files (not the "all-in-one" as it will not wipe your phone)?
Rooted i747 said:
Safestrap will keep your stock recovery from booting up if Kies needs it to. After you had Safestrap on it did you use any Odin files (not the "all-in-one" as it will not wipe your phone)?
Click to expand...
Click to collapse
Sorry it took me so long to respond to your question. No I followed the process from the below website. After I installed safestrap, SuperSU , Busybox and towel root, I just connected to Kies reinstalled most of my data then used Titanium backup to install my games levels. I did not follow the process to bring it back to lollipop.
http://zidroid.com/how-to-keep-root-att-galaxy-note-3-on-lollipop-oc1/
meregirljj said:
Sorry it took me so long to respond to your question. No I followed the process from the below website. After I installed safestrap, SuperSU , Busybox and towel root, I just connected to Kies reinstalled most of my data then used Titanium backup to install my games levels. I did not follow the process to bring it back to lollipop.
http://zidroid.com/how-to-keep-root-att-galaxy-note-3-on-lollipop-oc1/
Click to expand...
Click to collapse
If you wouldn't mind download Phone INFO ★Samsung★ from play store https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and take a screen shot of the Firmware and Android. Your's will be different than mine.
Here are mine
Rooted i747 said:
If you wouldn't mind download Phone INFO ★Samsung★ from play store https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and take a screen shot of the Firmware and Android. Your's will be different than mine.
Click to expand...
Click to collapse
Ok see below. I can't tell you how much I appreciate your helping me!
meregirljj said:
Ok see below. I can't tell you how much I appreciate your helping me!
Click to expand...
Click to collapse
Everything looks good. Where you on NC2 when you did your backup with Kies (with the old motherboard)? Because there is NJ 5 and NL1 which are Kitkat too.
I realized I have no idea
Rooted i747 said:
Everything looks good. Where you on NC2 when you did your backup with Kies (with the old motherboard)? Because there is NJ 5 and NL1 which are Kitkat too.
Click to expand...
Click to collapse
I don't remember what it was before. When I got my phone before I only needed to install towelroot and moved everything over. I never paid attention to which version of kitkat I was on. Hindsight I probably should have but I only remember being on Kitkat and not the specifics.
meregirljj said:
I don't remember what it was before. When I got my phone before I only needed to install towelroot and moved everything over. I never paid attention to which version of kitkat I was on. Hindsight I probably should have but I only remember being on Kitkat and not the specifics.
Click to expand...
Click to collapse
If you only installed Towelroot, then you was on NC2. This is up to you, if you want to. But I would Odin the [100% Stock] Lollipop 5.0 (N900AUCUEOC1) Odin Tars http://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 (the Individual/Wipe Tars ones) and then upgrade it to OC2 (though phone) and see if it gives you any problems. If it does, I would say that motherboard is the problem then. If there is no problems, you can always Odin back to NC2. Or if you want, install Busybox, supersu and Safestrap on what you have now and put your backup from Titanium and Kies on your phone and then boot into Safestrap and tap WIPE > ADVANCE WIPE > DALVIK CACHE and swipe to wipe. Then ADVANCE > FIX PERMISSIONS > swipe to confirm.
Adaway
Just thought you might not know of this Adaway https://f-droid.org/repository/browse/?fdid=org.adaway
I will try the lollipop way.
Rooted i747 said:
If you only installed Towelroot, then you was on NC2. This is up to you, if you want to. But I would Odin the [100% Stock] Lollipop 5.0 (N900AUCUEOC1) Odin Tars http://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 (the Individual/Wipe Tars ones) and then upgrade it to OC2 (though phone) and see if it gives you any problems. If it does, I would say that motherboard is the problem then. If there is no problems, you can always Odin back to NC2. Or if you want, install Busybox, supersu and Safestrap on what you have now and put your backup from Titanium and Kies on your phone and then boot into Safestrap and tap WIPE > ADVANCE WIPE > DALVIK CACHE and swipe to wipe. Then ADVANCE > FIX PERMISSIONS > swipe to confirm.
Click to expand...
Click to collapse
I will try this when I get back home. I am traveling back from vacation and will try it Monday night after I get off work. I will let you know how it goes. Thanks!!!
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
AntonJart said:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
Click to expand...
Click to collapse
I saw that thread, but most of those people started having the issue after the update. If the kit kat update fixes it then i'm at a loss. And since a new board fixed the issue for you that means most likely the the memory is beginning to fail. That's how SSDs die anyway.
tempy1 said:
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
Click to expand...
Click to collapse
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
tempy1 said:
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
Click to expand...
Click to collapse
Without battery in freezer.
No idea how it works but good thing is hopefully it will work cuz lot of users even recover their hard bricked devices by this.
As you said you have nothing to lose so give it a try and make sure be patient dont give up and do this when you have enough time to do at least couple of hours.
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
keithwwalker said:
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
Click to expand...
Click to collapse
so wait the freezer thing was not even a permanent fix?
No, the freezer sometimes helps you get a bricked device so that it turns on. It doesn't fix thermal issues. I believe it helps some electrical connection that has broken come into contact again.
I can't go to download mode or recovery. I tried both ways But there is no way to use my device.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
So i recently had a baby, thus i had no time at all to get my phone to work. WakeLock app was working alright.
But last night the phone just died. all attempts to revive failed. I left it in the freezer until the morning and it booted up but quickly locked up after about 5 minutes of use and became unresponsive.
I tried your method.
I failed right away. Modem could not be written..
I tried flashing the pit files like i did previously and that failed as well.
Any suggestions are appreciated. I am phoneless
EDIT#2: After I left the phone in the freezer for longer (3 hours). The odin firmware update went through !!!! This furtherst i've gone so far.
I went into recovery and did everything you said.
BUT now i have Kernel Panic Upload Mode on my screen with a little green android
EDit#3 few battery pulls later. And an over 15 minute wait time on the android logo and then about the same on the t-mobile logo i got into the OS. I did the OTA update, the phone heated up and a few restarts later it froze up like it did previously
Back to square 1
EDIT: THIS helped for a few days
https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335
Day 2: and all went back to the phone not waking up and after screen is turned off
So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
I ran into this exact same problem weeks ago on my S7. I tried flashing 7.0 on my 930V and for whatever reason the phone went into the exact same bootloop showing the Samsung logo every few seconds, vibrating, etc. I got back into download mode but wasn't able to fix it. Then went into Recovery and it only said in blue letters in the top left "Recovery rebooting" and kept flashing that message. Lucky for me I was under warranty and sent it to Samsung. They replaced it free of charge. I ended up trading for a Note 5. I kept running into issues with my S7 and network issues so I traded it.
Anyway, I'm like you in the fact I'm pretty comfortable rooting, repairing devices etc. But I still don't know what I did to mess up that S7 in Odin. Just wanted to share that I had a similar situation. Hope you were able to get a new phone or fix your issue.
sinkableelk said:
So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
Click to expand...
Click to collapse
My suggestion is this..
Download the latest version of TWRP
Boot to Download Mode
Odin flash TWRP
Boot to TWRP Recovery
Full wipe including internal storage x 2
Format DATA x 2
Odin flash the latest firmware for your device
(All 4 - BLUE, AP, CP, CSC)
OR
Use Smart Switch Emergency Recovery to restore the firmware.
Hope this helps. Good luck and happy flashing! Let's us know what happens.
Sent from my Samsung SM-G955U using XDA Labs