I Unlocked someones Xperia Z and installed Cyanogenmod and TWRP on it some time ago. It was too unstable for their liking so they reset it to its stock settings using Sony Emma (or whatever its called).
Well now that they've got a nexus 6P, they've given the Xperia Z to me, so i tried to install TWRP and i get errors trying to overwrite the recovery.
Upon inspection of the bootloader lock settings i found it to say "bootloader unlockable: Yes", which indicates it is unlockable but not yet unlocked, and it continues to say this no matter how many times i attempt to unlock it.
Below is a demonstration attempt to unlock the phone and install TWRP:
Code:
[email protected] ~/Desktop $ sudo fastboot oem unlock 0xC431F679A4E1ECEB
...
OKAY [ 0.408s]
finished. total time: 0.408s
[email protected] ~/Desktop $ sudo fastboot erase recovery
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
[email protected] ~/Desktop $ sudo fastboot flash recovery twrp.img
sending 'recovery' (10656 KB)...
OKAY [ 0.337s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.339s
[email protected] ~/Desktop $ sudo fastboot flash boot twrp.img
sending 'boot' (10656 KB)...
OKAY [ 0.337s]
writing 'boot'...
OKAY [ 0.563s]
finished. total time: 0.900s
I've also tried it using flashtool on Windows and similarly it doesn't work.
I can't understand why it would work the first time, but now that its been factory reset the unlock doesn't work.
Have you tried with Xperia z dual recovery? (XZ dual-recovery) . It's very simple to install, for more info please refer to the official thread.
aaronkatrini said:
Have you tried with Xperia z dual recovery? (XZ dual-recovery) . It's very simple to install, for more info please refer to the official thread.
Click to expand...
Click to collapse
To do that i'd need a custom recovery, and i can't install one because the bootloader is locked and there is no recovery present on the device.
EDIT: ah i just saw the install exploit for unrooted devices. I'll give it a shot.
Didn't work unfortunately :/
I wasn't able to to use dual recovery to unlock the phone.
I downloaded and then installed a 10.3.x.x version of a stock xperia Z rom using flashtool, then i ran the dual recovery setup. EVERY operation reported that the file or folder didn't exist,and that the install had failed.
I was able to root the phone using Root Genius. I then installed TWRP manager and tried to install TWRP from there (this worked on that phone before), but it corrupted the rom so now it just freezes and restarts on the boot animation.
Recovering with Emma does not relock the bootloader. So bootloader should still be unlocked. Recovering with Emma also removes root so you need to root your device before you can install a custom recovery.
Sent from my E6653 using XDA-Developers mobile app
You are indeed right! although the problem appeared to be a locked bootloader at first, it now appears it was a corrupted recovery partition.
I, again, set the phone to a stock 10.1.x.x ROM (it was still corrupted from last time so i had to reset it again using Sony Emma) using flashtool and rooted using Root Genius. I then tried to use flashify to install XZ-dual-recovery but it told me the recovery partition was missing.... so i searched around and found the cure to my woes may be DooMKernel, so i set it up, and everything fell into place from there! below is how i believe it worked:
1. Used fastboot on my PC to install DooMKernel v22 as per the official page instructions
2. successfully booted into TWRP
3. used TWRP to install XZ-dual-recovery
4. successfully booted into CWM recovery
5. used CWM recovery to format all internal paritions
6. used CWM to install ROM and root
Thank you everyone for your help!
My xperia z has the 5.1.1 rom and is rooted.
The boot loader is locked and I couldn´t unlock it.
I cannot get into recovery with PC, neither with the buttons.
I like to install a custom 6.0 rom.
any suggestion?
thxs in advance for your support.
I've had a KFFOWI since Christmas but have been too busy to do anything with it. Unforutnately, this means that it has been updated to 5.1.4. Now I want to see what I can do with it.
I've read many posts on this excellent forum over the past few days about this device. I thought I'd start by trying to load the custom recoveries CM and TWRP.
I have ADB and Fastboot on a Linux box (I don't use Windows at all). I Can put the device into Fastboot mode; the way I do this is to boot to stock recovery and then choose "reboot to bootloader". I verify Fastboot from my Linux prompt like this:
Code:
$ sudo fastboot -i 0x1949 getvar product
product: FORD
finished. total time: 0.002s
I have downloaded the recoveries and try to boot them like this:
Code:
$ sudo fastboot -i 0x1949 boot TWRP_Fire_2.8.7.0_adb.img
downloading 'boot.img'...
OKAY [ 0.256s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.258s
However, as you can see, it does not work. I guess that the bootloader has been updated with one that does not have the boot command.
I also found this thread which would appear to confirm my suspicions but I can't find any more recent information about this.
So is this correct, that it's no longer possible to run a custom recovery like this? Or am I doing something wrong ?
I doubt it, but will downgrading to 5.1.2 fix this?
(I also read the KFFB thread and also this one thread about fastboot, but perhaps it is out of date with respect to this?).
ogpog said:
...So is this correct, that it's no longer possible to run a custom recovery like this? Or am I doing something wrong ?
I doubt it, but will downgrading to 5.1.2 fix this?
Click to expand...
Click to collapse
For the reasons stated in your full post custom recoveries can not be used/booted once FireOS has been updated beyond 5.0.1 via normal OTA (ie: no steps taken to protect bootloader).
As you probably know FlashFire can be used to install custom ROMs and take other actions normally performed in a custom recovery like twrp. However, stock recovery is still the only way to recover the device if the installed rom won't boot or unstable.
I see, so the ability to boot a recovery was lost after 5.0.1. I didn't catch that from my reading. I am working on getting FlashFire up and running but I need to get root first. I won't pollute this thread with my efforts in that regard.
Hi all,
I have debranded my EVA-L09 from Three UK, so that I can get faster OTA updates (and also to try to participate in future betas) - I'm now successfully on C432B166
However, I'd like to now re-lock my bootloader, but am struggling.
Whenever I boot to fastboot and run "fastboot oem relock ****************", I get the following response:
Code:
...
FAILED (remote: root type is risk)
finished. total time: 0.006s
If I try "fastboot oem lock ****************", I get the following:
Code:
...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
I have tried with "Enable OEM unlock" both enabled and disabled in Developer Options.
Can anyone give me any pointers on how to re-lock the bootloader?
Many thanks!
Sorry to bump an old thread. I'm currently having the same problems @ConfusedTA . Unfortunately I think it's difficult to re-lock bootloader without being on the same firmware that you were on when you unlocked it.
If anybody knows a way of forcing the bootloader to lock it'd be much appreciated!
Hey guys,
I just bought the Honor 10 lite and I am not really a big fan of Huawei's EMUI. That's why I wondered if there is already any custom ROM somewhere out there for this phone? I know it's pretty new and I couldn't find anything so far..
Would still appreciate any information, if somebody knows more about it.
Thanks guys :highfive:
You need to unlock bootloader 1st and that's currently impossible for honor 10 lite with Android 9
Even paid service isn't an option.
Niight Knight said:
You need to unlock bootloader 1st and that's currently impossible for honor 10 lite with Android 9
Even paid service isn't an option.
Click to expand...
Click to collapse
Oh alright, forgot that they stopped providing unlock-code's.. Hope someone figures out something, still not a friend of EMUI.
Thanks for the reply man ?
Niight Knight said:
You need to unlock bootloader 1st and that's currently impossible for honor 10 lite with Android 9
Even paid service isn't an option.
Click to expand...
Click to collapse
I just noticed that with the latest fw update as of today (9.0.1.142), the OEM unlock option can be now changed from the developer options menu, I guess it is still impossible to unlock it but well, now at least it lets you to change the option (before the update it wasn't even possible to do so). I'm not now able to but someone should give it a try to see if by any chance they messed up with OEM...
I think we'll have to wait many months before someone finds an hack to unlock bootloader. This is a very recent smartphone and also Huawei and Honor are not for modding, since it's everything locked and they're not providing unlock codes anymore. Too bad I discovered it after I bought it !
tomax80 said:
I think we'll have to wait many months before someone finds an hack to unlock bootloader. This is a very recent smartphone and also Huawei and Honor are not for modding, since it's everything locked and they're not providing unlock codes anymore. Too bad I discovered it after I bought it !
Click to expand...
Click to collapse
Hello. I have an unlocked Honor 10 Lite, but can't to install Magisk. Who can help me with this question?
Shlendr said:
Hello. I have an unlocked Honor 10 Lite, but can't to install Magisk. Who can help me with this question?
Click to expand...
Click to collapse
How did you unlock the bootloader?
To install magisk you need to install twrp first, then flash magisk zip from there. But there's no twrp for our device so far, maybe you can try running a twrp of a device with our same socket without installing it, from fastboot, and see if it works. For example
Code:
fastboot boot twrpfilename.img
If it works, then you can try flashing magisk from there.
tomax80 said:
How did you unlock the bootloader?
To install magisk you need to install twrp first, then flash magisk zip from there. But there's no twrp for our device so far, maybe you can try running a twrp of a device with our same socket without installing it, from fastboot, and see if it works. For example
Code:
fastboot boot twrpfilename.img
If it works, then you can try flashing magisk from there.
Click to expand...
Click to collapse
I got the phone from presentation. So, it is already unlocked from factory.
I'm not realy understand how can i use the twrpfilename.img? And where i can get this file? Did you have some manual?
I tried to flash twrpkirin.img from Honor 8x, but all system sections are encrypted. So i can't flash magisk.zip
---------- Post added at 08:59 AM ---------- Previous post was at 08:40 AM ----------
tomax80 said:
How did you unlock the bootloader?
To install magisk you need to install twrp first, then flash magisk zip from there. But there's no twrp for our device so far, maybe you can try running a twrp of a device with our same socket without installing it, from fastboot, and see if it works. For example
Code:
fastboot boot twrpfilename.img
If it works, then you can try flashing magisk from there.
Click to expand...
Click to collapse
I have an error:
C:\adb>fastboot boot JSNtwrp.img
downloading 'boot.img'...
OKAY [ 0.550s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.550s
I got the phone from presentation. So, it is already unlocked from factory.
I'm not realy understand how can i use the twrpfilename.img? And where i can get this file? Did you have some manual?
I tried to flash twrpkirin.img from Honor 8x, but all system sections are encrypted. So i can't flash magisk.zip
I have an error:
C:\adb>fastboot boot JSNtwrp.img
downloading 'boot.img'...
OKAY [ 0.550s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.550s
Click to expand...
Click to collapse
There's no manual, just try booting phone in bootloader mode then use that command I told in the previous post. It's just a try , there are no tutorials for this phone so far
TWRP Recovery Honor 10 Lite
tomax80 said:
There's no manual, just try booting phone in bootloader mode then use that command I told in the previous post. It's just a try , there are no tutorials for this phone so far
Click to expand...
Click to collapse
Already done. Got an error
Shlendr said:
Already done. Got an error
Click to expand...
Click to collapse
Ok then probably that version of twrp doesn't work with our phone , we just need to wait for a compatible one.
TWRP Recovery Honor 10 Lite
tomax80 said:
Ok then probably that version of twrp doesn't work with our phone , we just need to wait for a compatible one.
Click to expand...
Click to collapse
I can send all nesessary data of the phone, which will help to creat a workable TWRP. But who can do this?)
Shlendr said:
I can send all nesessary data of the phone, which will help to creat a workable TWRP. But who can do this?)
Click to expand...
Click to collapse
I have no idea sincerely, I think we just need to wait patiently till someone works on it . And it's also not granted that it's going to happen, since it's everything blocked.
guys, what about Android root apps? can those apps help?
TWRP Recovery Honor 10 Lite
cyrusiranmehr said:
guys, what about Android root apps? can those apps help?
Click to expand...
Click to collapse
No
locked after i got into bootloader
hey guys, i tried using bootloader first time and got myself into some situation:
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>adb reboot bootloader
adb server version (39) doesn't match this client (40); killing...
* daemon started successfully
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery_ramdisk twrp_bkl_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.711s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Does anyone know how to unlock this one? or do i have to buy unlock bootloader code?
from site named: global unlocking solutions.miiduu ???
GraveDanger said:
hey guys, i tried using bootloader first time and got myself into some situation:
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>adb reboot bootloader
adb server version (39) doesn't match this client (40); killing...
* daemon started successfully
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery_ramdisk twrp_bkl_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.711s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Does anyone know how to unlock this one? or do i have to buy unlock bootloader code?
from site named: global unlocking solutions.miiduu ???
Click to expand...
Click to collapse
Bootloader is locked and you can't flash anything till it's locked. There are paid services to unlock it but so far our device is not supported. Though there's no sense to pay a lot of money to unlock it, also if it was supported, just to have root (if you're lucky) , since there are no custom ROMs for Honor 10 lite. Our device is not made for modding. The only solution on my opinion is to wait patiently till someone finds an hack to unlock it for free, or sell your phone and buy a Xiaomi. You can unlock bootloader very easily and there are plenty of custom ROMs for it.
TWRP Recovery Honor 10 Lite
GraveDanger said:
hey guys, i tried using bootloader first time and got myself into some situation:
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>adb reboot bootloader
adb server version (39) doesn't match this client (40); killing...
* daemon started successfully
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery_ramdisk twrp_bkl_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.711s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Does anyone know how to unlock this one? or do i have to buy unlock bootloader code?
from site named: global unlocking solutions.miiduu ???
Click to expand...
Click to collapse
Hello. What the twrp_bkl_0.7.img? Where did you get it?) Is it workable?
You can always install a different launcher like Nova Launcher
this link claims you can use TWRP from Huawei P9 lite
https://unofficialtwrp.com/root-twrp-hry-lx1-hry-lx2-hry-al00
Hey all, new poster but long time user of the site, just never needed an account until today lol. Anyways, just got a Pixel 5a5G that I am trying to install LineageOS on. I am following the instructions from here, and once I get to the point of flashing the vendor_boot partition, I receive this:
Code:
PS C:\Windows\system32> fastboot flash vendor_boot C:\Users\bobby\Downloads\vendor_boot.img
target reported max download size of 268435456 bytes
sending 'vendor_bootb' (98304 KB)...
OKAY [ 2.225s]
writing 'vendor_bootb'...
FAILED (remote: Not allowed to flash (vendor_bootb))
finished. total time: 2.307s
When running fastboost unlock bootloader, I receive this:
Code:
PS C:\Windows\system32> fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.055s]
finished. total time: 0.056s
I have reflashed the stock firmware with the Android Flashing Tool to 13.0.0, both keeping the bootloader locked and unlocked. I have tried unlocking and relocking the bootloader. I used the utility's "full-flash" feature to flash both partitions, all to no avail. Research on here seems to point that the bootloader is locked, but fastboot says it isn't, settings is greyed out saying the bootloader is already unlocked, and fastboot mode on the phone says Device state: unlocked.
Any ideas?
Did you remove your screenlock and Google account before flashing?
Leberkuchen said:
Did you remove your screenlock and Google account before flashing?
Click to expand...
Click to collapse
Yes. I've flashed from a factory install with no passcode or account ever set. Same issue
From the output it's trying to write vendor_bootb??? Some combination of this should fix it:
-Make sure to use platform tools r33.0.3, the latest r34 has at least one known problem with fastboot and I don't trust it
-If you're using powershell you have to run the command as .\fastboot flash you can only run fastboot flash if you are in cmd
-Make sure both slots are on latest February firmware (probably not really necessary but a last ditch effort)