Database Users

Stuck In BootLoop While updating lollipop

i used nexus root tool kit to update nexus 4 from 4.4 to 5.0... all done in pc but mobile is stuck in boot loop. can anyone tell me how can i restore my phone to normal working...
Please help me i am noob here

is there any one who can help me here
i thought i will get ans with in 1hr... still waiting if someone can help

letsnexus said:
i thought i will get ans with in 1hr... still waiting if someone can help
Click to expand...
Click to collapse
This is why we don't recommended using tool kits. You should try flashing the factory image using fastboot.
Sent from my Nexus 9 using XDA Free mobile app

Same here, i tried re-flashing many times. Darn that nexus root toolkit

any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help

I am currently in the same position ! Used a toolkit too, always have.

This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follows.
1. Download factory image
2. Download ADB files
3. Make a folder and extract the adb files and factory image inside the same folder.
4. Plug the phone in bootloader mode or simply type adb reboot bootloader (Developer options must be enabled and USB Debugging) by exiting the folder, holding shift, right clicking the folder and pressing open command window and typing the command.
5. Every factory image comes with a flashall.bat, double click it and voila. Updates like it should. (User data will be wiped)
If you don't want your userdata to be wiped, simply open flashall.bat with notepad++, erase the '-w' in "fastboot -w update image" and save the file and launch it again.
Sent from my HTC One_M8 using Tapatalk

I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend

hazwheel said:
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
Click to expand...
Click to collapse
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>

letsnexus said:
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
Click to expand...
Click to collapse
although the link is for kitkat but the same method applies to flashing lollipop
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

moorthidaniel said:
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
Click to expand...
Click to collapse
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !

For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.

hazwheel said:
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
Click to expand...
Click to collapse
OK great. Cheers, I helped someone today in this forum.

bett3rthan said:
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
Click to expand...
Click to collapse
That did NOT work for me, the getting into recovery and wiping the device DID work though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
moorthidaniel said:
OK great. Cheers, I helped someone today in this forum.
Click to expand...
Click to collapse
Yes, Thanks, unfortunately, she has withdrawn the offer of an early upgrade :silly:

thax
Misledz said:
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you alot, you help in really good manner
and teached us not to use toolkit
will learn more abt rooting and flashing thank you once again

I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.

Tried going to boot-menu and did factory reset and it booted good after ~10 mins.

sububack said:
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Click to expand...
Click to collapse
Power off, hold Vol Down + Power, when you get to the Android laying down, press volume up + pwr, then wipe the /cache from the menu (you do not need to do a full factory wipe, just wiping cache will do), and then reboot and wait. It will boot this time properly. @WugFresh is aware of the issue and said will put a fix in 1.9.9 for the N4

Thanks , I have tried clearing the cache and started waiting for an hour. Since it was still looping tried after factory reset/wiping user data. And then after 10min it came good.

I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/fo...ce=footer#!msg/nexus/Lv8fHtyJOPQ/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 + HelpMyNexus

[HOW TO] How to Root 5.1 with (unlocked bootloader)

I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link) UPDATE: There is an issue with TWRP 2.8.7.0 (SEE THIS POST Thanks @jodaboda ). Please use TWRP 2.8.6.0 for now!
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
EDIT: 9-17-2015 edited first TWRP link.

KidJoe said:
I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link)
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
Click to expand...
Click to collapse
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?

Do you know where I can find mfastboot for Mac OSX?

kidjoe, your a priceless resource!
i installed an older verison of twrp and had all the issues you speak off, installed 2.8.6 with success but would not root upon reboot, installed the super su zip in op via twrp, one last thing i had to enter the super su app and tap enable superuser and now all is good:good::good

Thanks, worked like a charm

Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.

Vampirexox said:
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Click to expand...
Click to collapse
twrp-2.8.6.0-ghost.img works on Lollipop too. (just used it last night on my sister-in-law's GSM Dev Edition XT1053 that got the lollipop update)

jay_em said:
Do you know where I can find mfastboot for Mac OSX?
Click to expand...
Click to collapse
Here is a copy on my Box 'drive':
https://app.box.com/s/5nlgy2avccupw4box8z2be50ezt4qn7p
EDIT: I just got an e-mail saying it had been downloaded. :good:
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
kyzn said:
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Click to expand...
Click to collapse
EDIT: [If you are still running the stock Recovery] You can also use:
Code:
adb reboot recovery
When you see the horizontal robot hold the Volume Up key for 3 seconds and then tap Power and the Recovery Menu will display.

Thanx for this how-to. Everyone has been getting confused in root process for 5.1 although it is nearly same as 4.4.4.
Sent from my XT1052

I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!

jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
I had the same issue with my XT1053. Following your advice did the trick. Not being able to modify my dpi since upgrading has been killing me. Its the only thing i really want root for. Thanks for everything both you and op!

jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
Ahh... 2.8.7 wasn't out when I tried.. 2.8.6 was the latest at that time. Maybe there is a bug in 2.8.7 that will get fixed in future versions?

Sunshine unlocked bootloader
Does anyone know if there are any issues resulting from a Sunshine unlocked bootloader? I saw one post that had a warning but it was a warning because there was no information at the time. Has this change?

i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader

md07 said:
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
Click to expand...
Click to collapse
When you say "installed TWRP successful"... do you mean that fastboot didn't error? or that fastboot completed the install, you did a mfastboot reboot-bootloader, and tried entering TWRP but it still gave you the "dead android" image?

Is there any unofficial way to unlock bootloader?
Sent from my Nexus 7 using Tapatalk

I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!

djibril13 said:
Is there any unofficial way to unlock bootloader?
Click to expand...
Click to collapse
Sunshine... IF you're phone has never been upgraded to 4.4.4.
BUT if you can get unlock code from Moto, while it can void your warranty (depending on your local laws), that is FREE, and the best way.

SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
help me understand your situation...
You are doing.. Mfastboot flash recovery -> mfastboot reboot-bootloader -> you get battery charging screen rather than fasboot/bootloader menu/screen?
or ??

SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
after flashing did you but to recovery befour booting system? with my experience i had to boot to recovery first befour system

[GUIDE] Unlocking, Rooting, and Restoring to Stock for Le 2 / S3 (noob-friendly!)

I don't have anything against toolkits, I just prefer to use adb and fastboot so I have more control over of what's going on. I also think it's a good idea for folks to have a little idea about what they're doing, even if they aren't experts. Below are the steps I used to install TWRP (recovery) and SuperSU (root) for my X522 (aka S3, the US variant which uses the Snapdragon 652). I don't see any reason this wouldn't work for all other Snapdragon variants: X520 (Chinese), X526 (Indian), and X527 (International). That said, you do what you do at your own risk. If you have one of the other Snapdragon variants and this works for you, though, please respond to the thread and let me know!
This thread is intended to be noob-friendly! That means that there are no dumb questions...unless you ask a question that is directly answered in the first post or in the FAQs found in the second post. To that extent, please read and re-read and if you still can't find your answer, please feel free to post your question.
Many thanks to @Rishabh Rao and his team for getting us an official TWRP image.
WARNING: this will reset your phone entirely! Make sure you save anything you want from internal storage before proceeding any further!
WARNING: as of right now, unlocking / rooting your phone will break your ability to take official OTAs. We're not sure why. That said, you should be able to flash modified OTA zip files manually, after a certain block of the update script is removed (see second post for more information).
Unlocking and Rooting your Le 2
Download and install Minimal ADB and Fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download latest official TWRP, place file in ADB installation folder, and rename to "twrp.img": https://twrp.me/devices/leecole2.html
Download SuperSU 2.78 (stable): https://download.chainfire.eu/1001/
Boot up phone and plug into computer
Settings > scroll to bottom to "About phone" > touch "Build" 7 times to enable developer options
Developer options > toggle "OEM unlocking" and "USB debugging" so that they're both enabled
When "Allow USB debugging?" window pops up on phone, check "Always allow..." box and hit OK
In Minimal ADB installation folder, hold Shift and right-click "Open command window here", then type:
Code:
adb reboot bootloader
Once in fastboot:
Code:
fastboot oem unlock-go
fastboot boot twrp.img
If password screen comes up, tap "Cancel" button
If it asks, tap "Keep Read Only" button (probably doesn't matter, but whatever)
Wipe > Format Data
Make backups (I suggest boot, recovery, and system since this will allow you to return everything to stock later on)
Mount > Enable MTP
Copy entire TWRP folder from internal storage to your computer
Copy SuperSU zip from your computer to root of internal storage
Reboot > Bootloader
Code:
fastboot oem unlock-go
fastboot flash recovery twrp.img
Hold Vol+ and Pwr until boots into TWRP
Swipe to Allow Modifications
Install > select SuperSU zip > swipe to flash
Wipe Cache/Dalvik
Reboot (first boot will take a little while, so be patient)
Enjoy your rooted phone!
Restoring to Stock(ish)
Follow steps 4-7 above
If your boot and recovery backups from TWRP aren't already on your phone, move them to the appropriate folder (internal storage/TWRP/BACKUPS/[yourphoneserialnumber])
In Minimal ADB installation folder, hold Shift and right-click "Open command window here", then type:
Code:
adb reboot recovery
Wipe > check Dalvik, Cache, Data
Restore > select your package, ensure boot and recovery are checked, then Swipe to Restore
Reboot > Recovery
In stock recovery: uncheck "Update system", check "Clear data", and tap "Start"
Reboot to bootloader (hold Vol- and Pwr until it comes up) and then:
Code:
fastboot oem unlock-go
fastboot boot twrp.img
Wipe > Format Data
Reboot > System
Your phone is now back to stock!
If you didn't back up your stock recovery, boot, or system, you can find the ones I pulled from my phone at the link below. They're from 19S. I don't know if that makes a difference (vs 18S) with boot and recovery or not, but obviously that's what you're getting with the system.
https://mega.nz/#F!bV0XUbhJ!k2ZfY5t9bxb8gRa3rKQbyA

FAQs
Fastboot and/or ADB doesn't see my phone!
If you've enabled OEM unlocking and USB debugging and fastboot devices returns <waiting for device> or adb devices doesn't show anything, the most likely culprit is that Windows is using updated ADB drivers and you need to roll back. You can do this via Device Manager > right-click Android Device (or Kedacom USB device) / Android Bootloader Interface > Update driver > Browse my computer for driver software > Let me pick... > Choose older version (probably something from 2014)
I haven't seen the "Allow USB debugging?" prompt. Where is it?
In some cases, you will need to run an ADB command first to make the prompt show up. If you toggled the appropriate developer options and didn't get the popup immediately, make sure your phone is plugged into your computer and type adb devices in the command prompt. You should get the popup box then.
Stock recovery is in Chinese and I can't read Chinese!
As I was testing the above procedures, this happened to me once or twice and I don't know why. Upon a full restore and boot back into recovery, it was in English again. It might have something to do with the data wipe in TWRP. Anyway, the options in stock recovery are the same in Chinese and English so do this:
Uncheck the first item and check the second
It will direct you to a screen with some red text and a blue button: tap the button
It will return you to the first page: ensure the second item is checked and tap the blue button
Uh, how do I re-lock the bootloader? Am I missing something?
As far as I can tell - and someone please correct me if I'm wrong - using this guide, your bootloader is only ever temporarily unlocked and will re-lock with a reboot. That's why you have to use fastboot oem unlock-go more than once. You can verify this by restarting the phone, rebooting into the bootloader, and using the code below to check the status:
Code:
fastboot oem device-info
If for some reason your phone shows that you still have an unlocked bootloader, you can re-lock it using:
Code:
fastboot oem lock-go
I'm stuck in a stock recovery bootloop. How do I get out of it?
This probably happened because you're just holding down the power button to reboot instead of using the "restart" button in stock recovery. If you use the "restart" button to in stock recovery, it should kick you out of the loop.

Thanks for this guide , can we expect some roms from your side.
Just curious to know if any developer is working for rom on le2

Great guide for beginners but can you tell that how can one lock the bootloader again and when we make a backup does it make the back up of TWRP recovery of stock recovery?

Great!! Informative thread for beginners!

Miketoulson said:
Just curious to know if any developer is working for rom on le2
Click to expand...
Click to collapse
Yes. @Rishabh Rao and his team (the same ones who did TWRP and the AIO toolkit) are working on CM. As a reminder, please do not ask for ETAs. They will post the ROM when it's available.
Swastik Raj Chauhan said:
Great guide for beginners but can you tell that how can one lock the bootloader again and when we make a backup does it make the back up of TWRP recovery of stock recovery?
Click to expand...
Click to collapse
1.) Regarding the bootloader: good question. I've updated the FAQ.
2.) Regarding recovery backup: that's why we only boot into TWRP the first time, rather than replacing recovery from the beginning. That way, stock boot and recovery are backed up. Later on, when we flash TWRP, stock recovery is replaced.

I'm having trouble with this guide. I have TWRP recover flashed, but it isn't working correctly. It says there is nothing in my sdcard directory and my computer won't connect to the phone in recovery. I've also tried "adb push ... /sdcard/" method. The SuperSU files gets put in the sdcard directory and I can flash it, but it says "unable to mount storage" and the file is gone after a reboot. Is this because it's encrypted and I'm just hitting cancel when it asks for a password?

abel408 said:
I'm having trouble with this guide. I have TWRP recover flashed, but it isn't working correctly. It says there is nothing in my sdcard directory and my computer won't connect to the phone in recovery. Is this because it's encrypted and I'm just hitting cancel when it asks for a password?
Click to expand...
Click to collapse
Sounds like you missed steps 12 and 14.

rczrider said:
Sounds like you missed steps 12 and 14.
Click to expand...
Click to collapse
Nope... I formatted data and enabled MTD. When I enable MTD, my computer tells my the phone is locked...
---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------
My bootloader keeps locking itself...
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
I can unlock it, but it locks itself after a reboot.

abel408 said:
Nope... I formatted data and enabled MTD. When I enable MTD, my computer tells my the phone is locked...
---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------
My bootloader keeps locking itself...
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
I can unlock it, but it locks itself after a reboot.
Click to expand...
Click to collapse
That's expected and is addressed in the FAQ
You're only ever temporarily unlocking it. You will need to unlock it every time you reboot the phone.

rczrider said:
That's expected and is addressed in the FAQ
You're only ever temporarily unlocking it. You will need to unlock it every time you reboot the phone.
Click to expand...
Click to collapse
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
---------- Post added at 07:45 PM ---------- Previous post was at 07:27 PM ----------
And now I'm stuck... I cannot go back to stock because TWRP doesn't mount the storage.
---------- Post added at 08:01 PM ---------- Previous post was at 07:45 PM ----------
abel408 said:
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
---------- Post added at 07:45 PM ---------- Previous post was at 07:27 PM ----------
And now I'm stuck... I cannot go back to stock because TWRP doesn't mount the storage.
Click to expand...
Click to collapse
I was able to fix this by wiping Internal Storage... You may need to add that to your guide. Thanks for the guide!

abel408 said:
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
Click to expand...
Click to collapse
I can't get permanent root using the AIO Toolkit, but maybe it's just the 2 phones I've tried. I'd love to hear from other users (X522 or other variants) on whether or not their unlock actually sticks after a reboot.
abel408 said:
I was able to fix this by wiping Internal Storage... You may need to add that to your guide. Thanks for the guide!
Click to expand...
Click to collapse
If other folks run into the same issue, I'll add it. I followed my own steps on a second phone (one that had never been unlocked/rooted before and was currently set up and in use) after your post and I didn't have any need to do anything different. I'm wondering if that need arose because you didn't unlock the bootloader a second time before booting into TWRP. If that's the case, the guide works as written, so I'll add it to the FAQ.

I seem to have done something wrong. I'm having a really difficult time accessing the Data partition in TWRP. Every time I reboot into recovery I cannot access the files on the sdcard (it is simply empty). I reboot and the files are still in storage (along with the TWRP backups I made) - I just can't seem to get to them in TWRP. I cannot mount Data because it doesn't appear. There is a box to decrypt data but that then requires a password (which I obviously don't know). Don't want to go any further if I can't seem to have a dependable way to access backups. Any suggestions?
Edit: Enable MTP also doesn't work for me in TWRP so there is no way to bring any files over from my PC while in TWRP - also adb push/pull doesn't seem to be working

skyman88882002 said:
I seem to have done something wrong. I'm having a really difficult time accessing the Data partition in TWRP. Every time I reboot into recovery I cannot access the files on the sdcard (it is simply empty). I reboot and the files are still in storage (along with the TWRP backups I made) - I just can't seem to get to them in TWRP. I cannot mount Data because it doesn't appear. There is a box to decrypt data but that then requires a password (which I obviously don't know). Don't want to go any further if I can't seem to have a dependable way to access backups. Any suggestions?
Edit: Enable MTP also doesn't work for me in TWRP so there is no way to bring any files over from my PC while in TWRP - also adb push/pull doesn't seem to be working
Click to expand...
Click to collapse
If TWRP is asking for a password, that means you missed step 12.

I'm trying to upgrade from 18s to 19s and I'm getting upgrade failed every time. I've tried restoring to factory defaults and restoring my TWRP backup. Seems to be fully on stock now and it still fails. My question is, do you think it would be alright if I restored your 19s TWRP backup so that I am on 19s?

abel408 said:
I'm trying to upgrade from 18s to 19s and I'm getting upgrade failed every time. I've tried restoring to factory defaults and restoring my TWRP backup. Seems to be fully on stock now and it still fails. My question is, do you think it would be alright if I restored your 19s TWRP backup so that I am on 19s?
Click to expand...
Click to collapse
Tell you what: give me an hour or two. I'm currently on non-stock (ie. rooted) 18S and since the Xposed module EUI Moder (http://forum.xda-developers.com/xposed/modules/mod-leeco-eui-moder-t3416932) doesn't work (lockscreen flicker / system UI crash), I don't mind wiping the phone and testing the ability to go back to stock and do an OTA update to 19S. If it doesn't work for me, I'll restore 19S (from my other S3) via TWRP and see if that does it.

@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.

rczrider said:
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
Click to expand...
Click to collapse
Thanks buddy!

Thank you sir, this worked (almost) perfectly. For some reason on my laptop, I wasn't able to get the phone to connect with debugging (never got the prompt for permission, etc.). No clue why not, I've got drivers and everything, and that laptop works with many other phones. Oh well. Went to a different PC and it worked perfectly.

rczrider said:
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
Click to expand...
Click to collapse
I think I'm doing something wrong @rczrider, but I can't get TWRP to even recognize the backup you uploaded. Do I just drag the extracted files to the TWRP folder?

Bootloader unlock and custom recovery

Hello guys. Before you proceed, I'll let you know that I don't own this device. Theoretically these steps should work.
1. Unlock bootloader
Go to settings>about, tap build number 7 times. This enables developer options. Here, select allow OEM unlock and USB debugging. Reboot in fastboot mode (power+vol down). Then go to this site
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
And follow the instructions. They are pretty straightforward.
2. Install TWRP
Go to
http://lenovo-forums.ru/topic/22535-moto-m-kastomnoe-rekaveri-twrp-otklyuchenie-shifrovaniya/
And download TWRP_Moto_M.img and boot_M_S124.img
In fastboot mode type fastboot flash boot <the name of the latter file image, just drag it into the CMD window from adb and fastboot folder> then type fastboot flash recovery <TWRP file>
Then type fastboot boot <TWRP file> and voila, you are booted in custom recovery.
IMPORTANT: FOR ALL THAT IS GOOD AND FAIR, MAKE A BACKUP OF EVERY FOLDER. IF YOU MESS UP SOMEWHERE, I WON'T BE ABLE TO HELP YOU!!
Now you may proceed to rooting procedures.
Tell me if this works. And before asking any questions in this thread, use the DAMN INTERNET; Google or Bing or Yahoo, whatever floats your boat

Reserved

If you are unsure of any step, and Google does not help, ask it in this thread and wait for my reply

Hi can u pls tell how to do this in XT 1663... Tried to enter bootloader mode but no luck

nanchilanto said:
Hi can u pls tell how to do this in XT 1663... Tried to enter bootloader mode but no luck
Click to expand...
Click to collapse
Search in google `lenovo forum 772 moto m`

jcanilkumarjc said:
Search in google `lenovo forum 772 moto m`
Click to expand...
Click to collapse
I tried tat but it boots normally only , OEM unlocking is switched on too , USB debugging is also turned on. Will give a shot connecting thrh PC . Anyways tnx for the response

Can we enable Mediatek Clear Motion feature in Moto M XT1663 ? Please kindly help me
Thanks!

If someone has been able to root the device successfully, do share with me the system and boot backup made in twrp. I will try bringing up a ROM.

For unlocking just enable it in developers and then
fastboot oem unlock

Guys, I'm I did a ****ty thing and my M got locked up. I did 'fastboot oem lock'. It said press volume up to lock/ volume down to cancel, pressed volume up. It said lock success. I can't even open recovery mode/ fastboot mode to flash something. Please help!
It keeps on rebooting after the 'Lenovo' logo.

sreenivas134 said:
Guys, I did a ****ty thing and my M got locked up. I did 'fastboot oem lock'. It said press volume up to lock/ volume down to cancel, pressed volume up. It said lock success. I can't even open recovery mode/ fastboot mode to flash something. Please help!
It keeps on rebooting after the 'Lenovo' logo.
Click to expand...
Click to collapse
I've flashed the stock ROM using sp flash tool. It has resolved the issue. Thanks...
---------- Post added at 11:04 AM ---------- Previous post was at 11:03 AM ----------
sreenivas134 said:
Guys, I did a ****ty thing and my M got locked up. I did 'fastboot oem lock'. It said press volume up to lock/ volume down to cancel, pressed volume up. It said lock success. I can't even open recovery mode/ fastboot mode to flash something. Please help!
It keeps on rebooting after the 'Lenovo' logo.
Click to expand...
Click to collapse
I've flashed stock ROM using sp flash tool. It has resolved the issue. Thanks...

sreenivas134 said:
I've flashed the stock ROM using sp flash tool. It has resolved the issue. Thanks...
---------- Post added at 11:04 AM ---------- Previous post was at 11:03 AM ----------
I've flashed stock ROM using sp flash tool. It has resolved the issue. Thanks...
Click to expand...
Click to collapse
Can you pls gimme the download link and the steps to flash the stock firmware ? I updated to nougat and flashed the wrong version of boot.IMG and the phone stays at your phone will reboot in 5 seconds

nanchilanto said:
Can you pls gimme the download link and the steps to flash the stock firmware ? I updated to nougat and flashed the wrong version of boot.IMG and the phone stays at your phone will reboot in 5 seconds
Click to expand...
Click to collapse
You can find the stock firmware here!
https://mega.nz/#!fcoS2SII!ipO0YBudxaTnF7XVdqjEMwByJmn95p-K4A2mHrY-DvE

sreenivas134 said:
You can find the stock firmware here!
https://mega.nz/#!fcoS2SII!ipO0YBudxaTnF7XVdqjEMwByJmn95p-K4A2mHrY-DvE
Click to expand...
Click to collapse
Password ?????????????????????

Moto M - Unlock bootloader
mrinmaydhar said:
Hello guys. Before you proceed, I'll let you know that I don't own this device. Theoretically these steps should work.
1. Unlock bootloader
Go to settings>about, tap build number 7 times. This enables developer options. Here, select allow OEM unlock and USB debugging. Reboot in fastboot mode (power+vol down). Then go to this site
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
And follow the instructions. They are pretty straightforward
Click to expand...
Click to collapse
The wrong way to go.
Follow these steps:
In Windows command prompt write adb reboot bootloader. The device will reboot into fastboot.
The following command - fastboot oem unlock. You will be prompted on the phone screen, volume up to confirm, down to refuse. Who decided to change his mind
I waited a few seconds and at the command prompt, I got the answer - OK.
Disconnect the cable from the phone and hold the power button reboot the phone and put aside. He will restart another 2 times, will go to the drain recovery and erase all data from your phone. Therefore, I recommend to make a backup.
You just have to wait to boot the phone. approximately 5-7 minutes.
The bootloader is unlocked.

BOPOH'Ok said:
The wrong way to go.
Click to expand...
Click to collapse
So what's wrong with what I posted? Just wanted to know, so that I can update the OP.

mrinmaydhar said:
So what's wrong with what I posted? Just wanted to know, so that I can update the OP.
Click to expand...
Click to collapse
That's just the point, that you give the wrong information.
You give a link to the unlocking of MOTO devices on the Qualcomm processor, and that method is not suitable for MTK.
I also laid out 100% working instructions.

problem
bro i am unlocking the bootloader it boots to bootloader then it asks for yes to unlocking the bootloader in phone it says volume up to yes or volume down to NO i press volume but it automatically cancelled what to do man

Boot loop after Android O DP2 update

I installed Android O DP2 update via OTA yesterday. The phone updated, rebooted to the new build and restarted abruptly and since then has been stuck in a boot loop. The Google logo shows up, goes to the android animation step and then Google logo appears again.
I don't have bootloader unlocked, don't have TWRP and have done OTA updates. I am able to get into the stock recovery mode.
How do I fix this, i.e. make it work in any way without erasing the user data? I don't mind extreme steps (without erasing user data) because I was planning to reflash 7 with unlocking & rooting today.

Try to wipe cache from recovery - in recovery hold volume-down and select "Wipe cache partition". Should do the trick

I tried, didn't work. Had to factory reset in the end. Also opted out of beta

I just read that some people that took the update from certain builds had boot loops due to the update only replacing part of the OS but leaving the 7.x.x system in place causing it to boot loop. I think it was like on android authority or something like that.
Sent from my Nexus 6P using XDA-Developers Legacy app

I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks

citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
POWER BUTTON + VOLUME DOWN BUTTON
Click to expand...
Click to collapse
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.

Mavelos said:
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.

citifone said:
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
Click to expand...
Click to collapse
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.

FAILED (remote: OEM unlock is not allowed)
Mavelos said:
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
Click to expand...
Click to collapse
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?

citifone said:
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
Click to expand...
Click to collapse
To unlock you first need to have ticked the allow OEM unlock from developer menu within the OS. It won't work otherwise.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here [="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.

scorneil said:
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
Click to expand...
Click to collapse
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Lord Aguacate said:
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Click to expand...
Click to collapse
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.

i have the same problem with this, and i cannot unlock it too, is there anyway to unlock this phone?

OTG works Perfect! But.....
Mavelos said:
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
Click to expand...
Click to collapse
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards

Lord Aguacate said:
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Click to expand...
Click to collapse
You're welcome. Get your phone fixed and return to the flashing community.

last night i my phone inside my freezer hehehe and this morning i tried to turn it on, and it pass the google logo boot normally but it only lasted for a few minute and then turn off and bootloop again. so i guess my 6p has a hardware faulty