Database Develop

FIX load HTC 626G?

Hi frend.
What do I have!
HTC 626G is written in the phone and on the box.
HTC 626ph on the phone cover.
626G and 626ph = from one box at purchase
CPU MTK6592
Android 4.4.2
build 1.78.401.100 and 1.79.401.100
When you enter commands: fastboot
fastboot: getvar version
fastboot out: getvar:version FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: getvar:version-bootloader FAILED (remote: not support on security)
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: getvar:version-main FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar serialno
fastboot out: getvar:serialno FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar product
fastboot out: getvarroduct FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar modelid
fastboot out: getvar:modelid FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar cidnum
fastboot out: getvar:cidnum FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar build-mode
fastboot out: getvar:build-mode FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar boot-mode
fastboot out: getvar:boot-mode FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar security
fastboot out: getvar:security FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar imei
fastboot out: getvar:imei FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: oem get_identifier_token
fastboot out: ...
FAILED (remote: unknown command)
finished. total time: 0.003s
Click to expand...
Click to collapse
fastboot oem get_identifier_token - error!
$ fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.003s
Click to expand...
Click to collapse
fastboot oem unlock - error! Unlocked, perhaps?
$ fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0x7000
)
finished. total time: 110.541s
Click to expand...
Click to collapse
I made backups
Backup HTC 626G 1.79.401.100 (for SP Flash Tool)
Backup HTC 626G 1.78.401.100 (for SP Flash Tool)
Backup HTC 626G 1.72.401.101 (for SP Flash Tool)
Instructions such!
If their upload to the phone via SP_Flash_Tool_v5.1348.01_SEC + download_agent MTK_AllInOne_DA.bin, phone is loaded. but there is no picture on the display (LСD), only backlight.
I have even copied preloader! by command dd if=/dev/preloader of=/mnt/sdcard/preloader.bin count=262144 bs=1 When copying he 256 KB. STOCK 1.79-1.78 Preloader
if it is open WinHEX and to edit the original 114kb (as in 0PM1100_A32MG_DUG_K44_SENSE53_htc_asia_1.03.707.1_Radio_MOLY_WR8_W1315_MD_WG_MP_V62_P4) and downloaded into the phone, it does not start. Not respond to the button.
Upload preloader in Backup HTC 626G 1.03.707.1 (для SP Flash Tool) (0PM1100_A32MG_DUG_K44_SENSE53_htc_asia_1.03.707.1_Radio_MOLY_WR8_W1315_MD_WG_MP_V62_P4)
Phone is turned on. No image, just backlighting. but it works.
There are still a similar patient. After loading TWRP recovery, It hangs on the splash screen HTC and reboots (bootloop). When downloading files from a backup of the original, nothing changes. (bootloop)
I can not understand why I can not get them to work. What else can be done?
Three weeks I can not understand.
I recommend to view a selection of photos on my topic.

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!

P30 Pro bricked? Bootloop

Hi, I bought a Huawei P30 Pro "defective" for very little money.
The device hangs in a boot loop, the Huaweo logo is displayed, then it restarts several times, at some point it goes to eRecovery.
I ran the system restore there, then unfortunately still the same game, bootloop.
hiSuite shows me that a system restore is not supported for the device.
Fastboot can be called up, it says "Phone is locked" in green at the bottom, but that probably only means that the bootloader is locked?
According to the seller, it was like that from one day to the next, it didn't fall or anything like that.
Anyone a suggestion? USB-C USB stick is available, ne NM card too.
Code:
>fastboot devices
22X7N19420013589 fastboot
>fastboot oem get-product-model
...
(bootloader) VOG-L29
OKAY [ 0.011s]
finished. total time: 0.011s
>fastboot oem get-build-number
...
(bootloader) :VOG-L29 12.0.0.149(C431E3R2P2)
OKAY [ 0.010s]
finished. total time: 0.010s
>fastboot getvar recue_enter_recovery
getvar:recue_enter_recovery FAILED (remote: Command not allowed)
finished. total time: 0.017s
>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: read oeminfo item failed)
finished. total time: 0.026s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Did you find a solution?
I have the exact same problem with the exact same version VOG-L29 12.0.0.149(C431E3R2P2).
I tried the restore the firmware with hisuite software and proxy modifing the xml file but once the recover is done the smartphone can't install it.I discovered that this procedure only works if the smartphone run normally(no bootloop or soft brick)
Tomorrow i will try with OTG and dload.After that if I can't unlock it I will send it to huawei customer service hoping they don't charge me more than 100 euro.