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....
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?
Are you using the stock USB cable?
It made a difference for me.
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
rushi.1986 said:
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
Click to expand...
Click to collapse
read the odin troubleshooting section in the "restoring to stock" link in my sig
Galaxy S2 SGH-I727 stuck on Odin Mode, Bricked ? Help Please
vincom said:
read the odin troubleshooting section in the "restoring to stock" link in my sig
Click to expand...
Click to collapse
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...
Cindor said:
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...
Click to expand...
Click to collapse
It's already in download mode bro. Get Odin fired up and flash it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yeah, that image is download mode.
Sent via the Skyrocket
Quando Omni Flunkus Moritati
Galaxy S2 SGH-I727 stuck on Odin Mode, Bricked ? Help Please
liquidzoo said:
Yeah, that image is download mode.
Sent via the Skyrocket
Quando Omni Flunkus Moritati
Click to expand...
Click to collapse
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...
Try Odin v1.85 I never liked the one you're using.
Sent from my SGH-I727 using xda app-developers app
jd1639 said:
Try Odin v1.85 I never liked the one you're using.
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
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.
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?
dLuck said:
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?
Click to expand...
Click to collapse
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
vincom said:
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
Click to expand...
Click to collapse
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?
dLuck said:
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?
Click to expand...
Click to collapse
i said might if its corrupted, jtag(unbrick) might fix it but unless tried who knows for sure
vincom said:
i said might if its corrupted, jtag(unbrick) might fix it but unless tried who knows for sure
Click to expand...
Click to collapse
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?
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
VIDID: 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?
Ok, I refuse to give up
a K900 phone has nothing on it. No system recovery, no backups, no real file system. I refuse to give up on this phone, there must be a way to push the k900 operating system to it. I have tried to create a sdfuse directory by adp push, but so far, fails saying something about permissions after taking forever to transfer the .inb file.
Suggestions? (Newb to android, not terminal scared)
viper359 said:
Ok, I refuse to give up
a K900 phone has nothing on it. No system recovery, no backups, no real file system. I refuse to give up on this phone, there must be a way to push the k900 operating system to it. I have tried to create a sdfuse directory by adp push, but so far, fails saying something about permissions after taking forever to transfer the .inb file.
Suggestions? (Newb to android, not terminal scared)
Click to expand...
Click to collapse
Did you try the intel flashing tool?
Sent from my Lenovo K900_ROW using xda app-developers app
mikey199 said:
Did you try the intel flashing tool?
Sent from my Lenovo K900_ROW using xda app-developers app
Click to expand...
Click to collapse
If you mean the manufacturing flash tool, I tried that method, installed all the drivers etc, but, it always fails the flash at the part that deals with the tlv file extention. If I remove that from the xml, it flashes properly, but, the device doesn't get past the final splash screen before loading into the phone.
09/02/13 00:16:52.281 INFO : Port 0/0/1 #0: XFSTK-PROGRESS SN: 35F4362CB55D4CD2 100
09/02/13 00:16:52.281 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 OS: Bytes left to send: 0
09/02/13 00:16:52.281 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 sending data to USB...
09/02/13 00:16:52.281 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::WriteOutPipe __BINARY__
09/02/13 00:16:52.281 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::WriteOutPipe 1
09/02/13 00:16:52.283 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::Write --->__BINARY__
09/02/13 00:16:52.884 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusOS::ReleaseOsImageDataChunk
09/02/13 00:16:52.885 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 End of RIMG
09/02/13 00:16:52.885 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::GetOpCode
09/02/13 00:16:52.885 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::ReadInAck
09/02/13 00:16:52.887 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::GetAck
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::GetAck - EOIU(0x4)
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 EOIU Received...
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 sending DFN...
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::WriteOutPipe DFN
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::WriteOutPipe 1
09/02/13 00:16:53.422 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::Write --->DFN
09/02/13 00:16:53.423 INFO : Port 0/0/1 #0: XFSTK-PROGRESS SN: 35F4362CB55D4CD2 100
09/02/13 00:16:53.423 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 OS: Operating system download completed.
09/02/13 00:16:55.424 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::LogError
09/02/13 00:16:55.424 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: 35F4362CB55D4CD2 Error Code: 0 - Success
09/02/13 00:16:55.424 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusDownloader::do_abort
09/02/13 00:16:55.424 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::Abort
09/02/13 00:16:55.424 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 L:/K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0426_LE_DVT3_PVT_2G_B1_SOS_ARB11.bin size:2031420 bytes
09/02/13 00:16:55.424 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: 35F4362CB55D4CD2 PASS
09/02/13 00:16:55.424 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: 35F4362CB55D4CD2 Firmware and OS download completed.
09/02/13 00:16:56.526 DEBUG : XFSTK SN: 35F4362CB55D4CD 2 -- Success: Transfer Completed Successfully
09/02/13 00:16:56.526 INFO : Port 0/0/1 #0: IFW flash success - SN : 35F4362CB55D4CD2
09/02/13 00:16:56.526 DEBUG : Port 0/0/1 #0: IFW flash success on device 35F4362CB55D4CD2 with state IFWI successfully flashed... REBOOT
09/02/13 00:17:04.657 DEBUG : Port 0/0/1 #0: SOC Device is disconnected - state:2 - status - IFWI successfully flashed... REBOOT
09/02/13 00:17:04.657 DEBUG : SOC device lost on port 1
09/02/13 00:17:26.042 DEBUG : Port 0/0/1 #0: Start Runnable : Medfield632B7AFE
09/02/13 00:17:26.042 INFO : Port 0/0/1 #0: Flashing OS
09/02/13 00:17:26.042 DEBUG : New Android device -> serial: Medfield632B7AFE status: 0 port: 1
09/02/13 00:17:26.042 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase factory
09/02/13 00:17:26.836 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:26.836 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:26.836 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase factory" returns:
erasing 'factory'...
OKAY [ 0.228s]
finished. total time: 0.228s
09/02/13 00:17:28.837 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase cache
09/02/13 00:17:29.579 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:29.579 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:29.579 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase cache" returns:
erasing 'cache'...
OKAY [ 0.721s]
finished. total time: 0.721s
09/02/13 00:17:31.579 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase config
09/02/13 00:17:31.900 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:31.900 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:31.900 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase config" returns:
erasing 'config'...
OKAY [ 0.302s]
finished. total time: 0.302s
09/02/13 00:17:33.902 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase data
09/02/13 00:17:35.663 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:35.663 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:35.663 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase data" returns:
erasing 'data'...
OKAY [ 1.741s]
finished. total time: 1.741s
09/02/13 00:17:37.664 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase spare
09/02/13 00:17:37.972 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:37.972 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:37.972 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase spare" returns:
erasing 'spare'...
OKAY [ 0.288s]
finished. total time: 0.288s
09/02/13 00:17:39.973 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase system
09/02/13 00:17:41.144 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:41.144 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:41.144 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase system" returns:
erasing 'system'...
OKAY [ 1.150s]
finished. total time: 1.150s
09/02/13 00:17:43.146 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE flash radio "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\radio_firmware_6360.bin"
09/02/13 00:18:08.425 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:08.425 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:08.425 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE flash radio "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\radio_firmware_6360.bin"" returns:
sending 'radio' (11310 KB)
fname=L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\radio_firmware_6360.bin...
OKAY [ 0.849s]
writing 'radio'...
OKAY [ 24.409s]
finished. total time: 25.257s
09/02/13 00:18:10.426 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE flash /tmp/NV_130119_MiddleEast.tlv "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\NV_130119_MiddleEast.tlv"
09/02/13 00:18:10.471 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:10.471 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:10.471 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE flash /tmp/NV_130119_MiddleEast.tlv "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\NV_130119_MiddleEast.tlv"" returns:
sending '/tmp/NV_130119_MiddleEast.tlv' (1 KB)
fname=L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\NV_130119_MiddleEast.tlv...
OKAY [ 0.013s]
writing '/tmp/NV_130119_MiddleEast.tlv'...
OKAY [ 0.012s]
finished. total time: 0.025s
09/02/13 00:18:12.472 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE flash splashscreen "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\rocket_start_logo-1080,480-2.bmp.stitched.signed.bin"
09/02/13 00:18:12.694 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:12.694 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:12.694 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE flash splashscreen "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\rocket_start_logo-1080,480-2.bmp.stitched.signed.bin"" returns:
sending 'splashscreen' (1520 KB)
fname=L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\rocket_start_logo-1080,480-2.bmp.stitched.signed.bin...
OKAY [ 0.125s]
writing 'splashscreen'...
OKAY [ 0.077s]
finished. total time: 0.201s
09/02/13 00:18:14.695 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:18:25.749 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:25.749 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:25.749 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 11.033s
09/02/13 00:18:27.750 WARNING: Port 0/0/1 #0: Retry to execute fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:18:38.766 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:38.766 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:38.766 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 10.997s
09/02/13 00:18:40.767 WARNING: Port 0/0/1 #0: Retry to execute fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:18:51.787 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:51.787 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:51.787 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 10.999s
09/02/13 00:18:53.788 WARNING: Port 0/0/1 #0: Retry to execute fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:19:04.807 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:19:04.807 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:19:04.807 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 11.000s
09/02/13 00:19:06.808 WARNING: Port 0/0/1 #0: Retry to execute fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:19:17.828 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:19:17.828 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:19:17.828 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 10.999s
09/02/13 00:19:19.829 ERROR : Port 0/0/1 #0: Flash failure
So if anyone has any clue how to deal with that error, it would help. If I remove the tvl commands from the xml sheet, for any build, it installs fully, but the phone doesn't boot past the last splash screen.
anyone?
viper359 said:
anyone?
Click to expand...
Click to collapse
I am having the same problem. I went into the .XML file and removed the command to apply the NV file. and retried and the flash completed but the device keeps rebooting itself. I am still digging into this and as soon as I get anywhere I will let you know.
I had the same problem. I used the default xml file it failed then i tried the latinamerica xml and it flashed fine. Not sure why quick glance at the xml files looked the same. Good luck hope this helps.
Sent from my
Non-chinese Lenovo K900.
Hello!
I try to unlock bootloader on my Xperia L but it seems something it went wrong...
C:\Users\Nicholas\Downloads\adt-bundle-windows-x86_64-20130729\adt-bundle-window
s-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce getvar version
version: 0.5
finished. total time: 0.002s
C:\Users\Nicholas\Downloads\adt-bundle-windows-x86_64-20130729\adt-bundle-window
s-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce oem unlock 0x6922E5F
13BDBB124
...
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
C:\Users\Nicholas\Downloads\adt-bundle-windows-x86_64-20130729\adt-bundle-window
s-x86_64-20130729\sdk\platform-tools>
Can i know where is my mistake , or if there is something i skipped?
Thanks in advance!
Hellspawm said:
Hello!
I try to unlock bootloader on my Xperia L but it seems something it went wrong...
C:\Users\Nicholas\Downloads\adt-bundle-windows-x86_64-20130729\adt-bundle-window
s-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce getvar version
version: 0.5
finished. total time: 0.002s
C:\Users\Nicholas\Downloads\adt-bundle-windows-x86_64-20130729\adt-bundle-window
s-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce oem unlock 0x6922E5F
13BDBB124
...
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
C:\Users\Nicholas\Downloads\adt-bundle-windows-x86_64-20130729\adt-bundle-window
s-x86_64-20130729\sdk\platform-tools>
Can i know where is my mistake , or if there is something i skipped?
Thanks in advance!
Click to expand...
Click to collapse
Are you using flashtool to unlock? If not, follow this tutorial: http://forum.xda-developers.com/showthread.php?t=2337955
Sent from within a Titan's stomach.
10 thousands THANKS man
allenwalker1998 said:
Are you using flashtool to unlock? If not, follow this tutorial: http://forum.xda-developers.com/showthread.php?t=2337955
Click to expand...
Click to collapse
allenwalker1998 said:
Sent from within a Titan's stomach.
Click to expand...
Click to collapse
i did it, thanks a lot...and i will tell you where was the mistake...when i was asking for Unlock Key on site at IMEI number i delete last number ...after when i try to unlock with flashtool on IMEI field i type the number unless last number...and i got failed again...after that i try once more and i add the last number and work as charm
here
13/058/2013 20:58:56 - INFO - Device connected in fastboot mode
13/059/2013 20:59:45 - INFO - Unlocking phone using key 6922E5F13BDBB124
13/059/2013 20:59:45 - INFO - ...
13/059/2013 20:59:45 - INFO - FAILED (remote: Command did not succeed)
13/059/2013 20:59:45 - INFO - finished. total time: 0.021s
13/000/2013 21:00:07 - INFO - Unlocking phone using key 6922E5F13BDBB124
13/000/2013 21:00:07 - INFO - ...
13/000/2013 21:00:07 - INFO - OKAY [ 0.060s]
13/000/2013 21:00:07 - INFO - finished. total time: 0.060s
13/000/2013 21:00:07 - INFO - Device will reboot into system now
13/000/2013 21:00:07 - INFO - Unlock code saved to C:\Flashtool\custom\mydevices\ZH8000Q5FA\ulcode.txt
Thanks button hit!
Cheers!
Note Unlocking bootloader will erase all your user data including Internal Storage
1. Go to Settings/About Phone and tap some 7-8 times on "Build Number" to enable Developer options in Settings.
2. In developer option just select "OEM unlocking" and "USB debugging"
3. Install the device Drivers.
4. Install adb and fastboot tools (Download link below)
5. Go to adb and fastboot folder in C:\ drive and hold shift and right click and select "Open command window here"
6. Then connect ur device to the System and make sure u have USB debugging enabled.
7. Type "adb devices" to check if the device is connected.
8. You will get a prompt in your device asking permission to allow USB debugging just click OK and allow.
9. Type "adb devices" again to see if ur device is connected or not and if its connected it will show something like this:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0123456789ABCDEF device
10. To reboot into fastboot mode use this command:
"adb reboot bootloader"
this will reboot the device in bootloader
11. Now to check if the device is connected in fastboot mode use this command:
"fastboot devices"
if its connected then u will get some output like this:
C:\adb>fastboot devices
85add0d3 fastboot
12. Now to unlock Bootloader use this command:
"fastboot oem unlock"
you will get an output like this:
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
13. Use this command right after oem unlock command:
"fastboot format userdata"
you will get an optput like this:
C:\adb>fastboot format userdata
Creating filesystem with partition
Size: 4730105856
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 18043
Label:
Blocks: 1154811
Block groups: 36
Reserved block group size
Created filesystem with 11/2
target reported max download
erasing 'userdata'...
OKAY [ 3.375s]
sending 'userdata' (75693 KB
OKAY [ 2.375s]
writing 'userdata'...
OKAY [ 1.625s]
finished. total time: 7.375s
14. To check if ur device bootloader is unlocked or not use this command:
"fastboot oem device-info"
you will see a screen like this:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
15. Now time to reboot the device into system, use this command:
"fastboot reboot"
16. Disconnect the device from system and wait for it to boot up.
It might take some 3-5 mins to boot up so no need to worry
ADB Driver
Hello. I try to unlock my phone but not working adb screen.
All necessary files and drivers are installed.
When I try run command "fastboot oem unlock", received this messages:
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.005s]
finished. total time: 0.006s
I try the this solution: https://forum.xda-developers.com/android/general/sharp-aquos-s2-ss2-sat-thread-t3761071/
and i writing this command in adb, giving me this :
fastboot.exe oem cert_timecount get
...
FAILED (remote: unknown command)
finished. total time: 0.002s
Please help me unlock this phone.
Hi, did you ever resolve this?