Related
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
JayZeus said:
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
Click to expand...
Click to collapse
If you made some modification to the 4.4.2 rom you'll have to restore the stock before upgrading to 4.4.4.
Bootloader can be unlocked, Recovery can be custom but any mod/root to the room will cause the error.
To restore to stock follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219
Thanks a lot, it worked!
By the way is the part where you erase you data mandatory ? In case I have to do this again.
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ! Thank you.
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) [emoji481]
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
This way I'll keep my installed applications?
Thanks.
4.4.2 > 4.4.4. just rolled out in UK (o2 moto g).
right after i get my phone rooted and started setting it up...
Thanks for this thread.. what's the minimum we have to restore, basically the system partition so it's unrooted?
If we have stock 4.4.2 (rooted) can we flash JUST these 3 files?
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
and skip the rest? I want to save redo-ing as much as possible..
I got the 4.4.4 OTA today (210.12.40.en.GB) and I have unlocked bootloader + Philz recovery - Philz worked fine for the 4.4.2 OTA update, but when I downloaded the 4.4.4 OTA and rebooted Philz would abort with "a status 7" mismatch error and then the phone would boot to Android, then 20 seconds later shutdown and reboot to Philz again, continuously. After some playing, I did the following:
1. Flashed stock recovery (taken from Mototool AIO's 4.4.2 stock.img) from fastboot - re-downloaded the 4.4.4 OTA but that failed with "Error!"
2. Flashed stock kernel (I was running faux123) - same issue, 4.4.4 OTA failed still.
3. Flashed latest Philz recovery again (philz_touch_6.50.6-falcon.zip) then
4. Flashed stock 4.4.2 GB kernel (to match my OTA version) - kernel from here http://forum.xda-developers.com/showthread.php?t=2649763 - success... OTA downloaded and this time installed.
SO, conclusion is you don't need stock recovery to flash OTA, BUT you do need the correct kernel for your update and having a custom kernel causes the mismatch error.
Hope this helps someone!
So the UPDATE-SuperSU-v1.91.zip in MotoG-Tools.zip still works to root 4.4.4 right?
i found it here
http://www.swedroid.se/forum/showthread.php?t=106595
and this is what i used for 4.4.2
Most of the old guides around no longer worked in 4.4.2, i dunno if they closed any other holes in 4.4.4?
edit: version typo sorry
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
JayZeus said:
I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error.
Click to expand...
Click to collapse
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
agoodhi said:
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
Click to expand...
Click to collapse
I figured it out... I simply did a delete cache from CWM recovery and now no more boot loop.
fatechand said:
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
Click to expand...
Click to collapse
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Smiff2 said:
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Click to expand...
Click to collapse
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
fatechand said:
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
Click to expand...
Click to collapse
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
---------- Post added at 06:32 AM ---------- Previous post was at 06:14 AM ----------
agoodhi said:
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
Click to expand...
Click to collapse
CWM message:
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
assert failed: getprop("ro.product.device) == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma"
E: Error in /cache/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
(Status 7)
Installation aborted.
Rebooting...
fatechand said he had CWM 6047 installed and OTA update was ok. he just had to re-root? perhaps difference between 6046 and 6047 CWM, or some difference in way you rooted?
I have same recovery, rooted, 4.4.2, so should work... ?
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Same problem here
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
A_Bunny said:
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
Click to expand...
Click to collapse
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Ulverinho said:
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Click to expand...
Click to collapse
Install the recovery with fastboot not adb.
A_Bunny said:
Install the recovery with fastboot not adb.
Click to expand...
Click to collapse
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Ulverinho said:
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Click to expand...
Click to collapse
Just load it onto your phone before you flash it. Your ROM does work.
A_Bunny said:
Just load it onto your phone before you flash it. Your ROM does work.
Click to expand...
Click to collapse
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Ulverinho said:
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Click to expand...
Click to collapse
It may work if it is the stock recovery.
A_Bunny said:
It may work if it is the stock recovery.
Click to expand...
Click to collapse
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Ulverinho said:
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Click to expand...
Click to collapse
Well the only thing I would recommend would be to install the stock system though fastboot manualy.
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
i feel ya same thing here, than i tryed installing a stock lollipop from here via twrp witch ended up messing my phone with failing the procedure wondered around couldnt revert to stock since im a noob and didnt even backed up the rom,but at the and of the day thank god for the cm12.1 finally menaged to make my phone running again at least
Greetings, I have the same problem, it is the last screen that appears when you install the update, and then restarts it goes off the screen update error ...
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yeah, that's the better way.
But I guess, I can install Stock 5.* straight away after wiping? Why bother about OTA, if there is ROM available?
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yep.
The solution is backup data, restore stock last firmware using fastboot guide posted in this forum and not even update apps (cancel gmail registration and everything it asks when it first starts) ONLY update motorola update services so you can get the ota again an install it. If you have the ota downloaded you can flash it through recovery but using the last recovery version (.61) and of course last firmware version. If you guys flash it all through fastboot, it should install w/o any problems.
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
I don't think the update will even proceed being that you're on a rooted ROM. I have that notification too, and i just don't know how to turn it off.
I to am rooted,unlockboot and stock rom. I don't feel like taking a chance. So I used titanium backup to freeze the software update and in the drop down notification if you press it, it's a notification from Google play services if you block it in apps it will disappear from your drop down. I also deleted the update zip in the cache folder.I used es file explorer ,device/cache/update
popwar said:
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
Click to expand...
Click to collapse
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
Why can't you flash the phone that is already rooted and has TWRP?
All you are doing is opening the LGUP tool and flashing the new H90120j .kdz file using the "refurbish" option then flashing the H90120j .tot file that has TWRP using the "update" option which will flash the phone regardless of what is running on your phone. The guides on the first link explain that. I believe your concern is keeping all of your settings and apps. Look up Titanium backup, it works for me.
Thank you. I only flash the LGH901AT-01-V20j-310-260-JUL-12-2016-ARB02+0ROOTTWRP tot file and all is good.
Well except that I lost Dolby audio.
I will look for a fix.
jun19inf said:
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Click to expand...
Click to collapse
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Anyone?
bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
There's a guide in general that tells how to do all this. In fact jun19inf WROTE it.
In a nutshell, do a twrp backup.
Upgrade to 20j by flashing the stock 20j kbz.
Enable usb debugging and oem unlock
flash tot that has twrp in it.
Now you can go into twrp and 1) root via supersu 2) restore ONLY data from your twrp backup taken previously to get your apps etc back. Alternatively Titanium Backup will also do just fine.
njdevils28 said:
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Click to expand...
Click to collapse
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ah. Thank you very much!
-NJ
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Where can I download the update file?
wbexpress said:
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Click to expand...
Click to collapse
Did you select refurbish or upgrade?
I believe you need to select upgrade when flashing or you get stuck in TWRP
Sent from my LG-H901 using XDA-Developers mobile app
How to root V10 T-mobile M.M ver V20L
How to root V10 T-mobile M.M ver V20L
Can some one guide me on the following:
1. Can I flash back and downgrade to Software version V20J from V20L.
2. Is there any root method for V10 t-mobile MM ver V20L.
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
jonsat said:
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
Click to expand...
Click to collapse
Thanks so much for your reply, I was about to flash it to downgrade my V10 from V20L to V20J i even downloaded the files for it Phew....
Okay, I have searched most of the rootings are V20J i have not found a method for rooting and twrp for V20L software update.
Please if u can share the link, that would be helpful...
thanks regards,
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
jonsat said:
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
Click to expand...
Click to collapse
Awwhh GOD!!! big thanks for your help, u r truly an awesome person. Peace and blessing upon u.
regards,
Hello everyone!
Today I got my Mate9 toyed around and then decided to root it. All went smooth as butter and everything is working perfectly.
Just about 1 hour ago, I see a notification saying that there is a system update available: later or restart now?
I am wondering, will this system update mess up my phone, since it is rooted, or not? I'd like to avoid any possible mess up for the time being
N3sh said:
Hello everyone!
Today I got my Mate9 toyed around and then decided to root it. All went smooth as butter and everything is working perfectly.
Just about 1 hour ago, I see a notification saying that there is a system update available: later or restart now?
I am wondering, will this system update mess up my phone, since it is rooted, or not? I'd like to avoid any possible mess up for the time being
Click to expand...
Click to collapse
Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
HUAWEI stock recovery installed
unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install).
st_voss said:
Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
HUAWEI stock recovery installed
unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install).
Click to expand...
Click to collapse
Here is what I did:
- Unlocked bootloader with Huawei code
- Installed new TWRP recovery
- Flashed supersu via adb (no SD card atm)
- Installed supersu apk
- Ta-da!
I actually checked the changelog of the new "update" and it is basically to restore the system back to before the change. Does it mean I am stuck with this version forever now?
N3sh said:
Here is what I did:
- Unlocked bootloader with Huawei code
- Installed new TWRP recovery
- Flashed supersu via adb (no SD card atm)
- Installed supersu apk
- Ta-da!
I actually checked the changelog of the new "update" and it is basically to restore the system back to before the change. Does it mean I am stuck with this version forever now?
Click to expand...
Click to collapse
What supersu zip did you use?
And no you are not stuck with your version forever. But updating will probably require more than simply applying an OTA update.
st_voss said:
What supersu zip did you use?
And no you are not stuck with your version forever. But updating will probably require more than simply applying an OTA update.
Click to expand...
Click to collapse
Followed this: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
N3sh said:
Followed this: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
Click to expand...
Click to collapse
So you are using Phh's superuser? I don't think that it's "systemless".
I would recommend a complete reinstall/update using https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 and using the lastest Magisk for rooting.
Mmm, I might just keep this until I have the need to reinstall. Thanks
It doesn't seem a system update allows you to skip it.
If the phone is rebooted, will it enter a loop or just fail the installation and carry on as normally?
I removed auto-download and rebooted, nothing different. Great
4thfloorcaveman said:
It doesn't seem a system update allows you to skip it.
If the phone is rebooted, will it enter a loop or just fail the installation and carry on as normally?
Click to expand...
Click to collapse
I think it's (stock) recovery that installs an OTA. I don't know the mechanism that allows the recovery to find the OTA file (maybe the OTA file is copied to a directory where recovery is lookup for update files or some boot parameter is modified) but a normal reboot should not trigger an OTA install attempt.
Thanks to user @NinjaBoyLao for the heads up... seems a new update is appearing on Moto X Pure, anybody else seeing it?
https://mobilesupport.lenovo.com/us/en/solution/MS124799
Screenshot attached.
EDIT: A see a few MXPE users in this thread have seen an update today as well.
Just checked and I'm now downloading the 8 MB update.
Yes I got it. It's just the Oct security update. It takes care of the wifi issue.
acejavelin said:
Thanks to user @NinjaBoyLao for the heads up... seems a new update is appearing on Moto X Pure, anybody else seeing it?
https://mobilesupport.lenovo.com/us/en/solution/MS124799
Screenshot attached.
EDIT: A see a few MXPE users in this thread have seen an update today as well.
Click to expand...
Click to collapse
Just got the notification here. I'm currently on 22 (Verizon). I'm rooted w/xposed so I can't take it without a full fastboot flash, but I downloaded it and extracted it. It's about 8mb. For other users, this is if you are on stock -22 and want to sideload the -25 ota from -22. I cannot confirm if this will work if you are on -23.
Blur_Version.25.11.22.clark_retus.retus.en.US: https://mega.nz/#!GR4yha5B!WT97ryQRKD8V0EkefLj6WHwUdTs3boMJea0D3e4ZSGY
autosurgeon said:
Yes I got it. It's just the Oct security update. It takes care of the wifi issue.
Click to expand...
Click to collapse
what wifi issue?
I'm rooted with just magisk and TWRP in my recovery partition, should I attempt to take this and/or capture it to verify the other capture?
jaysus145 said:
what wifi issue?
Click to expand...
Click to collapse
Pretty sure the user means the WiFi Vulnerability KRACK... https://www.krackattacks.com/
jaysus145 said:
what wifi issue?
Click to expand...
Click to collapse
KRACK is the issue it primarily addresses.
Can confirm, I just received the notification as well, USA on AT&T, no root but unlocked bootloader. I flashed to 25.200-22 manually.
I'm not sure how I should proceed if I plan on getting root and possibly lock bootloader again.
i did the update and my phone don't get out of the twrp screen. what i need to do now?
You cannot take updates if you are not completely stock. Yeesh it amazes me how few people root and fiddle without any idea what they are doing.
Got an update today. I returned to stock a while back to get nougat. I've had battery issues since even after factory reset. But I digress. Got this update today. I'm on Sprint.
Once we install this. Will there be any harm going back to .22? Have to say at least they are still pushing some updates out.
StankFiss said:
Once we install this. Will there be any harm going back to .22? Have to say at least they are still pushing some updates out.
Click to expand...
Click to collapse
Same rules apply as always... Downgrading is questionable at best, this seems to be a boot image update only though, since it is merely 8MB, so it should be possible to downgrade successfully but I don't think anyone has tried yet.
I received the update notification just now. Unfortunately I have TWRP and rooted with Magisk. I guess I'll have to wait for an OTA flashable zip.
annoyingduck said:
Just got the notification here. I'm currently on 22 (Verizon). I'm rooted w/xposed so I can't take it without a full fastboot flash, but I downloaded it and extracted it. It's about 8mb. For other users, this is if you are on stock -22 and want to sideload the -25 ota from -22. I cannot confirm if this will work if you are on -23.
Blur_Version.25.11.22.clark_retus.retus.en.US: https://mega.nz/#!GR4yha5B!WT97ryQRKD8V0EkefLj6WHwUdTs3boMJea0D3e4ZSGY
Click to expand...
Click to collapse
If I remember correctly, I can't just flash this via TWRP, correct? What are the fastboot flash commands for these files, or will I be better off waiting for someone to just upload a TWRP flashable version?
Thanks!
Just got an alert this morning. Not going to take it. Will wait for flashable file.
On Verizon and running .22 . Got the update message for 25.201.1. My phone has TWRP, SU root, a new logo.bin and Xposed.
I will be waiting for a flashable zip file. Any volunteers?
I wonder if there is any .23 goodness in this update such as newer radios for BT.
slicetwo said:
If I remember correctly, I can't just flash this via TWRP, correct? What are the fastboot flash commands for these files, or will I be better off waiting for someone to just upload a TWRP flashable version?
Thanks!
Click to expand...
Click to collapse
No TWRP. The file I provided is the actual OTA zip from Motorola. It will only apply from the stock recovery (side load) if you are on the -22 build unmodified. If your just stock with systemless root and left TWRP in read only mode, you could simply unroot, fastboot flash the stock recovery and then take the OTA. You would also have to fastboot flash any other modified partitions too from the -22 firmware (like if you changed the logo.bin). However, if your like me and are using the official N xposed or have allowed modifications in TWRP, you would need a full flash of the stock -22 firmware. In this case you could simply omit the bootloader lock, and data wipe commands and "dirty flash" the -22 firmware, take the OTA, and then re-root.
Note: I haven't had the time to do this yet. I cannot confirm if root/Xposed are working correctly on this -25 OTA, but I see no reason it wouldn't. I'm hoping I'll have time later to do it. I honestly don't care if there is some sort of failure, I'll be rocking a Pixel 2 soon. So I will be the guinea pig.
annoyingduck said:
No TWRP. The file I provided is the actual OTA zip from Motorola. It will only apply from the stock recovery (side load) if you are on the -22 build unmodified. If your just stock with systemless root and left TWRP in read only mode, you could simply unroot, fastboot flash the stock recovery and then take the OTA. You would also have to fastboot flash any other modified partitions too from the -22 firmware (like if you changed the logo.bin). However, if your like me and are using the official N xposed or have allowed modifications in TWRP, you would need a full flash of the stock -22 firmware. In this case you could simply omit the bootloader lock, and data wipe commands and "dirty flash" the -22 firmware, take the OTA, and then re-root.
Note: I haven't had the time to do this yet. I cannot confirm if root/Xposed are working correctly on this -25 OTA, but I see no reason it wouldn't. I'm hoping I'll have time later to do it. I honestly don't care if there is some sort of failure, I'll be rocking a Pixel 2 soon. So I will be the guinea pig.
Click to expand...
Click to collapse
Yeah... that's to much damn work. Haha. I am running Xposed and such. I'll just wait to see if someone makes a flashable file.