Database Users

Bricked Moto X Style (XT1572) stuck in bootloop while attempting root using TWRP

Hello
To cut a long story short I've followed the "How To ROOT Moto X Pure / Style (2015) EASIEST METHOD" YouTube video (cannot link video as I'm a new user) to root my Moto X Style.
I got as far as the end of the video to flash TWRP which appeared successful, and then flashed SuperSU. I understand SuperSU has bricked my phone because I am on 6.0 which is now incompatible. However, I can't seem to find a way to factory restore or enter recovery mode.
Here are some of the things I've tried and have observed:
- The phone shows the Moto logo indefinitely when switched on.
- I can get to the bootloader menu by pressing VolDown and Power but every single option therein such as "FACTORY MODE" and "RECOVERY MODE" results in a bootloop as above. This makes factory resets or recovery impossible via the device.
- ADB can no longer read my device no matter what mode I change the device to. All drivers are up to date. This makes remote access to the phone impossible as well. However, the device is listed in Windows Device Manager.
In the comments section of the YouTube video someone lists the following solution http://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155 but without being able to access my phone from ADB, I'm not sure how that would be possible either.
I'm hoping the device isn't permanently bricked but I can't quite see a way to access the device at the moment!
I would be very grateful if someone could point me toward a solution. Thanks.

Yes its cause you didn't flash modified boot.IMG
Download the modified boot.IMG and supersu .img from XDA just google it
I believe there a indie version I used worked fine .
You need to reboot into fastboot
Open command prompt .
Rename super su to recovery .img
And type fastboot flash boot boot.img then type fastboot flash recovery recovery.img
Sent from my XT1575 using XDA Free mobile app
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
jellyghost said:
Hello
To cut a long story short I've followed the "How To ROOT Moto X Pure / Style (2015) EASIEST METHOD" YouTube video (cannot link video as I'm a new user) to root my Moto X Style.
I got as far as the end of the video to flash TWRP which appeared successful, and then flashed SuperSU. I understand SuperSU has bricked my phone because I am on 6.0 which is now incompatible. However, I can't seem to find a way to factory restore or enter recovery mode.
Here are some of the things I've tried and have observed:
- The phone shows the Moto logo indefinitely when switched on.
- I can get to the bootloader menu by pressing VolDown and Power but every single option therein such as "FACTORY MODE" and "RECOVERY MODE" results in a bootloop as above. This makes factory resets or recovery impossible via the device.
- ADB can no longer read my device no matter what mode I change the device to. All drivers are up to date. This makes remote access to the phone impossible as well. However, the device is listed in Windows Device Manager.
In the comments section of the YouTube video someone lists the following solution http://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155 but without being able to access my phone from ADB, I'm not sure how that would be possible either.
I'm hoping the device isn't permanently bricked but I can't quite see a way to access the device at the moment!
I would be very grateful if someone could point me toward a solution. Thanks.
Click to expand...
Click to collapse
You need to just download android SDK to c drive and make folder named SDK
Then open platform tools and open command window in that folder
Your phone should be on start when your in fast boot to flash
Sent from my XT1575 using XDA Free mobile app

Thanks for your reply, but I can't actually get the device to show up in adb command prompt to be able to do this. Or can I still use CMD commands even if the device doesn't show up using "adb devices"?

Getting nexus Motorola anything fastboot is hard always the sure shot way is to follow the SDK platform tools way
Just install all that on PC and try
Did your phone prompt you to accept the RSA key the allowing trust of your pc before all this happened ?
Sent from my XT1575 using XDA Free mobile app
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
jellyghost said:
Thanks for your reply, but I can't actually get the device to show up in adb command prompt to be able to do this. Or can I still use CMD commands even if the device doesn't show up using "adb devices"?
Click to expand...
Click to collapse
If you find them files and out them in platforms tools folder inside C drive sdk
It should work you only need to flash the boot.img really
Sent from my XT1575 using XDA Free mobile app

Ahh, I see. I will do as you suggest and report back.

Okay, some success. I've used the modified boot. img and I've installed SuperSU 2.67 as well (through the phone not PC), and it all appears to be working fine. I couldn't get the recovery stuff to work though. How should I test that SuperSU is installed and working as expected?

jellyghost said:
Okay, some success. I've used the modified boot. img and I've installed SuperSU 2.67 as well (through the phone not PC), and it all appears to be working fine. I couldn't get the recovery stuff to work though. How should I test that SuperSU is installed and working as expected?
Click to expand...
Click to collapse
Download any apps that ask for root and run it. Or just download root checker app from Play Store.

I worked out that I needed to reinstall the latest TWRP. I think everything seems fine now, and I've been able to install a new ROM and apps requiring root etc. Thanks all.

jellyghost said:
Hello
To cut a long story short I've followed the "How To ROOT Moto X Pure / Style (2015) EASIEST METHOD" YouTube video (cannot link video as I'm a new user) to root my Moto X Style.
I got as far as the end of the video to flash TWRP which appeared successful, and then flashed SuperSU. I understand SuperSU has bricked my phone because I am on 6.0 which is now incompatible. However, I can't seem to find a way to factory restore or enter recovery mode.
Here are some of the things I've tried and have observed:
- The phone shows the Moto logo indefinitely when switched on.
- I can get to the bootloader menu by pressing VolDown and Power but every single option therein such as "FACTORY MODE" and "RECOVERY MODE" results in a bootloop as above. This makes factory resets or recovery impossible via the device.
- ADB can no longer read my device no matter what mode I change the device to. All drivers are up to date. This makes remote access to the phone impossible as well. However, the device is listed in Windows Device Manager.
In the comments section of the YouTube video someone lists the following solution http://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155 but without being able to access my phone from ADB, I'm not sure how that would be possible either.
I'm hoping the device isn't permanently bricked but I can't quite see a way to access the device at the moment!
I would be very grateful if someone could point me toward a solution. Thanks.
Click to expand...
Click to collapse
Sorry but what version of SuperSu Did you install ? and did you keep you system as read only ?
It seem we miss a clear how-to root XT1572 EU on MM !!

psxmail said:
Sorry but what version of SuperSu Did you install ? and did you keep you system as read only ?
It seem we miss a clear how-to root XT1572 EU on MM !!
Click to expand...
Click to collapse
For marshmallow I had to use 2.62 version of SuperSU. And flash via twrp recovery.

androidddaaron said:
Getting nexus Motorola anything fastboot is hard always the sure shot way is to follow the SDK platform tools way
Just install all that on PC and try
Did your phone prompt you to accept the RSA key the allowing trust of your pc before all this happened ?
Sent from my XT1575 using XDA Free mobile app
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
If you find them files and out them in platforms tools folder inside C drive sdk
It should work you only need to flash the boot.img really
Sent from my XT1575 using XDA Free mobile app
Click to expand...
Click to collapse
I have the same problem as the op had. However, your solution didn't work for me. I did exactly what you said. Do you have any alternative fix?

Hello, I have the same problem, my Moto X Style is dead.
I try to flash a boot.img, as well as a full firmware, but it does not work.
I throw this error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY 0.932s
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
The bootloader is locked, and no method has served me to unlock it, throw me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
Can you help me?

AlexAndroid said:
Hello, I have the same problem, my Moto X Style is dead.
I try to flash a boot.img, as well as a full firmware, but it does not work.
I throw this error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY 0.932s
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
The bootloader is locked, and no method has served me to unlock it, throw me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
Can you help me?
Click to expand...
Click to collapse
Looks like you tried it without enabling,"enable oem unlock" from developer option as it clearly says in last line bro!

May Factory Image now available MXC89F

For those in custom recovery land just flash the system and vendor img to upgrade
now in May flavor!
https://developers.google.com/android/nexus/images#instructions

Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine

redukt said:
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
Click to expand...
Click to collapse
The value of this posting would increase exponentially if you took it upon yourself to share what and how you flashed the files with ADB.

Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
No chance of losing root either, is that correct?

Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP

redukt said:
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
Click to expand...
Click to collapse
Yes, I will need to reflash both, too (I have TWRP).
Thanks!

Than you´re device is rooted again. With this method you lose no data or wipe anything (ok.... some cache *g)
And... we have a thanks button in XDA So you don´t have to thank mate

Change log ? Or its just a security update

Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.

After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...

rambobo said:
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
Click to expand...
Click to collapse
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk

houtx2 said:
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?

rambobo said:
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
Click to expand...
Click to collapse
Pleas try to reinstall right drivers, change the cable / USB ports. I think your main problem is your system configuration. Good luck

m8... so glad I wasn't too tired to listen to your tip. Awesome! Redid all the steps on my freshly installed laptop, and voila!
Seems either my main PCs USB-connection is flunky or I am damned to reinstall my Windows soon. Scary...
I used the following software to revive the Pixel:
official Google USB Drivers
You have to unzip the file and right-click and install it
then you have to go to your device manager in windows and after connecting the tablet with the PC and getting into fastboot
Find the Android device on the top, select to change driver and go straight to manual selection of the driver, select android and bootloader driver
unpack the official Factory Image with 7Zip until you get to the folder with the flash-all.bat
get the minimal adb fastboot and unpack it in the same folder as the flash-all file
wait until you see the sweet booting animation
I think I didn't forget anything important. My Pixel is alive and ready for prime time.
Big thanks redukt, may the warp speed not pass you!

rambobo said:
Big thanks redukt, may the warp speed not pass you!
Click to expand...
Click to collapse
Enjoy your device
Next time simply hit the thanks button

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
rambobo said:
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
Click to expand...
Click to collapse
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!

hugehead83 said:
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
Click to expand...
Click to collapse
You didn't have to apply root again via ADB or TWRP?

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Mates, the may-factory-image is available. Same procedure as ever
https://developers.google.com/android/nexus/images#instructions
Happy flashing

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Correct
But judging from others' experiences here, YMMV. I tried the latest FlashFire build too, but that got me nowhere.

LG LGMS550 Stylo 2 Plus?

Just delete this if it's considered in the wrong place. If and when is the the Stylo 2 Plus getting its own forum and has anyone come up with an exploit for rooting this phone yet?

Hiya
Yes this is the wrong place. This is for the g stylo not the stylo 2 plus as can be seen in the name of the forum.
No there is not an exploit yet. Kingroot, kangoroot, one clove root, etc all do not work yet. Soon i would imagine
I even have trouble looking on the web for things because it seems we share a model number ms550 with the lg optimus m. Weird

You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.

Reserved

Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
mustangtim49 said:
You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6

Remote: unknown command
Rmontoya83 said:
Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6
Click to expand...
Click to collapse
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.

[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.

I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Rmontoya83 said:
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.
Click to expand...
Click to collapse

[email protected] said:
I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Click to expand...
Click to collapse
Then Twrp didn't flash

Flashing
Rmontoya83 said:
Then Twrp didn't flash
Click to expand...
Click to collapse
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?

[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
What software version are you running?

[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
Wrong command your trying to boot twrp
The correct command is "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse

It was something I found in another tutorial when I started trying other things, since the "fastboot flash recovery recovery.img" was not getting me past the standard Android recovery. I'm about to try the file you sent me last night. I'll let you know the result.
---------- Post added at 10:25 PM ---------- Previous post was at 10:13 PM ----------
Rmontoya83 said:
What software version are you running?
Click to expand...
Click to collapse
Android version 6.0.1
Android security patch level 2016-08-01
Kernel version 3.18.20
Windows 7 Pro x64
The recovery.img you sent also said it flashed, but I got to the same Android factory reset screen after the key press procedure (volume down, power, release power, repress power, release all)
Here's the latest:
C:\Users\Darin\Downloads\platform-tools-latest-windows\platform-tools>fastboot f
lash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15518 KB)...
OKAY [ 0.495s]
writing 'recovery'...
OKAY [ 0.362s]
finished. total time: 0.865s

Once you boot into recovery, let the screen fully dim, do not touch it... once the screen is completely blacked out, turn it back on and all touch features will be up and running... and don't mess with the adoptable storage feature..migrating data.. because TWRP will not recognise any data if you have this enabled.

[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
You have to push the ing to and directory. Fastboot push img
Sent from my LG-K550 using Tapatalk

[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
Are you on the newest firmware for that phone?
If you are downgrade that could be a fix to lock down the recovery

I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it? Usbhost mode..mount
Usb pendrive-
Mouse
Usb hub
Keyboard...etc
They say LG STYLO 2 PLUS DOES NOT SUPPORT OTG...LIES....LIES....THEY JUST DISABLED IT...WHY?...WELL..
FOLLOW THESE STEPS TO ENABLE FULL OTG SUPPORT
1-in root explorer go to:
-/sys/devices/soc/78db000.usb/power_supply/usb/usb_otg and edit from =0 to 1save
then-/sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit disabled to enable.. plug in otg cable..
Done

WoodEe23 said:
I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it?
Click to expand...
Click to collapse
You enabled it by adding it to the build prop lol

Dig waaayyyy deeper ..like
/sys/devices/soc/78db000.usb/power_supply/usb/ scroll to usb_otg and edit it from disabled to enable.
Then /sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit it to enabled..
VOILA!!!"PLUGIN OTG CABLE AND UR IN THERE LIKE SWIMWEAR

P 8 lite bootloop on stock firmware

Hello all,
I have Huawei P8 lite bought from Romania. I install the android 6 and I wanted to go back to 5, so I go trough the steps on the official huawei website :
1) download an install rollback package - all went fine, the B500 firmware was shown
2)download an install B132 - on this step the problem appear; after the installation the phone is in a continuous bootloop, it can;t even shut down for good. I hear the start up sound, then if I press the volume keys it's beeping, so somehow is booting but without showing nothing(strange random colors ). The PC is recognizing the phone, but ADB won't .
The phone isn't going in to the recovery mode or update mode.
I search the forum and found methods to unbrick the phone, but only using fastboot. Since my phone isn't rooted , I can't use this method. What can I do?

Moshu646 said:
Hello all,
I have Huawei P8 lite bought from Romania. I install the android 6 and I wanted to go back to 5, so I go trough the steps on the official huawei website :
1) download an install rollback package - all went fine, the B500 firmware was shown
2)download an install B132 - on this step the problem appear; after the installation the phone is in a continuous bootloop, it can;t even shut down for good. I hear the start up sound, then if I press the volume keys it's beeping, so somehow is booting but without showing nothing(strange random colors ). The PC is recognizing the phone, but ADB won't .
The phone isn't going in to the recovery mode or update mode.
I search the forum and found methods to unbrick the phone, but only using fastboot. Since my phone isn't rooted , I can't use this method. What can I do?
Click to expand...
Click to collapse
You don't need to be rooted to use fastboot. However you need to unlock the bootloader in order to use it and don't tell me that your bootloader is locked otherwise it's a bad news.

Yes, it is locked

Moshu646 said:
Yes, it is locked
Click to expand...
Click to collapse
Use Huawei restore mode from hi suite.

I manage to enter in recovery mode(thus nothing is shown on the screen) , the HI Suite tells me that I successfully entered in recovery mode, but when I press Recover I get: Your device is not supported for system recovery

Moshu646 said:
I manage to enter in recovery mode(thus nothing is shown on the screen) , the HI Suite tells me that I successfully entered in recovery mode, but when I press Recover I get: Your device is not supported for system recovery
Click to expand...
Click to collapse
Is there an option for flashing rom? If then select that option and then select official firmware and then continue.

Suleiman01 said:
Is there an option for flashing rom? If then select that option and then select official firmware and then continue.
Click to expand...
Click to collapse
I don't see nothing on screen.
Now I discovered that if I enter in recovery mode ( Volume down + Power ; still nothing showing on the screen), fastboot is recognizing my device but when I want to write something I get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash BOOT boot.img
target didn't report max-download-size
sending 'BOOT' (21708 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.016s

Moshu646 said:
I don't see nothing on screen.
Now I discovered that if I enter in recovery mode ( Volume down + Power ; still nothing showing on the screen), fastboot is recognizing my device but when I want to write something I get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash BOOT boot.img
target didn't report max-download-size
sending 'BOOT' (21708 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.016s
Click to expand...
Click to collapse
You can't because your phone is locked. Did you find that rom flashing option on Hisuite?

Suleiman01 said:
You can't because your phone is locked. Did you find that rom flashing option on Hisuite?
Click to expand...
Click to collapse
It has an Update option but HI is not connecting to my device because I have to tap something on my phone in order to connect.

Moshu646 said:
Yes, it is locked
Click to expand...
Click to collapse
Hello ,
I have an update : I manage to unlock fastboot
I also manage to write successfully the boot, cust, recovery an system img's , but the phone is still not working: it starts up, the screen is lightening, I hear the Huawei sound, but no logo, and then the phone shut's down

Moshu646 said:
Hello ,
I have an update : I manage to unlock fastboot
I also manage to write successfully the boot, cust, recovery an system img's , but the phone is still not working: it starts up, the screen is lightening, I hear the Huawei sound, but no logo, and then the phone shut's down
Click to expand...
Click to collapse
Can you go to recovery?

Moshu646 said:
I have an update : I manage to unlock fastboot
Click to expand...
Click to collapse
How did you do that? My phone is also in bootloop and I am not sure how to unlock the bootloader...

cunami said:
How did you do that? My phone is also in bootloop and I am not sure how to unlock the bootloader...
Click to expand...
Click to collapse
There is a program called Huawei product ID generator. You need Imei,Serial no.(both are on the box) and Product ID (via Huawei product ID generator). Through this you can obtain unlocking code
In Fastboot and rescue mode type this in minimal adb and fastboot
fastboot oem unlock XXXXXXXXXXXXXXXXX
Where XXXXXXXXXXXXXXXXX is the unlocking code.

Moshu646 said:
It has an Update option but HI is not connecting to my device because I have to tap something on my phone in order to connect.
Click to expand...
Click to collapse
I was talking about this (see the picture below).

Suleiman01 said:
There is a program called Huawei product ID generator. You need Imei,Serial no.(both are on the box) and Product ID (via Huawei product ID generator). Through this you can obtain unlocking code
In Fastboot and rescue mode type this in minimal adb and fastboot
fastboot oem unlock XXXXXXXXXXXXXXXXX
Where XXXXXXXXXXXXXXXXX is the unlocking code.
Click to expand...
Click to collapse
Thanks! Will try definitely.
Last question - does the bootloader unlock wipe the user data on the phone? I want somehow to extract it before flashing any ROM over. So my idea was to unlock it, flash some better recovery and make a backup of data partition.

I don't have that option
Maybe it appear when the devices is connected.

Moshu646 said:
I don't have that option
Maybe it appear when the devices is connected.
Click to expand...
Click to collapse
It appears on 64 bit version of Windows I tried it on 32 bit it wasn't there.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
cunami said:
Thanks! Will try definitely.
Last question - does the bootloader unlock wipe the user data on the phone? I want somehow to extract it before flashing any ROM over. So my idea was to unlock it, flash some better recovery and make a backup of data partition.
Click to expand...
Click to collapse
No. At least when I unlock my phone bootloader didn't wipe my data.
Just press thanks button if you don't mind

Suleiman01 said:
It appears on 64 bit version of Windows I tried it on 32 bit it wasn't there.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
No. At least when I unlock my phone bootloader didn't wipe my data.
Just press thanks button if you don't mind
Click to expand...
Click to collapse
I also have X64 windows, but my HI version is 4.0.5 and this is the last one, and only this I found to download. Where do you have the 4.0.6?

Moshu646 said:
I also have X64 windows, but my HI version is 4.0.5 and this is the last one, and only this I found to download. Where do you have the 4.0.6?
Click to expand...
Click to collapse
I have 4.0.6.301 version of Hisuite. Download it from this link(use chrome to translate it's Chinese).
http://consumer.huawei.com/minisite/HiSuite_cn/index.html
---------- Post added at 11:25 AM ---------- Previous post was at 11:05 AM ----------
Moshu646 said:
I also have X64 windows, but my HI version is 4.0.5 and this is the last one, and only this I found to download. Where do you have the 4.0.6?
Click to expand...
Click to collapse
Try this multi tool by sokoban.
http://huaweip8lite.blogspot.com/2016/04/mod-p8-lite-multi-tool-by-sokoban.html?m=1

The ROM flashing option is not active- I think because the device is not connected.
Tried with the multi tool, same result

In dire need of help to root Huawei P8 Lite.

Hi all!
First of all, Im new here, sorry if this is in wrong section (please don't delete the thread, move it to other section if needed) and that this has been posted millions of times but Im in really really dire need of help, and people told me this is best place to come to!
So here it is, I've tried countless methods and read alot of threads all over internet and nothing seem to work for me. (All info is down below just read it )
I tried with ADB and Fastboot, but where I get stuck always is with that my phone, somehow rejects new recoveries (TWRP, CWM) (???). What I mean is that when I try to start phone in a custom recovery(either holding +-volume and power button , or volume + and power or volume - and power) I get nothing(I can get him into his own recovery, but only options are to reset, shutdown and update and recovery and that is from first holding -volume and power then from fastboot and rescue mode and then by holding +volume). I got him ONCE to recovery(or whatever/however that place is called) where I can wipe partition cache and dalvik , it just stays at Huawei logo.
I tried both with scripts and with manual way where I input commands in cmd. I've bricked my phone about 4-5 times , and I know how to unbrick it with ease. What I dont know is how to get phone to take a custom recovery. And yes, I have unlocked BootLoader and followed all and every step there was in each guide I found. I tried with the most hated method (KingRoot and other kinds) but nothing.
Info you might need:
-As stated, phone is p8 lite, with marshmallow 6.0. (ALE-L21C432B584)
-BootLoader unlocked.
-I have all necessary drivers installed and all permissions on my computer for drivers to work correctly.
-Kernel Version - 3.10.86-gd9a2b44
-Yes of course I have debugging enabled everytime.
Once again, methods I have tried:
-ADB and FlashBoot
-All kinds of programs through phone (Kingroot, Iroot, KingOroot etc.. (I read that you can't root phone through this method but gave it a shot.))
-I don't remember if there was any other method to do it tbh because Ive been doing it for last 2 days and Im kinda tired and super pissed hehe.
But if I forgot/missed something of information that you need please just ask.
Sorry if there is too much of detail, I just wanted to describe my problem as perfectly as possible and as in much detail as needed.
Thank you all who will read/read (Oh the typing world) my thread I really appreciate your time and effort. All and any help regarding my problem will be tried out and appreciated ^^!

What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.

keikari said:
What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.
Click to expand...
Click to collapse
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.

Ebilog said:
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.
Click to expand...
Click to collapse
Weird, though you must have done something wrong when installing TWRP, because it removes stock recovery. Make sure you have typed everything right. Because if you type like "flash recvery" insted of "flash recovery" it shows stuff that by quick glance might seem correct. Oh I forgot you need root to reboot with terminal emulator XD mb. Could you show what fastboot shows when you install TWRP.

Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?

Ebilog said:
Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?
Click to expand...
Click to collapse
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.

keikari said:
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.
Click to expand...
Click to collapse
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||

Ebilog said:
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||
Click to expand...
Click to collapse
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"

keikari said:
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP

Ebilog said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP
Click to expand...
Click to collapse
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.

keikari said:
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.
Click to expand...
Click to collapse
So i managed somehow to get the to twrp menu and i flashed supersu and i flashed new version of twrp . but i think thats what made it crash. Would it be ok if my phone stayed with 3.0.2.0 ver instead of getting 3.1.0.0?
Bcoz when i flashed 3.1.0.0 phone got stuck on 2nd logo and didnt reset or anything.
Thank god i know how to unbrick a phone at least hahahah
Edit: If this thread stays and people with problem like mine need help , feel free to pm me ill gladly help

yeah older TWRP is good if it works.
Though problems you got are still weird.

I had this problem ..
If you have restored your system and can access twrp recovery , download supersu v2.62 and install it .. this version worked for me after trying many ..
Every time my phone bricks i was downloading new whole system , instead try flashing it with twrp its better ..
Good luck .