Hello friends
My phone is HTC One m8w
There isn't "update" in
Setting
About
Android version,
5.0.1
Software number
1.0.0.m8w
Build number
4.19.1402.15 CL458284 release-keys
Please help me for this problem
How can I update my phone?
Thanks a lot
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Ta3miyyasandwich said:
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Click to expand...
Click to collapse
There isn't any update for my build number
Sent from my HTC_M9pw using Tapatalk
if you are willing to, just root your phone and flash the marshmallow rom on to your phone and use titanium backup to backup everything before you do so.
you can root your phone,flash twrp recovery,flash Marshmallow rom.
lmentor said:
you can root your phone,flash twrp recovery,flash Marshmallow rom.
Click to expand...
Click to collapse
That's exactly what I just said
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom on to your phone
Click to expand...
Click to collapse
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
redpoint73 said:
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
Click to expand...
Click to collapse
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone. Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
justinchao740 said:
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone .
Click to expand...
Click to collapse
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
justinchao740 said:
Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
Click to expand...
Click to collapse
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
redpoint73 said:
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
Click to expand...
Click to collapse
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
justinchao740 said:
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
Click to expand...
Click to collapse
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
redpoint73 said:
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
Click to expand...
Click to collapse
Agreed plus my post never stated anything about rooting.
justinchao740 said:
Agreed plus my post never stated anything about rooting.
Click to expand...
Click to collapse
While my intent is not to be the guy that always has the last word; I also can't let you state a complete falsehood.
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom
Click to expand...
Click to collapse
Related
Mine says the upgrade to 4.5.141 is available to download. My Atrix is rooted with locked bootloader, I presuming I am going to lose root with the upgrade.
If so, what rooting method will work?
Thanks for your help.
PS: Will this worK?
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
charlyee said:
Mine says the upgrade to 4.5.141 is available to download. My Atrix is rooted with locked bootloader, I presuming I am going to lose root with the upgrade.
If so, what rooting method will work?
Thanks for your help.
PS: Will this worK?
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
Click to expand...
Click to collapse
Just unlock your bootloader and flash a new ROM on your phone. Most of the ROMs available for our phone have that update or better already on the ROM.
Sent from Neutrino, a planet far, far away...
cwburns32 said:
Just unlock your bootloader and flash a new ROM on your phone. Most of the ROMs available for our phone have that update or better already on the ROM.
Sent from Neutrino, a planet far, far away...
Click to expand...
Click to collapse
Thanks, but I don't want to take the route of custom ROMs, sorry.
I had to unlock my bootloader first using RSDlite and the small .sbf file (pudding.rar) Click here to download
My bootloader was supposed to be already unlocked but I guess the updated firmware didn't realize it. I couldn't run fastboot flash without getting an error
I then rooted by flashing preinstall.img and running commands to install the superuser binary and .apk. Instructions here
I don't know of a way to root 4.5.141 without unlocking the bootloader first. If you find a way let me know
http://briefmobile.com/motorola-atrix-4g-root should work.
lauterm said:
http://briefmobile.com/motorola-atrix-4g-root should work.
Click to expand...
Click to collapse
Same thing I used... different source. Still it requires an unlocked bootloader to flash images.
I believe the OP is looking for a root option that will work with a locked bootloader.
charlyee said:
Thanks, but I don't want to take the route of custom ROMs, sorry.
Click to expand...
Click to collapse
Just wondering.. Why not? ;o
nthon9 said:
Just wondering.. Why not? ;o
Click to expand...
Click to collapse
It's kind of a "Been there, done that" kind of thing from my Win Mob days. lol
I am pefectly happy with stock Atrix ROMs, and just want to be able to retain root or re root to use a couple of apps like Titanium Backup.
Has anyone with an unlocked bootloader/rooted Atrix tried the update?
I like to stick with the stock rom for now but I haven't found directions for updating to 141 yet. I'd like to keep root and not hard brick my Atrix...After the 2nd time Moto might get suspicious
I wasn't able to use the OTA updates once I rooted (even before I unlocked my bootloader). Of course, that could be Bell building in a check. I even tried unrooting (using GingerBreak) and that still wouldn't allow me to use an OTA update.
I would think you'll have to root, unlock bootloader, and then flash an firmware file from this tread: http://forum.xda-developers.com/showthread.php?t=1125944.
Actually, you're right in that the OTA update will probably fail without me going to a more "out of the box" state. I suppose I'd have to first create a nandroid, a titanium backup then flash my phone with a 4.5.91 stock image using fastboot, do the OTA, then re-root, and restore the titanium backup to get back to where I was. And if anything fails restore from my nandroid.
Does that sound right?
I've heard there could be issues relating to going back to a locked bootloader file. So I'm not sure on specifics there. I just run CyanogenMod to avoid all that stuff.
penderway said:
Same thing I used... different source. Still it requires an unlocked bootloader to flash images.
I believe the OP is looking for a root option that will work with a locked bootloader.
Click to expand...
Click to collapse
preinstall fastboot method works on a locked bootloader...at least it does for me (locked, rooted and on 141).
gnahc79 said:
preinstall fastboot method works on a locked bootloader...at least it does for me (locked, rooted and on 141).
Click to expand...
Click to collapse
So...in fastboot mode, you were able to run fastboot flash preinstall preinstall.img and thus successfully create the "preinstall\" partition with the necessary files on your phone without getting an error message???
My bootloader was unlocked long ago but I still couldn't flash the preinstall partition without running the pudding unlock .sbf first. Idk
I wasn't even able to boot into fastboot without unlocking the bootloader first.
penderway said:
So...in fastboot mode, you were able to run fastboot flash preinstall preinstall.img and thus successfully create the "preinstall\" partition with the necessary files on your phone without getting an error message???
Click to expand...
Click to collapse
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
I love how no one is answering your question just telling you to unlock your bootloader...
I downloaded the ota update, installed and got failed to boot 4 starting rsd node.. i had unlocked bootloader before update help please!! I pulled the battery for now.
gnahc79 said:
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
Click to expand...
Click to collapse
Well then, that settles it. The OP (who also doesn't have an unlocked bootloader) should be able to do the same.
gnahc79 said:
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
Click to expand...
Click to collapse
Is there any way to get step by step instructions for this
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
you will need to unlock to flash custom zip, but u can relock after
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference
playya said:
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference
Click to expand...
Click to collapse
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?
gjjh25 said:
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?
Click to expand...
Click to collapse
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4
playya said:
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4
Click to expand...
Click to collapse
Thanks, what do you recommend for the easiest way to unlock and root then?
gjjh25 said:
Thanks, what do you recommend for the easiest way to unlock and root then?
Click to expand...
Click to collapse
I used a toolkit but honestly you can unlock manually by just booting into bootloader mode. Go into development and try Wugs Toolkit.... Rooting the phone is easy and all methods are relatively the same.
I do not see anything wrong with giving CM a try as well
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
I recommend you to stick to your original plan, its your phone, do what you like, you don't need to flash custom roms if you don't want to. I am using stock kernel and stock KitKat right now and the performance is excellent.
Follow these instructions to unlock bootloader, install latest kitkat factory image, install custom TWRP recovery, and root. http://forum.xda-developers.com/showthread.php?t=2010312
The links to fastboot package and driver required is in my signature.
Link to download factory image: https://developers.google.com/android/nexus/images
Link for latest TWRP: TWRP recovery
Link for latest SuperSU package: SuperSU package
After you do all that, in bootloader menu, you can flash back the stock recovery (recovery.img), which is location in the "image-occam-******.zip" of the factory image. (fastboot flash recovery recovery.img)
Then lock your bootloader by "fastboot oem lock". You can also use BootUnlocker to lock and unlock your bootloader on the fly while in the phone, without losing your data, since everytime you do fastboot oem unlock, it will wipe the entire device.
By using stock rom, stock recovery, stock kernel and temporarily unroot (SuperSU) or hide root (SuperSU paid version), it allows you to receive future OTA updates from Google. If you want to modify your phones more while staying with stock, read up on Xposed Framework and its module Gravity Box, which is not yet compatible with Android 4.4 but will be eventually.
Just remember if you don't have custom recovery, once something goes wrong and your phone can't boot, its very hard to save the data inside. Once you have custom recovery like TWRP, you can make a backup of your stock image (which also backup your stock kernel) and try out other custom roms and easily go back to stock, then you can flash stock recovery again to receive OTA updates.
Thanks for advice everyone.
I rooted and unlocked with Wugfresh over the weekend. A lot easier than I thought it would be
This METHOD was developed ONLY for an UNLOCKED Motorola Droid Razr Maxx HD XT926m phone that is already updated to the last version of KitKat 4.4.2 (System version "183.46.15.XT926.Verizon.en.US").
IF YOU HAVE AN LOCKED BOOTLOADER AND TRY THIS METHOD IT WILL BE ONLY YOUR RESPONSABILITY IF YOU DAMAGE YOUR PHONE !!!
My Motorola XT926m had an UNLOCKED BOOTLOADER (ICS 4.0.4) and I flashed via RSD Lite the last stock firmware, "183.46.15"... After that, I was, of course, unhappy, because I read on different forums that this firmware version didn't support root... I tried to download the Hydrogen Peroxide xt926 application that others users recommended here on XDA forum, without success.
But now, after I applied this method, my phone is again rooted... Enjoy the steps, but be carefull, it was developed for XT926 phones with UNLOCKED BOOTLOADER!
1. Download the files "VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml" and "VZW_XT926_4.4.2-KDA20.62-15.1_CFC_1FF.xml" from the Motorola firmware site: "motofirmware.com/files/file/"...
2. Unpack the files...
3. Substitute/replace the "gpt", "tz" files (FROM the folder with "15.1" version TO the folder with "10.1" version)... You should replace all the files that "RSD Lite" will tell you that don't fit when you try to flash the new stock firmware. You will obtain a MODIFIED version of "183.46.10" stock KitKAt 4.4.2 firmware!!!
4. Flash this MODIFIED "10.1" firmware with "RSD Lite v6.1.5 Multi-Flash" (without using Rsd Script Generator.jar), but don't forget to remove the first two 'getvar' lines in the xml file.
5. Download and install the "Towel Root.apk" and root the phone...
6. Now your phone should be ROOTED.
What to do NEXT:
7.Download from the Play Store and install "Superuser.apk" made by ClockWordMode and after reboot the application will ask you to update SU binary. In my case, the SU binary didn't support an online update and I installed the "Superuser.zip" file downloaded from the ClockWorkMode site, via recovery method, in order to gain this update (you can do this as well, if you already have a TWRP or CWM recovery installed on your phone). With the other version of superuser, like "SuperSU.apk" or "Superuser.apk" ("eu.chainfire.supersu-2.apk", the last version, 5.6mb, for example) you will need to follow the same steps...
8. Using "Total Commander.apk", you can go to "File System root"/"Etc"/"installrecovery.sh", and finally rename this last file... Or you can use "ES3 File Explorer.apk" in order to rename the same "installrecovery.sh" file in "Device"/"Etc" folder (choose, for example, the name "installrecovery.shbak")...
9. Flash with "Flashify.apk" (downloaded form PLay Store) a new "recovery img.": "TWRP.img" (2.8.3.0) or "CWM.img" (6.0.4.8) for KitKat... You can find them on "rootjunkysdl.com/?device=Droid%20Razr%20HD&folder=Firmware"...
10. If you flashed "TWPR recovery.img" you will need to install "Stericson.busybox-1.apk" (from Play Store...), because TWRP works with this busy box... (You could install "TWRP.apk" as well, but you must be careful, because you will need to be able to boot into Recovery mode directly from your phone (with the combination key), not from this app... Many times, the phone is able to boot into recovery mode from TWRP application, but not from the bootloader... That's why it is better to uninstall TWRP application if you have this problem). If you flashed a "CWM.img" you can install "RomManager.apk".
11.Now it is the time to backup your system to SD card!
That's it. My phone was unlocked, and I didn't have any issue following all this steps... If you're locked don't try it.
But.. If you're locked you could instead use an application named 'Safestrap' for some purposes (read more here on XDA forum please), because is destinated for the phones with locked bootloader...
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
jackeagle said:
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
Click to expand...
Click to collapse
THANKS!
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
RikRong said:
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
Click to expand...
Click to collapse
Thank you, I wasn't able to find another downgrade method, could you give me the link, please?
http://forum.xda-developers.com/showthread.php?t=2789743
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
joel_sinbad said:
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
Click to expand...
Click to collapse
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
RikRong said:
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
Click to expand...
Click to collapse
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
joel_sinbad said:
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
Click to expand...
Click to collapse
This method is for an XT926 with UNLOCKED BOOTLOADER, with the last 183.46.15 update and the root access lost. I only described the steps that I already done with my phone. My Maxx HD is working and has root access again... I flashed custom recovery too (TWRP 2.8.3.0), I haven't any other problem.
RikRong said:
http://forum.xda-developers.com/showthread.php?t=2789743
Click to expand...
Click to collapse
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
ciprianv. said:
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
Click to expand...
Click to collapse
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
RikRong said:
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
Click to expand...
Click to collapse
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
ciprianv. said:
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
Click to expand...
Click to collapse
Thanks for doing that, I just want to make sure no one messes up their phone.
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
Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?
It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
acejavelin said:
It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
Click to expand...
Click to collapse
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?
dt.dragonborn said:
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?
Click to expand...
Click to collapse
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.
dt.dragonborn said:
Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?
Click to expand...
Click to collapse
Which OTA(s) isn't installing?
Sent from my Moto G Plus (5th Gen) using XDA Labs
cdysthe said:
Which OTA(s) isn't installing?
Click to expand...
Click to collapse
I am not much of a tech guy but the update says
New Version-NPN25.1 37-67
Improved audio in Video Capture
Data traffic improvements
acejavelin said:
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.
Click to expand...
Click to collapse
Thank you for this. I unlocked the bootloader, and installed TWRP and Magisk to gain root. This worked fine. However, I decided I wanted to go back to complete stock yesterday. So I uninstalled Magisk and flashed stock firmware using ADB. My phone is now unrooted, has a locked bootloader, and is running stock firmware which is what I wanted. Once I get the phone to boot, almost everything functions normally. However, it seems as though I now do not have any recovery whatsoever (and I assume that's because I did not specifically replace TWRP with stock recovery). So when I boot my phone, it goes to the bootloader and stops. If I then hit "start" on the bootloader, the ROM loads up normally after that. f that were the only issue, I could live with it. But not being able to get to recovery is concerning. And I am not able to get OTAs at the moment.
So, I'll check the other thread you mentioned. I assume I will need to flash stock recovery in order to get where I need to be.
Thank you for the post!