I cant unlock the boot-loader because it sayd the password is wrong
I gave moto the code i got from fastboot oem get_unlock_data
whitch retuned this:
Code:
(bootloader) A000002CE5E9CC00#54413936353043
(bootloader) 38485500585431303331000000#236B
(bootloader) D082967F45C8B0297B92C52C7DBCF8D
(bootloader) 774E9#A1AC35030F000008000000000
(bootloader) 0000000
the email returned with the unlock code:
Code:
6OJPYDKQQXR2DMSL5UHU
but the bootloader is rejecting it saying
Code:
(bootloader) Password incorrect!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 0.316s
what do i do?
Trying a different code. Still failed.
tried again from a diffrent PC and got a diffrent code...
Code:
ROV6AISPVK4CMKGSMLDR
but still replied as werong
I had the same problem. I solved it by following the instructions in this zip. It involves upgrading the bootloader, unlocking, then downgrading it.
Hello, due to an coruppted bootloader/cache/data point in my schield tablet i tried to doe fastboot
fastboot oe lock.
It was previously unlocked, somehow i read somewhere that relocking can fix corrupted bootloader of data partitions.
But when i try to relock it with fastboot oem lock i get
D:\nvidia\image>fastboot oem lock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Locking...
FAILED (remote: ()
finished. total time: 3.905s
Can someone please help me
Did you try with fastboot oem relock ?
Yes i did but get failed unkown error when i do
I extracted the "fastboot oem" commands supported by the Pixel 3 XL from the firmware.
I haven't tested these, since most don't work when the bootloader is locked:
Code:
$ fastboot oem dmesg
FAILED (remote: 'Fastboot OEM command (dmesg) is not allowed when locked')
Finished. Total time: 0.081s
Note that fastboot commands can brick and damage your phone. Be careful when testing.
Here's the list of commands. You can run them with "fastboot oem <command>".
Code:
setbrightness
get_config
set_config
rm_config
get_platform_info
set_platform_info
select-display-panel
esim_erase
esim_atp
uart
off-mode-charge
sha1sum
ramdump
ramdump_sahara
rma
dump-chipid
check-hw-security
HALT
set_display_power_mode
citadel
enable-factory-lock
factory-lock
ddrtest
continue-factory
dmesg
500 Internal Server Error said:
I extracted the "fastboot oem" commands supported by the Pixel 3 XL from the firmware.
I haven't tested these, since most don't work when the bootloader is locked:
Code:
$ fastboot oem dmesg
FAILED (remote: 'Fastboot OEM command (dmesg) is not allowed when locked')
Finished. Total time: 0.081s
Note that fastboot commands can brick and damage your phone. Be careful when testing.
Here's the list of commands. You can run them with "fastboot oem <command>".
Code:
setbrightness
get_config
set_config
rm_config
get_platform_info
set_platform_info
select-display-panel
esim_erase
esim_atp
uart
off-mode-charge
sha1sum
ramdump
ramdump_sahara
rma
dump-chipid
check-hw-security
HALT
set_display_power_mode
citadel
enable-factory-lock
factory-lock
ddrtest
continue-factory
dmesg
Click to expand...
Click to collapse
Any idea what OEM citadel does? I have no clue from a precursory look.
Must be super secret. I can't find anything on that
I couldn't find anything about that either.
Pixel 3 XL, haven't crashed it, YET
its in the crosshatch source code....https://android.googlesource.com/de...bfe57aaaf2cdd656a4476bbfb5c01314a09/device.mk
i believe citadel has to do with the new Titan security chip but I could be wrong
elliwigy said:
i believe citadel has to do with the new Titan security chip but I could be wrong
Click to expand...
Click to collapse
It does seem that is the only command new to the 3 XL compared to the 2xl. The latter does not have the Titan chip
NVM, I misunderstood.
Pixel 3 XL, haven't crashed it, YET
cmh714 said:
its in the crosshatch source code....https://android.googlesource.com/de...bfe57aaaf2cdd656a4476bbfb5c01314a09/device.mk
Click to expand...
Click to collapse
Am I pretty much blind or anything, but it doesn't exist anything regarding what the 'set display power mode' OEM command does within the link to the Crosshatch source(s), or..?
Can you "turn off" Titan and then run commands? Is that something to do with Citadel?
500 Internal Server Error said:
I extracted the "fastboot oem" commands supported by the Pixel 3 XL from the firmware.
I haven't tested these, since most don't work when the bootloader is locked:
Click to expand...
Click to collapse
This is the message I am getting when trying to use anyone of the OEM commands, in this case, the possible adjustment of the display power mode.
FAILED (remote: Fastboot OEM command (set_display_power_mode) is not allowed)
finished. total time: 0.378s
PS C:\Users\Christofferwassberg\Downloads\platform-tools_r28.0.1-windows\platform-tools> fastboot oem set_display_power_
mode
Is it any secret restrictions enabled somewhere that is denying us from modifying, or checking the stats of phone, from the bootloader level?
EDIT: Yes, my bootloader is unlocked.
xFirefly93 said:
This is the message I am getting when trying to use anyone of the OEM commands, in this case, the possible adjustment of the display power mode.
FAILED (remote: Fastboot OEM command (set_display_power_mode) is not allowed)
finished. total time: 0.378s
PS C:\Users\Christofferwassberg\Downloads\platform-tools_r28.0.1-windows\platform-tools> fastboot oem set_display_power_
mode
Is it any secret restrictions enabled somewhere that is denying us from modifying, or checking the stats of phone, from the bootloader level?
EDIT: Yes, my bootloader is unlocked.
Click to expand...
Click to collapse
Yes, the device checks whether the PRODUCTION fuse, in our case, likely just QCOM_SEC_BOOT is blown, and if it is it restricts a whole number of commands/functions.
npjohnson said:
Yes, the device checks whether the PRODUCTION fuse, in our case, likely just QCOM_SEC_BOOT is blown, and if it is it restricts a whole number of commands/functions.
Click to expand...
Click to collapse
Sounds like something that only Samsung would add, but Google? Nah..
xFirefly93 said:
Sounds like something that only Samsung would add, but Google? Nah..
Click to expand...
Click to collapse
That wasn't said in a questioning way lol -- its just how it is.
Every non-Chinese phone has Qualcomm Secure Boot enabled by that exact means (the SEC_BOT Fuse row). If you Google it, you'll find such. It's why we can't run custom bootloader's (exempting S-OFF HTC devices which are an odd and interesting case where QCOM secureboot only verfies very specific chunks of the bootchain the user doesn't normally touch).
QCOM secure boot is literally the industry standard lol - using the production state to limit OEM commands is new as of the Pixel 2, and correctly restricting them is new to the 3 series.
Could you maybe provide some info on how you extracted these commands from the firmware? Might be useful to me and others as well.
npjohnson said:
Any idea what OEM citadel does? I have no clue from a precursory look.
Click to expand...
Click to collapse
This is from sargo. I tried some of the other oem commands that sounded non-destructive, but got a lot of invalid oem command errors.
I didn't try any of these citadel commands, but they do sound interesting. I have no idea if they will apply to the blueline/crosshatch.
Code:
[email protected]:# fastboot oem citadel
...
(bootloader) citadel <command>
(bootloader) Commands:
(bootloader) rescue Try to rescue Citadel
(bootloader) state Print current Citadel state
(bootloader) reset Reset Citadel
(bootloader) reset-locks Reset AVB locks
(bootloader) version Print citadel OS version
(bootloader) reprovision Reprovision device after a RMA unlock
(bootloader) suzyq on|off Enable or disable SuzyQable
FAILED (remote failure)
finished. total time: 0.060s
Does anyone know how to use the citadel commands?
Im trying to restore a bricked 3a. so far here are my attempts
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe oem citadel
(bootloader) citadel <command>
(bootloader) Commands:
(bootloader) rescue Try to rescue Citadel
(bootloader) state Print current Citadel state
(bootloader) reset Reset Citadel
(bootloader) reset-locks Reset AVB locks
(bootloader) version Print citadel OS version
(bootloader) reprovision Reprovision device after a RMA unlock
(bootloader) suzyq on|off Enable or disable SuzyQable
FAILED (remote: '')
fastboot: error: Command failed
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe oem citadel rescue
FAILED (remote: 'no staged data, use fastboot stage <file>')
fastboot: error: Command failed
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe stage bootloader-sargo-b4s4-0.2-5402313.img
Sending 'bootloader-sargo-b4s4-0.2-5402313.img' (8349 KB) OKAY [ 0.355s]
Finished. Total time: 0.413s
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe oem citadel rescue
(bootloader) Recovering citadel - it may take a couple of minutes
FAILED (remote: 'failed to rescue citadel Bad Buffer Size')
fastboot: error: Command failed
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
zimmie said:
Does anyone know how to use the citadel commands?
Im trying to restore a bricked 3a. so far here are my attempts
Click to expand...
Click to collapse
Did you ever manage to make this work? I'm in the same situation
Hello,
So I have been using my Shield Tablet just fine for the past few years but now its locked on the Nvidia logo when it boots up, I've tried going into recovery mode to factory reset but then it just hangs on "No Command" I noticed that the bootloader is locked so I got ABD and fastboot. Once I setup the tablet to register in fastboot devices, I then use 'fastboot oem unlock' like it says to from the Nvidia support forums, but it fails and gives this command. Can anyone help me out to figure out what is wrong?
.... > fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: '(')
fastboot: error: Command failed
Any advice would be helpful
Malzra said:
Hello,
So I have been using my Shield Tablet just fine for the past few years but now its locked on the Nvidia logo when it boots up, I've tried going into recovery mode to factory reset but then it just hangs on "No Command" I noticed that the bootloader is locked so I got ABD and fastboot. Once I setup the tablet to register in fastboot devices, I then use 'fastboot oem unlock' like it says to from the Nvidia support forums, but it fails and gives this command. Can anyone help me out to figure out what is wrong?
.... > fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: '(')
fastboot: error: Command failed
Any advice would be helpful
Click to expand...
Click to collapse
What happens when fastboot flashing unlock
Hello everybody,
I need help to get my phone inbricked. Last year I installed LineageOS on my device and everything worked fine. Since I needed for some reason to relock my phone. I did via fastboot:
Bash:
fastboot oem lock
Since then my phone prints out: "The System has been destroyed ..."
I cannot flash anymore...
Code:
$ fastboot oem device-info
< waiting for any device >
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
finished. total time: 0.000s
What can I do to unlock the bootloader?