Database Users

[HOW-TO][DEV EDITION ONLY]Root on 4.4 KitKat

https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!

What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app

Jexx11 said:
What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it

alex94kumar said:
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it
Click to expand...
Click to collapse
That's odd, I used the TWRP version in Hashcodes thread, flashed with the Motorola Fastboot. When I went to restart from TWRP it asked me if I wanted to root and I let it. Now I'm rooted.
Sent from my XT1060 using Tapatalk

Stranger things have happened, I guess. Regardless of which method you use, you'll end up with root either way

This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.

chaoslimits said:
This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.
Click to expand...
Click to collapse
same here but i have 85% battery
so i guess we will have to re-flash and push the supersu

The only advice I can give to either of you is to try reflashing TWRP again

Actually i did it again and it worked, guess we can't just skip steps.
Sent from my Nexus 7 using Tapatalk 4

Well im glad it worked out for you in the end

It worked after I charged the phone.
Thanks
Sent from my XT1060 using Tapatalk 2

How do I return my phone to default in order to install OTA
I have already flashed the stock recovery but my phone is still rooted. Do I need to unroot? I tried installing the OTA and it said it failed.

This method should work on any version with with an unlocked bootloader such as Sprint and T-Mobile - not just the dev editions.

alex94kumar said:
https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
Click to expand...
Click to collapse
Anyone knows how to do UNROOT if I used this method to get root?

I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.

1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.

s0nic69 said:
1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.
Click to expand...
Click to collapse
If we're already on 4.4, how do we know if we have the first OTA?
Thanks

chillmeow said:
I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.
Click to expand...
Click to collapse
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
---------- Post added at 03:45 PM ---------- Previous post was at 03:28 PM ----------
doctor_evil said:
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
Click to expand...
Click to collapse
OK I feel like an idiot. I just noticed that in the fastboot screen it shows that it's locked. I thought developer phones were unlocked by default?
ok after unlocking it I was able to install twrp recovery with no problems

Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?

pphi said:
Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?
Click to expand...
Click to collapse
Are you selecting recovery with the power button or the volume up button? Volume up selects. If you use the power button, the phone just boots normally.

Rooting Stock XT1575 MM

Hey guys. Im running stock MM with unlocked bootloader. I was able to flash twrp on but when I try to install superuser 2.46 through twrp I am stuck at the logo screen when I reboot. Is there something else that needs to be done to root this phone?
I also noticed that every time I boot into twrp it prompts me with the "keep system read only?" dialog. I "allow modifications" every time.

I used a systemless root on M. BETA-SuperSU-v2.62-20151210170034 for sure works.

jason2678 said:
I used a systemless root on M. BETA-SuperSU-v2.62-20151210170034 for sure works.
Click to expand...
Click to collapse
Amazing, thank you! This worked for me too. Any idea why the newer versions don't work?

madkapitolist said:
Amazing, thank you! This worked for me too. Any idea why the newer versions don't work?
Click to expand...
Click to collapse
Not really. I think the automation is changing in the newer versions. 2.65 tries to decide between systemless and traditional root somehow. 2.62 definitely works on the mxpe. I've heard 2.64+ do not.

How were you able to flash twrp on MM? I have tried the guides and have not been able to boot into recovery. Any advise?

veuro said:
How were you able to flash twrp on MM? I have tried the guides and have not been able to boot into recovery. Any advise?
Click to expand...
Click to collapse
The only real trick I'm aware of is that you have to boot straight into TWRP from the bootloader. Don't reboot into your rom after fastboot flashing the custom recovery. Use the volume buttons to select start recovery and power button to start it. If you reboot into your stock rom your recovery will get replaced.
Flash SuperSU once you get into recovery, and that should make TWRP "stick".
Some people have said to reboot to recovery from recovery once the first time you boot into TWRP before rebooting to system. I'm not entirely sure that is required, but I did do it and TWRP stayed working for me.
One other thing, every time I've flashed SuperSU 2.62 my phone seems to bootloop once after the moto logo on the first boot. Don't panic. This seems to be normal, just let it go. The second time it will boot normally.

I tried both and it would simply not boot into twrp
Sent from my XT1575 using Tapatalk

veuro said:
I tries both and it would simply not boot into twrp
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Veuro: Are you flashing TWP 2.8.7.1? as soon as you flash and it says ok, open Recovery.

I am flashing just like the guides say.. I'm on MM original rom
Sent from my XT1575 using Tapatalk

Has anyone been successful rooting mm?
Sent from my XT1575 using Tapatalk

Are you unlocked?

Yes I'm unlocked. I finally figured it out using the systemless root guide, but it was a little confusing at first
Sent from my XT1575 using Tapatalk

Would you mind explaining what you did? All of the instructions I've found for systemless root use files associated with variants besides the US version which is what I'm trying to root.
Edit: Never mind figured it out! For those of you that are confused, the only version of SuperSU that works for a stock systemless root is 2.62-3. Simply fastboot TWRP then install that version of SuperSU through TWRP and you're good to go.

How to fix DM-VERITY issue for 7.0 flashed updates

Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!

Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.

Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?

Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.

Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.

I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me

Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.

does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...

PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.

card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently

What causes the dm-verity issue in the first place?

guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?

saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk

Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update

noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm

Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom

jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.

lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom

card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.

{Guide} How to Root ONEPLUS 3T (Unlock bootloader, TWRP Recovery, SuperSu)

Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting.
1. Download the ADB For Windows from here :-
https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view
2. TWRP: https://mega.nz/#!v9MmGQ5C!i5VroRopCVz2_Uoc6Mi2U6N4oDa0HK1SxCrkDrc4mwQ
3. SuperSu: https://mega.nz/#!eh13yLiC!3tkx_RkLg-D8T6mi35zDUB8AYEPLliBsL8yO1dmZbI8
Steps:
1.Backup Data
2.Unlock boot loader
3.Flash Recovery
4.Flash SuperSU
ENJOY
Video:
https://youtu.be/wwd31NU7VC0
Rooting OOS 4.0.3 ONEPLUS 3T
https://youtu.be/0QYp5tkBaao

Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Simply flash the full ROM.zip manually in recovery, typically 1.4GB.
That means not installing the incremental mini zips. And not installing from the settings menu.
It's up to you whether you want to wipe data or cache.

Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Download complete zip file n flash using two.

Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
yes if u follow the steps you wont have DM verity issuse.

uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
Dm verity zip is not needed when you flash SuperSu.

*winces* Ooh, all the files on file hosts? Why not just link to the legit sites?

Very easy to download the required files. Very simple step-by-step video guide. A+
Thanks for putting this together you made my night!

Thanks, I have unlocked bootloader, Installed TWRP, and Super Su.
one question though, when after setting my account going for nandroid backup there I found SYSTEM as well SYSTEM IMAGE.
what is difference between them, What thing should I backup.
Also there is showing your system is Unmounted, so when I should have to mount it.
Thanks to all Once again.

Hello guys, thanks for the guide!
I was wondering if anyone has faced the same problem as me - while trying to root the Oneplus 3T I constantly get a bootloop after flashing SuperSU. The latest TWRP (3.0.4.0) is installed without any problems in fastboot, the system is mounted as r/w, and I don't see any problems during flashing SuperSU package...
I've tried it before and after OOS 4.0.2, I've tried old and new, stable and beta versions of SuperSU, but either way the phone is stuck on bootscreen after flashing.
P. S. If I flash the official ROM after that - it boots up instantly without any errors... And with no root :/

I'm having the same problem

respectableafrican said:
I'm having the same problem
Click to expand...
Click to collapse
So nice to know I'm not alone!
Did you find a way to root your phone?

Try this SuperSU

I heard only SuperSU SR3 works

Just tried both versions (2.79 and the SR3 beta) - unfortunately, the same bootloop happens.

I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help

nishant.roy24 said:
I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help
Click to expand...
Click to collapse
Power off and boot instead of selecting reboot from twrp

hrsa said:
So nice to know I'm not alone!
Did you find a way to root your phone?
Click to expand...
Click to collapse
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)

respectableafrican said:
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)
Click to expand...
Click to collapse
Oh, finally - thank you so much!
Followed the guide on reddit page, and got the Magisk root, with Android Pay compatibility!
I wonder why it was so hard to find

[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