How to lock the bootloader? - Moto X Q&A

It continues saying No Valid PIV block in SP for system piv validation failed (system) Re-lock failure.
I use these commands
C:\Users\x\AppData\Local\Android\sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.131s]
finished. total time: 0.133s
C:\Users\x\AppData\Local\Android\sdk\platform-tools>fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.247s]
finished. total time: 0.249s
C:\Users\x\AppData\Local\Android\sdk\platform-tools>fastboot oem lock
...
(bootloader) Re-Lock Failure. See display.
OKAY [ 0.536s]
finished. total time: 0.538s
I don't have any stock rom of xt1052 RETDE, anyone can help me?

Related

[Q] Bootloader problems

Hello anyone! I'm looking for some help.
i have 4.2 originaly and i update the software to 4.4, after that i unlocked my bootloader, installed custom cwm and flash CM11+12 and when i want to return to stock rom i flashed stock rogers firmware 4.2, in this step everything is ok, when i try to update to 4.4 the phone turn off and trying to install the update and then is stoped and i have a messages :
Device is locked. statuts cide : 0 (why? i try to unlock it again but failed!!!)
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
im trying to re-flash the stock recovery, reboot and flash the rom 4.2 but failed !! i dont know what i can do to make the phone working again!
Well, i wish someone could help me, thanks a lot XDA
messages error
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.306s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.243s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1588 KB)...
OKAY [ 0.427s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.723s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.008s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash logo logo.bin
< waiting for device >
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (2563 KB)...
OKAY [ 0.467s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.585s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.953s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.069s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash recovery recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.972s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.090s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (717764 KB)...
OKAY [ 46.448s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 46.565s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53644 KB)...
OKAY [ 4.224s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 4.343s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.110s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.102s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'fsg' (212 KB)...
OKAY [ 0.390s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.505s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.129s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.105s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase customize
erasing 'customize'...
(bootloader) Invalid partition name customize
FAILED (remote failure)
finished. total time: 0.105s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase clogo
erasing 'clogo'...
(bootloader) Invalid partition name clogo
FAILED (remote failure)
finished. total time: 0.101s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot fb_mode_clear
wolf1985 said:
Hello anyone! I'm looking for some help.
i have 4.2 originaly and i update the software to 4.4, after that i unlocked my bootloader, installed custom cwm and flash CM11+12 and when i want to return to stock rom i flashed stock rogers firmware 4.2, in this step everything is ok, when i try to update to 4.4 the phone turn off and trying to install the update and then is stoped and i have a messages :
Device is locked. statuts cide : 0 (why? i try to unlock it again but failed!!!)
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
im trying to re-flash the stock recovery, reboot and flash the rom 4.2 but failed !! i dont know what i can do to make the phone working again!
Well, i wish someone could help me, thanks a lot XDA
Click to expand...
Click to collapse
wolf1985 said:
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
Click to expand...
Click to collapse
(bold in the quote added by me for emphasis)
YOU CAN NOT DOWNGRADE!!! It has been warned many times that you can not downgrade due to GPT.BIN and MOTOBOOT.IMG.
The only time it was safe was downgrading from 4.4 to 4.2.2. w/Camera Update OTA as part of the SlapMyMoto/MotoWpNoMo process for those with LOCKED bootloaders,
Based on the file name you are using (from your 2nd post), you are trying to flash the ORIGINAL SHIPPING 4.2.2 ROM which does cause a brick.
Now, based your two posts, It appears your phone is an XT1058 from Rogers Canada. Is that correct? or are you just trying to flash the Rogers Canada rom?
(If your phone really is an XT1058 from Rogers)... At this point, there are two options.
1. If you can get the phone to boot into fastboot mode, Download the 4.4.4 SBF for Rogers Canada (RCI) from -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 . (NOTE: If your phone is NOT a Rogers XT1058, then download the newst SBF for your phone's carrier and model!) and use the Requirements and Option 5 from -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and hope it works. If it works, it will flash you to stock 4.4.4. At that point, you can try to re-unlock the bootloader. And never think about flashing any other older ROM again!
2. If you can't get into Fastboot mode to flash, Go to -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 for help.
Thanks KidJoe
You save me !!!!! thanks so much for your help !!!!! :good::good::good::good:
Recovery not working
i try to enter into recovery but the phone turn on, the recovery not working|
wolf1985 said:
i try to enter into recovery but the phone turn on, the recovery not working|
Click to expand...
Click to collapse
The stock recovery work fine sorry, thank you for your help

fastboot oem get_identifier_token FAILED (remote: unknown command)

Hi All,
please help I want to fix my phone no root no custom firmware just to want device work again
i tried htcdev to unlock no luck
fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: -0.000s
**************
fastboot flash recovery recovery_cwm_hboot1.03.img
sending 'recovery' (6992 KB)...
OKAY [ 0.219s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.234s
my phone stuck in recovery mode please help HTC Desire 500

Moto 4x Stuck in Fastboot

Hello Guy's!
Iv'e got a Moto x4 and wanted to install/ upgrade to Android Pie. With locked bootloder and original stock rom.
I get a failed and permission denied message in the command prompt.
No i am stuck in a fastboot loop.
I can't ven go to the recovery mode, all i do a allway get back to the fastboot screen.
This moto is the retail 1900-7 version.
Any help would be appreciated!
Thank You!
Do you have acctual Motorola drivers? Commends are correct, this is drivers problem in my opionion. What happens if you type in fastboot while phonw is connected- fastboot device
I have all the drivers installed. But I also got into this situation.
How could this even happen with a locked bootloader?
I tried to unlock the bootloader with the received code, but I did not succeed.
Bilbaobao said:
Do you have acctual Motorola drivers? Commends are correct, this is drivers problem in my opionion. What happens if you type in fastboot while phonw is connected- fastboot device
Click to expand...
Click to collapse
With "fastboot devices" it is recoginised correctly.
retaras said:
I have all the drivers installed. But I also got into this situation.
How could this even happen with a locked bootloader?
I tried to unlock the bootloader with the received code, but I did not succeed.
Click to expand...
Click to collapse
I should have enable the bootloder unlock in dev. options but didn't...
Because the guide i followed was with locked bootloader to upgrade to Pie.
I did not reicive an ota to pie, so i was stuck on 8.0 oktober patch.
The only command that was suxessfull was: fastboot flash partition gpt.bin
Is there any chanche to reverse this command?
Everything else was denied by bootloder prmission.
So actually i think there souldn't be much damage here, or am i wrong...
added: "fastboot getvar all" image to 1st post
Check this thread: https://forum.xda-developers.com/moto-x4/help/fastboot-longer-t3899010
I don't know what ROMs there are for XT1900-7, but I'm sure they're around.
dougo007 said:
Check this thread: https://forum.xda-developers.com/moto-x4/help/fastboot-longer-t3899010
I don't know what ROMs there are for XT1900-7, but I'm sure they're around.
Click to expand...
Click to collapse
Thank you!
Going to try this. :good:
Well, after a bunch of hours i found a soluion...
See command promt:
PS C:\adb> fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.001s
PS C:\adb> fastboot oem fb_mode_set
...
OKAY [ 0.010s]
finished. total time: 0.010s
PS C:\adb> fastboot continue
resuming boot...
OKAY [ 5.330s]
finished. total time: 5.333s
PS C:\adb> fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
PS C:\adb> fastboot oem fb_mode_set
...
OKAY [ 0.009s]
finished. total time: 0.010s
PS C:\adb> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (37 KB)...
OKAY [ 0.002s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.113s]
finished. total time: 0.118s
PS C:\adb> fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.257s
PS C:\adb> fastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\adb>

huawei p30 pro - dead - no startup

the phone have:
- locked bootloader.
- frp on
- acces to fastboot, erecovery ()cant use dload method )
fastboot info
C:\adb>
C:\adb>fastboot oem oeminforead-PRELOAD_VERSION
...
(bootloader) :VOG-AL10-PRELOAD 9.1.0.12(C00R1)
OKAY [ 0.015s]
finished. total time: 0.016s
C:\adb>fastboot oem oeminforead-PRELOAD_VERSION
...
(bootloader) :VOG-AL10-PRELOAD 9.1.0.12(C00R1)
OKAY [ 0.022s]
finished. total time: 0.026s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
(bootloader) :VOG-AL10-CUST 9.1.0.160(C00)
OKAY [ 0.020s]
finished. total time: 0.024s
C:\adb>fastboot oem oeminforead-BASE_VERSION
...
(bootloader) :VOG-LGRP1-CHN 9.1.0.162
OKAY [ 0.015s]
finished. total time: 0.017s
hisuite dont have any update, funkyhuawei - same problem.
erecovery dont find any support.
Thanks

Zenfone 5 lock bootloader

Does anyone how to/if it's possible to lock the bootloader on my Zenfone 5 ZE620KL? I want my play protect certification back.
ExulVx said:
有没有人如何/是否可以在我的 Zenfone 5 ZE620KL 上锁定引导加载程序?我想要我的游戏保护认证。
Click to expand...
Click to collapse
这两个可怕的重锁码吓了我一跳,以为手机没电了。幸运的是,我找到了解决方案。你可能需要找个老股rec,跟着视频操作,不用拆机,重点解压。进入adb文件夹,生效
Boot the device into bootloader mode and try using "fastboot oem asus-lock" although I'm not 100% sure same command works on this model. Just note, if you lock your bootloader without your boot signing with your ROM, your device will boot loop. Also, you'll likely lose your data when re-locking so backing up all your data is highly recommended.
Asus official android 10 rom has a special feature: it can unlock/lock the bootloader directly from the command-line indefinitely.
1. Execute fastboot getvar secret-key-optto get the unlock token (fixed value) and record this value in a file (for example secret.txt):
C:\> fastboot getvar secret-key-opt
secret-key-opt: cOmVzgMMwUQmLuXs
Finished. Total time: 0.001s
2. Execute fastboot oem get_random_partitionto obtain the virtual partition to be flashed, each phone is different:
C:\> fastboot oem get_random_partition
(bootloader) eDJqGqlOezSA
OKAY [ 0.000s]
Finished. Total time: 0.001s
3. Execute to fastboot flash eDJqGqlOezSA secret.txt enable the trick "Unlock/Lock the bootloader indefinitely", in this example:
C:\> fastboot flash eDJqGqlOezSA secret.txt
Sending 'eDJqGqlOezSA' (0 KB) OKAY [ 0.005s]
Writing 'eDJqGqlOezSA' (bootloader) Begin to do frp unlock ...
(bootloader) FRP unlock successful !!!
OKAY [ 0.001s]
Finished. Total time: 0.013s
4. Execute to fastboot flashing get_unlock_ability check if 1 is returned (successfully enabled):
C:\> fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total time: 0.000s
5. After successful, your ZenFone 5 can use standard Android commands to lock/unlock the bootloader (you can also frp unlock):
Unlock: fastboot flashing unlockwithfastboot flashing unlock_critical
Locked: fastboot flashing lockwithfastboot flashing lock_critical
an examination:fastboot oem device-info
C:\> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) ABL Info: Q-ZE620KL202003
(bootloader) SSN: XXXXXXXXXXXXXXX
OKAY [ 0.008s]
Finished. Total time: 0.009s
Thanks to shakalaca
owais989 said:
Asus official android 10 rom has a special feature: it can unlock/lock the bootloader directly from the command-line indefinitely.
1. Execute fastboot getvar secret-key-optto get the unlock token (fixed value) and record this value in a file (for example secret.txt):
C:\> fastboot getvar secret-key-opt
secret-key-opt: cOmVzgMMwUQmLuXs
Finished. Total time: 0.001s
2. Execute fastboot oem get_random_partitionto obtain the virtual partition to be flashed, each phone is different:
C:\> fastboot oem get_random_partition
(bootloader) eDJqGqlOezSA
OKAY [ 0.000s]
Finished. Total time: 0.001s
3. Execute to fastboot flash eDJqGqlOezSA secret.txt enable the trick "Unlock/Lock the bootloader indefinitely", in this example:
C:\> fastboot flash eDJqGqlOezSA secret.txt
Sending 'eDJqGqlOezSA' (0 KB) OKAY [ 0.005s]
Writing 'eDJqGqlOezSA' (bootloader) Begin to do frp unlock ...
(bootloader) FRP unlock successful !!!
OKAY [ 0.001s]
Finished. Total time: 0.013s
4. Execute to fastboot flashing get_unlock_ability check if 1 is returned (successfully enabled):
C:\> fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total time: 0.000s
5. After successful, your ZenFone 5 can use standard Android commands to lock/unlock the bootloader (you can also frp unlock):
Unlock: fastboot flashing unlockwithfastboot flashing unlock_critical
Locked: fastboot flashing lockwithfastboot flashing lock_critical
an examination:fastboot oem device-info
C:\> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) ABL Info: Q-ZE620KL202003
(bootloader) SSN: XXXXXXXXXXXXXXX
OKAY [ 0.008s]
Finished. Total time: 0.009s
Thanks to shakalaca
Click to expand...
Click to collapse
Hello,
I can unlock my phone like you but I don't make TWRP...
For flash it was "good" but it's recovery original
and for boot in TWRP I have :
fastboot boot 'TWRP_3.3.0_ZE620KL_190428.img'
downloading 'boot.img'...
OKAY [ 0.637s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.638s
Can you help me please ?
owais989 said:
Asus official android 10 rom has a special feature: it can unlock/lock the bootloader directly from the command-line indefinitely.
1. Execute fastboot getvar secret-key-optto get the unlock token (fixed value) and record this value in a file (for example secret.txt):
C:\> fastboot getvar secret-key-opt
secret-key-opt: cOmVzgMMwUQmLuXs
Finished. Total time: 0.001s
2. Execute fastboot oem get_random_partitionto obtain the virtual partition to be flashed, each phone is different:
C:\> fastboot oem get_random_partition
(bootloader) eDJqGqlOezSA
OKAY [ 0.000s]
Finished. Total time: 0.001s
3. Execute to fastboot flash eDJqGqlOezSA secret.txt enable the trick "Unlock/Lock the bootloader indefinitely", in this example:
C:\> fastboot flash eDJqGqlOezSA secret.txt
Sending 'eDJqGqlOezSA' (0 KB) OKAY [ 0.005s]
Writing 'eDJqGqlOezSA' (bootloader) Begin to do frp unlock ...
(bootloader) FRP unlock successful !!!
OKAY [ 0.001s]
Finished. Total time: 0.013s
4. Execute to fastboot flashing get_unlock_ability check if 1 is returned (successfully enabled):
C:\> fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total time: 0.000s
5. After successful, your ZenFone 5 can use standard Android commands to lock/unlock the bootloader (you can also frp unlock):
Unlock: fastboot flashing unlockwithfastboot flashing unlock_critical
Locked: fastboot flashing lockwithfastboot flashing lock_critical
an examination:fastboot oem device-info
C:\> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) ABL Info: Q-ZE620KL202003
(bootloader) SSN: XXXXXXXXXXXXXXX
OKAY [ 0.008s]
Finished. Total time: 0.009s
Thanks to shakalaca
Click to expand...
Click to collapse
Thank you, this was really helpful!

Categories

Resources