Related
U20i. Had a custom ROM SE_Style_V1.1, so phone was rooted, superuser installed. Now I wish to put MiniCM9 on the phone.
Flashtool gives:
ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
S1TOOL gives "R8A029" and SEMC SIMLOCK CERTIFICATE
Which threads say is because the phone is locked. But.......... the phone is rooted. Forgive noobness - I'm assuming rooted = bootloader unlocked.
None of the unlock procedures finish. Flashtool plugins menu option is empty, none of these methods work.
The “date” on the phone rear panel is 10W27.
The methods I was trying to follow:
SpyderX method - Last edited by SpyderX; 21st June 2012
http://forum.xda-developers.com/showthread.php?t=1254225
Another bootloader unlock method - Using SE Tweaker Tool
faiyyaz - Last edited by faiyyaz; 22nd July 2012
http://forum.xda-developers.com/showthread.php?t=1462278
Also: http://wiki.cyanogenmod.org/w/Install_CM_for_mimmi
All the bootloader unlock procedures hang at some point. I thought maybe these were failing because the phone is already rooted. So..
I reflashed with a stock ROM, and then using Superoneclick - this was successful - no problem, it rooted the phone. (no info if rooted = bootloader unlocked, my noob assumption)
But I tried flashtool and again, it fails with "SIN header verification failed"
I've been reading the forum for days, but just the same problem. I'm going in circles.
abssorb said:
U20i. Had a custom ROM SE_Style_V1.1, so phone was rooted, superuser installed. Now I wish to put MiniCM9 on the phone.
Flashtool gives:
ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
S1TOOL gives "R8A029" and SEMC SIMLOCK CERTIFICATE
Which threads say is because the phone is locked. But.......... the phone is rooted. Forgive noobness - I'm assuming rooted = bootloader unlocked.
None of the unlock procedures finish. Flashtool plugins menu option is empty, none of these methods work.
The “date” on the phone rear panel is 10W27.
The methods I was trying to follow:
SpyderX method - Last edited by SpyderX; 21st June 2012
http://forum.xda-developers.com/showthread.php?t=1254225
Another bootloader unlock method - Using SE Tweaker Tool
faiyyaz - Last edited by faiyyaz; 22nd July 2012
http://forum.xda-developers.com/showthread.php?t=1462278
Also: http://wiki.cyanogenmod.org/w/Install_CM_for_mimmi
All the bootloader unlock procedures hang at some point. I thought maybe these were failing because the phone is already rooted. So..
I reflashed with a stock ROM, and then using Superoneclick - this was successful - no problem, it rooted the phone. (no info if rooted = bootloader unlocked, my noob assumption)
But I tried flashtool and again, it fails with "SIN header verification failed"
I've been reading the forum for days, but just the same problem. I'm going in circles.
Click to expand...
Click to collapse
restore to stock and do it from the start!
abssorb said:
U20i. Had a custom ROM SE_Style_V1.1, so phone was rooted, superuser installed. Now I wish to put MiniCM9 on the phone.
Flashtool gives:
ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
S1TOOL gives "R8A029" and SEMC SIMLOCK CERTIFICATE
Which threads say is because the phone is unlocked. But.......... it is not.
None of the unlock procedures finish. Flashtool plugins menu option is empty, none of these methods work.
The “date” on the phone rear panel is 10W27.
The methods I was trying to follow:
SpyderX method - Last edited by SpyderX; 21st June 2012
http://forum.xda-developers.com/showthread.php?t=1254225
Another bootloader unlock method - Using SE Tweaker Tool
faiyyaz - Last edited by faiyyaz; 22nd July 2012
http://forum.xda-developers.com/showthread.php?t=1462278
Also: http://wiki.cyanogenmod.org/w/Install_CM_for_mimmi
I thought maybe these were failing because the phone is already rooted. So..
I reflashed with a stock ROM, and then using Superoneclick - this was successful - no problem, it rooted the phone.
But I tried flashtool and again, it fails with "SIN header verification failed"
I've been reading the forum for days, but just the same problem. I'm going in circles.
Click to expand...
Click to collapse
Your phone's bootloader is NOT unlocked, if it is the R8A029 would give a small 'r'
Put usb-debugging on on your phone and install busybox with flashtool.
I guess the plugins-menu of flashtool would give you the option to unlock the bootloader then.
isko95 said:
restore to stock and do it from the start!
Click to expand...
Click to collapse
I did that (above) but perhaps I didn't do it correctly. Flashtool loaded the stock kernel OK.
SmG67 said:
Your phone's bootloader is NOT unlocked, if it is the R8A029 would give a small 'r'
Put usb-debugging on on your phone and install busybox with flashtool.
I guess the plugins-menu of flashtool would give you the option to unlock the bootloader then.
Click to expand...
Click to collapse
Yes, USB-debugging was on, and unofficial sources.
busybox installed using Superoneclick, but I can do with flashtool if it's different.
plugins-menu of flashtool was empty at every attempt, including after restoring to stock. It's almost like I have a bad install of flashtool
Grateful for help.
Fixed by going back to stock with Sony Ericsson PC Companion update option.
I got it sorted. I'm sure my questions seem very noob, but it's good to get re-assurance when everything seems to be going wrong, so thanks for the answers above.
Details in case anyone else has the same problem.
Re-loading a stock kernel was not the same as "going back to stock". No matter how many times I successfully loaded a stock kernel and rom, the unlocking options would not appear in the flashtool plugin menu. Also I think this was re-locking the bootloader.
I got around this by using Sony Ericsson PC Companion, the update option, which got rid of my old custom setup and put the whole phone back to factory stock. PC Companion reported: "Xperia X10 mini pro (U20) was updated with 2.1.1.A.0.6"
After this, flashtool still would not work, but this time I had re-assurance that I was starting with a phone that should work.
I switched to a different PC which had never had any of these tools on. The first thing I did was load the Gordon Gate drivers, then flashtool. It worked perfectly.
I didn't find out what was up with the first PC, but it might have been driver problems. Every tool seems to come with its own set of drivers, and I had been installing and re-installing them, so I imagine it was a right mess. I should have made a restore point on the PC so I could go back to a "no drivers" position easily.
Hello, I have the M4 E2303 with the software version .167.
Everytime I try to flash an other version (like .128) my phone locks itself and I can't activate it because of an Error. It says Name/Password wrong. I googled it and I saw that some people have this problem.
Then I flash back to .167 an everything is ok.
I deactivated MXTP but nothing changes.
Any ideas how I can flash successfully .128 to root?
And an other Problem
Some people say I deactivate MXTP and then the Bootloader Unlock allowed status will be: "yes";
but on my phone it's always "no".
I hope you can help me.
thank you
You need to do a Downgrade man, it is all.
5.0 Lollipop for Xperia M 4 don´t have the MXTP
Firmware 5.0 https://mega.nz/#!lQx1BZ7L!RPNTzomzNDfA6RYjJJ_jSMp9nnHp0X2VXqyJGkUurHo
Drivers http://www.mediafire.com/download/o...y+El+Hombre+de+Tierra+(+52)+55+4079+0885+.zip
TUTO ON YOUTBE https://www.youtube.com/watch?v=FrjgXt1DVpM
Flashtool https://mega.nz/#!hdxEXDIR!3Dy5rgvijMwafYGWGGS4tBdAalgL_bJHR3-IucRzmow
If you have some ERROR put this Parch http://www.mediafire.com/download/s...ASH+M+4+x10flasher+By+El+Hombre+De+Tierra.jar
MY WHATSAPP FOR HELP -> (+52) 55 4079 0885
I buy phone at Amazone 24.12.2015
E2306 rev2 1297-2190 26.1.A.2.99 R3A
The phone was laggin and i decided to flash another rom via flashtool
After flashing phone on 1297-3910 26.1.A.2.99 Customized USA R10A, on startup have a massage - my Xperia LOCKED - enter my login and password for authentication (google account) > sing in google account and after thet i have an error - wrong username or password.
I dont save rom version 1297-2190 26.1.A.2.99 R3A what was at phone when i buy it and now dont now what to do.
There is no such version 1297-2190 26.1.A.2.99 R3A on flashtool
Anyone can help me?
Solved
1. from computer go to myxperia on the web
2. sing in with my google account
3. select my phone Sony Xperia M4 Aqua
4. clear data on my phone
5. on the phone MXTP sing in with my google account
The phone is unlocked!
On new rom the phone works much more better and faster
thank you @Marco Ochoa
I will try it tomorrow I will say if it works
erikgottschall said:
Hello, I have the M4 E2303 with the software version .167.
Everytime I try to flash an other version (like .128) my phone locks itself and I can't activate it because of an Error. It says Name/Password wrong. I googled it and I saw that some people have this problem.
Then I flash back to .167 an everything is ok.
I deactivated MXTP but nothing changes.
Any ideas how I can flash successfully .128 to root?
And an other Problem
Some people say I deactivate MXTP and then the Bootloader Unlock allowed status will be: "yes";
but on my phone it's always "no".
I hope you can help me.
thank you
Click to expand...
Click to collapse
I have the same problem here, have you found a solution?
No, i got yesterday a new M4 because I broke the screen of the old phone. Now I unlocked the bootloader.
Sorry
You need to do a Downgrade man, it is all.
5.0 Lollipop for Xperia M 4 don´t have the MXTP
Firmware 5.0 https://mega.nz/#!lQx1BZ7L!RPNTzomzN...X2VXqyJGkUurHo
Drivers http://www.mediafire.com/download/ob...4079+0885+.zip
TUTO ON YOUTBE https://www.youtube.com/watch?v=FrjgXt1DVpM
Flashtool https://mega.nz/#!hdxEXDIR!3Dy5rgvij...bJHR3-IucRzmow
If you have some ERROR put this Parch http://www.mediafire.com/download/sh...+De+Tierra.jar
MY WHATSAPP FOR HELP -> (+52) 55 4079 0885
Hi,
I made a different thread to find a solution about this error I got when I try to flash the Androkernel boot.im and TWRP recovery on my UNLOCKED BOOTLOADER Z4 712 wifi european tablet.
I updated with the Sony PC Companion tool, I DID NOT turn ofn the MySony Security (that was THE problem that caused this error last time), and bootloader is still unlocked (checked with Sony Mobile Flasher).
The service mode say "root:unknow", in previous tablets/room it should say "bootloader locked or unlocked", but I'm not sure.
That's what I got when I tri to flash boot.img:
C:\>fastboot flash boot boot.img
sending 'boot' (32584 KB)...
OKAY [ 1.633s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 2.150s
Click to expand...
Click to collapse
Thank you for the help
Diomorgan said:
Hi,
I made a different thread to find a solution about this error I got when I try to flash the Androkernel boot.im and TWRP recovery on my UNLOCKED BOOTLOADER Z4 712 wifi european tablet.
I updated with the Sony PC Companion tool, I DID NOT turn ofn the MySony Security (that was THE problem that caused this error last time), and bootloader is still unlocked (checked with Sony Mobile Flasher).
The service mode say "root:unknow", in previous tablets/room it should say "bootloader locked or unlocked", but I'm not sure.
That's what I got when I tri to flash boot.img:
Thank you for the help
Click to expand...
Click to collapse
First of all it's not polite to create new thread in android development part. Here should be only roms, fixes, patches recoveries. Not q&a threads.
As to your problem, are you sure that you've unlocked bootloader? In service menu you should see
"Rooting status:
Boot loader unlocked: Yes"
if you doesn't see it, it means you haven't unlocked it or unlocking is not allowed on your device.
Diomorgan said:
Hi,
I made a different thread to find a solution about this error I got when I try to flash the Androkernel boot.im and TWRP recovery on my UNLOCKED BOOTLOADER Z4 712 wifi european tablet.
I updated with the Sony PC Companion tool, I DID NOT turn ofn the MySony Security (that was THE problem that caused this error last time), and bootloader is still unlocked (checked with Sony Mobile Flasher).
The service mode say "root:unknow", in previous tablets/room it should say "bootloader locked or unlocked", but I'm not sure.
That's what I got when I tri to flash boot.img:
Thank you for the help
Click to expand...
Click to collapse
Hi,
I think the problem is here if you enable myXperia before or after unlocking the bootloader ( can be @AndroPlus can explain better the problem ?)
Verify that your USB drivers for fastboot and adb are correcctly installed (install the USB drivers provided with Flashtool)
I hope you can root your tablet again :good:
I'm very sorry if I opened the thread here, feel free to close or move it, but I found it related the modding and , actually, in installing the androplus kernel.
As I said I did not turn on the sony security nor befor nor after, root status is "unknown", Flas Tool say is't unlocked, I already flashed the androkernel before and the problem was the MySony security, but now I know I don't have to turn it on.
Drivers are Ok, I flashed the new rom with Flash tool and then with Sony Companion.
Anyhow, if I'm bothering with this thread pleas close it, al try again and again
I think it's okey moderators will move the thread over.
Did you unlock your tablet by flashtool or follow official Sony instructions?
Do you have myxperia app installed?
Have you got factory reset after unlocking?
killdozer56 said:
Hi,
I think the problem is here if you enable myXperia before or after unlocking the bootloader ( can be @AndroPlus can explain better the problem ?)
Verify that your USB drivers for fastboot and adb are correcctly installed (install the USB drivers provided with Flashtool)
I hope you can root your tablet again :good:
Click to expand...
Click to collapse
alex009988 said:
I think it's okey moderators will move the thread over.
Did you unlock your tablet by flashtool or follow official Sony instructions? Official sony on previous firmware and flashtool say i'ts unloked
Do you have myxperia app installed? yes, but it's not enabled! Actually it's not an app, but an option in "security" menu.
Have you got factory reset after unlocking?
Click to expand...
Click to collapse
yes, I reinstalled the new rom with flashtool then with Sony Companion and root status is "unknown".I can try reflashing it tomorrow.maybe someway I got stuck in a unknow situation between locked and unlocked X-(
farfetch has beaten the same topic here to death.
same style:
many threads (unrelated to his topic)
look it up - it is not easy because of this
you will not like what you read:
you have bricked your tablet with enabling myXperia after unlocking the BL
DHGE said:
farfetch has beaten the same topic here to death.
same style:
many threads (unrelated to his topic)
look it up - it is not easy because of this
you will not like what you read:
you have bricked your tablet with enabling myXperia after unlocking the BL
Click to expand...
Click to collapse
First of all, I don't really understand how he was able to update something via pc companion with unlocked bootloader?
No ota update, nor update via pc companion is available after unlocking.
DHGE will we have the same? I mean when android MM will be released, we flash it and will it be with myxperia? And if we launch it by accident we break our tablet, right? In this case, how to remove it, factory reset?
alex009988 said:
First of all, I don't really understand how he was able to update something via pc companion with unlocked bootloader?
No ota update, nor update via pc companion is available after unlocking.
DHGE will we have the same? I mean when android MM will be released, we flash it and will it be with myxperia? And if we launch it by accident we break our tablet, right? In this case, how to remove it, factory reset?
Click to expand...
Click to collapse
I read about a guy thoblem because after updating with Companion bootloader was relocked, he unlocked again and so.
Anyhow,I just NOT UPDATED, but RESTORE/REFRESH the firmware flashed with Flashbout a bad flash with Flashtool. Immediately after the flash with compsnion,even without turning on the phone, I try and I got the same FAILED (remote: Command not allowed)
:crying:
I even relocked and reunlocked bootloader with Flashtool (didn't even know it's possible to relocked...).Thi lost :-/
UPDATE: I found that myxperia was administrator even if I didn't turn it on, so I remove from administrators, but....same problem
Maybe it's better to try to unlock bootloader again following official Sony instructions, not flashtool? WITH flashtool unlocking, you haven't got a factory reset, that's the reason of all your problems IMHO.
After unlocking my xperia must disappear.
alex009988 said:
I mean when android MM will be released, we flash it and will it be with myxperia?
And if we launch it by accident we break our tablet, right?
In this case, how to remove it, factory reset?
Click to expand...
Click to collapse
SONY thinks MyXperia is a useful feature security wise and I agree. It is just not for me since it prevents my tampering with the device.
I am sure it will be in MM.
You have to launch it explicitly on setup! SONY warns in the bootloader instructions to activate it after unlocking.
Once activated after unlocking the tablet is bricked. End of discussion, beaten to death in the xperia fora....
If a factory reset could revive the devices this would be no security feature but rather an annoyance for thieves.
DHGE said:
SONY thinks MyXperia is a useful feature security wise and I agree. It is just not for me since it prevents my tampering with the device.
I am sure it will be in MM.
You have to launch it explicitly on setup! SONY warns in the bootloader instructions to activate it after unlocking.
Once activated after unlocking the tablet is bricked. End of discussion, beaten to death in the xperia fora....
If a factory reset could revive the devices this would be no security feature but rather an annoyance for thieves.
Click to expand...
Click to collapse
I completely agree with what @DHGE said this is a no sense if a thief can reset the tablet with a factory reset once MyXperia has been activated. MyXepria operates at a low level, also be able to deactivate it easily is not possible.
:crying:
Oh my God.I haven't known it. http://fxpblog.co/2015/07/03/dont-destroy-your-unlocked-device.html poor people. Indeed, with unlocked bootloader and enabled myxperia, people get tea-tray instead of working device. And it's unrecoverable.
If nevertheless icon of my xperia will appear in a menu of new MM. Can I delete it with some kind of system-app-uninstaller ?
Edit 1. This damned app was in my system, so I used "Uninstall" app and remove my xperia, wiped dalvik and cash.
I strongly recommend it everybody to keep your device safe and don't worry incidental pressing.Better delete it!!!
I activated myxperia with unlockebootloader and I have no problem, can't be able to unactivate it, when I reflash the ro if activate it or not and I can remove administrator priviledge in security section.
If I clickif I want to turn it on and sony says that "if turned on"repair the firmware but will be "unusable" till you imput your google account saved for the my'm UNLOCKED I try turning on myxperia a few days ago to an disable it later (no ways, my xperia has only a blank page without settings), then I reflashed 2 times and both time it asked me if I to turn on the myxperia.I even try with flashtools to chek the bootloader, relock and reunlock and everything wly problem is flashing things via fastboot!
Hi guys, so I seem to have scewed up my phone quite badly. I tried to deodex running the new nougat firmware (with drm-fix and ric-off) by flashing a zip in the nougat firmware thread. Somehow I ended up with not being able to fastboot anymore.
I found out that my bootloader seems to be locked again. Thus I am not able to approach the fastboot mode, but failed to do any flash, as it says [FAILED (remote: not allowed)].
I checked the service menu and found the [Bootloader unlock allowed:no] and [Remote Lock State: Locked] after reflashing the nougat firmware.
So I wanted to unlock the device, how ever I ended up with flashing back to Lollipop and the device boots and then power off after a few seconds of use.
Could this due to "remote lock state: not allowed"?
Try relocking via flashtool?
So. Tried to lock and relock via flashtool. Checked drivers which are working fine.
I was trying to relock and then unlock again using flashtool after updating to .305 Marshmallow firmware . However this does nothing to the bootloader states. The weird thing is that there are no errors showing up in flashtool when unlocking/relocking. I can't even unlock via OEM because when I tick OEM unlock in the developer options this doesn't do any change (Rooting status: Bootloader unlock allowed : No, Remote Lock State: Locked). My DRM keys are gone as well. However I do have a TA Backup but can't restore because after downgrading to lollipop the device shuts down after 30 seconds.
I'm really annoyed because I bought the device with an locked bootloader (without carrier costumizations) and unlocked it via OEM unlock then updated to . Is there any chance to unlock the device again? Restore TA? Any recommendations what I could have done wrong would be helpful.
iArvee said:
Try relocking via flashtool?
Click to expand...
Click to collapse
[solved ] Bootloader is now sucessfully relocked andBootloader states are back to [Bootloader unlock allowed: Yes] and [Remote Lock State: UnLocked].
I need to mention that I bought a phone without carrier lock with [Bootloader unlock allowed: Yes].
So, for anyone who is interested or might face the issue in the future, here's what I did.
You will need your backed up TA-Partition-Image to restore via iovyroot:
1. Downgrade to Lollipop (32.0.A.6.200 / R2B (STOREFRONT GENERIC)) using Flashtool .
->Therfore select/tick everything in the wipe section when selecting the Lollipop-tft
2. Unmount your SIM, reboot the device
3. Skip everything on the welcome/configuration screen as fast as you can to get beyond the Android configuration screen
(skip wif config, Google-Account setup, untick myXperia services! etc.)
The phone might power off only after a few seconds because of the downgrade. So be fast!!!
4. Once you end up on the home screen, unlock developer options, and activate ADB debugging, grant ADB access (check via cmd: fastboot devices)
again: be fast! --> Don't worry if the phone shuts down again. Just reboot if you were not fast enough.
5. Download iovy.root ( iovy.root. Place TA-backup.img in the iovyroot-folder.
Then I modified "tarestore. bat" to save some time regarding the shutdowns. I used notepad++:
...
set response=
set /p response=Type "y" if you want to restore this file:
if "%response%" == "y" (
echo Starting restore
echo.
adb push "root/iovyroot" "/data/local/tmp/iovyroot" > NUL 2> NUL
adb push "root/restore.sh" "/data/local/tmp/restore.sh" > NUL 2> NUL
...
5. Run CMD as admin. CD to Iovyroot folder.
Restore using tarestore.bat (tarestore.bat TA-2016-xxx.img) as soon as your device boots up to home screen and seems to be connected as ADB device.
( I checked this by running the windows device manager simultaniously)
Wait to end the process.
-->When the restore was sucessfull, the device shouldn't shutdown again.
6. Reboot. Your bootloader is now locked again (but able to unlock via OEM unlock). DRM keys/functionality is restored.
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
When I faced this problem I noticed it happened because I wiped TA options with Flashtool. Never do that if you don't want to lose TA partition and all other things connected to it. I could fix it only by flashing TA backup even though I hadn't the timing issue zegovernator had for flashing back TA.
I actually wonder why Flashtool allows to wipe these critical partitions/options
ric69 said:
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
Click to expand...
Click to collapse
I'm sorry for you. I would recommend updating back to MM since LP gives you immediate shut downs when recognising that your TA is lost/wiped. It's sometime a pain in the ass that stuff gets posted before testing. Nonetheless, you could still try to send in your device back to Sony Costumer Service if you are under warranty (after flashing .200, say that it is "broken" and keeps crashing). However, I would not trust on them sending you a new device.
jutphaas said:
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Click to expand...
Click to collapse
I sorry to say that, but if you lost your TA-backup or didn't even back it up before unlocking the bootloader there is no hope at the moment. You simply can't fastboot because of the Remote State: Locked. It keeps you from accessing the bootloader.
I found my iovyroot TA-backup.img file, I did have a .200 storefront ftf and tried it on that one, which was very anoying as it wants to start a demo , i found an other .200 ftf online which I tried, and the iovyroot seems to work, at that time no reboot, in service menu, the drm keys now seem fine there, Bootloader unlock allowed : No, Remote Lock State: unLocked , fastboot boot or oem unlock still seemed not working well i think that is what it said, (flashtool unlock always seems to, i did try) now i flash a new ftf and try my luck there with the unlock status.
flashing ftf 5.11 flashtool says
03/005/2017 05:05:49 - INFO - Loader : S1_Root_f936 - Version : MSM8994_50 / Boot version : S1_Boot_MSM8994_LA1.2_119 / Bootloader status : ROOTED
And now in 5.11 it also says bootloader unlocked : Yes Lost my drm again
So I am back in flashing and rooting (with drmfix etc) Android 7 again Thanks for sharing this solution!!
So you confirm that TA backup is the only solution to solve the "unlock allowed" bad state, don't you?
This is good for other people because when I faced the problem I was really scared to have messed up my phone!!!
i want to confirm the solution here
i had the same problem and the only way back of it was to downgrade to Lollipop and restore the TA-Partition
i dont think there is a solution if you did not backup your TA and have an image of it.
Yes, the TA restore is the only known solution, and I am glad Zegovernator shared his solution here
I'm getting an error when trying to unlock my phone's bootloader :
FAILED remote: Command not allowed.
I am copy/pasting "fastboot -i 0x0fce oem unlock 0xBEA3575C8951F712"
When I type "fastboot devices" it recognizes my device, and I installed all the drives from flashtool so I don't think its a driver issue.
I've tried using flashtool, the sdk, and minimal adb and falshboot. For flashtool I've tried adding the ulcode.txt to registerd devices folder.
I've tried different PC's and different cables. I've also tried it on androids 5, 6, 7, all of which I've flashed from the flashtool download tool (Custom UK versions).
I have USB Debuggin on, OEM unlock on, and Unkonwn Sources on. When I type *#*#7378423*#*# the phone says "Bootloader unlock allowed : yes".
A final thing to note is when I flashed android 7 the OEM unlock butto was grayed out - "Bootloader already unlocked", even though the *#*#.... code still said "Bootloader unlock allowed : yes".
I've searched all the forums and none of the fixes seem to work. Any help would be greatly appreciated - thanks!
Edit : I tried this on my old z1 compact and it worked, so its nothing wrong with my computer. I guess my z5 is just broken.
Nope, I am having the exact same issue you are. I have model E5823.
Got the unlock code off sony.
Trying everthing I can.. Can't get past that damn FAILED (remote: Command not allowed). error.
Installed 5 different fastboot/adb programs, sony drivers are latest. fastboot and adb do work, they see the device OK, it just won't accept any unlocking.
Unlockable is yes, in service settings view.
I am currently in the middle of trying to get the sony emma flashtool program to actually access my phone - it just gives me a "phone is locked" message..
going to try flashing a stock ROM with flashtool next.. but you're not giving me hope.
It is possible, because sony itself says it is, and there are other people out there who have done it. There must be a way.
Hey guys,
same here.
After fastboot fails to unlock the bootloader with
fastboot -i 0x0fce oem unlock 0xKEY
Click to expand...
Click to collapse
I tried it with flashtool and this post https://forum.xda-developers.com/showpost.php?p=58070067&postcount=34 and it worked!
But now I want to flash the modified kernel with TWRP and SuperSU with
fastboot flash boot kernel.img
Click to expand...
Click to collapse
but without success
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Same in Flashtool using option >>>>lightning icon"/Fastboot mode/Select kernel to Flash/path to boot.img.
Now bootloader is unlocked but DRM Keys still activ - if i can trust the system information.
Backup the TA-Partition was successful with iovyroot.
Whats wrong with this piece of plastic? I'm rooted all my Galaxy's before, but without any problems - this Z5c is annoying. And only because I want to change my MAC address, because my wife has same phone and same MAC Both in the same network isn't good.
Anybody who can help?
Thanks!
lfjriazr6kp6w95 said:
Hey guys,
same here.
After fastboot fails to unlock the bootloader with
I tried it with flashtool and this post https://forum.xda-developers.com/showpost.php?p=58070067&postcount=34 and it worked!
But now I want to flash the modified kernel with TWRP and SuperSU with
but without success
Same in Flashtool using option >>>>lightning icon"/Fastboot mode/Select kernel to Flash/path to boot.img.
Now bootloader is unlocked but DRM Keys still activ - if i can trust the system information.
Backup the TA-Partition was successful with iovyroot.
Whats wrong with this piece of plastic? I'm rooted all my Galaxy's before, but without any problems - this Z5c is annoying. And only because I want to change my MAC address, because my wife has same phone and same MAC Both in the same network isn't good.
Anybody who can help?
Thanks!
Click to expand...
Click to collapse
You helped me fix it! Turns out I had named my ulcode file ulcode.txt so it was actually ulcode.txt.txt
I still don't get why adb didn't work but flashtool does, though.
For your other point, I used this guide to flash a kernel.sin:
https://twigstechtips.blogspot.ca/2016/04/sony-z5-compact-root-without-losing-ta.html
Hope it helps, and thanks again!!!!!
lfjriazr6kp6w95 said:
>> I tried it with flashtool and this post ***pasted*** and it worked!
1.: Go to the folder where Flashtool was installed
2.: Open the folder named "custom"
3.: Open the folder named "mydevices" (if it exists, in my case Flashtool version 0.9.18.4)
4.: Right button, New, Folder. Name the folder with your device code.
5.: Open the folder created previously
6.: Right button, New, Text Document. Name the text document as ulcode
7.: Open the text document created previously
8.: Paste your unlock code and save
9.: Open Flashtools and try the BLU option again.
obs 1: the step #3 I think it depends on your Flashtool version, because it wasn't mentioned at the solution
obs 2: at the step #4 is mentioned your device code. your device code is showed in the log when you click the button BLU, at the "Current device", after your device model.
Search a line like:
09/045/2015 23:45:08 - INFO - Current device : C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17
in this case, the device code is AB100C2DE3 and this should be the new folder name (step 4)
Click to expand...
Click to collapse
I tried that method, it does not work. It SEEMS to work from face value, yes, but it is faulty I think.
Also, the location of the folder is wrong - it should go in /users/USERNAME/.flashtool/registeredDevices/
It 'unlocks' it during the flash stage of BLU in flashtool, yes, but it's supposed to do it in the fastboot stage according to other instructions I've read! It also freezes up and does not complete the operation unless I 'cancel' it - but it's supposed to go through a wipe process. It never does.
The system info has no status on whether or not it's unlocked or unlockable after flashtool 'unlocks' it using that method. Also, no other flashing can be done, because it returns the same Command not allowed error every time.
I believe fastboot is set up correctly as it returns getversion 0.5 and the device shows up in fastboot devices. I checked the IMEI was a correct one by going to imei.info. Don't know what else to do.
Why the heck are our devices refusing to unlock when others are doing it fine, and it's claiming to be unlockable?!?
I returned my Z5C and got a new one from the manufacturer and it's again refusing to unlock.
Hi,
I am late on this thread, but just buy a Z5C and face exactly that situation : no way to unlock the device ! Using flashtool and BLU results as a Rooting Status unknown, so I have to unlock the device using flashtool again...
The only thing I succeed is to flash the latest firmware with the help of XperiFirm. Still have "Bootloader unlock allowed : yes" but impossible to unlock it.
Has anyone found a solution for that problem ? Could it be related to a specific firmware to install ?
I am totally lost after two days of reading and unsuccessful attempts ; I would really like to install LineageOS on my new Z5C.
Any help would be greatly appreciated. Thanks.
Hi,
After some hours fighting with windows, drivers, signature (all in a VM), I switched back to Linux/Ubuntu. At least flashtool seems to work better (out of the box), and it asks me to reconnect the device in fastboot mode... But still the same error at the end. It adds "Maybe the OEM is not enabled", but it is of course (double checked).
But what means "Bootloader status : ROOTABLE" ? Did I miss something ?
Can somebody help please ? I contacted Sony support, but they don't support such operation...
Here is the log from flashtool :
====================
05/032/2018 17:32:18 - INFO - Please connect your device into flashmode.
05/032/2018 17:32:35 - INFO - Opening device for R/W
05/032/2018 17:32:35 - INFO - Device ready for R/W.
05/032/2018 17:32:35 - INFO - Reading device information
05/032/2018 17:32:36 - INFO - Phone ready for flashmode operations.
05/032/2018 17:32:36 - INFO - Opening TA partition 2
05/032/2018 17:32:37 - INFO - Current device : E5823 - CB5A274154 - 1299-1743_R12C - 1295-6639_32.2.A.5.11 - GENERIC_32.2.A.5.11
05/032/2018 17:32:37 - INFO - Closing TA partition
05/032/2018 17:32:37 - INFO - No loader in the bundle. Searching for one
05/032/2018 17:32:37 - INFO - Processing loader.sin
05/032/2018 17:32:37 - INFO - Checking header
05/032/2018 17:32:37 - INFO - Flashing data
05/032/2018 17:32:37 - INFO - Loader : S1_Root_f936 - Version : MSM8994_41 / Boot version : S1_Boot_MSM8994_LA1.2.2_42B / Bootloader status : ROOTABLE
05/032/2018 17:32:37 - INFO - Max packet size set to 4M
05/032/2018 17:32:37 - INFO - Opening TA partition 2
05/032/2018 17:32:37 - INFO - Start Reading unit 00 00 08 B2
05/032/2018 17:32:37 - WARN - ERR_SEVERITY="MINOR";ERR_CODE="0025";ERR_DYNAMIC="00000000";
05/032/2018 17:32:37 - INFO - Closing TA partition
05/032/2018 17:32:37 - INFO - Ending flash session
05/032/2018 17:32:37 - INFO - Now unplug your device and restart it into fastbootmode
05/033/2018 17:33:51 - INFO - Unlocking phone using key AF668B4FXXXXXXXX
05/033/2018 17:33:51 - INFO - ...
05/033/2018 17:33:51 - INFO - FAILED (remote: Command did not succeed)
05/033/2018 17:33:51 - INFO - finished. total time: 0.032s
05/033/2018 17:33:51 - WARN - Maybe the OEM is not enabled
05/033/2018 17:33:58 - INFO - Device disconnected
05/033/2018 17:33:58 - INFO - Device connected in fastboot mode
05/034/2018 17:34:07 - INFO - Device disconnected
I give up ! Tried almost everything (Win7x32, Win8.1x64, Flashtool v0.9.25 & 0.9.23 with ulcode.txt file created in user profile, Ubuntu, adb/fastboot command, from simple package, or Android studio), without any success. Some feedback though about Flashtool :
> Much easier to use the Linux version. On Ubuntu 18.10, it just works out of the box. I can easily flash the latest firmware ("Customized FR" in my case) though I downloaded it with Xperifirm on windows, as I did want to install mono on my Ubuntu desktop. At least I am now running Android 6.0.1.
> With version 0.9.25, I can use UBL button, Flashtool asks first for connect device in Flashboot mode (green light), then asks to disconnect and reconnect in Fastboot mode (blue But same error at the end : FAILED (remote: Command did not succeed). After a reboot, I can see "Rooting status : Unknown" in the service page.
> If I reflash, unknown rooting status is still there. I have to use Flashtool 0.9.23.2 (found link on another xda thread, only for windows) to "relock" the device and get back the "Bootloader unlock allowed : yes".
I don't understand what happens, what is the reason for that... Total mystery to me. There are so many posts about this issue, no one gives a real solution, Sony support does not care.
I am sad to be unable to install LineageOS on my device... Now will look how to "clean" Xperia Android as much as possible. Don't know if this is even possible. Don't know if I can root my phone, etc...
Last, why did I buy a Sony Z5C ? was looking for small (4.6") & afordable phone with good camera... Never thought I would be unable to install LineageOS.
That does sound frustrating. Have you checked the settings in the developer options? There's one there about "allow oem unlocking". If it's not set, you can't do it from fastboot, so maybe that's your problem? It's worth a try, at the very least.
tonsofquestions said:
That does sound frustrating. Have you checked the settings in the developer options? There's one there about "allow oem unlocking". If it's not set, you can't do it from fastboot, so maybe that's your problem? It's worth a try, at the very least.
Click to expand...
Click to collapse
Yes, I checked that for sure... Same for "Enable USB debug" and "Allow Unknown sources" in Security options.
Yesterday, as a last try, I follow that thread : I flashed old Lollipop firmware (E5823_32.0.A.6.200), backup TA partition, and tried unlock booloader again : same error FAILED (remote: Command did not succeed).
Probably something changed on Sony side that makes unlocking bootloader impossible ? That's what I think now.
Hmm, and in the service menu it says bootloader locking is allowed?
I'd be very surprised if Sony changed anything recently (if they even could, on a released phone), and I was able to do it successfully a few weeks back.
What's the error if you use an invalid unlock key? Maybe there's a typo (or request it from Sony again)? I know I'm grasping at straws, but I'm otherwise not sure. I had no difficulties at all...
tonsofquestions said:
Hmm, and in the service menu it says bootloader locking is allowed?
I'd be very surprised if Sony changed anything recently (if they even could, on a released phone), and I was able to do it successfully a few weeks back.
What's the error if you use an invalid unlock key? Maybe there's a typo (or request it from Sony again)? I know I'm grasping at straws, but I'm otherwise not sure. I had no difficulties at all...
Click to expand...
Click to collapse
Yes, Bootloader is OK, and providing a invalid unlock results in the same error : FAILED (remote: Command did not succeed).
From Sony website, you always get the same number when providing your EMEI.
Note there tones of threads about this issue, and really no clear solution, at least none from what I tried...
hi man!. Have you figure out how to unlock the bootloader? Same situation over here. This is my 3th xperia but first time facing this issue. Tomorrow I will install win 7 and will see if works
minos_cr said:
hi man!. Have you figure out how to unlock the bootloader? Same situation over here. This is my 3th xperia but first time facing this issue. Tomorrow I will install win 7 and will see if works
Click to expand...
Click to collapse
Unfortunately no. It is still the same, and I gave up for now, as I tried everything I could.
But I have a last plan : my Z5C is now running Android 6.0.1, which I installed myself using Flashtool & Xperifirm. Actually I got that phone with Android 5.1.1, and no upgrade was available when looking at system parameters, or even the Sony website). So I did it myself, using last package for French in Xperifirm.
And now, when looking at http://www.sonymobile.com/update, providing my EMIE code, it says my phone is up to date and running Android 7.1, which is wrong.
So I contacted Sony support for that, and they asked me to run a System -> Factory settings -> ReInit -> Clear everything. (or something simmilar).
I did not do it, because I am pretty sure this will not work, and I will probably go back to Android 5.1.1.
But I may contact the repair service (http://support.sonymobile.com/fr/repair/) and send my phone back to them asking for Android 7.1. I can complain for that, because my warranty is still valid !
My last hope is that when I will get back the phone from them, totally reinitialized, unlocking may work !!
I cannot do it for now, because I am going to move the next 2 months, but will try this when I am back. As I said, this is my last hope, unless someone find a solution to that problem.
Good luck to you, and keep us informed... By the way, which Android version are you running, and what says the Sony update site ?
man, yesterday I was frustrated too. Today, I installed windows 7 (it was a pain in the a**) and flashtool did the job like a champ.
pled said:
Unfortunately no. It is still the same, and I gave up for now, as I tried everything I could.
But I have a last plan : my Z5C is now running Android 6.0.1, which I installed myself using Flashtool & Xperifirm. Actually I got that phone with Android 5.1.1, and no upgrade was available when looking at system parameters, or even the Sony website). So I did it myself, using last package for French in Xperifirm.
And now, when looking at http://www.sonymobile.com/update, providing my EMIE code, it says my phone is up to date and running Android 7.1, which is wrong.
So I contacted Sony support for that, and they asked me to run a System -> Factory settings -> ReInit -> Clear everything. (or something simmilar).
I did not do it, because I am pretty sure this will not work, and I will probably go back to Android 5.1.1.
But I may contact the repair service (http://support.sonymobile.com/fr/repair/) and send my phone back to them asking for Android 7.1. I can complain for that, because my warranty is still valid !
My last hope is that when I will get back the phone from them, totally reinitialized, unlocking may work !!
I cannot do it for now, because I am going to move the next 2 months, but will try this when I am back. As I said, this is my last hope, unless someone find a solution to that problem.
Good luck to you, and keep us informed... By the way, which Android version are you running, and what says the Sony update site ?
Click to expand...
Click to collapse
I imagine (but can't say for certain) that whatever check Sony is using to display that info is either the last version that "called home" (maybe it needs the Xperia Companion software?), or the latest version that the phone was ever updated to. If you flash an old one with Flashtool (or worse: never connect to the internet with it), how on earth would you expect them to know the right version? Why would it even matter? The OS version is (largely) unrelated to the fastboot version, and shouldn't affect unlocking, other than the "allow oem unlocking" option in the developer settings.
I agree that the factory reset will leave it on the same OS; there's no reason it would upgrade.. I'm not sure why the OS wouldn't show updates available, maybe that customization version never had more releases. But is there any reason not to just download it and flash with Flashtool?
I couldn't find any other threads with people reporting problems - the majority of reports I saw were of successes. Not that I don't believe what you're seeing, mind you, just that I know there have been a lot of people getting things to work without a lot of issues.
minos_cr said:
man, yesterday I was frustrated too. Today, I installed windows 7 (it was a pain in the a**) and flashtool did the job like a champ.
Click to expand...
Click to collapse
Would be happy to know which Win7 (x32 or x64) and which flashtool version you used. Also if you setup the ulcode.txt file ?
---------- Post added at 09:59 AM ---------- Previous post was at 09:40 AM ----------
tonsofquestions said:
I imagine (but can't say for certain) that whatever check Sony is using to display that info is either the last version that "called home" (maybe it needs the Xperia Companion software?), or the latest version that the phone was ever updated to. If you flash an old one with Flashtool (or worse: never connect to the internet with it), how on earth would you expect them to know the right version? Why would it even matter? The OS version is (largely) unrelated to the fastboot version, and shouldn't affect unlocking, other than the "allow oem unlocking" option in the developer settings.
I agree that the factory reset will leave it on the same OS; there's no reason it would upgrade.. I'm not sure why the OS wouldn't show updates available, maybe that customization version never had more releases. But is there any reason not to just download it and flash with Flashtool?
I couldn't find any other threads with people reporting problems - the majority of reports I saw were of successes. Not that I don't believe what you're seeing, mind you, just that I know there have been a lot of people getting things to work without a lot of issues.
Click to expand...
Click to collapse
Well, this is a mystery to me. What I can say is that Sony website displays now :
Votre Xperia Z5 Compact est à jour !
Sortie : 32.2.A.5.11
Informations sur mon Android™
Android™ 7.1 Nougat est publié pour Xperia Z5 Compact.
Initially, I got the phone with Version 32.0.A.6.200. So they know somewhere I did an upgrade.
I would be happy to download the 7.1 version, but using Xperifirm, the only one I can find for the French country is the one I got, resulting in Android 6.0.1.
And because I have no knowledge at all on Sony specific things, I did try another firmware : I don't want to brick my phone.
Honestly, I have tried everything I could (Linux, Win, adb, flshtool, x32, x64, ulcode.txt, etc...) will always the same error, despite I agree most of people appears to success at one time. But most of the time without any clear explanation of what happen ! (except ulcode file story).
I read somewhere my problem could be related to the "Customization Version" (1299-1743_R12C in my case). Don't even understand what it could be related to, and how to change it.
What I expect is that Sony repair service will wipe everything on my phone, so that I could unlock it after it that.
Would be happy to know which Win7 (x32 or x64) and which flashtool version you used. Also if you setup the ulcode.txt file ?
Click to expand...
Click to collapse
I've personally used both Windows 10 (x64) and Linux. I used the latest version of Flashtool (0.9.25.0) and 0.9.24.4, though I couldn't tell you which combination I used on which OS.
[OS woes]
Let's start from the beginning. What OS are you trying to get to. Why?
Also note that there are multiple download versions in XperiFirm for your 1299-1743, make sure you're taking the right one.
I see 32.2.A.5.11, which it looks like you have (according to the earlier screenshot), which should be Marshmallow.
I also see 32.4.A.1.54, which should be Nougat.
Either should be straightforward to install with FlashTool (it sounds like you installed 5.11 with it?).
In the end, the customization option is mostly some regional differences - language, built-in apps, some VoLTE/fingerprint options for some regions, etc. Nothing significant ... or important if all you want to do is unlock it. That should be completely independent of the OS version.
Downgraing your OS and unlocking the bootloader should both end up resetting your phone/wipe the data.
So you should back up anything you want, and then mess around from there. I also fear the Sony Repair will wipe data, but it s also called "repair" so maybe it will backup/restore some of it. I'm not sure.
It's also possible that something is wonky with the OEM unlock setting, so wiping data will kick it back into working. It can't hurt to try, and is certainly easier than sending in a phone...
tonsofquestions said:
So you should back up anything you want, and then mess around from there. I also fear the Sony Repair will wipe data, but it s also called "repair" so maybe it will backup/restore some of it. I'm not sure.
It's also possible that something is wonky with the OEM unlock setting, so wiping data will kick it back into working. It can't hurt to try, and is certainly easier than sending in a phone...
Click to expand...
Click to collapse
Thank you for your advice. Will try again from scratch when I am back from travelling : 2 months in Asia ! At least, I will benefit of the "panorama" feature from the Sony camera that I may lose with LineageOS !