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.
Related
There are many threads that focus on this same issue I have run into. I am posting this now because there isn't anything that has been posted this recent. I literally spent three days trying to find a solution.
What I did to mess this up with my S4 I337m Fido phone.
1. Odin install TWRP recovery. This seemed to work fine. I think I had to flash it twice to get it to work but I could boot to recover no problem.
2. CF-Auto Root
This process worked up to the point where you are suppose to reboot the phone and open the Su App and allow it to write permissions. This failed to work. Every time I booted my phone it would lag out and tell me SU app failed to open.
3. Flashed Slim KAT anyway...bad idea but I figured I would follow proper steps and flash. Everything was fine except for WIFI...yes everything seemed to be running smooth except for WIFI. This was obviously unacceptable.
4. Flashed stock ROM for my S4 which I received from a thread and then updated with Kies to obtain fully stock. This by the way is a suggested fix from many threads but this is where the sounds stopped working!!! Yes WIFI was good but SOUND was gone!!! WTF!
5. Flashed like 4 different froms ranging from CM11 to Mokee ROM....Nothing worked.
FIX! So I downloaded my stock rom from Sammobile.
No I flashed this via ODIN and rebooted and then did an update from Kies...This did not work to resolve the ISSUE of No Sound for me! What I had to do to fix this was to do a "Firmware Upgrade and Initialization" in Kies! What this does is ask you for your MODEL# and SERIAL# under your BATTERY. This then gets the firmware specifically for your device from Samsung. This updated my phone to 4.4.2 and everything works better then when I originally got my phone.
Again their are other threads that lay most of this stuff out but the last tweak I did not read and tried out of desperation. I hope this helps at least one person. I will continue to try and root my device because I am crazy like that. I have been an XDA user for 8 years now and enjoy custom ROMS on every android device I have come across. I cracked this S4's screen a month ago and they said warranty was void so to hell with Stock **** lol
I thank the XDA community with all my heart for giving me restless nights of modding fun. I have learned a lot from all of you and appreciate your time.
Hello,
My story is pretty much the same as other people here. 2 weeks ago I rooted my S6 edge + and everything was fine, the device was working I downloaded lots of apps that needed special root permission done a lot of ad blocking---- Long story short the root was successful with ODIN and everything was working fine, I didn't mess around with other parts of the OS tho. So today I was checking my snap chat when all the sudden my phone started lagging, it does that every once a while, it used to happen on my note 3 too its just Samsung bug. Anyways it was lagging so I decided to press the restart button, I put the phone on my desk and continued to finish my work on my laptop about half an hour later I checked my phone for snap chats, but i realised that it didn't turn back on. I held the power button and this came up on top left corner.
KERNEL IS NOT SEANDROID ENFORCING (this one showed up before every time I booted after my root)
CUSTOM BINARY BLOCKED BY FRP LOCK (this one was new tho, I never seen it before)
Which means Im F***** because Im on a bootloop, and my battery could die anytime...
So I've done a little researching and I came up with the conclusion that I can use ODIN to put Official stock firmware back on my phone, but as I think everyone knows. I don't think there is Official stock firmware for G928W8. Which is weird, its the only firmware left out by who ever creates or extracts official firmware off Samsung phones. I also tried using smart switch but the device is apparently is not supported, although ODIN recognises it. I tried re rooting, on my phone it said Custom Binary(BOOT) blocked y FRP Lock. So basically I paid $1,150.00 and my phone bricked itself after 2 weeks. No stock firmware for G928W8, and no luck with Smart Switch. I don't have any other phone to use while an original stock firmware gets released by XDA. I looked pretty much everywhere there is no G928W8 Stock Firmware. So any ideas I really need to make some calls?
Thanks,
Artin P
Bro. I had the same problem couple of days ago but I managed to restore my phone like you mentioned by flashing the Original firmware via Odin and I remember seeing your version as well at Sammobile.com check it out you might want to subscribe to their cheapest subscription which is about $8 for a 14day subscription but the download time will be worth it trust me.
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
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Same deal here but i bought my 6p from best buy along with geek squad protection plan. Rather than send me another 64gb 6p, they've given me a gift card for the price at the time of purchase. At the moment only 32gb versions are available on best buy dot com. I'm not totally opposed to the 32gb version but I'm not excited about it. It took 3 days from the time I submitted my RMA request to get an email telling me this gift card b.s.
I haven't returned anything yet. Not sure what to do. I really liked that phone.
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps. phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
I wouldn't be. Sounds like you are unlocked and rooted. Just keep a good backup on your PC (including EFS) and enjoy your phone.
puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
Rooted or not and having a backup or not won't fix this unfixable bootloop. I have one in my possession I'm trying to restore and nothings working. Random reboots a week prior to it going into this bootloop. I've done a bunch of research and it's not good.
thesparky007 said:
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Click to expand...
Click to collapse
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
galakanokis said:
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
Click to expand...
Click to collapse
Call them here 1-888-5HUAWEI
thesparky007 said:
Call them here 1-888-5HUAWEI
Click to expand...
Click to collapse
Thanks, much appreciated.
I just went through the same thing. Waiting on the RMA box to arrive so it can be sent back.
Sent from my Nexus 6 using XDA-Developers Legacy app
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Going through the RMA process now, thanks again for the number.
I have heard it mentioned that flashing back to 6.0.1 might work, has anyone tried? I did flash all the way back to 7.0 with no luck.
tried flashing back to 6, 6.01 and 7.0 but it still persists. get it exchanged or repaired
It's now several phones a day... At what point does either Huawei or Google fess up to root cause? The one question I have is are all of these hard bricks on phones running nougat??
Sent from my Nexus 6 using XDA-Developers Legacy app
uzi132 said:
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Click to expand...
Click to collapse
You aren't alone obviously. These phones seem to be little time bombs where the boot loop issue is concerned. Mine goes into bootloops every time I flash an update or new ROM or attempt to restore a backup. I expect to hardbrick this phone at some point. It just hasn't happened yet.
Completely forgot about this thread. Huawei swapped out my motherboard with a 128 Gb (I had sent a 64 Gb). I actually quite happy my phone bricked itself. Haha
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
andrewnelson23 said:
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
Click to expand...
Click to collapse
On the same boat. Mine's stuck on bootloop, no recovery. 1 year is pretty good considering I've only had the device for 3 months...
Nexus 6p here in the UK, Got the OTA update yesterday and it caused crashes immediately. Had two crashes when it immediately rebooted and seemed ok. A third one soon followed and got stuck in a boot loop, a few minutes after it fixed it self and seemingly working fine. An hour later i was playing a game and it just locked, screenfroze and a buzzing noise from the speakers before going into a boot loop. Left it for a few hours while at the cinema and nothing.
Bought directly from Google and still under warranty. Interestingly though, i bought my 6p in March 2016, I then had to RMA it a few months later as the USB C port randomly broke I will be doing my second RMA in less than a year. When checking my IMEI the google support operative actually stated I was under warranty till August 2018. So a 30 month warranty. Got a new one coming out so if anyone develops this problem give them a ring.
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Narom88 said:
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Click to expand...
Click to collapse
That's way too common with this phone. Thinking about moving on to something else.
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