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.
Related
Dear XDA experts,
I'm trying to unlock the bootloader on my HTC one X phone for AT&T. My reason for doing this is i am no longer using AT&T so i unlocked the phone but i would also like to be able to use the wifi hotspot function which AT&T has blocked.
I followed this thread : http://forum.xda-developers.com/showthread.php?t=1671396 to accomplish the unlock but I'm getting this error when typing "su" in the adb shell command: /system/bin/sh: su: not found
127|[email protected]:/ $
I rooted the phone (AT&T HTC ONE X) using this technique : http://www.androidauthority.com/att-one-x-root-87398/
I'm a little new to all this so I would really appreciate any input.
Thanks a lot!
The Issue might be caused by your Firmware I Personally Recommend using Hasoon2000's AIO Toolkit which can be located @ http://forum.xda-developers.com/showthread.php?t=1952426 ive tried it on 5 of my devices all One X and works without an issue. If you run into errors feel free to contact me
new development
FragmentedLogik said:
The Issue might be caused by your Firmware I Personally Recommend using Hasoon2000's AIO Toolkit which can be located @ http://forum.xda-developers.com/showthread.php?t=1952426 ive tried it on 5 of my devices all One X and works without an issue. If you run into errors feel free to contact me
Click to expand...
Click to collapse
I'm really grateful for your reply, thanks for taking the time to answer me.
I was about to download the toolkit you mentioned but i noticed it says v2.0 and I'm running 2.2 is that still going to work ?
Also i before i read your post i had tried this technique :http://www.bestandroidblog.com/root...phone-on-2-20-firmware-with-x-factor-exploit/ which actually almost worked. What i mean is i was able to get the unlock token from http://htcdev.com/ but when i try to flash it to the device it just says "waiting for device" and i don't get the message on my phone asking if i would like to proceed with the unlocking of the bootloader.
C:\Android>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
The phone is on charge only mode and has usb debugging enabled.
Please help.
timaloud said:
I'm really grateful for your reply, thanks for taking the time to answer me.
I was about to download the toolkit you mentioned but i noticed it says v2.0 and I'm running 2.2 is that still going to work ?
Also i before i read your post i had tried this technique :http://www.bestandroidblog.com/root...phone-on-2-20-firmware-with-x-factor-exploit/ which actually almost worked. What i mean is i was able to get the unlock token from http://htcdev.com/ but when i try to flash it to the device it just says "waiting for device" and i don't get the message on my phone asking if i would like to proceed with the unlocking of the bootloader.
C:\Android>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
The phone is on charge only mode and has usb debugging enabled.
Please help.
Click to expand...
Click to collapse
Yes all the Version Means is it's Version 2.0 for the ToolKit, You probably have the 2.20 Firmware on Your phone... any way yes the ToolKit Will work, as a Troubleshooting step, make sure that you have the latest fastboot Drivers for HTC, and those can be found @ http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe also check your device manager and make sure that your PC is recognizing the Device, it should say Android Phone --> My HTC, or something similar.
FragmentedLogik said:
Yes all the Version Means is it's Version 2.0 for the ToolKit, You probably have the 2.20 Firmware on Your phone... any way yes the ToolKit Will work, as a Troubleshooting step, make sure that you have the latest fastboot Drivers for HTC, and those can be found @ http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe also check your device manager and make sure that your PC is recognizing the Device, it should say Android Phone --> My HTC, or something similar.
Click to expand...
Click to collapse
Ok successfully unlocked with the toolkit finally. I cannot begin to thank you.
Have a great weekend!
This phone(honor 4c indian edition) belonged to my friend and he rooted with kingo root app and aftewards unrooted it. Then he gave it to me to do it properly on opening the fastboot mode i've discovered that the bootloader was unlocked, so i tried flashing twrp recovery but it failed and just showed command not allowed. Ive tried factory reset, updating firmware by upadate.app, ive even tried flashing the stock rom through fastboot(extracted from the update.app) but nothing works . So as a last resort i came here , please tell me what to do right now.
Note: the phone was always on stock rom and nobody intentionally tried to unlock the bootloader im guessing the kingo root did it. And it also does not work right now.
man00701 said:
This phone(honor 4c indian edition) belonged to my friend and he rooted with kingo root app and aftewards unrooted it. Then he gave it to me to do it properly on opening the fastboot mode i've discovered that the bootloader was unlocked, so i tried flashing twrp recovery but it failed and just showed command not allowed. Ive tried factory reset, updating firmware by upadate.app, ive even tried flashing the stock rom through fastboot(extracted from the update.app) but nothing works . So as a last resort i came here , please tell me what to do right now.
Note: the phone was always on stock rom and nobody intentionally tried to unlock the bootloader im guessing the kingo root did it. And it also does not work right now.
Click to expand...
Click to collapse
Kingo root and other such apps use exploits to get the root done. Not the safe way to do.
You just have to unlock the bootloader using the standard procedure for your phone and you are good to go.
It does not matter that it's unlocked, just do it again once more.
Just google or search here on XDA and enjoy your phone.
muradulislam said:
Kingo root and other such apps use exploits to get the root done. Not the safe way to do.
You just have to unlock the bootloader using the standard procedure for your phone and you are good to go.
It does not matter that it's unlocked, just do it again once more.
Just google or search here on XDA and enjoy your phone.
Click to expand...
Click to collapse
I did that but the fastboot oem unlock xxxxxx command also isn't working
Sent from my Moto G 2014 using XDA-Developers mobile app
man00701 said:
I did that but the fastboot oem unlock xxxxxx command also isn't working
Click to expand...
Click to collapse
Have you turned on USB debugging and OEM unlock in the developer options?
Developer options can be seen after repeatedly tapping build number 7 times.
muradulislam said:
Have you turned on USB debugging and OEM unlock in the developer options?
Developer options can be seen after repeatedly tapping build number 7 times.
Click to expand...
Click to collapse
I've enabled the usb debugging, but the oem unlock option isn't there in developer options
Sent from my Moto G 2014 using XDA-Developers mobile app
man00701 said:
I've enabled the usb debugging, but the oem unlock option isn't there in developer options
Click to expand...
Click to collapse
I don't own a 4C now but if I remember correctly, there used to be something like that or may be I am mistaken.
Anyways, firing fastboot devices does show your device in the listed devices?
And have you tried flashing an image again after firing that unlocking command?
Yes it does show up in fastboot devices
Sent from my Moto G 2014 using XDA-Developers mobile app
After revoking the debugging authorisation and factory resetting the phone, the unlock command worked!!! And everything else also works. Thanks for your help, appreciate it
Sent from my Moto G 2014 using XDA-Developers mobile app
man00701 said:
After revoking the debugging authorisation and factory resetting the phone, the unlock command worked!!! And everything else also works. Thanks for your help, appreciate it
Click to expand...
Click to collapse
Nope, thank you for teaching me that if unlock command does not work, one can do the above steps to make it work.
We are even then:highfive:
muradulislam said:
Nope, thank you for teaching me that if unlock command does not work, one can do the above steps to make it work.
We are even then:highfive:
Click to expand...
Click to collapse
Guess thats another way of looking at things. Cheers!!!
Sent from my Moto G 2014 using XDA-Developers mobile app
Hi guys I downloaded the REtail version of my firmware for my device here https://mirrors.lolinet.com/firmware/motorola/denver/official/RETUS/
But when I patched and installed it via adb it seems to be a success
HOWEVER
I am STILL get the metro by tmobile splash screen on booting and I still have metro by tmobile apps pre installed on my phone. AND THAT Annoying metro news screen when you swipe to the left.
Am I not installing the correct firmware xda bros? TIA
Futtbucker34 said:
Hi guys I downloaded the REtail version of my firmware for my device here https://mirrors.lolinet.com/firmware/motorola/denver/official/RETUS/
But when I patched and installed it via adb it seems to be a success
HOWEVER
I am STILL get the metro by tmobile splash screen on booting and I still have metro by tmobile apps pre installed on my phone. AND THAT Annoying metro news screen when you swipe to the left.
Am I not installing the correct firmware xda bros? TIA
Click to expand...
Click to collapse
You flashed it using the flash_file.xml as a reference for flash commands?
These are my recommended steps If you have a Windows machine.
How to Change Software Channel
sd_shadow said:
You flashed it using the flash_file.xml as a reference for flash commands?
These are my recommended steps If you have a Windows machine.
How to Change Software Channel
Click to expand...
Click to collapse
sd_shadow said:
You flashed it using the flash_file.xml as a reference for flash commands?
These are my recommended steps If you have a Windows machine.
How to Change Software Channel
Click to expand...
Click to collapse
Thank you sir I can confirm the flash_file.xml reference was followed in the commands. I double checked.
I LMSA says it can't verify my software and won't let me continue . I got the new september update and i think lmsa don't have it yet. idk why else it would say this.
bump. Anyone?
update: I Reflashed 3 times successfully only the SOFTWARE CHANNEL still shows Universal SKU
This picture i found from ebay is from the same model I have. Yet they have no metro bloatware and North America Retail under software channel, Mine says Universal SKU.
https://mirrors.lolinet.com/firmwar...T_regulatory-DEFAULT_cid50_CFC_R3_CFC.xml.zip Is the firmware I used to flash\
THanks in advanced!
Futtbucker34 said:
Thank you sir I can confirm the flash_file.xml reference was followed in the commands. I double checked.
I LMSA says it can't verify my software and won't let me continue . I got the new september update and i think lmsa don't have it yet. idk why else it would say this.
Click to expand...
Click to collapse
Your best bet is honestly to just either use a custom rom or to remove all the bloatware either manually or systemlessly.
Long Story - Short:
Just got home with an Unlocked sofiap XT2043 - Moto G Stylus , networked unlocked, and I am able to toggle the OEM Unlock switch in Developer Options, However:
how did y'all unlock the Bootloader to start with ?
fastboot flashing unlock = FAILED
fastboot oem unlock = FAILED
is there a method to discern my oem unlock code ?
Thanks in Advance for any assistance !
barguybrady said:
Long Story - Short:
Just got home with an Unlocked sofiap XT2043 - Moto G Stylus , networked unlocked, and I am able to toggle the OEM Unlock switch in Developer Options, However:
how did y'all unlock the Bootloader to start with ?
fastboot flashing unlock = FAILED
fastboot oem unlock = FAILED
is there a method to discern my oem unlock code ?
Thanks in Advance for any assistance !
Click to expand...
Click to collapse
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
I am trying to unlock my nord ce 2 bootloader but everytime I try to access bootloader mode, it says something like Unlock_Verify_device ok and then reboots
how can I unlock the bootloader? Same happens on my nord 2. Oem unlocking is enabled and I have no selection of advanched startup options. I have magisk boot.img to flash
Can't say I experienced that myself. The message you got looks promising. The 'unlock_verify_device ok' message means you're getting to fastboot. But I'm not sure why it's rebooting. Do you have enough time to run the command 'fastboot devices'?
Also, what version is your firmware?
Here is the guide I used when I was unlocking the bootloader: https://www.droidwin.com/how-to-unlock-bootloader-on-oneplus-nord-ce-2/
I am running android 12 beta on oxygenos
Edit: fastboot doesn´t even find the device
Oh, now it tells that serial is not match. what's going on?
so? Can anyone help? Phone keeps saying that serial is not match and then reboots. Is this phone just a joke or something? Gonna buy samsung if yes.
What model is your phone? I wasn't aware of the Android 12 beta being available for the Nord CE 2. Another thing to try is this tutorial to manually install the OnePlus drivers: https://www.droidwin.com/fix-android-device-not-showing-in-fastboot-mode/
Was looking on the nord ce 1 xda Forum. It's only recently that a few roms and twrp are starting to appear, so there is hope. IMO oneplus need to take £$50 off the price, more users = more chance of getting more development
mr_munch said:
Can't say I experienced that myself. The message you got looks promising. The 'unlock_verify_device ok' message means you're getting to fastboot. But I'm not sure why it's rebooting. Do you have enough time to run the command 'fastboot devices'?
Also, what version is your firmware?
Here is the guide I used when I was unlocking the bootloader: https://www.droidwin.com/how-to-unlock-bootloader-on-oneplus-nord-ce-2/
Click to expand...
Click to collapse
I don't have fastboot on my device Nord ce 2 ..when I type fastboot reboot bootloader then it directly reboot into my device ..Please somebody help me.Im on current Android 12.1 version
neilop7 said:
I don't have fastboot on my device Nord ce 2 ..when I type fastboot reboot bootloader then it directly reboot into my device ..Please somebody help me.Im on current Android 12.1 version
Click to expand...
Click to collapse
Fastboot is stuffed on this device. There's no longer a way to make fastboot work.
burningcreation said:
Fastboot is stuffed on this device. There's no longer a way to make fastboot work.
Click to expand...
Click to collapse
I wanna unlock bootloader..is there any way to unlock ?
neilop7 said:
I wanna unlock bootloader..is there any way to unlock ?
Click to expand...
Click to collapse
No unfortunately.
burningcreation said:
No unfortunately.
Click to expand...
Click to collapse
Did you able to unlock bootloader?
neilop7 said:
Did you able to unlock bootloader?
Click to expand...
Click to collapse
No I am not able to unlock the bootloader either. There is currently nothing we can do.
Hi everyone, any update on this? Did someone manage to unlock the bootloader?
If I'm not mistaken. You can rollback to android 11 to get it back.
I'm currently facing the same problem, so I tried rolling back and have downloaded over 20 rollback zips now, and extracted them. All won't work, it reboots in recovery. And it is like fastboot just doesn't exist. So yeah they probably messed it up.
I'm so sad, I switched from Iphone to Oneplus partly because of the rooting options. So sad
Can I do this trough adb or not?
NiekKamer0105 said:
I'm currently facing the same problem, so I tried rolling back and have downloaded over 20 rollback zips now, and extracted them. All won't work, it reboots in recovery. And it is like fastboot just doesn't exist. So yeah they probably messed it up.
I'm so sad, I switched from Iphone to Oneplus partly because of the rooting options. So sad
Can I do this trough adb or not?
Click to expand...
Click to collapse
You don't extract it though. You just rename it by removing the _Rollback at the end.
See here: https://droidwin.com/downgrade-oneplus-nord-ce-2-from-android-12-to-android-11/
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