Boot loop after Android O DP2 update - Nexus 6P Q&A, Help & Troubleshooting

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

Related

Wiley Fox Swift2+ Bootloader Unlock

It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable
I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.
SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553
Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .
I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse
bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.
After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818

How to uninstall CWM from Huawei P8, B200, rolled back from MM

I don't have an unlocked bootloader and i flashed the CWM. Now when i try to enter the recovery mode with buttons, nothing happens just turns the phone on normally. I searched for stock recoveries, but didn't found nothing.
I have GRA-L09, B200, Europe Open
Thanks for help!
To get an unlocked bootloader you must go to settings> about phone> build number
and then press build number 7 times
after you did that exit out of about phone then click on the newly-appeared 'developer settings'
there you should find OEM Unlocking and Enable USB Debugging
You'll get it from there.
I have the Dev Ops, but don't have OEM unlock.
But shouldn't you already have an unlocked bootloader to have DevOps?
Don't know. I don't typed any code in to unlock bootloader.
Are you sure you have DevOps?
---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------
And also try to do it not with buttons, but with your computer
I don't know the script for how to boot into recovery mode but to fastboot, for example, you'd type in >fastboot
when your phone is connected to your PC via USB.
Y'know, just search up 'How to use Recovery Mode' - maybe you just did it wrong
Didn't tryed it w/ adb yet.
ADB didn't worked. I'm trying a full hard reset..
Hard reset didn't do nothing. HELP PLS!!
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
TheGolem said:
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
Click to expand...
Click to collapse
That means you have a locked bootloader, so CWM didn't install successfully.
In other words, you need to unlock the bootloader first in order to successfully install CWM.
So, 1st step - visit the Huawei unlocking code request page, taking your time to fill in the form accurately & submit it.
[Btw, if you don't already have a Huawei ID, you can register for one here: http://www-file.huawei.com/en/my-huawei/register
Then use these login details in the above link to request for the unlock code]
2nd step: Once you receive the unlock code from them, use it to unlock the bootloader by issuing the following command in fastboot mode [the asterisks (*) represent your 16-digit unlock code]:
Code:
fastboot oem unlock ****************
Now you can attempt to install CWM. Where are you getting the CWM img file from?
GaT7 said:
That means you have a locked bootloader, so CWM didn't install successfully.
In other words, you need to unlock the bootloader first in order to successfully install CWM.
So, 1st step - visit the Huawei unlocking code request page, taking your time to fill in the form accurately & submit it.
[Btw, if you don't already have a Huawei ID, you can register for one here: http://www-file.huawei.com/en/my-huawei/register
Then use these login details in the above link to request for the unlock code]
2nd step: Once you receive the unlock code from them, use it to unlock the bootloader by issuing the following command in fastboot mode [the asterisks (*) represent your 16-digit unlock code]:
Code:
fastboot oem unlock ****************
Now you can attempt to install CWM. Where are you getting the CWM img file from?
Click to expand...
Click to collapse
Sorry, "Phone Unlocked" with red
TheGolem said:
Sorry, "Phone Unlocked" with red
Click to expand...
Click to collapse
Ok, so it appears you may have corrupted the recovery partition.
Is the phone otherwise booting into the system & functioning normally?
Also, can you tell us what you are wanting to ultimately achieve by installing CWM?
Just to confirm the bootloader is unlocked, run this command in fastboot mode & let us know the result:
Code:
fastboot oem get-bootinfo
Ok, I just read your post in the other thread about wanting to update B200 to B370.
TheGolem said:
I have b200 but can't install it [B370]. Why?
Early flashed the CWM with flashify succesfully, but don't have unlocked bootloader. And if i try to enter recovery mode, nothing happens. Is it possible, that i cant' install it because of this?
Click to expand...
Click to collapse
As the guys already said, you do not need to install anything in order to update an official rom.
So, let's leave out CWM, bootloaders, etc for now, & help you update only from B200.
When you try using TopperBG's method to update, what happens?
What is your current FULL firmware version? It will be in this format: GRA-L09CxxxB200 - if everything else is as I've mentioned, I'm interested in the Cxxx part.
GaT7 said:
Ok, I just read your post in the other thread about wanting to update B200 to B370.
As the guys already said, you do not need to install anything in order to update an official rom.
So, let's leave out CWM, bootloaders, etc for now, & help you update only from B200.
When you try using TopperBG's method to update, what happens?
What is your current FULL firmware version? It will be in this format: GRA-L09CxxxB200 - if everything else is as I've mentioned, I'm interested in the Cxxx part.
Click to expand...
Click to collapse
Update succeed, it wroks fine. The problem is with the recovery mode.
When i'm trying the button method to enter recover, the phone just normally turns on. When still hold the buttons, black screen. It's with the abd too.
TheGolem said:
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
Click to expand...
Click to collapse
you don't have a unlocked bootloader so you can't have cwm
I said it wrong:
-Android 5 succeed
-If i try to install Android 6
https://forum.xda-developers.com/huawei-p8/how-to/emui4-0-1-p8-official-marshmallow-6-0-t3417212
or enter recovery mode, then happens the black screen.
TheGolem said:
I said it wrong:
-Android 5 succeed
-If i try to install Android 6
https://forum.xda-developers.com/huawei-p8/how-to/emui4-0-1-p8-official-marshmallow-6-0-t3417212
or enter recovery mode, then happens the black screen.
Click to expand...
Click to collapse
1. You need to install stock recovery for android 5(unlocked bootloader is required).
2. Then you can use the dload method to update.
3. You can flash TWRP after that because no-one uses CWM.
GaT7 said:
Ok, so it appears you may have corrupted the recovery partition.
Is the phone otherwise booting into the system & functioning normally?
Also, can you tell us what you are wanting to ultimately achieve by installing CWM?
Just to confirm the bootloader is unlocked, run this command in fastboot mode & let us know the result:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
Phone normally booting, no problem with current system.
I typed in the command, and its <waiting for device>.
GaT7 said:
Where are you getting the CWM img file from?
Click to expand...
Click to collapse
http://www.teamandroid.com/2015/06/07/install-huawei-p8-clockworkmod-recovery/2/
Step 5
cwm-p8-nogui.img

Axon 7 A2017G from Lineage OS go back to Stock and Lock Bootloader without Problems

1.) You must have a full ZIP from ZTE
2.) Flash back the Original Recovery from the Original ZIP e.g. B08 B10 with ADB Fastboot command ( You must ticked OEM unlock on and USB debugging on in Developer Setting ) in Lineage.
2.1) push Power and tick restart in Bootloader.
2.2) go to Minimal ADB and Fastboot and type fastboot flash recovery recovery.img.
2.3) After this push with the Volume down recovery ,tick power.
OK! You can see the ORIGINALRecovery from ZTE.
3.) You must put a SD Card in Phone with the Original Update.zip
4.) Go in recovery and tick Update from SD card. Search the Update.zip and press Power.
5.) Wait until the Flash Process is finished.
6.) Tick Factory reset with Volume up/down push Power wait.
7.) Tick format Cache with Volume up / down push Power wait.
8.) Push Power to start your Phone with the Original Stock.
9.) After this you go to Settings / Build Number and Tick that seven Times to activate Developer Options, go back to setting and tick Developer Options ,here you must tick the OEM unlocking and USB debugging.
10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
11.) in the Comand window you type" Fastboot oem lock" the Phone reboot and the bootloaer is locked. All your Data is lost in this Process!!![COLOR="Red"][/COLOR]
Voila all is done!! Original AXON 7 with Stock Rom .
I have test this with my Axon 7 Model A2017G and i have no Problem.
Sorry for my bad English.
Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?
spacemanvt said:
Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?
Click to expand...
Click to collapse
There is a global site where you can get the file. http://www.ztedevice.com/support/detail?id=C3BAC27838C4497C80C05EE008527885
Sent from my ZTE A2017G using XDA-Developers Legacy app
Hello,
I recovered my old stock recovery and when trying to apply update from sd card, it gives me this error: "Couldn´t mount /sdcard. installation aborted"
What can I do?
Edit: Solved by formatting the SD card
What is the ADB fastboot command to flash stock recovery?
JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
fastboot flash recovery "stock Recovery"
Flash the Original recovery.img from your Update.zip!!
JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.
julk13 said:
fastboot flash recovery "stock Recovery"
Click to expand...
Click to collapse
Thanks!
tester2017 said:
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.
Click to expand...
Click to collapse
Thanks for the help, I will try now
10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
Click to expand...
Click to collapse
You made a mistake there as you have to enter "adb reboot bootloader" instead of fastboot. Other than that, it works perfectly. Thank you.
I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.
idigg said:
I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.
Click to expand...
Click to collapse
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either
spearman792 said:
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either
Click to expand...
Click to collapse
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.
robertaramar said:
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.
Click to expand...
Click to collapse
You couldn't boot into bootloader because there was no bootloader mode. As soon as you update to a recent Nougat build (or an upcoming one) via official zips, your aboot.img will be changed and you won't have bootloader mode anymore. Axon7toolkit relies on fastboot, so it flashes a package through MiFlash that gets you fastboot support.
Jus sayin
Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?
robertaramar said:
Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?
Click to expand...
Click to collapse
You can use the A2017U_FASTBOOT_UNLOCK_EDL from 4pda guys with MiFlash. Doesn't matter if you have a G, use this one
Actually axon7toolkit seems to flash that every time it does something related to fastboot. And after you lock it, you can install an official update zip (the latest one for example) and you'll get your phone totally stock, bootloader mode will be blocked.

----- Root Moto M S356 Android 7 -------

Hi guys,
I have started this thread so that you guys can root your moto M XT_1663_S356 andriod (7.0)
First of all i'm not responsible if your phone bricks burns or dies.
A big thanks to VVizard from lenovo RU forum with out him, it was not possible.
Thanks to Chainfire for the SuperSu.zip
To check Build number go to Settings -> About Phone-> Build number
Note -
1 - This only works for Moto M which is having build number XT1663_S356_170621_ROW. If you are on any other build number then please don't proceed.
2 - All the files are attached
3 - Install all the Motoral drivers and Minimal and adb folder.
4 - Following link contains all files needed to root the phone.
https://drive.google.com/file/d/0B3eDb0dWRU-uUjk4ZS1tdFpRR1U/view?usp=sharing
Rooting Moto M phone is divided into 3 Parts
1) Unlocking BootLoader
2) Flashing TWRP
3) Flashing SuperSu.zip
unlocking the bootloader
Note - This will wipe out all the data hence take a backup before unlocking boot loader
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot oem unlock
12 - Check your phone you would have written"do you really want to unloock bootloader ? "(something like this). Just select yes using volume up and down button and press power button to confirm it .
13 - Congrats your bootloader is unlocked
Install TWRP
Note - You should have your bootloader unlocked before proceeding.
Copy the boot_XT1663_356.img and TWRP_Moto_M.img to Minimal adb folder
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot flash boot boot_XT1663_356.img
12 - To flash the recovery, Type the command
fastboot flash recovery TWRP_Moto_M.img
13 - Congrats! you have successfully installed TWRP.
Rooting Phone.
Note -
You should have your bootloader unlocked.
You should have TWRP installed.
You should have supersu.zip copied in your phone.
1 - Switch off your phone. Now press volume down + power button till phone vibrates. Once it vibrates release the power button you should see android logo.
2 - Now with the help of volume up and down button select 'Recovery mode' and press power button.
3 - TWRP should start up.
4 - Select 'Allow Modification' and proceed.
5 - Select 'Install' and then select the 'SuperSu.zip' file and flash it.
6 -Restart the Phone.
7 - Congrats! your phone is rooted.
Note -
I have tried all this steps and have successfully rooted my phone i'm not responsible for any damage.
I have not build the boot_M_S365/ img file this is done by VVizard and really very thank full to him.
I am making a video on this!
Method Issues
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?
manandua01 said:
Thanks bro, I will give you credits ^_^
Click to expand...
Click to collapse
Cool!
manandua01 said:
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?
Click to expand...
Click to collapse
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.
TWRP Recovery
akash.mahadeshwar said:
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.
Click to expand...
Click to collapse
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?
manandua01 said:
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?
Click to expand...
Click to collapse
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)
manandua01 said:
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)
Click to expand...
Click to collapse
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
EDIT: Here's what was on my cmd after flashing the recovery http://prntscr.com/ft3t1l
manandua01 said:
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
Click to expand...
Click to collapse
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6
manandua01 said:
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6
Click to expand...
Click to collapse
Ext_sdcard folder is ur memory card folder and sdcard folder is the internal memory folder in twrp
BAM!
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------
I really thank you for this great effort
all things went good but I had a problem that I didn't find the SuperSU-v2.82-201705271822.zip although I am sure that I put it in the internal memory
please help
Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware
pdf5 said:
Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware
Click to expand...
Click to collapse
May I have the firmware file, just in case? Is it ok if firmware country code doesn't match? Do you get imei?
any idea? when image for new build will be released?
rajesh280392 said:
any idea? when image for new build will be released?
Click to expand...
Click to collapse
Well, yes ... The new boot.img for removing encryption. Especially for post-OTA updating to XT1663_S364_170803_ROW.
boot_XT1663_364.img
Does anyone know how to keep your Moto M rooted even after updating to the new security update of 7.0? Do we just flash the new .img file or what? Kinda newb here

Downgrade Orea beta to Nougat

Orea beta is great but battery drain so much.
for 30 min of screen use it used 11%, is it normal ?
and I am looking to go back to Nougat, could any one please tell me how can I go back.
Thank you.
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Yup those are them, I just did it yesterday.
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
vjyrdy said:
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Click to expand...
Click to collapse
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
swagglepuff said:
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
Click to expand...
Click to collapse
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
tech_head said:
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
Click to expand...
Click to collapse
I have ran both unlock commands successfully and still get permission denied
swagglepuff said:
I have ran both unlock commands successfully and still get permission denied
Click to expand...
Click to collapse
And you checked the OEM unlock in developer options?
Hmmmm
tech_head said:
And you checked the OEM unlock in developer options?
Hmmmm
Click to expand...
Click to collapse
The issue has something to do with Mac and the platform tools. I was able to downgrade with no problem using a friend's Windows PC.
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
trizon2016 said:
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
Click to expand...
Click to collapse
Nothing confusing about that statement for Windows, MacOS or Linux.
A command path needs to exist so that when you type the command it can be found.

Categories

Resources