Hi guys!
A little background. I am trying to unlock the bootloader, after seeing the root status: unknown, a second time after re-flashing back to stock rom. I could unlock the bootloader perfectly fine on the first try on firmware .251 but after updating to .260, the
Code:
fastboot -i 0x0fce oem unlock 0x<key>
command keeps failing. I was trying to flash a custom rom from FreeXperia, but after several attempts of not being able to send the system.img into the tablet, I decided to re-flash to stock using Flashtool, and had selected all the option for wipe and no exclude.
Which leads to my question: Does the
Code:
fastboot getvar all
retrieves anything at all? I also tried
Code:
fastboot getvar boot
fastboot getvar version-main
but also retrieves nothing.
This is the log:
Code:
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot devices
CB5A27L24G fastboot
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar all
all:
finished. total time: 0.007s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar version-main
version-main:
finished. total time: 0.006s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar boot
boot:
finished. total time: 0.013s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x0fce oem unlock 0x<key>
...
FAILED (remote: Command not allowed)
finished. total time: 0.014s
special flash command for the large partitions
flash system like outlined here:
http://developer.sonymobile.com/kno...ocked-xperia-devices/#build-aosp-lollipop-5-1
What do you expect from the getvar command?
DHGE said:
flash system like outlined here:
What do you expect from the getvar command?
Click to expand...
Click to collapse
Hi, thanks for the reply! I was trying to get back root and unlock bootloader after splendidly failing to successfully flash a custom rom to my Z4 tablet. I was searching around Google for the remote: command not allowed error, and actually found out that some of the users actually have output for the getvar all command, which was bootloader version information and other stuff. I should also point out that I have successfully unlocked the bootloader the first time but not the second time.
Another question: Will downgrading the firmware change the rooting status in the service menu?
Edit: Will re-flashing the stock rom lock the bootloader?
Going to try the link you posted! Will report back if there's any disaster that I've made.
you better search here on XDA and not on the web
SONY devices are a bit special in terms of partitions and bootloaders:
http://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
AFAIK bootloader stays unlocked whatever you flash after unlocking and only using Flashtool or SONY PC Companoin (the latter useless for unlocked devices) you should be on the safe side.
fastboot flash ... is a bit more dangerous but I would never flash anything were I have a hunch the developer is taking too many chances and were there is no README. And it really has to be for your specific device!
Sometimes I think people complaining here have flashed obscure phone ROMs to their tablet or Wifi ROM to their LTE device or any weird pre Lollipop root tricks (there are scams easiliy found via web search).
I just tried downloading the Flashtool from Sony's website. The Emma one.
However, the program says that my bootloader is locked for some odd reason. I'm inclined to think I am in a state where I can't unlock my bootloader any more though.
I also did enable My Xperia after I reflashed the stock rom during the initial setup, but immediately deactivated it. I wonder if this is causing it to have this error.
the fora for newer Xperia devices are plastered with MyXperia "accidents"
riveria said:
I also did enable My Xperia after I reflashed the stock rom during the initial setup, but immediately deactivated it. I wonder if this is causing it to have this error.
Click to expand...
Click to collapse
Emma is useless. Does not work on our Lollipop devices. Updates of Emma seem to be automatic but no improvement. Maybe they forgot to switch off their update bot.
You bricked your device.
From SONY (READ before you do risky things!!!):
After unlocking your device, you should not enable My Xperia (found in the settings menu under security on some devices running Android 5.0) as this might cause the device to malfunction.
Click to expand...
Click to collapse
source: http://developer.sonymobile.com/unlockbootloader/
DHGE said:
Emma is useless. Does not work on our Lollipop devices. Updates of Emma seem to be automatic but no improvement. Maybe they forgot to switch off their update bot.
You bricked your device.
From SONY (READ before you do risky things!!!):
Click to expand...
Click to collapse
Oh ok, so there's no chance of me unlocking the bootloader? The device still boots up normally though.
riveria said:
Oh ok, so there's no chance of me unlocking the bootloader?
Click to expand...
Click to collapse
I do not know.
I do not think so though - if you could unlock the MyXperia Software would be no protection at all. Thieves could just unlock the BL of the stolen device and lough at SONY.
The device still boots up normally though.
Click to expand...
Click to collapse
You are lucky then - there are reports where only a repair at SONY could revive the device:
http://fxpblog.co/2015/07/03/dont-destroy-your-unlocked-device.html
DHGE said:
I do not know.
I do not think so though - if you could unlock the MyXperia Software would be no protection at all. Thieves could just unlock the BL of the stolen device and lough at SONY.
You are lucky then - there are reports where only a repair at SONY could revive the device
Click to expand...
Click to collapse
Alright! Thanks for the help! I guess no more rooting for me then. I'll try reflashing the stock rom again and see what are the results.
Reflashing doesn't change the rooting status. So a reminder to all: Don't enable My Xperia.
Related
Hi all,
So I spent like the whole afternoon tryin to unlock bootloader on my MB860 (rooted) with no luck. This is international version with 2.3.4 system updated OTA.
I tried to unlock bootloader with fastboot - no luck:
Code:
OEM Unlock is not implemented
So i tried flash unlocked sbf file (intl-fix-try1.sbf), still no luck:
Code:
Failed to boot 1
So, I've flashed whole sbf file: 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
Phone started and all was same as before this operation,
next - I tried another full sbf's:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-Retail-GB.sbf
1FF-olympus_latam-user-2.3.6-4.5.2A-51_OLL-17.8-111109-release-keys-signed-BellMobility-CA-GAS_NA_OLYMPUSGBCANADABELL_P019.sbf
On both - failed to boot 1
so in the end only sbf that actually allows me to boot my cell is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
And the question is - how to get unlocked bootloader for this one?
You really should have searched and read up ahead of time. "Failed to boot XXX" is a perfectly normal and expected thing to happen when unlocking the BL. You shouldn't have messed with any more SBFs. You can still try running the fixer script as mentioned in that thread, hopefully you didn't mess it up too bad.
Thank you ravilov, but isn't this script only for ATT devices?
I am fairly certain it can be used on an international device as well.
Thanks, will try later on today, so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
stingu said:
so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
Click to expand...
Click to collapse
Yes.
stingu said:
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
Click to expand...
Click to collapse
Yeah, that's to be expected.
I think the worst case scenario would be that you won't be able to unlock, in which case you might be one of the unlucky people with the non-unlockable bootloader. If not, this script should help in unlocking your BL.
so, with the script and option number 3 i got the same thing:
Code:
(bootloader) OEM unlock is not implemented
OKAY [ -0.000s]
finished. total time: -0.000s
Or should i first flash small sbf and then use the script?
any other suggestions or am I stuck with soft 2.3.4?
You did flash the pudding/ihop SBF, right? If not, try doing that before you attempt to run oem unlock. If you did already... Well, I'm out of ideas then. I guess while waiting for someone else to chime in, you might as well start mentally preparing that you might indeed stay stuck with the stock firmware.
Well, made it unlocked, it was little bit tricky, so what I did:
-flashed IHOP
-got failed to boot 1 error message again - here, where i was not aware of - I pressed vol up and it switched to fastboot protocol support with boot error present
-did the script, fail to boot error was still there after reboot
-did those 2 points with flashboot application (whole instruction available here http://forum.xda-developers.com/showthread.php?t=1302423):
Code:
13.back in your command prompt window type "fastboot oem unlock" no quotes
14.You will now receive a warning along with a unique device ID
15.Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####•
fastboot oem unlock ####
fastboot reboot
Now its time to install CWM somehow...
I need to do a warranty exchange and my bootloader is unlocked, how can i relock it?
How can i relock it without using a USB?
Cannot relock without USB. You would need to run
fastboot oem lock
Sent from my LG-H901 using Tapatalk
Did you end up successfully locking it? Does it still display the 'unlocked' message on the logo boot screen?
-LBT- said:
Did you end up successfully locking it? Does it still display the 'unlocked' message on the logo boot screen?
Click to expand...
Click to collapse
Necro to say: YES, you can run "fastboot oem lock" to RELOCK the bootloader. "fastboot getvar unlocked" returns "unlocked: no".
Just tried it on my (two hour old) phone here.
Code:
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: no
finished. total time: 0.007s
C:\Assorted Programs\LGV10 Toolkit>fastboot oem unlock
...
OKAY [ 3.374s]
finished. total time: 3.374s
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.008s
C:\Assorted Programs\LGV10 Toolkit>fastboot oem lock
...
OKAY [ 1.764s]
finished. total time: 1.765s
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: no
finished. total time: 0.005s
hi guys
am not able to boot into bootloader to unlock it
I tried
adb reboot bootloader
and
adb reboot boot-loader
it's just making a restart
even I tired the manual way by pwr + - volume but didn't work
my model is LG-H960
any ideas!!
I'm going to be upgrading real soon and I'm stuck between the v10 and note 5. I must have root
Sent from my Nexus 6 using Tapatalk
How did you unlock the bootloader ?
melorib said:
How did you unlock the bootloader ?
Click to expand...
Click to collapse
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
KAsp3rd said:
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks, I will do it when/if I move to marshmallow
melorib said:
Thanks, I will do it when/if I move to marshmallow
Click to expand...
Click to collapse
Hi, Have you been able to Relcok it successfully? Does bootloader unlock still appears on your screen or it is gone?
Waxim1 said:
Hi, Have you been able to Relcok it successfully? Does bootloader unlock still appears on your screen or it is gone?
Click to expand...
Click to collapse
I dont think my phone bootloader was ever unlocked, at least I never noticed such message, but since I rooted in lolipop I get this funny screen everytime I reboot, even after upgrading to marshmallow
KAsp3rd said:
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks, it worked
if we relock the bootloader after doing root and debloat the stock rom, when they factory reset everything the root stay or just be gone after do the relock? are we able to unlock it again if we need TWRP?
other thing, the "cant check software for corruption" message will still appear or be gone when re-locked?
Howdy,
I have an xperia z3 tablet compact, aka SGP621, which has a locked bootloader. I have currently rooted my Z3TC using this method but I want to be able to flash a custom rom. I understand that the sim lock is separate from the bootloader, but I've read in a few threads on XDA that the device needs to be sim unlocked to unlock the bootloader. Even after using sony's unlock page, the process fails with fastboot giving the following error:
fastboot -i 0x0fce oem unlock 0xC8267EA2C7B838AF
...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
Click to expand...
Click to collapse
Can anyone confirm if the device needs to be sim unlocked to unlock the bootloader or if there is another method to unlock the bootloader ?
For anyone else curious, I got an unlock code from my service provider so the device is now sim unlocked. However, the bootloader is still unlocked. I am looking for a solution but its not looking good.
Also stuck with one of these. I can flash an ftf type file with the flash tool. Anything else it seems is out of the question.
Hi, I'm having issues trying to root brand new XZ1 following this guide: https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375 .
When I try to fastboot flash G8342 boot img I get "Flashing is not allowed in Lock State" error. I have made sure that OEM bootloader is unlocked in developer options...
I have tried updating drivers, using different boot img no luck. Anyone know what the solution is?
goldenboy23 said:
Hi, I'm having issues trying to root brand new XZ1 following this guide: https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375 .
When I try to fastboot flash G8342 boot img I get "Flashing is not allowed in Lock State" error. I have made sure that OEM bootloader is unlocked in developer options...
I have tried updating drivers, using different boot img no luck. Anyone know what the solution is?
Click to expand...
Click to collapse
Sounds like your bootloader is still locked, just because you flipped the OEM switch doesn't mean it's unlocked... Go read over here before you do anything else.. ( https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ )
lilbrat said:
Sounds like your bootloader is still locked, just because you flipped the OEM switch doesn't mean it's unlocked... Go read over here before you do anything else..
Click to expand...
Click to collapse
Thanks, that's a good guide. But when I try to run "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it always returns that the command's syntax is incorrect. Is this because I don't have 26.0.2 platform tools?
goldenboy23 said:
Thanks, that's a good guide. But when I try to run "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it always returns that the command's syntax is incorrect. Is this because I don't have 26.0.2 platform tools?
Click to expand...
Click to collapse
Did you get your unlock code?
lilbrat said:
Did you get your unlock code?
Click to expand...
Click to collapse
Actually I sorted that out, I was entering it with the brackets when I was meant to remove them. But when I enter it now, it doesn't tell me incorrect syntax, but tells me instead "unknown option: -- i" I wonder if this is an issue of using too new version of Platform tools? (I'm using 28.0.1)
Right I figured it out. Just omitted the -i option and it worked. So it looked like "fastboot oem unlock 0x<unlock code>"
no further issues cheers
I get same problem (bootloader unlocked, OEM unlocked .....But show I'm in lock state)
goldenboy23 said:
Hi, I'm having issues trying to root brand new XZ1 following this guide: https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375 .
When I try to fastboot flash G8342 boot img I get "Flashing is not allowed in Lock State" error. I have made sure that OEM bootloader is unlocked in developer options...
I have tried updating drivers, using different boot img no luck. Anyone know what the solution is?
Click to expand...
Click to collapse
Google 'unlock xperia bootloader', and check the xz1 compact forum for the DRM backup method for your phone. (I know you said you have a xz1)
You need to unlock the bootloader using a code from sony, and enter it via a fastboot command before twrp can be booted/installed.
Hello guys I'm trying to save my bricked P20 Lite but I am running into some issues. I unlocked the bootloader using testpoint but twrp won't flash or boot. Flashing gives me a flash write failure, booting gives me a invalid command error and I can't wipe cache either. I could really use your help.
Advanced07 said:
flash write failure
Click to expand...
Click to collapse
"flash write failure" - it might be due to a locked bootloader or hardware issue, AFAIK.
Try explaining what exactly happened, step by step.
-Alf- said:
"flash write failure" - it might be due to a locked bootloader or hardware issue, AFAIK.
Try explaining what exactly happened, step by step.
Click to expand...
Click to collapse
I unlocked my bricked P20 lite bootloader with the test pin method, then I tried to flash TWRP in fastboot and I got those errors.
Advanced07 said:
I unlocked my bricked P20 lite bootloader with the test pin method, then I tried to flash TWRP in fastboot and I got those errors.
Click to expand...
Click to collapse
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Have you enabled in Developer menu
"OEM unlock" ?
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Have you enabled in Developer menu
"OEM unlock" ?
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
1. Yes I do get that message that it's unlocked.
2. My device is bricked so that's impossible to enable. I unlocked it after it started bootlooping.
3. Gonna do those commands and tell the results
(bootloader) :ANE-LX1 9.1.0.372(C432E7R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
What shows Fastboot screen, at the bottom, Phone unlocked and FRP unlock ?
-Alf- said:
What shows Fastboot screen, at the bottom, Phone unlocked and FRP unlock ?
Click to expand...
Click to collapse
Phone unlocked and FRP unlock.
I unlocked the phone and the frp went away but it still gave me errors. Rebooted and frp lock was back + bootloader unlock gives error
Advanced07 said:
Rebooted and frp lock was back + bootloader unlock gives error
Click to expand...
Click to collapse
as i mentioned a month ago :
-Alf- said:
IMO it might be the HW problem , dead memory or damaged motherboard
Click to expand...
Click to collapse
Probably your emmc memory is fried. Not being able to unlock BL & FRP permanently is a sure sign. But I'm just an amateur and an android fan, maybe I'm wrong.
-Alf- said:
as i mentioned a month ago :
Probably your emmc memory is fried. Not being able to unlock BL & FRP permanently is a sure sign. But I'm just an amateur and an android fan, maybe I'm wrong.
Click to expand...
Click to collapse
It does have water damage could it be because of that? That would be unfortunate.
Advanced07 said:
It does have water damage could it be because of that? That would be unfortunate.
Click to expand...
Click to collapse
- known failure due to water exposure , although the write failures are intermittent.
P.S.: since January are you trying unbrick a water damaged phone?
-Alf- said:
- known failure due to water exposure , although the write failures are intermittent.
P.S.: since January are you trying unbrick a water damaged phone?
Click to expand...
Click to collapse
Nope i already know it was dead (repairs say it was total loss) but when I saw the new unlock method I thought it might be saved. Guess I was wrong but oh well I tried anyways.
Advanced07 said:
Nope i already know it was dead (repairs say it was total loss) but when I saw the new unlock method I thought it might be saved. Guess I was wrong but oh well I tried anyways.
Click to expand...
Click to collapse
Hi i have a query, the phone that you unlocked was it running on emui 9.1? If yes did you use potato nv to unlock? I wanna try it myself
apexashwin said:
Hi i have a query, the phone that you unlocked was it running on emui 9.1? If yes did you use potato nv to unlock? I wanna try it myself
Click to expand...
Click to collapse
It was running on the latest version and yes I did use potato NV
Advanced07 said:
It was running on the latest version and yes I did use potato NV
Click to expand...
Click to collapse
Hello thanks for your quick reply,I finally managed to unlock my p20 lite using potato nv.