Hello!
Frequent reader but not so frequent poster...
I have read through jcase's SlapMyMoto thread but am confused when during this process are we supposed to force the phone to boot into recovery and when we should just "let it boot". Throughout the thread there are random references to booting into recovery during this process but no reference to which step.
For example in Step 7 does it automatically reboot into recovery or do I need to hold the volume down button and force it?
Any insight you can provide will be appreciated....
Thanks!
Related
Many people when they first get a Nexus device, choose to unlock the bootloader right away to prevent a mandatory data wipe if they unlock it later. Myself and a few others have encountered a bootloop after doing so. If this happens to you, follow these steps.
1) If your phone is stuck in a bootloop, Hold volume up, volume down & the power button until the phone turns off.
2) Wait a minute as trying to turn the phone back on may be unresponsive.
3) Hold volume up, volume down & power to boot into the bootloader.
4) Toggle to recovery and press the power button.
5) When you see the android laying down: press and hold the power button and immediately press volume up. It should open the menu.
6) Choose wipe data/factory reset. When completed the phone will reboot and should boot to the welcome screen
Hope this helps anyone who has this issue!
If I boot once, then reboot to boot loader then unlock will I be ok? I'm getting mine tomorrow.
Thanks for the heads up. I have no doubt that I will run into this issue and these instructions will help.
Zainiak said:
If I boot once, then reboot to boot loader then unlock will I be ok? I'm getting mine tomorrow.
Click to expand...
Click to collapse
Yes.
Suppose that's from the update that happens when you first boot, we all know how well OTAs and unlocked bootloaders get along.
Sent from N7
This is related to the typical Nexus data partition situation: If the data partition is wiped, the partition needs to be regenerated in some fashion before it can be written to, and this can only be done by booting once into the OS. Recovery and bootloader are unable to complete this operation alone.
If you find yourself in the situation of having wiped both system and data, you must flash any bootable OS version to system & boot via fastboot, and boot into it once, before you will be able to install ROMs via recovery again.
This is very important and I do this with every Nexus device on first boot.
Sent from my Nexus 5 using Tapatalk
This help, also had to format "data" because i skipped the first boot and installed the recovery right away
Thanks for this post
I booted mine straight to bootloader when it came and unlocked it with no problems. I wonder why this only happens sometimes?
did those of you who got a bootloop have to download/install the OTA when it finally booted?
Hello!
Frequent reader but not so frequent poster...
I have read through jcase's SlapMyMoto thread but am confused when during this process are we supposed to force the phone to boot into recovery and when we should just "let it boot". Throughout the thread there are random references to booting into recovery during this process but no reference to which step.
For example in Step 7 does it automatically reboot into recovery or do I need to hold the volume down button and force it?
Any insight you can provide will be appreciated....
Thanks!
Hey,
I've been reading along in the XDA forums for quiet some time now, and have found very useful information on multiple occasions. A general thanks! for that.
Right now I am trying to gain access to a Moto X 2013 (XT1052) with a broken/black screen. The phone is rooted and has a custom recovery installed. Unfortunately USB-debugging was disabled.
I am trying to gain adb-access in recovery in order to try and activate debugging as shown here: http://forum.xda-developers.com/showthread.php?t=2335799
The problem is, I can't get the Phone into recovery mode. fastboot boot recovery.img is disabled on the moto x.
When I'm in fastboot mode and press Vol-Down the phone immediately performs a normal reboot. On a non-broken Moto X Vol-Down and then Vol-Up should bring the phone in recovery.
Can anybody explain this behavior? Is there another way to access recovery?
Thanks in advance!
Lukas
After flashing CM 12 recovery my device shows "no command" error when in recovery
Hi Guys,
I have a moto g 2014 xt 1068
finally decided to install cyanogen mod on my device and used the guide provided here.
I have unlocked the bootloader
I have followed the steps: adb reboot bootloader -> fastboot flash recovery my_image.img -> entered recovery it worked. It didn't have any 'install from zip options'.
The tutorial said to copy the files on the internal card, which I did after booting the phone. Then I wanted to enter recovery mode again and this time it showed a black screen followed by the message "no command" and a dead android animation. If I hold the power button for a few seconds it restarts in normal mode and I can use the phone, but I can't install cyanogen mod.
I tried flashing again the cynogen recovery, it worked, I could enter the menu, but again, no 'install from zip' option. If the phone boots in normal mode, the cyanogen recovery gets corrupted or something and I can't use it. I'm afraid to brick my device if I continue with something else by my own and wanted to ask you guys for help.
I'm not a total noob when it comes to phones (rooted, flashed a variety of devices in the past) but I'm not that familiar with the recent developments.
Thanks!
Nevermind,
installed TWRP and made sure that:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
My solution
First go to this link to restore to stock using this easy install script by @reefuge (find your device and country)(THIS WILL WIPE YOUR INTERNAL STORAGE!!)
http://http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
While restoring stock do not lock your bootloader.
Now got to this link for twrp : http://dl.twrp.me/titan/ Download 2.8.6.0
Now you put the twrp file in the platform tool in your android sdk. and install as usual.
Now disconnect from comp and press volume down button to selet recovery and then press vol up to enter into recovery. TWRP will patch your system to restrain it from reverting to stock recovery. Now youre done flash whatever you want.
One more thing : Try this battery guide By @Abhishek Bhagwat (works really well and its noob friendly) http://http://forum.xda-developers.com/moto-g-2014/general/guide-battery-guide-cm-based-stock-t3153365
I'm sure 90% that this will solve your problem. But if it doesnt well we'll see about that if it doesnt.
---------- Post added at 03:34 PM ---------- Previous post was at 03:32 PM ----------
*facepalm* You replied that you fixed the issue while i was typing my solution (We'll ill never see thise 15 min ever again)
Hoping I can get some help with the same issue.
I sent my 6P back in for a warranty repaid so I'm using this phone (XT1095) for now. I'd like to put LineageOS on it and root with Magisk BUT I'm having a ridiculous time getting TWRP to flash.
I certainly know how to flash images via fastboot and have done it for years but this is seriously pissing me off lol.
I got the code from Moto and unlocked the bootloader. I tried a simple "fastboot flash recovery _____.img", I've tried "fastboot boot _____.img".
At first, I was booting back into the system first but now I've tried it both ways. Regardless of what I do, after flashing the recovery, it boots into the system. The ONLY I can get this thing into recovery is if I boot into the system and just use "adb reboot recovery" but it's obviously the stock recovery because the phone keeps overwriting TWRP upon boot.
Just so we're clear:
1. Reboot into bootloader
2. Confirm bootloader unlocked
3. Fastboot flash recovery _____.img
4. Volume button to boot into recovery
Result = Boots into system
1. Reboot into bootloader
2. Confirm bootloader unlocked
3. Fastboot flash recovery _____.img
4. Fastboot reboot bootloader
5. Bootloader reboots
6. Volume button to boot into recovery
Result = Boots into system
1. Fastboot boot _____.img
Result = Boots into system
If it helps at all, upon flashing recovery I get this message 100% of the time "mismatched partition size", similar to the case on this thread: https://goo.gl/6Nm9cu
By dumb luck I found where someone used the "fastboot boot ____.img" with a pretty old version and it worked just fine. I'll root and such with that and upgrade the recovery later.
jonzey231 said:
Just so we're clear:
1. Reboot into bootloader
2. Confirm bootloader unlocked
3. Fastboot flash recovery _____.img
4. Volume button to boot into recovery
Result = Boots into system
Click to expand...
Click to collapse
For clarification of step 4. I think recovery is the second or third option in bootloader. You are hitting volume down twice and then volume up correct
Volume up selects.
The mismatched partition size doesn't matter everyone gets that error.
Visi0nofExcellence2 said:
For clarification of step 4. I think recovery is the second or third option in bootloader. You are hitting volume down twice and then volume up correct
Volume up selects.
The mismatched partition size doesn't matter everyone gets that error.
Click to expand...
Click to collapse
You know what, I am so used to newer devices like N6 and 6P that I completely overlooked that the Volume Up button was the selector instead of the power button. It was rebooting into the system EVERY TIME because I was hitting the power button. Recovery installed successfully and running LineageOS with Magisk with Android Pay and Direct TV Now working just fine.
Thanks for your help and I'll be sure to actually READ from now on :laugh::laugh: