Database Users

Help - I'm stuck in a bootloop 4 circles !

Hi I just tried to flash Android 4.4.4 without wiping & losing root using Nexus Root Toolkit
as per this link trendblog.net/flash-android-4-4-4-without-wiping-and-loosing-root/
I had slimkat 4.4.4 and tried to put stock 4.4.4 on this
After success messages the toolkit told me to wait for it to boot up but I am stuck on the four circles.
I have no recovery !!!
What can i do ?

Stop using took kits. They're nothing but trouble. Flash the factory image in fastboot and start over
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?

k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
First Google 15 second adb install xda. That'll set up fastboot on your PC. Then download the factory image. Google nexus 4 factory image. Extract that using 7-zip or winrar. In there is a flash-all.bat. just double click it. It will wipe your device so backup off the device first
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
Here is an excellent guide how to use fastboot:
http://forum.xda-developers.com/showthread.php?t=1907796
It is guide for Nexus 7, but the proceeding is just identic like with all other Nexus devices.
tetakpatalked from Nexus 7 flo

Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !

k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !
Click to expand...
Click to collapse
You say you can't boot into recovery? That's going to be a problem retrieving data
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

Is there no way to get cwm back on there ?

k500zm said:
Is there no way to get cwm back on there ?
Click to expand...
Click to collapse
Maybe, you'll need fastboot for that too. Download the latest image file from here. Rename it recovery
http://techerrata.com/browse/twrp2/mako
We'll go from there. You're going to learn a lot more than you bargained for
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
Click to expand...
Click to collapse
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Click to expand...
Click to collapse
Correct, but I'm not sure for the bootloader mode. I don't own a N4. Rather charge your battery first, it should work.
Also is it possible to get my files from the device before I wipe ?
Click to expand...
Click to collapse
If you're lucky, ADB might work even in bootloop if USB debugging was enabled in the developer options. As you didn't wipe, there is a small chance ADB pull might work.
IMHO the best you can do is to flash any custom recovery like TWRP or PhilZ with fastboot. The recovery.img file must be saved in the same folder where fastboot.exe is.
I assume Google USB driver is properly installed?
Fastboot must work, check in the guide I posted link for in my first post here how to check that fastboot commands are working. If "fastboot devices" returns "(your N4 serial No) fastboot" and your custom recovery is saved in proper folder, enter in CMD:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
After that, enter recovery mode, there is another chance your ADB pull function might work. The phone should charge in recovery mode.
To install SlimKat again, format: system, data, cache, dalvik cache (TWRP) or choose factory reset and "clean to install new ROM" in PhilZ. Then flash ROM and Gapps, best with ADB sideload.
tetakpatalked from Nexus 7 flo

Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'

k500zm said:
Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'
Click to expand...
Click to collapse
Did you install fastboot with the 15 second adb install?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

I have installed Android SDK manager and the 15 sec drivers

I have android bootloader interface in my xp device manager

k500zm said:
I have installed Android SDK manager and the 15 sec drivers
Click to expand...
Click to collapse
OK, we'll try with that. Put your recovery image in the same folder as fastboot.exe. Open a command window in that folder, shift right mouse click in a open area in that folder
Plug your device into the USB port. Type
fastboot devices (return) in the cmd window
Is your device recognized? If it is then in the cmd window type
fastboot flash recovery recovery.img
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

ok - this is what I got...
C:\adb>fastboot devices
fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>

Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]

k500zm said:
ok - this is what I got...
C:\adb>fastboot devices
01...... fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>
Click to expand...
Click to collapse
That sounds excellent, mate! Now try to reboot into the recovery mode
BTW: it isn't recommended to write down your device's serial No in worldwide public forum, it is your privacy in fact. Best edit your post now and remove big part of it (I also did it im my quote of your post)
tetakpatalked from Nexus 7 flo

k500zm said:
Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]
Click to expand...
Click to collapse
Good job. The nandroid won't be compatible. Let me see if I can find a cwm image. Now that you know how to use fastboot
Sent from my Nexus 5 using XDA Free mobile app

I have a nandroid backup from cwm just before i fcud up - is there any way to restore this ?
Thanks for your help so far geezers

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.

Help with rooting P8-lite Ale L21 dual-sim C432B564

I have a relatively new P8-lite L21 dual sim phone and I am quite happy with it. It came with C432B170 which is Lollipop I think 5.01. After a few days it updated to B172. I have unlocked the bootloader after registering with Huawei and waiting 2 weeks. Then I have successfuly rooted the phone with Kingroot phone version. Two or three weeks ago I have updated the phone to MM (6) and Emui 4 with local update (B560) that I have gotten from this forum. 2 days ago I recieved the notification of OTA B564 which went smoothly beside the fact that it reset the phone but i have succesfully restored (contacts, data etc.) All of this time since I upgraded to MM i have tried to root the phone but I was unsuccesful either with any software solution ( Kingroot, Kingoroot or others). After reading most if not all discussions on this forum and several blogs and how -tos, I tried the so called fastboot method others have recommended but here is now the gist of my problem. My phone is seen by my PC - OK so USB drivers are properly installed (by the way my PC is Win 10) and I have installed Android SDK as well as minimal ADB. When i try to flash TWRP 3.00.2 I can not do it (the message says something about not able to access or i think remote command not allowed. So since I cannot flash TWRP i am unable to put SU on the phone and root it. I hope someone more experienced and skillfull in Android world can point me in the right direction and help me. Thank you

Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.

VladHD said:
Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.
Click to expand...
Click to collapse
Downloaded minimal adb fastboot and installed it. Tried the procedure. Copied TWRP recovery to the minimal folder. Shift right clicked in the folder of minimal and opened command window. Adb rebooted to bootloader. Phone shows it is unlocked. The device is seen in fastboot window but flashing recovery doesn't work (same message) I am really confused. How do I give adb full permissions ?
Any way thanks in advance.

Did you activate usb debugging ?

VladHD said:
Did you activate usb debugging ?
Click to expand...
Click to collapse
Yes of course !

Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.

VladHD said:
Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.
Click to expand...
Click to collapse
The drivers were reinstalled. My bootloader shows unlocked on bootloader (bottom of fastboot screen). Fastboot devices does nothing. Adb devices shows my phone serial number correctly (I have it written down). But then when i try to flash recovery it is unsuccessfull. It says "FAILED (remote: Command not allowed)"

What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app

amageek said:
What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img

doomking_99 said:
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img
Click to expand...
Click to collapse
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)

amageek said:
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)
Click to expand...
Click to collapse
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.

doomking_99 said:
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.
Click to expand...
Click to collapse
ahhh... sorry mate, dont know the solution.. but try re-installing adb drivers again ...

Are you logged as adminstrator on pc?
Try to plug usb into different slots.

VladHD said:
Are you logged as adminstrator on pc?
Try to plug usb into different slots.
Click to expand...
Click to collapse
I am and I have. I am stumped. Obviously something is wrong with windows permissions I think. Is it possible to put recovery. img on sd card or on phone and flash recovery from the phone ?

This is the output every time no matter which usb port
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
W3D7N15C08019820 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.624s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
C:\Program Files (x86)\Minimal ADB and Fastboot>
The thing i don't understand is why fastboot command doesn't show device while adb command does.

You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app

amageek said:
You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.

doomking_99 said:
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.
Click to expand...
Click to collapse
Sorry for the zombiethreading here, but... what whas the solution? I'm curious

For the time being there is no solution. Can not flash TWRP - phone not rooted

doomking_99 said:
For the time being there is no solution. Can not flash TWRP - phone not rooted
Click to expand...
Click to collapse
Weird... i can't think of anything else myself that hasn't been said. Perhaps... redownloading twrp? Maybe the image is corrupted by something... ot's a long shot because ot should flash everytging that comes its way. But it's the only thing you hven't tried.

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