Database Users

[OTA] Captured Pure Edition XT1095 update from 23.16.3 to 23.16.6 (stagefright patch)

I received a Motorola OTA notification for a minor maintenance update which patched the "stagefright" vulnerability in my Moto X 2014 Pure Edition xt1095. I captured the OTA ZIP file from my cache folder, and it is attached to this post. Size of OTA ZIP is 4.29MB. (Note that Motorola OTA updates are named for the software version from which you must apply the update, not the software version to which you are upgrading.)
This is for a stock, unrooted xt1095 running Android Lollipop 5.1.
Prerequisite:
System version: 23.16.3
Build number: LPE23.32-21.6 or LPE23.32-21.3
After update:
System version: 23.16.6
Build number: LPE23.32-21.6 or LPE23.32-21.3 (unchanged)
You should be able to adb sideload this from stock recovery if you know how. If you're rooted, you'll need to request the stock 23.16.3 firmware from Motorola, and at least flash system.img and recovery.img to get back to stock system and recovery. After you do that, you might be able to sideload the OTA zip.

Deleted, sorry.

Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.

romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.

Thanks thenestor and Romracer worked perfectly as stated I went with twrp flash -

I just installed this update from the stock recovery and it worked flawlessly. Thanks for uploading this. My wife got it a few days ago and updated before I could grab the the zip file.
Sent from my XT1095 using Tapatalk

Flintberg said:
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.
Click to expand...
Click to collapse
System.img? Download please

I reflashed system.img of my current version and then flashed the zip in twrp.

romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?

I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?

I'm rooted with adaway applied, I tried flashing romracer's file but I'm stuck on the boot screen saying that my bootloader is unlocked. Is it because of adaway?

romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thank you so much for this! I lost my stock recovery so this is a godsend.

Flintberg said:
I reflashed system.img of my current version and then flashed the zip in twrp.
Click to expand...
Click to collapse
system.img have the backup to download and can flash? Sorry my english

tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
I'm having the same problem! Any idea how to fix it?

Damn. That file from romracer broke my phone
seriously....i can't fix it

@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops

sh33z0r said:
@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops
Click to expand...
Click to collapse
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
supremekizzle said:
Damn. That file from romracer broke my phone
seriously....i can't fix it
Click to expand...
Click to collapse
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
macravin said:
I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?
Click to expand...
Click to collapse
RSchmauk said:
I'm having the same problem! Any idea how to fix it?
Click to expand...
Click to collapse
Did you have Xposed install? Reflash the install zip. Otherwise see above.

romracer said:
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
Did you have Xposed install? Reflash the install zip. Otherwise see above.
Click to expand...
Click to collapse
i was rooted with xposed only, and now my phone won't turn on, stuck on the boot screen...
i have two questions,
If i reflash system.img, will that wipe anything?
is there a system.img only file that i can download, downloading 1.1 gbs on my slow connection will take 4 hours, i can't afford 4 hours without a phone....

After the ota, my phone won`t turn on, like many here. What i`m worried about is that my PC is not recognizing my phone in adb. What can I do?

I was also rooted, with stock everything else but hung on the unlocked bootloader warning screen. I'm thinking AdAway or Greenify must have modified /system since that's really the only root stuff I use. For the time being I just restored my /system backup and it's working but I'll eventually need to flash stock system.img I'm guessing. Otherwise I'm gonna end up accidentally tapping the update nag screen and screwing it up again.

Supersu abort on 7.1.1

Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash

Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).

ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess

I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)

Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.

Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?

Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!

Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck

I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.

ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore

Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.

dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work

Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.

Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)

dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread

Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt

Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip

HELP PLEASE!!PHONE not working after update

Guys help me please! After the last OTA update, I tried rooting as I always do through boot_a.img patching via magisk etc, and now the phone is not working appropriately. No network and no wifi, and after a while touchscreen stops working. I can't reflash the latest firmware I find on the official site as it's from February 15th and it says it's older than the one I have, so it doesn't allow me.
What can I do to fix my phone?

lowrider82 said:
Guys help me please! After the last OTA update, I tried rooting as I always do through boot_a.img patching via magisk etc, and now the phone is not working appropriately. No network and no wifi, and after a while touchscreen stops working. I can't reflash the latest firmware I find on the official site as it's from February 15th and it says it's older than the one I have, so it doesn't allow me.
What can I do to fix my phone?
Click to expand...
Click to collapse
Use the MSM tool and restore your phone to older firmware that way.
I don't know about the boot_a.img process you've been following, but that is not how I would recommend rooting.
Using fastboot, boot (DO NOT FLASH) TWRP, and then use a dd command to pull the boot.img
Boot into Android, install Magisk, inject root into the boot.img you pulled in the last step
Boot into fastboot, boot (DO NOT FLASH) the boot.img you just injected root into
Using Magisk Manager, Direct Install the kernel you booted from, then reboot and you are rooted

edit

NotATreoFan said:
Use the MSM tool and restore your phone to older firmware that way.
I don't know about the boot_a.img process you've been following, but that is not how I would recommend rooting.
Using fastboot, boot (DO NOT FLASH) TWRP, and then use a dd command to pull the boot.img
Boot into Android, install Magisk, inject root into the boot.img you pulled in the last step
Boot into fastboot, boot (DO NOT FLASH) the boot.img you just injected root into
Using Magisk Manager, Direct Install the kernel you booted from, then reboot and you are rooted
Click to expand...
Click to collapse
Thanks man, I managed to recover and boot again..now all I need is to reinstall magisk. Is there some guide you can point me to, that details the process you mention, mine is international unbranded and NOT-5G phone? I am not an expert so some of the things you say I am unsure how they are done...thanks again and very grateful for your time

lowrider82 said:
Thanks man, I managed to recover and boot again..now all I need is to reinstall magisk. Is there some guide you can point me to, that details the process you mention, mine is international unbranded and NOT-5G phone? I am not an expert so some of the things you say I am unsure how they are done...thanks again and very grateful for your time
Click to expand...
Click to collapse
The rooting process is the same, regardless of 5G or not. Check this thread, and follow the steps that begin with booting from TWRP (Step 5):
https://forum.xda-developers.com/7t-pro-mclaren/how-to/how-to-guide-root-oneplus-7t-pro-t4021325
You should not need the final step of setting A or B active, so disregard that one.

NotATreoFan said:
The rooting process is the same, regardless of 5G or not. Check this thread, and follow the steps that begin with booting from TWRP (Step 5):
https://forum.xda-developers.com/7t-pro-mclaren/how-to/how-to-guide-root-oneplus-7t-pro-t4021325
You should not need the final step of setting A or B active, so disregard that one.
Click to expand...
Click to collapse
Thank you I am so grateful... you helped me and it worked!
I have one last question for you in case you found a possible alternative. I noticed the camera app is quite poor, it doesn't even allow to select video/photo resolution/megapixels. Is there any modded version of the camera app you'd recommend, that will allow me to keep the same quality and full triple camera utilization that the stock camera app offers, while adding some nifty extra options?

lowrider82 said:
Thank you I am so grateful... you helped me and it worked!
I have one last question for you in case you found a possible alternative. I noticed the camera app is quite poor, it doesn't even allow to select video/photo resolution/megapixels. Is there any modded version of the camera app you'd recommend, that will allow me to keep the same quality and full triple camera utilization that the stock camera app offers, while adding some nifty extra options?
Click to expand...
Click to collapse
I haven't used it myself, but with root access, GCam ports are able to access all the cameras.

HELP - Is there any straightforward guide on how to root the latest OP7TPro firmware?

Hi guys, I have the OP7TP ME. I have always managed to root it through:
1)extraction of boot_a.img
2)patch file with magisk
3)flash file through adb
4)boot phone and patch again through magisk direct in order to recover wifi functionality
with the latest update though this process doesn't work anymore. Step 4 does not work which means if I do the first 3 and boot the phone, I have no wifi and after a while the phone crashes and reboots.
The only way to fix my phone so that it works again, is to reflash the full official update file.
Any help will be well appreciated on how to get root access without issues again.
Many thanks in advance

lowrider82 said:
Hi guys, I have the OP7TP ME. I have always managed to root it through:
1)extraction of boot_a.img
2)patch file with magisk
3)flash file through adb
4)boot phone and patch again through magisk direct in order to recover wifi functionality
with the latest update though this process doesn't work anymore. Step 4 does not work which means if I do the first 3 and boot the phone, I have no wifi and after a while the phone crashes and reboots.
The only way to fix my phone so that it works again, is to reflash the full official update file.
Any help will be well appreciated on how to get root access without issues again.
Many thanks in advance
Click to expand...
Click to collapse
Don't extract boot_a but extract boot.img which is from the current partition. Also I'd flash via fastboot. You don't need to patch with Magisk again if it's already patched.

Macusercom said:
Don't extract boot_a but extract boot.img which is from the current partition. Also I'd flash via fastboot. You don't need to patch with Magisk again if it's already patched.
Click to expand...
Click to collapse
Thanks I'll try

Macusercom said:
Don't extract boot_a but extract boot.img which is from the current partition. Also I'd flash via fastboot. You don't need to patch with Magisk again if it's already patched.
Click to expand...
Click to collapse
Hi thanks, I just tried with boot.img and it still doesn't work. No Wifi after flashing the patched version of it, and after a while phone crashes. Do you have a detailed guide to link me to?

lowrider82 said:
Hi thanks, I just tried with boot.img and it still doesn't work. No Wifi after flashing the patched version of it, and after a while phone crashes. Do you have a detailed guide to link me to?
Click to expand...
Click to collapse
Check this out: https://forum.xda-developers.com/7t-pro/how-to/10-0-3-patched-boot-image-oneplus-7t-pro-t3986351
That should do the trick

Hi thanks.. Unfortunately that's the guide I followed and it doesn't work no wifi and crash... Have you managed to root yours this way, with the latest firmware? Also I noticed that the latest magisk manager I have, doesn't offer the two options Prserve AVB 2.0/dm-verity & Preserve force encryption...they are just not present in the application....
Sent from my HD1913 using Tapatalk

lowrider82 said:
Hi thanks.. Unfortunately that's the guide I followed and it doesn't work no wifi and crash... Have you managed to root yours this way, with the latest firmware? Also I noticed that the latest magisk manager I have, doesn't offer the two options Prserve AVB 2.0/dm-verity & Preserve force encryption...they are just not present in the application....
Click to expand...
Click to collapse
Strange. Which OOS version are you running? It is fine for me with my BA version (the EU one)

lowrider82 said:
Hi thanks.. Unfortunately that's the guide I followed and it doesn't work no wifi and crash... Have you managed to root yours this way, with the latest firmware? Also I noticed that the latest magisk manager I have, doesn't offer the two options Prserve AVB 2.0/dm-verity & Preserve force encryption...they are just not present in the application....
Click to expand...
Click to collapse
Use beta magisk manager and try again
Also the lack of wifi is usually a mismatched boot to os ver
I'm on latest global ver of op7tp and rooted this way

Thanks! It worked now!

How to update to 11.0.8.8IN11AA on pre rooted device

Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.

paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.

MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?

Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.

MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.

paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.

Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.

Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...

datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?

Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches

What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.

It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.

Could someone post boot img I can't find this 11.8.8 to download.
Thanks.

Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.

If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.

h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541