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
Related
i would like to install the latest OTA update for 4.4.2 but it keeps failing.
i flashed stock recovery and i have stock kernel.
when i apply the update it just states that the update was unsuccessful.
any idea on how to solve this? i have tesco moto g on which i flashed stock UK firmware. it is only rooted. i do not think that i have deleted system apps and i tryed disabling xposed modules.
could someone make a flashable zip if it is possile?
i would really appreciate it :victory:
I use the latest TWRP as my recovery and it updates the OTA files fine, so I would suggest trying that.
Atomix86 said:
I use the latest TWRP as my recovery and it updates the OTA files fine, so I would suggest trying that.
Click to expand...
Click to collapse
i installed TWRP and disabled all xposed modules. the update went fine. the only thing is when it booted i got: an unexpected error has occured. please try again later.
should i worry about it? system version is now 176.44.1.
ManBearrrPig said:
i installed TWRP and disabled all xposed modules. the update went fine. the only thing is when it booted i got: an unexpected error has occured. please try again later.
should i worry about it? system version is now 176.44.1.
Click to expand...
Click to collapse
I didn't get that error so I can't answer that I'm afraid, sorry.
Sent from my Google Nexus G -
Hello,
Today i tried to install the Update for my Moto G. But after the download i get an Error Message.
How can i fix that?( My phone is Unlocked and Rooted).
same problem.
after the update failed (in the log):
...systemui.apk has unexpected contents
i think i need the original systemui.apk
version 176.44.1 en.DE Retail
but have no backup
- Moto G 8GB / DE Retail / unlocked / Rooted / Xposed / Softkeyz -
I use SoftkeyZ too but i have the backup. German Version too.
Sent from my XT1032 using XDA Free mobile app
Can it be that the update does not work on rooted phones?
On my rooted Moto it does not work unfortunately.
Why they say "Update available" if its not working?
Well with my buddy be the phone not rooted the update worked fine, so my guess
Do you have xposed installed or something like that? Or modified a System APK?
Busybox before a while. I did, however, completely uninstalled.
So my phone is only rootet
ok, I don't want to unroot my phone because I need to uninstall busybox and xposed so I don't make the Update.
mm.chrs said:
same problem.
after the update failed (in the log):
...systemui.apk has unexpected contents
i think i need the original systemui.apk
version 176.44.1 en.DE Retail
but have no backup
- Moto G 8GB / DE Retail / unlocked / Rooted / Xposed / Softkeyz -
Click to expand...
Click to collapse
Here you go. It's not flashable and includes apk and odex.
Hurriname said:
ok, I don't want to unroot my phone because I need to uninstall busybox and xposed so I don't make the Update.
Click to expand...
Click to collapse
I have root, busybox and xposed. Updated nicely.
Bec de Xorbin said:
Here you go. It's not flashable and includes apk and odex.
Click to expand...
Click to collapse
NICE...
Replaced the Files...
and it works...
Sorry for noob question.
how you replace it just copied or with adb?
slevin71 said:
Sorry for noob question.
how you replace it just copied or with adb?
Click to expand...
Click to collapse
i use root-explorer.
-make a copy of systemui.apk und systemui.odex
-copy new files
-chmod (File Permissions)
-reboot
-update
I'd suggest if you are performing a STOCK OTA update then safest way is to get back to STOCK 4.4.2 ROM first via fastboot commands (Unrooted status) and perform the OTA update.
==vj== said:
I'd suggest if you are performing a STOCK OTA update then safest way is to get back to STOCK 4.4.2 ROM first via fastboot commands (Unrooted status) and perform the OTA update.
Click to expand...
Click to collapse
Or restore the files you have modified. That's not any less "safe".
mm.chrs said:
same problem.
after the update failed (in the log):
...systemui.apk has unexpected contents
i think i need the original systemui.apk
version 176.44.1 en.DE Retail
but have no backup
- Moto G 8GB / DE Retail / unlocked / Rooted / Xposed / Softkeyz -
Click to expand...
Click to collapse
How did you get the log?
Sent from my XT1032 using XDA Free mobile app
SOLUTION
Hi,
I solved my fail to update so wanted to share for others. I spent trying for 3 hrs...
my phone is rooted, Xposed framework, unlocked with code from Tesco UK, 16 gb 3G model, stock UK Tesco rom = no kernel changes!
1)You need to flash a 'stock recovery' BUT do NOT use the recovery.img from the tool called 'MOTOtools All in One' it will not work, but the tool is good for flashing without any coding.
Download the latest Stock ROM for your phone model, and extract the Recovery.img. Flash it using MotoTools (you have to be in fastboot, right after flashing you should not see any error message on the phone, go to recovery right after flashing (NO reboots!!).
You will see a droid with 'No command' message after a long black screen, let it be like that for a few mins or you can hold down power button to force a reboot. Now you are ready to update OTA!
Hit thanks if this solved your problem.
Cheers,
Hurriname said:
How did you get the log?
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
after the update failed, you can view the temp. log in /cache
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
No luck here...there is post over on Android Forums that Verizon users are getting the 4.4.4 OTA update but nobody has posted the captured zip file yet.
Captured Verizon CDMA Moto G 4.4.4 Update Zip
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
netkeys said:
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.
judask24 said:
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.
Click to expand...
Click to collapse
This is the file downloaded on 7-21-2014. Attached is a screen shot of the updater.
netkeys said:
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?
chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
It was pulled from the /cache folder. If you put in /storage/sdcard0 you may also need to rename to update.zip
randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
Yes please do. My wife's phone is wanting to update since Sunday night.
Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.
chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
I think you can select "apply update from sdcard" in the recovery mode. No?
EDIT: You flashed to PagePlus. I missed that part. Sorry about that.
I was on a AOSP based rom.
So I flashed back to stock via CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.
Booted up once to make sure the the flash went well.
Flashed CWM via bootloader. Tried TWRP first, did not work with the update.zip.
Renamed the zip above to update.zip and flashed via cwm. Worked fine. (yes the zip is 4.4.4)
Before rebooting, went ahead and flashed supersu.zip.
Then rebooted back to bootloader and flashed my preferred recovery, TWRP.
All seems well. This is on PagePlus.
Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.
XDA Dark said:
Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.
Click to expand...
Click to collapse
It sounds like the 4.4.4 update is working fine...the only issue is that there doesn't seem to be a full stock 4.4.4 flash available (like we have for 4.4.2), and from what I can tell from posts (haven't tried this myself), you cannot reflash the full stock 4.4.2 after the 4.4.4 update since the bootloader and/or partitions have changed. There may be some workarounds, but those seem to be for other models or geographies as best I can tell. Once we have the full 4.4.4 flash, then at least you can always revert to that, but it doesn't appear to be released yet.
I've been keeping an eye out for the update OTA. I guess I'd rather just go down that path officially since my phones not rooted and had stock locked bootloader. Just wish it would hurry up and be pushed to my device.
Install zip via stock recovery
judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
Ota file works it is 4.4.4 update for Verizon Mota G. Download zip to phone power off. Hold down power and volume down for a few seconds release. Once at menu go to recovery. Once in recovery android with exclamation with no options will appear. Press and hold Volume up for 10 seconds continue to hold while now also pressing power button for 3 seconds release. Your in recovery mode select update from zip and proceed. Happy camping with new dialer update camera shots in low lightness and other fixes and features!
randomchaos26 said:
Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.
Click to expand...
Click to collapse
Followed these directions and worked without any problem.
The fixed the external USB mounting problem that was in 4.4.2
I updated today on Boost Mobile Moto G flashed to Page Plus with no issues... Success
Sent from my XT1028 using XDA Free mobile app
randomchaos26 said:
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
Click to expand...
Click to collapse
Thanks for the instruction. Questions:
(1) My flashed page plus moto-g is on rooted stock rom (with unlocked bootloader of course). Do I still need to restore the system partition back to stock?
(2) What is "CFC-fastboot"? Do you mean
fastboot falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip
(i.e. no underscore between fastboot and falcon) ?
Thanks!
it's available on OTA now yay
I flashed the following factory firmware image on my XT1541;
Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7
from here and followed the steps on this page to do so.
I updated to MM through OTA, flashed TWRP from here through fastboot, booted in to TWRP and flashed SuperSU v.2.65 from here.
I then reboot the phone and it gets stuck on the white "unlocked bootloader" screen.
I've repeated this process twice now, same thing. :/
Any ideas?
EDIT: I tryed flashing factory 5.1.1 through fastboot again, to get the phone working. But now I can't even do that.
When I enter "fastboot flash partition gpt.bin" I get the following error;
(bootloader) Preflash validation failed
FAILED (remote failure)
If you have a twrp backup from marshmallow, restore system. Then flash superSU 2.62-3 from here http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip.
SuperSU 2.65 don't detect properly the need to install it in systemless mode and try to install in system. V.2.62 is only systemless.
If you don't have the system backup, I don't know how to revert the modifications made by v. 2.65, but it's possible.
Good luck.
coolizard said:
If you have a twrp backup from marshmallow, restore system. Then flash superSU 2.62-3 from here http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip.
SuperSU 2.65 don't detect properly the need to install it in systemless mode and try to install in system. V.2.62 is only systemless.
If you don't have the system backup, I don't know how to revert the modifications made by v. 2.65, but it's possible.
Good luck.
Click to expand...
Click to collapse
Thank you. I did not have a backup, but I was able to flash factory 5.1.1 by skipping gpt.bin.
I then updated to MM through OTA, flashed TWRP and SuperSU v2.62-3.
Is there a reason why later versions of SuperSU do not install systemless on our phone and therefor cause the bootloop?
coolizard said:
If you have a twrp backup from marshmallow, restore system. Then flash superSU 2.62-3 from here http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip.
SuperSU 2.65 don't detect properly the need to install it in systemless mode and try to install in system. V.2.62 is only systemless.
If you don't have the system backup, I don't know how to revert the modifications made by v. 2.65, but it's possible.
Good luck.
Click to expand...
Click to collapse
I had a similar experience with v2.65. I know systemless root is experimental and all the current versions are beta. But I don't understand the reports from others indicating 2.65/2.65/2.67 work just fine on their G3. Is it possible that once 2.62-3 is installed, the later versions will flash properly?
Flash this supersu file , it will remove all latest binaries of supersu. And your phone will start.
https://download.chainfire.eu/204/SuperSU
Then flash supersu2.63 to root.
Astug said:
I flashed the following factory firmware image on my XT1541;
Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7
I updated to MM through OTA
Click to expand...
Click to collapse
Where did you find OTA for XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7? I've flashed this factory image but I haven't received OTA for this build and I haven't found an OTA file on Internet.
Could you share the OTA that you've used?
Osid said:
Where did you find OTA for XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7? I've flashed this factory image but I haven't received OTA for this build and I haven't found an OTA file on Internet.
Could you share the OTA that you've used?
Click to expand...
Click to collapse
Here.
I received the OTA on my phone though.
Astug said:
Here.
I received the OTA on my phone though.
Click to expand...
Click to collapse
The thread linked contains only MY OTA for XT1541 2GB.
Are you really sure that tour source build was LPI23-72.33 ?
Your warranty is now void, don't blame me if your phone blows up blahblahblah.
Only system and kernel are being flashed, no Modem, BL, etc. You should already have updated to 20B before using.
Have not tested this myself, due to not owning the H850. edit: flashed it on T-Mobile 830 for fun with 20A 830 boot, no surprise, didn't work.
Decided to post anyway. If your going to use it, BACKUP, BACKUP, BACKUP
Based off of H85020b_00_TIM_IT_OP_1123.kdz
Only things touched are bootanimation (pixel black) and renamed recovery-from-boot.bak. It's also been zip-aligned.
Flash in recovery, profit??
SuperSu and Busybox included. Only /system is wiped, data left alone.
Should be able to dirty flash over current 20B if you like.
Any errors, etc, would most likely be related to deodexing as all files are stock.-Again, haven't tested this one myself
Link: H850_20B_DeOdexed
MD5: 99c9667294d1227de91605b8958233e0
If anyone would like to use this as a base, Great! Would appreciate some credit. [emoji13]
Enjoy.
Optional: Adjust Screen Color
Credits: @Chainfire for supersu. @SuperR. for the kitchen. @PlayerZ_ZawZaw for bootanimation. @jcadduono for TWRP. @bullghost for Firmware Extractor
It's people like them that make Android great!
Finally, thanks to Google/LG & XDA.
...whew.
Reserved
Great work Bro, nice. :good:
A couple questions 1. Isn't 20B just a security patch update? 2. Does this ROM zip upgrade firmware (bootloader , radio, recovery) or just update software. 3. Since it's based off of the Italian H850 variant this won't cause troubles for EU variant?
xlxcrossing said:
A couple questions 1. Isn't 20B just a security patch update? 2. Does this ROM zip upgrade firmware (bootloader , radio, recovery) or just update software. 3. Since it's based off of the Italian H850 variant this won't cause troubles for EU variant?
Click to expand...
Click to collapse
1. Not 100% sure. 2. Just system and kernel are flashed. No M/BL, etc. 3. No idea really.
Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation - same here with the 20B version
Mr. Schnabel said:
Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation - same here with the 20B version
Click to expand...
Click to collapse
Hmmm flashed ok on my h830(swapped kernel), wouldnt boot (of course, this is for 850), but still flashed. Not sure why your getting that error, already removed the assert.
lordodin912 said:
Hmmm flashed ok on my h830(swapped kernel), wouldnt boot (of course, this is for 850), but still flashed. Not sure why your getting that error, already removed the assert.
Click to expand...
Click to collapse
Same error... Keep at it tho, something like this could be really useful
If anyone wants to try this themselves here's a quick guide.
You can take the system.img and boot.img from either the kdz with LG Firmware Extractor or from autoprime complete zip.
Then Google "superR kitchen xda", if your using windows there is a VM iso in the thread you can use with VirtualBox etc.
Once you have the kitchen working just remember, set_metadata for perm, use smali/baksmali for deodexing and don't sign the zip or let it remove the meta-inf folders from apps.
In my h850 doesn't finish to install, it remains on initial boot animation.
failax said:
In my h850 doesn't finish to install, it remains on initial boot animation.
Click to expand...
Click to collapse
Flashed ok but stuck on LG logo? May need to flash no verify or "format data" in TWRP. BACKUP everything if formatting.
Ok so I just clean flashed my 20a for h830 and got that error code 7, doesn't happen on dirty. Just restarted TWRP after wiping and then it flashed ok. Might be the same problem over here.