Hey, I apologize about the new thread but I can't seem to find the answer anywhere else from here. I can NOT get this damn thing unlocked. I have went to HTCDev. Got my unlock_code.bin. Plug in the file to the fastboot directory, run the command and this happens:
C:\Users\Xyria\Desktop\htc root\fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.008s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.065s.
I've tried getting new bin files, using a different browser to download the files, everything. I've made sure that OEM Unlocking and USB Debugging are turned on.
I noticed that when I prompt for the Identifier token, this happens:
C:\Users\Tae\Desktop\htc root\fastboot>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 3E27037B17FEB4FAEDC1A20E2217CFA9
(bootloader) F96D682BECF7F1E2AC5C2AE4CC5092F2
(bootloader) ED3DEA52E0188B695B93FB1FD94465CD
(bootloader) 4F34BE816CFBEC1C783D5CAEAF2DF427
(bootloader) DA2974C3BCF133DD3F6648C56DE93DFE
(bootloader) 18D887CE6B0549A0F0E2AC1EA5F4E64C
(bootloader) A5097191BA197028D9D99E4D40E5B078
(bootloader) A6A0DE48ED0E4F7F77EEB533B2B520B2
(bootloader) D22F541EDF71EB0D7EBD9698BAE2BE68
(bootloader) CA1752D23E7DA7D8977024E93B7DE0CE
(bootloader) A70A97DE25BCAE70073CDECF3DFD6D25
(bootloader) 737A41254DE10723FA7E0558B043AC1C
(bootloader) 9A9FEB98F1C55DD167DE63B519DD1934
(bootloader) 2D203A3FF4FD71394732365ACC443794
(bootloader) D76BF85C7B23CFF7D56912AB963C97F9
(bootloader) 9679FB42A661A65AFE1B446BE19B2499
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.090s]
finished. total time: 0.090s
I'm not sure what "enable unlock" means. I am doing it from download more for sure using vol down and power. It successfully downloads the file but will not write it. This is starting to frustrate me, lol.
Nothing I'm doing is working past this point. Any ideas? I really just want to root this thing.
Have you tried rebooting back into download mode? Also just get another unlock.bin code cause sometimes the first one won't work.
Sent from my HTC 10 using Tapatalk
Try changing USB ports. You've already done everything else I would have suggested but you can also try going into settings and doing a factory reset, skipping the setup and just enabling debugging and oem unlock and starting over with a new key.
Nope, did nothing.
EtherealRemnant said:
Try changing USB ports. You've already done everything else I would have suggested but you can also try going into settings and doing a factory reset, skipping the setup and just enabling debugging and oem unlock and starting over with a new key.
Click to expand...
Click to collapse
I've reset the device 3 times now. Same error every time no matter what computer I'm on or how many unlock code bin's I get. Sigh.
explasia said:
I've reset the device 3 times now. Same error every time no matter what computer I'm on or how many unlock code bin's I get. Sigh.
Click to expand...
Click to collapse
Are you rebooting to bootloader or to download? On the 10 this has to be down in download mode to work adb reboot download then try the unlock.bin from there. Unless you've already done that I don't know what else could help
bbell101584 said:
Are you rebooting to bootloader or to download? On the 10 this has to be down in download mode to work adb reboot download then try the unlock.bin from there. Unless you've already done that I don't know what else could help
Click to expand...
Click to collapse
Right, I'm going to download mode. Thanks for your help. I'll take a shot in the dark after work and say its possibly Windows 10's fault. I'll try it on linux when I get back home.
Are you deleting the (bootloader) on each line before using the token? If not, that's your problem.
metalfan78 said:
Are you deleting the (bootloader) on each line before using the token? If not, that's your problem.
Click to expand...
Click to collapse
Yes I did. I copied only the code and the <<<>>> section.
I ran into the same issue, and I had extra 'spaces' in various spots from deleting those, after I cleaned up the token it worked. I copied and pasted it into notepad and cleaned it up and it worked.
Nvm
I fixed it; here's how.
I went to a Win 7 machine and did the same damn thing I was doing before.
Good ****, Microsoft.
Thanks for trying to help, guys.
For anyone on a Windows 8/10 computer who is still having this issue, open Command Prompt, right click on the header and go to "Properties." In the Options tab, check the box that says "Use Legacy console (requires relaunch)" and reopen command prompt.
Make sure "OEM Unlocking" is checked in Developer Options. Repeat all of your steps, and after you use the 'fastboot oem get_identifier_token' command, right click in the terminal window and select Mark. Highlight ONLY the area you're instructed to (from <<<< Identifier Token Start >>>> to <<<<< Identifier Token End >>>>>), then use CTRL + C or CTRL + X to copy and paste the token on HTC's site.
My unlock worked fine on Windows 10. But I also launched an admin command prompt to make sure it had all the access it may need.
Related
I've got this phone for a while now but since i updated it to official marsmallow it's been stuck into bootloader. The phone is stock, still locked and S-ON. I've tried to unlock it so i can use a custom rom but when i do the official bootloader unlock from htc it goes all okay until it should promp me on the phone screen to confirm bootloader unlock, i can't find a way to make it work. I also tried to use the RUU but when it's rebooting my phone into bootloader (witch it is already) it doesn't reboot the phone goes stand by and the program stops. I the tried to get the zip RUU into an SD but the CID doesn't match since i got the Vodafone UK one so my cid is VODAP001 and i can't find the right RUU for this version. Can someome please help, i'm desperate.
I've tried to use the RUU.zip file from cmd using comand fastboot oem rebootRUU bur it gives me this message:
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.058s]
finished. total time: 10.058s
BlackMambo90 said:
I've got this phone for a while now but since i updated it to official marsmallow it's been stuck into bootloader. The phone is stock, still locked and S-ON. I've tried to unlock it so i can use a custom rom but when i do the official bootloader unlock from htc it goes all okay until it should promp me on the phone screen to confirm bootloader unlock, i can't find a way to make it work. I also tried to use the RUU but when it's rebooting my phone into bootloader (witch it is already) it doesn't reboot the phone goes stand by and the program stops. I the tried to get the zip RUU into an SD but the CID doesn't match since i got the Vodafone UK one so my cid is VODAP001 and i can't find the right RUU for this version. Can someome please help, i'm desperate.
I've tried to use the RUU.zip file from cmd using comand fastboot oem rebootRUU bur it gives me this message:
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.058s]
finished. total time: 10.058s
Click to expand...
Click to collapse
same issue here
did you find the solution?
skierr said:
same issue here
did you find the solution?
Click to expand...
Click to collapse
Yeah I had to send it to support since it had a hardware problem with the memory ( I've pinpointed the problem to the ROM) if you your warranty is expired maybe you should try replacing the motherboard
skierr said:
same issue here
did you find the solution?
Click to expand...
Click to collapse
You have the same sector/emmc errors? Of you just have the problem of stuck in bootloader? Those are two very different things. With the second one being quite possibly fixable.
You need to be specific if you want any meaningful help. Saying you have the "same issue" is never sufficient for folks to give help; and is just going to end up confusing you and others.
Assuming it is not a hardware emmc failure, and you want some direction, please provide the following:
- If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
- If you don't know how to do fastboot, what OS number and radio number does it say on the phone's bootloader screen?
- Bootloader locked or unlocked?
- Any other mods (TWRP, custom ROM, etc.).
- What events led to the current condition? Did you try to flash something, or update OS? Or just happened spontaneously?
- Exact names/version numbers of files you installed, or tried to flash.
The more detail you can give, the better.
Hello everyone,
My phone boots straight into bootloader and I only have access to bootloader and download mode (no recovery). My phone is S-ON and Re-locked. Unlocking again doesnt seem to work and I get this error message when I try:
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.015s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
Any help on how to get S-OFF as well would be awesome!
I cannot find an RUU that matches my phone. My details are:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226065287278
(bootloader) version-main: 2.10.61.6
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440601_83.06.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: ORANG001
Any help would be greatly appreciated so thank you in advance! :good :
PlumpPanda said:
Hello everyone,
My phone boots straight into bootloader and I only have access to bootloader and download mode (no recovery). My phone is S-ON and Re-locked. Unlocking again doesnt seem to work and I get this error message when I try:
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.015s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
Any help on how to get S-OFF as well would be awesome!
I cannot find an RUU that matches my phone. My details are:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226065287278
(bootloader) version-main: 2.10.61.6
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440601_83.06.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: ORANG001
Any help would be greatly appreciated so thank you in advance! :good :
Click to expand...
Click to collapse
Factory Reset Protection is stopping the unlock. You should have removed your google account before messing with it.
Now you're locked out of your OS which is preventing you from flipping the bootloader unlock switch.
I honestly don't know how to get around that. I'm not sure an ruu flash will help either..
S-off, you need to run an app called "sunshine" and pay $25 or buy an xclip or the likes.
Beamed in by telepathy.
shivadow said:
Factory Reset Protection is stopping the unlock. You should have removed your google account before messing with it.
Now you're locked out of your OS which is preventing you from flipping the bootloader unlock switch.
I honestly don't know how to get around that. I'm not sure an ruu flash will help either..
S-off, you need to run an app called "sunshine" and pay $25 or buy an xclip or the likes.
Beamed in by telepathy.
Click to expand...
Click to collapse
It's true that this is a security feature but the google account has nothing to do with it. It's the option "OEM Unlock" in the developer options that seems to be inactive in this case. And yes, a RUU could fix this issue.
@PlumpPanda: That usually happens if the phone gets relocked although it's not completely stock. Security checks notice that the software isn't original (e.g. if TWRP is installed) and prevent the phone from booting so that it doesn't get "damaged" by the "faulty" software. (The software actually isn't faulty in reality but the security checks only distinguish between original software and not-original=faulty software if the bootloader is locked or relocked.) There seems to be no publicly available RUU for your firmware so all you can do is contacting Llabtoofer's RUU service and ask whether he can help you out. (Chances are high that he can.) Sunshine is no alternative since you have no booting system and java cards or xtc clips are way more expensive than the RUU service (unless you have friend that already owns one ).
Note the red highlight.. Frp = factory reset protection. If you have seen this error before then ignore me, I'm talking rubbish but as far as I can tell it wouldn't have frp if it was just the unlock killswitch stopping it. Would it?.
It does say that "enable unlock" then rejects it, probably due to the frp?.
Something tells me that this rabbit hole may go deeper if you keep digging but one thing is for sure.. Bye bye data.
Beamed in by telepathy.
shivadow said:
Note the red highlight.. Frp = factory reset protection. If you have seen this error before then ignore me, I'm talking rubbish but as far as I can tell it wouldn't have frp if it was just the unlock killswitch stopping it. Would it?.
It does say that "enable unlock" then rejects it, probably due to the frp?.
Something tells me that this rabbit hole may go deeper if you keep digging but one thing is for sure.. Bye bye data.
Beamed in by telepathy.
Click to expand...
Click to collapse
Yeah, I noticed the part that you highlighted in red. And it is a factory reset protection since it prevents the factory reset that gets triggered by a bootloader unlock. However, it has nothing to do with google accounts and it doesn't prevent you from flashing RUUs. But you're right, since a RUU completely wipes the phone the currently saved data (e.g. contacts, pictures, messages, etc.) is lost.
That error is not new. It exists since the M9 received firmware 2.x. You can't unlock the bootloader unless OEM Unlock is activated in the developer options. The oldest threads which deal with this problem got started around august 2015.
Edit: Wait a minute. I missed that part:
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
Click to expand...
Click to collapse
If OEM Unlock was disabled the output would be the following:
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
Click to expand...
Click to collapse
@PlumpPanda did you maybe try to use your old unlock token? Can you try to get a new one, please?
Flippy498 said:
Yeah, I noticed the part that you highlighted in red. And it is a factory reset protection since it prevents the factory reset that gets triggered by a bootloader unlock. However, it has nothing to do with google accounts and it doesn't prevent you from flashing RUUs. But you're right, since a RUU completely wipes the phone the currently saved data (e.g. contacts, pictures, messages, etc.) is lost.
That error is not new. It exists since the M9 received firmware 2.x. You can't unlock the bootloader unless OEM Unlock is activated in the developer options. The oldest threads which deal with this problem got started around august 2015.
Edit: Wait a minute. I missed that part:
If OEM Unlock was disabled the output would be the following:
@PlumpPanda did you maybe try to use your old unlock token? Can you try to get a new one, please?
Click to expand...
Click to collapse
Yeah I used the 'htcdev' website to get a new unlock code after my old one didn't work and it still doesn't unlock it. Thank you for all your help so far guys :good:
Edit:
@Flippy498 I've just got an email back saying Llabtoofer's RUU service can flash my phone so I'll let you know when all is said and done Thanks!
Phone is now fixed!! I used the Llabtoofer's RUU service and it worked perfectly. Highly recommended as it took roughly half an hour and now it works perfectly!!!! Thanks for you rhlpe guys!
I can't flash my recovery.
Bootloader is unlocked.
Phone is not rooted
This sucks becouse i bought this phone thinking i whould not have this ****ing problem again.
(also lost my old one for the millionth time)
PS C:\Users\Admin> fastboot flash recovery C:\ProgramData\chocolatey\lib\adb\tools\platform-tools\twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.473s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.502s
PS C:\Users\Admin>
Click to expand...
Click to collapse
Weird, that validation error is usually shown when bootloader isn't actually unlocked. Have you tried unlocking it again? Have you tried with mfastboot?
DrunkenPanda2000 said:
I can't flash my recovery.
Bootloader is unlocked.
Phone is not rooted
This sucks becouse i bought this phone thinking i whould not have this ****ing problem again.
(also lost my old one for the millionth time)
Click to expand...
Click to collapse
Either you are flashing the wrong recovery for the phone - or you renamed a zip file instead of extracting the img file first
Or
Put quotation marks around the file path eg "c:/file path" or navigate to where you have fastboot and the twrp image first so all you have to type is
fastboot flash recovery recovery.img
Also make sure adb debugging is enabled in dev options of phone settings
Also if the bootloader is unlocked you should get a bootloader unlocked warning when the device starts unless you have replaced the boot logo with a modified one
If you haven't replaced this & you don't get said warning your device doesn't have an unlocked bootloader
The console is definatly finding the file. this is not the issueadb debugging is enabled. altho i realised i have the insert pattern before startup enabled and i think that might be interfering.
I am not gettIng the bootloader unlocked warning.
I disabled the pattern on bootup.
I unlocked with oem unlock.
i tried to flash from directory
Same issue
Stil no unlocked warning
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.493s
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools>
Click to expand...
Click to collapse
DrunkenPanda2000 said:
I disabled the pattern on bootup.
I unlocked with oem unlock.
i tried to flash from directory
Same issue
Stil no unlocked warning
Click to expand...
Click to collapse
Just to check, have you requested and used the unlock key from the Motorola website? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
echo92 said:
Just to check, have you requested and used the unlock key from the Motorola website? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
I have requested one. haven't received it yet.
The website doesn't show if eligable if click that button.
Also they havent send me anything for an houer after requesting.
DrunkenPanda2000 said:
I have requested one. haven't received it yet.
The website doesn't show if eligable if click that button.
Also they havent send me anything for an houer after requesting.
Click to expand...
Click to collapse
Hopefully they'll send you an email with the code in soon. Sometimes the website is a little slow, but regardless it should say if your device is eligible for unlocking. Is your device a carrier bought device or a retail device or bought from Amazon Prime? They do say if your device is bought from Motorola, to wait at least 24 hours before requesting the code.
Check that the unlock string from your device is properly formatted for the website
Ok, so my device should be eligible, but when in enter my unlock string in your tool, I get an error message. What’s wrong?
Please make sure the string you enter in the tool is:
formatted to fit on one line only
has no spaces (you have to remove them manually)
has no carriage returns (these pesky \n)
is of the right length, e.g don’t forget to append the extra 000000… on the last line
USE THE SCRUB TOOL on the UNLOCK PAGE - ABOVE the INPUT BOX
As an example, this is what is returned with the fastboot command
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 99999999999999993332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
And this is what you should enter in the form; it’s a single line, no spaces but with all the trailing zeroes.
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2A 0C39F951A3E5#1F532800020000000000000000000000
Click to expand...
Click to collapse
credit to: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
That code in the email should let you unlock the bootloader and let you flash TWRP, no other way to unlock your bootloader (officially). If you don't get the code after a few tries of the website/waiting for the email, you may have to post on the Motorola forums: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
Ok so now i unlocked with the code and when i flash i get the following.µ
Model is cedric XT1676 16GB P5
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.469s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.510s]
finished. total time: 0.985s
Seems to be working now.
DrunkenPanda2000 said:
Ok so now i unlocked with the code and when i flash i get the following.µ
Model is cedric XT1676 16GB P5
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.469s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.510s]
finished. total time: 0.985s
Click to expand...
Click to collapse
That looks normal - the 'Image not signed or corrupt' message is normal as TWRP has not been cryptographically signed. As you've unlocked your bootloader that message is informational to alert that you're flashing non-Motorola files to your device (which you are).
I'd reboot to recovery after flashing and perform the other steps required (which appear to include disabling dm-verity: https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737 )
When flashing super su i get the error message
-extracting ramdisc
---failure aborting
DrunkenPanda2000 said:
When flashing super su i get the error message
-extracting ramdisc
---failure aborting
Click to expand...
Click to collapse
Flash Magisk v16.0 instead of su zip. It will work.
shad.man92 said:
Flash Magisk v16.0 instead of su zip. It will work.
Click to expand...
Click to collapse
Thx for the advice i need to act before i post sometimes.
I've done this already now i'm facing issues with the magisk nethunter module. this will be discussed in their thread.
Can i close or remove this ?
DrunkenPanda2000 said:
Can i close or remove this ?
Click to expand...
Click to collapse
Yeah sure.
Boot loader unlock
Shooting Star Max said:
Weird, that validation error is usually shown when bootloader isn't actually unlocked. Have you tried unlocking it again? Have you tried with mfastboot?
Click to expand...
Click to collapse
I have tried a same,got a bootloader and tried with fastboot,but i got error 'need to enable OEM in android settings'
.Actualy my mobile stuck with logo,once moto logo appear its gets shutdown,
Looking for your reply.
Hello there,
I have Moto G5 Cedric XT1672 RETBR Brazilian Version
But I can't get ID number to get finished bootloader unlock.
After I load this line on fastboot mode:
fastboot oem get_unlock_data
Terminal show:crying: me this feedback:
(bootloader) slot-count: no found
(bootloader) slot-suffixes: no found
(bootloader) slot-suffixes: no found
…
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.271s]
Finished total time 0.272s
:crying:
johnniebrazil said:
Hello there,
I have Moto G5 Cedric XT1672 RETBR Brazilian Version
But I can't get ID number to get finished bootloader unlock.
After I load this line on fastboot mode:
fastboot oem get_unlock_data
Terminal show:crying: me this feedback:
(bootloader) slot-count: no found
(bootloader) slot-suffixes: no found
(bootloader) slot-suffixes: no found
…
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.271s]
Finished total time 0.272s
:crying:
Click to expand...
Click to collapse
Make sure you have
1 - enabled usb debugging in the Developers settings
2 - You have installed the Motorola drivers
3 - You have installed the android sdk
4 - You are using the adb/fastboot in the android sdk platform-tools folder
5 - You are running cmd as administrator
TheFixItMan said:
Make sure you have
1 - enabled usb debugging in the Developers settings
2 - You have installed the Motorola drivers
3 - You have installed the android sdk
4 - You are using the adb/fastboot in the android sdk platform-tools folder
5 - You are running cmd as administrator
Click to expand...
Click to collapse
Sure, I followed this steps, but this problem continue
johnniebrazil said:
Sure, I followed this steps, but this problem continue
Click to expand...
Click to collapse
Hmm, you may wish to post on the Motorola forums in the Bootloader unlocking help thread. https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809
They'll want the output of the fastboot oem get_unlock_data (even if it's failed, as in your case) and your getvar info including IMEI. Once your report is forwarded by Alpha_dog or another Motorola forum staff member, you may have to wait 2-3 business days for a response if they can generate a code for you.
Can you send the device other commands? Or do all fail to work?
All others are recognized by adb yes
Hello,
just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup)
Enabled developer options, OEM unlocking and USB debugging.
After update, 1*reboot.
then another reboot to bootloader, and executed "fastboot oem unlock".
Phone rebooted to recovery. Wiped data, another reboot, now i have only the Red & white dots.....
Any suggestions/hints?
Thanks
Edit:
Entered fastboot mode, did a fastboot oem lock -> same, Red and white dots.
When I unlocked the bootloader I had to wait a much longer time than normal (about 8 minutes) for the dot splash screen to transition to the setup screen and for the phone to boot up fully.
I apologize if this is sort of a "duh I already did that" suggestion. Hope it can help.
Unfortunately not, i waited around 1 hour.
But thanks 4 your comment!
Booting the stock boot.img posted here on XDA -> same result.
Tried to swap the boot slot -> FAILED (remote: Slot Change is not allowed in merging state)
(bootloader) has-slot:system:no
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:3d12cbee
(bootloader) product:lahaina
(bootloader) snapshot-update-status:merging
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
finished. total time: 0.605s
Waiting msm
empty.cad said:
Waiting msm
Click to expand...
Click to collapse
Regarding MSM: if i understood correctly, this is something OPO does not provide, but is "extracted" by some guys here? (key extraction etc??)
So this may take some time.... Probably RTM (cancel order) next week.
yeah once I unlocked BL in fastboot and rebooted, the subsequent next boot took close to 10 minutes, but did boot into a wiped device after
Regarding the error "FAILED (remote: Slot Change is not allowed in merging state)" when swapping the slot, i found tha a
snapshot-update merge — Completes a merge operation, booting to recovery/fastbootd if necessary. This command is valid only if snapshot-update-status is merging, and is only supported in fastbootd.
May help.
But they talk also about
If merging or snapshotted, issue snapshot-update cancel.
But i prefer to ask here before executing, as i have no idea what this does
Well, i could not wait.
After doing a fastboot snapshot-update merge
i rebooted. Same issue.
Booted stock kernel -> issue
Swapped active slot -> Qualcom crash dump
Rebooted to fastboot, oem lock -> phone boots again.
Rebooted twice normally to confirm
Again fastboot oem unlock
Boot fine now. No idea what happened on first oem unlock.
I haven't tried this yet, but I found this link which seems to give a different fastboot command to use. Not sure how much difference it'll make for other users but thought I'd link to it just in case it helps others. I'll probably try it either tomorrow or over the weekend.
I did not use the fastboot oem unlock but the fastboot flashing unlock on the OP9P Global and worked the first time.