I've try update my software with OTA and PC Companion before and it said error. Then I tried to flash 292 FTF using flashtool 0.9.18.4 and this error keep showing.
07/001/2015 03:01:51 - INFO - Phone boot version : S1_Boot_Lagan_1.0_2. Boot delivery version : S1_Boot_Lagan_1.1.1_1
07/001/2015 03:01:51 - INFO - Going to flash boot delivery
07/001/2015 03:01:51 - INFO - Processing emmc_appsboot_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin
07/001/2015 03:01:51 - INFO - Checking header
07/001/2015 03:01:51 - ERROR - Processing of emmc_appsboot_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin finished with errors.
07/001/2015 03:01:51 - INFO - Ending flash session
07/001/2015 03:01:51 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80080021 ";
Click to expand...
Click to collapse
I've checked *#*#7378423#*#* and bootloader unlocked is yes
Please solve this error for me
Thank you!
And I've spend 2 days searching, it's not much but I think I can't do anything to solve this problem.
hacphongthan said:
I've try update my software with OTA and PC Companion before and it said error. Then I tried to flash 292 FTF using flashtool 0.9.18.4 and this error keep showing.
I've checked *#*#7378423#*#* and bootloader unlocked is yes
Please solve this error for me
Thank you!
And I've spend 2 days searching, it's not much but I think I can't do anything to solve this problem.
Click to expand...
Click to collapse
Why you're using flashtool instead of fastboot if your bootloader is unlocked either way?
You can try to flash Lollipop 5.0.x ROM : PABX's ROM YUGA 5.0
The instructions are written in the page, but before that you need to download android SDK.
After you will be done that either, you will need to go /sdk/platform-tools/ (where fastboot.exe and adb.exe are installed), then with holding SHIFT button press Right Mous Button and push "Open command prompt here". And then just write the commands which are written in the page, again.
And don't forget to install adb and fastboot drivers.
LaurynasVP said:
Why you're using flashtool instead of fastboot if your bootloader is unlocked either way?
The instructions are written in the page, but before that you need to download android SDK.
After you will be done that either, you will need to go /sdk/platform-tools/ (where fastboot.exe and adb.exe are installed), then with holding SHIFT button press Right Mous Button and push "Open command prompt here". And then just write the commands which are written in the page, again.
And don't forget to install adb and fastboot drivers.
Click to expand...
Click to collapse
So my phone bootlocker has been unlocked right ?
Can I do anything to relock it?
I don't have old TA partition because I've bought an used phone and I just want to use stock ROM
hacphongthan said:
So my phone bootlocker has been unlocked right ?
Can I do anything to relock it?
I don't have old TA partition because I've bought an used phone and I just want to use stock ROM
Click to expand...
Click to collapse
If via *#*#7378423#*#* shows, that status is : "Bootloader unlockED: YES", then yes, your bootloader is unlocked and your DRM keys have been erased permanently, without any way of getting them back (if you don't have TA-Partition backup, of course). If status is : "Bootloader unlock ALLOWED: Yes", then your bootloader isn't unlocked and yours DRM keys is in their "place".
If your bootloader unlocked, then you could ask the person you have bought your phone from for TA-Partition backup, if he/she has it.
If not - don't ever think to flash anyone else's Ta-Partition, otherwise you'll brick your phone permanently.
You can relock it via Flashtool, If I'm right. But it doesn't change the situation you're in, 'cause your DRM keys are lost and you'll not be able to use BE2, Clear Audio+ and other fuctions, which requires the DRM keys to be working.
I'm sorry about that.
You can still flash stock .FTF, I suggest you to flash Generic.
If error persists, you could try other .ftf to fry for flashing.
LaurynasVP said:
If via *#*#7378423#*#* shows, that status is : "Bootloader unlockED: YES", then yes, your bootloader is unlocked and your DRM keys have been erased permanently, without any way of getting them back (if you don't have TA-Partition backup, of course). If status is : "Bootloader unlock ALLOWED: Yes", then your bootloader isn't unlocked and yours DRM keys is in their "place".
If your bootloader unlocked, then you could ask the person you have bought your phone from for TA-Partition backup, if he/she has it.
If not - don't ever think to flash anyone else's Ta-Partition, otherwise you'll brick your phone permanently.
You can relock it via Flashtool, If I'm right. But it doesn't change the situation you're in, 'cause your DRM keys are lost and you'll not be able to use BE2, Clear Audio+ and other fuctions, which requires the DRM keys to be working.
I'm sorry about that.
You can still flash stock .FTF, I suggest you to flash Generic.
If error persists, you could try other .ftf to fry for flashing.
Click to expand...
Click to collapse
It's show me Bootloader unlock allowed: Yes. I've flash C6603_10.5.1.A.0.292_Generic_NCB.ftf for my device but it show the above error.
Then I flash C6603_10.1.1.A.1.307_Generic BE.ftf it's all right nothing error.
Both of them are GENERIC but the 292 ftf error.
Could you please help suggest me which 292 ftf not error on my device.
And one more thing strange, I can't update my device with OTA even on 307 TFT. Someone say it only happen if my bootloader unlocked
I just tried C6603_10.5.1.A.0.292_Generic_UK.ftf too but it still error
The fact is I can't only flash which FTF include S1_Boot_Lagan_1.0_2 that mean I can't update my S1_Boot ?
hacphongthan said:
It's show me Bootloader unlock allowed: Yes. I've flash C6603_10.5.1.A.0.292_Generic_NCB.ftf for my device but it show the above error.
Then I flash C6603_10.1.1.A.1.307_Generic BE.ftf it's all right nothing error.
Both of them are GENERIC but the 292 ftf error.
Could you please help suggest me which 292 ftf not error on my device.
And one more thing strange, I can't update my device with OTA even on 307 TFT. Someone say it only happen if my bootloader unlocked
I just tried C6603_10.5.1.A.0.292_Generic_UK.ftf too but it still error
The fact is I can't only flash which FTF include S1_Boot_Lagan_1.0_2 that mean I can't update my S1_Boot ?
Click to expand...
Click to collapse
Well, you've not unlocked your bootloader. Your bootloader status is locked. However, do you have flashtool drivers? You could give a try on another pc, maybe your pc is causing issues, like mine (my os is Windows 10 and doesn't support fastboot and adb, as I can see).
LaurynasVP said:
Well, you've not unlocked your bootloader. Your bootloader status is locked. However, do you have flashtool drivers? You could give a try on another pc, maybe your pc is causing issues, like mine (my os is Windows 10 and doesn't support fastboot and adb, as I can see).
Click to expand...
Click to collapse
Yes I have flash tool driver on windows 7 Vmware but it error same my Windows 8 main PC :crying:.
Talk about OTA, why I can't update via OTA or PC companion
hacphongthan said:
Yes I have flash tool driver on windows 7 Vmware but it error same my Windows 8 main PC :crying:.
Talk about OTA, why I can't update via OTA or PC companion
Click to expand...
Click to collapse
I don't know anything else whast I could suggest you. U should better contact SONY:
Sony Support. Or if you have warranty - take it to there
LaurynasVP said:
I don't know anything else whast I could suggest you. U should better contact SONY:
Sony Support. Or if you have warranty - take it to there
Click to expand...
Click to collapse
oh ok thanks for your help
Related
Hi Guys,
i have some problem, this is my story:
after unlocking the bootloader without any problem i decided to root, but some reason i get superuser app but root explorer dont worked and no answer for it for superuser access, nothing.. like the root was dummy..
after i tryed to flash stock kernel with recovery for unlocked bootloader (for do the root via Recovery) but nothing adb say me <waiting for the device>... not knowing what to do and why this problem i thinked maybe the XZ is not still with unloked bootloader and i try another time to unlocked it.. result the XZ now is in bootloop
i tryng to relock the bootloader (this was ok) and flash the stock firmware with flashtool...
apparently i dont go in flashmode because no led green appear, but flashtool say me im in flashmode...
but i get this log:
16/059/2013 20:59:27 - INFO - <- This level is successfully initialized
16/059/2013 20:59:27 - INFO - Flashtool Version 0.9.10.2beta built on 2013-03-15 09:11:22
16/059/2013 20:59:34 - INFO - Device disconnected
16/059/2013 20:59:44 - INFO - Device connected in flash mode
16/059/2013 20:59:52 - INFO - Selected C6603 / Generic Uk / Non
16/059/2013 20:59:52 - INFO - Please connect your device into flashmode.
16/059/2013 20:59:52 - INFO - Preparing files for flashing
16/000/2013 21:00:45 - INFO - Device disconnected
16/001/2013 21:01:08 - INFO - Flash canceled
the flash stuck in "Preparing files for flashing"
i dont know why
I revived the XZ with SUS (Is Italian No brand) but this is my situation:
My rooting status (my bootloader) is unknown (before was unlockable) and i cant flash with Flashtool beta because i get the stuck on "Preparing files for flashing".
I would like to unlock my XZ another time to rooting and flashing recovery and cooked rom..
What should I do to make it?
Thanks
EDIT:
Ok, for the problem "the flash stuck in Preparing files for flashing" i solve with this operation http://forum.xda-developers.com/showpost.php?p=39256827&postcount=138
Now i flashed the firmware with flashtool.. but my bootloader still unknown (before relock was unlockable) why the flash dont fix it?
what i must to do for have back bootloader unlockable?
Ok, for the problem "the flash stuck in Preparing files for flashing" i solve with this operation http://forum.xda-developers.com/showpost.php?p=39256827&postcount=138
This is my situation now:
i relock the bootloader with flashtol and flashed the firmware.. my bootloader before lock it was unlockable, after relock and flash firmware is unknown why the flash dont fix it?
i tryed also rooting, after this become NO, i tryed this fix http://forum.xda-developers.com/showpost.php?p=39178406&postcount=96 but not came back to YES but is still another time
to unknown
what i must to do for have back bootloader unlockable?
Please someone Help me
Thanks
For For those who have my problem here http://forum.xda-developers.com/showpost.php?p=39338155&postcount=178 the solutions :good::laugh:
tanoxxx said:
For For those who have my problem here http://forum.xda-developers.com/showpost.php?p=39338155&postcount=178 the solutions :good::laugh:
Click to expand...
Click to collapse
Hi,
I'm having the same problem with the "Rooting status: unknown".
I can't flash kernel (via Flashtools) and can't unlock (via android fastboot).
Unfortunately the file posted in the solution you mentioned is unavailable.
Can you tell me how you proceed to fix it?
Thank you very much
help
Please Help me
I was flashing a stock rom for my xperia z ultra c6833.
After that, the flashing proccess started and done without any problem. When i put the sim card in the phone, it says: "Invalid Sim card" and in the service menu says: "Rooting status: Unknown". Before this, the service menu said: "Rooting status: Unlock Bootloader allowed: yes" then I unlocked my bootloader without any problem and everything was perfect, but after that flashing on flashtool the Rooting status change to "Unknown" and my sim card are unable to read. There is no problem with my sim card because I tried to put it on another phone and works perfect.
How do I fix it?
How I change the roothing status back to "allowed: yes"
and how I fix it to be able to read my sim card again?
and what ? any solution ?
hi exery one
i have the seem problem (Unlock Bootloader Allowed: Unknown)
and i can't Unlock it.
please help me.
im having trouble trying to root my phone again after it crashed and had to start from beginning. When i try fastboot flash boot Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img it gives me fails and says FAILED <Remote: command not allowed> does any body know what im doing wrong? I managed to root it teh first time no problem.
Cheers
sturtz1987 said:
im having trouble trying to root my phone again after it crashed and had to start from beginning. When i try fastboot flash boot Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img it gives me fails and says FAILED <Remote: command not allowed> does any body know what im doing wrong? I managed to root it teh first time no problem.
Cheers
Click to expand...
Click to collapse
Is you bootloader unlocked?
krabappel2548 said:
Is you bootloader unlocked?
Click to expand...
Click to collapse
yes the bootloader is unloack but i had my phone rooted before then had to use pc companion to repair it, ive unlocked it again to be sure.
It seems driver problem.
I met the same problem as well as others yesterday, when I unlock, relock, re-unlock, root locked, root unlocked, flash recovery... for some crazy reason.
Try these:
Connect to flashtool (beta2 or beta4) with device power-on debug off, to see if flashtool can recognize it, and how much it can recognize.
Connect to flashtool with device power-on debug on , to see if flashtool can recognize it.
Connect to flashtool with device in fastboot mode, to see if flashtool can recognize it.
Connect to flashtool with device in flashmode, to see if flashtool can recognize it.
Flashtool may fix some driver error. I just succeeded after hours of bungling like that.
Good luck.
orc.x.lei said:
It seems driver problem.
I met the same problem as well as others yesterday, when I unlock, relock, re-unlock, root locked, root unlocked, flash recovery... for some crazy reason.
Try these:
Connect to flashtool (beta2 or beta4) with device power-on debug off, to see if flashtool can recognize it, and how much it can recognize.
Connect to flashtool with device power-on debug on , to see if flashtool can recognize it.
Connect to flashtool with device in fastboot mode, to see if flashtool can recognize it.
Connect to flashtool with device in flashmode, to see if flashtool can recognize it.
Flashtool may fix some driver error. I just succeeded after hours of bungling like that.
Good luck.
Click to expand...
Click to collapse
Thank you i got it by turning of debugging mode, strange it worked but cheers
I have this problem as well, tried doing above things, uninstalling drivers, reinstalling - help appreciated.
and Phone is working normal but after 5 second reboot and FC 's
Plz Help
same issue...
Has anyone found a sure fix for the issue presented by the original post? I am having this issue and I have tried different drivers, ftf's, computers, adb/fastboot/versions and flashtool versions. I have unlocked and relocked. Is rooting status "unknown" normal after bootloader unlock? -Z Ultra 6833 EU
Still no solution?
With my C6603 it does not allow to write boot aswell. Any final solutions?
edit: solution found: bootloader was not unlocked
Error flashing kernel
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
aravindjr said:
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
Click to expand...
Click to collapse
This is the wrong forum to ask this. This is the Xperia Z section.
Despite that, you need to unlock your bootloader to flash kernels via fastboot.
Sent from my C6603 using Tapatalk
After months using stock everything I decided to flash CM11 yesterday, I'm doing exactly same step as I was doing when on 4.1/4.2 but it seems like it doesn't works, I'm not even sure that my BL is unlocked despite success message, when trying to reboot after unlock BL I had a bootloop and when trying to recover with Sony's Flashtool it says 'device not unlocked'. So I repaired with PCC and restarted from scratch but same results today.
I'm totally lost as like I said I was doing exactly same thing on the same PC.
Edit : Now my XZ doesn't even start! I have the red led blinking while connected with usb, power+ Vol+ doesn't do anything, no vibrations at all!
I was on latest sony official ROM
Edit2 : Tryied again to recover with Sony's Flashtool but it says "Mobile Locked" that's crazy!
aravindjr said:
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
Click to expand...
Click to collapse
Check PM
Relax!
4.3 introduced a new security feature. Look up "unlock bootloader 4.3 xperia z" for help :good:
babylonbwoy said:
After months using stock everything I decided to flash CM11 yesterday, I'm doing exactly same step as I was doing when on 4.1/4.2 but it seems like it doesn't works, I'm not even sure that my BL is unlocked despite success message, when trying to reboot after unlock BL I had a bootloop and when trying to recover with Sony's Flashtool it says 'device not unlocked'. So I repaired with PCC and restarted from scratch but same results today.
I'm totally lost as like I said I was doing exactly same thing on the same PC.
Edit : Now my XZ doesn't even start! I have the red led blinking while connected with usb, power+ Vol+ doesn't do anything, no vibrations at all!
I was on latest sony official ROM
Edit2 : Tryied again to recover with Sony's Flashtool but it says "Mobile Locked" that's crazy!
Click to expand...
Click to collapse
BatteryAidFree said:
4.3 introduced a new security feature. Look up "unlock bootloader 4.3 xperia z" for help :good:
Click to expand...
Click to collapse
I know I'm late but thanks anyway, just updated to 4.4.4 today, I'll look to your advice, thanks for replying, you're the only one that took time to write few words to help.
Hope it goes well!
babylonbwoy said:
I know I'm late but thanks anyway, just updated to 4.4.4 today, I'll look to your advice, thanks for replying, you're the only one that took time to write few words to help.
Click to expand...
Click to collapse
You're welcome! The only thing I can think is if you want to install/rate 5 stars my app, would be greatly appreciated! ("Battery Aid" - I can't post the link apparently, "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!")
use flashtool to writ kernel
fastboot remote command not allowed Xperia Z3
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
stevenmanzano said:
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
Click to expand...
Click to collapse
Look in the service menu to confirm if your bootloader is unlocked.
Enter *#*#7378423#*#* in the dialler, then look in Service info -> Configuration. It will say "Bootloader unlocked: Yes" if it's unlocked.
Sent from my C6603
solved remote command not allowed
stevenmanzano said:
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
Click to expand...
Click to collapse
By installing FLASHTOOL by Sony I was instantly notified that my bootloader was not unlocked, even though I had already unlocked it three or four times without any errors. So I unlocked it again. Then fastboot flashed my images just fine.
Hi
Yesterday my phone dead? Reloop after sony logo, i cant go to recovery. (before i had Ressurection 5.0.2 rom)
Later i flashed boot.img for lollipop and phone booted with charger, but mt wifi don't worked and i tired to install another rom with cwm.
Later idk how my recovery changed to Cyanogenmod Recovery and i cant do anything
Now i flashed unrooted stock .tft and i still have loops.
When i try to flash boot.img i have problem with writing :
sending 'boot' (10182 KB)...
OKAY [ 0.337s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.339s
Click to expand...
Click to collapse
I have warranty but idk do I have to give my phone to service.
What i have to do?
m1ko8 said:
Hi
Yesterday my phone dead? Reloop after sony logo, i cant go to recovery. (before i had Ressurection 5.0.2 rom)
Later i flashed boot.img for lollipop and phone booted with charger, but mt wifi don't worked and i tired to install another rom with cwm.
Later idk how my recovery changed to Cyanogenmod Recovery and i cant do anything
Now i flashed unrooted stock .tft and i still have loops.
When i try to flash boot.img i have problem with writing :
I have warranty but idk do I have to give my phone to service.
What i have to do?
Click to expand...
Click to collapse
Well, sad to say, but you don't have the warranty anymore, as you have unlocked your bootloader, within erasing all your DRM keys (ironic, I know).
But if you have a TA-Partition backup, then you could just push in, (just be sure before pushing TA to flash stock .ftf with its kernel) and your DRM keys are back. Then you could proceed futher for warranty service.
Firstly, if you don't want go to warranty, try to flash Pabx Lollipo (it's stock lollipop). After that you could check if it has been fixed and flashing commands are properly working
LaurynasVP said:
Well, sad to say, but you don't have the warranty anymore, as you have unlocked your bootloader, within erasing all your DRM keys (ironic, I know).
But if you have a TA-Partition backup, then you could just push in, (just be sure before pushing TA to flash stock .ftf with its kernel) and your DRM keys are back. Then you could proceed futher for warranty service.
Firstly, if you don't want go to warranty, try to flash Pabx Lollipo (it's stock lollipop). After that you could check if it has been fixed and flashing commands are properly working
Click to expand...
Click to collapse
DRM keys ? What is that?
I locked bootloader before and deleted all files accidentally
How to flash this file?<--- nvm
Can i flash userdata.img in flashtool? Idk why fastboot dont work in cmd .-.
Edit2: After flash Unrooted ftf PC Companion accepted my phone and now my phone is repairing, i will write later does it works.
Edit3: PC companion repair dont work too.
m1ko8 said:
DRM keys ? What is that?
I locked bootloader before and deleted all files accidentally
How to flash this file?<--- nvm
Can i flash userdata.img in flashtool? Idk why fastboot dont work in cmd .-.
Edit2: After flash Unrooted ftf PC Companion accepted my phone and now my phone is repairing, i will write later does it works.
Edit3: PC companion repair dont work too.
Click to expand...
Click to collapse
DRM keys are stored in your TA-Partition, they're required for many functions to work: Clear audio, Camera functions, Official ROM and it's updates (If i'm right with this one) and other.
I recommend you to download android SDK, then go to it --> Platform tools --> SHIFT + RMB (right mouse button) --> Open Command Prompt Here.
After that, shut down your phone. Wait atleast 30 seconds. then by holding Vol +, plug it into PC. Blue LED should show up.
Then in CMD type this:
fastboot devices
Click to expand...
Click to collapse
It should be returned some numbers and letters. If it doesn't show anything, then your windows maybe doesn't support fastboot or you don't have drivers to that (fastboot + adb drivers).
Make sure in this folders are fastboot.exe and adb.exe (the most importantly to us is fastboot.exe) and some other files as well.
If ir returns information correctly, then you can download any rom and extract it (I sugges you to use Pabx).
Extract everything from .ZIP/.RAR, you should see system.img, boot.img, userdata.img. Place them into platform-tools directory (where fastboot.exe and other files are).
Then simply write these commands in CMD:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
If everything will go OK, then you can reboot your device:
fastboot reboot
Click to expand...
Click to collapse
Then your phone should start normally, after that you can manually install CWM and other things either.
If it didn't work, just quote me regarding the problem, I'll try to help you
LaurynasVP said:
DRM keys are stored in your TA-Partition, they're required for many functions to work: Clear audio, Camera functions, Official ROM and it's updates (If i'm right with this one) and other.
I recommend you to download android SDK, then go to it --> Platform tools --> SHIFT + RMB (right mouse button) --> Open Command Prompt Here.
After that, shut down your phone. Wait atleast 30 seconds. then by holding Vol +, plug it into PC. Blue LED should show up.
Then in CMD type this:
It should be returned some numbers and letters. If it doesn't show anything, then your windows maybe doesn't support fastboot or you don't have drivers to that (fastboot + adb drivers).
Make sure in this folders are fastboot.exe and adb.exe (the most importantly to us is fastboot.exe) and some other files as well.
If ir returns information correctly, then you can download any rom and extract it (I sugges you to use Pabx).
Extract everything from .ZIP/.RAR, you should see system.img, boot.img, userdata.img. Place them into platform-tools directory (where fastboot.exe and other files are).
Then simply write these commands in CMD:
If everything will go OK, then you can reboot your device:
Then your phone should start normally, after that you can manually install CWM and other things either.
If it didn't work, just quote me regarding the problem, I'll try to help you
Click to expand...
Click to collapse
Thanks, i know how to use fastboot but xperia dont charge. I will do everything what u said for a while and i leave edit.
btw. Thanks
Edit: Idk it's important but before it in android 5.0.2 Ressurection ROM sometimes it turn off without charger plugged , i think it was ROM fail
Edit1: Do you think it's better solution than SUS repair?
Edit2:After flash tired to turn on phone but red led blinked 3 times , then i connect phone to charger and red led blinks every 1-2 second. What i have to do?
@m1ko8
Don't be panic
download latest z fw .292 ftf then download flashtool and install it and goto C>flashtool>drivers install that file,then put downloaded ftf to firmware folder ,after run flastool and click thunder icon select flashmode select fw and wait prepairing then connect device when notify popup massage.then progress bar fill when it end disconnect cable and power on ur device
Isuru cs said:
@m1ko8
Don't be panic
download latest z fw .292 ftf then download flashtool and install it and goto C>flashtool>drivers install that file,then put downloaded ftf to firmware folder ,after run flastool and click thunder icon select flashmode select fw and wait prepairing then connect device when notify popup massage.then progress bar fill when it end disconnect cable and power on ur device
Click to expand...
Click to collapse
When I try to install this drivers with checked fastboot and flashtool drivers "Installation failed" for both drivers.
After install FTF my phone still stuck on sony logo and restart , its important what firmware i install? (region?) I have from Play in Poland then i must install Firmware Play PL ? I installed Firmware UK and RU and EU . still i have bootloop.
I tired too repair with pc companion. hmm.. bad luck, today probably i will give my phone to service
m1ko8 said:
When I try to install this drivers with checked fastboot and flashtool drivers "Installation failed" for both drivers.
After install FTF my phone still stuck on sony logo and restart , its important what firmware i install? (region?) I have from Play in Poland then i must install Firmware Play PL ? I installed Firmware UK and RU and EU . still i have bootloop.
I tired too repair with pc companion. hmm.. bad luck, today probably i will give my phone to service
Click to expand...
Click to collapse
I'm sorry to tell you, but you phone doesn't have warranty anymore and specilized Sony staff won't take it for fixing, as you have unlocked your bootloader, so you need take it to local repair service (Sony might fix it, but with some price of course).
Either way, you can try install drivers on other computer, if you have one, then try on it.
LaurynasVP said:
I'm sorry to tell you, but you phone doesn't have warranty anymore and specilized Sony staff won't take it for fixing, as you have unlocked your bootloader, so you need take it to local repair service (Sony might fix it, but with some price of course).
Either way, you can try install drivers on other computer, if you have one, then try on it.
Click to expand...
Click to collapse
I locked bootloader before. Repair with PC companion. Bootloader is locked and when i unlocked it (have unlock code) after reconnect fastboot it was locked again. idk how I think they can't see it cause its power and software problem and service give me new phone . They can see i had unlocked bootloader ?
I think something inside phone overheated and i dont thinnk so does Polish service see it
m1ko8 said:
I locked bootloader before. They can see it?
I think something inside phone overheated and i dont thinnk so does Polish service see it
Click to expand...
Click to collapse
Yeah, if your phone is psychical damage (overheated) and doesn't turn on, then they may change it for you to another one, but If they will bring the life back to it, they would be able to see if DRM keys are in their place, and even if you've re-locked your BL, it doesn't change the situation at all, because in the service menu they could check if DRM keys are not erased, if so - they will not fix it under the warranty
LaurynasVP said:
Yeah, if your phone is psychical damage (overheated) and doesn't turn on, then they may change it for you to another one, but If they will bring the life back to it, they would be able to see if DRM keys are in their place, and even if you've re-locked your BL, it doesn't change the situation at all, because in the service menu they could check if DRM keys are not erased, if so - they will not fix it under the warranty
Click to expand...
Click to collapse
2 days ago my phone stay in my bed at night witch charger and he was very hot. Later i dont turn it on again.
Yesterday i connected my phone to charger and he dont charging. I can go to flashmode and fastboot .Installing system throught fastboot , pc companion repair dont worked. I think they are too lazy to check it.
I have no choice , money is no problem anyway i must repair it
Edit: Now wait ~2 weeks >.<
LaurynasVP said:
Yeah, if your phone is psychical damage (overheated) and doesn't turn on, then they may change it for you to another one, but If they will bring the life back to it, they would be able to see if DRM keys are in their place, and even if you've re-locked your BL, it doesn't change the situation at all, because in the service menu they could check if DRM keys are not erased, if so - they will not fix it under the warranty
Click to expand...
Click to collapse
Some news
Service gave me new Xperia Z (under warranty ofc)
m1ko8 said:
Some news
Service gave me new Xperia Z (under warranty ofc)
Click to expand...
Click to collapse
Cool! I'm happy for you!
And try to not harm your phone anymore, make care of it
LaurynasVP said:
Cool! I'm happy for you!
And try to not harm your phone anymore, make care of it
Click to expand...
Click to collapse
They informed me about motherboard repair. But they gave me new phone
Now i have Android 5.1 and unlocked bootloader But i will take care of my phone .
But.. what ROM You recommend for nice look and smooth work ( You like lollipop? )
They gave you a new z with lollipop preinstalled? Or did you flash a custom rom?
shoey63 said:
They gave you a new z with lollipop preinstalled? Or did you flash a custom rom?
Click to expand...
Click to collapse
Dont be funny OFC I flashed .
m1ko8 said:
They informed me about motherboard repair. But they gave me new phone
Now i have Android 5.1 and unlocked bootloader But i will take care of my phone .
But.. what ROM You recommend for nice look and smooth work ( You like lollipop? )
Click to expand...
Click to collapse
@m1k8 I suggest you to use Validus ROM. Just now I'm waiting for 5.1 update @shoey63 - of course he has phone with an unlocked bootloader, even he said so, that means he just pre-installed it by himself
LaurynasVP said:
@m1k8 I suggest you to use Validus ROM. Just now I'm waiting for 5.1 update @shoey63 - of course he has phone with an unlocked bootloader, even he said so, that means he just pre-installed it by himself
Click to expand...
Click to collapse
What version ? Validus-LP-v7.0-2015-03-09 or Validus-LP-v7.0-2015-03-11? ( New version not always is better)
m1ko8 said:
What version ? Validus-LP-v7.0-2015-03-09 or Validus-LP-v7.0-2015-03-11? ( New version not always is better)
Click to expand...
Click to collapse
09-03 for now. I'm not sure which version was perfect working, as the newest 03-11 isn't working properly as it should to.
Now I'm waiting for the update to 5.1.. I do know that from 03-08 there will be lots of bugs : screen always on, even if you turn of it just will turn to grey color, that's all, ambient auto display doesn't work either and some other problems.
So, I suggest you to try only from 03-03 to 03-08
LaurynasVP said:
09-03 for now. I'm not sure which version was perfect working, as the newest 03-11 isn't working properly as it should to.
Now I'm waiting for the update to 5.1.. I do know that from 03-08 there will be lots of bugs : screen always on, even if you turn of it just will turn to grey color, that's all, ambient auto display doesn't work either and some other problems.
So, I suggest you to try only from 03-03 to 03-08
Click to expand...
Click to collapse
Understand
So , I decided to install ressurection ROM , and work perfect ( Validus rom is dark , i dont like dark themes and have some bugs , Ressurection is for me much better. )
I have a sony xperia z c6603 , it was never unlocked from the start but it worked very fine on its original firmware, android 4.1.2. But then someone flashed a c6602 android 4.1 on it and now the IMEI is corrupted and it restarts every 9.3minutes.
It says bootloader unlock allowed: Yes which I guess means the bootloader is locked and can be unlocked, but since IMEI is corrupt, i cant request for unlock code from sony or use fastboot.
My only other option is the famous flashtool. I have three issues with flashtool.
1. I already downloaded the correct firmware and preparing to flash, so I click on the flash icon and start flash (Using Androxyde flash tool). It goes through the normal process and then an empty device selector screen comes up, with no option but to cancel. and when i cancel, it says "loader not found for this device"
2. Okay, after step 1, i am thinking "maybe i have to unlock the bootloader first" so i click on the BLU button and connect the device in flash mode, it starts and the empty device selector screen comes up again, once i cancel, it says "your device can not be officially unlocked"
3. So i did a little bit of digging around on here more and found that i have to update xflasher.jar to beta6, and so i did and flash tool started as "androxyde and bin4ry flash tool" .Only problem is when i click on the flash icon and choose flash mode, nothing comes up, i cant get into flash mode. but I can get into every other thing like fastboot mode and BLU
Please if you think you have an idea on how to solve this problem, please reply. I cant afford a new phone and I would also like to know if my phone can be repaired too, I also dont have a lot of time to waste trying to repair it.
try to reinstall flashtool after deleting it first .. install fastboot and flashmode drivers and drivers for ur device from drivers folder in flashtool folder.. disable any antivirus and any app that could interfere and unplug any usb device ... try to flash with flashmode
---------- Post added at 12:39 AM ---------- Previous post was at 12:35 AM ----------
mordr3d said:
I have a sony xperia z c6603 , it was never unlocked from the start but it worked very fine on its original firmware, android 4.1.2. But then someone flashed a c6602 android 4.1 on it and now the IMEI is corrupted and it restarts every 9.3minutes.
It says bootloader unlock allowed: Yes which I guess means the bootloader is locked and can be unlocked, but since IMEI is corrupt, i cant request for unlock code from sony or use fastboot.
My only other option is the famous flashtool. I have three issues with flashtool.
1. I already downloaded the correct firmware and preparing to flash, so I click on the flash icon and start flash (Using Androxyde flash tool). It goes through the normal process and then an empty device selector screen comes up, with no option but to cancel. and when i cancel, it says "loader not found for this device"
2. Okay, after step 1, i am thinking "maybe i have to unlock the bootloader first" so i click on the BLU button and connect the device in flash mode, it starts and the empty device selector screen comes up again, once i cancel, it says "your device can not be officially unlocked"
3. So i did a little bit of digging around on here more and found that i have to update xflasher.jar to beta6, and so i did and flash tool started as "androxyde and bin4ry flash tool" .Only problem is when i click on the flash icon and choose flash mode, nothing comes up, i cant get into flash mode. but I can get into every other thing like fastboot mode and BLU
Please if you think you have an idea on how to solve this problem, please reply. I cant afford a new phone and I would also like to know if my phone can be repaired too, I also dont have a lot of time to waste trying to repair it.
Click to expand...
Click to collapse
try to install a newer version of flashtool ...
Hey, I have a Xperia Z C6602 running 5.1.1 and firmware version: 10.7.A.0.222
I was trying to root the device but got in trouble.
I used this guide to root the device but soon after Super-SUme got installed & updated, the device was supposed to reboot but it just shows "Power off ; restart ; take screenshot " options and nothing else.
I went into fastboot mode:
Code:
fastboot devices
worked but couldn't flash recovery.
I can't unlock the bootloader since I don't know the IMEI code. I don't have the phone box or receipt to check the IMEI.
Please help.
THANKS IN ADVANCE.
I install the emma. It show imei. Then i unlocked bootloader.
You should install flashtool from:
http://www.flashtool.net/index.php
It's a multipurpose tool for Sony Xperia Devices!
Be sure to install the right drivers "Devices -> Check Drivers" for the Xperia Z.
If you are running Windows 8 64-Bit or a higher version you need to disable Driver Signature Verification before installing the drivers!
Example guide: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
If everything went well you can now connect your phone to the PC and the Flashtool program will be able to recognize it.
As far as I remember it, the boot loader unlock from flashtool will automatically save your "DRM-Keys" so you will be able to restore them later on to your phone, which also relocks the boot loader (but you might want to check on that before doing the boot loader unlock process as you won't be able to restore the DRM-Keys if you loose them once!).
Now you press the "BLU" button inside flashtool and it will guide you through the progress!
I hope that will help you! If not, feel free to ask!