Related
Hey all,
I noticed many people seem to be having problems with the new OTA update (174.44.1 US). I also tried to update and my Moto G went into a bootloop. After much tinkering, I found a possible solution.
As far as I can tell, the update problems are caused by:
- Xposed modules like Gravitybox (not really sure why)
- Hacks like the H/H+ hack that replaces SystemUI.apk
- Any other mod that changes something in /system
This is what I did:
(Note that I have 4.4 Stock, rooted and PhilZ CWM recovery. Xposed, Gravitybox, H/H+ hack and Logo hack)
- Downloaded the zip from http://forum.xda-developers.com/showthread.php?t=2653978
- Placed it in the SD of the phone
- Unchecked all modules in Xposed and rebooted
- Rebooted again, this time into PhilZ and installed the update zip from the SD
It showed me an error with SystemUI.apk (and I remembered changing it for the H,H+ hack). So I went and restored the original.
Then I tried again. It went smoothly. And I still have root
Now I'm just waiting to see if the new SystemUI.apk is different from the old one before I restore the hack.
NOTE: For those who can't remember any/all changes made to /system, the stock system.img should be flashed in fastboot mode.
Hope this is useful...
(FIRST THREAD!:laugh
[UPDATE]: I have included my stock SystemUI.apk and .odex. Copy into /system/priv-app, overwrite existing files and set permissions to rw-r--r--.
All Xposed tweaks can be undone by unselecting the modules in the Xposed framework and rebooting.....before rebooting again into recovery..
UPDATE: Added the version of Philz recovery I use, for those with the "this package is for falcon_umts devices : this is a xt1034" error.
Extract into your fastboot folder and issue command:
fastboot flash recovery PhilZ.img
That should set all that straight...
When you say stock system.img do you mean system.img_sparsechunk1 2 and 3? Would I just flash them with fastboot flash system system.img? Would it wipe anything other than mods made in the system folder?
draco259 said:
When you say stock system.img do you mean system.img_sparsechunk1 2 and 3? Would I just flash them with fastboot flash system system.img? Would it wipe anything other than mods made in the system folder?
Click to expand...
Click to collapse
It will return the system folder to default. All changes should be reset, as far as I can tell...
secretkloud said:
Hey all,
I noticed many people seem to be having problems with the new OTA update (174.44.1 US). I also tried to update and my Moto G went into a bootloop. After much tinkering, I found a possible solution.
As far as I can tell, the update problems are caused by:
- Xposed modules like Gravitybox (not really sure why)
- Hacks like the H/H+ hack that replaces SystemUI.apk
- Any other mod that changes something in /system
This is what I did:
(Note that I have 4.4 Stock, rooted and PhilZ CWM recovery. Xposed, Gravitybox, H/H+ hack and Logo hack)
- Downloaded the zip from http://forum.xda-developers.com/showthread.php?t=2653978
- Placed it in the SD of the phone
- Unchecked all modules in Xposed and rebooted
- Rebooted again, this time into PhilZ and installed the update zip from the SD
It showed me an error with SystemUI.apk (and I remembered changing it for the H,H+ hack). So I went and restored the original.
Then I tried again. It went smoothly. And I still have root
Now I'm just waiting to see if the new SystemUI.apk is different from the old one before I restore the hack.
NOTE: For those who can't remember any/all changes made to /system, the stock system.img should be flashed in fastboot mode.
Hope this is useful...
(FIRST THREAD!:laugh
Click to expand...
Click to collapse
Hi can you include your original systemui.apk i lost mines >.<
serophia said:
Hi can you include your original systemui.apk i lost mines >.<
Click to expand...
Click to collapse
Added to first post...
secretkloud said:
Added to first post...
Click to expand...
Click to collapse
i restored recovery, disabled all mods, unrooted, and did a factory reset when i try to install update i get an "error" in stock recovery? Any other suggestions i should do?
EDIT: nvm fixed by flashing system.img adaway was the problem for me >.<
Error when in recovery
I downloaded the zip but when I go to CWM recovery and try to install it from the SD it shows me an error.
it says; This package is for "falcon_umts" devices; this is a xt1032.
any help?
Maybe you'll find the solution to your problem here.
thanks!!
mokkami said:
Maybe you'll find the solution to your problem here.
Click to expand...
Click to collapse
thanks dude, now I just gotta know how to change the recovery haha
Thanks
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
mdentener said:
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Why root??
OP says he kept root after update was applied??
Sent from my Nexus 7 using Tapatalk
mdentener said:
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Same thing for me!
Is this gonna be worked with the last update 176...
i have used ur system ui but i still get the error
serophia said:
i restored recovery, disabled all mods, unrooted, and did a factory reset when i try to install update i get an "error" in stock recovery? Any other suggestions i should do?
EDIT: nvm fixed by flashing system.img adaway was the problem for me >.<
Click to expand...
Click to collapse
Adaway modifies the "system/etc/hosts" file. It should also be disabled before updating.
irishpancake said:
QUOTE=mdentener;50672956]Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Why root??
OP says he kept root after update was applied??
Sent from my Nexus 7 using Tapatalk[/QUOTE]
I kept my root also after the update. Those mods were installed before the OTA and remained installed after. I only disabled xposed modules temporarily and changed CWM to Phil's CWM to install the OTA.
Sent from my Moto G using Tapatalk
Hi everyone. About a week ago I got the 4.4.3 update for my Nexus 5. I was on vacation than and had very poor wifi and very poor data connection so I could not download it. Once I got home, I got the notification that there was an update so I downloaded it and than it asked me to restart and install. My phone is rooted so it booted me into ClockWorkMod Recovery. I read on the bottom that it said "Signature verification failed" and than on the top it asked me if I want to install the untrusted zip file. I said yes I do want to install. So when I clicked yes, a bunch of stuff came up on the bottom including the file name for 4.4.3 and than after that it just said "installation aborted". I looked online for solutions and one person said to go into clockworkmod and navigate to the option for signature verification and make it disabled. I did that and booted into my phone and the update notification would not come. I went into my settings and into about phone and clicked on system updates but it just said that "your system is up to date". So I am still running 4.4.2 stock right now. I dont know if this matters but I do have xposed framework installed and I have gravitybox and snapshare modules loaded on. I have a lot of tweaks from gravitybox. Is there a way I can get the latest version of Android for my Nexus without having to go through this process. Thank you all.
Dirty flash vomer's stock 4.4.4 rom via recovery.
Thread link: http://forum.xda-developers.com/goo...t/rom-stock-4-4-3-ktu84m-odex-deodex-t2771010
next time, use search:
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
What he said ^ I would read how to do everything before unlocking bootloader/rooting. You simply uninstall xposed framework (if you still have stock kernel/radio) and flash the OTA update. then reinstall superSU and custom recovery. when you reinstall xposed all your settings are saved.
PsychDrummer said:
What he said ^ I would read how to do everything before unlocking bootloader/rooting. You simply uninstall xposed framework (if you still have stock kernel/radio) and flash the OTA update. then reinstall superSU and custom recovery. when you reinstall xposed all your settings are saved.
Click to expand...
Click to collapse
Ok so I uninstalled xposed framework and I restored my volume mod but I am still not getting the OTA update. I am on 4.4.2 right now so now I am going to flash the OTA zip file of 4.4.3 which is this one:
KTU84M from KOT49H -
http://android.clients.google.com/p...ed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
I want 4.4.3 right now since I am leaving town soon. Once I get 4.4.3, should I go ahead and install 4.4.4 or just wait for the OTA update
maxell505 said:
Ok so I uninstalled xposed framework and I restored my volume mod but I am still not getting the OTA update. I am on 4.4.2 right now so now I am going to flash the OTA zip file of 4.4.3 which is this one:
KTU84M from KOT49H -
http://android.clients.google.com/p...ed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
I want 4.4.3 right now since I am leaving town soon. Once I get 4.4.3, should I go ahead and install 4.4.4 or just wait for the OTA update
Click to expand...
Click to collapse
ok I tried doing it but it said there was an error in the file and the installation was aborted. Please help somebody!!!
maxell505 said:
ok I tried doing it but it said there was an error in the file and the installation was aborted. Please help somebody!!!
Click to expand...
Click to collapse
go read this: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
maxell505 said:
Ok so I uninstalled xposed framework and I restored my volume mod but I am still not getting the OTA update. I am on 4.4.2 right now so now I am going to flash the OTA zip file of 4.4.3 which is this one:
KTU84M from KOT49H -
http://android.clients.google.com/p...ed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
I want 4.4.3 right now since I am leaving town soon. Once I get 4.4.3, should I go ahead and install 4.4.4 or just wait for the OTA update
Click to expand...
Click to collapse
You can flash KTU84M and if it succeeds then wait for the OTA or again flash KTU84P to get to 4.4.4
OR
Just dirty flash vomer's stock 4.4.4 rom which will bump you up to 4.4.4. It's up to you to decide.
vin4yak said:
You can flash KTU84M and if it succeeds then wait for the OTA or again flash KTU84P to get to 4.4.4
OR
Just dirty flash vomer's stock 4.4.4 rom which will bump you up to 4.4.4. It's up to you to decide.
Click to expand...
Click to collapse
ok if i dirty flash vomer's stock 4.4.4 rom, I will be completely stock than right. Like after that I will recieve normal OTA's from Google right??
maxell505 said:
ok if i dirty flash vomer's stock 4.4.4 rom, I will be completely stock than right. Like after that I will recieve normal OTA's from Google right??
Click to expand...
Click to collapse
Yes Sir. If you don't want root access, simply remove it afterwards.
vin4yak said:
Yes Sir. If you don't want root access, simply remove it afterwards.
Click to expand...
Click to collapse
Ok so I successfully upgraded to 4.4.4. There is one problem though. When I click on the SuperSu app, it says "there is no SuperSU binary installed, and SuperSU cannot install it. This is a big problem!"
maxell505 said:
Ok so I successfully upgraded to 4.4.4. There is one problem though. When I click on the SuperSu app, it says "there is no SuperSU binary installed, and SuperSU cannot install it. This is a big problem!"
Click to expand...
Click to collapse
Flash the supersu zip from that thread or download the latest supersu by chainfire and flash it.
- Sent from an IceCold Hammerhead!
hi guys !
i have a nexus 5 with version 6.0.1 rooted with TWRP recovery
i got an OTA update its size about 8 MB, when i try to install it, the phone booting with TWRP and got the error attached
Chouiyekh said:
hi guys !
i have a nexus 5 with version 6.0.1 rooted with TWRP recovery
i got an OTA update its size about 8 MB, when i try to install it, the phone booting with TWRP and got the error attached
Click to expand...
Click to collapse
Read what the error is telling you. It expects x and you have y.
wangdaning said:
Read what the error is telling you. It expects x and you have y.
Click to expand...
Click to collapse
my phone running 6.0.1 not 5.0.2, anyway what is the solution ?
Ota updates can only be installed on an unrooted system with stock recovery unless the ota update has been compiled for flashi via twrp.
It is asking for google and you have omni.
wangdaning said:
Read what the error is telling you. It expects x and you have y.
Click to expand...
Click to collapse
audit13 said:
Ota updates can only be installed on an unrooted system with stock recovery unless the ota update has been compiled for flashi via twrp.
Click to expand...
Click to collapse
so, is there a way to install this ota update manually, without unroot the phone and wipe twrp recovery ?
Why would you install a Google OTA when you are obviously running a custom ROM?
Wait for the developer of that to update, or revert back to stock.
In January I installed SuperSU 2.6.2-3 in accordance with this forum. Interestingly, today I received notification from the Playstore to update SuperSU to 2.65 (dtd Feb 01, 2016). I don't know why I received this notification from the Playstore since I did not install from there and did not receive this notification much earlier. Also, I assume updating to 2.65 through the Playstore would not be a good idea.
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Funcionando en Moto g 2015 xt1543 México [MM]
Probé la actualización y todo bien ? OK
TVD1903 said:
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Click to expand...
Click to collapse
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
MrTooPhone said:
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
Click to expand...
Click to collapse
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
TVD1903 said:
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
Click to expand...
Click to collapse
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
MrTooPhone said:
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
Click to expand...
Click to collapse
I am using a Custom ROM with SuperSU built-in. I have however also used the Stock ROM with SuperSU v2.65, installed using TWRP.
Got the same notification, updated fine, updated also su binaries (asked by the app) and - everything works fine. Stock 6.0.
Well I was reluctant to try based on my first experience flashing 2.65. But I accepted the update via Playstore, SuperSU updated the binaries, rebooted, and all is still good.
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
MrTooPhone said:
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
Click to expand...
Click to collapse
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
pjc123 said:
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
Click to expand...
Click to collapse
I have had no issues backing up with twrp-osprey-3.0.0-r2.img. I have not tried restoring yet.
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
don'tn worry ... the update works perfectly ...
..::Matr!x::.. said:
don'tn worry ... the update works perfectly ...
Click to expand...
Click to collapse
Thanks.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
I have received several updates since 2.62-3. All have installed from playstore just fine including 2.79. As an initial installation, I think 2.62-3 was the only one that installed as systemless without forcing a systemless installation. Once you have a successful installation, all updates should be as well.
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
mirpuri said:
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I followed these directions eleven months ago for the initial unlock bootloader, TWRP recovery and root, using the versions of SuperSU and TWRP listed, however I did not install Xposed.
http://forum.xda-developers.com/201...twrp-root-xposed-t3294588:confused::confused:
I have since updated to:
SuperSU 2.79
TWRP 3.0.2-r1
Caveat: My phone is a XT1540.
Hey all
So a while back I wanted to use a certain app on my Motorola One Hyper that required root privileges, so I rooted my phone using Magisk for it. I didn't need the app later so I unrooted my phone, but now when I try to update my phone to a newer version, I get an error message saying "Package verification failed. The update package being downloaded is not compatible with the current software version on the device".
I'm not sure if me rooting the device has anything to do with it or not, but I'm guessing it is since I never had this issue before the root. Any way to fix this? Thanks in advance!
BlobTea said:
Hey all
So a while back I wanted to use a certain app on my Motorola One Hyper that required root privileges, so I rooted my phone using Magisk for it. I didn't need the app later so I unrooted my phone, but now when I try to update my phone to a newer version, I get an error message saying "Package verification failed. The update package being downloaded is not compatible with the current software version on the device".
I'm not sure if me rooting the device has anything to do with it or not, but I'm guessing it is since I never had this issue before the root. Any way to fix this? Thanks in advance!
Click to expand...
Click to collapse
Yes, it probably is the root.
If you are trying to update the stock rom, it probably will not work. You may have to manually flash the stock rom again. Then, you may be able to upgrade to android 11. Otherwise you can just manually install android 11.
RVR said:
Yes, it probably is the root.
If you are trying to update the stock rom, it probably will not work. You may have to manually flash the stock rom again. Then, you may be able to upgrade to android 11. Otherwise you can just manually install android 11.
Click to expand...
Click to collapse
Ahh gotcha. Looks like I'm gonna have to flash the stock rom then. Thanks a lot for your help!
Does having a SafetyNet fix have something to do with it? Maybe unrelated, maybe not but when I check off the software update on the Magisk DenyList, exit and then come back, it becomes unchecked and I don't know why. Perhaps if the OTA updates werent detecting root, I could update to a security patch.
BlobTea said:
Ahh gotcha. Looks like I'm gonna have to flash the stock rom then. Thanks a lot for your help!
Click to expand...
Click to collapse
Stock updates usually can't be applied to rooted devices or devices with custom recovery, root has to be completely removed and stock recovery has to be reinstalled. If those aren't corrected before applying the update, it will fail because it checks the system partition for modifications and requires stock recovery to apply the update, whether it actually boots into recovery or not during the update process.