Database Develop

[Q] HTC Raider Stuck in hboot cant relock

**UPDATE: Wednesday 2:30pm GMT-5
I have 9 hours of research in on this project and I am learning lots.
I have a 2nd Raider and I have unlocked and relocked the bootloader, installed CWM then WCX and did backups with them.
I am now working on getting the default image and renaming it to PD98IMG.zip but I am thinking I need to re-lock??? (I think I needed to have it unlocked -- weird) the bootloader before I do that?
>>>>>>>>>>>>>>>>>>>>>>>>
Bought a HTC soft-bricked phone and trying to get an image on it. Here is what I have done so far. Any tips will be received with thanks giving.
Here is what my phone says at hboot:
*** UNLOCKED ***
HOLIDAY PUT SHIP S-ON RI,
HBOOT-1.83.0014
MICROP-0360
eMMC-boot
Sep 21 2011, 15:34:37
My HTC Raid (I am in Canada so don't know if this is a Bell or Rogers or who knows, I bought it white screened) is stuck in white screen with HTC logo. I took the following steps:
Downloaded RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe
from
http://hotfile.com/dl/145619873/245....77.551061.02L_release_219561_signed.exe.html
--Ran RUU and the program noted I have image version 1.65.566.3 on my Radier
--Selected Update and tried to update to 1.65.631.1
--The Raider came up in the HTC/black backgroup and then gave the following ERROR[155] UNKNOWN ERROR.
--After exiting RUU and disconnecting the cable the phone shows along with the general hboot information on the phone "RUU, Security fail! Update fail!"
--Restarted phone with volumn down and power and it came up in hboot and showed the following error:
SD Checking
Loading...[PH39DIAG.zip]
No Image!
Loading...[PH39DIAG.nbh]
No image or wrong image!
Loading...[PH39IMG.zip]
No image!
Loading...[PH39IMG.nbh]
No image!
Loading...[PH39IMG.tar]
No image!
Loading...[PH39IMG.aes]
No image!
--I tried re-locking the bootload with "fastboot oem lock" and I get a "..." after the command and nothing else happens. Waited for 10 minutes.
--Also "adb devices" shows no devices.
--Installed HTCSync, started HTCSync, pluged in hbooted HTC Raider, Drivers Software Installation diolog box shows "My HTC" driver installed, still nothing when I run "adb devices"
--Ran "fastboot oem lock" and get the following.
(bootloader) Lock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.026s
--When I run Hasoon2000s HTC Vivid AIO Kit v1.2 Relock Bootloader I get the following.
INFOLock successfully
FAILED (status read failed (Too many links))
finished. total time: 0.022s
--With Hasoon2000s HTC Vivid AIO Kit v2.0 I get.
INFOLock successfully
FAILED (status read failed (Unknown error))
finished. total time: 0.023s
--reboot into hboot and status still "*** UNLOCKED ***"

MORE BAD NEWS
I yanked zom.zip out of the RUU for my Raider.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.197s]
finished. total time: 0.199s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.184s]
finished. total time: 1.186s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip c:\
junk\zom.zip
sending 'zip' (420878 KB)...
OKAY [ 39.172s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 40.786s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
so ends up the EMMC chip has bad sectors and this is a problem with this phone. I ended up on freenode at #htc-holiday and had a good chat with IOMonster, so I will try to return the phone to HTC 866.449.8358 and if not I will do the following.
by the way fastboot boot recovery-beta2.img did get me into recovery -- strange no one pointed that out to me...
The above error is how I found out the EMMC chip has write errors.
I will try to remember to come back and post what happens when I call HTC tomorrow.

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

ICS ROM bricked my Raider, has old hboot, unlocked, how to relock getting error

I have a soft-bricked Raider that I dont know the history of and looks like it was updated to a ICS ROM with out updating the hboot, it has hboot 1.83.0014 and unlocked, a getver all shows the version-main to be 1.65.666.3 so I google that up and found this ICS image...
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1498003
So it appear I need to lock my bootloader and update the hboot.
When I run oem lock this is what I get.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.022s
I let it sit for 15 minutes but no change.
what do I need to do to get my bootloader relocked?

That's relocked. Reboot into hboot.
Sent from an HTC Vivid via XDA Premium

I have do.e fastboot OEM lock 5 or more times on this phone and it says *** locked *** when I reboot into hboot

http://forum.xda-developers.com/showthread.php?t=1421760
Maybe you can try this tool to wipe your device. I have no idea if it will work. It's worth reading up on though.

Tx I will check that when I get home

MORE BAD NEWS
I yanked zom.zip out of the RUU for my Raider.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.197s]
finished. total time: 0.199s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.184s]
finished. total time: 1.186s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip c:\
junk\zom.zip
sending 'zip' (420878 KB)...
OKAY [ 39.172s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 40.786s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
so ends up the EMMC chip has bad sectors and this is a problem with this phone. I ended up on freenode at #htc-holiday and had a good chat with IOMonster, so I will try to return the phone to HTC 866.449.8358 and if not I will do the following.
by the way fastboot boot recovery-beta2.img did get me into recovery -- strange no one pointed that out to me...
The above error is how I found out the EMMC chip has write errors.
I will try to remember to come back and post what happens when I call HTC tomorrow.

bobmutch2 said:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.184s]
finished. total time: 1.186s
Click to expand...
Click to collapse
Did you solved it? I have a same problem [SD/EMMC]Error status=0x400008.

[q] help plzz fast....

NEED HELP PLZZ
I was trying to change the MID,CID with this guide http://forum.xda-developers.com/showthread.php?t=2322820 and now i'm stuck on the last step with my HTC One on with that gray screen and whenn i try to flash the RUU from this guide http://htc-one.wonderhowto.com/how-to/convert-any-htc-one-into-stock-google-play-edition-with-bootloader-recovery-ota-updates-0148068/ i get this:
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'

Did you do this:
fastboot oem rebootRUU.
fastboot flash zip filename
fastboot flash zip filename (second time) ?

SaHiLzZ said:
Did you do this:
fastboot oem rebootRUU.
fastboot flash zip filename
fastboot flash zip filename (second time) ?
Click to expand...
Click to collapse
when i use : fastboot oem reboot RUU the screen gose black and nothing hapens :/

Post a fastboot getvar all output

SaHiLzZ said:
Post a fastboot getvar all output
Click to expand...
Click to collapse
so i manage to get my HTC running again but couldn't install tha RUU:
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
C:\sdk\platform-tools>fastboot flash zip gpe.zip
error: cannot open 'gpe.zip'
C:\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.046s]
finished. total time: 0.046s
C:\sdk\platform-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
sending 'zip' (467625 KB)...
OKAY [ 22.085s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 23.430s
C:\sdk\platform-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
< waiting for device >
target reported max download size of 1526722560 bytes
sending 'zip' (467625 KB)...
OKAY [ 23.033s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 23.450s

The error is obviously MID. Fix it!

SaHiLzZ said:
The error is obviously MID. Fix it!
Click to expand...
Click to collapse
i fixed the MID isue and now sows an other error -.-
C:\sdk\platform-tools>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip
target reported max download size of 1526722560 bytes
sending 'zip' (467625 KB)...
OKAY [ 23.207s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 23.242s

You didn't do rebootruu

sahilzz said:
you didn't do rebootruu
Click to expand...
Click to collapse
omg works perfect now i have htc one google play edition thanks a lot :ddddd

[Q] bricked?

hey i may have messed up my nexus 6 already. unlocked the bootloader, rooted it with no problem. downloaded the twrp from play store and installed. got an install error. i looked online for someone having the issue and they said they got error and booted into recovery and it was working. i did the same. once in recovery i did a hard reset just to see if it was working, it worked. after that i hit fix permissions. and then phone would never boot. i was a little drunk so i went into recovery again, and wiped but this time i checked system. not smart i know, but what can i say. now phone boots upto google screen with unlock icon? what do i do?

Reflash factory imagine

Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

El Daddy said:
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.

uncfan44 said:
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
Click to expand...
Click to collapse
Sometimes you have to install the drivers on your computer again while your phone is connected and in the boot loader.
Also, if you don't have your environment variables set up correctly, you'll have to open the command prompt from the same folder in which fastboot.exe lies. As well as putting the image files in that folder.
Sent from my Nexus 5 using Tapatalk

and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.

uncfan44 said:
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
Click to expand...
Click to collapse
Make sure you have fastboot selected in bootloader and try this tool to make sure fastboot is installed in your machine properly.
http://forum.xda-developers.com/showthread.php?t=2588979

ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!

uncfan44 said:
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
Click to expand...
Click to collapse
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!

Make sure you have the newest fastboot and flash everything manually. If you don't have the newest fastboot it'll throw errors.

12MaNy said:
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Click to expand...
Click to collapse
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>

uncfan44 said:
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
Click to expand...
Click to collapse
You have the latest fastboot installed? Also the system image from Google was extracted to platform tools? And lastly did u check md5 of original download?
Definitely not something wrong with the commands your using.

yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.

uncfan44 said:
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
Click to expand...
Click to collapse
I know im a little late but you can just use wugfresh nexus toolkit and flash back to stock.

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!