I have got a Motorola E5 plus device (Model: XT1924-3). Which restarts on logo screen (seems OS crashed).
Able to access the bootloader and recovery mode but oem is locked so can't flash new image using RSD Lite.
Have tried factory reset, wiping the user data and cache nothing works. Also, I have tried using moto smart assistant but it required debugger mode enables but unfortunately it is disabled in my case.
Could anyone help me to identify ways to unlock oem in current case or is there any other way to flash/ recover the OS.
Thanks a lot.
You can unlock the phone through recovery. You can than install twrp and flash a new rom. But did this just randomly happen or did you try and flash something? If it randomly did this than your phone may have a issue.
Smurfy76 said:
You can unlock the phone through recovery. You can than install twrp and flash a new rom. But did this just randomly happen or did you try and flash something? If it randomly did this than your phone may have a issue.
Click to expand...
Click to collapse
Hi! I'm in the same situation as OP. What's the way to unlock through recovery? I've tried adb commands to change the flashing_locked flag using "adb shell setprop ro.oem_unlock_supported 1" and "adb shell setprop ro.oem_unlock_allowed 1". The flags don't get saved after the phone boots again into fastboot.
Thanks in advance!
You unlock it through Motorola website. Plenty of guides for that here.
Related
I tried following this guide to downgrade to 4.2.2 so that I could root my AT&T device.
I was able to adb and fastboot into the device. And I flashed the ATT CU update with fastboot.
After that the device constantly reboots after reaching the M logo screen,
I can boot into the bootloader, and I can send fastboot commands, but not any adb commands.
I also cannot load any of the options in the bootloader (Recovery, Factory, etc), they simply reboot the phone.
I don't care what version of Android I go to as long as it gives me a working phone. Please help!
Thanks.
Edit: I was able to recover my phone by flashing the 4.4 update. I would like to know where I went wrong, so that I could possibly still do the downgrade>root>upgrade path.
UberSprode said:
I tried following this guide to downgrade to 4.2.2 so that I could root my AT&T device.
I was able to adb and fastboot into the device. And I flashed the ATT CU update with fastboot.
After that the device constantly reboots after reaching the M logo screen,
I can boot into the bootloader, and I can send fastboot commands, but not any adb commands.
I also cannot load any of the options in the bootloader (Recovery, Factory, etc), they simply reboot the phone.
I don't care what version of Android I go to as long as it gives me a working phone. Please help!
Thanks.
Edit: I was able to recover my phone by flashing the 4.4 update. I would like to know where I went wrong, so that I could possibly still do the downgrade>root>upgrade path.
Click to expand...
Click to collapse
You know there's a way to unlock your bootloader for $43ish. Many success stories. Your phone playing life would improve greatly.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
I'm running the Android SDK on linux (Ubuntu). My stock H81110n G4 is connected via USB cable and it is listed properly when I run `adb devices`. However, the command `adb reboot bootloader` simply reboots the phone into Android.
I can't boot into the bootloader. What is the solution for this?
Of course, I have USB Debugging enabled. I also checked OEM Unlock just to see if that helped. It didn't. My phone is not bootloader unlocked yet. I plan to do that next, but first I want to be reboot into the bootloader (e.g., to get the device ID for the LGE Developer site).
Thanks for any assistance.
You don't need to use the LGE developer site to unlock your bootloader. From what I understand, as soon as you tick the OEM unlock then you are unlocked. The LG site is for 815 only.
hyperfriend said:
You don't need to use the LGE developer site to unlock your bootloader. From what I understand, as soon as you tick the OEM unlock then you are unlocked. The LG site is for 815 only.
Click to expand...
Click to collapse
Thanks for that info. However, that's not really my question. My question is why `adb reboot bootloader` causes the phone to boot into Android instead of into the bootloader. That's my real issue.
`adb reboot download` doesn't work either. It simply reboots into Android. Therefore, I'm not able to install TWRP or do anything else I want to do.
Also, using the phone's power and vol-down buttons will not boot it into the bootloader, so something seems strange with this phone. I haven't run into this issue on other phones. I rooted an HTC One M9 today. But I can't get past this step with the LG G4.
MountainX said:
Thanks for that info. However, that's not really my question. My question is why `adb reboot bootloader` causes the phone to boot into Android instead of into the bootloader. That's my real issue.
`adb reboot download` doesn't work either. It simply reboots into Android. Therefore, I'm not able to install TWRP or do anything else I want to do.
Also, using the phone's power and vol-down buttons will not boot it into the bootloader, so something seems strange with this phone. I haven't run into this issue on other phones. I rooted an HTC One M9 today. But I can't get past this step with the LG G4.
Click to expand...
Click to collapse
That is strange, but I don't see why you need to reboot to the bootloader if it's already unlocked. Try to flash TWRP and see what happens.
hyperfriend said:
That is strange, but I don't see why you need to reboot to the bootloader if it's already unlocked. Try to flash TWRP and see what happens.
Click to expand...
Click to collapse
Like I mentioned in the OP, my H81110n LG G4 is stock. It is not rooted. As far as I know, flashing TWRP requires booting into recovery / download mode first. Here's how I usually do it:
In a linux terminal:
Code:
/opt/android-sdk-linux/platform-tools# ./adb devices
/opt/android-sdk-linux/platform-tools# ./adb reboot download
/opt/android-sdk-linux/platform-tools# ./fastboot flash recovery recovery.img
This phone will not boot into download (or bootloader). All it does is reboot into Android OS. Any ideas?
Bump.
I'm having this same issue. Hardware keys and proper adb commands to get to bootloader are ineffective. Suggestions??
---------- Post added at 02:33 AM ---------- Previous post was at 02:25 AM ----------
MattKilla said:
Bump.
I'm having this same issue. Hardware keys and proper adb commands to get to bootloader are ineffective. Suggestions??
Click to expand...
Click to collapse
ACTUALLY-- solved.
Hold Vol-Up and plug into the PC. Do not press power. Holing Vol-Up and inserting the USB cable will trigger "download mode". Bootloader.
Booting into download mode is Vol UP + Plug in USB (While the phone is off)
You can then use the low effort root if on firmware H or Rhyda's thread in the dev section for firmware N to get root.
I can't get into the bootloader either, I think T-Mobile did something. After rooting you can download a terminal emulating app and just run the command:
>su
(grant SU permissions)
>reboot bootloader
Have you tried flashing TWRP using Flashify? I think that how I installed it on my H811 (should've taken notes >.< )
I don't know of any way to access the bootloader either. Typing "su" and "reboot bootloader" in the terminal doesn't work, nor does using an app like ROM Toolbox.
I posted this in another thread. This was the only way I could workaround this problem.
Many ADB bootloader commands do not work on this model. Nor do I think they work on any G4. Not sure why LG went this route, whereas on the V10 (some models at least) it's as easy as a Nexus.
I forgot, how do you reboot into fastboot again?
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.
try the "fastboot continue" command
dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not
Hi guys, thank you ahead for helping me.
I've unlocked the bootloader successfully and installed TWRP and Rooted, but found some issues with Banking apps, PayPal, NFC, Google pay, so I decided to lock the bootloader again.
Following the procedure by Jerry08 downloaded C35, installed via TWRP, and stock recovery was restore just fine.
But while trying to access Bootloader I'm not able to, tried:
adb reboot fastboot
adb reboot bootloader
Holding Vol down and power
Deep-in test says: "you can only apply to exit in-depth test after carrying out bootloader lock operation in fastboot mode"
Last method worked, I get "bootloader" with Chinese words flashes for a second and then reboots to system.
I'm able to boot into stock recovery, but not into Bootloader for some reason, Formatted Data and tried again without luck.
Any suggestions?
Installed RMX1931EX_11_A.09_200116_dfb212dd.ofp with Auth-Flash and MSMTool, you need to purchase credits 7$, use #3 MSMtool from Auth-fash and done bootloader locked and brand new phone.
But bootloader was still unlocked, and not able to access bootloader via adb reboot bootloader.
In-deph test exit does not work either
any updates i have the same problem
mike_san said:
Installed RMX1931EX_11_A.09_200116_dfb212dd.ofp with Auth-Flash and MSMTool, you need to purchase credits 7$, use #3 MSMtool from Auth-fash and done bootloader locked and brand new phone.
But bootloader was still unlocked, and not able to access bootloader via adb reboot bootloader.
In-deph test exit does not work either
Click to expand...
Click to collapse
solved ????
terrymorris said:
solved ????
Click to expand...
Click to collapse
Nope, still cant access to bootloader to lock it, it keeps rebooting even after using realme flash.