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/
Related
So. I would like to unlock the bootloader. All fine, I get the code, and when I type in
Code:
fastboot -i 0xfce oem unlock 0xcodehere
it says
Code:
FAILED: Command did not succeed.
However, when I do it the second time (enter the command right again) it says OKAY but the device will end up on a bootloop next start, and when I try to flash a kernel, it says not allowed.(fastboot) If I flash when unlocked without restarting device, the device will shut down at SONY logo. Is it possible that I got a temporary unlock? How could I unlock the device successfully?(permanently) I tried it with Flashtool, and the same results. I literally tried everything. I also cannot install the permanent OS-independent CWM because of the shutdown at the SONY logo. I didn't yet contact my service provider, but I don't think they would like the idea. I really want CyanogenMod on my device, and I'd also like to fix some problems if I can. Please try to help ASAP. Thanks!
Code:
C:\Users\Felix>fastboot devices
e46fc864 fastboot
C:\Users\Felix>fastboot getvar version
version: 0.5
finished. total time: 0.000s
C:\Users\Felix>fastboot -i 0xfce oem unlock 0xCODEHERE
...
FAILED (remote: Command did not succeed)
finished. total time: 0.162s
C:\Users\Felix>
I have the same problem. Did you resolve it?
Open Phone and dial *#*#7378423#*#* go to Service Info->Configuration if Rooting Status says Bootloader unlock allow: No you can't unlock it. If it says Yes go to Sony's official website for unlocking and follow the instructions.
Good Luck.
Xperia M2 D2303 on K.K. 4.4.4
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
So I've pretty much hit a wall. I have unlocked bootoader, and everytime I try to enter into factory resetting via volume + power button, it'll boot into "your device is booting now..." and it'll stay there. Same thing if I try to do it via the settings.
Whenever I try to install custom recovery or anything, I get this message.
C:\adb>fastboot flash recovery TWRP-CN.img
target reported max download size of 471859200 bytes
sending 'recovery' (29218 KB)...
OKAY [ 0.789s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.804s
I've tried all sorts of twrp files. My phone has locked me out of changing anything from adb commands it seems. How do I fix this?
My FRP is also locked, if that matters. I've tried to delete all accounts from my phone, as well as the "find my phone" option.
I'm on Anroid 7, EMUI 5.
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot devices
73QDU16B22001173 fastboot
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (remote: Command not allowed)
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format cache
FAILED (remote: Command not allowed)
OEM is greyed out in the developer settings, I can't activate it or decative.
Try the unlock command again for the bootloader. This worked for me even when it was unlocked before
TomboIa said:
Try the unlock command again for the bootloader. This worked for me even when it was unlocked before
Click to expand...
Click to collapse
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.
Zebieok said:
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.
Click to expand...
Click to collapse
Dont share your unlock key here, and are you sure that was your bootloader unlock keys.
Frp lock means your bootloader is locked.
FRP lock is a security action, for remove them you must boot a device and remove all google accounts.
Unfortunately this casw happened to me, when i want factory reset my phone, his dead and i cant boot it again just fastboot work but FRP LOCK activate and i cant flash any thing, give error command not allowed, in last i have to go to repair services, and they do this with hard box (maybe chimera or sigma.. Or other).
If you can boot your device you can do any thing, but if your device get bootloop go to services center.
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
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: