Related
Hi people, I've unlocked the BootLoader following 9Lukas5's instructions (http://forum.xda-developers.com/showthread.php?t=1254087)
And now I don't have radio anymore.
I checked first with the s1tool and it said "SEMC SIMLOCK CERTIFICATE". I've used the correct bat file and it said that it was unlocked successfully.
It was unlocked because I could install the latest Doom's kernel and Wolf's rom. But I didn't have radio.
I've been searching through the threads looking for answers, but all the methods people suggested, didn't work.
What I've tried: re-locking the bootloader and restauring the phone with seus (still no radio), unlocking again and trying several kernels, basebands and roms (versions 2.1 and 2.3, but still no radio).
Any tips?
Im on the exact same page searched a ton of times this forum and the net and no solution seems to work
Do u know how to check the status of your bootloader?
Sent from my X10S using XDA
I don't think so. How do I do that?
Type *#*#7378423#*#*, go to software info, look at your s1boot version (it will be an r and some numbers) if the r is uppercase (R) it is still locked. If it's a lower case r it has been unlocked
Sent from my X10S using XDA
It has an R..
So the bootloader isn't unlocked? Then how can I use Doom's kernel?
Solution found thanks to all of you guys.
First, use pc companion from sony to restore the mobile. (easy)
Then enable usb debug in the apps menu and with flash tools root the phone, it will restart.
Then with flashtools install the xrecovery (easy)
Again with flashtools in the plugins menu select unlock bootloader and run. Phone will restart a few times, do not unplug usb cable (i was unplugin after the first reboot) and it shall be done
Is it doomkernel for locked bootloader?
Sent from my X10S using XDA
I have radio now. I tried to do what BrixSat said and on the second try it worked
Thanks everyone for your help
i have a similar problem...radio signal of my X10 is so bad and low, when i am at home the signal is 1/4 or 2/4 bar (before was always 3/4 or 4/4).
repair with pc companion or seus did not help me...tried to relock BL, repair with pc companion and unlock BL but the problem still here.
it is antenna problem or software problem?
I only just rooted my x10 mini pro, now want to install mini CM9, but dunno how to check the manufacturing date of the phone, and if the bootloader is already unlocked or not. Please help
Oh got the Manufacturing date, its "11w13". Can it's bootloader be unlocked?
11wk13 is ok, but you need a compatible sim-lock certificate too.
Get S1Tool and post the output of the Identify-button, that might tell us more
SmG67 said:
11wk13 is ok, but you need a compatible sim-lock certificate too.
Get S1Tool and post the output of the Identify-button, that might tell us more
Click to expand...
Click to collapse
Here's the result...
Welcome to Si identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD 'BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING 51_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/008C"
LOADER VERSION: "R4A045"
MODEL (from GDFS): U20i
SOFTWARE VERSION: 1235-3411_2.1.1A.0.6
CUSTOM VERSION: 1240-8044_R46
FILESYSTEM WORLD-1-8_2.1.1.A.0.6
SERIAL NO: C13511TTEEV
SEMC SIMLOCK CERTIFICATE
Elapsed: 10 secs.
Cool attach your phone in flashtool and choose unlock bootloader from the plugins menu. Should work ok, but make sure to boot your phone first and check if you've still got network-connectivity
If you don't, relock the bootloader with S1Tool Restore-button, but I think you'll be ok.
If that's ok, you can flash whatever is appropriate for your phone
Good luck
SmG67 said:
Cool attach your phone in flashtool and choose unlock bootloader from the plugins menu. Should work ok, but make sure to boot your phone first and check if you've still got network-connectivity
If you don't, relock the bootloader with S1Tool Restore-button, but I think you'll be ok.
If that's ok, you can flash whatever is appropriate for your phone
Good luck
Click to expand...
Click to collapse
Thanks, I'll give it a shot later tonight after reading a bit more about it
Don't wanna screw it up... Will post the result later.
Edit: There is no RESTORE button in the S1tool, just 3 buttons actually, DO JOB, STOP and QUIT.
SmG67 said:
Cool attach your phone in flashtool and choose unlock bootloader from the plugins menu. Should work ok, but make sure to boot your phone first and check if you've still got network-connectivity
If you don't, relock the bootloader with S1Tool Restore-button, but I think you'll be ok.
If that's ok, you can flash whatever is appropriate for your phone
Good luck
Click to expand...
Click to collapse
Uhmm :S something went wrong... i think.
Result...
Code:
24/039/2012 01:39:38 - INFO - <- This level is successfully initialized
24/039/2012 01:39:38 - INFO - Flashtool Version 0.8.0.0 built on 2012-05-27 21:57:12
24/039/2012 01:39:38 - INFO - You can drag and drop ftf files here to start flashing them
24/039/2012 01:39:43 - INFO - Device connected with USB debugging on
24/039/2012 01:39:45 - INFO - Connected device : U20
24/039/2012 01:39:45 - INFO - Installed version of busybox : N/A
24/039/2012 01:39:45 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
24/040/2012 01:40:33 - INFO - Please connect your device into flashmode.
24/040/2012 01:40:39 - INFO - Device disconnected
24/041/2012 01:41:04 - INFO - Opening device for R/W
24/041/2012 01:41:05 - ERROR - Drivers need to be installed for connected device.
24/041/2012 01:41:05 - ERROR - You can find them in the drivers folder of Flashtool.
24/041/2012 01:41:06 - INFO - Flashing loader
24/041/2012 01:41:06 - INFO - Ending flash session
24/041/2012 01:41:06 - WARN - Cancelled
24/041/2012 01:41:06 - INFO - Device connected in flash mode
24/042/2012 01:42:17 - INFO - Device disconnected
24/042/2012 01:42:26 - INFO - Device connected with USB debugging off
24/042/2012 01:42:26 - INFO - For 2011 devices line, be sure you are not in MTP mode
24/044/2012 01:44:03 - INFO - Device disconnected
24/045/2012 01:45:42 - INFO - Device connected with USB debugging on
24/045/2012 01:45:49 - INFO - Connected device : U20
24/045/2012 01:45:49 - INFO - Installed version of busybox : N/A
24/045/2012 01:45:49 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
24/045/2012 01:45:52 - INFO - Pushing D:\Program Files\Flashtool\.\devices\U20\busybox\1.19.0\busybox to /data/local/tmp/busybox
24/045/2012 01:45:56 - INFO - Remounting system read-write
24/045/2012 01:45:57 - ERROR - Error mounting /system rw
24/045/2012 01:45:57 - INFO - Root Access Allowed
Fas1h said:
Thanks, I'll give it a shot later tonight after reading a bit more about it
Don't wanna screw it up... Will post the result later.
Edit: There is no RESTORE button in the S1tool, just 3 buttons actually, DO JOB, STOP and QUIT.
Click to expand...
Click to collapse
There is a newer version of S1Tool somewhere that adds that functionality
Can't remember which link i got it from though
On the other side: see if busybox is installed now, when you connect your phone to flashtool it should give a version-number in the line: installed version of busybox, instad of N/A. I guess you managed to install the proper drivers for your phone?
SmG67 said:
There is a newer version of S1Tool somewhere that adds that functionality
Can't remember which link i got it from though
On the other side: see if busybox is installed now, when you connect your phone to flashtool it should give a version-number in the line: installed version of busybox, instad of N/A. I guess you managed to install the proper drivers for your phone?
Click to expand...
Click to collapse
Oh yes, found the new S1tool it has all the buttons.
Nopes, busybox is not installed... Do I download it over market? Oh well I'll search it and install it. As for the drivers, yes, installed both x10minipro and flash mode drivers.
you can install busybox from flashtool no need to search for it...
SmG67 said:
you can install busybox from flashtool no need to search for it...
Click to expand...
Click to collapse
Yippeeeeeeeeeeeeeee! Thank you man
All done.
Code:
Welcome to S1 tool.
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "r4A060"
MODEL (from GDFS): U20i
SOFTWARE VERSION: 1235-3411_2.1.1.A.0.6
CUSTOM VERSION: 1240-8044_R4B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: CB511TJTEV
SEMC SIMLOCK CERTIFICATE
Elapsed:15 secs.
The small "r" I suppose means the bootloader is unlocked. Right?
Now if you'd be kind enough to help me chose which rom to go for? Lol, or just temme which you are using and WHY! Also why not MiniCM 9?
Fas1h said:
Yippeeeeeeeeeeeeeee! Thank you man
All done.
The small "r" I suppose means the bootloader is unlocked. Right?
Now if you'd be kind enough to help me chose which rom to go for? Lol, or just temme which you are using and WHY! Also why not MiniCM 9?
Click to expand...
Click to collapse
Yeh, your bootloader is unlocked I guess you still have network-access too.
I'm not sure what to go for as far as ROMS for the x10mini-pro is concerned, because i don't have that phone, but the most popular roms will be on the first page of the development section. It just depends on how you want your phone to work and look.
As for MiniCM9: is still in early development, although the progress made is very impressive it leaves a few things that will not work properly, most notably video recording and playback and battery life could be improved too, so if you need your phone for normal every day use, I would try something more stable and proven. On the other hand, if you can live with those deficiencies, by all means, having ICS on your little phone is just way too cool. Happy Hunting
SmG67 said:
Yeh, your bootloader is unlocked I guess you still have network-access too.
I'm not sure what to go for as far as ROMS for the x10mini-pro is concerned, because i don't have that phone, but the most popular roms will be on the first page of the development section. It just depends on how you want your phone to work and look.
As for MiniCM9: is still in early development, although the progress made is very impressive it leaves a few things that will not work properly, most notably video recording and playback and battery life could be improved too, so if you need your phone for normal every day use, I would try something more stable and proven. On the other hand, if you can live with those deficiencies, by all means, having ICS on your little phone is just way too cool. Happy Hunting
Click to expand...
Click to collapse
Umm, last question then. I cant post in most sections just yet...
I think I'll stick to MiniCM7 for now, will surely give MiniCM9 a shot sometime later on, after I get a bit used too to this phone. So anyways, on this page http://forum.xda-developers.com/showthread.php?t=1415026
Code:
Download the MiniCM7-xxx.zip from the release link that follows
Backup your /data contents: contacts, apps, sms, etc. or backup via recovery
Move the MiniCM7-xxx.zip to the root folder of your sdcard. Download the suggested Google Apps for CM7 from here (check http://goo-inside.me/gapps/ if you want to experiment with other gapps versions)
Unlock your bootloader, if you haven't already. Check http://forum.xda-developers.com/show....php?t=1254225 for a nice tutorial
Flash the nAa kernel using Flashtool. To to this:
- Turn off your phone
- Start the Flashtool\X10FlashTool.exe and select Flash. Then select the U20_nAaxxx kernel firmware (this flashes both the kernel.sin and the loader.sin)
- Keep the back button pressed while connecting the usb cable. Flashtool should detect your phone and flash the kernel.
- Once done, disconnect the usb cable and power on the phone.
Once the logo appears, press the back button repeatedly to enter CWM.
- Select 'backup and restore -> Backup'
- Select 'wipe data/factory reset' (RECOMMENDED)
- Flash the MiniCM7-xxx.zip. To do this, Select 'install zip from sdcard -> choose zip from sdcard' and select the MiniCM7-xxx.zip
- Flash gapps
Reboot (first boot will take ~2 mins)
Once your device has booted, you can navigate to CM Settings -> System -> Update notifications and select 'Register'. This way you can get update notifications on new versions of MiniCM7!
So it directly jumps to flashing the kernel and then booting up with CWM. So I am assuming the kernel is somehow linked to CWM or the kernel will automatically install the CWM recovery as well?
All custom kernels have CWM built in so it will work irrespective of the ROM you are using.
SmG67 said:
All custom kernels have CWM built in so it will work irrespective of the ROM you are using.
Click to expand...
Click to collapse
After flashing the kernel, i was rather familiar with the steps. Everything worked out as expected Thanks for the help. Am on MiniCM7 now with nAa-11 kernel.
Hello, and sorry if i am posting in wrong place, but I've just get a new(for me it is) x10 mini pro, and i also want to unlock my bootloader.
Previously i had xperia x8 with 11w44 prod. date, and i was unable to unlock its bootloader.
With x10minipro, s1tool says SEMC-SIMLOCK CERTIFICATE, so i can unlock its bl, but when i removed my battery i just saw, that my x10minipro-s production date is 11w43, and now i am a little bit confused about bl unlocking it.
Can somebody tell me that this x10minipro is bootloader unlockable?
aj-alberto said:
Hello, and sorry if i am posting in wrong place, but I've just get a new(for me it is) x10 mini pro, and i also want to unlock my bootloader.
Previously i had xperia x8 with 11w44 prod. date, and i was unable to unlock its bootloader.
With x10minipro, s1tool says SEMC-SIMLOCK CERTIFICATE, so i can unlock its bl, but when i removed my battery i just saw, that my x10minipro-s production date is 11w43, and now i am a little bit confused about bl unlocking it.
Can somebody tell me that this x10minipro is bootloader unlockable?
Click to expand...
Click to collapse
Are you sure it says 11w43 and not 10w43? If it is 11w43 i wouldn't risk it.
SmG67 said:
Are you sure it says 11w43 and not 10w43? If it is 11w43 i wouldn't risk it.
Click to expand...
Click to collapse
yes it is 11w43. but i found another date on its back, near to the speaker, and it says 11w20.
aj-alberto said:
yes it is 11w43. but i found another date on its back, near to the speaker, and it says 11w20.
Click to expand...
Click to collapse
Dunno what that is, mine also says Date: 10W46 beside the speaker and under the battery 11W13.
Just disregard whatever it says beside the speaker. You were supposed to check under the battery only.
Fas1h said:
Dunno what that is, mine also says Date: 10W46 beside the speaker and under the battery 11W13.
Just disregard whatever it says beside the speaker. You were supposed to check under the battery only.
Click to expand...
Click to collapse
thanks for the information. So i got again a phone, that is unlockable.
aj-alberto said:
thanks for the information. So i got again a phone, that is unlockable.
Click to expand...
Click to collapse
un-unlockable
Hi I've tried searching about quite a bit but can't seem to find the correct solution.
I've had the bootloader unlocked once by following DoomLords instrucions but locked it as an upgrade popped up on my pc companion, now I can't seem to unlock it again.
I've followed the same process as before, even through the sony bootloader unlock site (this gave me the same unlock key as before) I've attached my error from the command prompt screen.
Anyone??
the screenshot is not readable.
maybe you forgot to remove the last number form the unlock key.
or flash a firmware first then try again
Sorry here's another screen.
I tried to re unlock the bootloader after an update via pc companion, it didn't work then.
I've now flashed ICS onto the phone with flash tool and unlocking the bootloader still doesn't work.
I've tried taking the last digit off the unlock code, with no luck!
Random post to keep the thread alive, hopefully someone will know whats up
Last try, anyone?
You're not using 0xFFFFFFF as the key are you?
No definitely not. That was the error the 2nd time round trying.....
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!
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 !