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!

[GUIDE] Unlock Bootloader, Install Custom Recovery, and Root the Pixel C (2/4/2016)

The instructions in this guide are outdated and way more complicated than necessary. Once the official release of Android 7.0 Nougat becomes available/rooted, I will update the procedures in this thread. In the meantime, I recommend referencing this post along with the original instructions.
A massive shout out to @cheep5k8 for all the hard work he did in getting root and recovery working on the Pixel C. Please donate to him if you can. He deserves it.
Disclaimer: This will wipe your device. Backup anything important before you start. I mostly made this guide for selfish reasons. cheep5k8 has done a great job but some of the instructions are a little vague. I like being spoon fed and I wanted a resource to refer to in the future. You know the drill. If it breaks, not my problem. Post in the forums or hop onto the XDA IRC channel.
There may be more efficient ways to do this, but this will get you where you need to be. If you find any problems or have any suggestions, feel free to reply (BE VERY SPECIFIC WITH STEPS) and I will do my best to update the instructions.
Prerequisites:
ADB/Fastboot - Minimal ADB and Fastboot
ADB/Fastboot Drivers - I recommend using Wugfresh's Nexus Root Toolkit and using the full driver installation guide. Alternatively, you can install them yourself using the official Google Drivers (no installer)
An easy way to access the ADB prompt is to navigate to the directory that ADB is installed in, hold shift and right click inside the directory. This will give you an expanded right click menu that includes an option to "Open command window here." Select this option and a command prompt will open that is already in the ADB directory, saving you from having to do a bunch of cd nonsense. You can check to see if your device is recognized in ADB by typing "adb devices." If ADB and the driver are all working correctly, it should come back with something like "5A20001071 device." You can also check to make sure your device is recognized in fastboot by booting to the bootloader and typing "fastboot devices." It will show something similar.
Necessary Files:
Pixel C Recovery - Cheap5k8's Recovery -- NYCHitman's Recovery (newer)
Pixel C Root files - Download the XCeeD kernel, su.img, and SuperUser.apk
Copy these files to your directory that contains the ADB and Fastboot executables.
Device Prep:
Enable developer mode
Go to Settings > About tablet
Tap on Build Number 7 times until it says "You are now a developer"
Enable OEM Unlocking
Go to Settings > Developer options
Enable OEM Unlocking
Tap on Enable when a disclaimer pops up
Enable USB Debugging (ADB)
Go to Settings > Developer options
Enable USB debugging
Tap on OK when prompted with a disclaimer
If the ADB USB driver has been installed, you will see a popup that says "The computer's RSA key fingerprint is: xx:xx:xx:xx(blah blah)"
Check the box next to "Always allow from this computer"
Tap on OK
Unlock Bootloader:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
Input the following to unlock the bootloader:
Code:
fastboot flashing unlock
You will be prompted on the tablet screen with a warning about unlocking the bootloader.
Press the power button to unlock the bootloader.
The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see the green android with some spinny stuff. This is the userdata being formatted.
When complete, the device will boot back into the bootloader and say
Code:
Waiting for fastboot command...
Boot back into Android by inputting:
Code:
fastboot reboot
Your Pixel C will be reset, so you will need to re-enable USB debugging. Connect to your wireless network and then skip past everything else in the initial setup, as all of this setup info will be wiped again later on. Refer to the "Enable USB Debugging (ADB)" steps above to re-enable USB debugging.
Install Custom Recovery:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
With the Pixel C in the Fastboot bootloader and the recovery file in your ADB directory, input the following:
Code:
fastboot flash recovery (replace with custom recovery filename).img
Example:
Code:
C:\>fastboot flash recovery twrp-2.8.7.0-dragon-ryu-01082016-2.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
(bootloader) erasing flash
OKAY [ 0.054s]
sending 'recovery' (13760 KB)...
OKAY [ 0.349s]
writing 'recovery'...
(bootloader) writing flash
OKAY [ 0.375s]
finished. total time: 0.783s
Reboot into Recovery using the physical buttons. If you reboot the device back into Android, it will write over the custom recovery with the stock one. This will be fixed in the future.
Code:
Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
Install Root:
In TWRP, navigate to Wipe > Format Data
Type "yes" in the warning prompt and wait for the userdata partition to format. Again, this will wipe your tablet.
Press the Home button at the bottom when the format is complete
Navigate to Reboot > Bootloader to boot back into Fastboot
In the ADB prompt, flash the new kernel:
Code:
fastboot flash boot (replace with xCeeD kernel filename).img
Example:
Code:
C:\>fastboot flash boot xceed-kernel-google-dragon-02-01-2016-RC1.img
target reported max download size of 268435456 bytes
erasing 'boot'...
(bootloader) erasing flash
OKAY [ 0.064s]
sending 'boot' (6220 KB)...
OKAY [ 0.161s]
writing 'boot'...
(bootloader) writing flash
OKAY [ 0.197s]
finished. total time: 0.426s
Reboot into Android. The device may boot twice.
Code:
fastboot reboot
Reboot back into Recovery. Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
In TWRP, navigate to Mount and check only Data
In the ADB prompt move su.img to /data:
Code:
adb push su.img /data
Example:
Code:
C:\>adb push su.img /data
5677 KB/s (33554432 bytes in 5.772s)
In TWRP, navigate to Mount and uncheck Data
In TWRP, navigate to Reboot > System
Perform initial device setup
Once you are at the home launcher, re-enable USB debugging (Refer to Device Prep)
In the ADB prompt, install superuser.apk:
Code:
adb install Superuser.apk
Example:
Code:
C:\>adb install Superuser.apk
8612 KB/s (6227998 bytes in 0.706s)
pkg: /data/local/tmp/Superuser.apk
Success
Install Busybox from the Play Store: link
Congrats. You are now rooted (not in the Australian sense).

Big big thanks
Amazing, great job.

P.S. One thing to add, for those who bought SuperSU Pro, you can install that too from the Play Store instead of installing the APK, but at the moment, it will say that the su binary is outdated (because the xCeeD kernel comes with 2.66, but SuperSU is already at 2.67). There needs to be a somewhat better solution but it's a bit hard to come up with it.
xCeeD v1-RC4 will have SuperSU updated to 2.67, and I'm thinking of how to make it possible to flash the normal SuperSU ZIP in TWRP. I will probably modify TWRP in some way to make that possible.

Very good step by step, guide, I went through the same process myself yesterday, although without the benefit of your guide!
Just one additional suggestion I would make, especially for people who have already got things set up nicely on their device.
Before doing anything you can make a backup of your device data using adb.
I used the guide at - http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Although you cannot guarantee everything will restore perfectly (I recommend that for important apps that have the capability - backup the settings manually and remember to copy them off the device), it certainly saved me a heck of a lot of time in putting things back exactly as they were before - and it is a lot quicker than letting google backup restore things.

Does this void the warranty?
Great job,anyway
Enviado desde mi Pixel C mediante Tapatalk

Cool, but you don't mind make put the video or pictured for guides.
Keep it up!!

there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command

Scarfacez2007 said:
there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command
Click to expand...
Click to collapse
Are you booting into TWRP recovery or the stock Android recovery?

I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command

Thank you for this in depth tutorial.. GREATLY appreciated..my C will be in tomorrow just in time for RC4! Hopefully all goes smooth with this. So no need to swipe fastboot fix in twrp??

Scarfacez2007 said:
I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command
Click to expand...
Click to collapse
I had that too after my first attempt, I reinstalled TWRP and it worked after the second flash.
There were no errors shown either time.

The same thing - no command, though the TWRP is installed. Re-installing doesn't help at all.
UPD Just managed to do this step by manually booting into recovery without booting the ui.

I updated the instructions saying to use the physical buttons to boot into recovery immediately after writing TWRP to flash. I believe this should mitigate the issue with the device overwriting the custom recovery before the kernel is flashed.

You don't mind guide put with the video or picture?

Scarfacez2007 said:
You don't mind guide put with the video or picture?
Click to expand...
Click to collapse
I have no plans to make a video or pictures.

Finally I got rooted about time!!!! thanks oRAirwolf!!!!

I just wondering I can download Xposed 6.0.1 on my pixel c?

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
I have no idea. I would probably start a new thread in the Q&A section.

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
Yep xposed works fine

How did you get download xposed with arm64 for Google Pixel C? where get it? you don't mind can find for me on link?

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

[Root][RS988] Rooting RS988

Now that LG has released the bootloader unlock for the RS988 it can now be rooted.
------------------------------------------------------------------------Disclaimer---------------------------------------------------------------------------------------
This post is meant to be educational and I am not responsible for any lost data or damaged devices resulting from the following instructions
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-----Instructions on Unlocking your bootloader can be found here---------
WARNING THIS WILL FORMAT YOUR DEVICE
https://forum.xda-developers.com/lg-g5/development/official-european-lg-g5-h850-bootloader-t3363040
The only difference is selecting RS988 when selecting your device
---------------------------------------------------------------------------------------
Requierments:
ADB
fastboot
An RS988 LGG5
The working (though not entirely tested!) TWRP image is found here https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-rs988.img (Thank you jeffsga88 for finding this link)
The Latest SuperSu Binary
Step 1:
Make sure your RS988 is fully updated, the rebooting into the bootloader is only unlocked in the most recent updates.
Step 2:
Enable Developer options and USB Debugging
Step 3:
Enter Command
Code:
adb reboot bootloder
Step 4:
Once in bootloader run
Code:
fastboot flash recovery [path to twrp image on your pc]
Step 5:
Turn off the device DO NOT let it boot back into android!!
If you do boot back into android, you will need to re-flash TWRP (Steps 1-4)
Step 6:
With your device unplugged, hold power and volume down, releasing the power button for a moment when you see the LG logo, then
re-pressing the button to enter recovery, on the following screen select yes both times
Step 7:
(The Following Text other than step numbers is written by and entirely created by jcadduono, and can be also found at his post at https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047)
At this point, you will see the TWRP splash and reach a screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 8 you will be unable to boot!
If you are going to root your device or follow the rest of these steps, then it is safe to swipe right and enable modifications.
Step 8:
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
Step 9:
Please consider backing up your stock boot partition in TWRP before proceeding to the next steps!
Step 10:
If you want to be rooted with SuperSU:
Download the latest SuperSU stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
-or-
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Step 11:
Go to [Reboot] -> [System].
---------End of jcadduono post clip-------------
Now upon reboot, the phone may loop a few times and take up to 5 minutes to complete the process.
When you get into the device, run through setup as normal and you will have SuperSu installed and you will be rooted.
I can not verify Magisk Root Yet but will be attempting to do so soon.

You guys that have the rs988 you may want to ask one of the devs to add support for LOS and custom ROMs. But don't bug them either.
Maybe @King_lilrowrow could help if he has time, although I know he's been busy lately with other things. Hopefully someone will help you guys out. I have no idea how to, otherwise I would try and help. Nice you guys have rootr and twrp finally though.

I am using latest version: RS98810d
Step 4: flash recovery finished without error but cannot Power Off when press "Power" for 10 seconds so I unplug batterry then plugin again and press "Power+Volume down" but it cannot so I tried run command "fastboot boot twrp-3.0.2-1-rs988.img" after re-flash recovery but system shows:
=======================================
D:\adb>fastboot boot twrp-3.0.2-1-rs988.img
downloading 'boot.img'...
OKAY [ 0.554s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.585s
==========================================

AriesTruong said:
I am using latest version: RS98810d
Step 4: flash recovery finished without error but cannot Power Off when press "Power" for 10 seconds so I unplug batterry then plugin again and press "Power+Volume down" but it cannot so I tried run command "fastboot boot twrp-3.0.2-1-rs988.img" after re-flash recovery but system shows:
=======================================
D:\adb>fastboot boot twrp-3.0.2-1-rs988.img
downloading 'boot.img'...
OKAY [ 0.554s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.585s
==========================================
Click to expand...
Click to collapse
After flashing recovery, unplug USB cable and pull battery. Put battery back in, then press and hold volume down (hold volume down entire time) and press and hold the power button, when you see the lg logo, let go of power button for 1 second and then press and hold power button again until it reaches factory reset screen. One at factory reset screen select yes both times and you'll enter TWRP. When using the buttons remember to never let go of the volume down button only the power button for 1 second at lg logo.
You can also try after flashing it:
adb reboot recovery
Note: you must reflash TWRP if you allowed it to boot into os without flashing SuperSU or magisk.

AriesTruong said:
I am using latest version: RS98810d
Step 4: flash recovery finished without error but cannot Power Off when press "Power" for 10 seconds so I unplug batterry then plugin again and press "Power+Volume down" but it cannot so I tried run command "fastboot boot twrp-3.0.2-1-rs988.img" after re-flash recovery but system shows:
=======================================
D:\adb>fastboot boot twrp-3.0.2-1-rs988.img
downloading 'boot.img'...
OKAY [ 0.554s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.585s
==========================================
Click to expand...
Click to collapse
It is stated instead of doing that you turn off the phone and boot into the recovery with power+voldown

jeffsga88 said:
After flashing recovery, unplug USB cable and pull battery. Put battery back in, then press and hold volume down (hold volume down entire time) and press and hold the power button, when you see the lg logo, let go of power button for 1 second and then press and hold power button again until it reaches factory reset screen. One at factory reset screen select yes both times and you'll enter TWRP. When using the buttons remember to never let go of the volume down button only the power button for 1 second at lg logo.
You can also try after flashing it:
adb reboot recovery
Note: you must reflash TWRP if you allowed it to boot into os without flashing SuperSU or magisk.
Click to expand...
Click to collapse
I've followed your steps and I can root successful. Thanks alot

AriesTruong said:
I've followed your steps and I can root successful. Thanks alot
Click to expand...
Click to collapse
No problem! Glad we finally have it on RS988

I've held off on unlocking the bootloader and rooting, since it seems there currently are no ROMs available for the RS988 to flash. Basically you just end up with rooted stock?

FAUguy said:
I've held off on unlocking the bootloader and rooting, since it seems there currently are no ROMs available for the RS988 to flash. Basically you just end up with rooted stock?
Click to expand...
Click to collapse
Yes, currently all you can do is install TWRP and root stock. You can also install some audio mods like viper, but no custom ROMs yet for this version of the device.

Is there a touch TWRP recovery available? Granted I'm not sure if I will be able to flash it, since my power button is broken.

maRioHD said:
Is there a touch TWRP recovery available? Granted I'm not sure if I will be able to flash it, since my power button is broken.
Click to expand...
Click to collapse
Yes it's touch TWRP, can't even remember last time I saw a non-touch based one, been at least 3 years or so. Anyways it's located in the op. As far as flashing it, I believe you can do it without the power button. The issue will be rebooting to recovery after flashing it to flash SuperSU or magisk (if you don't do that or at least get into TWRP before first bit after flashing and delete the recovery from boot.p file, TWRP will be overwritten by default recovery and you have to flash again). While in fastboot mode, after flashing you could try and use:
Code:
adb reboot recovery
Not sure if that will get work or not while in fastboot mode, but something to try since your power button is broke.

Is it work on h860?
Sent from my LG-H860 using Tapatalk

Thank you for the advice. I'll try to give it a go tomorrow and report my success. And ya it's been a while since i have been able to do anything to my phone.

memi_pt said:
Is it work on h860?
Sent from my LG-H860 using Tapatalk
Click to expand...
Click to collapse
No. This is for RS988 only.

maRioHD said:
Is there a touch TWRP recovery available? Granted I'm not sure if I will be able to flash it, since my power button is broken.
Click to expand...
Click to collapse
Yes the twrp in the article is touch

Is the latest build RS98811d? Please confirm..
cheers!

wasabitobiko said:
Is the latest build RS98811d? Please confirm..
cheers!
Click to expand...
Click to collapse
You can always check using LG bridge and use update feature. If just wanting to know because your wanting to root and get TWRP, try and follow the guide. If you're not on latest version you'll know because you won't be able to unlock the bootloader using fastboot. If you can unlock your bootloader, you're good to go.
Here's the link and info for LG bridge and using it to check for updates:
http://www.lg.com/us/support-mobile/lg-LGRS988

jeffsga88 said:
Yes it's touch TWRP, can't even remember last time I saw a non-touch based one, been at least 3 years or so. Anyways it's located in the op. As far as flashing it, I believe you can do it without the power button. The issue will be rebooting to recovery after flashing it to flash SuperSU or magisk (if you don't do that or at least get into TWRP before first bit after flashing and delete the recovery from boot.p file, TWRP will be overwritten by default recovery and you have to flash again). While in fastboot mode, after flashing you could try and use:
Not sure if that will get work or not while in fastboot mode, but something to try since your power button is broke.
Click to expand...
Click to collapse
Adb reboot recovery sadly does not work, i encountered this myself , a replacement power button is quite cheap though

xaviex said:
Adb reboot recovery sadly does not work, i encountered this myself , a replacement power button is quite cheap though
Click to expand...
Click to collapse
Yeah didn't think it would but was worth trying Yeah, looks like a $10-15 fix

Thanks for the reply..
Gonna wait until there's some development happening for this device..
Cheers!
jeffsga88 said:
You can always check using LG bridge and use update feature. If just wanting to know because your wanting to root and get TWRP, try and follow the guide. If you're not on latest version you'll know because you won't be able to unlock the bootloader using fastboot. If you can unlock your bootloader, you're good to go.
Here's the link and info for LG bridge and using it to check for updates:
http://www.lg.com/us/support-mobile/lg-LGRS988
Click to expand...
Click to collapse

Boot loop after Android O DP2 update

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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