Related
I tried to root huawei p8 lite ALE-L04 Lollipop 5.1 . The bootloader has been unlocked successfully. I followed these :
http://forum.xda-developers.com/p8lite/general/step-step-guide-to-unlock-bootloader-t3150616
http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
http://forum.xda-developers.com/p8lite/general/video-bootloader-unlock-root-custom-t3213616
But I cannot get into recovery mode., either by ADB command or volumn + power. Whenever I tried it, I get into the fastboot screen. I did flash the TWRP, but I cannot get into recovery , so I cannot flash supersu zip. Please help me.
If I downgrade to kitkat, do I need to unlock the bootloader again?
yes, if u go back to kk you need to unlock it again
type adb reboot recovery, it should reboot into twrp
I tried adb reboot recovery, it still goes to fadtboot screen (saying connect usb, and connect to PC with hisuite). If I unlock bootloader after downgrade to kk, is it the same unlock code that I used before ? Thanks
yep same code
jabonloco said:
yep same code
Click to expand...
Click to collapse
Thanks, do you feel my issue can be fixed by downgrade to KK? Thanks a lot.
jabonloco said:
yep same code
Click to expand...
Click to collapse
I tried to download p8 lite ALE-L04 lollipop twrp FROM http://forum.xda-developers.com/showthread.php?t=3208809 but the download link doesn't work. Do you where can I download it? Thanks a lot.
Problem solved after I used twrp for p8 Lite ALE-L04 lollipop
xdataibai said:
Problem solved after I used twrp for p8 Lite ALE-L04 lollipop
Click to expand...
Click to collapse
Can you provide the link that you used to download? I have downloaded and flashed twice successfully, but can't get TWRP to respond to the touch screen.
https://drive.google.com/open?id=0B4Ct__YyTYrBcU1Hc0JkQjhfWG8
jabonloco said:
https://drive.google.com/open?id=0B4Ct__YyTYrBcU1Hc0JkQjhfWG8
Click to expand...
Click to collapse
Thanks, that screen touches were very erratic, but enough persistence enabled me to flash Super SU and achieve root.
jabonloco said:
https://drive.google.com/open?id=0B4Ct__YyTYrBcU1Hc0JkQjhfWG8
Click to expand...
Click to collapse
Thank you!
touching screen doesn't respond at all... anyway, I'm able to adb shell as root, and therfore gain full filesystem access...
Strange. I flashed the same twrp.img, installed Supersu.zip from the internal storage, and rooted the phone. The twrp touch screen is responsive for me. So I am keeping this twrp recovery instead of re-installing the stock recovery.
The only thing I have to get used to is the keys to boot into twrp recovery are "vol up" and power buttons.
ALE-L04 Android 5.1, twrp-p8lite-5.1, UPDATE-SuperSU-v2.46
narigondelsiglo said:
Thank you!
touching screen doesn't respond at all... anyway, I'm able to adb shell as root, and therfore gain full filesystem access...
Click to expand...
Click to collapse
[GUIDE] [OSPREY] [MM] 【6.0/6.0.1】Install TWRP, Root and Xposed successfully on 6.0
1) Unlock your bootloader . for complete unlocking process go here.
https://m.youtube.com/watch?v=sw675ipX-ds&feature=youtu.be
IT WILL RESET ALL YOUR DATA.
2) Turn on USB debugging on
3) Boot your device into bootloader mode
4) flash TWRP recovery v2.8.7 r5. http://forum.xda-developers.com/devdb/project/?id=11051#downloads
5) Boot into TWRP recovery
6) Flash supersu zip v2.62-3. http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
7) After succsesfull flashing wipe cache/dalvik cache . reboot system. If it asks to install Root. DO NOT INSTALL ROOT AT THIS STAGE.
8) wait till Boot finishes.
9) If you want to install Xposed Boot into TWRP recovery.
10) Flash Xposed installer xposed-v79-sdk23-arm.zip. http://forum.xda-developers.com/showthread.php?t=3034811.
Thanks for contributors of TWRP, Supersu and Xposed.
I am G-Root...ed
Thanks man!, being trying a lot with no succes... till now... Excelent Work :good:
abhijeetc9762 said:
1) Turn on USB ) .
Click to expand...
Click to collapse
do we have twrp for moto g turbo?
The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?
abhijeetc9762 said:
3) flash TWRP recovery v2.8.7 r5.
Click to expand...
Click to collapse
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
You don't have chance anyway after rooting. You have to have Flash the firmware again to receive OTA
Sent from my MotoG3 using XDA Premium 4 mobile app
soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.
Tel864 said:
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.
Click to expand...
Click to collapse
In an earlier post you indicated that you can simply do a full unroot with SuperSU and receive OTA updates. Did that only apply to 5.1.1 and not 6.0?
Tel864 said:
I was able to d/l the update, but had to unroot to install the update. If you're using SuperSU to root, it's a simple matter to use the SuperSU app and do a full unroot, then just root again after the update.
Click to expand...
Click to collapse
Kakaroth89 said:
The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?
Click to expand...
Click to collapse
Same question. Coming from a Nexus 4 phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
EDIT (01-20-2016): Thanks for adding the missing unlock bootloader step to the instructions. I just ordered a Moto G yesterday.
pjc123 said:
Same question. Coming from a Nexus phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
Click to expand...
Click to collapse
To root you will need an unlocked bootloader.
Any one?
Rooted xt1550 with supersu 2.62 and then deleted moto bloatware, now phone stuck on black screen after rebooting. Any help abt deleting bloatware?
Seems fine..but
just done this and boot up looks normal but seems forever to boot up. It has not boot up yet, what is the estimated time to wait?
Does it matter if TWRP is configured as "Read Only" or not?
Tel864 said:
To root you will need an unlocked bootloader.
Click to expand...
Click to collapse
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader
Kakaroth89 said:
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader
Click to expand...
Click to collapse
No, all your data and apps will still be there.
Tel864 said:
No, all your data and apps will still be there.
Click to expand...
Click to collapse
I lost all apps and data when I unlocked bootloader.. I did not unlock until after the 6.0 upgrade.
MrTooPhone said:
Does it matter if TWRP is configured as "Read Only" or not?
Click to expand...
Click to collapse
Do no tick as read only.
Sent from my MotoG3 using XDA Premium 4 mobile app
OP updated for bootloader unlocking procedure
Sent from my MotoG3 using XDA Premium 4 mobile app
abhijeetc9762 said:
5) Boot into TWRP recovery
Click to expand...
Click to collapse
@abhijeetc Excellent instructions. One recommendation is to address the issue with the "read only" TWRP option. I am sometimes presented with this option during TWRP boot (not sure why this option is not presented every time since I never check "don't show again"). I am not sure if "read only" makes a difference or not. But I can confirm I was soft bricked after enabling read only and flashing 2.66. I did not wipe Dalvik/Cache either. I was successful with 2.62-3 but was not presented "read only" option either. Also, you may want to recommend a Nandroid back up prior to any attempt flashing root. Just a recommendation.
I notice under developer settings (tap Build Number a bunch of times in the "About Phone" section to access developer mode) it has the option "OEM unlocking - Allow bootloader to be unlocked" as an option. Does that make this process any easier or is it necessary? I bought my phone straight from motomaker.
Two-Click Unlock for Zenfone 2 official Android 6.0
original post in Taiwan Asus Zentalk by @shakalaca
**do it at your risk**
1.Your PC must be adb environment ready.
2.You should know how to get into stock bootloader.( press Power and Volume up together)
files needed:
1. Download unlock.bat and restore.bat from here.
2. Recomended TWRP for verification.(repacked)
steps:
1.Copy unlock.bat and restore.bat on to your PC.
2.Plug your device in PC, click unlock.bat. The program will enter bootloader mode, reboot and then unlock.
3.After it run through unlock, the device will indicate it will reboot in 5 second. **important** PRESS VOLUME UP at the moment to enter bootloader.
4. If you miss step 3, the device will stuck in Asus logo. Don't worry. Just press POWER and VOLUME UP to enter bootloader.
5.When the device is in bootloader, click restore.bat Wait for the reboot and you are done unlock.
6.To verify unlock status, flash the recommended TWRP.
Good luck and all credits to @shakalaca
Is it the same as the unofficial method for bootloader unlock? also is there a way to relock bootloader like flashing it again over MM Beta?
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Flynhx said:
Is it the same as the unofficial method for bootloader unlock? also is there a way to relock bootloader like flashing it again over MM Beta?
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Click to expand...
Click to collapse
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
timbernot said:
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
Click to expand...
Click to collapse
According to @shakalaca, the restore process get back to 6.0 ifwi. After the unlock, the droidboot stay at .184 alright.
What is the status of your device before unlock, rooted or unrooted? Can you flash the twrp provided by him ?
samcjtsai said:
According to @shakalaca, the restore process get back to 6.0 ifwi. After the unlock, the droidboot stay at .184 alright.
What is the status of your device before unlock, rooted or unrooted? Can you flash the twrp provided by him ?
Click to expand...
Click to collapse
my device doesnt get to this part > 3.After it run through unlock, the device will indicate it will reboot in 5 second. **important** PRESS VOLUME UP
but stays on > press any key to finish...... which then closes the window
I flash twrp,says ok but reboots back to bootloader after restarting recovery.
flashed back stock recovery and factory reset for another attempt...lets see
Works good to me. Miss that step where I supposed to pressed vol up button and phone stuck on white splash screen. Force off and then go to bootloader, then execute restore.bat and done. After that root and exposed and then I mess up some another stuff so need to flash 6.0.1 MOFD_SDUPDATE manually from stock recovery. Everything pass smoothly but root and exposed framework disappeared obviously. Root and exposed again no problems
cannot flash custom roms???
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Yousvel said:
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Click to expand...
Click to collapse
ATM this unlock can backup/restore stock rom in recommended twrp, but can't flash CM. Seems its boot.img need to be repacked.
Yousvel said:
Hi everyone,
I successfully unlocked my bootloader from MM beta, I successfully flashed the recommended twrp recovery, I successfully flashed rom and gapps but when I reboot the phone goes back to twrp recovery. Anyone else facing the same issue? Or is it impossible to flash custom roms?
Click to expand...
Click to collapse
Same problem here
samcjtsai said:
ATM this unlock can backup/restore stock rom in recommended twrp, but can't flash CM. Seems its boot.img need to be repacked.
Click to expand...
Click to collapse
how can i flash a stock 5.0 rom from the recommended twrp? I tried to do that but it doesn't work. Do I have to flash a stock 6.0.1 beta rom?
It worked perfectly!Thanx a mill!
Can't flash TWRP although the splash screen became white after unlock.bat -> unlocked
After restore.bat the splash screen went black as usual. Then I flash the recommended TWRP. But when I choose recovery mode in fastboot, it reboot to fastboot. When I adb reboot recovery in Android OS, it reboot to stock recovery. Can anyone help me to solve this problem?
I'm running .69 MM beta, I replaced the .54 fastboot image in the package with .69 one. Does this effect the unlock state?
timbernot said:
Different by the looks , the date gives it away and not a temp twrp-- although i am going to find out in about 10 mins --lets hope this works :highfive:
Not working for me
says flashing droidboot .184
anyone got this to work ?
no recovery after trying this - got stock recovery back from here ok
mega:///#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!ok8SQKII
Click to expand...
Click to collapse
Edit Unlock.bat, find "sleep 3" in the line 24 and change it to "sleep 25" to increase the waiting time to detect back the fastboot after your phone reboots...
This fixed me the issue.... try it...
can i flash supersu to become root after unlock with this method?
ponnuvelpandian said:
Edit Unlock.bat, find "sleep 3" in the line 24 and change it to "sleep 25" to increase the waiting time to detect back the fastboot after your phone reboots...
This fixed me the issue.... try it...
Click to expand...
Click to collapse
Thanks :good: , i`ll keep that in mind when the time comes back on 5 atm
kamyk70 said:
Works good to me. Miss that step where I supposed to pressed vol up button and phone stuck on white splash screen. Force off and then go to bootloader, then execute restore.bat and done. After that root and exposed and then I mess up some another stuff so need to flash 6.0.1 MOFD_SDUPDATE manually from stock recovery. Everything pass smoothly but root and exposed framework disappeared obviously. Root and exposed again no problems
Click to expand...
Click to collapse
How you root your MM beta?, please tell me, i wanna root mine too
Sent from my ASUS_Z008D using XDA-Developers mobile app
Bring twrp zip android 6 please.
Can anyone backup with TWRP and upload?
Factory reset, backup with TWRP, and upload[emoji6]
Gesendet von meinem ASUS_Z00AD mit Tapatalk
KarloHD said:
Bring twrp zip android 6 please.
Can anyone backup with TWRP and upload?
Factory reset, backup with TWRP, and upload[emoji6]
Gesendet von meinem ASUS_Z00AD mit Tapatalk
Click to expand...
Click to collapse
Are you going to post this in EVERY tread?
Sent from my ASUS_Z00A using Tapatalk
Now, if we can unlock stock 6.0, can anyone confirm me if we can directly flash custom roms without downgrading to 5.0
after running restore it worked, however when running unlock.bat, I get permission denied and the device goes tinto bootloader bootloop, and I had the device rooted and bootunlocked already in lollipop, I wonder why that happens?
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
If this didn't work you can also try flashing this modified boot.img, it has only been tested with the Mexican AT&T variant, so I don't know if it will work properly with other variants.
Thanks!
I would try this if I was certain Flashfire would work...(don't want to reflash for an OTA)
diegochiva95 said:
where? I want to see him
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-z-play/help/unlocked-bootloader-t3459976/page4
Post number 34
I take it back, sadly it is stuck at boot for me I tried it yes. No other SuperSu? I think I had the 03 version and you have 02... I think?
EDIT: not true, I had 02 too, but it just wouldn't work.
EDIT: It forced somewhat of a factory reset on me when I tried the same SuperSU but no systemless, I didn't lose any media but I had to relog in my account and download and update all apps again.
I will just wait for nougat...
several people commented that password is required to enter the recovery......
Enviado desde mi XT1635-02 mediante Tapatalk
diegochiva95 said:
several people commented that password is required to enter the recovery......
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
The same password that you used to encrypt the phone while setting it up. If you're using a pattern you can use the numbers equivalent to the pattern you used.
FreedFromDeath said:
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
Click to expand...
Click to collapse
Thanks for the tutorial. But was inquisitive to know why one cannot use systemless root on our Vertex??
Thanks!
great
just pick up my phone
btw 7 is not released yet right
hmnk said:
Thanks for the tutorial. But was inquisitive to know why one cannot use systemless root on our Vertex??
Thanks!
Click to expand...
Click to collapse
This isn't the Vertex though, this is the Addison.
FreedFromDeath said:
This isn't the Vertex though, this is the Addison.
Click to expand...
Click to collapse
http://www.gsmarena.com/moto_z_play...r_testing_55inch_screen_in_tow-news-19195.php
Anyways, coming back to the topic, why can't we use systemless root on our device?
Thanks,
Regards.
FreedFromDeath said:
As usual, I am not responsible for any damages done to your device after trying this little guide.
1.-You need to unlock your bootloader first, which means this doesn't work on the Verizon variant. You also need to be sure you have your system image available in case something goes wrong.
2.-Then flash the chinese TWRP found here. Thanks to @hjk23 for providing the link.
3.- Flash SuperSU-v2.78-SYSTEMMODE.zip from here.
4.-BOOM, you're rooted. You need to have in mind that this is using the System mode and it works without modifying the boot.img. This means you will NOT be able to flash OTAs the usual way. I haven't tried using Flashfire since I have not received any OTAs so far.
Click to expand...
Click to collapse
says it is not necessary to flash the .zip SuperSU only accept the root for the TWRP own. It is true?
diegochiva95 said:
says it is not necessary to flash the .zip SuperSU only accept the root for the TWRP own. It is true?
Click to expand...
Click to collapse
Isn't there a warning to never accept the root from the recovery?
Another thing, if deencryption doesn't work you can sideload the SuperSU zip using adb through TWRP.
Updated OP with a possible workaround.
FreedFromDeath said:
Updated OP with a possible workaround.
Click to expand...
Click to collapse
If you dont mind, could you provide the details of your device?
So I see there is a Chinese twrp for moto z play but is anyone working on a north American version? Same question for SuperSU? Will there be official versions with systemless root? I guess what I'm asking is should I wait a bit or go this route? I like otas. I also reeeeally like a rooted phone (exchange server BS needs to be bypassed for piece of mind).
Not enitrely sure what happened, but my phone wouldnt boot after flashing SuperSU, even after i restored stock system,boot, and EFS. The boot.img got me booting again though and now rooted. (US variant)
Edit: Can someone upload a stock boot.img for the US variant? I think my backup boot.img might be corrupt, as it causes my phone not to boot.
jon7701 said:
Not enitrely sure what happened, but my phone wouldnt boot after flashing SuperSU, even after i restored stock system,boot, and EFS. The boot.img got me booting again though and now rooted. (US variant)
Edit: Can someone upload a stock boot.img for the US variant? I think my backup boot.img might be corrupt, as it causes my phone not to boot.
Click to expand...
Click to collapse
My phone got frozen at boot, dual sim in the EU version.
I tried to flash the non-systemless SuperSU and that made it factory reset, still not rooted.
I will wait....
hmnk said:
Anyways, coming back to the topic, why can't we use systemless root on our device?
Thanks,
Regards.
Click to expand...
Click to collapse
Anyone??
Thanks
hmnk said:
Anyone??
Thanks
Click to expand...
Click to collapse
I tried to do systemless and it was unable to patch the boot image.
Also if someone could upload a US variant boot.img that would be very appreciated. On the mexican boot.img I cant get data or recieve calls. I can only make outgoing calls for some reason.
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