I tried to unlock my Moto G using the standard way suggested on Motorola site, by passing the command - fastboot oem unlock <unlock code> to fastboot screen via command prompt. Got the below messages on command prompt.
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 10.225s
After that, screen on phone showed the message - UNLOCK...
& got stuck on that. I switched off & started again in Fastboot mode. On the screen it said - Device is UNLOCKED. Status Code: 3
Thinking that my phone did got unlocked, I restarted it in normal mode. After taking some time on logo screen, the phone started normally. Then to verify that its properly rooted or not, I tried to remove few apps which comes pre-installed, as I should be getting access to remove them in rooted phone; but didn't got the uninstall option.
Secondly, I installed Root checker apps from Play Store which gives the rooting information; checked with two random apps, both said that Device is not properly rooted.
Tried with SuperSU app as well, on opening it says, Device not rooted.
Hence I concluded that there was some problem with rooting and its not completely rooted.
Then tried to repeat the process with same method which I did earlier, but then got the below message saying its already unlocked.
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.021s
So now its unlocked as per fastboot screen, but in actual its not giving features or access of unlocked device.
Please suggest what to do to correct it. And will it create some problem if I try to flash any ROM in same condition.??
Current Android version installed in my phone is 5.1 - Lollipop.
Problemo, Solved.
Never mind, it got resolved.
First of all, the steps which I followed was only to unlock the device; while I was checking the root access after that.
So I simply flashed SuperSU with TPRW recovery, and phone got rooted too in no time.
Thanks anyway.
deleted, wrong thread
Related
So 10 hours ago I decided I wanted to root my phone to install some apps and maybe even a cool ROM.
I read that the first step is to unlock the bootloader. I have trying my hardest to do this first step for 10 hours.
I've read 4-5 different tutorials twice on xda.
My phone is:
HTC One A9(hiae), bought in Sweden
hTc download mode
*** LOCKED ***
htc_hiaeuhl PVT S-ON
LK-1.0.0.000
[email protected]
OpenDSP-7.8.2.00197-8952_1228
OS-1.56.401.70
Jan 22 2016....
I have tried the normal way through htcdev.com even had the Unlock_code.bin at one point. But I had to reinstall all drivers twice to get it.
I have tried using the WinDroid Toolkit, no better than the manual way.
I got my hard earned token ID through both ways.
I find that every time I want to use fasstboot to send over a file i.e. "fastboot flash recovery twrp.img" hTc download mode is stuck at Start download, like I need to confirm it but can't because the command failed. The same goes for the Unlock_code.bin, can't send it over.
Code:
C:\adb>fastboot devices
HT5AVBE04449 fastboot
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.003s
I can get past this next problem temporarily by reinstalling all drivers, tedious.
Code:
C:\adb>fastboot oem get_identifier_token
...
FAILED (command write failed (Unknown error))
finished. total time: 5.002s
Possible problems:
hTc download mode: I need to accept the download before fastboot give up, instant.
Win10: Bad OS for this?
USB connectors: Not enough power? Some other USB devices don't work here normally.
HTC Sync Manager: I've not bother installing the software.
Solution
I've made it;
I'm not sure if I was in the real download mode at the time, but that might have been it.
Also this time I redid everything, deleted all the drivers correctly and installed via Universal Naked Drivers
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
ouioui01 said:
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
Click to expand...
Click to collapse
For my phone it is 8 taps and yes. Every time I start a new Android I do a OEM unlock.
But I might be correct to change USB connector.
Dear people,
First of all, although dilligent and trying to do my homework, I am a total newbie regarding anything Android. Therefore, if I am posting on the wrong section of the site, please let me know and I will try my best to fix it.
That being said, I have a Moto G3 (Moto G 2015), model XT1543 (osprey), that is stuck in the fastboot boot. I have searched a lot of the web trying to find solutions and, after having failed all of them, decided to come here for assistance.
My device only boots and displays:
AP Fastboot Flash Mode (Secure)
version downgrade for recovery
failed to validate recovery image
ERROR: Failed to pass verification, backup to fastboot
Fastboot Reason: Fall-through from recovery boot mode
I already downloaded the appropriate TWRP recovery image for the device (osprey), but the bootloader is locked and, since I can't get into the system properly, I can't switch the "Unlock OEM boot" flag when the full system is running.
In particular, when I try to flash TWRP, this is what I get:
# fastboot flash recovery twrp-3.1.0-1-osprey.img
target reported max download size of 268435456 bytes
sending 'recovery' (7546 KB)...
OKAY [ 0.373s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.454s
Indeed, since I am only in fastboot mode, I went away and requested a boot unlock code from Motorola and trying to unlock the bootloader and this is what I get:
# fastboot oem unlock <my-code-here>
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.034s
I already tried looking at similar questions in many, many forums and no answer actually applied to my device (including, for example, https://forum.xda-developers.com/2015-moto-g/help/moto-g3-struck-fastboot-screen-t3542147 and even others for other models and vendors).
Thanks in advance for any help.
At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Sent from my MotoG3 using Tapatalk
riggerman0421 said:
At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Click to expand...
Click to collapse
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).
rtbrito said:
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).
Click to expand...
Click to collapse
You can follow the guide here. Try it with the latest firmware available here.
Broadcasted from Zeta Reticuli
hey i have a moto g3 2016 with internal memory 8 gb which isn't sufficient for me. So one of my friend suggested me to root my phone so that i could uninstall my internal apps but when i googled i got to know that we need to unlock boot load first i tried many tutorials about how to unlock bootload but it failed everytime saying(i used ABD and FAST BOOT)
(bootloader) Unlock code = QJRAF2YW7GEJIYV3SQJ3
(bootloader) fastboot oem lock currently disabled!
FAILED (remote failure)
finished. total time: 0.030s
please help!!!!!
(i noticed every phone which every youtuber was using had AP Fastboot Flash Mode (secure)
but my phone had AP Fastboot Flash Mode (Not Secure) )
Dear Community!
I need your help! After factory resetting my Motorola G3 it stucks on logo. I can access bootloader and recovery mode, but even after doing factory reset again it gets stuck on the same place. I can run adb and fastboot and it recognizes my device, but I can't install new OS because the phone is locked. I also cannot unlock - after entering "fastboot oem unlock" and the unlock key from Motorola, I get the message
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote: '')
Finished. Total time: 0.020s
Probably, because I can't access the device's menu and allow rooting. I would appreciate any help! I am sorry, probably I made some mistakes in my explanations... Thank you!
overtones said:
Dear Community!
I need your help! After factory resetting my Motorola G3 it stucks on logo. I can access bootloader and recovery mode, but even after doing factory reset again it gets stuck on the same place. I can run adb and fastboot and it recognizes my device, but I can't install new OS because the phone is locked. I also cannot unlock - after entering "fastboot oem unlock" and the unlock key from Motorola, I get the message
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote: '')
Finished. Total time: 0.020s
Probably, because I can't access the device's menu and allow rooting. I would appreciate any help! I am sorry, probably I made some mistakes in my explanations... Thank you!
Click to expand...
Click to collapse
See if one of these options work,
https://www.android.gs/unbrick-motorola-moto-g/
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
iqbal.jewel said:
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
Click to expand...
Click to collapse
You can't fix it. :crying: