Question CANNOT re lock. - Sony Xperia 1 III

So I have an unlocked XPERIA 1 III. I was trying to relock it (for software updates) and couldn't. I first tried going to the fastboot menu (adb reboot fastboot) and tried using fastboot oem lock. This resulted in a command not supported in default implementation error.
This is not a surprise as I had the same problem when I tried to unlock my phone. I then did adb reboot bootloader. When I unlocked my phone this was the solution to the problem however now when I reboot to bootloader, I get a black screen or I just boot into the OS. neither will accept fastboot commands.
Anyone have a clue whats happening.
If it is relevant.
I run Riru, LSposed, Magisk, Xposed Edge Pro... OFC I am rooted (considering I am using these apps... yeah)
Plz help

Try fastboot flashing lock 0x <your bootloader unlock code>

Related

Dad in need of assistance with bricked KFHDX 7" 3rd Gen

Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
DadSteveo said:
Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
Click to expand...
Click to collapse
Unfortunately, there is no known recovery from this type of failure. I don't say that casually and wish there was a solution. The symptoms you report are both common and tell tale. The device is bricked.
I just replaced the motherboard on my hdx 8.9
It worked, I had to order a daughterboard also.
Total cost around $50 from where I got them.
Worth looking into. Watch teardown videos on YouTube and get the right tools.
Sent from my SM-N920T using Tapatalk
Too late?
DadSteveo said:
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Click to expand...
Click to collapse
Since fastboot appears to respond as expected on your device,
I'd be **very** interested in testing my long-standing theory
that 'fastboot update' __might__ work even on locked devices.
The "gotcha" is that we'd need to prepare the right package for
your Kindle. So, I gather it's an HDX 7" (3rd Gen?), i.e. "thor" model.
Do you remember what version of Fire OS you had installed?

Bricked and unable to boot into recovery

Hi all, yesterday I updated the bootloader of my OnePlus X and today I accidentally rebooted it into fastboot mode, when I tried to reboot the device it started a bootloop. Now I can't even boot into recovery but only in fastboot. I also tried to flash TWRP with command prompt but it says that the device isn't unlocked (strange i'm sure it was till yesterday) so I tried to unlock it with "fastboot oem unlock" but it says that oem unlock is disabled. Please help me
To unbrick your phone use this
You can then update to 3.1.3 Stock with the default bootloader.
You need to enable OEM-unlock in the developer-settings else patching the new bootloader may lock it again had the same problem.
Nordii said:
To unbrick your phone use this
You can then update to 3.1.3 Stock with the default bootloader.
You need to enable OEM-unlock in the developer-settings else patching the new bootloader may lock it again had the same problem.
Click to expand...
Click to collapse
Thank you! It worked

EMUI 4.1 Huawei Sensa H715BL boot loader

Has anybody ever gotten this boot loader to unlock on this specific model ? Ive been trying for days and I have the unlock code that DC unlocker furnished. ADB keeps saying failed and it sees my device. It has a funny boot loader with limited options, not like your normal boot loader. I would really like to unlock it and install twrp. Ive had great success with other phones and tablets but this one here is a booger. Any feed back or solutions would be great. Love this phone.just not EMUI...
Huawei Sensa on sale for $19.99 Refurb
I am looking for the same answers. I bought 5 of these phones at $20 each refurbed. I would like to use them for fun/stupid projects. Root would be required for some of my projects. TWRP would be very nice as well. If any one has any insight. I got on huawei support chat. They claim it is a Snapdragon 615 Soc , it is underclocked to 1.2Ghz to keep the heat issues to a minimum.
https://shop.straighttalk.com/shop/en/straighttalk/phones/st-huawei-sensa-lte-reconditioned
This phone have a root method ? H715BL version
ANYONE ?
Same question here. I got as far as getting a boot unlock code. I can't seem to get into fastboot. Oem Unlock is turned on. I did Volume down+Power from off, and I tried Volume down + inserting usb cable. No luck. I also ran the adb command "reboot bootloader". Still no fastboot.
When I run fastboot command while in the screen with the little android (volume down + Power) the phone is listed but "fastboot oem unlock" fails as an unknown command.
Do we really need to unlock the bootloader for root? Isn't it just for Twrp? I can do without Twrp since I'll have other rooted backup methods. I'll try a few root apps and see I guess.
gggirlgeek::: how did you manage get bootloader unlock code
To unlock bl need latest platform tool sdk to send fastboot commands
gggirlgeek said:
Same question here. I got as far as getting a boot unlock code. I can't seem to get into fastboot. Oem Unlock is turned on. I did Volume down+Power from off, and I tried Volume down + inserting usb cable. No luck. I also ran the adb command "reboot bootloader". Still no fastboot.
When I run fastboot command while in the screen with the little android (volume down + Power) the phone is listed but "fastboot oem unlock" fails as an unknown command.
Do we really need to unlock the bootloader for root? Isn't it just for Twrp? I can do without Twrp since I'll have other rooted backup methods. I'll try a few root apps and see I guess.
Click to expand...
Click to collapse
Please use latest platform sdk tools and run fastboot from there
Gggirlgeek:: Maybe fastboot reboot recovery … then from recovery reboot bootloader. I guess it can work just that i not have unlock code yet

CUBOT X12 - Bootloader returns to "locked" after unlock processing

Hi,
First I bricked my phone. Then I flashed the official stock rom using the SP Flash Tool. Then I started the phone and went directly to the build number and tapped it 7x. That made me a developer. Next I enabled USB developer options and enabled OEM bootloader unlocking. Then I connect my device to my Windows PC and start adb
Code:
adb reboot bootloader
That brings me into fastboot. There I use this command to unlock my bootloader:
Code:
fastboot oem unlock
After that I have tried two options:
Flashing twrp using
Code:
fastboot flash recovery x12-twrp.img
Which ends in a twrp bootloop. I guess because the cache was not wiped.
Using adb to reboot
Code:
fastboot reboot
. This however starts the rebootprocess and shows the Android man shortly - I guess that is wehere the cache is wiped - but then when I'm in the OS again everything is gone. It's like a factory reset. I can start over again by making myself a developer --> enable USB-developer options and allwo OEM bootlaoder unlock etc.
What am I doing wrong? I want to see the twrp screen on my phone. What should I do?
Many thanks for your help.

Stuck in bootmenu

Hey there,
I wanted to install twrp on my google nexus 5x.
Therefore I've unlocked the bootloader, entered fastboot mode and flashed the new recovery file.
I did this with adb fastboot tool.
No errors occured during the process, but after restarting the bootloader and entering the recovery mode, twr opens for a few seconds
and then gets closed again. Now I get an errormessage everytime (device software can't be checked... please lock bootloader) and I'm unable to do anything in the twr menu because it keeps getting closed
over and over again.
Now I can't even start my phone "normally" and can't get a connection with adb (no results when using: adb devices )
Some Bootmenu informations:
FASTBOOT MODE
PRODUCT_NAME - bullhead
.
.
.
SECURE BOOT - enabled
DEVICE STATE - unlocked
Does anyone know how to fix this issue?
Have you tried relocking the bootloader?
TechieComputers said:
Have you tried relocking the bootloader?
Click to expand...
Click to collapse
I can't connect via adb, so I can't relock the bootloader

Categories

Resources