Related
Hi Guys,
So i bought a second hand XZ(C6603) as an upgrade from my XS. The previous owner told me he had unlocked the bootloader and then again relocked it(he used the BLU function in flashtool). Yesterday i wanted to unlock it again but somehow i cant get it unlocked anymore. In the service menu it says: "Bootloader unlock allowed" YES meaning i can unlock it.
I've used flashtool and adb both with the same result:
14/055/2013 22:55:31 - INFO - Device connected in fastboot mode
14/055/2013 22:55:36 - INFO - Unlocking phone using key XXXXXXXXXXXXXXXXXX
14/055/2013 22:55:36 - INFO - ...
14/055/2013 22:55:36 - INFO - FAILED (remote: Command did not succeed)
14/055/2013 22:55:36 - INFO - finished. total time: 0.035s
XXXXXXXXXXXXXXXXXX= the unlock code i got from Sony
I've all ready tried whiping & reflashing it with the flashtool(.423 frimware) and also repaired it with PC companion but after that i still get the same results
Anyone got some advise for me? Could it be a driver related isue(btw i'm on win 7 64)?
Are you sure you correctly type the key? I also was in this situation, but after ctrl+c/ctrl+v the code more accurate the unlocking went ok...
Try to reinstall fastboot drivers
Bairei said:
Are you sure you correctly type the key? I also was in this situation, but after ctrl+c/ctrl+v the code more accurate the unlocking went ok...
Try to reinstall fastboot drivers
Click to expand...
Click to collapse
Yes is deffintly the correct key. I typed it and i copied/pasted it but still with the same result. I going to uninstall all sony software/flashtool from my computer tonight and start over again.
Try all caps.
...Sent from Zed
XperienceD said:
Try all caps.
...Sent from Zed
Click to expand...
Click to collapse
Tried it but still same result
kistigun said:
Tried it but still same result
Click to expand...
Click to collapse
Do you have any branding on the phone from your carrier, are you sure rooting hasn't changed status to yes by accident.
Are your drivers correctly installed (load up flashtool and connect your phone in fastboot and it will say device connecter in fastboot)
Sent from my C6603 using xda premium
Maddhouse said:
Do you have any branding on the phone from your carrier, are you sure rooting hasn't changed status to yes by accident.
Are your drivers correctly installed (load up flashtool and connect your phone in fastboot and it will say device connecter in fastboot)
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Dont have any branding. I uninstalled all sony software & flashtool from my computer. Reinstalled the flashtool & drivers but still no luck:
15/008/2013 18:08:55 - INFO - Please connect your device into flashmode.
15/009/2013 18:09:06 - INFO - Device connected in flash mode
15/009/2013 18:09:07 - INFO - Opening device for R/W
15/009/2013 18:09:07 - INFO - Reading device information
15/009/2013 18:09:07 - INFO - Phone ready for flashmode operations.
15/009/2013 18:09:07 - INFO - Current device : C6603 - CB5A1PZ0TV - 1270-4975_R3B - 1269-5309_10.3.A.0.423 - GLOBAL-LTE_10.3.A.0.423
15/009/2013 18:09:07 - INFO - Processing loader
15/009/2013 18:09:07 - INFO - Checking header
15/009/2013 18:09:07 - INFO - Flashing data
15/009/2013 18:09:07 - INFO - Loader : S1_Root_5ca3 - Version : APQ8064_30 / Bootloader status : ROOTABLE
15/009/2013 18:09:07 - INFO - Start Reading unit 000008B2
15/009/2013 18:09:07 - INFO - Reading TA finished.
15/009/2013 18:09:07 - INFO - Ending flash session
15/009/2013 18:09:07 - INFO - Now unplug your device and restart it into fastbootmode
15/009/2013 18:09:08 - INFO - Device connected in flash mode
15/009/2013 18:09:08 - INFO - Device disconnected
15/009/2013 18:09:12 - INFO - Device connected in flash mode
15/009/2013 18:09:12 - INFO - Device disconnected
15/009/2013 18:09:17 - INFO - Device connected in fastboot mode
15/010/2013 18:10:19 - INFO - Unlocking phone using key XXXXXXXXXXXXXXXX
15/010/2013 18:10:19 - INFO - ...
15/010/2013 18:10:19 - INFO - FAILED (remote: Command did not succeed)
15/010/2013 18:10:19 - INFO - finished. total time: 0.035s
Maddhouse said:
Do you have any branding on the phone from your carrier, are you sure rooting hasn't changed status to yes by accident.
Click to expand...
Click to collapse
This is a common occurrence @kistigun so it could be just that (although it doesn't allow unlockable Phones to be unlocked unfortunately), but as you were informed it has been unlocked before you shouldn't be having any issues. Have you tried doing it manually using command prompts?
XperienceD said:
This is a common occurrence @kistigun so it could be just that (although it doesn't allow unlockable Phones to be unlocked unfortunately), but as you were informed it has been unlocked before you shouldn't be having any issues. Have you tried doing it manually using command prompts?
Click to expand...
Click to collapse
Also tried it with command prompts but with the same result
If it's locked by any way, is there any way to unlock it again?
kistigun said:
If it's locked by any way, is there any way to unlock it again?
Click to expand...
Click to collapse
You should just be able to do it the same way I would have thought, are you sure you're just not seeing the wood for the trees perhaps? And have you backed up your TA Partition before trying btw?
XperienceD said:
Bootloader Unlocking & CWM;
[Tutorial] Xperia Z & ZL Bootloader Unlocking/Relocking
[Locked Bootloader]CWM recovery 6.0.2.8 for locked bootloaders v4[25-03]
[XZDualRecovery][v2.3 RELEASE] cwm 6.0.3.2 & twrp 2.5.0.0 [locked bootloader]
[TOOL][Z/ZL/ZQ] Backup TA v8.6 for Windows
[Tutorial] Backup You TA Partition To Keep Your Drm Keys before unlocking
Click to expand...
Click to collapse
kistigun said:
Also tried it with command prompts but with the same result
If it's locked by any way, is there any way to unlock it again?
Click to expand...
Click to collapse
the key is case sensitive ..
fish droid said:
the key is case sensitive ..
Click to expand...
Click to collapse
Yeah i know that is/was not the problem
XperienceD said:
You should just be able to do it the same way I would have thought, are you sure you're just not seeing the wood for the trees perhaps? And have you backed up your TA Partition before trying btw?
Click to expand...
Click to collapse
Pff, finaly got i unlocked! Found a German forum where someone had the same problem:
http://www.android-hilfe.de/root-custom-roms-modding-fuer-sony-xperia-z/380742-xperia-z-root-bootloader-unlock-anleitung-23.html
Had to create a folder in flashtool/custom with my XZ serial code as name. In the folder i created a text file named ulcode.txt in text file i've put the unlock code i got from Sony after that it unlocked!
Thanks guys for the advice! For now i'm going to flash the sh*t out of my XZ
i have the same problem, but I have no solutions
Didn't think that your bootloaders are unlockable?
Sent from my SGP321 using xda app-developers app
in serivce menu i have rooting status on bootloader unlock allowed:yes
sorry for my bad bad english
tobyax said:
in serivce menu i have rooting status on bootloader unlock allowed:yes
sorry for my bad bad english
Click to expand...
Click to collapse
Are you sure your drivers a correctly installed Toby? Have you tried the command prompt way?
What version on XZ do you have C66??
Sent from my C6603 using xda premium
i have tried prompt way and flashtool on windows and flashtool on mac, all same error FAILED (remote: Command did not succeed)
this is my device : C6603 - BX903GQ6KF - 1270-3964_R3B - 1269-5309_10.3.1.A.0.244 - GLOBAL-LTE_10.3.1.A.0.244
Android version : 4.2.2 / kernel version : 3.4.0-g3865184 / Build number : 10.3.1.A.0.244
no one can help me
tobyax said:
no one can help me
Click to expand...
Click to collapse
If you have tried command prompt way and you are 100% sure drivers are installed then you have a locked bootloader
Sent from my C6603 using xda premium
At the end I did it with flashtool ... I do not know why it does not work first time.....
Hey All¡¡
Im new here and i just want to ask if someboy can tell me something about unlocking my xperia`s bootloader. I tried to do it throught sony`s guide but in the first step in my soft info was : "Unlock bootloader allowed: no" or something like that. Any ideas?
I have JB 4.3 flashed for my country downloaded from another thread for Spain. Thank you
If the status is 'Bootloader unlock allowed : No', then you can’t unlock it. There's no way around it.
Sent from my C6603 using Tapatalk
Other?..
kingvortex said:
If the status is 'Bootloader unlock allowed : No', then you can’t unlock it. There's no way around it.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
And there is no other method to do that? Maybe flashing an old version or something? I mean, want to root it and install cyanogenmod or another rom . Thanks
No. When I said there was no way around it, I meant it.
Sent from my C6603 using Tapatalk
Marc19c said:
And there is no other method to do that? Maybe flashing an old version or something? I mean, want to root it and install cyanogenmod or another rom . Thanks
Click to expand...
Click to collapse
you can't flash custom kernel for (cm, aosp, aokp, pac, omni, pa) roms to work if you cannot unlock the bootloader, that means only stock based custom rom can only get flashed on your device.
Error unlock: FAILED (remote: Command did not succeed)
Hello. Help me, please.
I can´t unlock my zperia Z 6602. "Unlock bootloader allowed: yes"
ERROR:
07/030/2014 23:30:22 - INFO - Device disconnected
07/030/2014 23:30:29 - INFO - Device connected in flash mode
07/030/2014 23:30:30 - INFO - Opening device for R/W
07/030/2014 23:30:30 - INFO - Reading device information
07/030/2014 23:30:30 - INFO - Phone ready for flashmode operations.
07/030/2014 23:30:30 - INFO - Current device : C6602 - BX903J7MKA - 1270-5691_R3C - 1269-5309_10.4.B.0.569 - GLOBAL-HSPA_10.4.B.0.569
07/030/2014 23:30:30 - INFO - Processing loader
07/030/2014 23:30:30 - INFO - Checking header
07/030/2014 23:30:30 - INFO - Flashing data
07/030/2014 23:30:30 - INFO - Loader : S1_Root_5ca3 - Version : APQ8064_30 / Bootloader status : ROOTABLE
07/030/2014 23:30:30 - INFO - Start Reading unit 000008B2
07/030/2014 23:30:30 - INFO - Reading TA finished.
07/030/2014 23:30:30 - INFO - Ending flash session
07/030/2014 23:30:30 - INFO - Now unplug your device and restart it into fastbootmode
07/030/2014 23:30:30 - INFO - Device connected in flash mode
07/030/2014 23:30:31 - INFO - Device disconnected
07/030/2014 23:30:35 - INFO - Device connected in flash mode
07/031/2014 23:31:25 - INFO - Device disconnected
07/031/2014 23:31:32 - INFO - Device connected in fastboot mode
07/031/2014 23:31:56 - INFO - Unlocking phone using key XXXXXXXXXXXXXX
07/031/2014 23:31:56 - INFO - ...
07/031/2014 23:31:56 - INFO - FAILED (remote: Command did not succeed)
07/031/2014 23:31:56 - INFO - finished. total time: 0.035s
PLEASE HELP ME!!! THANKS!!!!
hi everyone
i have a xperia sp c5303 and this information you need to know:
1) unlocked bootloader
2) i had Mahdi Rom ver 2.7
3) williams kernel v42
now my problem
my phone suddenly restart and stop on boot loop
then i try to flash with flash tools and i notice it's not work for the first time because i flash sevral time my phone and others
then try fast boot and not work again
then start search and realize my phone had hard break or soft break ( i cant realize diff between two )
now that's interesting because my battery level is so low and i need to wall charge for hours to get the green ( when connect to charger sony arm show and red led on and 3 sec later black screen and red led off . 2 hours later red les startin on and 30min laters turn to green and on my phone show battery level of full )
but when i want to flash for 10 sec battery die and flash give me nothing
24/051/2014 12:51:15 - INFO - Selected Bundle for Xperia SP(C5303). FW release : 12.0.A.2.266. Customization : Middle East
24/051/2014 12:51:15 - INFO - Preparing files for flashing
24/051/2014 12:51:28 - INFO - Please connect your device into flashmode.
24/051/2014 12:51:30 - INFO - Device connected in flash mode
24/051/2014 12:51:30 - INFO - Opening device for R/W
24/051/2014 12:51:30 - INFO - Reading device information
24/051/2014 12:51:31 - INFO - Phone ready for flashmode operations.
24/051/2014 12:51:31 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
24/051/2014 12:51:31 - INFO - Start Flashing
24/051/2014 12:51:31 - INFO - Processing loader.sin
24/051/2014 12:51:31 - INFO - Checking header
24/051/2014 12:51:31 - INFO - Flashing data
24/051/2014 12:51:31 - INFO - Processing of loader.sin finished.
24/051/2014 12:51:32 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
24/053/2014 12:53:48 - INFO - Ending flash session
and then nothing happen and my phone led on the flash mode goes off and battery die and i try to start again of begining
any suggestion for you guys can help me please ?
if i try oppen the phone by myself ( because i repair laptop ) and change the battery . do you think i can flash again and the error in flash mode because of battery level .
thx
more information about fastboot
when I want to flash kernel (boot.img) with fastboot phone very easily goes to fastboot mode and blue led start and when i want to start flash here goes nothing ( waiting for my phone ) that's weird because program said the phone connected.
although i try to flash kernel with QuikIMG too and the same happens.
need your suggest ...
rayanafshan said:
hi everyone
i have a xperia sp c5303 and this information you need to know:
1) unlocked bootloader
2) i had Mahdi Rom ver 2.7
3) williams kernel v42
now my problem
my phone suddenly restart and stop on boot loop
then i try to flash with flash tools and i notice it's not work for the first time because i flash sevral time my phone and others
then try fast boot and not work again
then start search and realize my phone had hard break or soft break ( i cant realize diff between two )
now that's interesting because my battery level is so low and i need to wall charge for hours to get the green ( when connect to charger sony arm show and red led on and 3 sec later black screen and red led off . 2 hours later red les startin on and 30min laters turn to green and on my phone show battery level of full )
but when i want to flash for 10 sec battery die and flash give me nothing
24/051/2014 12:51:15 - INFO - Selected Bundle for Xperia SP(C5303). FW release : 12.0.A.2.266. Customization : Middle East
24/051/2014 12:51:15 - INFO - Preparing files for flashing
24/051/2014 12:51:28 - INFO - Please connect your device into flashmode.
24/051/2014 12:51:30 - INFO - Device connected in flash mode
24/051/2014 12:51:30 - INFO - Opening device for R/W
24/051/2014 12:51:30 - INFO - Reading device information
24/051/2014 12:51:31 - INFO - Phone ready for flashmode operations.
24/051/2014 12:51:31 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
24/051/2014 12:51:31 - INFO - Start Flashing
24/051/2014 12:51:31 - INFO - Processing loader.sin
24/051/2014 12:51:31 - INFO - Checking header
24/051/2014 12:51:31 - INFO - Flashing data
24/051/2014 12:51:31 - INFO - Processing of loader.sin finished.
24/051/2014 12:51:32 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
24/053/2014 12:53:48 - INFO - Ending flash session
and then nothing happen and my phone led on the flash mode goes off and battery die and i try to start again of begining
any suggestion for you guys can help me please ?
if i try oppen the phone by myself ( because i repair laptop ) and change the battery . do you think i can flash again and the error in flash mode because of battery level .
more information about fastboot
when I want to flash kernel (boot.img) with fastboot phone very easily goes to fastboot mode and blue led start and when i want to start flash here goes nothing ( waiting for my phone ) that's weird because program said the phone connected.
although i try to flash kernel with QuikIMG too and the same happens.
need your suggest ...
thx
Click to expand...
Click to collapse
anyone please...
hey guys . im still waiting ...
Try using a different usb port on your laptop or a different usb cable. Sometimes flashing may fail due to damaged usb port or cable. Also try using the usb cable that sony bundled with your phone (I used LG cable and didnt work for me). If that doesnt work, it seems that your battery is dead.
tj_droid said:
Try using a different usb port on your laptop or a different usb cable. Sometimes flashing may fail due to damaged usb port or cable. Also try using the usb cable that sony bundled with your phone (I used LG cable and didnt work for me). If that doesnt work, it seems that your battery is dead.
Click to expand...
Click to collapse
1) i use my pc and my sony laptop and 3 diffrent cable sony nokia sony
2) i try diffrent usb port such az usb2 and usb3
3) when i try to flash in flashmod with flashtool after
24/051/2014 12:51:15 - INFO - Selected Bundle for Xperia SP(C5303). FW release : 12.0.A.2.266. Customization : Middle East
24/051/2014 12:51:15 - INFO - Preparing files for flashing
24/051/2014 12:51:28 - INFO - Please connect your device into flashmode.
24/051/2014 12:51:30 - INFO - Device connected in flash mode
24/051/2014 12:51:30 - INFO - Opening device for R/W
24/051/2014 12:51:30 - INFO - Reading device information
24/051/2014 12:51:31 - INFO - Phone ready for flashmode operations.
24/051/2014 12:51:31 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
24/051/2014 12:51:31 - INFO - Start Flashing
24/051/2014 12:51:31 - INFO - Processing loader.sin
24/051/2014 12:51:31 - INFO - Checking header
24/051/2014 12:51:31 - INFO - Flashing data
24/051/2014 12:51:31 - INFO - Processing of loader.sin finished.
24/051/2014 12:51:32 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
24/053/2014 12:53:48 - INFO - Ending flash session
this log green led for flash mod turn off ( when i try to flash and connect usb until green led off take 5 sec not more)
4) if my battery dead if replace with new one ... can flash it again?
thx for respond
if my battery dead if replace with new one ... can flash it again?
Hello.
It could help others more if you could describe what happened when you tried to turn on the phone, after the flashmode LED turned off? Thanks.
rayanafshan said:
if my battery dead if replace with new one ... can flash it again?
Click to expand...
Click to collapse
Try locking your bootloader first (If it possible through fastboot). Looking at the errors the flashtool is giving, it seems like the flashing stops because bootloader is unlocked. Even if you read flashtool thread, it says bootloader should be locked (as far as I remember, havent visited the thread since a long time)
TechnoSparks said:
Hello.
It could help others more if you could describe what happened when you tried to turn on the phone, after the flashmode LED turned off? Thanks.
Click to expand...
Click to collapse
battery dead and need recycle again for more hours.
tj_droid said:
Try locking your bootloader first (If it possible through fastboot). Looking at the errors the flashtool is giving, it seems like the flashing stops because bootloader is unlocked. Even if you read flashtool thread, it says bootloader should be locked (as far as I remember, havent visited the thread since a long time)
Click to expand...
Click to collapse
that is actually good idea thx . i'll gonna working on that and let you know for 5-6 hours.
thank you both for respond.
rayanafshan said:
battery dead and need recycle again for more hours.
that is actually good idea thx . i'll gonna working on that and let you know for 5-6 hours.
thank you both for respond.
Click to expand...
Click to collapse
i try and that's result
when i want to relock my phone with flashtool ( because my phone sp 2013 for sony and they said we must do it this way for relock) here it is my log
27/004/2014 21:04:34 - INFO - Device connected in flash mode
27/004/2014 21:04:35 - INFO - Opening device for R/W
27/004/2014 21:04:35 - INFO - Reading device information
27/004/2014 21:04:35 - INFO - Phone ready for flashmode operations.
27/004/2014 21:04:35 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
27/004/2014 21:04:38 - INFO - Processing loader.sin
27/004/2014 21:04:38 - INFO - Checking header
27/004/2014 21:04:38 - INFO - Flashing data
27/004/2014 21:04:38 - INFO - Processing of loader.sin finished.
27/004/2014 21:04:39 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
27/004/2014 21:04:39 - INFO - Start Reading unit 000008B2
27/004/2014 21:04:39 - INFO - Reading TA finished.
and stop and 5 min later when i disconnect the phone this log
27/031/2014 23:31:55 - ERROR - Read error :31 : A device attached to the system is not functioning.
27/031/2014 23:31:55 - INFO - Your phone bootloader cannot be officially unlocked
27/031/2014 23:31:55 - INFO - You can now unplug and restart your phone
and when ii see this i try to use rubber band trick and see this in the morning
28/035/2014 06:35:09 - INFO - Device connected with USB debugging off
28/035/2014 06:35:09 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/035/2014 06:35:10 - INFO - Device disconnected
28/045/2014 06:45:01 - INFO - Device connected in flash mode
28/045/2014 06:45:43 - INFO - Device disconnected
28/049/2014 06:49:14 - INFO - Device connected with USB debugging off
28/049/2014 06:49:14 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/049/2014 06:49:18 - INFO - Device disconnected
28/058/2014 06:58:45 - INFO - Device connected in flash mode
28/059/2014 06:59:28 - INFO - Device disconnected
28/002/2014 07:02:55 - INFO - Device connected with USB debugging off
28/002/2014 07:02:55 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/002/2014 07:02:59 - INFO - Device disconnected
28/012/2014 07:12:26 - INFO - Device connected in flash mode
28/013/2014 07:13:09 - INFO - Device disconnected
28/016/2014 07:16:32 - INFO - Device connected with USB debugging off
28/016/2014 07:16:32 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/016/2014 07:16:36 - INFO - Device disconnected
28/026/2014 07:26:02 - INFO - Device connected in flash mode
28/026/2014 07:26:45 - INFO - Device disconnected
28/030/2014 07:30:08 - INFO - Device connected with USB debugging off
28/030/2014 07:30:08 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/030/2014 07:30:12 - INFO - Device disconnected
28/039/2014 07:39:39 - INFO - Device connected in flash mode
28/040/2014 07:40:21 - INFO - Device disconnected
28/043/2014 07:43:41 - INFO - Device connected with USB debugging off
and this repeat again and again . interesting was i am always active usb debugging mode and now log said is off. i confused here
now my usb debugging off how flash what can i do now .
for unlocked bootloader for flash
i want my phone back
help
Okay the problem is getting worse. Have you tried to unlock your bootloader again? If not, please try so. I have a final option for you to decide.
TechnoSparks said:
Okay the problem is getting worse. Have you tried to unlock your bootloader again? If not, please try so. I have a final option for you to decide.
Click to expand...
Click to collapse
i try several time .
this morning
there is another way to relock bootloader other than flashtool for sp?
if there are other way please.. or if any way to back my phone .
rayanafshan said:
i try several time .
this morning
there is another way to relock bootloader other than flashtool for sp?
if there are other way please.. or if any way to back my phone .
Click to expand...
Click to collapse
Please understand my posts correctly. Are you currently on an unlocked bootloader? Or if you can confirm it is locked, do you manage to be able to unlock the bootloader through the Flashtool?
TechnoSparks said:
Please understand my posts correctly. Are you currently on an unlocked bootloader? Or if you can confirm it is locked, do you manage to be able to unlock the bootloader through the Flashtool?
Click to expand...
Click to collapse
ohhh ok i get wrong . now i found you mean i unlocked bootloader however it is unlocked. ok i try and ley your know
rayanafshan said:
ohhh ok i get wrong . now i found you mean i unlocked bootloader however it is unlocked. ok i try and ley your know
Click to expand...
Click to collapse
hi again
now result
in 2days i try evrything
1- i try to unlocked again with fastboot but fastboot said you unlocked bootloader before and then finished
2- try to unlocked bootloader with flashtool with the final version and when said connect your phone with flashmode and i did it then said pick your model phone and i select xperia sp and green led turn off ang didnt enything
i unlocked bootloader before many time and now i'm stuck
if there is another way please let me know?
rayanafshan said:
hi again
now result
in 2days i try evrything
1- i try to unlocked again with fastboot but fastboot said you unlocked bootloader before and then finished
2- try to unlocked bootloader with flashtool with the final version and when said connect your phone with flashmode and i did it then said pick your model phone and i select xperia sp and green led turn off ang didnt enything
i unlocked bootloader before many time and now i'm stuck
if there is another way please let me know?
Click to expand...
Click to collapse
I can't really help if I don't know the current state of your bootloader
Your last option here is to retry flashing a stock ROM FTF onto your phone. I hope it will work. [Choose your desired stock ROM based on your XSP model here]
TechnoSparks said:
I can't really help if I don't know the current state of your bootloader
Your last option here is to retry flashing a stock ROM FTF onto your phone. I hope it will work. [Choose your desired stock ROM based on your XSP model here]
Click to expand...
Click to collapse
I really do not understand what you asking from me
if you want to know about my bootloader : is 100% unlocked and when i try to unlocked again it's said you bootloader unloacked if you need i posted log from fastboot here
also i try more than 100 times to flash with stock ftf of my phone and also flash kernel stock and flash recovery for unlocked and locked bootloader . i try everything in this froum and others
i dont know why when i want to flash kernel ( stock and cm) is stuck on
flashing...
and blue led is on untill battery dead and myphone not respond to program
i posted logs before
here situation of my phone
xperia sp xx03
bootloader unlocked
android 4.4.4 mahdi version 2.8
recovery cm11_williams_kernel_v4
evrything start of here 3 weeks ago
((my phone restart and when i far from my phone , it stucked on boot logo animation for 3 or 4 hours and when i found my phone situation shutdown my phone via the OFF botton of the back of my phone.))
and then i try to flash FTF stock or CM from MahdiRom or any rom , did not let me. and you know others untill now ?
I research and i Think the only way is from Fastboot mode and fstboot program with terminal function .
can you undrestand my problem know please?
rayanafshan said:
I really do not understand what you asking from me
if you want to know about my bootloader : is 100% unlocked and when i try to unlocked again it's said you bootloader unloacked if you need i posted log from fastboot here
also i try more than 100 times to flash with stock ftf of my phone and also flash kernel stock and flash recovery for unlocked and locked bootloader . i try everything in this froum and others
i dont know why when i want to flash kernel ( stock and cm) is stuck on
flashing...
and blue led is on untill battery dead and myphone not respond to program
i posted logs before
here situation of my phone
xperia sp xx03
bootloader unlocked
android 4.4.4 mahdi version 2.8
recovery cm11_williams_kernel_v4
evrything start of here 3 weeks ago
((my phone restart and when i far from my phone , it stucked on boot logo animation for 3 or 4 hours and when i found my phone situation shutdown my phone via the OFF botton of the back of my phone.))
and then i try to flash FTF stock or CM from MahdiRom or any rom , did not let me. and you know others untill now ?
I research and i Think the only way is from Fastboot mode and fstboot program with terminal function .
can you undrestand my problem know please?
Click to expand...
Click to collapse
My intention or objective right now is to have you successfully boot up your phone and restore it without relying on flashtool so much.
Since you said your bootloader is unlocked, you'll now left to flash DoomLord's advanced kernel that will give you recovery access.
Because my understanding is limited, based on your posts earlier, it seemed you indeed tried to flash a kernel via fastboot but your phone died. Based on multiple logs, there are also multiple errors that seemed to be involving hardware. And due to that kind of advanced log error I must apologise and tell you that I am now unable to help you.
Your log listed so many errors, it even unable to detect the model number of your phone, nor the current state of your bootloader (on newer posts).
If you wish to try my last suggestion, do said so. Otherwise, I have to back myself out of this since it is not my expertise.
I am very sorry
TechnoSparks said:
My intention or objective right now is to have you successfully boot up your phone and restore it without relying on flashtool so much.
Since you said your bootloader is unlocked, you'll now left to flash DoomLord's advanced kernel that will give you recovery access.
Because my understanding is limited, based on your posts earlier, it seemed you indeed tried to flash a kernel via fastboot but your phone died. Based on multiple logs, there are also multiple errors that seemed to be involving hardware. And due to that kind of advanced log error I must apologise and tell you that I am now unable to help you.
Your log listed so many errors, it even unable to detect the model number of your phone, nor the current state of your bootloader (on newer posts).
If you wish to try my last suggestion, do said so. Otherwise, I have to back myself out of this since it is not my expertise.
I am very sorry
Click to expand...
Click to collapse
i know that situation is sucks i know and thank you for helping me to this step and i'm so much own you.
but last question i found a post for fastboot unbricked my type of phone but i dont undrestand small part of it and maybe it's help others
boot.img -The main kernel and initrd
recovery.img -A 'backup' kernel, initrd, and OS 4 sysm recovery/maintanance
sytem.img -The main OS
userdata.img -User data and settings
splash.img -Has Boot image. can be splash1 as well.
cache.img -Temp storage
...there can be similar partition names depends on your device type.... but basically these 6 partitions constitute a ROM. Copy all of (6) files to .android folder. (Henceforth, we can use this recovery.img as stock recovery for your device.)
"As your device is bricked/corrupted, we need to erase all old Partitions and flash (rewrite) new partitions that we have extracted from Update zip and placed in .android."
(1) Lets erase all partitions first (one by one)using: fastboot erase <partition>
Quote
C:\.android>fastboot erase system
Successful
C:\.android>fastboot erase recovery
Successful
C:\.android>fastboot erase boot
Successful
C:\.android>fastboot erase userdata
Successful
C:\.android>fastboot erase splash
Successful
C:\.android>fastboot erase cache
Successful
(2) Continuing with Flashing new partions using the Images copied in .android:
Command: fastboot flash <partition> <partition_name.img>
Quote
C:\.android>fastboot flash boot boot.img
Successful
C:\.android>fastboot flash recovery recovery.img
Successful
C:\.android>fastboot flash system system.img here people gen. get stuck
Successful
C:\.android>fastboot flash userdata userdata.img
Successful
C:\.android>fastboot flash splash splash.img
Successful
C:\.android>fastboot reboot
If all successful, Your phone will update and automatically reboot into the Factory State. Cheers !!!
...If you are Unable to flash 'system.img' successfully...
Reason: Your device is not allowing to format and rewrite 'system' partition manually. If your device is Rooted then probably such failure will never occur.
Let's overcome this Issue as well...Try Following...
First, Understand current State of Device...
We Wiped out old partitions and Flashed new partitions except :-\ system :-\ So No System on your Device at present.
What we will do now..
We will now wipe all partitions again
We will then flash only recovery.img saved in .android folder
We will use update.zip saved in .android folder to Flash it using SD Card.
We will copy update.zip on SD Card (using adb). If you can do it manually using a card reader skip step-II in below process.
Step-I: Wiping 'partitions' and Flashing 'recovery.img':Let's wipe all partitions again:
Quote
C:\.android>fastboot -w
C:\.android>fastboot reboot-bootloader
C:\.android>fastboot flash recovery recovery.img
C:\.android>reboot
Step-II: Copy update.zip on SDCARD
Quote
C:\.android>adb push update.zip /data/sdcard
(Let the process complete. It will take damm much more time !!!)
Once you get 'Successful' message..your update.zip is on your SDCARD. If this is tidious then get a Card reader and copy Update.zip to SD Card directly and replace in Device.
Step-III: As you can't manage to see what is happening on screen(No Display) hence Don't do mistakes here, read carefully and follow exactly:
1.Reboot Device into Recovery Mode:
On cmd type:
Quote
C:\.android>adb reboot recovery
2.Now Press 'Volume(-)' button ONCE. (Once means 'once only'-if you did mistake here repeat the Step-III)
3.Press 'Power' Button TWICEand Leave you Device for some 10 Minutes time.
If phone don't get alive in 10 Minutes Repeat Step-III again.
You may not able to see but Your phone will update and automatically reboot into the Factory State. Cheers !!!
Explaining Last Step:
We used simple logic in last procedure/ Its nothing but updating using Recovery Mode. Always remember Custom Recovery of Micromax A56/57 has following options: (May be diferent for other devics)
1. Reboot device
2. Apply Update.Zip from SDCARD
3. Wipe userdata on device/Factory Update
4. Wipe Cache on Device
As the default curser in recovery UI remains on Option-1 and we needed to choose Option-2.
Hence to select "Apply update for sdcard" we pressed 'Vol(-)' ONCE and then to Confirm and execute that option Tapped 'POWER' button TWICE.
Hope this Guide helped you or ...will Help you to help others !!!
Click to expand...
Click to collapse
i want to know where i found update.zip or recovery.img sytem.img userdata.img splash.img cache.img because in stock rom sp they are .sin
if i wipe my all partition maybe i have chance to restore my phone
thank you
Hi, guys. Try to unlock my xperia sp, but flashtool says FAILED. What is the problem and what i need to do? Help, please
INFO - Device connected in fastboot mode
INFO - Unlocking phone using key EB35EC91061C376C
INFO - ...
INFO - (bootloader) Unlock phone requested
INFO - FAILED (remote: oem unlock failed!)
INFO - finished. total time: 0.066s
P.S.: drivers already installed without any problems, imei - first 14 symbols, flashtool version 0.9.19.10, firewall and eset offs
makzze said:
Hi, guys. Try to unlock my xperia sp, but flashtool says FAILED. What is the problem and what i need to do? Help, please
INFO - Device connected in fastboot mode
INFO - Unlocking phone using key EB35EC91061C376C
INFO - ...
INFO - (bootloader) Unlock phone requested
INFO - FAILED (remote: oem unlock failed!)
INFO - finished. total time: 0.066s
P.S.: drivers already installed without any problems, imei - first 14 symbols, flashtool version 0.9.19.10, firewall and eset offs
Click to expand...
Click to collapse
I used fastboot method in android sdk folder (the one suggested in unlock topic and sony page) without flashtool software, however are you sure all drivers are installed? (in my case, the S1 fastboot drivers wasn't correctly installed/operative). What system do you have? with 8, 8.1, 10 you should disable driver signature (hold shift then restart) and reinstall flashtools drivers.
Why do you used only first 14 digits? (In my case, all imei numbers worked)
Good day. Please assist me in solving bleeding problem.
I have unlocked bootloader unbranded device C6903.
Some time ago, I used EMMA(sony flashtool) to update it to 14.6.A.1.236
(Service Name: C6903 14.6.A.1.236 Customized_NCB 1276-9897 R2D User-Live COM)
Today, I try to downgrade to 14.6.A.0.368 using same sony flashtool.
After this, l a got booting animation forever.
I restarted few times. Tries to flash cyanogen, tries services from EMMA.
Now I have boot loop, no animation, no nothing, only vibrates once when press power.
fasboot and flash mode a working, but reflashind don't do anything.
When connected to dockstation - screen blinking with sony logo, shutdown, blink, shutdown.
Is issue can caused by some invalid drm keys that gotten by mistake to my phone?
Will be grateful for any help.
Thanks.
Use Flashtool of Androxyde. Never Use EMMA for such things. EMMA just sucks rly bad and is only useful for very specific things. Everything else towards flashing, belongs to Flashtool.
Flashing different firmwares with flashtool don't make any difference.
A even try to relock bootloader and use sony companion to restore device - no luck.
Update, I flashed boot.img from custom rom and now I have 3 times red light blinking when power on.
Update.
I was trying to use this guide https://forum.xda-developers.com/showthread.php?t=2646405
When flashing s1tool give me the message
Code:
MINOR ERROR [ Open_TA_failed, err: 001D ]
After this all the same.
When connect phone to dockstation it just blinking the screen. Is it possible to be battery issue?
full log
Code:
Welcome to S1 tool.
That is small and crippled subset of SETOOL2 service tool.
SELECT FIRMWARE PACKAGES
YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
CHECKING PACKAGES ...
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
will use Sahara protocol ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
PROCESSING ...
SERIAL NUMBER : 48CC8901
HARDWARE ID : 04000100E1007B00
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
Emergency loader uploaded ...
RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: 0004
DEVICE ID: 0189CC48
FLASH ID: "0011/01000010"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
WRITING PACKAGES ...
Processing package
C:\Home\Downloads\C6903\14_2_A_0_290.APP_SW_Honami_GENERIC_1272_6084_S1_SW_LIVE_6732_PID1_0005_MMC.SIN_FILE_SET
WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_LA1.04_15
PARSING: "DEVELOPMENT"
value OTP_LOCK_STATUS_1 : UNLOCKED, not match LOCKED
PARSING: "TEST_OEM0_007B00E1"
value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
value OTP_DATA_1 : 00000100, not match 01000400
value IDCODE_1 : 007B00E1, match 007B00E1
PARSING: "PRECOMMERCIAL_007B00E1"
value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
value OTP_DATA_1 : 01000400, match 01000400
value IDCODE_1 : 007B00E1, match 007B00E1
PROCESSING : dbi_S1_Boot_MSM8974_LA1_04_15_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
PROCESSING : emmc_appsboot_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : s1sbl_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : sbl1_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : tz_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : Honami_S1BootConfig_MiscTA_130115_1430.ta
MINOR ERROR [ Open_TA_failed, err: 001D ]
BOOT UPDATED
Processing ACPU files
PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
no update files in package
FINISHED
Elapsed:128 secs.
Problem solved by flashing C6903_14.1.G.2.257_Global LTE.ftf
Thanks.
Nyakov said:
Problem solved by flashing C6903_14.1.G.2.257_Global LTE.ftf
Thanks.
Click to expand...
Click to collapse
Device began to charge, but still not boot.
When I try to flash AOSP
I cannot write recovery, get:
Code:
fastboot -S 256M flash recovery recovery.img
sending 'recovery' (14152 KB)...
OKAY [ 0.460s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.463s
Have you solved the issue. My phone C6903 is struck in bootloop in 4.2.2
I have unknown baseband issue.