ok so i have my play (r800x) unlocked and everything but i installed omnius and it gave me this log when i identified the phone
Code:
[code]
Action journal
17:09:32 Identify
17:09:32 Shows detailed information about the connected phone.
17:09:32 Operating system: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
17:09:32 Application version: 1.38.4753
17:09:32 . The action name is 'Identification'
17:09:32 Selected phone type: Xperia™ PLAY
17:09:32 Selected connection method: USB EROM
17:09:32 i Instructions
17:09:32 i 1. Make sure the phone battery is charged to at least 50%.
17:09:32 i 2. Switch off the phone!
17:09:32 i 3. Remove the phone battery and wait at least 5 seconds, then insert the battery back to the phone!
17:09:32 i 4. Press and hold the return back button, then connect the cable to the phone!
17:09:32 . The action started waiting for the user
17:09:44 . The action finished waiting for the user
17:09:44 Connecting via SEMC USB Flash Device (USB1)...
17:09:44 Device driver version: 2.2.0.5
17:09:44 Detected chipset: MSM7X30
17:09:44 Boot mode: EROM
17:09:44 EROM version: 1241-3656 R9A021
17:09:44 IMEI: A100001713D1A9
17:09:45 Device ID: 65EE28BC0613A8CC0C72EE449ED67DF6ED81A858
17:09:45 Minimum loader AID: 0001
17:09:45 Color: Red SEMC
17:09:45 The phone is rooted.
17:09:45 i Unsigned flashing is disabled.
17:09:45 Sending loader...
17:09:45 Waiting for loader response...
17:09:47 Phone model (from TA): R800x
17:09:47 Current CXC (from TA): 1243-3001_3.0.1.E.0.88
17:09:47 Current CDA (from TA): 1245-4101_R91C
17:09:47 Current FS (from TA): VERIZON_3.0.1.E.0.88
17:09:47 i The phone is not locked to a network.
17:09:47 i Simlock origin: SEMC
17:09:47 s Successfully done.
17:09:47 . The action entered shutdown phase
17:09:47 . The action reported success
Additional details
---
2F B4 6E 69 5C EB 9C F5 36 FD 40 C1 3A DB D8 84
D9 94
---
[/CODE]
does this mean that my bootloader is still locked i'm wondering from line "17:09:45 i Unsigned flashing is disabled." or is it unlocked as i used fastboot and it erased the blocks from the bootloader and it completed successfully
Looks like it is unlocked.... Well at least to me it does.
Sent from my R800x
Lordomn said:
Looks like it is unlocked.... Well at least to me it does.
Sent from my R800x
Click to expand...
Click to collapse
ok thanks a whole bunch for your input but what about the unsigned flashing being disabled?
IF you wan't to check if your bootloader is unlocked, put the phone in fastboot mode and run "fastboot getvar secure"
what that does is check the device security
yes is locked
no is unlocked
As for the unsigned flashing disabled, in flash mode you can't flash anything not signed by SONY. fastboot will let you flash things though.
chevyowner said:
IF you wan't to check if your bootloader is unlocked, put the phone in fastboot mode and run "fastboot getvar secure"
what that does is check the device security
yes is locked
no is unlocked
As for the unsigned flashing disabled, in flash mode you can't flash anything not signed by SONY. fastboot will let you flash things though.
Click to expand...
Click to collapse
OK thanks so much as this is my first device other then the Samsung fascinate that I will flash kernels with so I'm just cautious as also this is my only phone
Sent from my GBTweaked v7.1 r800x using Tapatalk 2
When I try to flash a new kernel flashtools give me this error, some good soul is out there to help me ?
14/051/2015 16:51:36 - INFO - <- This level is successfully initialized
14/051/2015 16:51:36 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
14/051/2015 16:51:39 - INFO - Device disconnected
14/051/2015 16:51:52 - INFO - Device connected in fastboot mode
14/052/2015 16:52:27 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Ronan\Downloads\DXEngine-Fast.img
14/052/2015 16:52:27 - INFO - Flashing selected kernel
14/052/2015 16:52:27 - INFO - sending 'boot' (6808 KB)...
14/052/2015 16:52:27 - INFO - FAILED (remote: Unrecognized command, bork!)
14/052/2015 16:52:27 - INFO - finished. total time: 0.001s
14/052/2015 16:52:27 - INFO - FASTBOOT Output:
sending 'boot' (6808 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.001s
14/052/2015 16:52:27 - INFO - Please check the log before rebooting into system
I also try'ed lupus kernel and get same error.
have you made sure you have the fastboot drivers installed? is it recognized in fastboot?
Lordomn said:
have you made sure you have the fastboot drivers installed? is it recognized in fastboot?
Click to expand...
Click to collapse
Yes, its all installed, strange is that I was on lupus gb/ics when I had this problem, then I thought it was just flash the sotck firmware then was goinf to be fixed.. But not problem still there, and I relock and unlock it again., same results.
I can't even root my device, someone please help :crying: :crying:
15/003/2015 14:03:17 - INFO - Connected device : SonyEricson Xperia Play
15/003/2015 14:03:17 - INFO - Installed version of busybox : N/A
15/003/2015 14:03:17 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf / Build number : 4.0.2.A.0.79
15/003/2015 14:03:55 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
15/003/2015 14:03:57 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
15/003/2015 14:03:57 - INFO - Pushing C:\Flashtool\.\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
15/003/2015 14:03:58 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
15/003/2015 14:03:58 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
15/003/2015 14:03:59 - INFO - Running part1 of Root Exploit, please wait
15/004/2015 14:04:18 - INFO - Waiting for device. After 60secs, stop waiting will be forced
15/005/2015 14:05:18 - INFO - Forced stop waiting.
15/005/2015 14:05:18 - ERROR - The part1 exploit did not work
15/005/2015 14:05:18 - INFO - Cleaning files
HUEguy said:
I can't even root my device, someone please help :crying: :crying:
15/003/2015 14:03:17 - INFO - Connected device : SonyEricson Xperia Play
15/003/2015 14:03:17 - INFO - Installed version of busybox : N/A
15/003/2015 14:03:17 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf / Build number : 4.0.2.A.0.79
15/003/2015 14:03:55 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
15/003/2015 14:03:57 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
15/003/2015 14:03:57 - INFO - Pushing C:\Flashtool\.\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
15/003/2015 14:03:58 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
15/003/2015 14:03:58 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
15/003/2015 14:03:59 - INFO - Running part1 of Root Exploit, please wait
15/004/2015 14:04:18 - INFO - Waiting for device. After 60secs, stop waiting will be forced
15/005/2015 14:05:18 - INFO - Forced stop waiting.
15/005/2015 14:05:18 - ERROR - The part1 exploit did not work
15/005/2015 14:05:18 - INFO - Cleaning files
Click to expand...
Click to collapse
Zergrush work for up to .42 firmware
For later (.62 .69 .79 or .84) firmwares use eroot
Edit: Is DXEngine-Fast.img even a kernel for xperia play?
Bakisha said:
Zergrush work for up to .42 firmware
For later (.62 .69 .79 or .84) firmwares use eroot
Edit: Is DXEngine-Fast.img even a kernel for xperia play?
Click to expand...
Click to collapse
Yeah, well, the site I download it was saying that, but even this or lupus kernel(v12 gb or v7 GB/ICS) I can't flash it, always got that error message
Edit: Eroot works, thanks a lot!
HUEguy said:
Yeah, well, the site I download it was saying that, but even this or lupus kernel(v12 gb or v7 GB/ICS) I can't flash it, always got that error message
Edit: Eroot works, thanks a lot!
Click to expand...
Click to collapse
Ah, you mean extremekernel (i didn't know exact kernel filename).
My guess is that you still have locked bootloader.
If you unlocked bootloader with official sony's method, then i don't know what might be the problem
Bakisha said:
Ah, you mean extremekernel (i didn't know exact kernel filename).
My guess is that you still have locked bootloader.
If you unlocked bootloader with official sony's method, then i don't know what might be the problem
Click to expand...
Click to collapse
I've unlock it via flashtools, I relock again and I will try the official sony method, then I will let you know if I still have the problem. Its strange cause before this happen I flashed kernels whitout any problem then flashtools started to give this error
@Bakisha , I was see the comments on the video of the "How to unlock the boot loader of an Xperia device" from sonydev channel and the comments people was saying something about losing the DRM key with that method and camera or bravia engine not working, is it safe to do that on the xplay ?
HUEguy said:
@Bakisha , I was see the comments on the video of the "How to unlock the boot loader of an Xperia device" from sonydev channel and the comments people was saying something about losing the DRM key with that method and camera or bravia engine not working, is it safe to do that on the xplay ?
Click to expand...
Click to collapse
No, for Xperia Play it doesn't matter (it matter for Xperia 2013+ phones). Once you unlock bootloader, you don't need to relock it ever again.
As i said, i don't know why you can't flash kernel, but here is some general tips:
-reinstall/update flashtool
-reinstall all drivers from device manager related to xPlay
-try different usb cable
-try different (all) usb ports
-try on different pc
-try kernels in ftf format
-redownload kernel you are trying to flash
-try unlocking your bootloader with official Sony's method
Bakisha said:
No, for Xperia Play it doesn't matter (it matter for Xperia 2013+ phones). Once you unlock bootloader, you don't need to relock it ever again.
Click to expand...
Click to collapse
Yeah finally works on windows 8 with latest flashtool version, thank you so much for your answers, it helped me a lot.
please i have a Sony arc s but anytime i try to unlock i get this "FAILED " (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
finished. total time : 0.009s......but i have the unlock keys too from Sony and i know i am following the same steps they gave me .guys please help me....thanks in advance
driver install ???
nextking_jay1 said:
please i have a Sony arc s but anytime i try to unlock i get this "FAILED " (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
finished. total time : 0.009s......but i have the unlock keys too from Sony and i know i am following the same steps they gave me .guys please help me....thanks in advance
Click to expand...
Click to collapse
1 http://www.flashtool.net/downloads.php
2 download and intall flashtool
3 install driver in c: / flashtool / driver / install Flashtool-drivers.exe
unlock cmd from sony http://developer.sonymobile.com/unlockbootloader/
1 fastboot.exe -i 0x0fce getvar version
2 fastboot.exe -i 0x0fce oem unlock 0xKEY
or via flashtool check unlock
or wotan server (pay) http://www.wotanserver.com/en/sony-ericsson/xperia-arc-s-lt18/unlock-tool/debranding-flash !!!
check thank's please for help you !!!
Hello guys I am a new member here but I have been followed this forum for years and at the end I decided to became a member to get your help.
I have used my device for 5 years and after a while the power button was broken. I needed to press it hard to make it work. At the end my z1c suddenly turned off and I couldn't turn on it anymore. These are things i did:
- I tried to turn on it by pressing the small button near the sim slot. It doesn't give any response on battery but when it is on plug it vibrates three times but it doesn't boot and starts to charge the phone again. By the way I am able to charge the device.
-To flash a firmware I used Software Repair option on Xperia Companion but unfortunately I broke power flex cable while disassembling so
the device couldn't enter download mode. It also sometimes gives an error like this: "Your device is locked".
- I also tried munjeni's testpoint solution .Here is the log:
Code:
12.07.2019 18:54:09 Welcome to S1 tool.
12.07.2019 18:54:09 That is small and crippled subset of SETOOL2 service tool.
12.07.2019 18:54:13
12.07.2019 18:54:13 SELECT FIRMWARE PACKAGES
12.07.2019 18:54:13 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
12.07.2019 18:54:18 CHECKING PACKAGES ...
12.07.2019 18:54:18
12.07.2019 18:54:18 DETACH USB CABLE FROM PHONE
12.07.2019 18:54:18 REMOVE BATTERY FROM PHONE
12.07.2019 18:54:18 ATTACH TESTPOINT
12.07.2019 18:54:18 PRESS "READY", THEN ATTACH USB CABLE TO PHONE
12.07.2019 18:54:18
12.07.2019 19:08:01 will use Sahara protocol ...
12.07.2019 19:08:01 REMOVE TESTPOINT NOW, THEN PRESS "READY"
12.07.2019 19:08:01
12.07.2019 19:08:46 PROCESSING ...
12.07.2019 19:08:47 llbug: write error: "Aygıt komutu algılayamıyor"
12.07.2019 19:08:47 llbug: blk write fail.fatal
12.07.2019 19:08:47 Elapsed:873 secs.
12.07.2019 19:09:10
12.07.2019 19:09:10 SELECT FIRMWARE PACKAGES
12.07.2019 19:09:10 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
12.07.2019 19:09:14 CHECKING PACKAGES ...
12.07.2019 19:09:14
12.07.2019 19:09:14 DETACH USB CABLE FROM PHONE
12.07.2019 19:09:14 REMOVE BATTERY FROM PHONE
12.07.2019 19:09:14 ATTACH TESTPOINT
12.07.2019 19:09:14 PRESS "READY", THEN ATTACH USB CABLE TO PHONE
12.07.2019 19:09:14
12.07.2019 19:09:42 will use Sahara protocol ...
12.07.2019 19:09:42 REMOVE TESTPOINT NOW, THEN PRESS "READY"
12.07.2019 19:09:42
12.07.2019 19:09:56 PROCESSING ...
12.07.2019 19:09:56 SERIAL NUMBER : 08194506
12.07.2019 19:09:56 HARDWARE ID : 04000100E1007B00
12.07.2019 19:09:56 HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
12.07.2019 19:09:57 Emergency loader uploaded ...
12.07.2019 19:10:01
12.07.2019 19:10:01 RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
12.07.2019 19:10:01 LOADER AID: 0004
12.07.2019 19:10:01 DEVICE ID: 06451908
12.07.2019 19:10:01 FLASH ID: "0015/01000001"
12.07.2019 19:10:01 LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
12.07.2019 19:10:01
12.07.2019 19:10:02 WRITING PACKAGES ...
12.07.2019 19:10:02 Processing package
12.07.2019 19:10:02 C:\Users\BARIN\Desktop\fw\amami_testpoint.SIN_FILE_SET
12.07.2019 19:10:02
12.07.2019 19:10:02 WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_RHINE1.2_LA1.04_19
12.07.2019 19:10:02 PARSING: "DEVELOPMENT"
12.07.2019 19:10:02 value OTP_LOCK_STATUS_1 : UNLOCKED, not match LOCKED
12.07.2019 19:10:02 PARSING: "TEST_OEM0_007B00E1"
12.07.2019 19:10:02 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
12.07.2019 19:10:02 value OTP_DATA_1 : 00000100, not match 01000400
12.07.2019 19:10:02 value IDCODE_1 : 007B00E1, match 007B00E1
12.07.2019 19:10:02 PARSING: "PRECOMMERCIAL_007B00E1"
12.07.2019 19:10:02 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
12.07.2019 19:10:02 value OTP_DATA_1 : 01000400, match 01000400
12.07.2019 19:10:02 value IDCODE_1 : 007B00E1, match 007B00E1
12.07.2019 19:10:02 PROCESSING : dbi_S1_Boot_MSM8974_Rhine1.2_19_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
12.07.2019 19:10:02 PROCESSING : emmc_appsboot_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
12.07.2019 19:10:02 PROCESSING : s1sbl_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
12.07.2019 19:10:03 PROCESSING : sbl1_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
12.07.2019 19:10:03 PROCESSING : tz_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
12.07.2019 19:10:03 PROCESSING : Amami_S1BootConfig_MiscTA_130115_1430.ta
12.07.2019 19:10:03 MINOR ERROR [ Open_TA_failed, err: 001D ]
12.07.2019 19:10:03 BOOT UPDATED
12.07.2019 19:10:03 Processing ACPU files
12.07.2019 19:10:03 PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:04 PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:05 PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:06 PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:07 SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
12.07.2019 19:10:07 PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:07 no update files in package
12.07.2019 19:10:07 FINISHED
12.07.2019 19:10:08 Elapsed:57 secs.
I wanted to know what should happen to my device. Possible scenarios on my mind are those:
- Power ic on the mainboard broken,
- Somebody copied its imei and device was locked (It is nearly impossible as it has qualcomm chip),
- Battery completely discharged
I would be really happy if you give your opinions and solutions other than mine. Thanks for your help.
Sounds like you should replace the battery.