Database Users

T-Mobile OTA URL 5.0.1 LRX22C to 5.1 LMY47M

5.0.1 Build LRX22C OTA to 5.1 Build LMY47M "T-Mobile"
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
Your bootloader MUST be unlocked already, if not, these instructions do not apply to you so don't do them, it won't work.
These are the steps I did that worked for me. No guarantees that it will work for you, or if it wipes or bricks your phone.
Basically, you're downgrading your phone to 5.0.1 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None. Set OEM Unlock in Developer Options on just in case.
2. Reboot phone to bootloader (adb reboot-bootloader), or Power+Vol Down while the phone is off.
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
Green Android with Red Exclamation mark is stock recovery. Press Power + Vol Up to activate the menus. I sometimes have to press them a lot to get it to show.
If your PC does not recognize ADB Sideload mode, unplug your phone and plug it back in, it should work. If not check Device Manager and reload ADB drivers.

nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
Click to expand...
Click to collapse
Thank You! THANK YOU! THANK YOU! lol thanks for sharing

How do i install this again what are the requirements

Looks like I'm reverting back to 5.01 to get this one.

Just installed it. Thank you!

iGoogleNexus said:
Just installed it. Thank you!
Click to expand...
Click to collapse
Good job, mine is still optimizing apps, super slow, 160 of 202.

someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???

simms22 said:
someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???
Click to expand...
Click to collapse
Radio is 95R, it's the same in the D system image.

nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
You must be bootloader unlocked already, if not, these instructions do not apply to you so don't do them.
Basically, you're downgrading your phone to 5.01 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None.
2. Reboot phone to bootloader (adb reboot-bootloader)
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
FYI, Radio is 95R, the E (Verizon build) is 98R
Click to expand...
Click to collapse
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?

the.emilio said:
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?
Click to expand...
Click to collapse
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.

nxt said:
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.
Click to expand...
Click to collapse
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol

Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!

I just finish side loading it......

mr pnut said:
I just finish side loading it......
Click to expand...
Click to collapse
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
the.emilio said:
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol
Click to expand...
Click to collapse
Same not sure. Ended flashimg all the img, 47E

jay661972 said:
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
Same not sure. Ended flashimg all the img, 47E
Click to expand...
Click to collapse
Yes sir.......

Sorry too far OT delete

kaos2569 said:
Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!
Click to expand...
Click to collapse
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?

LGSilva said:
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?
Click to expand...
Click to collapse
What if u already stuch with 5.1 47E bootloader, flash the one from op but when about tonto recovery, got the same woth the other guy, android with the spinning thing and not exclamation.

Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)

lainemac said:
Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)
Click to expand...
Click to collapse
98R and E build is for Verizon phones. The D builds are for all other non Verizon nexus 6 phones. I went back to 95R because 98R was giving me calling issues.

Android 6.0.1 and any camera (stock included) fail.

I haven't done a factory reset yet but I would love to avoid it if possible.
I went to take a picture of the wife's newly decorated Christmas tree and the stock camera fails to fully start. It behaves as if it can not use the hardware. When I look at the back there is a small red light/laser that refuses to go out unless the phone is rebooted.
I've rebooted the phone a few times and tried Manual Camera and a couple others .. same behavior.
The phone is running 6.0.1 and is rooted.
Anyone seeing this and have any ideas?

Are you using the stock kernel

I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.

SuperSmashedBro said:
Are you using the stock kernel
Click to expand...
Click to collapse
Yep. With the exception of being rooted and using a few utils like root explorer and recently ... nothing special. I did just notice Google Play Services *****ed and said there was an error but it wasn't specific about the error. I did bounce the cache for Google Play Services after seeing that.
Nothing odd about this phone ... it's been top notch for the last month.

fury683 said:
I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.
Click to expand...
Click to collapse
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.

aergern said:
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.
Click to expand...
Click to collapse
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------
Full reflash (without wiping userdata) with factory image seems to have worked... Now to try proceeding one step at a time with TWRP/root/Xposed to see if it breaks again.

fury683 said:
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
Click to expand...
Click to collapse
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.

I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img

aergern said:
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.
Click to expand...
Click to collapse
No dice. Reflashing the 6.0.1 vendor.img did squat. I'll wait.

darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
So reflashing the system.img and waiting for Chainfire to make a new boot image could be the solution. That kinda sucks but it could be the only solution.

darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.

fury683 said:
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.
Click to expand...
Click to collapse
Same here. Using the same root method each time with my Nexus 6 was never an issue.
Damn. hmm.

Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera

edd247 said:
Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera
Click to expand...
Click to collapse
Oh. So just flash supersu 2.61 instead of using the boot.img and supersu 2.5x method. Good. I'll give that a whirl.

I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.

fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I just erased and reflashed each partition except userdata so it's doing it's thing. Once it's back up then I'll just use 2.61 and be done with it.
Thanks. Just hope I don't have to look at the boot animation much longer ...

Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?

fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I did this ...
fastboot erase system
fastboot erase cache
fastboot erase boot
fastboot erase vendor
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot reboot
Seems to be stuck at the bootloader animation ... so far .. 20 minutes? I shouldn't have to wipe userdata .. right?

captainwahid said:
Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?
Click to expand...
Click to collapse
I used the only Angler boot.img in the list and it worked to root but the camera was screwed.

this one? http://forum.xda-developers.com/showpost.php?p=64004628&postcount=1195

Marshmallow and root

Hey. I had rooted 5.1.1 Moto X Style and did a return to stock 5.1.1. eu version (relocked bootloader). After booted up, I received update to Marshmallow, I installed it. It worked. Later I wanted to root it, so I unlocked bootloader again and also did flash custom recovery - TWRP (twrp-2.8.7.1-clark). Later I restarted device and its was stuck on logo of Motorola. Nothing boots up.
Cant find solution for this. Thanks.
UPDATE:
Solved my issue here.
UPDATE2:
If there is problems upgrading your device to Marshmallow, I would suggest install custom ROM TruPureXMM with custom KERNEL Frankenclark. I am using this combo for long period of time and now I can suggest to others too!

Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.

I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.

dgato said:
I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.
Click to expand...
Click to collapse
You need to reflash the LP radio from the restore all file ( NON-HLOS.bin ). That should do it.

I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.

JayShams said:
I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.
Click to expand...
Click to collapse
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.

BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.

ChadMan097 said:
Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.
Click to expand...
Click to collapse
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.

JayShams said:
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.
Click to expand...
Click to collapse
Nop, could find solution, so I did full wipe, and restored my backup file with 5.1.1. Also flashed stock logo, boot and modem, so it can boot my old 5.1.1. Moto.
Will wait for some kind of european ROM with Marshmallow, or TWRP update. Maybe later will try again to go fully stock and upgrade to Marshmallow, maybe will find something that will work, right now I just need my "phone" back so I can use it as daily driver.

I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.

JayShams said:
I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.
Click to expand...
Click to collapse
For wifi you should flash modem from his thread: https://www.androidfilehost.com/?fid=24269982087017262
Its Pure modem with band 12 fix.
I was using his Rom for some hours and didnt like it, my personal opinion:
Good: easy to install; twrp, supersu, xposed is working.
Bad: modified kernel (had more problems with it, it was draining battery so fast - 4 little cores was always online for ~900-1440MHz, and 1 big core always online for same frequancy as little cores, only one big core was going idle), so I didnt like all this modifications to stock kernel, also I didnt like that mine EU version now is listed as US version XT1575, and last that I noticed after some hours of usage is that on secret menu, mine 3G network was listed as WCDMA, but on EU of mine Style same 3G is using GSM auto method. I suppose that there can be some difficulties in EU countries - after changing settings to 4G, I loosed signal, and only after restart I got it back.
Thats the main reasons why I want european rom, or to modifie stock eu MM with xposed.

patt2k said:
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.
Click to expand...
Click to collapse
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.

ChadMan097 said:
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.
Click to expand...
Click to collapse
Either do systemless or 2.52 had same issue til I flashed 2.52
Sent from my XT1575 using Tapatalk

Solved my issue here.

BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.

Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work

donebrasko said:
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.
Click to expand...
Click to collapse
For this you need adb files on your PC.
You should read this thread, for how to get this files on your PC.
Then:
Basically, open terminal within adb driver folder, connect phone via USB to PC with USB Debugging ON, and you are ready to go - boot your phone into fastboot mode (shut down phone first, and then power+volume down) and now your are ready to use this command: fastboot flash modem NON-HLOS.bin, but remember to put this "NON-HLOS.bin" file into folder where you opened terminal from.
But if you experience problems, I suggest just install TruPureXMM ROM. It whould be much easier!
Good luck!

Kennyeni said:
Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work
Click to expand...
Click to collapse
Hello!
Have you read my other thread?
I have explained all my steps there, my device is Moto X Style (XT1572).
But I can suggest also use TruPureXMM ROM. Right now I am using this rom for about month, you could try it!
Good luck!

No luck with reflashing NON-HLOS.bin
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.

[email protected]@lker said:
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.
Click to expand...
Click to collapse
Lets start from beginning.
What is your device codename (region)?

[GUIDE] Enable Multi-window

Remember if you want to enable the test version of multi window in MM
you just need to change the ro.build.type in build prop from user to userdebug, then go to the drawing section in developer options and enable.
So far no major issues except a few graphic glitches but i can now watch a video with mx player and use chrome at the same time, so let the good times role
more detailed guide can be found below with root and non-root methods ( Root tested by me only)
[GUIDE] Enable Multi-Window Mode on Android 6.0 Marshmallow

Haven't rooted my Pixel as of yet, but I think this might just be the reason I do! Thanks for the heads-up!

NJ72 said:
Haven't rooted my Pixel as of yet, but I think this might just be the reason I do! Thanks for the heads-up!
Click to expand...
Click to collapse
you can do it without root just adb push pull the build prop to make changes

Even frigging better! thanks!
EDIT: Tried this and could pull absolutely fine, but can't push without unlocking BL and flashing TWRP I don't think as android recovery doesn't work and it won't let me write whilst it's booted.
Any advice welcome

You will need to unlock and boot loader and do it with TWRP. No need to root.

clubtech said:
You will need to unlock and boot loader and do it with TWRP. No need to root.
Click to expand...
Click to collapse
I have tried following this method with the new Software of Pixel C (6.0.1 (MXB48T)) and no root. I was able to flash the TWRP and do the pull/push method. But after that whenever I try to reboot the device, it goes back to the TRWP screen. It never boots to Android OS no matter how much or what I try and it only works when I flash the whole factory image all over again.
Anyone has a clue on how to make it work?

oneshotaz said:
I have tried following this method with the new Software of Pixel C (6.0.1 (MXB48T)) and no root. I was able to flash the TWRP and do the pull/push method. But after that whenever I try to reboot the device, it goes back to the TRWP screen. It never boots to Android OS no matter how much or what I try and it only works when I flash the whole factory image all over again.
Anyone has a clue on how to make it work?
Click to expand...
Click to collapse
TBH, this may only work with root, given the unique architecture of the pixel c or something else.
But seeing as you have flashed twrp and gone that far, why not just flash the xceed kernel, as I can confirm I have it working on lastest stock build with xceed and su

beardymcgee said:
TBH, this may only work with root, given the unique architecture of the pixel c or something else.
But seeing as you have flashed twrp and gone that far, why not just flash the xceed kernel, as I can confirm I have it working on lastest stock build with xceed and su
Click to expand...
Click to collapse
Ok I will try to do that!

beardymcgee said:
TBH, this may only work with root, given the unique architecture of the pixel c or something else.
But seeing as you have flashed twrp and gone that far, why not just flash the xceed kernel, as I can confirm I have it working on lastest stock build with xceed and su
Click to expand...
Click to collapse
I have flashed the kernel and rooted the device. It is all working great on the new build.
P.S: I also enabled the Multi-Window feature and it is working great

Unresponsive screen

I'm running h918 and never had a weird issue like this with any phone. I flashed Resurrection ROM latest version and Gapps with Magik 14.0 . The ROM won't boot which happens but when I go into twrp my screen is nonresponsive. Won't recognize any touch at all. I can get in fastboot mode also. Is there anything you guys could suggest trying to fix this cluster.Ive never had a ROM not boot then not be able to use twrp to fix. I didn't update to the latest bootloader were u can't roll back yet,if that would matter ..
Sent from my Nexus 6 using Tapatalk

The latest lineage source code is causing major issues with the v20. In order to fix the touch screen issue you need to reflash twrp through fastboot, or rerun dirty santa from step 3. Basically automates the fastboot stuff. Any rom that is using the latest lineage kernel trees for the the v20 is affected by this bug. I read somewhere it compiles with a corrupt ramdisk. Also flashing the werewolf 2.0 kernel fixes the unresponsive screen in twrp.

How can I flash werewolf? I've tried in adb fastboot..Dude this is frustrating as fk..I'm trying not to throw this phone against the wall..Been trying for hours
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
How can I flash werewolf? I've tried in adb fastboot..Dude this is frustrating as fk..I'm trying not to throw this phone against the wall..Been trying for hours
Click to expand...
Click to collapse
You can put the phone in fastboot mode and rerun dirty santa from step 3. Should reflash twrp and boot and get you into a working twrp. If you can't use fastboot ( fastboot flash boot "name of boot".img and fastboot flash recovery "name of recovery".img) - make sure the boot/recovery image is in the same directory as fastboot and ADB then the only thing you can try is grabbing a USB otg mouse and trying to use that once in twrp. Fastboot is super finicky so try renaming twrp and boot to simple names such as recovery.img and boot.img. Like I said rerunning dirty santa step 3 handles this automatically and after you should be able to power off and hardware combo directly into a working twrp. Don't really know what else to suggest.
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
Worst comes to worst you can always use lgup to kdz back to stock to get back up and running again. If you want root again be sure to use a of with an early security patch. Dec 2016 or earlier. H918 have lots of kdz available.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Also it doesn't have to be werewolf. Any working kernel in boot.img form for h918 can be placed in your fastboot directory and flashed. It will fix the broken touch screen as it is related to the kernel.

I don't think my fast boot is working...I've tried for 2 days .to flash twrp and a boot image ..Is it normal when downloading twrp to a windows 10 computer that the file is a disc file?It keeps saying corrupt..Or fastboot says no such file or directory but in adb and fastboot it always recognize my device ..Never had a issue like with this
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
I don't think my fast boot is working...I've tried for 2 days .to flash twrp and a boot image ..Is it normal when downloading twrp to a windows 10 computer that the file is a disc file?It keeps saying corrupt..Or fastboot says no such file or directory but in adb and fastboot it always recognize my device ..Never had a issue like with this
Click to expand...
Click to collapse
Yes windows will read it as a disc image file and will give a warning about not being able to read it that's fine. Fastboot should work regardless of ADB. mine is installed under c :/android/tools. You have to navigate there using cmd in order for fastboot to work. Also make sure you have your working boot.img right there next to fastboot.exe. They should be next to each other. Fastboot cannot flash anything unless the images are in the exact same directory. If your boot/recovery images are in any other folder besides the fastboot folder flashing will fail saying it could not locate it. Dirty Santa step 3 does this for you. If fastboot is borked completely and you know everything you are doing is correct than boot into download mode and run lgup. It will get your phone back to running bone stock. Many people have faced the same issue with the broken touch screen and have gotten their phone back. Check out the rez remix and lineage threads and read a few pages back. Lots of info on there

Yep mine was remix too..I've been reading for a couple days..One more question..Since my computer updated it now gives me power shell and not command prompt when shift and double click to open a window..Is that a issue ..They are similar but different in commands..Mine is in platform tools that's OK right ? I have the boot and the twrp in there too
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Yep mine was remix too..I've been reading for a couple days..One more question..Since my computer updated it now gives me power shell and not command prompt when shift and double click to open a window..Is that a issue ..They are similar but different in commands..Mine is in platform tools that's OK right ? I have the boot and the twrp in there too
Click to expand...
Click to collapse
Power shell should work just fine but if you think it may be causing issues open cmd and use cd c:\pathtofastboot\pathtofastboot. That will get you into the correct directory. Then try fastboot commands as normal. But I haven't heard of powershell causing issues as I've used it myself without problems just never used it to flash stuff.
You'll know if the path isn't correct because command prompt will report back with "unknown command" errors. Platform tools is fine

Got a new ROM flashed and wolf but no fix of touch screen
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Got a new ROM flashed and wolf but no fix of touch screen
Click to expand...
Click to collapse
Have you reflashed the recovery image as well? Reflashing twrp should fix it if you haven't. If that doesn't work I'm out of ideas

toastyp said:
Have you reflashed the recovery image as well? Reflashing twrp should fix it if you haven't. If that doesn't work I'm out of ideas
Click to expand...
Click to collapse
Yeah bro I have flashed several times.Been looking for a twrp flash able version .Ive found away to flash in twrp without a touch screen..I think something could be wrong with my fastboot or on both my computers it keeps saying can't find IMG but it's right there in the folder..Thanks for your help
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Yeah bro I have flashed several times.Been looking for a twrp flash able version .Ive found away to flash in twrp without a touch screen..I think something could be wrong with my fastboot or on both my computers it keeps saying can't find IMG but it's right there in the folder..Thanks for your help
Click to expand...
Click to collapse
That really sucks sorry to hear that man. Really doesn't make sense considering it is due to the lineage kernel. Try contacting the op of the rez remix thread. He had similar problems and was able to fix it. Might be able to help. And if you need the phone back immediately there's always lgup. When you figure it out let us know how you fixed it. Could help a lot of people who flash the latest lineage builds or compile rez remix themselves.
Also the op of the return to v10m stock thread might be able to help. There's a lot of people having issues with fastboot

I GOT IT FIXED BRO....USED ADB SHELL WHILE IN TWRP AND RESTORED A BACKUP OF A STOCK ROM AND BOOOOOM..AFTER DAYS OF STAYING UP AND TRYING ..I NEVER KNEW YOU COULD DO THAT WITH TWRP AND ADB..MAN THANK THE LORD ..
Sent from my LG-H918 using Tapatalk

kenbrownstone said:
I GOT IT FIXED BRO....USED ADB SHELL WHILE IN TWRP AND RESTORED A BACKUP OF A STOCK ROM AND BOOOOOM..AFTER DAYS OF STAYING UP AND TRYING ..I NEVER KNEW YOU COULD DO THAT WITH TWRP AND ADB..MAN THANK THE LORD ..
Click to expand...
Click to collapse
That's awesome! Happy to hear it. Definitely good to know that an ADB restore of a working backup can solve touchscreen issues for people where fastboot is failing. Definitely stay away from lineage sources until someone reports that it's working.

I am for sure...thanks man
Sent from my Nexus 6 using Tapatalk

toastyp said:
The latest lineage source code is causing major issues with the v20. In order to fix the touch screen issue you need to reflash twrp through fastboot, or rerun dirty santa from step 3. Basically automates the fastboot stuff. Any rom that is using the latest lineage kernel trees for the the v20 is affected by this bug. I read somewhere it compiles with a corrupt ramdisk. Also flashing the werewolf 2.0 kernel fixes the unresponsive screen in twrp.
Click to expand...
Click to collapse
THANK YOU!!! I have a 2 day old US996 that I was ready to take a hammer to. Flashed latest Lineage and booted up after a very long time...only to find the touchscreen not responding. I figured a ROM issue so I pulled battery and got back into TWRP but it also would not respond. At this point I figured it was certainly a hardware failure and I was freaking since I've unlocked the bootloader and it's no longer under warranty.
You are a lifesaver my friend. Many many thanks. Reflashing TWRP with fastboot worked a trick. Never seen a ROM completely disable a portion of the hardware. lol

LGtMgG2t said:
THANK YOU!!! I have a 2 day old US996 that I was ready to take a hammer to. Flashed latest Lineage and booted up after a very long time...only to find the touchscreen not responding. I figured a ROM issue so I pulled battery and got back into TWRP but it also would not respond. At this point I figured it was certainly a hardware failure and I was freaking since I've unlocked the bootloader and it's no longer under warranty.
You are a lifesaver my friend. Many many thanks. Reflashing TWRP with fastboot worked a trick. Never seen a ROM completely disable a portion of the hardware. lol
Click to expand...
Click to collapse
Glad to hear it! Some people have been having issues with fastboot itself so nice to hear it worked well for you. A couple of members have figured out the touch screen issue and have uploaded the changes to Gerrit. Hopefully we will see it merged within the next few days. The firmware makefile within the kernel source was not calling the appropriate firmware images breaking the touchscreen in the process.