My Galaxy S6 recently took a dip in a lake and would not turn on. After trying to displace the water with 91% isopropyl alcohol and I tried to power on again, but no LEDs and would not bootup still. I disassembled the phone and tried cleaning the board with a toothbrush and alcohol to clean any corrosion and hope that my attempts to turn it on did not permanently damage any components. After the cleaning the LEDs turn on, but the screen seems to be damaged beyond repair.
At this point salvaging the phone is not a priority, some very important and irreplaceable pictures that were not yet backed-up are my only concern. Another XDA user suggested trying to install a custom recovery but ODIN keeps failing. I cannot tell you what the S6 screen is showing of course, even putting it into download mode is a bit of a chore.
I am trying to install TWRP on a SM-G920P with ODIN 3.10.7
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have also tried other versions of TWRP and ODIN, all have the same error.
Thanks in advance
Did you by chance have USB debugging enabled? If so, boot phone normally, and use 'adb pull' commands to retrieve what you want.
Sent from my SM-G920W8 using Tapatalk
DarryDoo said:
Did you by chance have USB debugging enabled? If so, boot phone normally, and use 'adb pull' commands to retrieve what you want.
Sent from my SM-G920W8 using Tapatalk
Click to expand...
Click to collapse
Sorry, forgot to mention that debugging has not been enabled. Is there anyway to force USB debugging?
Related
So here's what happened. I tried to install CWM 6.0.1.2 using EZ Recovery and it rebooted into ODIN with the words, could not do normal boot, in red. When I reboot it, it would just go back to the ODIN screen, so I tried to use the root 66 method. At first, it would get to system.img.ext4, but the green bar would barely move and be stuck there for 30 minutes. I would try again by taking out the USB cord, rebooting phone (maybe bad idea?). I did it again and it would be stuck there. I tried different USB ports on my laptop. Some will get to system.img and be stuck or get to recovery.img and say fail. Is my phone hard bricked or is there something else I can do? Thanks!
I also tried it on a different computer and it gets stuck on boot.img instead. Any help would be greatly appreciated!
It seems like using the older version of Odin gave me more consistent results. I now always get to system.img before it fails. The green bar gets 1/3 of the way then says failed.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway to get it to be successful?
Hi all,
Been searching these forums for the past 3 hours and trying numerous options and still haven't been able to fix my problem.
Long story short, dropped S6 in water, turned off and left in rice bag for 2 weeks.
Tried to turn on today and it only boots to download mode, everything else just reboots the phone. Also it will only turn on when connected to USB so i'm guessing the battery is dead also.
My main concern is I have photos that I really want to try and recover and yes I know I know, always have a backup, as a desktop technician I really should have had that setup on my phone but here we are.
So my main target is to somehow get into recovery mode and then use ADB to pull files from the phone.
I've tried to flash many different recovery files but they always fail in Odin v3.10.7, log for Odin is:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I don't want to flash stock firmware cause I'm guessing that will wipe the phone and photos?
Any help would be appreciated!
alicg said:
Hi all,
Been searching these forums for the past 3 hours and trying numerous options and still haven't been able to fix my problem.
Long story short, dropped S6 in water, turned off and left in rice bag for 2 weeks.
Tried to turn on today and it only boots to download mode, everything else just reboots the phone. Also it will only turn on when connected to USB so i'm guessing the battery is dead also.
My main concern is I have photos that I really want to try and recover and yes I know I know, always have a backup, as a desktop technician I really should have had that setup on my phone but here we are.
So my main target is to somehow get into recovery mode and then use ADB to pull files from the phone.
I've tried to flash many different recovery files but they always fail in Odin v3.10.7, log for Odin is:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I don't want to flash stock firmware cause I'm guessing that will wipe the phone and photos?
Any help would be appreciated!
Click to expand...
Click to collapse
A long time ago my s2 got stuck in download mode after getting wet, back then it was caused by some corrosion in the usb port. I fixed it by trying to scrape it clean with a usb cable, you could also try isopropylalcohol (even let it soak in there for a few days)
btw the s2 continued working up until this day (a friend now has it)
godutch said:
A long time ago my s2 got stuck in download mode after getting wet, back then it was caused by some corrosion in the usb port. I fixed it by trying to scrape it clean with a usb cable, you could also try isopropylalcohol (even let it soak in there for a few days)
btw the s2 continued working up until this day (a friend now has it)
Click to expand...
Click to collapse
I heard of this isopropylalcohol, so just fill a jar and drop phone in for few days? And then back in rice?
Spent 2 weeks drying the thing out, kind of worried to attempt this.
But as I've nothing to lose!
alicg said:
I heard of this isopropylalcohol, so just fill a jar and drop phone in for few days? And then back in rice?
Spent 2 weeks drying the thing out, kind of worried to attempt this.
But as I've nothing to lose!
Click to expand...
Click to collapse
I think isopropyl alcohol doesn't conduct, so no short circuits and no need to dry but from my experience with keyboards which got wet and not dried properly those thin contacts and flex cables are very prone to just corroding through and through.
Hello. Sorry for my enlgish.
Theres a soft-bricked SM-P900, I can normally open download mode. (asking for Kies)
Here's the Odin log:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It's always stucks on "system.img" in ANY .tar I try to flash.
Yesterday, it could power on. But now it's not powering on at all. I hope this is because of battery charge.
===UPD: Yes, it was because of battery charge. Now it's powered on.
What should I do, guys? Help, please!
V01DY said:
Hello. Sorry for my enlgish.
Theres a soft-bricked SM-P900, I can normally open download mode. (asking for Kies)
Here's the Odin log:
It's always stucks on "system.img" in ANY .tar I try to flash.
Yesterday, it could power on. But now it's not powering on at all. I hope this is because of battery charge.
===UPD: Yes, it was because of battery charge. Now it's powered on.
What should I do, guys? Help, please!
Click to expand...
Click to collapse
If it were me I would verify the files, perhaps redownload it. I'd also try a different USB port, cable or reinstall USB drivers on the computer. Sometimes one has to clean out old device drivers manually. I've done this with USBDEVIEW.
Sent from my SM-P900 using Tapatalk
Hello all,
My tablet note 10.1 N8000 (3G, Wi-Fi, 16 GB) suddenly got stuck in bootloop. I was not trying to flash anything when it did so, nor did I flashed anything recently before the bootloop (although it seemed to constantly freeze before the bootloop when trying to switch between my two whatsapp accounts that I have using Titanium Backup which allows creating more than one account in all apps).
I did however root the device when I bought it in 2012 and it was the only time I did so, and I still have USB debugging mode on.
The device would bootloop in the first Samsung logo most of the time, but on rare occasions it would move to the second animated logo and get stuck repeating the animation forever.
I can only access Odin Download mode, but cannot access recovery mode (when I try to do so, it shows the first Samsung logo, then attempts to go into recovery but only shows a lit black screen then reboots).
Here are the steps I did (might help some of you, but unfortunately didn't help me):
1) I tried flashing a custom recovery (CMW, Philz touch, TWRP, and stock recovery) through Odin (Odin 3 version v3.10.6):
- Put the .tar file in AP slot then put device in download mode (power key + volume down), then plug device into my computer.
- Check only auto restart and F. time reset.
- Here's what it says after flashing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
2) I tried flashing stock rom through Odin:
(Roms I tried: N8000XXCMF1, N8000XXUDOF1, N8000XWALG7, N8000XXCMA2, N8000XXUDOF1)
- I put the .tar.md5 file in AP and follow same steps above, here's what Odin says after flashing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
3) I tried following the post here:
http://forum.xda-developers.com/galaxy-note-10-1/general/n8000-stuck-samsung-logo-t3212923
I followed everything until the part where I have to access recovery (because I could not access recovery still to flash rom from recovery). Here's what it says in Odin after it's done:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300_Repair_efs.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> efs.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But again it did not work even though it always says "PASS"! And I also tried flashing stock rom after trying this method through Odin, shows success but still stuck in bootloop.
I don't know what else to try really. I will not take it to support to fix it, either I fix it myself or use it as a cutting board.
If anyone has any ideas please reply. I'm sure there are more things to try.
EDIT:
- Is there a way to clear cache without accessing recovery (since I can't access it)? Lots of people say it worked after clearing cache.
- Is Nand erase all an option? I wish someone would explain it in details instead of telling me not to do it without saying exactly why.
- Could the problem be in hardware? How can I know if so?
NaND ERASE WILL KILL THE PRODUCT .
JJEgan said:
NaND ERASE WILL KILL THE PRODUCT .
Click to expand...
Click to collapse
So you mean that it will erase everything even the Odin download mode and the Samsung logo? Why would they include this option then? I don't see any practical use of it :/
No help?
RHAddict said:
So you mean that it will erase everything even the Odin download mode and the Samsung logo? Why would they include this option then? I don't see any practical use of it :/
Click to expand...
Click to collapse
Odin is a tool that we are able to borrow .
You could try recovery via KIES .
RHAddict said:
No help?
Click to expand...
Click to collapse
HI RHAddict,
It happened to my Note GT-N8000, if a Hardware failure. If you send to SAMSUNG service center it will cost u around US$ 200 for motherboard replacement. But i manage to find a mobile service center, the technician said it only 1 of the chip in motherboard out of service. I got my tablet fixed just US$ 50-60. Now is working as is it before.
TQ
My Samsung 8010 has just gone exactly the same way. Cannot enter recovery mode, just get a blank lit screen for a second then goes back into a reboot cycle and never gets past the Samsung logo. Did you get anywhere with fixing it, or have you given up? Was thinking of taking mine to a service centre, but probably not worth it?
Hello all,
I have a Samsung Galaxy S7, from Rogers but unlocked, version SM-G930W8 that I bought second hand.
Phone was rooted, I factory reset it to prepare it for my wife, then installed apps and moved data and everything.
Turned the phone off and put it aside, the next day I bought a new Nano SIM, turned it ON and I got "Custom binary blocked by FRP lock".
I downloaded G930W8VLU1APG1_G930W8OYA1APG1_XAC tried flashing via ODIN and got this:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> Home Binary Download
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the phone I had: SW REV. CHECK FAIL. DEVICE: 2. BINARY: 1
Tried: twrp-3.0.2-4-herolte.img.tar with Odin
It goes all the way through but fails at the end with this message:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the phone I had: Custom Binary(Recovery) Blocked by FRP Lock
Also I have tried multiple computers, multiple cables, multiple versions of ODIN, ...
Now the phone is stuck at the Samsung screen and won’t turn on or off, until the battery dies.
Tried Smart Switch but it asks for the serial number, which I do not have. (There is just IMEI on the back of the phone)
Not sure but I think somehow after the factory reset the OEM Unlock got disabled.
Any help is greatly appreciated.
Did you ever figure this out? I'm facing the same thing and hoping my phone isn't bricked.
https://forum.xda-developers.com/galaxy-s7/help/potentially-bricked-s7-flat-custom-t3583502
This will fix and let you flash.
1) Open Odin, place all the necessary files into their slots.
2) Go the the options tab, make sure "Auto Reboot" IS ticked.
3) Press "start", but as soon as you do, hold down Vol down+Home+Power on your phone.
Odin will fail and your phone will reboot into download mode again.
Now press "Start" in Odin again, and your phone should flash without a problem.
This might take a few attempts to get right, but I hope it helps.