My device (Neo V mt11a) was unlocked (test pin method), rooted , custom kernel (Lupus), custom rom (cm10 nightlies).
I needed to send it for the lab (still in warranty).
So I needed to flash stock rom and relock the bootloader -
I flashed sony stock rom for mt11a (MT11a_4.1.B.0.587_Americana.ftf).
I checked with S1tool that the bootloader is still unlocked - shows letter "r" (as it should ).
I then flashed Xperia_Relock_bootloader.ftf according to this thread
which is said to not really relock but actually just deletes a key so the device "APPEARS LOCKED TO SE, BUT ACCEPTS UNSIGNED IMAGES".
I checked again with S1tool that the bootloader is locked- shows unlocked (letter "r")
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Right now the device is working, I need to send it to warranty.
So...
When I get the phone back - I don't want to brick it attempting to root, unlock etc....Will the same procedure work as before?
Much obliged..
Dial *#*#7378423#*#* and go to service info - configuration - rooting status and see if it says "bootloader unlock allowed". If yes it's relocked
The same procedure should work again
Sent from my Nexus 4 running Android 4.2.2
Related
mini-e10i bootloader phone lose signal, please help us
I unlocked my mini-e10i using s1tool , get this picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and then msm7227_setool2.cmd, and flash the E10_nAa-09_2.6.29.6-nAa-09.ftf, then cwm installed the rom of MiniCM7-2.1.7, but when turn on the phone, the simcard is inserted the phone doesn't recognize it? and when network is searched a message. lost the signal. I have been tried to flash to 2.1, but it still had no signal. How can I do?
please help me
And Who have the software is named setool2? please send me [email protected]. Thank u.
did you try to flash back to Stock via SEUS??
You shouldn't unlock bootloader because of incorrect requirements. You must have SEMC SIMLOCK SERTIFICATE instead of NOT RECOGNIZED SEMC SIMLOCK SERTIFICATE. Try to re-unlock bootloader using msm7227_semc file. Next time be more careful
Thanks so much. I save my phine.
Thanks so much. I save my phine.
I have mine x10 mini (e10i) and idk did i unlock bootloader so when i want to flash custom kernel it stops on reading header so if someone can help me plss reply...
Hi today i want to share the new sony trackID.apk from the Z1 system dump
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
install it as normal app or move to system/app giving right permission :good:
are you sure this will work in unlocked bootloader using official method from sony? or is it only for locked bootloader and testpoint unlocked bootloader only? because trackID from original ROM require a phone with DRM key which this key will be lost forever after you had unlocked your bootloader using official method but not testpoint.
xange said:
are you sure this will work in unlocked bootloader using official method from sony? or is it only for locked bootloader and testpoint unlocked bootloader only? because trackID from original ROM require a phone with DRM key which this key will be lost forever after you had unlocked your bootloader using official method but not testpoint.
Click to expand...
Click to collapse
Tried and tested on my Neo V unlocked officially and its WORKING!!!
Hi, I have problem with service menu. When I select BOOTLOADER UNLOCK CHECK I get message that hiddenmenu stopped working. I never tried to unlock my bootloader and I have stock ROM V20C. Is possible that I can't unlock bootloader now ? Before few months I didn't have this problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
flash firmware original
wlado93 said:
Hi, I have problem with service menu. When I select BOOTLOADER UNLOCK CHECK I get message that hiddenmenu stopped working. I never tried to unlock my bootloader and I have stock ROM V20C. Is possible that I can't unlock bootloader now ? Before few months I didn't have this problem.
Click to expand...
Click to collapse
Hey buddy you can unlock the boot loader anytime through fastboot.. Its a simple process... :good:
Codeplex said:
Hey buddy you can unlock the boot loader anytime through fastboot.. Its a simple process... :good:
Click to expand...
Click to collapse
via fastboot ? how ? I thought that fastboot will be available after bootloader unlock...
It is, technically you can access fastboot with omap4boot but you can't unlock from that or from normal fastboot because it is disabled until the boot loader is unlocked.
Sent from my LG-P769 using Tapatalk
Hi,
I just bought a sony xperia Z5compact from another guy that barely used it. He gave it to me with apparently, a stock ROM. But I dont know if the other guy did anything on the phone like rooting, unlocking, whatever.
But now I want to update from 6.0 to 6.0.1 and I cant do it. Neither in the phone, nor with the computer coz I get this error:
error: UEGetPhoneInfoFailure
UE_2003".
I checked more, and the phone has TWRP recovery and an Androdplus kernel. So it has been modified, but I dont know how to check the status of the bootloader or if it rooted.
I want to update the phone to 6.0.1. and I would like to have a stock rom and a locked bootloader. (because I read that custom rom and unlocking bootloader affect to the function of the camera).
How can I do it?
I am getting different information over the forum and the internet, and I am getting a bit lost...
the security thing from service info, stays like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Hi, i've got the same issue,
did you find any solution to update the phone ?
Thanks !
Can the bootloader be locked after a custom rom or a root, well if the stock rom and stuff is flashed again can it be locked?
Compec said:
Can the bootloader be locked after a custom rom or a root, well if the stock rom and stuff is flashed again can it be locked?
Click to expand...
Click to collapse
The answer is a bit complicated.
To lock the bootloader, a root of trust must be set - whereas a cryptographic key is installed, as well as a verification hash against which the boot image and system image may be checked for their integrity. This is always the case with factory firmware, but only some ROM developers have gone this far.
I am not sure if it is possible to lock the bootloader if the firmware is untrusted. If it is, one of 2 things will likely happen.
The device may fail to boot, and display this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or, it may boot, but display this message:
If however a custom root of trust has been set, the device will boot with this notice:
Ultimately, my advice is this: Do not try to lock the bootloader on anything other than OEM firmware, unless the developer of a custom ROM explicitly affirms that the device can be locked when using that firmware.