So I attempted the root process via ODIN. Every time ODIN would hang on the <ID:0/004> SetupConnection.. step For greater than 15 minutes. I pulled the battery and attempted the process again 3 times.
After that I got the phone --!-- computer error saying " Firmware upgrade encountered an issue."
Now when I plug the phone into ODIN now get
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.. and it hangs.
I have double and triple checked my drivers. Running odin in admin mode... tried compatibility mode... Tried Kies Recovery [does absolutely nothing]
I had this issue back on my Vibrant and all we had to do was flash the stock .tar image and the .pit files...
Do we have / are we working on the stock image and/or .pit files?
Is there anything I can do to help solve this issue?
EDIT: Redid the steps on an old laptop and it worked like a charm... weird. So if your phone gets stuck on setup connection try it on another computer. It might have been because I messed with ODIN so much with my vibrant?? *shrug*
Related
I recently found out I soft bricked my phone after browsing through the forums. I looked up for the solution and it turns out that I need to reset it back, no problem with that so I installed odin back again (I rooted my phone before so I had it). I first downloaded the official firmware from sammobile or some site like that and I downloaded a PIT file for my phone because the tutorial said it was essential when resetting a smartphone. I followed every step but when I launch odin and select the required tick boxes and the PDA PITi I start it. It starts up but in the middle of the loading I shows up the DO NOT TURN OFF THE TARGET!!! message and It stops.
<OSM> Leave CS..
<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>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the error and I can't seem tı get past it. I really need to deal with this quickly so if any of you have a solution, ı would appreciate it. Thanks
Anyone has the same issue? I need to fix this ASAP.
a
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
Now the error goes like this and nothing more.
aqertmen said:
Anyone has the same issue? I need to fix this ASAP.
Click to expand...
Click to collapse
I'm getting the exact same problem, can't fix it
Have you made any progress?
Thanks.
aqertmen said:
I recently found out I soft bricked my phone after browsing through the forums. I looked up for the solution and it turns out that I need to reset it back, no problem with that so I installed odin back again (I rooted my phone before so I had it). I first downloaded the official firmware from sammobile or some site like that and I downloaded a PIT file for my phone because the tutorial said it was essential when resetting a smartphone. I followed every step but when I launch odin and select the required tick boxes and the PDA PITi I start it. It starts up but in the middle of the loading I shows up the DO NOT TURN OFF THE TARGET!!! message and It stops.
<OSM> Leave CS..
<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>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the error and I can't seem tı get past it. I really need to deal with this quickly so if any of you have a solution, ı would appreciate it. Thanks
Click to expand...
Click to collapse
doc1975 said:
I'm getting the exact same problem, can't fix it
Have you made any progress?
Thanks.
Click to expand...
Click to collapse
Hi
Do you have a custom recovery?
Which phonemodel do you have?
U can install TWRP through Odin using a tar file. Go to TWRP and search your model, get the tar file and install it.
From TWRP u can sideload a rom using ADB.
You can push files to the phone using it, that way u can push the rom to the phone and install it through TWRP.
A long way around but worth trying when all else fail.
So, I've recently wanted to use a custom ROM for my phone, and I have done this before, but there's a bunch of changes I guess. I thought that "unified s3" meant that the ATT variants and others (including my i747m) would be compatible, so I tried to flash "Liquid Smooth v3.0" ROM but it didn't work with TWRP. So I got CWM and restored my phone (also my restore file by accident) so my phone was totally wiped, but I could flash the ROM. The problem occurs here, the phone WILL NOT boot, it is stuck at the "Samsung Galaxy S III" splash and won't go past it. I cannot delete the cache or anything without the phone restarting itself. I tried to flash a modem with Odin but get an error also.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I've been searching the forums for a way to fix my i747m but I cannot find anything. Any solutions or is my phone dead. Also I can get into both recovery and download screen. I cannot flash a stock ROM because another error pops up. And when I go into download mode and flash, the "QUALCOMM SECUREBOOT: ENABLE" turns into "SECURE CHECK FAIL : aboot"
Tonamon said:
So, I've recently wanted to use a custom ROM for my phone, and I have done this before, but there's a bunch of changes I guess. I thought that "unified s3" meant that the ATT variants and others (including my i747m) would be compatible, so I tried to flash "Liquid Smooth v3.0" ROM but it didn't work with TWRP. So I got CWM and restored my phone (also my restore file by accident) so my phone was totally wiped, but I could flash the ROM. The problem occurs here, the phone WILL NOT boot, it is stuck at the "Samsung Galaxy S III" splash and won't go past it. I cannot delete the cache or anything without the phone restarting itself. I tried to flash a modem with Odin but get an error also.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I've been searching the forums for a way to fix my i747m but I cannot find anything. Any solutions or is my phone dead. Also I can get into both recovery and download screen. I cannot flash a stock ROM because another error pops up. And when I go into download mode and flash, the "QUALCOMM SECUREBOOT: ENABLE" turns into "SECURE CHECK FAIL : aboot"
Click to expand...
Click to collapse
Since you can get into both download and recovery modes, there is plenty of hope and your phone is far from dead. Odin probably failed because you were trying to flash incompatible firmware or one that involved a bootloader downgrade attempt. You may be able to recover by re-flashing the correct firmware from (custom) recovery. You need to provide more information including what stock were you on before going custom and what stock you are now trying to revert to. When flashing stock firmware, however, you need to be sure you are working with the right ones. In spite of the near similarity in the names, firmware for the i747U... (AT&T) is different from the Canadian versions (i747M...) and you should be careful to pick only the ones specific to your phone model. You probably were on a 4.3 bootloader so your safest bet now may be to search for and download the i747M 4.3 stock rom, bootloader/modem and kernel zips and reflash these via recovery. If you are on TWRP, you may also do an advance wipe to remove all existing firmware before flashing new ones.
I have bricked my S3 before and have successfully unbricked it. This time is very much unlike the last, however. To start with, I don't know what caused the brick. My S3 has been working perfectly on rooted stock firmware for several months. The day it bricked, I was using it normally and hit the power button for it to go to sleep. 3 hours later I noticed I hadn't heard any notifications and I found that my phone wasn't turning on. So for starters, I don't even know what caused my phone to become bricked.
Anywho, I located the unbrick img, booted into Linux, and flashed the image to an SD card. Popped that into the S3 and....nothing. After some searching I found there was a specific unbrick img for the new bootloader that came with the KK updates. After flashing that image to the SD and popping it in the S3 I was greeted with the "Boot Recovery Mode" which appears to transfer to Odin Mode just fine.
I open Odin 3.07 and tried flashing the factory reset tar for NJ2 and I get this:
Code:
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So I found 2 different PIT files for my Sprint Galaxy S3 16GB. Both give me this error:
Code:
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried this in Odin 3.09 and even 1.85 just to see if any of that would magically work. Nope. I saw several users report that rebooting the phone/PC would get the PIT to flash but nothing on that front either. So I'm guessing that means the PIT files are bad but I find that a little difficult to believe. I also noticed that Odin 1.85 reports the device as "Android+SLP" and not an S3. I also read about the S3 having a problem with its eMMC and that it would need to be shipped away for motherboard surgery. So I'm prepared to call the time of death on this phone but I figured I would give one last ditch attempt by presenting my situation to the genius collective of XDA. Any suggestions?
Hello everyone and thank you for checking my post. It is also my first of I hope many on XDA!
I had a CM 12.1 Nightly on my Tab Pro 12.2 and it was beginning to get a little slow, so I went into recovery (TWRP) and started a factory reset. It though got frozen at "erasing cache". It then rebooted itself and was stuck on the CM logo for minutes on end. So then I turned it off, opened Odin, and tried to install a newer nightly, only for it to get stuck in the same place, "cache". Odin then gave me a "fail" screen, which I have pasted below in the code section.
So now the tablet is stuck at the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" screen. I tried Kies and it detects that I have plugged a device in but does not connect to it, it stays stuck in "trying to connect". I can go to Download mode but that is about it. When trying to flash anything, even the stock Samsung 5.1.1 firmware, it gives me a "Fail" like so:
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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
I would appreciate if any of you could help me with this issue, I am willing to try your suggestions
Hello, I was just wondering if anyone can help me fix this problem, anyways, I bought the phone it was on Android 9 Pie, I got the notification for software update, the phone was working fine, the owner said to me that there was a motherboard issue which I neglect and I'm fully sure that it's a software problem with the latest update, anyways, I downloaded and installed the update and when it finished It started going in nonstop bootloop, I tried flashing the device with the latest firmware, the Carier ID is: INS(INDIA), however when I try to flash the phone the Odin shows me this:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5716 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone also says SW REV CHECK FAIL (Bootloader) Device 7, Binary: 6 after failed ODIN flashing
I know the error is saying to me that I'm trying to DOWN-grade the phone but it's the latest official firmware for the phone, i tried also flashing it with on BL and AP in Odin and Z3x tools, however when I try to flash it in Z3X tool and when I insert only AP and BL the loading on the phone goes to the middle, and sometimes Z3X tool shows that the flashing is done but it's still in a Bootloop.
Honestly I'm desperate for the help, any kind of help will be appreciated, if someone knows how to help and needs fruther information, feel free to ask.
Thanks in advance!
Also I cannot enter to Recovery Mode the phone either goes to Download Mode or constant bootloop
Well, i think the phone has the wrong CSC or something else.
I was seeing the SW REV CHECK FAIL part and it seems like that the phone's binary is U7, but firmware is U6, meaning that the phone has a different CSC.
If it's possible, flash another firmware with a different CSC, but with U7.
And tell if it works.
Do you have any link to U7 firmware I tried flashing with like 10 combinations, none of them worked, I was searching for U7 firmware but i couldn't find it, I haven't slept for 3 days trying to fix it, or if you can tell me how can I recognize the file combination has the U7 firmware, I think there's a some trick in reading the symobols in combination files but I don't know, thanks for replying!