My Moto Z XT1650-03 was hardbricked, finally after several days I found a blankfiles that worked with my version, however as soon as the phone started in fastboot I verified that the bootloader was blocked, hence I am not able to install recovery or any ROM, I have already tried several ROMS, I tried to install by RSD but with the bootloader blocked there is always the same error, when I try to unlock the bootloader the following error appears: (bootloader) Check 'Allow OEM Unlock' in Android Settings> Developer)
Any solution?
*My bootloader is in version 91.08, but the newest ROM I found is with version 91.07, may be why I can not update with adb?
https://imgur.com/a/Qwpz5
Related
Hey,
Five months ago, I decided to flash the EMUI 9 beta on my Huawei Mate 10 Pro (BLA-L29)
Everything was working fine until one day the device didn't want to boot.
I decided to fix the problem by using the recovery but the phone refused to boot to recovery, So I headed to fastboot and I tried flashing EMUI 8 but it gave me the error "Command not allowed"
I then noticed FRP Lock was enabled, I was so stupid to disable OEM Unlocking.
I tried using DC Phoenix with this :tutorial: but It didn't work, I got the error "Device running incompatible security patch", "Command not allowed".
I decided to try the DLOAD method but the phone never booted to the installation process.
Model: BLA-L29
Build number: :BLA-LGRP2-OVS 9.0.0.108(log)
OEM LOCK INFO:
FB LockState: Locked
USER LockState: UNLOCKED
OEM get bootinfo:
unlocked.
I don't know how to solve this problem, Could anyone help me?
Hi.
I have a Doogee X6 S.
It is currently flashed with stock ROM¹, which runs Android 6.0 with a 3.4.5 kernel and contains OEM adware, and maybe worse.
I'd like to be able to flash a more trustworthy rom of android.
I was unable to root the device with kingoroot app. The bootloader is locked, I can't flash TWRP.
I tried to unlock the bootloader:
- I unlocked and enabled developer options,
- I checked the "oem unlocking" option ("allow the bootloader to be unlocked"),
- "adb reboot bootloader" rebooted the phone in fastboot mode
- "fastboot oem unlock" asked me confirmation for unlock, VOL_UP for "Yes", VOL_DWN for "No", but none of the keys have any effect when pressed.
I tried flashing older versions of the stock ROM with SP Flash Tool, but this resulted in a softbick (solved by flashing back last stock ROM).
I tried contacting Doogee support, to no avail.
I don't know what to try next, so here I am!
While I'm not an Android hacker, I know my Linux, and I'm not affraid of complex solutions.
¹ available from official support page: community.doogee.cc/forum.php?mod=viewthread&tid=4872
Since I didn't get any answer here in one week, I opened a thread on the official support forum :
community.doogee.cc/forum.php?mod=viewthread&tid=7544&page=1&extra=#pid50966
If I get a solution there, I'll relay it here.
Hello everyone
Recently I've hard reseted my lenovo Phab (pb1-750n) mistakenly before removing my google account and unfortunately I stocked in google FRP lock, I've searched many sites and seen many videos to bypass the FRP with no success.
Finally I found a russian forum that uploaded the Chinese version of device ROM, since the google apps are banned in China therefore updating the ROM from recovery mode succeed (I downloaded ROM and put it in the SD card, then update the ROM from recovery) and device got back alive again. (NO Google NO FRP )
but the second struggle wave slapped my face, (NO google apps NO joy ), for instance I downloaded Gapps and tried to install it by replacing stock recovery with TWRP, so in device, I turned on developer mode by tapping build number many times and turned on USB debugging and oem unlock, see, I turned on damn oem unlock!!! but in the fastboot when I run the
Code:
fastboot oem unlock-go
, the result ends in oem unlock not allowed report and
Code:
fastboot flash recovery TWRP.img
also failed due to the bootloader lock status. BTW international ROM seems to be all in Chines clouds and is not accessible for non Chines people to download them, at least I couldn't do it.
any idea what is wrong in here????? did Chines made ROM to be like that???? any chance to solve the issue???
this happens because you do not unlock the bootloader, just released to unlock
jeangraff30 said:
this happens because you do not unlock the bootloader, just released to unlock
Click to expand...
Click to collapse
well, after updating system to the 6.0.1, problem solved, it seems android 5.1.1 stock ROM for this phablet do not allow to unlock bootloader, I found it in a russian forum, they said so.
anyway thanks for reply.
Hey All!
I recently(2 days back) purchased a Yu Yutopia running android 5.1.1. I enabled developer options, but it didn't have the OEM unlock option. And whenever i go into fastboot, and type
Code:
fastboot -i 0x2A96 oem unlock
it says
FAILED (remote: unknown command)
finished. total time: 0.008s
Click to expand...
Click to collapse
.. Any help would be appreciated. I went through tons of documentation. the only thing missing for now is the Yutopia Drivers. Is that the problem? If so, can someone share the driver packs? This thread had it, but the link is broken, and is old.
If in Android -> Settings -> Developer options -> OEM unlock option isn't present then unlocking phone's bootloader is denied, you can't unlock it by means of Fastboot.
May be you can obtain from OEM/Carrier an unlock-key. Contact them.
BTW: You always can check Android's system file named build.prop for device's bootloader-unlock capability
Code:
adb devices
adb shell "getprop ro.oem.unlock_supported"
If the device supports "fastboot flashing unlock", then the returned value is 1
Soham41 said:
Hey All!
I recently(2 days back) purchased a Yu Yutopia running android 5.1.1. I enabled developer options, but it didn't have the OEM unlock option. And whenever i go into fastboot, and type
Code:
fastboot -i 0x2A96 oem unlock
it says .. Any help would be appreciated. I went through tons of documentation. the only thing missing for now is the Yutopia Drivers. Is that the problem? If so, can someone share the driver packs? This thread had it, but the link is broken, and is ol
Click to expand...
Click to collapse
Same here tried everything from flashing in EDL mode to downloading Yuware and trying to unlock bootloader. The adb commands
Code:
getprop sys.oem_unlock_allowed
getprop ro.oem_unlock_supported
both return blank. Using Miracle box software to check device info returns Bootloader : unknown. Trying to root via Miracle Box, Kingroot and other methods fails. The original Signed Android 5.1.1 based CM signed zips also won't flash via Recovery and the links are also almost non existent for those. Any hope of finding a original CM firmware to flash via QFIL is very slim. There has to be some way to get it working, there was a YouTube video showcasing the YU Yutopia on Stock Android 5.1.1 Engineering build that now doesn't have the OEM Unlock option only if someone would help. Getting it rooted somehow god knows how is the only option to get started.
Don't waste more time with trying to unlock phone's bootloader: it's NOT supported.
if anyone interested, I made some modifation in stock rom, so it is rooted, without unlocking bootloader, here is the link of my thread
Yu Yutopia (Yu5050) (Sambar) Stock engineering rom, rooted (Android 5.1)
For those interested, this is exactly engineering rom, with added modified patched boot, so it is rooted with magisk. v23 This is the detailed install procedure: You need to download the following: 1. YU_Yutopia_YU5050_V1_24.12.15 rom, link give...
forum.xda-developers.com
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11. Many guides online seem to gloss over needing the bootloader unlocked before root. TMALSS; I'm not sure if the non-international version can be bootloader unlocked and/or if I can root without needing this. Long version of what I've tried is below:
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Thus to unlock the bootloader, I am following a guide from TWRPupdate:
It says to perform 'adb reboot bootloader' and then 'fastboot oem device-id':
Code:
C:\adb-platform-tools>fastboot device-id
fastboot: usage: unknown command device-id
My phone only reboots into normal mode whenever running reboot bootloader command within ADB.
I can run fastboot commands when I run 'adb reboot fastmode' but I don't believe this is true fastmode. As I have tried everything mentioned here, such as cables or different computers. Essentially most fastboot commands I've tried do not work except for showing my device as listed / connected.
I have also tried the drivers from LG / Google / ADB separately. And on 2 computers.
Is it possible that I don't have rescue mode or a bootloader still? As I get a black screen when entering recovery mode (but my computer recognizes A device), but adb nor fastboot does. I used to see the recovery screen logo, but I stopped seeing this screen either after updating to Android V11 or reading/backing-up the partitions in QFIL.
In last resort, I have tried rooting via patching the boot image using Magisk v23. I downloaded the firmware for my carrier, converted the KDZ to DZ via Python, and extracted the boot.img_117638 file. Given the file is 0 bytes with nothing in text edit, I still converted it to an img file. But in the kdztools android app, when I select this image file and run, I get:
Code:
!Invalid input file
!Installation failed
I'm guessing the boot.img file should have some data in it. But I'm not sure this method would even work due to the fastboot issues, especially with 'download to device' errors.
-------
I'm just at a standstill on what to even try next. I don't see many people having this much trouble unlocking/rooting their v60. Did the OTA Android v.11 break the root-ability?!
PS: Debugging and OEM unlock are both set in developer options. I can also list drivers used if need.
Thanks for the help in advance!
While digging I also found a post by alexenferman whom managed to use QFIL to root many older ZTE smartphones. They state it may but likely won't work on newer flagship phones. It's a great tutorial I'll have to try soon, but is there a reason it likely won't work here?
kyij said:
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11.
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
NGOwner said:
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
Click to expand...
Click to collapse
Haha, I remember reading that and still continued
I am on Verizon myself using this TM model. I know the phone was unlocked to the point where I could use it with Verizon. I even got 5g using my old 4g sim card.
Anyhow.. I have tried using that command already, and get the same 'command not supported issue'.
Code:
C:\adb-platform-tools>fastboot devices
LMV600TMc40cxxxx fastboot
C:\adb-platform-tools>fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Again have tried different computers and cables as I've read fastboot can be pretty picky too.
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
NGOwner said:
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
Click to expand...
Click to collapse
Yes I do, I have turned it off and back on as well.
Well then at this point, I'm tapped out. Smarter folks than me will need to step in and take up the mantle.
[NG]Owner
I ended up posting a form to reddit where about 10 people insisted I did something wrong, and with little surprise -- I did.
I did not flash the engineering bootloader after saving a copy.
Makes a lot more sense since it seemed like a lot of steps to backup without actually doing anything
Thanks NG for the help too!
are you success to unlock bootloader yet. if no i will show you
adb reboot fastboot> select reboot bootloader on your phone> fastboot oem unlock