I'm using Huawei nova y90.
No option "oem unlock" in dev opts.
(in 'fastboot flashing unlock' gives "flashing unlock not allowed" error.)
How can I make it available in developer options ?
veritvitos said:
I'm using Huawei nova y90.
No option "oem unlock" in dev opts.
(in 'fastboot flashing unlock' gives "flashing unlock not allowed" error.)
How can I make it available in developer options ?
Click to expand...
Click to collapse
Did you search before posting?
You'll have better luck finding an answer when you ask your question in the correct section.
V0latyle said:
Did you search before posting?
You'll have better luck finding an answer when you ask your question in the correct section.
Click to expand...
Click to collapse
I've searched a lot. For this model I don't find answer why the option is unavailable. For samsung phones there is an advice to change the date, remove auto updates and possibly 'oem unlock' becames available.For my phone it doesn't work.
I ask in this general section because, there's no forums for this phone model.
veritvitos said:
I ask in this general section because, there's no forums for this phone model.
Click to expand...
Click to collapse
Huawei Nova / Nova Plus section
We will move your thread.
I think unlocking may possible if you can get raw access with (leaked) firehose programmer for huawei.
aIecxs said:
I think unlocking may possible if you can get raw access with (leaked) firehose programmer for huawei.
Click to expand...
Click to collapse
Okay, don't know what this means, but will look into it.Thanks
Search for an unlock tool for your device , its a python script Im using this for MTK devices , the Bat Will tell you to enter BRom mode, once u enter ,the bootloader Will be unlocked
innergat said:
Search for an unlock tool for your device , its a python script Im using this for MTK devices , the Bat Will tell you to enter BRom mode, once u enter ,the bootloader Will be unlocked
Click to expand...
Click to collapse
Okay thanks for that., My main problem is that there is no "OEM unlock" in dev options...So I guess it's locked by default.
I found two python scripts, tried them they work with IMEI; phone enters bootloader, the first script gives error message, but the secondand starts forcing with randoms....but until dev opts is unlocked it won't work..
innergat said:
Search for an unlock tool for your device , its a python script Im using this for MTK devices , the Bat Will tell you to enter BRom mode, once u enter ,the bootloader Will be unlocked
Click to expand...
Click to collapse
you know it is Qualcomm and not MediaTek SoC? Do you mean this tool? I doubt there is a Huawei signed Loader floating around for this SM6225 Snapdragon 680.
https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349
Related
Using Windroid 3.1 to unlock moto g 2015 osprey, drivers installed and works perfectly on wife phone. On trying to unlock my phone i get error message.
Houston, we have a problem
An error has occured! a log file has been placed in the Logs folder.
The same error occurs whether oem locking is on or not. Also i am having communication fails when using fastboot, yet the phone is recognised and read to but not written.
Where would i find this log file please and any help offered i would be grateful.
bantamroberts said:
Using Windroid 3.1 to unlock moto g 2015 osprey, drivers installed and works perfectly on wife phone. On trying to unlock my phone i get error message.
Houston, we have a problem
An error has occured! a log file has been placed in the Logs folder.
The same error occurs whether oem locking is on or not. Also i am having communication fails when using fastboot, yet the phone is recognised and read to but not written.
Where would i find this log file please and any help offered i would be grateful.
Click to expand...
Click to collapse
Try adb and fastboot instead of Windroid
As I tried to explain in my post , this is not possible as the phone will not write the data sent. Thinking this is why windroid returns an error.
bantamroberts said:
As I tried to explain in my post , this is not possible as the phone will not write the data sent. Thinking this is why windroid returns an error.
Click to expand...
Click to collapse
Did you enable OEM Unlocking the Developer Options menu? Still required...
I would also recommend doing it manually, the commands are easy and the process is simple... if something goes wrong you can see exactly what fails. Tools like Windroid are not really useful for simple tasks like this.
done oem unlock in developer options but not manually as im unsure how. please elaborate.
bantamroberts said:
done oem unlock in developer options but not manually as im unsure how. please elaborate.
Click to expand...
Click to collapse
Gotta be 50 tutorials on-line, there is only one real, official way...
You need at least fastboot (you can get it from Minimal ADB & Fastboot)
Then follow the Moto official method which even using a tool you have to go through anyway to get the tokem
acejavelin said:
Gotta be 50 tutorials on-line, there is only one real, official way...
You need at least fastboot (you can get it from Minimal ADB & Fastboot)
Then follow the Moto official method which even using a tool you have to go through anyway to get the tokem
Click to expand...
Click to collapse
Done this, error message failed to get unlock data. remote failure.
bantamroberts said:
Done this, error message failed to get unlock data. remote failure.
Click to expand...
Click to collapse
So you have OEM Unlocking enabled in Developer Options and fastboot is still complaining?
What model and variant? Is this a carrier locked phone or a Moto retail version?
Sent from my MotoG3 using Tapatalk
acejavelin said:
So you have OEM Unlocking enabled in Developer Options and fastboot is still complaining?
What model and variant? Is this a carrier locked phone or a Moto retail version?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
its a xt1541 on tesco mobile and unlocked with sim code.
So,
Its not my problem but one of my friend is facing it and I am unable to resolve it no matter what.
He have moto g 2015 Indian variant briefly XT1550
I tried unlocking its bootloader but every time I give command, " fastboot OEM get_unlock_data "
It gives a weird error. Saying
Code:
...
(bootloader) Failed to get unlock data, Please try again!
Failed (Remote Failure)
Finished. Total time: 0.243s
I tried searching for a fix all over internet some moto x play users were facing it but no solution.
I tried almost everything. I tried minimal adb and fastboot even mfastboot.
Drivers are installed and command, "fastboot devices" reports positively.
I will be attatching a screenshot of fastboot output. So please try to help him.
These community had never let me down.
Have you granted permission for OEM Unlocking in your phone in developer options..?
Jithin91 said:
Have you granted permission for OEM Unlocking in your phone in developer options..?
Click to expand...
Click to collapse
Yup. Followed everything correctly. And if OEM unlocking was deal then it clearly states that in cmd. And yes its enabled.
Sir, I am not sure but would contacting Motorola directly be of any help?
Can you post a photo of your bootloader screen and/or the output of 'fastboot getvar all'?
acejavelin said:
Can you post a photo of your bootloader screen and/or the output of 'fastboot getvar all'?
Click to expand...
Click to collapse
Here is it.
I haven't seen this kinda issue in any osprey till now.
BTW I have attached the getvar all output.
Arcade said:
Here is it.
I haven't seen this kinda issue in any osprey till now.
BTW I have attached the getvar all output.
Click to expand...
Click to collapse
Hmm... That all looks fine. You're bootloader doesn't show Status as ENGINEERING does it? Otherwise I got nothing, it's giving you a remote failure, which is a device issue. Lenovo official forums has a specific area to ask for assistance with unlocking.
There is no harm in turning usb debugging off, turning OEM unlocking off and turning developer options off.
Then do a factory reset
Then turn developer options on agin, usb debugging on again , OEM unlocking on again and try again via fast boot
It won't cost a penny but may help to resolve the issue
just check u select correct command of ur moto id then sent it again to motorola offical page
Geekyogi said:
just check u select correct command of ur moto id then sent it again to motorola offical page
Click to expand...
Click to collapse
Maybe you should read the thread again, OP can't get the code from the phone with get_unlock_data at all, not issues with the Moto site... The phone is getting the correct command, it even acknowledges its an unlock command, it just fails to get data with a "Remote failure" meaning a failure inside the device.
acejavelin said:
Maybe you should read the thread again, OP can't get the code from the phone with get_unlock_data at all, not issues with the Moto site... The phone is getting the correct command, it even acknowledges its an unlock command, it just fails to get data with a "Remote failure" meaning a failure inside the device.
Click to expand...
Click to collapse
Yup. If that was the case then it was a very little problem and myself could have resolved it. No need to post it here.
BTW can't get unlock code till now. Isn't there any other way?
I have checked the cid value and its unlockable.
You must have known that too.
Arcade said:
Yup. If that was the case then it was a very little problem and myself could have resolved it. No need to post it here.
BTW can't get unlock code till now. Isn't there any other way?
I have checked the cid value and its unlockable.
You must have known that too.
Click to expand...
Click to collapse
We have done all we can do... You should go to the official Lenovo Motorola Support forums, they have an area specifically for bootloader unlock issues.
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/bd-p/230
acejavelin said:
We have done all we can do... You should go to the official Lenovo Motorola Support forums, they have an area specifically for bootloader unlock issues.
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/bd-p/230
Click to expand...
Click to collapse
Okay. Thanks for your help.
Its kinda weird problem.
That only my poor friend encountered.
Make sure you have properly installed Motorola Drivers.
Maybe that must be causing the issue..!!
Did u find any solution or Lenovo care helped u in any way ? I recently got my g3 and facing same issue . Everything is installed properly drivers and all . Device is unlockable as well . Tried changeing pc as well . Flashed stock firmware and tried again bt no luck . If sm1 faced this , plz tell me the solution . Thanks .
gamerboy_010 said:
Did u find any solution or Lenovo care helped u in any way ? I recently got my g3 and facing same issue . Everything is installed properly drivers and all . Device is unlockable as well . Tried changeing pc as well . Flashed stock firmware and tried again bt no luck . If sm1 faced this , plz tell me the solution . Thanks .
Click to expand...
Click to collapse
What is your output from 'fastboot devices' and 'fastboot oem get_unlock_data'?
acejavelin said:
What is your output from 'fastboot devices' and 'fastboot oem get_unlock_data'?
Click to expand...
Click to collapse
fastboot devices shows my device id .
fast oem get_unlock_data shows same result as of OP .
gamerboy_010 said:
fastboot devices shows my device id .
fast oem get_unlock_data shows same result as of OP .
Click to expand...
Click to collapse
Please post bootloader status (verbage and number, like Locked & 0, Engineering & 1, etc) and output of 'fastboot getvar all' please...
acejavelin said:
Please post bootloader status (verbage and number, like Locked & 0, Engineering & 1, etc) and output of 'fastboot getvar all' please...
Click to expand...
Click to collapse
Attached below . PLz help me .
gamerboy_010 said:
Attached below . PLz help me .
Click to expand...
Click to collapse
Unfortunately, everything looks fine... Going to have to say look at the link to Lenovo official forums given a few posts back, nothing else we can do.
Hi all,
I have a Straight Talk Galaxy A20, model SM-S205DL. Will root instructions work for this model? I don't notice an OEM unlock option in the Developer Mode menu, but I can boot in download mode. Thoughts? It's been a while since I tried to install custom firmware.
justlance said:
Hi all,
I have a Straight Talk Galaxy A20, model SM-S205DL. Will root instructions work for this model? I don't notice an OEM unlock option in the Developer Mode menu, but I can boot in download mode. Thoughts? It's been a while since I tried to install custom firmware.
Click to expand...
Click to collapse
You need to unlock OEM for it to work
physwizz said:
You need to unlock OEM for it to work
Click to expand...
Click to collapse
Okay. Is there a way to do that other than the developer options menu? If the OEM unlock option isn't there, is there some other method?
justlance said:
Okay. Is there a way to do that other than the developer options menu? If the OEM unlock option isn't there, is there some other method?
Click to expand...
Click to collapse
There is a trick where you change the date to some weeks in the future.
im having the same issue
yea the dev options to show OEM Unlock seems to be gone from Straighttalk/tracfone versions, its even Gone from Download Mode (you dont even SEE the option for long-press vol+ to unlock bootloader)
is there a way to root
Corelua01 said:
is there a way to root
Click to expand...
Click to collapse
Some places claim to be able to change the CID of the phone. Would that help? I imagine once able to load different non-TFN BS firmware on the phone that magic developer option may appear. Or is it a hardware thing and the exynos chip has something to do with it? Not sure how it all works yet. Anyone know what the unlocked us retail model contains?
I'm not smart enough to find out so hopefully someone is and reads this and can chime in regarding all the points...
Me and my arrow...
Ive looked for hours for a way to do this myself and i keep coming up short. Ive tried using fastboot method and it wont work. Its got a qualcomm chipset. A couple guides that i did find used using fastboot commands but they didnt work and i cant find anything else so far. The tablet is carrier unlocked to the best of my knowledge. Please guys if anyone could point me in the right direction i have no problem with doing the work i just need a nudge or even a possible solution if anyone can help. Thanks in advance for your time and attention to hear me out and for any help you could give.
ronnieshane1 said:
Ive looked for hours for a way to do this myself and i keep coming up short. Ive tried using fastboot method and it wont work. Its got a qualcomm chipset. A couple guides that i did find used using fastboot commands but they didnt work and i cant find anything else so far. The tablet is carrier unlocked to the best of my knowledge. Please guys if anyone could point me in the right direction i have no problem with doing the work i just need a nudge or even a possible solution if anyone can help. Thanks in advance for your time and attention to hear me out and for any help you could give.
Click to expand...
Click to collapse
First of all you have to mention the information about your device like device name,android version then we can help your
the_arxyn said:
First of all you have to mention the information about your device like device name,android version then we can help your
Click to expand...
Click to collapse
I thought I did when I created the post.im not used to posting on here and must have done it wrong sorry. It's a Blu M8L 2002 tablet running M0220WW firmware on Android 11. It has a Qualcomm chipset and I believe it is unlocked USA version
ronnieshane1 said:
I thought I did when I created the post.im not used to posting on here and must have done it wrong sorry. It's a Blu M8L 2002 tablet running M0220WW firmware on Android 11. It has a Qualcomm chipset and I believe it is unlocked USA version
Click to expand...
Click to collapse
Sorry my mistake not noticed in the title
You can follow this website https://www.google.com/url?sa=t&sou...oQFnoECA4QAQ&usg=AOvVaw2D0-geZL-AyAdYhvITs7nj
If it doesn't work show the error message
the_arxyn said:
Sorry my mistake not noticed in the title
You can follow this website https://www.google.com/url?sa=t&sou...oQFnoECA4QAQ&usg=AOvVaw2D0-geZL-AyAdYhvITs7nj
If it doesn't work show the error message
Click to expand...
Click to collapse
That's one of the guides that I mentioned that I tried. After using both unlock commands the response was FAILED (remote: unknown cmd.) I tried to use the fastboot OEM device-info command and got the same response
Tablet's OS is Android 11 GO, it got released 2020.
Is "OEM Unlock" option provided in Developer Settings? if so have you turned it on and afterwards rebooted the tablet?
Have you installed the Fastboot driver that's suitable to tablet?
If Fastboot returns "FAILED: (remote: unknown cmd.) " then Fastboot is obviously not supported.
the_arxyn said:
Sorry my mistake not noticed in the title
You can follow this website https://www.google.com/url?sa=t&sou...oQFnoECA4QAQ&usg=AOvVaw2D0-geZL-AyAdYhvITs7nj
If it doesn't work show the error message
Click to expand...
Click to collapse
That's one of the guides that I mentioned that I tried. After using both unlock commands the response was FAILED (remote: unknown cmd.) I tried to use the fastboot OEM device.
jwoegerbauer said:
Tablet's OS is Android 11 GO, it got released 2020.
Is "OEM Unlock" option provided in Developer Settings? if so have you turned it on and afterwards rebooted the tablet?
Have you installed the Fastboot driver that's suitable to tablet?
If Fastboot returns "FAILED: (remote: unknown cmd.) " then Fastboot is obviously not supported.
Click to expand...
Click to collapse
I realized i had my command line in the wrong place and i corrected it and now the commands are recognized but they are still failing. I do have the oem unlock option turned to unlock and im using the adb and fastboot quick setup from xda to use on my computer. I honestly cant figure out where im going wrong this time. Ive used adb and fastboot commands before. Im no expert but im not totally green either. Still thank you guys for attempting to help me out. It really is appreciated
jwoegerbauer said:
Tablet's OS is Android 11 GO, it got released 2020.
Is "OEM Unlock" option provided in Developer Settings? if so have you turned it on and afterwards rebooted the tablet?
Have you installed the Fastboot driver that's suitable to tablet?
If Fastboot returns "FAILED: (remote: unknown cmd.) " then Fastboot is obviously not supported.
Click to expand...
Click to collapse
I may have the wrong driver. As soon as i get back home ill try the one from the link you gave me and post my result. Thanks again
@ronnieshane1 Did you ever figure this out, I'm about to dive in and figured I'd see if there is an update before so?
No I finally just gave up. Sorry
Jacob_dillon said:
@ronnieshane1 Did you ever figure this out, I'm about to dive in and figured I'd see if there is an update before so?
Click to expand...
Click to collapse
Are you talking about the M8L 2022? I've unlocked the bootloader but can't get it back to recovery and its FRP locked so i can't use ADB. ugh.
Also, its a Unisoc chip I think.
You have to use a modified fastboot and get the identifier token.
r1pp3d2 said:
You have to use a modified fastboot and get the identifier token.
Click to expand...
Click to collapse
How do you do that?
Damonkg1 said:
How do you do that?
Click to expand...
Click to collapse
Look up modified fastboot for spreadrum devices. There is also a guide on hovatek forum.
For anyone and everyone who has had any trouble locating the firmware files (.pac) for the 2022 BLU M8L tablet, I FINALLY, after more than a month of searching found them on needrom.
Link is: https://www.needrom.com/download/blu-m8l-2022-m0220w/
Since idk if the link will be redacted or edited out, you can also google needrom and M0220WW
Be carefull when downloading the fireware for the M8L and pay close attention to the version your needing. From all that I gathered, there are mutiple versions...M0170WW, M0171WW, M0173WW, M0174WW, and the one I have that I have yet to find anywhere on the net. Its the most recent ..the M0176UU. If anyone happens to have this version, please make a full backup image and post it here. Thank you
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
TimmyP said:
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
Click to expand...
Click to collapse
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
TimmyP said:
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
Click to expand...
Click to collapse
Permanent unlock is sim unlocking, has nothing to do with OEM unlocking
Thats great thanks
I got it. Set to midi connection so ADB detects phone.
adb shell
pm disable-user com.qualcomm.qti.uim
Now OEM unlocking is ungreyed
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
TimmyP said:
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
Click to expand...
Click to collapse
Maybe the site down, probably wait a bit, got the same error too
Thanks Ill get all prudent info in a text file. What a pita. I loathe having a new phone and not knowing whether I can root it. So much setting up already.
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
TimmyP said:
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
Click to expand...
Click to collapse
i got mine around an hour later after applying mine, maybe check hourly to see if you gotten it or not?
Nothing. Tbh I think Im gonna return this. Its only 128gb version and I was much happier with rooted A32 5G.
Sucks cant even use tasker for fun stuff.
Look through the OP9 forums for the OnePlus Tool..... it helps you get the number you write down to request the unlock code from OnePlus, also it can ungrey the OEM switch
Thanks but I already got that stuff requested. Still no token :-( Been talking to support tho they said they are on it!
underworld737 said:
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Click to expand...
Click to collapse
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
barguybrady said:
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
Click to expand...
Click to collapse
Try ,,,,,,fastboot oem unlock,,,,
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
TimmyP said:
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
Click to expand...
Click to collapse
I already have that... Hence my confusion.
I'm thinking that there's Just One Little Thing I'm doing wrong here... Can't figure it out..!
Aha. I had been doing it in the wrong order.
Bash:
fastboot devices
fastboot flash cust-unlock unlock_code.bin
fastboot oem unlock