Database Users

[Q] OTA Updates with Root

I have a stock rooted Nexus 4 running Android 4.3 (JWR66V) and a custom recovery. Recently, the JWR66Y update showed up on my phone and I turned on OTA survival mode in SuperSU and proceeded to install the update. It booted into TWRP and proceeded to install up until a certain point but then it froze. I cancelled the installation and rebooted my device and I even got the "Updating Applications" indicator on the first boot. However, I checked the version and it was still on JWR66V and my device no longer shows an update available. I did the exact same thing with my Nexus 7 (2013) with the JWR66Q update and the same thing happened. Is there any way I can install an OTA update on a rooted device? Every time an update is available for one of my devices, I end up doing a full factory reset of my device to install an update. I have only been able to find things like Clean ROM and Shiny ROM and while I do appreciate the work these developers are doing for the community, I would prefer to be able to either download a fully stock and non-deodexed flashable zip for my device or find a way to install the OTA update without losing root. It would also be great if I could do so without a computer because I currently only have a Chromebook. Thank you very much.

Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2

Nathanation said:
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.

KeanuKe said:
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
Click to expand...
Click to collapse
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.

xda6969 said:
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
Click to expand...
Click to collapse
Can I fastboot flash the stock recovery after I've already flashed a custom recovery and still have root? And if the answer to that is "yes" will I still be rooted after the next OTA update?

I am having the same problem. Both my nexus 4 and 7 recieved an update (1.8MB) but it seems that i cannot get the update to install. Both devices were rooted using the Nexus Root Tool kit.
When i got the update the devices booted in recovery mode with TWRP. Do not know what to do. I saw no update in the baseband or build number.
I am running stock android.
Please advise

[Q] Nexus 7 Jellybean 4.3 update

hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.

Lemegeton300 said:
hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.
Click to expand...
Click to collapse
Same Here!, I had TWRP recovery and I'm rooted, so Just Flashed stock recovery and I though I can update easily. But now I can't!
-By the way, I did not change any system file.

Since you have Stickmount did your error message reference a bad file check on 'debuggerd' in the /system/bin folder? It seems Stickmount may replace or alter that file and you have to put back an original for 4.2.2 to successfully flash the update with TWRP. After replacing 'debuggerd', the update flashed just fine for me. Are you sure you didn't get any text other than 'Error'? Are you sure you didn't freeze or delete any system apps?

It also happened to my nexus 4, they recommended to use this way: (It won't erase the data)
http://forum.xda-developers.com/showthread.php?t=2377307

hey, the error has no message or info. it literally says the word "error" with red exclamation and thats it. i have not touched any of the system apps or done anything that could upset the system files.
i will try the suggestion from alipashang77, thanks

sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions

Lemegeton300 said:
sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions
Click to expand...
Click to collapse
There's tonnes of older posts with all the info you'll need. Gotta just search more.
Ota will erase everything except your internal/external sd cards. Plus ota wont work if anything system wise had been altered. You'd have to Odin stock 4.2.2 then do ota.
No reason why you can't just flash a 4.3 rom like anything else tho.
And in all cases, wiping your data and apps is best. You gotta back it up. Restore after. Apps and their data anyway. Restoring system app data is never ever a good idea.
Sent from my cellular telephone

Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium

thanks everyone. its finally updated to 4.3. i backed up my data and then flashed the stock 4.3 image and that failed and the device would not boot. i thought it was bricked but it let me flash the 4.2.2. image and then the 4.3 OTA update worked.
:good::good::good::good::good:

hi guys i know that the previous reply was that flashing to the 4.2.2 worked then the OTA worked, however i have an explaination for people that were stuck like me
i JUST managed to upgrade my nexus 7 to 4.3 (JWR66Y)
i found a helpful link to upgrade from http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
after following all the steps, my i wasnt able to flash the bootloader (bootloader-grouper-4.23.img).
after doing some googling today, i found that it is the bootloader in the 4.3 update that is different (according to http://forum.xda-developers.com/showthread.php?t=2417097&page=2) and that you need the JWR66V bootloader img file (which is also the bootloader-grouper-4.23.img) they explain it in the link above, and have a download link for it there.
so in order to do the update, what you need to do is follow the steps from the 1st link (extract all the files etc in place), but before flashing, copy the bootloader from the 2nd link into your platform-tools folder, then follow the steps to flash.
as long as you follow the steps, and skip step 10, you will keep your data also
hope that helped

95Z28 said:
Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/

vndnguyen said:
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/
Click to expand...
Click to collapse
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium

95Z28 said:
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
ok thanks. I'm on 4.3 and only root with stock recovery. So if the 4.4 available I will unroot and then OTA. Thanks!

Installing 5.0.2 on rooted tablet

So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff

viper2ko said:
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
Click to expand...
Click to collapse
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.

So if I get this right, OTA breaks also when recovery is stock, but supersu installed, modified hosts and gps.conf file

jshamlet said:
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
Click to expand...
Click to collapse
Only changed I have made are installing ad away

viper2ko said:
Only changed I have made are installing ad away
Click to expand...
Click to collapse
The HOSTS file came with the stock image. It counts, unfortunately. (I'm also an Adaway user)

Modify /system, you don't OTA. Period.
Just download the Nexus image and flash just system.img, not the batch file.

Can I flash the system.img in TWRP or do I need to flash the stock recovery?
And will this upgrade me from 5.0.1 to 5.0.2 without losing anything except for root?
Thanks!

^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.

yosmokinman said:
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
Click to expand...
Click to collapse
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.

flyinion said:
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
Click to expand...
Click to collapse
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.

magnumlove said:
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
Click to expand...
Click to collapse
Oh I wasn't going to do a fresh install (i.e. wiping everything), just flash that system.img or modify the batch file to remove the "-w" flag and just run that. I'm wary of running 3rd party ROMs now after I couldn't play movies through Play Movies that were downloaded to the device instead of streamed. Something to do with copy protection I guess

It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.

Telyx said:
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Click to expand...
Click to collapse
Assuming this was in reply to me? I'm not worried about losing anything. I've done the whole back it up and wipe between ROMs a ton on my OG Droid and Galaxy Nexus. In this case it's a worry that Play Movies for instance will detect that it is not a stock ROM/image and will disallow playing downloaded versions of movies in the app. I.e. you can download vs. stream for offline playback. I nearly found out the hard way (night before leaving on a vacation) that I couldn't play downloaded versions (it will download but not play them) when I for instance installed AOKP to my Nexus 7. As best I could tell from a bunch of Googling, it's something to do with copy protection.

It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.

Telyx said:
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Click to expand...
Click to collapse
Ah ok. Well, I ended up using fastboot to flash the system.img last night and looks like I'm good to go. I tried unrooting (SuperSU remove root function) and changing betterbatterystats to a non-system app first but the OTA still failed. Yeah I learned how to use the basic adb/fastboot stuff when I got my Galaxy Nexus and again with the N7. I figured that way if I totally broke something I'd know how to fix it, and all the fancy tools weren't around when the GNex first came out (at least I don't think they were).

I dirty flashed scrosler's 5.0.1 ROM when I got the 5.0.1 OTA notification, but when the 5.0.2 factory image was posted I fastboot flashed the system.img from that and rerooted. Naturally, less than half a day or so later, scrosler posted his 5.0.2.

So for someone that's not really too experience with fastboot, could someone post a step by step?
Where would I get the system.img?

Check the sticky threads for guides. Read and reread then get started on setting up the Android SDK. Once complete, type in the commands letter for letter.

Factory images with January security patch now available

This update is known as 6.0.1 (MMB29S): https://dl.google.com/dl/android/aosp/shamu-mmb29s-factory-fc7b590e.tgz
Anyone want to confirm that we can still use systemless root for this update?

Xplicit84 said:
Anyone want to confirm that we can still use systemless root for this update?
Click to expand...
Click to collapse
why, whats the point? why wouldnt you be able to use systemless root with it?

simms22 said:
why, whats the point? why wouldnt you be able to use systemless root with it?
Click to expand...
Click to collapse
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.

Xplicit84 said:
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Click to expand...
Click to collapse
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out

Everything's fine for me.

FYI, the radio.img and bootloader.img are the same as MMB29K, so they don't need to be flashed. Boot.img and cache.img are the same size, but I'll flash them anyway. System.img is a different size, so it definitely needs to be flashed.

Looks like the kernel is the same.
Sent from my Nexus 6 using Tapatalk

anyone having trouble downloading the new system image from the site?

simms22 said:
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Click to expand...
Click to collapse
While this is true. These security updates are meant to target thing like the root exploits. So while things may still work don't be surprised if it does start needing updates each time Google pushes a security patch. It's a cat and mouse game that will be played until Google manages to lock it down to the point that it is not worth it to root.

maddoggin said:
anyone having trouble downloading the new system image from the site?
Click to expand...
Click to collapse
The factory image download was very slow. Timed out the first time. Second time it worked OK, but still took about 30 minutes.

Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk

tsongwh said:
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
Click to expand...
Click to collapse
I second this too. Thank you in advance

i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.

daimonmustdie said:
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
Click to expand...
Click to collapse
Stock w/ systemless root and Elite kernel.
To applying the update I downloaded the factory image from https://developers.google.com/android/nexus/images untar and unzip image-shamu-mmb29s.zip to get at the system.img file. Then did fastboot flash system system.img, just finished booting and and 'upgrading' my apps. It looks like something in boot.img changed too, but everything seems to be running perfectly fine without flashing it; note that I do have a custom kernel installed, so that might have something to do with it.
If you also fastboot flash boot boot.img then you will likely need to go through the root process again to modify the boot.img to allow root to work properly.
Code:
$diff shamu-mmb29k shamu-mmb29s
Binary files shamu-mmb29k/boot.img and shamu-mmb29s/boot.img differ
...
Binary files shamu-mmb29k/recovery.img and shamu-mmb29s/recovery.img differ
Binary files shamu-mmb29k/system.img and shamu-mmb29s/system.img differ

Stock ROM, TWRP
I have followed the instructions and flashed only the system.img..Nexus 6 - Unlocked, Rooted, Stock ROM, TWRP. It appears everything is running well and the Update notification hasn't appeared..this update was constantly appearing in the notification window and was reported as 5.8mb downloaded patch.
Thanks for your help.

[OTA] Marshmallow Build MCG24.251-5-5

Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://www.androidfilehost.com/?fid=745425885120733909
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.

TheSt33v said:
Do not take this if your bootloader is locked and you'd like to unlock it at some point.
Click to expand...
Click to collapse
There, fixed it for you.
Gotta bold the important stuff.

ChazzMatt said:
There, fixed it for you.
Gotta bold the important stuff.
Click to expand...
Click to collapse
You're inhibiting natural selection.

TheSt33v said:
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://mega.nz/#!70Zh1BbS!cC_mZ8xouLVwvMlOZLKW2UyC-JXDS7SdnCjxDoafXbI
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
Click to expand...
Click to collapse
hweew ... new kernel ...
could you upload it?

3Dota said:
hweew ... new kernel ...
could you upload it?
Click to expand...
Click to collapse
TWRP flashable, including kernel, version will be up shortly.

TheSt33v said:
TWRP flashable, including kernel, version will be up shortly.
Click to expand...
Click to collapse
Any modem updates?

koftheworld said:
Any modem updates?
Click to expand...
Click to collapse
Yes. Will also be included in TWRP version.

Yee!

I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk

mustafu said:
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Have you done any modifications at all? Even in the past? For example, if you were rooted and then unrooted, if any files were left over from that process, the update will fail. If you had xposed and removed it, same deal. Even if you replaced your emoji file with an updated one, that will also cause it to fail. Did you modify build.prop? Fail.
The only way to be sure that it will pass is to reflash MCG24.251-5 with fastboot before taking the OTA. Or you could always do it the easy way and flash MCG24.251-5-5 with TWRP: https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795

I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia

I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app

g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Install titanium backup and freeze the app called Motorola Update Services.

Shtiff1 said:
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.

So I'm guessing it's for "security" issues. So I really don't need to take this, because it involves to much crap... Unrooting, cleaning cache, reflashing, having to do the phone over again, etc.... If that is all true, then how can I get rid of the system update?

g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Download "Disable Service" from the play store

TheSt33v said:
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
Click to expand...
Click to collapse
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Sent from my XT1254 using Tapatalk

mustafu said:
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Click to expand...
Click to collapse
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.

trial TWRP or temp TWRP custom recovery
trial TWRP or temp TWRP custom recovery
TheSt33v said:
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
Click to expand...
Click to collapse
Don't know if this would help someone install an update like this, but let me throw this out there. There's a way to boot to TWRP custom recovery and use TWRP without installing TWRP. Think of it as "temporary" TWRP.
Thus, you should still be able to flash stuff, including any TWRP-flashable updates, boot logos (to replace the unlocked bootloader warning, SuperSu, etc -- and when you reboot you still have stock recovery.
Now, I don't know why anyone would want to keep stock recovery when TWRP recovery does so much more... But I just recently helped someone with the same suggestion. He wanted to install SuperSu, get root, but keep stock recovery -- for some reason.
Anyway, think of it as "trial TWRP" or "temp TWRP".
I remembered when I made factory images for my Quark, in a variety of states, I used this temporary TWRP trick. I'd almost forgotten about it!
So, seems like you could flash THIS TWRP-flashable version of this update while temporarily booting to TWRP (but not actually installing it), and it wouldn't matter if everything "checked" out or not.
Of course, if you like it, then you can always install it permanently.
For reference, here's the most recent version of TWRP for our phone. (use the one with the most recent post date. @bhb27 updates it fairly often.)
TWRP FOR QUARK
https://www.androidfilehost.com/?w=files&flid=39562
Here's my complete reply:
______
Rahuld107 said:
@ChazzMatt,
Hi, can i root xt1225 using temporary twrp ( one time method). I don't need twrp/custom recovery. Just want root with stock recovery. I am on stock marshmallow, bootloader is unlocked .
Click to expand...
Click to collapse
TEMPORARY TWRP
OK, here's another suggestion. There is a way to boot to TWRP to install SuperSu but NOT install TWRP. You will not be flashing TWRP over stock recovery. You will STILL have stock recovery when you reboot. Think of it as "temporary" TWRP.
Put the TWRP file in your ADB folder and use this command. Your phone will boot to TWRP, but it will not be permanently installed. You can then flash SuperSu while booted into the TWRP interface and then reboot back to your system.
fastboot boot file-name.img (whatever your file name of TWRP is.)
Whereas, the command to permanently install TWRP is this:
fastboot flash recovery file-name.img (whatever your file name of TWRP is.)
___
Back when I first got this phone -- now over two years ago -- I made a bunch of backups in TWRP and posted the images online in various stages -- pure stock, stock + root, stock + root + TWRP. I made the first two with the "temporary" TWRP. People could flash them and already have root without having TWRP installed.
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
Click to expand...
Click to collapse
See? Even just stock + rooted but with no TWRP. I made that backup with a "temporary" TWRP which did not overwrite the stock recovery.
But they were only for 4.4.4 Kitkat, which came with this phone. After we went to Lollipop, I posted some more images, but just pure factory. Still, the "temporary" TWRP trick is useful.

Is it just me or the Gallery app in 6.0.1 scrolls really slow? Btw i didnt do a clean update from LP in case that could be the reason