Related
Ok so long story short I had a bad flash because for some reason I was unable to fully copy over a ROM to my SD card (my phone was constantly dismounting from my computer without me clicking disconnect). Now, I am trying to return to Stock via Odin. I have downloaded and unzipped the correct md5 file for the Stock rom for 2.3.6 and put my phone in download mode and ran odin with the md5 file. Now I am stuck with Odin saying this
"ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989UVKL1_HOME_SGH-T989user_CL799405_REV00.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection.."
I have been stuck here for nearly 20 minutes, I have no idea what I should do. Do i pull the battery? restart odin or what?
Any help would be greatly appreciated.
If your phone was disconnecting why did u even try odin? You probably can just get the battery off and try with a better cable?
I had to Odin because when I went into recovery and tried to flash I got stuck at bootloader. Now I am stuck at screen which reads "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
Husam2011 said:
If your phone was disconnecting why did u even try odin? You probably can just get the battery off and try with a better cable?
Click to expand...
Click to collapse
What Husman is trying to explain, if you have issues connecting/disconnecting to your PC, there's a HIGH probability this going to happen again while you're flashing your device with Odin. As he suggested, get the battery off and try to flash it again with a better cable (not a cheap one).
ElYukiPR said:
What Husman is trying to explain, if you have issues connecting/disconnecting to your PC, there's a HIGH probability this going to happen again while you're flashing your device with Odin. As he suggested, get the battery off and try to flash it again with a better cable (not a cheap one).
Click to expand...
Click to collapse
come on man atleast copy my name right.
Husam2011 said:
come on man atleast copy my name right.
Click to expand...
Click to collapse
LOL
OP:
Your phone isn't even bricked. Your phone Turns on, the screen is on, it displays something to you, so it is not bricked.
It looks to me like it didn't even flash the stock ROM on there.
BUT FIRST... what ROM were you trying to flash that was odinable? I don't recall any except the stock ones....
It looks like you got the right stock ROM.. and it looks like you already pulled your battery since you got stuck at ODIN.. hence the firmware update error screen...
You can either pull your battery leave it out for a couple minutes and and get back into odin/download mode and try flashing the ROM again or get a jig to get into download mode... this time use a better cable and try another port...
If it gets stuck at setupconnection again.. do not pull your battery. Your phone has not done anything yet, it's still in odin mode.
SO close odin, change USB port, and start up odin again. repeat until it finally flashes. also switch cables if that doesn't work either.
I am trying to follow the "Very easy steps" on
Re: [GUIDE] Rooting the Samsung Captivate Glide i927/i927r
Steps so far:
Downloaded:
KiesSetup.exe ( 70,227,456 bytes, md5sum=3891cd32e2bc467f77f4d65f0244faf )
Odin3-v1.85.zip ( 203,676 bytes, md5sum=14e3af7c4c01e21527aeaab65e68a75 )
boot2.zip ( 3,944,864 bytes, md5sum=64a78f6f86e13eedba20c2d5243d651 )
i927_factoryfs_rooted_img.tar (432,711,680 bytes, md5sum=2b913a5480008d8ae4c3138411cf099 )
usb_drivers_GalaxyS_x64.zip ( 19,780,425 bytes, md5sum=2378aa7a2f5191eeb832ce5c86b03b1 )
(following file was not initially downloaded)
SGH-I927R_insecure_bootimg.zip ( 3,938,408 bytes, md5sum=09b01d3e49f2a2b7b5817f3fb59c6b9b )
Installed the usb drivers as per the AT&T forums. This is a waste of time. Windows installs it's own USB drivers as soon as I plug in the phone.
I unzipped Odin3-v1.85 to it's own subdir.
Copied i927_factoryfs_rooted_img.tar to Odin dir. Unzipped boot2.zip to get a TAR and copied that to Odin dir.
With phone on and connected via USB, run Odin.
(From the GUIDE) Step 5. Put phone in Download mode.
Turn off phone (check)
Press volume UP, keep it pressed, press power button (check)
Phone boots up - no Download mode screen.
Do much searching on web....
GUIDE instructions to get phone into Download mode are probably fine if you already know what to do. I don't, so here's suggestion:
To get into Download mode:
Press and Hold Volume Up.
While keeping Volume Up pressed, Press and Hold the Power button. Keep both buttons pressed until the Download option screen appears. This may take up to a minute.
Release Volume Up and Power buttons.
If you want to download, press the Volume Up to Continue.
I could have used some hints about when to connect the phone via USB or more importantly, when the phone should NOT be connected. I'm still not sure. Obviously it needs to be connected to download F/W.
It would have been helpful/reassuring for me if the had explicit description of phone status at beginning of procedure (On/Off? Connected/Disconnected via USB? SIM card in/out? memory card in/out? Battery in/out?). I still can't guess.
It took several tries to get Odin3 running, the phone connected, and Odin3 to recognize the phone.
*** GUIDE needs to give me a clue when phone and Odin3 are talking, or tell me where to find that info.
I'm guessing that a yellow "ID:COM" box with "0:[COM4]" means something.
GUIDE step 7-9. In Odin, select the "boot.tar" file in PDA and click Start. Fails almost immediately.
NOTE:
The GUIDE does not explicitly say which TAR file to use - I guessed.
The f/w coder part of my brain really wanted to use BOOTLOADER instead of PDA (I didn't).
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
GUIDE says wait for the phone to reboot. I waited several hours before deciding that nothing was happening.
I turned phone off.
Turning it back on *OR* plugging in the USB, phone says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
Starting the phone in Download mode gives me the ODIN3 Download Mode screen:
----- cut here -----
ODIN3 Download Mode (Protocol v2.1)
Reason: Force Key
Secure Mode: Secure
Check Signature: Check
Custom Binary downloaded: No (0 counts)
Current Binary: Samsung Official
Waiting USB Cable....
==> Connected! Press the [Start] of Odin3
(android graphic)
Downloading...
Do not turn of target!!
* <--- about 3/4s of a blue dot.
----- cut here -----
As per GUIDE step 11:
Download and unzip SGH-I927R_insecure_bootimg.zip. Unzip TAR to Odin3 dir.
Repeat above steps but select the "insecure" TAR. Download fails:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Starting the phone tells me to run Kies in "recovery" mode.
Kies cannot connect to the phone and Kies "Firmware emergency recovery" mode does not see a device.
Kies "Troubleshoot connection error" has me disconnect the phone then it reinstalls device driver.
Connecting the phone causes Windows to install it's own device drivers.
Starting the phone in Download mode gives me the ODIN3 Download Mode screen.
I am stuck but not suicidal (yet). Phone seems partially functional. I can't figure out how to get either Odin or Kies to do anything useful.
Please help. I'm hearing a voice that sounds like Steve Jobs ... Paul .... give in to the dark side ...
_____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____
Update:
I can get the phone into "Android system recovery <3e>" mode, but still have no idea what to do next....
reboot
apply update from sdcard
wipe data/factory reset
wipe cache partition
-- Copying media files...
Successfully copied meida files.
# MANUAL MODE #
-- Updating application...
Successfully updated application.
-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ATT/system/'.
Successfully applied multi-CSC.
Thx in advance.
Some help
mnemotronic said:
I am trying to follow the "Very easy steps" on
Re: [GUIDE] Rooting the Samsung Captivate Glide i927/i927r
Steps so far:
Downloaded:
KiesSetup.exe ( 70,227,456 bytes, md5sum=3891cd32e2bc467f77f4d65f0244faf )
Odin3-v1.85.zip ( 203,676 bytes, md5sum=14e3af7c4c01e21527aeaab65e68a75 )
boot2.zip ( 3,944,864 bytes, md5sum=64a78f6f86e13eedba20c2d5243d651 )
i927_factoryfs_rooted_img.tar (432,711,680 bytes, md5sum=2b913a5480008d8ae4c3138411cf099 )
usb_drivers_GalaxyS_x64.zip ( 19,780,425 bytes, md5sum=2378aa7a2f5191eeb832ce5c86b03b1 )
(following file was not initially downloaded)
SGH-I927R_insecure_bootimg.zip ( 3,938,408 bytes, md5sum=09b01d3e49f2a2b7b5817f3fb59c6b9b )
Installed the usb drivers as per the AT&T forums. This is a waste of time. Windows installs it's own USB drivers as soon as I plug in the phone.
I unzipped Odin3-v1.85 to it's own subdir.
Copied i927_factoryfs_rooted_img.tar to Odin dir. Unzipped boot2.zip to get a TAR and copied that to Odin dir.
With phone on and connected via USB, run Odin.
(From the GUIDE) Step 5. Put phone in Download mode.
Turn off phone (check)
Press volume UP, keep it pressed, press power button (check)
Phone boots up - no Download mode screen.
Do much searching on web....
GUIDE instructions to get phone into Download mode are probably fine if you already know what to do. I don't, so here's suggestion:
To get into Download mode:
Press and Hold Volume Up.
While keeping Volume Up pressed, Press and Hold the Power button. Keep both buttons pressed until the Download option screen appears. This may take up to a minute.
Release Volume Up and Power buttons.
If you want to download, press the Volume Up to Continue.
I could have used some hints about when to connect the phone via USB or more importantly, when the phone should NOT be connected. I'm still not sure. Obviously it needs to be connected to download F/W.
It would have been helpful/reassuring for me if the had explicit description of phone status at beginning of procedure (On/Off? Connected/Disconnected via USB? SIM card in/out? memory card in/out? Battery in/out?). I still can't guess.
It took several tries to get Odin3 running, the phone connected, and Odin3 to recognize the phone.
*** GUIDE needs to give me a clue when phone and Odin3 are talking, or tell me where to find that info.
I'm guessing that a yellow "ID:COM" box with "0:[COM4]" means something.
GUIDE step 7-9. In Odin, select the "boot.tar" file in PDA and click Start. Fails almost immediately.
NOTE:
The GUIDE does not explicitly say which TAR file to use - I guessed.
The f/w coder part of my brain really wanted to use BOOTLOADER instead of PDA (I didn't).
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
GUIDE says wait for the phone to reboot. I waited several hours before deciding that nothing was happening.
I turned phone off.
Turning it back on *OR* plugging in the USB, phone says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
Starting the phone in Download mode gives me the ODIN3 Download Mode screen:
----- cut here -----
ODIN3 Download Mode (Protocol v2.1)
Reason: Force Key
Secure Mode: Secure
Check Signature: Check
Custom Binary downloaded: No (0 counts)
Current Binary: Samsung Official
Waiting USB Cable....
==> Connected! Press the [Start] of Odin3
(android graphic)
Downloading...
Do not turn of target!!
* <--- about 3/4s of a blue dot.
----- cut here -----
As per GUIDE step 11:
Download and unzip SGH-I927R_insecure_bootimg.zip. Unzip TAR to Odin3 dir.
Repeat above steps but select the "insecure" TAR. Download fails:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Starting the phone tells me to run Kies in "recovery" mode.
Kies cannot connect to the phone and Kies "Firmware emergency recovery" mode does not see a device.
Kies "Troubleshoot connection error" has me disconnect the phone then it reinstalls device driver.
Connecting the phone causes Windows to install it's own device drivers.
Starting the phone in Download mode gives me the ODIN3 Download Mode screen.
I am stuck but not suicidal (yet). Phone seems partially functional. I can't figure out how to get either Odin or Kies to do anything useful.
Please help. I'm hearing a voice that sounds like Steve Jobs ... Paul .... give in to the dark side ...
_____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____
Update:
I can get the phone into "Android system recovery <3e>" mode, but still have no idea what to do next....
reboot
apply update from sdcard
wipe data/factory reset
wipe cache partition
-- Copying media files...
Successfully copied meida files.
# MANUAL MODE #
-- Updating application...
Successfully updated application.
-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ATT/system/'.
Successfully applied multi-CSC.
Thx in advance.
Click to expand...
Click to collapse
I just bought an unlocked Glide and I struggled with the steps myself, but I went about things differently and I hope this can help you.
FIRST, use the Samsung KiES to update the software from GingerBread 2.3.6 to the ICS 4.0.4 stock
Then, after I did that, I visited this blog where the writer did a FABULOUS job explaining how to install the CWM recovery and flashing the rooted version of the ICS ROM (AT&T version):
http://transce080.blogspot.com/
Let me know if you need further help and I'd be willing to guide you along.
Update as of 03-Nov-2013
_____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____
Update as of 03-Nov-2013
I don't know what I did, but after getting into the "Android system recovery screen the phone came back up. At least phone is working.
seekdatruth101:
Many thanks for the suggestion - I'll try it are report back.
Currently, Kies is running and almost connecting. Kies shows "SGH-I927" in the "Connected devices" but it the "Connecting..." screen just keeps spinning it's wheels. Last night Kies was able to connect and was showing Contacts, Music, etc. Today, zilch. I tried restarting Kies, powering down the phone and removing battery. When I connect phone to computer, Windows 7 installs the device driver s/w. Sometimes this works, sometimes it works and says it's "Samsung xxxd #2", then "... #3". Sometimes the device driver s/w fails to install and returns error. Assuming I can figure out the crappy Samsung USB driver ....
What are phone USB settings for:
Settings / Applications / Development / USB debugging (current not checked) :
Settings / Applications / Development / Allow mock locations (current not checked) :
Settings / Wireless and network / USB utilities / USB mass storage (current not connected) :
Dial / *#7284# / UART (currently MODEM) :
Dial / *#7284# / USB (currently PDA:
has legullia
What was the original OS on the phone, the GB or the ICS?
mnemotronic said:
I am trying to follow the "Very easy steps" on
Re: [GUIDE] Rooting the Samsung Captivate Glide i927/i927r
Steps so far:
Downloaded:
KiesSetup.exe ( 70,227,456 bytes, md5sum=3891cd32e2bc467f77f4d65f0244faf )
Odin3-v1.85.zip ( 203,676 bytes, md5sum=14e3af7c4c01e21527aeaab65e68a75 )
boot2.zip ( 3,944,864 bytes, md5sum=64a78f6f86e13eedba20c2d5243d651 )
i927_factoryfs_rooted_img.tar (432,711,680 bytes, md5sum=2b913a5480008d8ae4c3138411cf099 )
usb_drivers_GalaxyS_x64.zip ( 19,780,425 bytes, md5sum=2378aa7a2f5191eeb832ce5c86b03b1 )
(following file was not initially downloaded)
SGH-I927R_insecure_bootimg.zip ( 3,938,408 bytes, md5sum=09b01d3e49f2a2b7b5817f3fb59c6b9b )
Installed the usb drivers as per the AT&T forums. This is a waste of time. Windows installs it's own USB drivers as soon as I plug in the phone.
I unzipped Odin3-v1.85 to it's own subdir.
Copied i927_factoryfs_rooted_img.tar to Odin dir. Unzipped boot2.zip to get a TAR and copied that to Odin dir.
With phone on and connected via USB, run Odin.
(From the GUIDE) Step 5. Put phone in Download mode.
Turn off phone (check)
Press volume UP, keep it pressed, press power button (check)
Phone boots up - no Download mode screen.
Do much searching on web....
GUIDE instructions to get phone into Download mode are probably fine if you already know what to do. I don't, so here's suggestion:
To get into Download mode:
Press and Hold Volume Up.
While keeping Volume Up pressed, Press and Hold the Power button. Keep both buttons pressed until the Download option screen appears. This may take up to a minute.
Release Volume Up and Power buttons.
If you want to download, press the Volume Up to Continue.
I could have used some hints about when to connect the phone via USB or more importantly, when the phone should NOT be connected. I'm still not sure. Obviously it needs to be connected to download F/W.
It would have been helpful/reassuring for me if the had explicit description of phone status at beginning of procedure (On/Off? Connected/Disconnected via USB? SIM card in/out? memory card in/out? Battery in/out?). I still can't guess.
It took several tries to get Odin3 running, the phone connected, and Odin3 to recognize the phone.
*** GUIDE needs to give me a clue when phone and Odin3 are talking, or tell me where to find that info.
I'm guessing that a yellow "ID:COM" box with "0:[COM4]" means something.
GUIDE step 7-9. In Odin, select the "boot.tar" file in PDA and click Start. Fails almost immediately.
NOTE:
The GUIDE does not explicitly say which TAR file to use - I guessed.
The f/w coder part of my brain really wanted to use BOOTLOADER instead of PDA (I didn't).
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
GUIDE says wait for the phone to reboot. I waited several hours before deciding that nothing was happening.
I turned phone off.
Turning it back on *OR* plugging in the USB, phone says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
Starting the phone in Download mode gives me the ODIN3 Download Mode screen:
----- cut here -----
ODIN3 Download Mode (Protocol v2.1)
Reason: Force Key
Secure Mode: Secure
Check Signature: Check
Custom Binary downloaded: No (0 counts)
Current Binary: Samsung Official
Waiting USB Cable....
==> Connected! Press the [Start] of Odin3
(android graphic)
Downloading...
Do not turn of target!!
* <--- about 3/4s of a blue dot.
----- cut here -----
As per GUIDE step 11:
Download and unzip SGH-I927R_insecure_bootimg.zip. Unzip TAR to Odin3 dir.
Repeat above steps but select the "insecure" TAR. Download fails:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Starting the phone tells me to run Kies in "recovery" mode.
Kies cannot connect to the phone and Kies "Firmware emergency recovery" mode does not see a device.
Kies "Troubleshoot connection error" has me disconnect the phone then it reinstalls device driver.
Connecting the phone causes Windows to install it's own device drivers.
Starting the phone in Download mode gives me the ODIN3 Download Mode screen.
I am stuck but not suicidal (yet). Phone seems partially functional. I can't figure out how to get either Odin or Kies to do anything useful.
Please help. I'm hearing a voice that sounds like Steve Jobs ... Paul .... give in to the dark side ...
_____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____
Update:
I can get the phone into "Android system recovery <3e>" mode, but still have no idea what to do next....
reboot
apply update from sdcard
wipe data/factory reset
wipe cache partition
-- Copying media files...
Successfully copied meida files.
# MANUAL MODE #
-- Updating application...
Successfully updated application.
-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ATT/system/'.
Successfully applied multi-CSC.
Thx in advance.
Click to expand...
Click to collapse
mnemotronic said:
_____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____
Update as of 03-Nov-2013
I don't know what I did, but after getting into the "Android system recovery screen the phone came back up. At least phone is working.
seekdatruth101:
Many thanks for the suggestion - I'll try it are report back.
Currently, Kies is running and almost connecting. Kies shows "SGH-I927" in the "Connected devices" but it the "Connecting..." screen just keeps spinning it's wheels. Last night Kies was able to connect and was showing Contacts, Music, etc. Today, zilch. I tried restarting Kies, powering down the phone and removing battery. When I connect phone to computer, Windows 7 installs the device driver s/w. Sometimes this works, sometimes it works and says it's "Samsung xxxd #2", then "... #3". Sometimes the device driver s/w fails to install and returns error. Assuming I can figure out the crappy Samsung USB driver ....
What are phone USB settings for:
Settings / Applications / Development / USB debugging (current not checked) :
Settings / Applications / Development / Allow mock locations (current not checked) :
Settings / Wireless and network / USB utilities / USB mass storage (current not connected) :
Dial / *#7284# / UART (currently MODEM) :
Dial / *#7284# / USB (currently PDA:
Click to expand...
Click to collapse
Current Phone/OS info
mnemotronic said:
_____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____
{snipsnip}
seekdatruth101 said:
What was the original OS on the phone, the GB or the ICS?
Click to expand...
Click to collapse
Current Phone/OS info:
Samsung-SGH-I927
Android version: 2.3.6
Baseband version: I927UCKL1
Kernel version: 2.6.36.3
Build number: GINGERBREAD.UCKL1
Click to expand...
Click to collapse
You HAVE to update to Ice Cream Sandwich in order to install the correct bootloaders for Odin.
You can do this via kies.
Also, when using Odin, completely close kies, as it can sometimes interfere with the procedure. USB debugging allows many communication features between your phone and computer, mock locations allow certain apps to fake location data, and USB mass storage is used to connect your phone to your PC like a flash drive.
I would suggest installing the USB drivers as instructed, either through kies or by going into control panel - device manager - (whatever you're phone is listed as) choosing update driver and selecting the folder with the drivers in them.
Odin will flash yellow as you said to let you know there is a device attached.
As I said before, all of the guides are for captivate glides with ice cream sandwich, so you MUST update.
Hope that helps a bit.
Sent from my SGHI927 using Tapatalk
I'm running CM 11 latest nightly and I can't get my phone to connect to my laptop (Windows 7).
I am greeted with an error "USB device has malfunctioned" and it won't connnect. I've tried different laptops but with no luck. I do have the SAMSUNG USB Drivers installed. Also, USB ports on both laptops are definitely working.
USB isn't working even on download mode. What can I do?
Plus, I tried flashing a rom and now I am in a bootloop and I can't reflash GB27 because my phone won't connect.
What can I do community?
Have you tried a different USB cable?
You can try installing Kies, which I've heard can help help get USB working. I have two PCs, one has no problem, the other has the USB errors no matter what I try.
unknownsoldierx said:
Have you tried a different USB cable?
You can try installing Kies, which I've heard can help help get USB working. I have two PCs, one has no problem, the other has the USB errors no matter what I try.
Click to expand...
Click to collapse
I've tried three different usb cables. They definitely work.
My device is able to charge with the USB cables but won't be recognized by a computer.
When in download mode, do you see a screen "Downloading...do not turn off target!" or do you see another screen? You may need to hit a button to continue to that screen.
unknownsoldierx said:
When in download mode, do you see a screen "Downloading...do not turn off target!" or do you see another screen? You may need to hit a button to continue to that screen.
Click to expand...
Click to collapse
No, its definitely in download mode. I did press a button to continue.
So I was able to get the phone to be recognized by ODIN after installing kies but I get this when I try to flash my phone. Also, the phone does not stay connected long.
<ID:0/004> Added!!<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
HELP!
IamFlynn said:
No, its definitely in download mode. I did press a button to continue.
So I was able to get the phone to be recognized by ODIN after installing kies but I get this when I try to flash my phone. Also, the phone does not stay connected long.
<ID:0/004> Added!!<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
HELP!
Click to expand...
Click to collapse
Now that you can connect to Odin (if only for a bit), have you tried flashing just a kernel by itself (not a whole ROM)? Specifically the EL26CWM tar. If you can get that to flash, you'd at least have a working recovery with which to flash another ROM.
Good luck
Sent from my SPH-D710 using Tapatalk
Surj138 said:
Now that you can connect to Odin (if only for a bit), have you tried flashing just a kernel by itself (not a whole ROM)? Specifically the EL26CWM tar. If you can get that to flash, you'd at least have a working recovery with which to flash another ROM.
Good luck
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I have a working recovery, CWM6 but everytime I try to access it, I am able to reboot into recovery but it reboots my phone after a few seconds and I see no options I can select from.
IamFlynn said:
I have a working recovery, CWM6 but everytime I try to access it, I am able to reboot into recovery but it reboots my phone after a few seconds and I see no options I can select from.
Click to expand...
Click to collapse
OK, well now it sounds like your power button is on its way out. Mine was doing that (my phone's had all kinds of issues, but it's good now... minus a working USB port lol) maybe 8 months back, with symptoms just like yours.
Question: Do you ever see the Power Menu screen randomly pop up?
I would see that (sometimes) then it would reboot by itself. It would also reboot by itself while in recovery, and would not stay OFF if I had a battery reinserted.
I looked online for a solution, which led to dismantling the phone and cleaning inside the power button as well as i could, with alcohol. No dice [emoji20]
This went on for a few days and i was already looking for another phone. I was on JB Touchwiz with Agat's kernel at the time, so I rebooted into recovery and flashed OldMan CM9, hoping it wouldn't reboot mid-flash... Flashed fine without rebooting.
But when I booted into CM9, the issue had completely disappeared, no BS!! I have no explanation for this, as I was positive it was a hardware issue, but it worked. I have never had a Power Button issue since, regardless of ROM (I'm a registered flashaholic). Hope this helps.
Sent from my SPH-D710 using Tapatalk
Surj138 said:
OK, well now it sounds like your power button is on its way out. Mine was doing that (my phone's had all kinds of issues, but it's good now... minus a working USB port lol) maybe 8 months back, with symptoms just like yours.
Question: Do you ever see the Power Menu screen randomly pop up?
I would see that (sometimes) then it would reboot by itself. It would also reboot by itself while in recovery, and would not stay OFF if I had a battery reinserted.
I looked online for a solution, which led to dismantling the phone and cleaning inside the power button as well as i could, with alcohol. No dice [emoji20]
This went on for a few days and i was already looking for another phone. I was on JB Touchwiz with Agat's kernel at the time, so I rebooted into recovery and flashed OldMan CM9, hoping it wouldn't reboot mid-flash... Flashed fine without rebooting.
But when I booted into CM9, the issue had completely disappeared, no BS!! I have no explanation for this, as I was positive it was a hardware issue, but it worked. I have never had a Power Button issue since, regardless of ROM (I'm a registered flashaholic). Hope this helps.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I don't think its the power button, because the phone does not reboot automatically if i'm in download mode. I'll check it out tho. Thanks bud!
Hi
I have a Note 2 that only shows the "Firmware upgrade encountered an error screen" (attached)
I cannot enter recovery or download mode. When i hold the button combination for either mode, the phone blinks and then returns to the "Firmware upgrade encountered an error screen".
Any ideas or comments greatly appreciated.
Thanks in advance
This is download mod, connect at pc open odin, prefer odin 3 1.87 version mount stock firmware same you had or newer and flash. If it fails disconnect phone from pc put battery out push power button with battery out for 15 sec put battery back push power button again and you'll go to same screen, flash firmware with odin. If again fail post for further instructions.
Sent from my GT-N7100 using Tapatalk 2
Vagsvag
Followed your instructions. Using Odin 1.87 the flashing stops
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNE1_N7100BTUFNE1_N7100XXUFND3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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..
Thanks
try kies 3
Kies 3 does not connect to the phone. It shows as unrecognized device
grwalker said:
Kies 3 does not connect to the phone. It shows as unrecognized device
Click to expand...
Click to collapse
try different Odin, for me 3.09 was the best
Already tried all versions of Odin. None work
grwalker said:
Already tried all versions of Odin. None work
Click to expand...
Click to collapse
try different ROMs, even custom and don't go into download mode, but just stay on the screen, where error appears - odin should recognize the device and finally flash rom
Tried different ROMS, etc. No luck
grwalker said:
Tried different ROMS, etc. No luck
Click to expand...
Click to collapse
try different USB cable and PC.
I have tried, different PC's (running XP, W7, W8.1 and W10). Also tried different cables and different ports. No luck
Thanks for your comments
I think there is nothing else you can do on your own. Probably Samsung support will inform you what to do and there is a great chance that they will do it for free.
Unfortunately i have asked Samsung. Since the phone was purchased outside the EU they cant (or wont) do anything. So much for an international organisation!!
Thanks
you can try in local phone service, cuz probably a special flasher is needed
'SHAME'sung?
Only God Can Forgive
I have a Sprint gs6 that like many others is stuck on the initial boot screen. I have scoured the internet for ideas and tricks, but nothing I'm doing works. This is my last ditch effort since the phone is out of warranty and I have to either pay Samsung to fix it if I can figure this out. I've installed firmware on phones before and such so I'm familiar but not 100% pro at this.
Here are the details: Phone was in use running an app and then randomly it rebooted but it got stuck on the Samsung logo. Its my son's phone so I don't think he tried anything else but I can't be 100% sure.
This is the phone info in download mode
ODIN MODE
PRODUCT NAME: SM-G920P
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download : Enabled
KNOW WARRANTY VOID: 0 (0x0000)
AP SWREV: B:4 K:2 S:3
I've downloaded Odin 3.10.6 and have installed this file (G920PVPS4CQB1_G920PSPT4CQB1_G920PVPS4CQB1_HOME.tar.md5)
onto this phone.
BTW: THE ONLY thing I can do is get it into download mode.
For some reason even after installing this rom which says successful it still won't let me boot into recovery mode.
which works here is the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPS4CQB1_G920PSPT4CQB1_G920PVPS4CQB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I've tried to install twrp and cw but odin fails and the phone is basically preventing anything non standard. I can't do a fastboot because the phone is not operable .
I don't get it!?!?!?! the stock firmware loads with no problem but it still gets stuck on that boot screen.
ANY ideas????
strike1nc said:
I have a Sprint gs6 that like many others is stuck on the initial boot screen. I have scoured the internet for ideas and tricks, but nothing I'm doing works. This is my last ditch effort since the phone is out of warranty and I have to either pay Samsung to fix it if I can figure this out. I've installed firmware on phones before and such so I'm familiar but not 100% pro at this.
Here are the details: Phone was in use running an app and then randomly it rebooted but it got stuck on the Samsung logo. Its my son's phone so I don't think he tried anything else but I can't be 100% sure.
This is the phone info in download mode
ODIN MODE
PRODUCT NAME: SM-G920P
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download : Enabled
KNOW WARRANTY VOID: 0 (0x0000)
AP SWREV: B:4 K:2 S:3
I've downloaded Odin 3.10.6 and have installed this file (G920PVPS4CQB1_G920PSPT4CQB1_G920PVPS4CQB1_HOME.tar.md5)
onto this phone.
BTW: THE ONLY thing I can do is get it into download mode.
For some reason even after installing this rom which says successful it still won't let me boot into recovery mode.
which works here is the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPS4CQB1_G920PSPT4CQB1_G920PVPS4CQB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I've tried to install twrp and cw but odin fails and the phone is basically preventing anything non standard. I can't do a fastboot because the phone is not operable .
I don't get it!?!?!?! the stock firmware loads with no problem but it still gets stuck on that boot screen.
ANY ideas????
Click to expand...
Click to collapse
Leave the phone while its boot looping until the battery runs out and it shuts off. Then charge to around 10 or 20 percent without turning the phone off. Then unplug and hold power home and volume UP. Keep holding until a recovery shows and then factory reset. Then reboot and if its still boot looping try going back into download mode and re flashing the firmware.
Thanks, but no luck
g4_e said:
Leave the phone while its boot looping until the battery runs out and it shuts off. Then charge to around 10 or 20 percent without turning the phone off. Then unplug and hold power home and volume UP. Keep holding until a recovery shows and then factory reset. Then reboot and if its still boot looping try going back into download mode and re flashing the firmware.
Click to expand...
Click to collapse
I left it charging for 50 mins not sure how long it would take to get to 10/20%, but figured that was long enough. The problem is that its not really rebooting.
even after I hold down Vol Down and power to shut it of within 2 sec. it turns itself back on. The phone just hangs on the Samsung Galaxy S6 Logo and sticks there I tried tricking it to power off and on download mode cancel right away going to vol up but it won't go into recovery no matter what I've tried. I've tested the download of the Fireware with 3.10.6, 3.10.7, 3.11.1 and 3.12.5 of odin and nothing is working. I think this phone is done ughhh
I've even tried to kill the battery then while holding down VOL UP, Home, PWR I have someone else plug the phone in and still won't go into recovery. I don't get how it is preventing to go into Recovery mode. I know that if I could get into that I would be fine. WHY did the this lame s6 have to come with no SD Card.....
The reason why you can install a custom recovery is because the FRP lock is on.
But no Recovery also?
Poebat said:
The reason why you can install a custom recovery is because the FRP lock is on.
Click to expand...
Click to collapse
but why is it not letting me into recovery mode. The stock firmware works, but it just hangs on this logo? Does that feature also block that. When I look over the FRP Lock everyone in videos can get into recovery option no problem!
strike1nc said:
but why is it not letting me into recovery mode. The stock firmware works, but it just hangs on this logo? Does that feature also block that. When I look over the FRP Lock everyone in videos can get into recovery option no problem!
Click to expand...
Click to collapse
Power + Vol up and down. The second the screen turns off let go of the Vol Down and power button and press the home button. That should put you in recovery mode.
Bummer
Poebat said:
Power + Vol up and down. The second the screen turns off let go of the Vol Down and power button and press the home button. That should put you in recovery mode.
Click to expand...
Click to collapse
man something I hadn't tried in this sequence, but after trying still powers up to logo and no change. I tried holding down for a solid minute just now.
I wish I could post video of link me doing this to confirm I'm doing it right, but I'm pretty sure I was doing it right....
Bummer I was excited to try something new....
Thanks for reply this is so odd never seen a phone do this.
strike1nc said:
man something I hadn't tried in this sequence, but after trying still powers up to logo and no change. I tried holding down for a solid minute just now.
I wish I could post video of link me doing this to confirm I'm doing it right, but I'm pretty sure I was doing it right....
Bummer I was excited to try something new....
Thanks for reply this is so odd never seen a phone do this.
Click to expand...
Click to collapse
When the screen turns off try Home + Vol Down. Tell me what happens.
self turn on
Poebat said:
When the screen turns off try Home + Vol Down. Tell me what happens.
Click to expand...
Click to collapse
When I do the VOL Down and PWR it shuts off I let go and within 1-2 sec. MAX it turns itself on and get stuck on the logo screen.
https://www.dropbox.com/s/nh2nqso7k189evg/20170414_150830.mp4?dl=0
after I turn it off I know it looks like I'm trying to hold down keys, but I didn't actually press any of them it turned itself on before.
strike1nc said:
When I do the VOL Down and PWR it shuts off I let go and within 1-2 sec. MAX it turns itself on and get stuck on the logo screen.
https://www.dropbox.com/s/nh2nqso7k189evg/20170414_150830.mp4?dl=0
after I turn it off I know it looks like I'm trying to hold down keys, but I didn't actually press any of them it turned itself on before.
Click to expand...
Click to collapse
Yeah, in not sure about turning it off completely. Vol Down and up + power is supposed to force restart the phone. Try Vol Down + Vol up.
Edit: ignore all that ^. I tried it myself and I see your issue. Try power + vol up and down + home. Then when the screen turns off Press Vol up + home button. That worked for me
any new ideas ? i have the exact same problem
have been trying all the above
nothing works
Need to let phone die completely! All. The. Way.
Then reboot to recovery and factory reset.
sorry had to send back to samsung for repair.
it was defective i tried everything and i mean everything.
strike1nc said:
sorry had to send back to samsung for repair.
it was defective i tried everything and i mean everything.
Click to expand...
Click to collapse
what was the problem? according to samsung....
---------- Post added at 07:24 PM ---------- Previous post was at 07:20 PM ----------
crazynapkinman said:
Need to let phone die completely! All. The. Way.
Then reboot to recovery and factory reset.
Click to expand...
Click to collapse
I cannot get into recovery now
do u think i will after draining the battery?
eligoren said:
what was the problem? according to samsung....
---------- Post added at 07:24 PM ---------- Previous post was at 07:20 PM ----------
I cannot get into recovery now
do u think i will after draining the battery?
Click to expand...
Click to collapse
Yes. It should reboot like normal after full drain and charging up to 10 percent. Initial start will take a bit. Watch the LED. Is it pulsing? Will be easier to tell in a darker room.
If it's pulsing, let it go for a while. Will eventually boot. Wait up to 20 minutes.
crazynapkinman said:
Yes. It should reboot like normal after full drain and charging up to 10 percent. Initial start will take a bit. Watch the LED. Is it pulsing? Will be easier to tell in a darker room.
If it's pulsing, let it go for a while. Will eventually boot. Wait up to 20 minutes.
Click to expand...
Click to collapse
i have done what you have suggested.
the thing is... as soon as i plug the phone back to the charger it powers up
i cannot control it and let it charge for 10 min. before power on.
eligoren said:
i have done what you have suggested.
the thing is... as soon as i plug the phone back to the charger it powers up
i cannot control it and let it charge for 10 min. before power on.
Click to expand...
Click to collapse
Does it do a full boot? Or does it go to the battery charging screen?
crazynapkinman said:
Does it do a full boot? Or does it go to the battery charging screen?
Click to expand...
Click to collapse
NO
as soon as i force a reset (power+vol dwn) or drain battery and connect power, it goes to boot screen and stay there.
no charging screen (since you need to stay in power-down state to get this...)
If you can get to Download mode, reflash the stock firmware depending which version of Android you were on.
To get to recovery, I have always had to press Down + Home + Power. When it asks to either continue or reboot, reboot then hold Up + Home + Power then let go of power as soon as it starts up
eligoren said:
NO
as soon as i force a reset (power+vol dwn) or drain battery and connect power, it goes to boot screen and stay there.
no charging screen (since you need to stay in power-down state to get this...)
Click to expand...
Click to collapse
Te post below is correct. Put your device in download mode and let go of ALL the buttons. Place your fingers over the Home, Vol Up, & Power buttons. Tap Power down to exit download mode and SOON as the screen starts to turn off, press & hold those 3 buttons until it goes into recovery. You'll have the factory recovery installed but I believe you might still be able to do a wipe. So if you get it into recovery just go ahead and wipe it or a factory reset. Whatever you can wipe just do it. You have nothing to lose but if you ticked the wrong buttons in Odin that's your issue. Sounds like you probably checked the repartition button? Maybe not but if you do or did then the device will NOT boot unless you wipe it in recovery. If you get that far then reboot your phone. The operating system is already installed.
nhail47 said:
If you can get to Download mode, reflash the stock firmware depending which version of Android you were on.
To get to recovery, I have always had to press Down + Home + Power. When it asks to either continue or reboot, reboot then hold Up + Home + Power then let go of power as soon as it starts up
Click to expand...
Click to collapse