Database Info

Unable to re-lock nexus-s through fastboot

i'm in the process of re-locking my bootloader in order to send it to Samsung for repair (home button not working). when i run the command line "fastboot oem lock", it just keeps hanging at "waiting on device" and nothing happens. i have the correct drivers installed. when i run "adb devices", it shows up the device. however, when i run "fastboot devices", it does not show up anything. any help on relocking my bootloader would be appreciated. Thanks!

Probably shouldn't be answering this here buuuuut...
adb reboot bootloader
and THEN
fastboot oem lock.
See what happens. You have to be in boot loader mode. Please move your questions to the Q&A section sir.

i did enter that command in order to get into fastboot. after that , i ran the command "fastboot oem lock" but it gets stuck at "waiting on device"

Update your drivers

Yea at this point I'd say its a connectivity problem. Drivers and or cable, but since you are getting adb devices to recognize, its not your cable. You should really use ubuntu, you would save yourself a lot of time, because you don't really have to deal with drivers like windows.

'sudo fastboot oem lock'
You need to be super user.

sure you went into bootloader and not recovery? because adb is seen in recovery and doesnt work in bootloader!

Need help getting in to fastboot

Hi!
I unlocked my phone - but when i type in the command "adb reboot bootloader"
it goes in to fastboot for a second, and then I get "bootloader unlocked" warning and after that it boots in to android.
How can I stop at fastboot to flash a custom recovery ?
Cheers!
EDIT:
NVM fixed

I am sure it was the right way.
How did you get it fixed?

I turned it off completely and after that, it accepted the command and stayed in fastboot.

Good to know, thanks for the information.

Unable to Unlock Bootloader (help!)

I've tried online guides to unlock bootloader, but messed up in some point and now I'm stuck.
1st. Download indepth test and reboot to bootloader within the app.
2nd. Tried adb devices successfully
3rd. Fastboot oem unlock nor Fastboot flashing unlock run (output: fastboot oem unlock failed "remote unknown command")
4th. Decided to make a factory reset (just becase I had to make an stupid desition)
Now I can reboot into fastboot again, because in depth test app won't install anymore. Installer says "Installation failed -An app with the same signature has already been installed"
I've unsuccessfully tried to flash stock rom from recovery but thein depth test seems to be "installed" without front user interface, also fasboot reboot bootloader get stuck in waiting for any device.
Can someone have a solution I already tried anything that comes to my mind.
Thanks.
I was able to solve the problem installing extractly the same apk.

The "fastboot oem unlock" dont work for me
What work on me 5pro is "fastboot flashing unlock"
Then flash twrp and vbmeta
To relock bootloader "fastboot flashing lock"
Source https://forum.xda-developers.com/realme-5-pro/how-to/bootloader-unlock-tutorial-t3985003

Other, might helpful source:
https://forum.xda-developers.com/realme-5-pro/development/rom-pixel-experience-t4053357

your device is corrupted and cannot be trusted.

Hello,
I have OP8 and its was rooted before, I did oem lock from fastboot then I got this message. " your device is corrupted and cannot be trusted"
i can't even flash stock rom. fastboot not accept command

OmanGhost said:
Hello,
I have OP8 and its was rooted before, I did oem lock from fastboot then I got this message. " your device is corrupted and cannot be trusted"
i can't even flash stock rom. fastboot not accept command
Click to expand...
Click to collapse
Sounds like the bootloader was modified, which breaks the digital signature.
Try unlocking the bootloader again and reboot. Go into developers options and turn usb debugging on. Then connect a cable between your computer and the phone. An RSA signature key should be presented. Check the box "always accept from this computer". Then try rebooting into fastboot and flashing stock.
Not sure of this will help but that's the best advice I can offer.
Cheers,
B.D.

Motorola Moto G8 "Your device is corrupt. It can't be trusted and will not boot."

I have a phone (Moto G8), I wanted to get rid of TWRP and I thought that just locking the bootloader will do it.
I only after saw that if you lock the bootloader with TWRP flashed you get into a boot-loop.
I found out that I can only use "fastboot boot" to boot into stuff because of the error stating: "Your device is corrupt. It can't be trusted and will not boot.".
Even if I go into the recovery mode the same error message would appear.
I know that by unlocking the bootloader I could get rid of that error but I don't have an unlocked bootloader and,
as most of you already know, after relocking the bootloader you need to enable OEM unlocking from developer options.
That was a huge problem since I couldn't access the phone at all besides the
bootloader, TWRP (although limited by the locked bootloader), and the default recovery.
That way I got into TWRP but I couldn't do much because of the locked bootloader.
Even if I had a full backup (which I didn't have) I couldn't do much.
I also tried downloading the full OTA image of an updated version of Android (I had Android 10 and I tried to go to Android 11)
to sideload but I couldn't find it. I found one but it was not a full OTA image (with bootloader, recovery, etc.) and I got an error message saying:
"Invalid zip verification signature" or something like that. Also, the error was happening at the start of the ADB sideload, I didn't know what else I could try.
So I have a question: Since I can use "fastboot boot" to bypass the error message,
is there maybe a bootable .img file that I can use to boot directly into the system and enable OEM unlocking?
Any help would be highly appreciated as well any other way to enable OEM unlocking through the bootloader or somehow ADB.