I have a Samsung Note 8 GT-N5110 (WiFi only) that is stuck at the Samsung logo.
This started after there was an attempt to flash a non-stock firmware and the device powered off before it was done.
When I attempt to enter Recovery Mode (Volume Up + Home + Power) it displays "Write Fail!" in upper left of the screen.
I am able to enter "Download Mode", so I've tried flashing a stock firmware using Odin.
I've tried both a One-Click recovery based on ODIN3 v1.81 and also tried Odin3 v3.12.10.
Each time, Odin fails, with a message:
write fail!!
SW REV. CHECK FAIL. DEVICE:2, BINARY:1
I've tried various versions of firmware, and nothing seems to work.
I've tried disconnecting the battery for a minute or so, and it still fails.
Any ideas what else I can try?
I have screen shots and detailed logs of what I've been getting, if that helps.
Thanks!
Believe it or not, I still have this device, and have not been able to get it to work!
So, I'll just revive this zombie post more than 2 years later, and see if anyone has any idea on what to do.
I'm in the fourth (fifth? sixth?) week of corona-quarrantine, so plenty of time to look into this!
The tablet needs more power than the computer's USB port can deliver. Thus, it will slowly drain the battery while connected to the computer and working via ADB, Odin or Heimdall. Seems like that has been the case in your earlier attempt, resulting in a corrupt flash memory. I can't tell if it's really defective or just corrupt and in need of formatting.
I'd try to:
1) Charge the battery
2) Copy LineageOS to the MicroSD card
3) Boot into download mode and install TWRP only via Odin or Heimdall. If this works,
4) Boot into Recovery (TWRP, not the stock one!), connect the charger to keep it powered and go from there (wipe and repair the internal flash, install LineageOS)
If this doesn't work, try if you can find any service functions in Odin or Heimdall to wipe and repair the internal flash.
Good Luck!
Ektus.
Hi Ektus,
Thanks for your help!
I will try as you suggested, and see what happens.
I'll let you know how I do.
Thanks!
I had similar problem. What I did is just change the USB cable to new.
Related
My Salutations, I am asking a question in regards to a serious bootloop I have managed to pull myself into.
Most bootloops I usually just enter CWM and flash another rom or restore. This problem however is much more serious.
Every time I attempt to enter CWM it goes directly to download mode. It's as if CWM doesn't exist on my phone anymore or something.
Download mode is the only thing I can access. I have tried multiple attempts to enter any other recovery mode but they all end up getting me to download mode.
This isn't the only problem. I thought this wouldn't be a big deal until I realized my PC can't recognize my phone at all anymore. Even before I got into the bootloop, my phone would only charge but any other recognition from the PC was absent. I have all the correct drivers installed including numerous attempts at re-installing, re-configuring, and restarting my PC.
I think I may have reached an irrecoverable error.
Any ideas would be much appreciated. Thanks.
FYI, The ROM I flashed when my Phone started acting like a bundle of ninnyhammerness was AOKP milestone 6. It's not the ROMs fault of course, seeing as how this ROM is very good. I also had the Darkside kernel. This is when I couldn't manually enter CWM. In stead, I had to let the phone boot up and utilizing the power menu, restart in recovery mode. I thought this was strange at first. I then wiped, and decided to flash the 20th Nightly of AOKP Jellybean just to try it. It booted fine, but then when I had to restart to enter CWM again I chose to flash another Darkside kernel. After this, my phone went into a bootloop. That is where everything else fell apart.
Sounds like either the recovery isn't sitting in the system correctly or its gone. When your phone is in download mode you said that you can't connect to pc. Are you running odin as admin and/or connecting the device to pc previous to putting the battery back?
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Yes I did run Odin as an administrator. I also tried connecting the device prior to putting the battery in, and also after.
I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!
kmcclry said:
I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!
Click to expand...
Click to collapse
Thanks but, it still hasn't worked. It keep saying "USB device not recognized, Device driver software was not successfully installed."
I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.
i3lackDawn said:
I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.
Click to expand...
Click to collapse
also it may be because of a faulty data cable !
Hi,
Summary: Was running Cyanogenmod 10.2.0 and tried to update to 10.2.1. Phone won't boot. Using CWM recovery 6.0.4.3. Factory Reset reports that it can't mount / clear /data (due to encryption?). Can get phone into CWM recovery and Download mode. Haven't been able to successfully connect to PC (ADB or Odin) even though I have samsung drivers.
I do have an unencrypted SD card in the phone so my normal way of flashing is to connect SD card to PC, download, then in CWM recovery to install ZIP from SD card.
Looking to get into any good state - Cyanogenmod 10.2.1, or 10.2.0, or heck go back to stock.
**** I think the answer might be use ODIN and flash back to stock, I see some guides but haven't been able to get ODIN to "see" my phone *****
Details
I had downloaded Cyanogenmod update to phone using "About this phone" menu and when I tried to "Install it" from that window the machine booted into recovery, immediately failed, and rebooted. The phone is encrypted (work requires this) and I discovered Cyanogenmod saves the download to encrypted phone storage and CWM recovery doesn't support encryption.
Downloaded 10.2.1 to my SD card and flashed it. (no back-up, no wiping of cache). Installed successfully, reboot asked me for my encryption password, Android optimized apps, rebooted, encryption password, then blue spinner spins forever.
From here I started my troubleshooting:
- I flashed back to 10.2.0 then flashed Gapps again, no change.
- Reading about boot.img I installed ADB and SDK Manager and tried connecting and flashing boot.img. ADB devices shows up empty. I have installed Samsung drivers.
- Researching going back to Stock points me to installed Triangle to reset my custom ROM count - but I can't boot.
Thanks in advance.
Matt
[Solved] This is for anyone who happens to read this wondering if their phone is screwed. Relax! If you can get into Download mode and Odin can see your phone, you'll be o.k.
Turns out the machine and cable you use do matter. I tried for days connecting using my MAC running Windows 7 Virtual Machine. Once I switched to my Win7 laptop and used the original Samsung cable things starting working out more smoothly.
Steps:
1) Get Odin (mine was 3.09) and run as admin. If you see an error in Korean it's because you have to unzip the entire Odin folder.
2) Get stock firmware for t-mobile. There's only 1 firmware file, I didn't need a PIT nor a specific recovery step. The t-mobile firmware includes everything I needed. Flashing failed in Odin saying Complete Write failure. This had me stumped for hours and hours. When I switched to stock cable and Win7 laptop it succeeded. I never had to check Nand erase all or repartitian (almost did in desparation though). Flash took about 10 minutes but eventually PASSED.
3) However, when it rebooted it asked for encryption key and my old one didn't work. Turns out their are more steps. This scared me.
4) Reboot into recovery (up, home, power) which gave a bunch of scary error messages. Actually those listed at the bottom in http://forum.xda-developers.com/showthread.php?t=1840030.
5) Factory Reset then Wipe Cache
6) Reboot
Now I'm back at stock and breathing a sigh of relief. Unclear if I'll ROM back to Cyanogenmod.
I spent hours and hours reading discussions and going down one dead end after another. I'd say it was like looking for a needle in a haystack but it was the complete opposite. It was like looking for a specific needle in a sea of needles. Every search query yielding tantilizing results and a plethora of step by step guides that ultimately didn't work. A very frustrating experience all around. Good luck to anyone who reads this.
Hi Matt
Similar thing happened to me last night. I am/was using Omni-Nightly build. I plugged it in to the charger before bed, and it rebooted, saying upon reboot - "Encryption Failed" and saying the only way to recover would be to wipe the machine and start again, it then rebooted and all I get is the Samsung boot screen.
Tried rebooting, wiping, everything, Odin, Android Toolkit, nothing works. It shows up on my Linux PCs but not accessible, but not windows at all.
ok so i had the latest cm13 rom on my phone partition is in ext4 had many issues with the rom so i went to flash the stock rom with odin
while the firmware was loading my usb cable failed and an error popped up saying odin process was aborted then the com port went empty (the phone disappeared) no the phone will not go into download mode while trying to get into download mode every thing looks good till you press the up button an you go to odin mode but with a message: firmware upgrade encountered an issue. please select recovery mode in kies and try again.
however my pc will not recognize my phone any more and i can not get into recovery either
in fact if i just plug the phone in it boots up to this message screen without even touching any buttons
I have tried just about everything i can think of even a unified toolkit but nothing will work as i cant access recovery or odin or kies???
I have also gone threw the forums and was not able to find anything pertaining to this directly
please help
Its been a long time since I booted my Galaxy Note-II (GT-N7100) as I use an iPhone and Nexus 5 as my daily drivers.
The phone wont boot past the Samsung Galaxy Note II GT-N7100 logo. I am able to access the recovery and download mode as well, and I have flashed the latest stock rom from Sammobile using the Odin. The flashing was successful. however the phone doesn't boot past the logo. Also the phone will not power up unless connected to a PC, it wont power up even when connected to a charger and will immediately shut down when the USB cable is disconnected from the PC. I flashed TWRP 3.0.2 Custom Recovery using the Odin and tried installing CM 13 based Rom through the mem card, however the log reads patching image unconditionally and also that "Failed to mount /system" (invalid argument). The phone when restarted into recovery can no longer mount the /system partition. However on flashing the stock rom using Odin, the /system partition is available for mounting. The recovery log also shows MTP enabled, but my PC doesn't detect the phone when in recovery, it only detects the phone in Download mode. I have the Samsung drivers installed. Since the phone is not being detected in recovery I am unable to use the adb.
I am out of ideas and request your suggestions other than approaching a service centre.
If I can somehow access the phone via ADB, I might be able to check the memory partitions for corrupt units, and possibly create a custom PIT file to repartition and suit the available memory units.
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
audit13 said:
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
Click to expand...
Click to collapse
Thanks a lot.
Tried your method and finally the phone has booted into the OS.
Had to replace the battery with another spare one in the process.
However the phone is still not being detected by the PC unless it's in Fastboot/ Download mode.
When connected to a computer, does anything appear on the phone screen? If you're using Windows, nothing new appears in device manager?
sorry to jump in this thread but i am having a similar problem
my completely stock tmobile note 2 is stuck on the samsung logo
i have never flashed it or done anything to it
my phone was working really slow, freezing up and battery draining fast
so i did a hard reset and it fixed the problem of running slow and freezing up for a week or so but battery drained fast
so i bought a replacement battery from ebay and installed it and the next day i restarted my phone and it froze on the samsung logo
i tried turning it off and on and still the same thing
any suggestions or should i start a new thread?
fyi i am a noob
I bought this device recently. Unfortunately it seems now that it's hard bricked. I've got the Hyperdrive rom installed and it used to work perfect. The problem started when the battery ran out while I were streaming live TV. Since then it wouldn't boot properly. It was stuck in bootloop, however I were still able to get it into recovery and download mode. I tried to recover from a backup through TWRP but did not succeed properly (the screen just froze after a couple of minutes). Afterwards it was really hard to make it do anything. It started to boot into something called "SDCARD MODE", with options to press the volume up key for normal reboot, and volume down for "download mode". But neither option worked.
I managed to get it into download mode and tried to reflash the original firmware for my device (P600ZHUCNH1) with Odin but it failed. When I rebooted the device the display showed the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I tried to flash the same firmware again with Odin but it failed again.
And since then I haven't managed to turn on the device. Holding Home button + Volume Up + Power or Volume Down + Power doesn't work. Battery is fully charged. Tried to reinstall battery. Tried a USB Jig. But no luck.
Any suggestions on what to do?
Thanks in advance!
@MikkelJakobsen
You have a solution to resolve that problem off yours.
Those 3rd screen image, tell that you need to use the Kies Software to restore your tablet to his own factory firmware.
Just follow this steps:
1. turn off your tablet, and go into "Download Mode"
2. start Kies3 Software in Windows, and go to the menu Tools -> Firmware Upgrade and Initialisation
3. Write the Model number off your tablet -> SM-P600
4. Then write the Serial Number (that on the backcover off the tablet).
5. Confirm all ok.
Then it starts to download the original firware files from the Samsung Servers. And it will flash the firmware.
And that's it. You should have after the tablet running smooth and 100% again!!!!
Best regards!
Flygye said:
@MikkelJakobsen
You have a solution to resolve that problem off yours.
Those 3rd screen image, tell that you need to use the Kies Software to restore your tablet to his own factory firmware.
Just follow this steps:
1. turn off your tablet, and go into "Download Mode"
2. start Kies3 Software in Windows, and go to the menu Tools -> Firmware Upgrade and Initialisation
3. Write the Model number off your tablet -> SM-P600
4. Then write the Serial Number (that on the backcover off the tablet).
5. Confirm all ok.
Then it starts to download the original firware files from the Samsung Servers. And it will flash the firmware.
And that's it. You should have after the tablet running smooth and 100% again!!!!
Best regards!
Click to expand...
Click to collapse
Thanks for your help! However, the problem is that I can't even turn on the tablet anymore. The screen just stays black no matter what I do. So I don't see the "Firmware upgrade encountered an issue" anymore and theremore Kies doesn't recognize any connected device.
Try do take off the back cover from the tablet, disconnect all the flex cables.
Remove the 13 screws from the batery holder, and then disconnect the battery cable's power.
Wait a few seconds, and then place all the parts on the tablet again.
And try to turn on the table again.
See if this helps.