Hi there. I have a Galaxy A6 with broken screen. I don't know if touchscreen works, but all I see is a permanently white screen.
All I want is to recover my files from in there, but obviously all I see on PC is an empty device because the phone is not unlocked. I stupidly didn't set a Samsung account in the device, so unlocking it with find my device is not an option. There's no USB debugging or OEM unlocking done either. Here's what I already tried:
1. Rebooting in recovery mode and trying to get into ADB: nope, stock recovery ROM apparently doesn't allow that.
2. Rebooting in download mode and flashing TWRP with Odin to get a recovery with adb and disk mounting enabled: Odin sees the device and start flashing, but then fails. This is the output:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 25 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write 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)
3. Trying to flash stuff with adb and fastboot while in download mode: adb and fastboot don't see the device at all in any mode (tried normal boot, recovery and download). In windows device manager, the device is seen, in download mode, as "Samsung Mobile USB Modem". Yes, I have installed the Samsung drivers.
Does anyone have a clue about what can I do? Thanks for the help!
Related
So I tried updating to the newest Cyanogenmod Beta1 when it failed to boot repeatedly I went to reflash via Odin using stock JM9 with repartition 803.pit. This is what I got on Odin:
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> modem.bin
<ID:0/004> modem.bin
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
I had selected the modem and rom file that came with the samfirmware.com package.
Now phone will not even turn on, react to button presses, or show that it is charging while plugged in.. Tried taking out battery and putting it back in a few times with no luck.
This is an international version of the phone. Am I screwed? Could the battery have died while flashing or could the bootloader have been messed with?
I am panicing
Did you find a solution?
I have run into the identical issue and was wondering what your solution was?
I flashed the Vibrant firmware by accident onto my GT-i9000m and now the phone is dead, no boot screen, no logo, no reaction to any button combo.
I previously used the usb jig to get into the download mode, and when I reflashed a known to be good rom back on the phone I checked off "update bootloader" assuming the bootloader was at fault. Big mistake.
I've ordered a replacement phone from Bell, but if you have any info it would be greatly appreciated.
Thank you in advance.
This is resolved (I simply pulled battery, and tried again.)
Hello,
Quick backstory. Prior to the last OTA from ATT I could actually get, I had used towerlroot and everything worked fine. I then updated and lost root(naturally). Now I could not get my S5 to OTA to the most recent update (currently running G900AUCU2ANG3) and tried to use ODIN to flash the original Stock firmware. This process failed. Any suggestions on how I can start over?
Edit to add:It is soft bricked now. Can only load into the "Kies" recovery screen
Here is ODIN output: <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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Leon
Hello
I have a problem , try to restore my samsung tab s2 with original ROM by Odin but may fail when I try to flash the original ROM .
Have a T810
Great.
A littlr more information would help us help you.
Which version of Odin, what is failing, what if any messages are Odin or the device giving you?
kvadde said:
Hello
I have a problem , try to restore my samsung tab s2 with original ROM by Odin but may fail when I try to flash the original ROM .
Have a T810
Click to expand...
Click to collapse
I had some issues with ODIN failing when trying to go back to stock after rooting failed. I found a Samsung tool called SmartSwitch (suggested in the error I was getting )and installed and ran it on my PC to get my tablet back in stock working order. You can get it from Samsung.
Sent from my SM-T810 using XDA Free mobile app
The only reason why you would get issues flashing a stock firmware with odin is if the firmware isn't intended for your device.
Odin is quite smart and can prevent you from bricking your device.
I try to flash this one T810XXU1BOH7_T810XAR1BOH7_HOME.tar, Now i have flash custom rom so my tab si working but cant flash to stock rom.
Sorry my bad english :/
lakingslayer said:
I had some issues with ODIN failing when trying to go back to stock after rooting failed. I found a Samsung tool called SmartSwitch (suggested in the error I was getting )and installed and ran it on my PC to get my tablet back in stock working order. You can get it from Samsung.
Sent from my SM-T810 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you its work
I'm having the same issue. Odin fails on me when I'm attempting to install the stock rom.
I see the note about using SmartSwitch, but when I try to run it, it says my device isn't support. I tried used Kies, and I get the same message, that my device isn't supported.
I have a Galaxy Tab S2 8.0. T710 model, running Cyanogenmod 12.1
EDIT:
Here's what Odin is telling me.
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> system.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
shaneman150 said:
I'm having the same issue. Odin fails on me when I'm attempting to install the stock rom.
I see the note about using SmartSwitch, but when I try to run it, it says my device isn't support. I tried used Kies, and I get the same message, that my device isn't supported.
I have a Galaxy Tab S2 8.0. T710 model, running Cyanogenmod 12.1
EDIT:
Here's what Odin is telling me.
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> system.img
<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
One more with problems when having CM. Try flashing TW ROM and then run Odin with stock firmware. BTW why ur odin is not checking MD5? What file did you download?
shaneman150 said:
I'm having the same issue. Odin fails on me when I'm attempting to install the stock rom.
I see the note about using SmartSwitch, but when I try to run it, it says my device isn't support. I tried used Kies, and I get the same message, that my device isn't supported.
I have a Galaxy Tab S2 8.0. T710 model, running Cyanogenmod 12.1
EDIT:
Here's what Odin is telling me.
Added!!
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
boot.img
NAND Write Start!!
cache.img
hidden.img
recovery.img
sboot.bin
system.img
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Select repartition when flashing stock rom.
Coming out of an old build of Maximum Overdrive from last year, I felt the need to update. Wiped, found base/build epj2, flashed and rooted that. I guess that wasnt the latest build, it think it was released in oct 2016. Had major issues with this firmware, So i rewiped, reflashed epj2, and just let tmobile ota's take over. Now Im on baseband/ build N910T3UVS3EQE2, which is the latest firmware to date.
My problem, flashing twrp does nothing. Im getting no errors in odin, (see text below) when I reboot into recovery after flashing, I still have stock recovery. First time Ive encountered this. If its relevant, Ive tried odin 3.12.3 and 3.12.7, and twrp 3.0.2 and 3.1.1. Im out of ideas at this point, and my searches have turned up nothing related to specifically root issues related to eqe2 firmware.
Any tips would be appreciated Thanks!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
scoogots said:
Coming out of an old build of Maximum Overdrive from last year, I felt the need to update. Wiped, found base/build epj2, flashed and rooted that. I guess that wasnt the latest build, it think it was released in oct 2016. Had major issues with this firmware, So i rewiped, reflashed epj2, and just let tmobile ota's take over. Now Im on baseband/ build N910T3UVS3EQE2, which is the latest firmware to date.
My problem, flashing twrp does nothing. Im getting no errors in odin, (see text below) when I reboot into recovery after flashing, I still have stock recovery. First time Ive encountered this. If its relevant, Ive tried odin 3.12.3 and 3.12.7, and twrp 3.0.2 and 3.1.1. Im out of ideas at this point, and my searches have turned up nothing related to specifically root issues related to eqe2 firmware.
Any tips would be appreciated Thanks!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
Click to expand...
Click to collapse
TWRP Recovery might be Released within a few months for this base, now if you can downgrade to epj2 then do it and redo the twrp if you cant then try to downgrade to 5.1.1 and then upgrade to epj2
I'm on the same build but I'm able to install TWRP and it works. I can even install different versions of TWRP. The problem I have after is no matter what ROM I try to flash after I get either error 7, error 6, or errors about the zip file. When I try to Odin it just crashes. I wonder if this build is more secure than others?
scoogots said:
Coming out of an old build of Maximum Overdrive from last year, I felt the need to update. Wiped, found base/build epj2, flashed and rooted that. I guess that wasnt the latest build, it think it was released in oct 2016. Had major issues with this firmware, So i rewiped, reflashed epj2, and just let tmobile ota's take over. Now Im on baseband/ build N910T3UVS3EQE2, which is the latest firmware to date.
My problem, flashing twrp does nothing. Im getting no errors in odin, (see text below) when I reboot into recovery after flashing, I still have stock recovery. First time Ive encountered this. If its relevant, Ive tried odin 3.12.3 and 3.12.7, and twrp 3.0.2 and 3.1.1. Im out of ideas at this point, and my searches have turned up nothing related to specifically root issues related to eqe2 firmware.
Any tips would be appreciated Thanks!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Are you unchecking Auto reboot befour flashing twrp?...pulling the battery and booting directly into recovery to make it stick?
Hey Everyone,
New to this, so excuse my ignorance, but I was attempting to remove the FRP lock from a tablet E (SM-T377P) I purchased from a few from a company that used them.. Flashed it with stock firmware thinking it would just remove the lock (again, new) and clearly that isn't the case. Did some searching and found some firmware on here that actually put 5.1.1 and since I wasn't thinking, flashed that version on the tablet with odin 3.14. Device now only goes into factory mode and I cannot flash with either the combination file or stock firmware for 6 or 7, getting error Fused 3/Binary 2). Not really sure where to go from here, if anywhere, if there is anyone that could offer any help that would be great. (Not new to computers or tech, so I am pretty literate with any questions).
Odin Error is...
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2360 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Still looking for some help, thanks!
Update: Was able to find a fix and its working now!