Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/showthread.php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!
i have not used my phone in any wrong way. i did not install a custom rom or anything. no root. randomly in my evedy day normal usage of my phone, it started to restart. and the the problem got worse and worse. for a few minutes, i will be able to use my phone but then my phone will restart and be stuck restarting. most of the times i cant even go into recovery mode. it restarts again when i get to that. i already reseted my phone, and i wiped the partition.
i have a samsung galaxy s6 SM-G920W8 telus/koodo 32 gb. i got the battery replaced by samsung but that didnt work. i noticed that after a few hours, my phone stops restarting when it reaches to 10% battery life.
WHAT DO I DO?? YOU GUYS ARE THE PHONE EXPERTS!!
You might want to try re-flashing the firmware. If that doesn't fix it, then you probably have a faulty device.
i tried reflashing but now i got "there has been an error updating the softawre. please use smart switch to recover" or something like that. and my phone is not supported by smart switch..... and when ever i try using odin, i always get NAND write error.i have a telus locked phone, 5.0.2 or 5.1.1 firmware. it is the latest odin and i have the drivers and i tried several solutions but that didnt help with the NAND write error.
Jaadi said:
i tried reflashing but now i got "there has been an error updating the softawre. please use smart switch to recover" or something like that. and my phone is not supported by smart switch..... and when ever i try using odin, i always get NAND write error.i have a telus locked phone, 5.0.2 or 5.1.1 firmware. it is the latest odin and i have the drivers and i tried several solutions but that didnt help with the NAND write error.
Click to expand...
Click to collapse
Have you tried the original LATEST firmware from SamMobile? Using the original cable? The latest version of Odin?
Immoblize said:
Have you tried the original LATEST firmware from SamMobile? Using the original cable? The latest version of Odin?
Click to expand...
Click to collapse
latest telus/koodo version i can find for my galaxy s6 SM-G920w8 is 5.0.2. i only use my origional usb cable. i always get nand write error. my version is 3.10.7 of odin.
phone: SM-G920WZKATLS
locked to: telus/koodo
firmware: 5.0.2
i tried a 5.1.1 update too but that didnt work. i tried a rogers one but i still got nand write failure. on my s6, it says "
system rev. check fail device: 2 binary 1"
Ok...make sure you enable developer options...and enable OEM unlock....also go to security settings and make sure Reactivation lock is disabled or unchecked. ..then try flashing the firmware and it should go through just fine
Sent from my SM-N910G using Tapatalk
i managed to flash a rogers firmware using the samfirm software but my phone is still restarting multiple times
My sister had a Galaxy S4 that would randomly reboot once in a while. Over time it became more frequent until it would barely finish booting before it would restart. Eventually it stopped turning on altogether.
Before it died completely, I tried different firmware versions and three different batteries and no change. I even took out the motherboard and put it in another S4 and it still wouldn't boot. Put the other S4's motherboard into the broken phone and it worked just fine. So it was something on the motherboard that died.
Sounds like a similar issue with your S6. Fact is, if a full wipe and firmware flash doesn't fix it, it's a hardware issue and there's nothing we can do.
ok i really need help with this i have tried to restore 10x and i ether get a SLOW device and reboots when its starts applications or the device reboots then inters mmc_read fail continue on still nothing i really need help i have also installed the cok2 base band also still nothing can anyone please help. And also getting a replacement is not an option also
Update#2 i got it working now in 5.1.1 update had to but know there is random freeze time and reboots and when opening apps it also freezes any help?
Try DEEP FORMAT
I am having a problem with rooting my S6. Every time I try I get an error when it gets to the step of checking the RAMdisk or something like that and it says recovery failed or something, it goes by very quickly. Then my phone just reboots normally except now I cannot update my phone because I have changed the OS even though it did not root successfully.
Okay. I was messing around with my firmware which I've done in the past. I've had a few problems then due to my phone model being obscure (Samsung Galaxy S6: SM-S906L). I've always had a copy of the firmware saved to my computer in the event of a bootloop or a similar issue, I figured I could just flash it with Odin to fix it. I have also done this in the past. After accidently wiping my phone, I went to re-install Magisk, but noticed my phone trying to push an update. I let it go through without much though and after it finished saw it didn't change much. I carried on with re-installing Magisk when I figured I might as well fix some problems I had with booting the phone (I would have to boot it into download mode then recovery to get it out of a bootloop each time I turned it off). I carried on with flashing my saved firmware to fix the problem. Everything flashed fine except the bootloader. It's come to my understanding now that because I let the update carry through with my phone, my saved firmware is no longer compatiable dispite the fact that it didn't change my android version. So now I have a bootloader installed that is meant for a higher update without my known ability to downgrade. Due to the obscurity of my phone model, I can't find anything to bring my firmware up to what my bootloader is at. So now my phone is stuck in a bootloop with the ability to access download mode, but recovery mode simply gives me a "recovery is not seandroid enforcing" error. I would greatly appreciate it if someone has any advise they could give me.