Has anyone got a easy newbie walk through on how to replace drm keys? I unlocked bootloader and lost them in the process. The only thing that won't work is my Camera at the moment help would really be appreciated here's my model information and the faults.
frankiebateman said:
Has anyone got a easy newbie walk through on how to replace drm keys? I unlocked bootloader and lost them in the process. The only thing that won't work is my Camera at the moment help would really be appreciated here's my model information and the faults.
Click to expand...
Click to collapse
You can't recover them. Your best call is using one of the custom kernels with drm fix.
frankiebateman said:
Has anyone got a easy newbie walk through on how to replace drm keys? I unlocked bootloader and lost them in the process. The only thing that won't work is my Camera at the moment help would really be appreciated here's my model information and the faults.
Click to expand...
Click to collapse
DRM KEYS can never be revered!
before unlocking, you should have used Dirtycow script to EXTRACT TA.IMG (android6.01)
anyhow
now the only solution is to use kernel with drmfix
https://forum.xda-developers.com/xperia-x/development/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Is there one that will work with my phone and also a walk through that I can understand lol
frankiebateman said:
Is there one that will work with my phone and also a walk through that I can understand lol
Click to expand...
Click to collapse
this kernel will work: https://forum.xda-developers.com/xp...t-xperia-x-f5122-android-n-34-2-2-47-t3594502
tried flashing but keeps saying failed ?
13/045/2017 21:45:47 - INFO - Flashtool Version 0.9.23.2 built on 19-01-2017 21:50:00
13/045/2017 21:45:47 - INFO - Executing search strategies to find proxy selector
13/045/2017 21:45:48 - INFO - No proxy found for IE. Trying next one
13/045/2017 21:45:48 - INFO - No proxy found for firefox. Trying next one
13/045/2017 21:45:48 - INFO - No proxy found for java. Trying next one
13/045/2017 21:45:48 - INFO - Syncing devices from github
13/045/2017 21:45:49 - INFO - Opening devices repository.
13/045/2017 21:45:50 - INFO - Scanning devices folder for changes.
13/046/2017 21:46:14 - INFO - Pulling changes from github.
13/046/2017 21:46:15 - INFO - Quietly closing devices repository.
13/046/2017 21:46:16 - INFO - Devices sync finished.
13/046/2017 21:46:16 - INFO - Loading devices database
13/046/2017 21:46:16 - INFO - Loaded 98 devices
13/046/2017 21:46:16 - INFO - Starting phone detection
13/046/2017 21:46:22 - INFO - Device connected in fastboot mode
13/046/2017 21:46:45 - INFO - Device disconnected
13/049/2017 21:49:43 - INFO - Now plug your device in Fastboot Mode
13/049/2017 21:49:53 - INFO - Device connected in fastboot mode
13/050/2017 21:50:16 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Batemans\Desktop\New folder\Suzu_F5121_34.3.A.0.206-12July17\Suzu_F5121_34.3.A.0.206-12July17\boot_F5121_34.3.A.0.206_7.1.1_clean.img
13/050/2017 21:50:16 - INFO - Flashing selected kernel
13/050/2017 21:50:18 - INFO - target reported max download size of 536870912 bytes
13/050/2017 21:50:18 - INFO - sending 'boot' (17204 KB)...
13/050/2017 21:50:18 - INFO - OKAY [ 0.558s]
13/050/2017 21:50:18 - INFO - writing 'boot'...
13/050/2017 21:50:18 - INFO - FAILED (remote: Command not allowed)
13/050/2017 21:50:18 - INFO - finished. total time: 0.561s
13/050/2017 21:50:18 - INFO - FASTBOOT Output:
target reported max download size of 536870912 bytes
sending 'boot' (17204 KB)...
OKAY [ 0.558s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.561s
13/050/2017 21:50:18 - INFO - Please check the log before rebooting into system
and bootloader is unlocked ive checked service menu
sorry for all the posts ive now managed to flash but am getting the following message. your phone is unlocked and cannot be trusted and then on loadup to start android enter your password
kistigun said:
this kernel will work: https://forum.xda-developers.com/xp...t-xperia-x-f5122-android-n-34-2-2-47-t3594502
Click to expand...
Click to collapse
Thanks for that! All working now just a message on startup your phone is unlocked and cannot be trusted. Is there any way to hide this?
No, that is the message you always get after unlocking your bootloader. Only solution is to relock and flash a stock rom.
I remember when sony did this to us with the z1 i think it was, we all complained to sony and they delivered an update that allowed the camera to work again with an unlocked loader.
Related
Hi all,
i tried several time to root my device, bot via flashtools and adb. As written in many guides here and around, I downgrade kernel, use binary method, then upgrade kernel again. When I switch on the phone, I have SU installed, and apps with su permission like Samba filesharing, work perfectly. I also have CWM recovery installed and working. But
I have problem when I want to flash a new kernel. This is the log of flashtools:
Code:
26/052/2013 15:52:34 - INFO - (FastBootToolboxGUI.java:461) - Selected kernel (boot.img or kernel.sin): C:\Users\administración\Downloads\boot.img
26/052/2013 15:52:34 - INFO - (FastBootToolboxGUI.java:465) - Flashing selected kernel
26/052/2013 15:52:34 - INFO - (ProcessBuilderWrapper.java:91) - sending 'boot' (6726 KB)...
26/052/2013 15:52:34 - INFO - (ProcessBuilderWrapper.java:91) - FAILED (remote: The Device must be rooted first)
26/052/2013 15:52:34 - INFO - (ProcessBuilderWrapper.java:91) - finished. total time: 0.002s
26/052/2013 15:52:34 - INFO - (FastBootToolboxGUI.java:467) - FASTBOOT Output:
sending 'boot' (6726 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
26/052/2013 15:52:34 - INFO - (FastBootToolboxGUI.java:468) - Please check the log before rebooting into system
26/052/2013 15:52:46 - INFO - (FastBootToolboxGUI.java:231) - Finished Fastboot Toolbox
Any hint?
Sorry, I post in the wrong section. Please mod move it in General.
Thanks
R: Unable to root Xperia P
Rooted on fastboot/adb is unlocked,you have unlocked bootloader?
If no you cant flash kernel partition for now!
i have Bricked my Xperia ion(soft brick).
And now if i plug to charger or to pc it starts rebooting ( only sony logo lights up and then become yellowish and restarts the phone,it appears i think 10-20 times and then turn off).
I can't charge because if i put to wall charger after 10 minutes it starts bootlooping and then turn off and again the led becomes red and then again it starts bootloops........:crying::crying::crying::crying::crying::crying::crying::crying:
Gaurav Vashist said:
i have Bricked my Xperia ion(soft brick).
And now if i plug to charger or to pc it starts rebooting ( only sony logo lights up and then become yellowish and restarts the phone,it appears i think 10-20 times and then turn off).
I can't charge because if i put to wall charger after 10 minutes it starts bootlooping and then turn off and again the led becomes red and then again it starts bootloops........:crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Ok, can you enter to CWM?
Plus, this is not the subforum to post this things.
Try this.
This is the forum where you can post your problem.
manudo said:
Ok, can you enter to CWM?
Plus, this is not the subforum to post this things.
Try this.
This is the forum where you can post your problem.
Click to expand...
Click to collapse
no i can't enter the cwc:crying::crying:
and for ur rom i think u should try a different name ( my opinion_)
Gaurav Vashist said:
no i can't enter the cwc:crying::crying:
and for ur rom i think u should try a different name ( my opinion_)
Click to expand...
Click to collapse
I don't have that device but there's something called "fastboot" mode that is for flashing custom kernels. I suggest that try to enter that mode, if you can... Flash a kernel for your phone and enter to CWM, if you can do that, you have done a HUGE step.
Have to update my signature, I'll build in JB not ICS, nevermind.
manudo said:
I don't have that device but there's something called "fastboot" mode that is for flashing custom kernels. I suggest that try to enter that mode, if you can... Flash a kernel for your phone and enter to CWM, if you can do that, you have done a HUGE step.
Have to update my signature, I'll build in JB not ICS, nevermind.
Click to expand...
Click to collapse
i can access fastmode but flashtool gives an error"device must be rooted first"
05/023/2014 10:23:13 - INFO - <- This level is successfully initialized
05/023/2014 10:23:14 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
05/023/2014 10:23:21 - INFO - Device disconnected
05/023/2014 10:23:43 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/023/2014 10:23:43 - INFO - Preparing files for flashing
05/023/2014 10:23:43 - ERROR - .\firmwares\prepared\userdata.sin (Access is denied)
05/023/2014 10:23:43 - INFO - Cannot open bundle. Flash operation canceled
05/024/2014 10:24:02 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/024/2014 10:24:02 - INFO - Preparing files for flashing
05/024/2014 10:24:42 - INFO - List of connected devices (Device Id) :
05/024/2014 10:24:42 - INFO - List of ADB devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:42 - INFO - List of fastboot devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:48 - INFO - Please connect your device into flashmode.
05/031/2014 10:31:42 - INFO - Device connected in fastboot mode
05/032/2014 10:32:03 - INFO - Flash canceled
05/032/2014 10:32:12 - ERROR - This action needs a connected device in ADB mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ ]
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/032/2014 10:32:25 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/033/2014 10:33:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\kernel.sin
05/033/2014 10:33:04 - INFO - Flashing selected kernel
05/033/2014 10:33:04 - INFO - sending 'boot' (3209 KB)...
05/033/2014 10:33:04 - INFO - FAILED (remote: The Device must be rooted first)
05/033/2014 10:33:04 - INFO - finished. total time: 0.008s
05/033/2014 10:33:04 - INFO - FASTBOOT Output:
sending 'boot' (3209 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.008s
and also i can't access recovery mode)
No i think there should be no issuse
Gaurav Vashist said:
i can access fastmode but flashtool gives an error"device must be rooted first"
05/023/2014 10:23:13 - INFO - <- This level is successfully initialized
05/023/2014 10:23:14 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
05/023/2014 10:23:21 - INFO - Device disconnected
05/023/2014 10:23:43 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/023/2014 10:23:43 - INFO - Preparing files for flashing
05/023/2014 10:23:43 - ERROR - .\firmwares\prepared\userdata.sin (Access is denied)
05/023/2014 10:23:43 - INFO - Cannot open bundle. Flash operation canceled
05/024/2014 10:24:02 - INFO - Selected LT28h / 6.2.B.0.211 / Generic
05/024/2014 10:24:02 - INFO - Preparing files for flashing
05/024/2014 10:24:42 - INFO - List of connected devices (Device Id) :
05/024/2014 10:24:42 - INFO - List of ADB devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:42 - INFO - List of fastboot devices :
05/024/2014 10:24:42 - INFO - - none
05/024/2014 10:24:48 - INFO - Please connect your device into flashmode.
05/031/2014 10:31:42 - INFO - Device connected in fastboot mode
05/032/2014 10:32:03 - INFO - Flash canceled
05/032/2014 10:32:12 - ERROR - This action needs a connected device in ADB mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - ERROR - This action can only be done in fastboot mode
05/032/2014 10:32:24 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ ]
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/032/2014 10:32:25 - INFO - Fetching connected device info
05/032/2014 10:32:25 - INFO - Connected device info: [ PSDN:CB5A1KN8ZN&ZLP ]
05/033/2014 10:33:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\kernel.sin
05/033/2014 10:33:04 - INFO - Flashing selected kernel
05/033/2014 10:33:04 - INFO - sending 'boot' (3209 KB)...
05/033/2014 10:33:04 - INFO - FAILED (remote: The Device must be rooted first)
05/033/2014 10:33:04 - INFO - finished. total time: 0.008s
05/033/2014 10:33:04 - INFO - FASTBOOT Output:
sending 'boot' (3209 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.008s
and also i can't access recovery mode)
No i think there should be no issuse
Click to expand...
Click to collapse
Try to post the same thing in the Xperia ION forum, since I don't own the device, there's a LOT of people that can help you.
I'm trying to unlock my bootloader, i've already installed ADB and fastboot drivers from sonys website and the Android SDK platform-tools with adb and fastboot
Both ADB and fastboot recognize my device, i've approved the device's RSA fingerprint from my phone, and I can run the command ADB reboot bootloader to get into fastboot.
Fastboot devices shows my correct device and I can run fastboot getvar version which returns 5.0
I can run fastboot reboot, and fastboot devices without any problem
When I try to unlock my device I get this error
Code:
fastboot.exe -i 0x0fce oem unlock 0xexamplekey
...
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
My devices shows bootloader unlock is allowed in the service menu.
Not sure what else to try besides another PC.
More stuff
Code:
08/053/2015 11:53:09 - INFO - Please connect your device into flashmode.
08/053/2015 11:53:10 - INFO - Opening device for R/W
08/053/2015 11:53:10 - INFO - Reading device information
08/053/2015 11:53:10 - INFO - Phone ready for flashmode operations.
08/053/2015 11:53:10 - INFO - Current device : E5823 - CB5A29DXXX - 1298-7272_R8B - 1295-6639_32.0.A.6.152 - GENERIC_32.0.A.6.152
08/053/2015 11:53:10 - INFO - Processing loader.sin
08/053/2015 11:53:10 - INFO - Checking header
08/053/2015 11:53:10 - INFO - Flashing data
08/053/2015 11:53:10 - INFO - Processing of loader.sin finished.
08/053/2015 11:53:10 - INFO - Loader : S1_Root_f936 - Version : MSM8994_41 / Boot version : S1_Boot_MSM8994_LA1.2_119 / Bootloader status : ROOTABLE
08/053/2015 11:53:10 - INFO - Start Reading unit 000008B2
08/053/2015 11:53:10 - INFO - Reading TA finished.
08/053/2015 11:53:11 - INFO - Ending flash session
08/053/2015 11:53:11 - INFO - Now unplug your device and restart it into fastbootmode
08/053/2015 11:53:11 - INFO - Device connected in flash mode
08/053/2015 11:53:11 - INFO - Device disconnected
08/053/2015 11:53:19 - INFO - Device connected in flash mode
08/053/2015 11:53:38 - INFO - Device disconnected
08/053/2015 11:53:46 - INFO - Device connected in fastboot mode
08/054/2015 11:54:20 - INFO - Unlocking phone using key 0xB6E1A89C6FEXXXXX
08/054/2015 11:54:20 - INFO - ...
08/054/2015 11:54:20 - INFO - FAILED (remote: Command not allowed)
08/054/2015 11:54:20 - INFO - finished. total time: 0.011s
08/054/2015 11:54:27 - INFO - Unlocking phone using key B6E1A89C6FEXXXXX
08/054/2015 11:54:27 - INFO - ...
08/054/2015 11:54:27 - INFO - FAILED (remote: Command not allowed)
08/054/2015 11:54:27 - INFO - finished. total time: 0.008s
08/055/2015 11:55:25 - INFO - List of connected devices (Device Id) :
08/055/2015 11:55:25 - INFO - - USB\VID_0FCE&PID_0DDE\CB5A29DXXX Driver installed : true
08/055/2015 11:55:25 - INFO - List of ADB devices :
08/055/2015 11:55:25 - INFO - - none
08/055/2015 11:55:25 - INFO - List of fastboot devices :
08/055/2015 11:55:25 - INFO - - CB5A29DXXX
http://forum.xda-developers.com/showthread.php?t=3236237
Xerwulf said:
http://forum.xda-developers.com/showthread.php?t=3236237
Click to expand...
Click to collapse
I've used you guide, it didn't work.
I've tried unlocking with fastboot and flash tool with no success.
Maybe you are in flashmode not fastboot? Volume down is flashmode and volume up fastboot, when I remember right
Xerwulf said:
Maybe you are in flashmode not fastboot? Volume down is flashmode and volume up fastboot, when I remember right
Click to expand...
Click to collapse
Nope, I've tried both. I can get into both modes, but flashing or unlocking gives me that error
Did you start Cmd as ADMIN?
Xerwulf said:
Did you start Cmd as ADMIN?
Click to expand...
Click to collapse
Yes.
Found my mistake, i didn't check the allow OEM bootloader unlock box. It's working now. My mistake.
tylerwatt12 said:
Found my mistake, i didn't check the allow OEM bootloader unlock box. It's working now. My mistake.
Click to expand...
Click to collapse
I'm having the exact same issue right now, where did you find this OEM bootloader unlock box?? I only have a blank screen when I get to fastboot mode on the Z5C... Cheers
ds980x said:
I'm having the exact same issue right now, where did you find this OEM bootloader unlock box?? I only have a blank screen when I get to fastboot mode on the Z5C... Cheers
Click to expand...
Click to collapse
In the same place where you enabled USB debugging (to enable ADB), developer options of settings.
You won't ever see a screen in fastboot mode, just a color LED, same with flashmode. The only time you'll see a screen is if you hit the volume buttons after the amber light during boot, which takes you into software update mode, (recovery)
Never mind found it in dev settings cant believe I missed such a small thing to create huge problems lol all done
Hi
I followed the guide here: http://goo.gl/b7NTn9
My problem is, I keep getting the error FAILED (remote: Command not allowed) as soon as I press "unlock" after I pasted the unlock code.
Can anyone perhaps help , please? I'm at my wits end on this one.
Log Dump:
Code:
24/052/2016 13:52:13 - INFO - Please connect your device into flashmode.
24/052/2016 13:52:21 - INFO - Device connected in flash mode
24/052/2016 13:52:21 - INFO - Opening device for R/W
24/052/2016 13:52:21 - INFO - Reading device information
24/052/2016 13:52:21 - INFO - Phone ready for flashmode operations.
24/052/2016 13:52:21 - INFO - Opening TA partition 2
24/052/2016 13:52:21 - INFO - Current device : E2303 - [COLOR="red"]DEVICE_CODE_HERE[/COLOR] - 1294-6067_R9A - 1291-5963_26.1.A.2.167 - GENERIC_26.1.A.2.167
24/052/2016 13:52:21 - INFO - Closing TA partition
24/052/2016 13:52:21 - INFO - Processing loader.sin
24/052/2016 13:52:21 - INFO - Checking header
24/052/2016 13:52:21 - INFO - Flashing data
24/052/2016 13:52:22 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_36 / Bootloader status : ROOTABLE
24/052/2016 13:52:22 - INFO - Max packet size set to 512K
24/052/2016 13:52:22 - INFO - Opening TA partition 2
24/052/2016 13:52:22 - INFO - Start Reading unit 000008B2
24/052/2016 13:52:22 - INFO - Reading TA finished.
24/052/2016 13:52:22 - INFO - Closing TA partition
24/052/2016 13:52:22 - INFO - Ending flash session
24/052/2016 13:52:22 - INFO - Now unplug your device and restart it into fastbootmode
24/052/2016 13:52:22 - INFO - Device connected in flash mode
24/052/2016 13:52:23 - INFO - Device disconnected
24/054/2016 13:54:13 - INFO - Device connected in fastboot mode
24/054/2016 13:54:32 - INFO - Unlocking phone using key [COLOR="red"]UNLOCK_KEY_HERE[/COLOR]
24/054/2016 13:54:32 - INFO - ...
24/054/2016 13:54:32 - INFO - FAILED (remote: Command not allowed)
24/054/2016 13:54:32 - INFO - finished. total time: 0.005s
Thank you for reading!
Have you checked to see if unlock is allowed? And if it says it can be unlocked, did you put the right imei for unlock. I found that the unlock code for the Xperia M worked fine
hy
exactly the same problem is occuring to me !
i tried to unlock the bootloader with different options for example the new and the old version of flashtool but it´s not working.
the rooting status is: Bootloader unlock allowed: Yes
i also noticed that when you put in your imei code on the sony developer page you have to put in 15 digits to get the ul-code but the flashtool just shows 14 digits of the imei code when you have to enter it.
i have the e2303 8Gb
build number 26.1.A.2.167
Android 5.0
Thank you !
ardentis said:
Have you checked to see if unlock is allowed? And if it says it can be unlocked, did you put the right imei for unlock. I found that the unlock code for the Xperia M worked fine
Click to expand...
Click to collapse
Thanks for replying! Yeah, I did all that, I tried the M and M2 unlock code, unlock is allowed, it just isn't doing anything though
Make sure you use the imei from the phone and not the unlock tool. It's purposely wrong to protect your imei if you share a picture of the unlock tool. Just keep trying
ardentis said:
Make sure you use the imei from the phone and not the unlock tool. It's purposely wrong to protect your imei if you share a picture of the unlock tool. Just keep trying
Click to expand...
Click to collapse
I have also the Problem, in the settings is Allowed, but the Software can't unlock the
the Bootloader well (remote: Command not allowed),
I have with Blu install't .1.128 but no way.
Do have tips for me?
i have read the Driver can under windows 8.1 a problem, but he find my Smartphone,
also must it work or?!
Greetz
Unlocking the bootloader in M4 Aqua
Was stuck with the same problem. M4, says its bootloader can be unlocked.
13/034/2016 22:34:37 - INFO - Unlocking phone using key XXXXXXXXXXXXXXX
13/034/2016 22:34:37 - INFO - ...
13/034/2016 22:34:37 - INFO - FAILED (remote: Command not allowed)
13/034/2016 22:34:37 - INFO - finished. total time: 0.005s
The solution is to enable OEM unlocking in the developer options. Also, in some cases, it helps to perform a factory reset before unlocking.
Good luck!
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.
ethoms said:
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.
Click to expand...
Click to collapse
Thanks bro. It worked
Hi
Same problem, and thanks for oem unlocking in developers menu option.
The unlock option works fine now
ethoms said:
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.
Click to expand...
Click to collapse
i have same problem, but my device bootlop so i can't allow OEM unlocking. someone help me please? tanks
This thread is dead, but I'll post anyways. I am using xperia xz1c. Bootloader unlock is allowed. OEM unlocking is allowed. Device is being detected on fastboot devices command. On fastboot, the output I am getting is "FAILED (remote: command did not succeed)". I have tried latest platform tools 28.0.1, older platform tools 25.0.5 and 26.0.0 with no success. Thanks for reading.
i decided to mess around with my old wt19 so after unlocking the bootloader i wanted to install a custom rom. I have some experience with that so im not a complete newbie
I have flashed roms and unlocked bootloaders on multiple devices. I always read carefully instructions etc.
But this one gave me a headache.
After deciding to install a custom rom i had to unlock the bootloader. I had problems with fastboot recognizing the device but after an hour and a half of so of reading ad searching i managed to get it working and unlocked the bootlader.
After that i spent about 50 mnutes looking for a good kernel and after failing to flash one via fastboot i used flashtool to do it.
I used this guide
After seeing no errors i unplugged the phone and tried booting. I pressed power button, the phone vibrated but the screen was always black and nothing happened.
Long pressing power button did not reset, completely unresponsive, i had to pull the battery out to make it vibrate again uppon booting but same thing happened, no response. Flashtool no longer recognises the device the ledt doesnt light up when charging but the phone got hot during this time indicating itwas trying to do something.
After a short while,maybe the battery died, but even pulling out the battery and trying to boot again did not make any vibration indicating it was completely dead.
Kernel i flashed was kappa kernel
I tried booting to kernels cwm recovery but nothing happened.
SO im out of ideas
Any suggestions ?
This is the flashtool log
15/003/2018 16:03:43 - INFO - Flashtool Version 0.9.25.0 built on 17-06-2018 16:00:00
15/003/2018 16:03:43 - INFO - Searching for a web proxy
15/003/2018 16:03:44 - INFO - No proxy found, using direct connection
15/003/2018 16:03:44 - INFO - Syncing devices from github
15/003/2018 16:03:44 - INFO - Opening devices repository.
15/003/2018 16:03:44 - INFO - Scanning devices folder for changes.
15/003/2018 16:03:52 - INFO - Pulling changes from github.
15/003/2018 16:03:53 - INFO - Devices sync finished.
15/003/2018 16:03:53 - INFO - Loading devices database
15/003/2018 16:03:53 - INFO - Loaded 112 devices
15/003/2018 16:03:53 - INFO - Starting phone detection
15/003/2018 16:03:56 - INFO - Device disconnected
15/027/2018 16:27:11 - INFO - Device connected with USB debugging on
15/027/2018 16:27:11 - INFO - Connected device : SonyEricson Xperia Live Walkman
15/027/2018 16:27:11 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary.
15/027/2018 16:27:11 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Platform : 32bits / Build number : 4.1.B.0.587
15/027/2018 16:27:11 - INFO - Checking root access
15/027/2018 16:27:12 - INFO - Installing toolbox to device...
15/027/2018 16:27:12 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
15/027/2018 16:27:12 - INFO - Running installftkit as root thru sysrun
15/027/2018 16:27:13 - INFO - Root Access Allowed
15/027/2018 16:27:28 - INFO - Device disconnected
15/027/2018 16:27:56 - INFO - Device connected with USB debugging off
15/027/2018 16:27:56 - INFO - For 2011 devices line, be sure you are not in MTP mode
15/027/2018 16:27:58 - INFO - Device connected with USB debugging on
15/027/2018 16:27:59 - INFO - Connected device : SonyEricson Xperia Live Walkman
15/027/2018 16:27:59 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary.
15/027/2018 16:27:59 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Platform : 32bits / Build number : 4.1.B.0.587
15/027/2018 16:27:59 - INFO - Checking root access
15/028/2018 16:28:01 - INFO - Root Access Allowed
15/030/2018 16:30:40 - INFO - Now plug your device in Fastboot Mode
15/030/2018 16:30:48 - INFO - Device disconnected
15/031/2018 16:31:05 - INFO - Device connected in fastboot mode
15/031/2018 16:31:34 - INFO - Selected kernel (boot.img or kernel.sin): C:\adb\platform-tools\KaCoconut2.img
15/031/2018 16:31:34 - INFO - Flashing selected kernel
15/031/2018 16:31:36 - INFO - target didn't report max-download-size
15/031/2018 16:31:36 - INFO - sending 'boot' (5580 KB)...
15/031/2018 16:31:36 - INFO - (bootloader) USB download speed was 9186kB/s
15/031/2018 16:31:36 - INFO - OKAY [ 0.629s]
15/031/2018 16:31:36 - INFO - writing 'boot'...
15/031/2018 16:31:36 - INFO - (bootloader) Download buffer format: boot IMG
15/031/2018 16:31:36 - INFO - (bootloader) Flash of partition 'boot' requested
15/031/2018 16:31:36 - INFO - (bootloader) S1 partID 0x00000003, block 0x00000148-0x00000179
15/031/2018 16:31:36 - INFO - (bootloader) Erase operation complete, 0 bad blocks encountered
15/031/2018 16:31:36 - INFO - (bootloader) Flashing...
15/031/2018 16:31:36 - INFO - (bootloader) Flash operation complete
15/031/2018 16:31:36 - INFO - OKAY [ 1.028s]
15/031/2018 16:31:36 - INFO - finished. total time: 1.657s
15/031/2018 16:31:36 - INFO - FASTBOOT Output:
target didn't report max-download-size
sending 'boot' (5580 KB)...
(bootloader) USB download speed was 9186kB/s
OKAY [ 0.629s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000148-0x00000179
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.028s]
finished. total time: 1.657s
15/031/2018 16:31:36 - INFO - Please check the log before rebooting into system
15/032/2018 16:32:53 - INFO - Device disconnected
15/040/2018 16:40:18 - INFO - Now plug your device in Fastboot Mode
15/042/2018 16:42:29 - INFO - Failed
Click to expand...
Click to collapse