EDL mode
EDL mode
26-11-2019, 02:44 PM
non of the command work
i tried combination with and without seril number or device id not working
the vivo_fastboot_windows_2.zip look promising
when i search string in aboot.img, one of the string output come out is "invalid unlock id string!". so i believe id string is required
maybe the fastboot command i inserted not correct.
this fastboot gives "unlock check Signature fail..." so means i getting close, (finger cross)
some of the fastboot command i use not successful are
C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot bbk
unlock check Signature fail...
C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot -l bbk unlock_vivo
...
FAILED (remote: unclock fail.)
finished. total time: 0.011s
C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot -l vivo_bsp unlock_vivo
...
FAILED (remote: check Signature Fail)
finished. total time: 0.021s
C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot -l vivo_bsp unlock_vivo
...
FAILED (remote: check Signature Fail)
finished. total time: 0.013s
C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot vivo_bsp unlock_vivo 150100524836344142054fd7de539400
...
FAILED (remote: check Signature Fail)
finished. total time: 0.023s
C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot vivo_bsp unlock_vivo
...
FAILED (remote: check Signature Fail)
finished. total time: 0.021s
...many more
hopfully can give me some idea on the fastboot command syntax
26-11-2019, 10:51 PM
(26-11-2019, 02:44 PM)ahhl non of the command work
i tried combination with and without seril number or device id not working
the vivo_fastboot_windows_2.zip look promising
when i search string in aboot.img, one of the string output come out is "invalid unlock id string!". so i believe id string is required
maybe the fastboot command i inserted not correct.
this fastboot gives "unlock check Signature fail..." so means i getting close, (finger cross)
some of the fastboot command i use not successful are
Code:C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot bbk unlock check Signature fail... C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot -l bbk unlock_vivo ... FAILED (remote: unclock fail.) finished. total time: 0.011s C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot -l vivo_bsp unlock_vivo ... FAILED (remote: check Signature Fail) finished. total time: 0.021s C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot -l vivo_bsp unlock_vivo ... FAILED (remote: check Signature Fail) finished. total time: 0.013s C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot vivo_bsp unlock_vivo 150100524836344142054fd7de539400 ... FAILED (remote: check Signature Fail) finished. total time: 0.023s C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot vivo_bsp unlock_vivo ... FAILED (remote: check Signature Fail) finished. total time: 0.021s ...many more
hopfully can give me some idea on the fastboot command syntax
just to confirm, you got all these while using the v2? and you enabled OEM unlock in developer options?
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
27-11-2019, 02:50 AM
(26-11-2019, 10:51 PM)ahhh....need to check whether i enable the developer mode later.ya i am using V2. it seems in V2 fastboot the comand alreadu include the latest vivo_unlocklater i ll do it againthanksX3non(26-11-2019, 02:44 PM)ahhl non of the command work
i tried combination with and without seril number or device id not working
the vivo_fastboot_windows_2.zip look promising
when i search string in aboot.img, one of the string output come out is "invalid unlock id string!". so i believe id string is required
maybe the fastboot command i inserted not correct.
this fastboot gives "unlock check Signature fail..." so means i getting close, (finger cross)
some of the fastboot command i use not successful are
Code:C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot bbk unlock check Signature fail... C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot -l bbk unlock_vivo ... FAILED (remote: unclock fail.) finished. total time: 0.011s C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot -l vivo_bsp unlock_vivo ... FAILED (remote: check Signature Fail) finished. total time: 0.021s C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot -l vivo_bsp unlock_vivo ... FAILED (remote: check Signature Fail) finished. total time: 0.013s C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot vivo_bsp unlock_vivo 150100524836344142054fd7de539400 ... FAILED (remote: check Signature Fail) finished. total time: 0.023s C:\QTADB\[Hovatek] ADB & fastboot v1.0.41>fastboot vivo_bsp unlock_vivo ... FAILED (remote: check Signature Fail) finished. total time: 0.021s ...many more
hopfully can give me some idea on the fastboot command syntax
just to confirm, you got all these while using the v2? and you enabled OEM unlock in developer options?
28-11-2019, 10:28 AM
(28-11-2019, 12:15 AM)ahhl unfortunately still not successful after turning on the bootloader unlock under developer tab.
Sent from my Redmi Note 7 using Tapatalk
well, that's bad news for you cause it means the only ones who'd know the right command / tool to unlock the bootloader would be the manufacturers
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)