Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Bro something similar happened to me as well .. even I did purchase new battery as everyone and also repair service guy said it's due to battery but that didn't solved the issue ..
Kindly check this xda post by me , it may help you.
https://forum.xda-developers.com/note-4/help/weird-white-bar-booting-sm-n910g-t3529413
adrscu said:
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Click to expand...
Click to collapse
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Hey guys and thanks for the replies.
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
adrscu said:
Hey guys and thanks for the replies.
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
Click to expand...
Click to collapse
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Amar.B said:
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
adrscu said:
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
Click to expand...
Click to collapse
All the best mate and it's my pleasure.. cheers
Sent from my SM-N910G using Tapatalk
Related
I am a newbie in android and rooting. i previously had sony xperia x8 which i had rooted and installed custom roms. i shifted to galaxy tab 2 months ago. i had a harrowing experience with rooting since last two days. let me tell you how it all started. i rooted my device to install titanium backup. it worked fine for few days . then i installed cmw recovery and it worked fine too. no issues what so ever. there were random FC's and hanging about once or twice a day.
Then all of sudden while browsing tablet hanged and it went into bootloop. i tried everything .. from factory reset to flashing firmware. it did not work. it was stuck on samsung logo. when i had lost all hope after about 2 hours or so it started working again. i got scared and unrooted the device and removed cmw.
for two days it was working fine. Then again i had this urge to root it . i rooted it . it worked fine for a week or so .. And then all of sudden it started having force closes . TW and google play and all other apps. i got scared and removed root and cmw again. this time however i decide to take it to service center. i did not tell them i had rooted and all . just told them i was having problem with reboots and all . they gave me full warranty. After two days i got a call from them that it was not booting and they have to replace motherboard
i asked them to return the tab to me for a night and i will give it back to them in morning since it was going to take two days for board to arrive. when i checked i found it was possible to go into download mode and not recovery mode. i tried flashing firmware via odin but it was stuck at factory.img.
i read somewhere in Galaxy note forum that it was superbrick bug and i had to use .pit file to repartition. i downloaded the file from google and repartioned it and installed firmware for my country via odin.
and it worked
Now my question is ....
Should i get a motherboard replacement or demand a new tab ? or is this tab ok now ? will i get such problems in future .
om0 said:
I am a newbie in android and rooting. i previously had sony xperia x8 which i had rooted and installed custom roms. i shifted to galaxy tab 2 months ago. i had a harrowing experience with rooting since last two days. let me tell you how it all started. i rooted my device to install titanium backup. it worked fine for few days . then i installed cmw recovery and it worked fine too. no issues what so ever. there were random FC's and hanging about once or twice a day.
Then all of sudden while browsing tablet hanged and it went into bootloop. i tried everything .. from factory reset to flashing firmware. it did not work. it was stuck on samsung logo. when i had lost all hope after about 2 hours or so it started working again. i got scared and unrooted the device and removed cmw.
for two days it was working fine. Then again i had this urge to root it . i rooted it . it worked fine for a week or so .. And then all of sudden it started having force closes . TW and google play and all other apps. i got scared and removed root and cmw again. this time however i decide to take it to service center. i did not tell them i had rooted and all . just told them i was having problem with reboots and all . they gave me full warranty. After two days i got a call from them that it was not booting and they have to replace motherboard
i asked them to return the tab to me for a night and i will give it back to them in morning since it was going to take two days for board to arrive. when i checked i found it was possible to go into download mode and not recovery mode. i tried flashing firmware via odin but it was stuck at factory.img.
i read somewhere in Galaxy note forum that it was superbrick bug and i had to use .pit file to repartition. i downloaded the file from google and repartioned it and installed firmware for my country via odin.
and it worked
Now my question is ....
Should i get a motherboard replacement or demand a new tab ? or is this tab ok now ? will i get such problems in future .
Click to expand...
Click to collapse
Superbick bug? Isnt that on leaked ICS kernels??
I had an issue like this a while ago it looked like my data partitions got corrupted. Just had to e2fs em
Well if they want to replace it, I'd let them. I personally don't think it was root and cwm causing your issues but that's just opinion
Sent from my DROID BIONIC using Tapatalk 2
nicduim said:
I had an issue like this a while ago it looked like my data partitions got corrupted. Just had to e2fs em
Well if they want to replace it, I'd let them. I personally don't think it was root and cwm causing your issues but that's just opinion
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
What is e2fs? And is the OP saying there's a solution to superbrick bug?
--thanks for tolerating my lack of familiarity with repartitioning mobile devices (i still get nervous repartitioning regular HD's)
The indefinite microcosm becomes the indefinite macrocosm in a definite manner and by definite means...and vice versa.
aletheus said:
What is e2fs? And is the OP saying there's a solution to superbrick bug?
--thanks for tolerating my lack of familiarity with repartitioning mobile devices (i still get nervous repartitioning regular HD's)
The indefinite microcosm becomes the indefinite macrocosm in a definite manner and by definite means...and vice versa.
Click to expand...
Click to collapse
Sorry tired but here is a link where to the thread I came across in the past
http://forum.xda-developers.com/showthread.php?p=25848578
I did something similar to what was posted in here after checking the partition thread. Looks like it's mentioned in the link. Hope it helps. Will look it over later and try to find the exact steps I had done and looked up but it did help fix my loops and they're been gone for like 2 months.
Sent from my GT-P6800 using Tapatalk 2
Superbrick ?
i dont know if my tab was stuck on superbrick or not
it was stuck on factoryfs.img while odin flash. i read this thread where it mentions that if a phone is stuck on factoryfs.img then its super brick. i followed the method mentioned in this thread to get it unblocked and it worked .
http://forum.xda-developers.com/showthread.php?t=1656635
Nobody wants to ruin a $28 per square inch tablet, but I REALLY don't want to. So I'm just doing what research I can before the official ics update rolls out. It's looking alot sunnier knowing that the thing isn't DOOMED, even if samsung doesn't compensate for the superbrick bug...
i'd say they'd be fools not to, but we've all gotten real up close and personal with samsung and how they treat their customers with the release of the p6800, so....
Thanks ALOT guys for getting down into the trenches and figuring all this out.
-----------
The indefinite microcosm becomes the indefinite macrocosm in a definite manner and by definite means...and vice versa.
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
KalarAzar said:
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Repulsa said:
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Click to expand...
Click to collapse
Hi and thanks for your reply,
I can boot into download mode - one of the only things I can do! - and it says 0x1 under KNOX WARRANTY VOID, so yes it is showing Knox void.
Just in case you need it, the full information shown on the screen in download mode is as follows:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thanks again..
KalarAzar said:
Thanks again..
Click to expand...
Click to collapse
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Repulsa said:
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Click to expand...
Click to collapse
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
KalarAzar said:
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
Click to expand...
Click to collapse
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Repulsa said:
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Click to expand...
Click to collapse
Yes, I'm afraid it does, and I have already done the wipe cache and factory reset, but no joy. I did it again anyway and on reboot it went back into the bootloop again, I'm afraid..
KalarAzar said:
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Acer4605 said:
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Click to expand...
Click to collapse
Ah FFS. My battery serial does start with BD and I was wondering if it was a battery issue, but didn't want to replace it if the fault was wider spread. I guess I may have to try this then..
I'm just flashing to MJ7 right now, but if it reboots again I will see about a new battery from where I bought it on Monday
And, as I forgot to say in the last post: thanks for your reply. If this fixes it, much kudos, my friend..
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
KalarAzar said:
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
Click to expand...
Click to collapse
you can get passed the samsung logo if you boot while your charger is connected to the phone, the battery might swell as well or is already bigger then it originally was
My phone has been randomly shutting down over the past couple of days and the only way I can get it to boot is to connect a charger/cable to pc. I've tried different ROMs and returning to stock. No joy.
I guess my battery could well be the problem
---------- Post added at 11:33 AM ---------- Previous post was at 11:28 AM ----------
My phone has randomly started shutting down over the past couple of days and the only way I can get it to boot is to connect charger/cable to pc. When it dies, it also loses all of my wifi passwords. It's a bit of a head scratcher. Any help appreciated
Definately the battery, dude
I was experiencing the same problems, and I observed that the battery swollen. So I replaced it and now the phone is functioning properly. Do not wait for the battery to modify its volume because you are risking to put pressure on the display and crack it. Beware.
Was, indeed, the battery
Hey everyone,
Just to let you know that I went back to Phones4u with the receipt from September (when I bought the new phone) and they filled out a form to request a new battery from Samsung and replaced mine their and then in the shop with a new battery from another Samsung Galaxy S4.
My old battery did, indeed, have a serial number that started with BD and the new one starts with AA so hopefully I am now sorted.
Massive thanks to everyone who replied and hopefully this thread will save someone else the time and lost data that flashing ROMs can incur.
Cheers,
A very happy Steve :laugh:
Note 4 Stuck in Boot Loop - Help
I have a Note 4 SM-N910F, never been rooted, stock rom upgraded to 5.1.1 back in October, working fine until yesterday when it got stuck in a Boot loop.
Not sure what caused it but before it got stuck I was messing around with Google Photos which was running a bit slow.
Also I put it on the Qi Charger just before the loop started. It has an aftermarket Fone charger stuck to the battery. I’ve had this and the Qi Charger for 6mths with no problems before now.
It gets to the Samsung page waits a couple of seconds then boots again.
Here’s what I’ve tried - unsuccessfully - to fix the boot loop:
1: recovery mode.
I can get the little recovery text to appear in the top left but after a few seconds it boots again.
2: volume down, home
This gets me to the screen with up/down for continue/cancel.
This is the _only_ screen I can get to stay up without rebooting. It sits there waiting for input.
- Cancel, causes restart, of course, but back into the bootloop
3: Mashing on power button. Banging it, wiggling it, blowing on it.
I read somewhere this could cause a boot loop, but I doubt it is my case because
a. I’ve never had problems with the power button before
b: When I take out the battery and put it back in, it does NOT turn on. If I do the same holding the power button, it powers into the boot loop. So if the button were jammed on I would expect it to never remain off with the battery in.
3: flashing stock rom
I’m not 100% sure what build I had before. I know it was stock 5.1.1 OTA, and I’m pretty sure it was unlocked (my wife bought the phone and i inserted my old sim, but she may have bought it from my carrier and can’t remember)
So anyway I tried all three versions of TPH (unlocked) 5.1.1 from Sammobile.
Installed Odin 3.10.7 and flashed them.
It reboots to recovery but immediately boot loops again.
I doubt its to do with the version of the rom anyway since the symptoms are identical after flashing. Only now the boot loop always shows the little ‘recovery booting...’ text in the top left.
Here’s what I have NOT tried but am thinking about:
A: Re-partition option in Odin
B: Nand Erase All option in Odin
C: Buying a new battery.
On A/B: as far as I can tell what I have done so far should have left the data intact. I’m prepared to wipe all my data if it fixes my phone (no lectures about backups please!) and I’m tempted to do one of these on the off chance that the problem is caused by data or the “disk" problems.
But I don’t want to brick it. Can someone recommend how likely these are to help
And what they actually do?
(Please refrain from responses I see elsewhere like “this will brick your phone if you don’t know what you’re doing”. I don’t know what I’m doing, thats why I’m asking - just the facts please)
On C: the battery seems ok in that the power is solid even after not being plugged in for a long time, but since it was on the Qi Charger with that aftermarket thing stuck to it when it happened, I’m suspicious. Can any one say if this is a likely cause?
If so, it might be worth waiting till I get a new batter before doing A or B (can I wait days for Amazon!?)
[UPDATE] Got a new (genuine) battery at a local electronics store. No dice. Same problem, so it's not the battery. Shall I go ahead and re-partition.
[UPDATE] Got a PIT file from another forum, and flashed again with re-partition checked and PIT loaded. same results.
Is Nand-rease worth trying?
The phone is still under warranty so maybe I can return it.
But in that case I want to erase what's on it first.
thanks for any help
rhubarb
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
You can flash TWRP through ODIN while on COJ5 bootloader. It's locked but you still can flash recoveries and kernel and 5.1.1 ROMS
I am very interested in this thread. I have the EXACT same problem as you have after installing SimplRom, which was a ROM prior to COJ5. It could indeed be that our bootloaders are locked now?
I am using the N910F and just like you, installing any ROM/Custom Recovery/Bootloader/Kernel doesn't help. Perhaps installing a COJ5 ROM might help. I will give that a try, but I've recently used Kies to install the latest official firmware, but it didn't fix the issue.
I will report back here and we'll work on this together to make our phones work again!
Osama lakdawala said:
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Click to expand...
Click to collapse
Thanks but:
1: I have no custom rom. I have never had a custom rom on this device. I want to take it to Samsung, but want to clear the memory first. How can I do that?
2: I _am_ a software engineer_
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
roverrhubarb said:
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Click to expand...
Click to collapse
I have the exact same as you. I did install a custom recovery (multiple) and still get the bootloop. From my tries yesterday, I indeed also suspect it may be a hardware issue. Perhaps to do with the battery/charging port. When I have my device unplugged and try to start in recovery/normalboot, it does not have a bootloop but simply turns off (and then doesn't respond until I pull the battery out). I think a NAND erase wouldn't do anything as I've personally tried that already.
Have you prior (upto a week) before you got the issues had your phone in a moist environment (bathroom while showering for example). I got my problems a week after I accidentally left my phone in the bathroom and installed custom ROM (which was done earlier and had no issues).
I've read online that it may have caused oxidation on the inside and may need some cleaning/drying with alcohol.
I still hold hope that we just have a software issue as download mode is working fine (apart from the Power off not working unless we pull out the battery).
Anybody have any experience with oxidation on their phone? Perhaps have had a similar bootloop due to hardware failure?
roverrhubarb said:
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
Click to expand...
Click to collapse
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
dork997 said:
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
Click to expand...
Click to collapse
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
Since you can get into download mode I'd flash firmware through ODIN again after verifying it's correct.
I'm seeing off the sammobile site for the 910F not all are the COJ5 locked bootloader.
Since you did update in Oct you may be on the COJ3. I'd try one of those and see if it works.
If it doesn't work and stops on the sboot.bin file then you have the COJ5
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
i am sorry i don't know any way to remove personal data other than doing it via recovery. There is an option of "nand erase" in odin it is used while flashing firmware and it wipes everything on the phone but i have never used it (and also don't know whether it can help you or not) ... Senior members kindly help us with this.
Any update to your situation?
very interested as I am in the same situation as you are. Download mode works, recovery+normal boot not. No matter what ROMs/recoveries I install
Same issue I think
I am also in the same situation, although I can enter the recovery mode - home power and volume up - I have tried the wipe cache and then factory wipe to no avail - I have also entered download mode and flashed the stock recovery and even though Odin says pass, it is still in a boot loop. Also when I go to the download screen it has a line saying knox warranty void 0x1(4) does this mean I have voided the warranty even though I only used Odin to flash stock recovery?
Did anyone found a solution
Did anyone ever found a solution to this problem I'm having the exact same issue on a note 4 smn910a
I have a slightly different issue with my Note 4 SM-N910G, wherein am not able to start the phone at all, it is completely dead, if i put the cell phone on charge then also there is no LED on the top but if i connect the device to the PC it does make the connected sound on the PC but Odin is still not able to recognize the device neither kies. I tried draining the power by removing the battery, connected the device to PC without battery and then inserting it but the same problem. Please suggest me any resolution for this dead body am carrying from past few weeks.
hi Op,
did you find any solution for this issue?
Hello all. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Do you have memory card installed? if so then scan you memory card for possible viruses.
Actually I have this issue too before.
Even if I left it lying on the table, it can restart by itself.
I tried to update to latest PB1 rom, the update failed, the phone restart while ODIN updating.
So I use Kies recovery and got it working again.
After that, i tried again update to PB1 rom using ODIN. and now no issues at all.
I dont know which one did the trick whether update to PB1 or KIES recovery.
Goldendawn said:
Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Click to expand...
Click to collapse
Munawar Mehmood said:
Do you have memory card installed? if so then scan you memory card for possible viruses.
Click to expand...
Click to collapse
Thanks - but no I don't - these are the first things I did when it started happening.
When it started happening I did factory reset, removing memory card, factory reset again, didn't restore backup from google... etc etc - so the general admin tech stuff.
Because under warranty (2 year contract) I didn't want to do anything more so sent to provider to get dealt with (into my 22 months of 24 months). For the last 4 months it has been to them a number of times for the same thing.
Now each time they send it back they claim "software corrupt" and that there is no hardware issue. So doing a software root and mod change for me is a hope - and probably not a good one - that the Stock 5.0 is the problem on this phone. And only going down this road because I am coming out of the warranty and right now I have a phone I can't really use, and damn Samsung won't support it or fix it (which is really all I want them to do!!) sigh
syamsoul said:
Actually I have this issue too before.
So I use Kies recovery and got it working again.
Click to expand...
Click to collapse
Thanks for this information, because in fact you are not the first time I have read this but I am not sure what the Kies recovery is - is there some instructions you have because maybe that is what should try, because I have seen other people on Google state this has helped them with restarting, but that was usually after Mod fix. Maybe there is something in the 5.0 update on GN3 that might cause this?
Rosli59564 said:
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Click to expand...
Click to collapse
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Goldendawn said:
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Click to expand...
Click to collapse
Just flash the firmware with odin. Factory reset in recovery after it's done. That's it. There are a lots of threads about going down such this:
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
I suggest you read through before you go further. They are mixed results. Some successful. Some did not. That is why it is better to flash the same csc firmware.
I even able to downgrade my S6 from 6.01 to 5.1.1 without issue but of course it's different phone.
Sent from my SM-N920C
---------- Post added at 08:38 PM ---------- Previous post was at 08:15 PM ----------
I sent you a PM.
Sent from my SM-N920C
Hello everyone,
I have a friend who uses a S4. He was on marshmallow 6.0.1 twrp3.0.2.0. Suddenly the phone turns off, and wont boot anymore to android.
We tried to wipe data+cache+system+dalvik, and install MM 6.0.1 again and install stock 4.4.4 and 5.0.1. All led to fail.
Is it a pit file case or a broken bootloader ? Or it might be some sort of hardware issue ? Thank you.
Could be hardware.
What is the Odin error message when trying to flash stock roms?
It might be a hardware.
No error occurs in odin. It flashes and passes !!
But when i try to boot, the phone always gets stuck on SAMSUNG.
Yeah, you're not doing anything wrong, probably a hardware issue
Samofr said:
But when i try to boot, the phone always gets stuck on SAMSUNG.
Click to expand...
Click to collapse
It's probably the GPU.
Recovery and download mode don't need the GPU to function, so that's why they work.
But android does need it, so that why it doesn't work.
I took the phone to a mobile shop today.. The guy told me that overheating caused this.
Very bad news
But this is so weird.. We all know that the s3 at previous versions of android OS used to boil on moderate~heavy usage and i'm still on my s3 since 2012, and it still didnt show any kind of hardware-related problems... But anw i think i should stick to a safe side and start backing up my important stuff online
Samofr said:
I took the phone to a mobile shop today.. The guy told me that overheating caused this.
Very bad news
Click to expand...
Click to collapse
Sorry about your phone mate..