[Q] Galaxy S2 SGH-I727 stuck on Odin Mode, Bricked ? Help Please

Search This thread

Cindor

Member
Dec 1, 2012
5
1
Finally I found the correct forum...

Hello, I need help with my Samsung Galaxy SGH-727 skyrocket..Got stuck on the Odin mode...
That happen when i try to root my phone

I got this message:
Firmware upgrade encountered an issue.Please select recovery mode in Kies & try again.
Nothing is working, Vol -, Vol + usb, getting Download Mode, Vol + and I stuck in Odin Mode again...... Very frustrated
How can i get out of the Odin Mode? This is a Hard Brick.?

Kies failed to connect and Odin Failed to flash....

<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<ID:0/008> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

Please help ..Thanks in advance....
 

Attachments

  • photo.JPG
    photo.JPG
    96.5 KB · Views: 277

stoopendis

Senior Member
May 10, 2012
1,132
271
Burnaby B.C
Are you sure you have the right Version of Odin and are using it correctly. Are you sure you have the correct tar file for your phone? Have you read Vincoms sticky on the whole odin/flash/recovery process?
 

RK

Senior Member
Feb 8, 2012
867
443
Not bricked. Use different USB port and try flashing the firmware again. Preferably use one of the back usb ports that are on the PC main board.

Sent from my SAMSUNG-SGH-I727 using xda app-developers app
 

Cindor

Member
Dec 1, 2012
5
1
Galaxy S2 SGH-I727 stuck on Odin Mode, Bricked ? Help Please

read the odin troubleshooting section in the "restoring to stock" link in my sig

Thank You Vincom, Yes I did, I read all the post, but the problem is I can´t enter in Dowloading Mode....
Nothing is working, Up and Volume Down keys simultaneously + usb, getting Warning, Volume up Continue, Volume down Cancel, Restart phone, and then I press Vol + and I stuck in Odin Mode again.....
Check the picture.
Kies failed to connect and Odin Failed to flash...
 

Attachments

  • photo.JPG
    photo.JPG
    96.5 KB · Views: 180

xcrazydx

Senior Member
Feb 3, 2012
6,319
2,123
Thank You Vincom, Yes I did, I read all the post, but the problem is I can´t enter in Dowloading Mode....
Nothing is working, Up and Volume Down keys simultaneously + usb, getting Warning, Volume up Continue, Volume down Cancel, Restart phone, and then I press Vol + and I stuck in Odin Mode again.....
Check the picture.
Kies failed to connect and Odin Failed to flash...

It's already in download mode bro. Get Odin fired up and flash it

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
 
  • Like
Reactions: Cindor

Cindor

Member
Dec 1, 2012
5
1
Galaxy S2 SGH-I727 stuck on Odin Mode, Bricked ? Help Please

Yeah, that image is download mode.

Sent via the Skyrocket

Quando Omni Flunkus Moritati

Thanks, liquidzoo and xcrazydx, so if this is a Download mode, I flashing a wrong file probably... :(
I´m using Odin3 V3.04, and trying Flashing: I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5, and recovery.tar.md5 but they are not working....
I used 3 different USB cable already with out luck.
Can some one address me to the correct procedure please, Thank You...
 

jd1639

Inactive Recognized Contributor
Sep 21, 2012
16,833
5,404
Minnesota
Try Odin v1.85 I never liked the one you're using.

Sent from my SGH-I727 using xda app-developers app
 

liquidzoo

Senior Member
Mar 17, 2010
1,025
209
Florence, AZ
Try Odin v1.85 I never liked the one you're using.

Sent from my SGH-I727 using xda app-developers app

That seems like the right file, but yes 1.85 is the recommended version (download in vincom's thread).

Also, make sure that you're using the cable that came with the phone. I had issues on other ones, but that one worked perfectly.
 

dLuck

Member
Sep 24, 2012
20
1
Stuck on "Complete(Write) operation failed."

Hi guys. This is my story. Few days ago i wanted to view fotos. Suddenly phone switched off. Phone couldn't switch on again. Samsung logo appeared than disappeared and nothing happend. I decided to clean cache. Rebooted to CWMR, selected clean cache and system showed me message "/cache cannot be mounted". I've decided to reinstall my ROM. Reinstallation failed. On next reboot I couldn't enter CWMR. Holding Up and Down buttons hanged phone on Samsung logo. On normal reboot again Samsung logo appeared than disappeared and nothing happend.

Used Odin 1.85 to factory reset my SGS II i727. Got this picture on the screen https://dl.dropboxusercontent.com/u/84573385/preodinmode.jpg and than this one https://dl.dropboxusercontent.com/u/84573385/odinmode.jpg.
First got "Getting PIT for mapping" error. Used solution from vincom's thread from section 3.
Now it stucks on write operation (screenshot attached):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_low_ship.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..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tried two different cables on all USB ports of my two laptops on Windows 7 and XP. Rebooted PCs few times after driver installation.

ROM installed before crash: Avatar ROM 4.2.2
Version of CWMRTouch installed before crash: 6.0.4.3
Samsung drivers installed on PC: SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail (w/ version v1_3_2200_0 Odin stucked on Initialisation or SetupConnection stage)

Please, help. What else can I do with my problem?
 

Attachments

  • odin_err.png
    odin_err.png
    62.3 KB · Views: 69
Last edited:

vincom

Inactive Recognized Contributor
May 5, 2011
3,877
4,152
GB
meettomy.site
Hi guys. This is my story. Few days ago i wanted to view fotos. Suddenly phone switched off. Phone couldn't switch on again. Samsung logo appeared than disappeared and nothing happend. I decided to clean cache. Rebooted to CWMR, selected clean cache and system showed me message "/cache cannot be mounted". I've decided to reinstall my ROM. Reinstallation failed. On next reboot I couldn't enter CWMR. Holding Up and Down buttons hanged phone on Samsung logo. On normal reboot again Samsung logo appeared than disappeared and nothing happend.

Used Odin 1.85 to factory reset my SGS II i727. Got this picture on the screen https://dl.dropboxusercontent.com/u/84573385/preodinmode.jpg and than this one https://dl.dropboxusercontent.com/u/84573385/odinmode.jpg.
First got "Getting PIT for mapping" error. Used solution from vincom's thread from section 3.
Now it stucks on write operation (screenshot attached):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_low_ship.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..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tried two different cables on all USB ports of my two laptops on Windows 7 and XP. Rebooted PCs few times after driver installation.

ROM installed before crash: Avatar ROM 4.2.2
Version of CWMRTouch installed before crash: 6.0.4.3
Samsung drivers installed on PC: SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail (w/ version v1_3_2200_0 Odin stucked on Initialisation or SetupConnection stage)

Please, help. What else can I do with my problem?
try the celox pit file again, but remember to use the "pit" option in odin and not pda, idk if it will work but u got nothing to loose, the emmc(memory) could be screwed up or dead, unbricking it might also help
 

dLuck

Member
Sep 24, 2012
20
1
try the celox pit file again, but remember to use the "pit" option in odin and not pda, idk if it will work but u got nothing to loose, the emmc(memory) could be screwed up or dead, unbricking it might also help

tried celox.pit again and now it is write error (screenshot attached). I did it by default w/o unchecking Re-partition option.
Sorry for asking but what do you mean "unbricking it" ? How can I repair internal memory if it is dead?
 

Attachments

  • odin_err1.png
    odin_err1.png
    65.7 KB · Views: 54
Last edited:

vincom

Inactive Recognized Contributor
May 5, 2011
3,877
4,152
GB
meettomy.site
tried celox.pit again and now it is write error (screenshot attached). I did it by default w/o unchecking Re-partition option.
Sorry for asking but what do you mean "unbricking it" ? How can I repair internal memory if it is dead?
i said might if its corrupted, jtag(unbrick) might fix it but unless tried who knows for sure
 

dLuck

Member
Sep 24, 2012
20
1
i said might if its corrupted, jtag(unbrick) might fix it but unless tried who knows for sure

So for this moment w/o JTAG option you can say that my phone is dead? Like you said I have nothing to loose. What else can I do maybe to fix my problem? If nothing :crying: - is there any way to get data (fotos) from internal SDcard?
 

dLuck

Member
Sep 24, 2012
20
1
I tried Heimdall on Linux machine.
Executed two commands:
1. sudo heimdall detect --verbose --stdout-errors --usb-log-level debug (Description: Indicates whether or not a download mode device can be detected.)
Result:
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.003046] [00000c57] libusbx: debug [libusb_get_device_list]
[ 0.003115] [00000c57] libusbx: debug [discovered_devs_append] need to increase capacity
[ 0.003143] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003156] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003171] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003186] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003200] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003212] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003226] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003240] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003253] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003266] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003280] [00000c57] libusbx: debug [libusb_get_device_descriptor]
Device detected
[ 0.003320] [00000c57] libusbx: debug [libusb_exit]
[ 0.003335] [00000c57] libusbx: debug [libusb_exit] destroying default context​

2. sudo heimdall print-pit --verbose --stdout-errors --usb-log-level debug (Description: Prints the contents of a PIT file in a human readable format. If a filename is not provided then Heimdall retrieves the PIT file from the connected device.)
Result:
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.005876] [00000c5b] libusbx: debug [libusb_get_device_list]
[ 0.005970] [00000c5b] libusbx: debug [discovered_devs_append] need to increase capacity
[ 0.006011] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006038] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006066] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006096] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006123] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006149] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006176] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006202] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006232] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006260] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006287] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006317] [00000c5b] libusbx: debug [libusb_open] open 5.2
[ 0.006380] [00000c5b] libusbx: debug [usbi_add_pollfd] add fd 11 events 4
[ 0.006444] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006481] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.006532] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.006561] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.007328] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.007377] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=0 transferred=4
[ 0.007388] [00000c5b] libusbx: debug [handle_control_completion] handling completion status 0
[ 0.007399] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.007412] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x16681f8 has callback 0x7fbb5a5c97f0
[ 0.007422] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=4
[ 0.007451] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.007480] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.007491] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.008323] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.008371] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=0 transferred=18
[ 0.008383] [00000c5b] libusbx: debug [handle_control_completion] handling completion status 0
[ 0.008395] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.008407] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x16681f8 has callback 0x7fbb5a5c97f0
[ 0.008418] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=18
Manufacturer: "Sasmsung"
[ 0.008446] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.008473] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.008484] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.009174] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.009197] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=0 transferred=4
[ 0.009207] [00000c5b] libusbx: debug [handle_control_completion] handling completion status 0
[ 0.009216] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.009226] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x16681f8 has callback 0x7fbb5a5c97f0
[ 0.009236] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=4
[ 0.009249] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.009268] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.009278] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.010077] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.010126] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=0 transferred=16
[ 0.010138] [00000c5b] libusbx: debug [handle_control_completion] handling completion status 0
[ 0.010149] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.010162] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x16681f8 has callback 0x7fbb5a5c97f0
[ 0.010172] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=16
Product: "MSM8x60"

length: 18
device class: 2
S/N: 0
VID:pID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
[ 0.010239] [00000c5b] libusbx: debug [libusb_get_config_descriptor] index 0

interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
[ 0.010341] [00000c5b] libusbx: debug [libusb_claim_interface] interface 1
Setting up interface...
[ 0.010389] [00000c5b] libusbx: debug [libusb_set_interface_alt_setting] interface 1 altsetting 0

Initialising protocol...
[ 0.013097] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.013156] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.013185] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.013858] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.013932] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.013962] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.013990] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.014019] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.014048] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.014077] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #1 failed. Result: 0
[ 0.014209] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.014253] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.014282] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.014857] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.014933] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.014962] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.014990] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.015019] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.015049] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.015077] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #2 failed. Result: 0
[ 0.015185] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.015229] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.015258] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.015785] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.015860] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.015889] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.015918] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.015946] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.015976] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.016014] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #3 failed. Result: 0
[ 0.016134] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.016178] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.016207] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.016765] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.016858] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.016887] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.016916] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.016944] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.016974] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.017001] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #4 failed. Result: 0
[ 0.017105] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.017150] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.017179] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.017769] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.017846] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.017874] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.017903] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.017931] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.017961] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.017988] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #5 failed. Result: 0
[ 0.018092] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.018137] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.018165] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.018648] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.018731] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.018766] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.018801] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.018836] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.018872] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.018901] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #6 failed. Result: -9
WARNING: Control transfer #6 failed. Result: 0
[ 0.019008] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.019037] [00000c5b] libusbx: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 4
[ 0.019084] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.019112] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 1.019126] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 1.019166] [00000c5b] libusbx: debug [handle_events] timerfd triggered
[ 1.019177] [00000c5b] libusbx: debug [libusb_cancel_transfer]
[ 1.019365] [00000c5b] libusbx: debug [disarm_timerfd]
[ 1.019411] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 1.019425] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 1.019445] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 1.019464] [00000c5b] libusbx: debug [reap_for_handle] urb type=3 status=-2 transferred=0
[ 1.019477] [00000c5b] libusbx: debug [handle_bulk_completion] handling completion status -2 of bulk urb 1/1
[ 1.019490] [00000c5b] libusbx: debug [handle_bulk_completion] abnormal reap: urb status -2
[ 1.019501] [00000c5b] libusbx: debug [handle_bulk_completion] abnormal reap: last URB handled, reporting
[ 1.019511] [00000c5b] libusbx: debug [usbi_handle_transfer_cancellation] detected timeout cancellation
[ 1.019520] [00000c5b] libusbx: debug [disarm_timerfd]
[ 1.019531] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 1.019540] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
ERROR: Failed to send data: "ODIN"
ERROR: Failed to send data: "(null)"
Releasing device interface...
[ 1.019581] [00000c5b] libusbx: debug [libusb_release_interface] interface 1

[ 1.019618] [00000c5b] libusbx: debug [libusb_close]
[ 1.019640] [00000c5b] libusbx: debug [usbi_remove_pollfd] remove fd 11
[ 1.019679] [00000c5b] libusbx: debug [libusb_exit]
[ 1.019689] [00000c5b] libusbx: debug [libusb_exit] destroying default context​

Will this help to find out whether emmc memory is dead?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Not bricked. Use different USB port and try flashing the firmware again. Preferably use one of the back usb ports that are on the PC main board.

    Sent from my SAMSUNG-SGH-I727 using xda app-developers app
    read the odin troubleshooting section in the "restoring to stock" link in my sig
    1
    Thank You Vincom, Yes I did, I read all the post, but the problem is I can´t enter in Dowloading Mode....
    Nothing is working, Up and Volume Down keys simultaneously + usb, getting Warning, Volume up Continue, Volume down Cancel, Restart phone, and then I press Vol + and I stuck in Odin Mode again.....
    Check the picture.
    Kies failed to connect and Odin Failed to flash...

    It's already in download mode bro. Get Odin fired up and flash it

    Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
    1
    Yeah, that image is download mode.

    Sent via the Skyrocket

    Quando Omni Flunkus Moritati