Database Info

OTA upgrade for rooted 4.3

I'm trying to apply the OTA upgrade to my rooted UK Retail Moto G running 4.3. The upgrade keeps failing, even if I disable root using the option in SuperSU. Is there some step I am missing out, or must I use a clean flash and lose all my configuration? (The phone was rooted using the superboot method, and had Xposed framework, but this had been removed using the Xposed framework app.) Thanks.

What exactly does fail?
There should be an error message when you try to flash the OTA.
Look at the screen and report back, the boot.img you flashed to get root on your phone shouldn't have any impact on the update procedure.

CassandraN said:
I'm trying to apply the OTA upgrade to my rooted UK Retail Moto G running 4.3. The upgrade keeps failing, even if I disable root using the option in SuperSU. Is there some step I am missing out, or must I use a clean flash and lose all my configuration? (The phone was rooted using the superboot method, and had Xposed framework, but this had been removed using the Xposed framework app.) Thanks.
Click to expand...
Click to collapse
I am in the exact same situation i unrooted and uninstalled xposed and it fails shortly after the progress bar appears i tried twice and same in gonna flash the boot.img and recovery.img out of the factory img later and try again.

Same here I removed root update downloads then install fails It don't tell you why it failed.
Sent from my XT1032 using XDA Premium 4 mobile app
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
I spoke to Motorola and she said I may not be able to update if my bootloader is unlocked
Sent from my XT1032 using XDA Premium 4 mobile app

+1 Phone downloads the update. Restarts and gives "error". Phone is unlocked and rooted.

You either have to restore all the stock things you modified - boot / recovery OR save the OTA, flash stock and put the OTA again into the sdcard, restart and voila

darkeingel said:
You either have to restore all the stock things you modified - boot / recovery OR save the OTA, flash stock and put the OTA again into the sdcard, restart and voila
Click to expand...
Click to collapse
Do you know where i can find the "14.71.8.falcon_umts.Retail.en.GB" file to restore my uk moto G to stock without root?
I can find only the US retail files in android dev section.
PS: thanks found it

deadpunk said:
Do you know where i can find the "14.71.8.falcon_umts.Retail.en.GB" file to restore my uk moto G to stock without root?
I can find only the US retail files in android dev section.
PS: thanks found it
Click to expand...
Click to collapse
I used pauls root method 2 to root with a modified recovery i bet that's why it fails the update ill post my findings later after i flash unmodified stock recovery for anyone who's situation is the same as mine.

Skinpipe said:
I used pauls root method 2 to root with a modified recovery i bet that's why it fails the update ill post my findings later after i flash unmodified stock recovery for anyone who's situation is the same as mine.
Click to expand...
Click to collapse
I had to use method 2 to root too, and mine is also failing to update... :/ keep us informed!
xTx

darkeingel said:
You either have to restore all the stock things you modified - boot / recovery OR save the OTA, flash stock and put the OTA again into the sdcard, restart and voila
Click to expand...
Click to collapse
Well I've been able to reverse everything but the original superboot root itself. Does anyone know how that might be reversed?

CassandraN said:
Well I've been able to reverse everything but the original superboot root itself. Does anyone know how that might be reversed?
Click to expand...
Click to collapse
Flashing the boot.img from a stock firmware - from the specific firmware that you are running now even.

darkeingel said:
Flashing the boot.img from a stock firmware - from the specific firmware that you are running now even.
Click to expand...
Click to collapse
boot.img is the kernel, you only need to flash back a stock kernel if you have flashed a custom one earlier.
The superboot method does not alter the kernel, it just does some magic one-time boot that roots the phone (ie alters files in /system). You still have the original kernel in place. superboot just flashes superSU. superSU is the app itself plus certain /system file addtions and alterations.
To remove root all the /system files that rooting updates must be set back to how they were, the updater does a checksum on the files and if they differ from what they should be then the update fails.
superSU for example modifies /system/etc/install-recovery.sh as well as adding new files to /system. So /system/etc/install-recovery.sh would need to be put back to how it was.
Depending on which files the superboot method uses will depend on which files need altering back.
In general you are going to want to flash back stock /system as thats easiest (or maybe you did a nandroid and can restore /system from that).

ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx

tee_pot said:
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
Click to expand...
Click to collapse
Thats good. So SuperSU basically cleans itself up and reverts all /system files it changed back to their original values. Easier than restoring a stock /system.

CassandraN said:
Well I've been able to reverse everything but the original superboot root itself. Does anyone know how that might be reversed?
Click to expand...
Click to collapse
Unroot using the supersu app if that's what you mean you cant do

tee_pot said:
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
Click to expand...
Click to collapse
Same thing here. Uk retail Moto G 8Gb, restore back to 4.3 stock, copy the OTA to sdcard and go to system update...
Phone will ask to copy OTA, just tap yes and install now...

Skinpipe said:
Unroot using the supersu app if that's what you mean you cant do
Click to expand...
Click to collapse
Yes you can, superSU has an 'unroot' option. On another thread Im sure someone had issues with it as it left some junk lying behind, but for the poster in this thread it seems to have worked fine.
---------- Post added at 01:15 PM ---------- Previous post was at 01:10 PM ----------
deadpunk said:
Same thing here. Uk retail Moto G 8Gb, restore back to 4.3 stock, copy the OTA to sdcard and go to system update...
Phone will ask to copy OTA, just tap yes and install now...
Click to expand...
Click to collapse
if you restore entirely back to stock, ie stock recovery as well, then waiting for the OTA to download the 'offical' way may be better. This will then update not just Android but your stock recovery as well. Im unsure if installing from the sdcard updates the radios (ie mobile radios) or not. If not then again installing the officiall way may be better.
If someone on here knows if the mobile radios get updated I'd like to know. I see many /modem files in the update.zip. Its these Im interested in whether they get flashed or not when using the sdcard method.

rooted 4.4.2 now working:
followed the guide http://forum.xda-developers.com/showthread.php?t=2563599&highlight=mismatched to install CWM recovery
downloaded the latest SuperSU from http://download.chainfire.eu/376/SuperSU/ , copied to root of the sdcard and installed using CWM
titanium backup (free version) worked a charm, only thing it seems it didn't backup was my live wallpaper choice! bit of a pain to have to click "install" and "done" on each app (all 181 of them!) but much quicker than reinstalling and setting them up again from the Play store
now to have a play with my new kitkat!
xTx
EDIT: incidentally, where does it show what bootloader is being used? can't see anything in phone settings or fastboot...

tee_pot said:
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
Click to expand...
Click to collapse
do any of these steps wipe data and/or apps?
cause I'd like to avoid that but disabling superuser from app doesn't fix the problems of the update failing

-sandro- said:
do any of these steps wipe data and/or apps?
cause I'd like to avoid that but disabling superuser from app doesn't fix the problems of the update failing
Click to expand...
Click to collapse
Are you just disabling superSU or are you actually choosing the option to unroot, ie the option in superSU that says:
Full unroot
Cleanup for permanent unroot
If you do this is should remove root and put all /system files back as they were (ie the ones it altered during root).
Also I assume you have not modifed any system apps yourself, eg installed newer versions etc or removed any? If you have then again the update wont work. The update checks lots of files to ensure they have not been modified before it does the update.

Updating Nexus 5

Hello,
I have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.

Start here, then still questions in that thread
http://forum.xda-developers.com/showthread.php?p=69234
Sent from my Nexus 5 using XDA Free mobile app

Hello,
Thanks for your reply. I can't access your link though.

D5R said:
Hello,
Thanks for your reply. I can't access your link though.
Click to expand...
Click to collapse
Something is goofed up with xda. It's the ota help in the general forum. Look for it there. Should have everything you need
Sent from my Nexus 5 using XDA Free mobile app

D5R said:
Hello,
Thanks for your reply. I can't access your link though.
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217

D5R said:
Hello,
I have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.
Click to expand...
Click to collapse
First thing, turn off mobile data. Your phone may try re-download it over and over again and use up your mobile data plan.
To install the ota via the ota update on the stock rom you will need to return to stock recovery and maybe stock kernel (not sure about this one).
NOTE: Before trying the below steps as I haven't tested them myself, please backup your ROM first. Better safe than sorry.
You can try installing the OTA updates manually from TWRP. You can find the links in the post - http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327.
If you are running 4.4.2 KRT16M you will need to download three updates.
1. KTU84M from KOT49H (4.4.2 update to 4.4.3)
2.KTU84P from KTU84M (4.4.3 update to 4.4.4)
Download them together and also put on a flashable zip of TWRP in the same location as it looks like it will reinstall the stock recovery.
You can even put on one of Franco kernel just in case too.
In TWRP select install zip and install number 1 first, then install 2. and finally install TWRP again. You should be updated to 4.4.4.
You can then install Franco kernel again just in case.
I hope this makes it easier.
EDIT: follow the link in the previous post as it has different scenarios and the steps needed.

Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes and/or kernel, reboot into recovery, flash the OTA , boot to bootloader, connect to pc, fastboot flash recovery, reboot into recovery, flash supersu.
Rooted stock = reboot into recovery, flash the ROM.
No brainer really. Flashing an OTA if rooted is a fool's errand.
Sent from my Nexus 5 using Tapatalk

[Q] Move from CM11 (JBBL) to CM12 (KKBL)

Apologies if this has been asked before but I can't seem to find the answer. I've read this post but it seems more complicated than it needs to be...
I've got an unlocked, rooted xt925.
I'm on CM11 JBBL nightlies (with CWM Recovery) and I want to move to CM12, which I believe means I need to revert from JBBL to KKBL first.
Is that correct?
If so, can I just download the KKBL firmware and flash it? Or do I have to use some other process? I'm on a Mac so I can't use PC-based tools (although I can use adb etc).
And where can I download KBBL from?? And will I lose root?
Thanks...

SamuriHL is the man. He has an updated HoM 4.1 that makes it somewhat easier, but it still involves flashing the FXZ, setting up custom recovery, re-rooting, etc... He has MAC "notes" in the thread, Im not sure if I can link the other forum its on, but f you google house of mot 4.1, it is (or was in my case) the first result
I was on the JBBL and 5.0.2 Validus ROM, but upgraded my BL to KK yesterday and Im running CM 12. So far I am loving it.

updated bootloader
jlang11 said:
SamuriHL is the man. He has an updated HoM 4.1 that makes it somewhat easier, but it still involves flashing the FXZ, setting up custom recovery, re-rooting, etc... He has MAC "notes" in the thread, Im not sure if I can link the other forum its on, but f you google house of mot 4.1, it is (or was in my case) the first result
I was on the JBBL and 5.0.2 Validus ROM, but upgraded my BL to KK yesterday and Im running CM 12. So far I am loving it.
Click to expand...
Click to collapse
Could you please tell me, what KK bootloader you are using now? I'm still not able to get CM 12. "...needs bootloader 4.4..."

xMandy said:
Could you please tell me, what KK bootloader you are using now? I'm still not able to get CM 12. "...needs bootloader 4.4..."
Click to expand...
Click to collapse
What I suggest as it worked for me, find SamuriHL's House of Moto 4.1, follow the directions to a T, as he says read, read, and read again, and use the firmware (FXZ) XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml. The bootloader kernel is 3.4 that was upgraded on our phones with that version of the firmware. Do a google search for House of Moto 4.1 and it should be easy to find.

XT925 or XT926
jlang11 said:
What I suggest as it worked for me, find SamuriHL's House of Moto 4.1, follow the directions to a T, as he says read, read, and read again, and use the firmware (FXZ) XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml. The bootloader kernel is 3.4 that was upgraded on our phones with that version of the firmware. Do a google search for House of Moto 4.1 and it should be easy to find.
Click to expand...
Click to collapse
thanks so far!
But why are you using a XT926-FXZ and not some for the XT925?
Any hint how to find out which one is the one I should use? ADB says "vanquish_u"... :silly:
...still trying...

xMandy said:
thanks so far!
But why are you using a XT926-FXZ and not some for the XT925?
Any hint how to find out which one is the one I should use? ADB says "vanquish_u"... :silly:
...still trying...
Click to expand...
Click to collapse
Because I have the xt926
If you have xt925, then make sure you use the correct firmware for your phone...

Hey guys, i'm trying the same, and i don't get it working.
Phone is an unlocked xt925.
Could upgradeto KKBL but now nothing works to get cm12 working, always get bootloops...

virgin xt925
jlang11 said:
Because I have the xt926
If you have xt925, then make sure you use the correct firmware for your phone...
Click to expand...
Click to collapse
as far as I see, the House of Moto does the same as RSD lite - it brings the RAZR back to "a minty factory fresh state" - means 4.1.2. with JBBL.
After that you did the OTA update to 4.4.2.? Is this the trick to get KKBL? Trying to use twrp didn't work for me (still on 4.1.2), the screen was frozen, no touch, no reaction. . .
Didn't get to 4.4.2 so far or was not able to flash a recovery that supports CM 12. :crying:
It would be great if you will share your secret :fingers-crossed:
thx

xMandy said:
as far as I see, the House of Moto does the same as RSD lite - it brings the RAZR back to "a minty factory fresh state" - means 4.1.2. with JBBL.
After that you did the OTA update to 4.4.2.? Is this the trick to get KKBL? Trying to use twrp didn't work for me (still on 4.1.2), the screen was frozen, no touch, no reaction. . .
Didn't get to 4.4.2 so far or was not able to flash a recovery that supports CM 12. :crying:
It would be great if you will share your secret :fingers-crossed:
thx
Click to expand...
Click to collapse
As far as HoM being the same as RSD lite, it mat very well be similar. If you are familiar with RSD by all means use that utility. SamuriHL wrote the scripts for flashing FXZ's and worked hard at making it easy for "n00bs" like myself to upgrade their phones.
As far as flashing back to "minty factory fresh" state, if you are flashing the correct FXZ, you are not flashing 4.1.2, you would be flashing 4.4.2 (see previous post mentioning XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml) so no you are not OTA to 4.4.2. The 4.4.2 FXZ HAS the KKBL.
All this is assuming you are already UNLOCKED.
I am in NO WAY an expert, and actually I am a n00b myself. Just trying to point you in the right direction. Go back and read the post, then read it again (as SamuriHL states in his post).

xMandy said:
as far as I see, the House of Moto does the same as RSD lite - it brings the RAZR back to "a minty factory fresh state" - means 4.1.2. with JBBL.
After that you did the OTA update to 4.4.2.? Is this the trick to get KKBL? Trying to use twrp didn't work for me (still on 4.1.2), the screen was frozen, no touch, no reaction. . .
Didn't get to 4.4.2 so far or was not able to flash a recovery that supports CM 12. :crying:
It would be great if you will share your secret :fingers-crossed:
thx
Click to expand...
Click to collapse
xMandy said:
thanks so far!
But why are you using a XT926-FXZ and not some for the XT925?
Any hint how to find out which one is the one I should use? ADB says "vanquish_u"... :silly:
...still trying...
Click to expand...
Click to collapse
OK, so here is a little explanation, followed by a link on how to upgrade xt925 or 926 to 4.4.2
So HoM and RSD-Flasher are almost the same as RSD-Lite, they have a little more functions and so on. Everything you might wanna do with RSD-Lite u can do with these two tools.
XMandy: You can find out your version this way: settings -> about phone -> system version. At least on my phone it states xt925
Here is how i upgraded my xt925 to stock 4.4.2 i would recommend to be BL unlocked, but it seems like there are ways to unlock and root 4.4, so that is not that important.
Guide
With everything else from that point on i also got my problems, thats why i'm here in the first place but probably after upgrading you guys can help me too

so far - so bad
esok44 said:
OK, so here is a little explanation, followed by a link on how to upgrade xt925 or 926 to 4.4.2
So HoM and RSD-Flasher are almost the same as RSD-Lite, they have a little more functions and so on. Everything you might wanna do with RSD-Lite u can do with these two tools.
XMandy: You can find out your version this way: settings -> about phone -> system version. At least on my phone it states xt925
Here is how i upgraded my xt925 to stock 4.4.2 i would recommend to be BL unlocked, but it seems like there are ways to unlock and root 4.4, so that is not that important.
Guide
With everything else from that point on i also got my problems, thats why i'm here in the first place but probably after upgrading you guys can help me too
Click to expand...
Click to collapse
I did this several times now. . .
XT 925, VANQUISH_U, unlocked BL:
# Clean install of 4.1.2. with RSD lite and zip-file 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml
=> works, with result JB 4.1.2
# OTA update
=> restart folowed by bootloader with message:
Device is LOCKED, Status Code: 0
downgraded security version
update gpt_main version vailed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
# fastboot flash partition gpt.bin
# fastboot flash tz tz.mbn
# fastboot reboot-bootloader
=> works, with result Device is UNLOCKED, Status Code: 3
# fastboot reboot
=> works, with result KK 4.4.2, version 180.46.117.XT925.CEE-Retail.en.EU
# second OTA update
=> works, with result KK 4.4.2, version 180.46.127.XT925.CEE-Retail.en.EU, build number KDA20.127
==> so far everything is fine
# flashing recovery TWRP-2.8.4.1-xt925.img
=> works, with result recovery boot TWRP is posible and "install from zip" too
# wipe to factory reset
# wipe cache / repair cache
# install zip cm-12-20150217-NIGHTLY-xt925.zip
# install zip gapps-lp-20141220-signed.zip
# reboot to system
==> rebooting and bl warning
==> starting the ignition and looooooop
==> shows the CM 12 logo, is "active" and does this for hours if I won't stop it
So, where's my fault?

Heyho,
The mistake is not on your side. Its what i have stated before:
To not get the bootloop after installing cm12 u must Flash it over cm11. Currently i was not able to find a cm11 Version for kkbl which i could install on the xt925. I Asked i several Threads, regarding this topic and Noone helped/could help me so far
Sorry i thought your mistake was some where else
Sent from my RAZR HD using XDA Free mobile app

getting closer
esok44 said:
Heyho,
The mistake is not on your side. Its what i have stated before:
To not get the bootloop after installing cm12 u must Flash it over cm11. Currently i was not able to find a cm11 Version for kkbl which i could install on the xt925. I Asked i several Threads, regarding this topic and Noone helped/could help me so far
Sorry i thought your mistake was some where else
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Sorry to ask again...
Where's the step i have to insert the flash of CM 11?
As far as i know with twrp.2.8.2.1 (KKBL) it's not posible to flash CM 11?
So. . . will this way do it?
# 4.4.2 stock
# flash recovery for jbbl (for example CW6.0.4.4)
# flash CM 11
# flash recovery for kkbl (twrp.2.8.2.1)
# flash CM 12
With some jbbl and CM 11 on the phone i was not able to use the CM 12 update - neither OTA nor recovery flash.
and again a big :good::good::good:

esok44 said:
Heyho,
The mistake is not on your side. Its what i have stated before:
To not get the bootloop after installing cm12 u must Flash it over cm11. Currently i was not able to find a cm11 Version for kkbl which i could install on the xt925. I Asked i several Threads, regarding this topic and Noone helped/could help me so far
Sorry i thought your mistake was some where else
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).

kabaldan said:
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
Click to expand...
Click to collapse
I'm having the exact same problem, except on my XT926M.
I was on an unlocked XT926M running 4.1.2 stock Verizon. Yesterday I installed the FXZ 4.4.2 ROM with RSD Lite to upgrade the bootloader to KKBL. It works fine on 4.4.2 (183.46.15.XT926.Verizon.en.us)
Today I tried installing TWRP 2.8.4.2 and installing the latest CM12 nightly (Feb 17). I created a backup with TWRP, factory wiped , and flashed the CM12 image through TWRP. It succeeded flashing, but got stuck on the boot screen. After 20 minutes, I powered it off, tried turning it on again...stuck for another 10. Tried mounting the system partition in TWRP, doing an advanced wipe of system, data (NOT internal storage), and cache, but even that didn't work. Eventually after two hours of reflashing and draining my battery to 75% I decided to restore my TWRP 4.4.2 stock backup so I would have a phone to use again.
I can't post in the actual dev thread where people were talking about this. I would love to help troubleshoot this issue if they would direct me.

kabaldan said:
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
Click to expand...
Click to collapse
Hey Kabaldan,
i wiill provide a logcat later today.
Will just give the most recent cm12 Version a shot.
A logcat will be posted
Thanks for your interest in helping us

I actually found a user on the droidrzr forums who has the same issue in a thread for the Dirty Unicorns Lollipop ROM.
You can see the logs he posted of the window here:
droidrzr.com/topic/56216-romofficialdirty-unicornsv91502moto-msm8960kk-bl21015/page-21#entry491765
This is only a few days old. There's a few others in the thread who were chiming in with the same problem. So far not much progress.

another try
kabaldan said:
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
Click to expand...
Click to collapse
again on-the-fly
XT925, KK 4.4.2 stock, clean, BL unlocked, SuperSu installed, twrp v2.8.4.2 running
# install
# external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip
# swipe to confirm flash
=> result on screen:
Installing '/external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip'
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
script succeeded: result was [0.200000]
Updating partition details. . .
. . .done
# Wipe cache/dalvik
# swipe to wipe
=> result on screen:
Wiping Dalvik Cache Directories. . .
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# back
# return
# external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip
# swipe to confirm flash
=> result on screen:
Installing 'external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip'. . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
*****************************************
Google Apps for Android 4.4.2
*****************************************
Installing files . . .
Cleaning up and setting metadata . . .
Installation complete!
Upddating partition details . . .
. . .done
# Wipe cache/dalvik
# swipe to wpe
=> result on screen:
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# Back
# Reboot System
==> result:
BOOTING !
=> first time the phone is booting and installing the apps
=> results on screen:
process " . . . several during the boot . . ." was aborted
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
=> result after booting:
some com.google.processes were aborted, for example "com.google.phone"
# reboot in recovery twrp 2.8.4.2
# wipe
# data
# swipe to confirm
# reboot to system
==> result: BOOTLOOOOOOP
Can anyone tell me what's goin' on?

xMandy said:
again on-the-fly
XT925, KK 4.4.2 stock, clean, BL unlocked, SuperSu installed, twrp v2.8.4.2 running
# install
# external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip
# swipe to confirm flash
=> result on screen:
Installing '/external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip'
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
script succeeded: result was [0.200000]
Updating partition details. . .
. . .done
# Wipe cache/dalvik
# swipe to wipe
=> result on screen:
Wiping Dalvik Cache Directories. . .
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# back
# return
# external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip
# swipe to confirm flash
=> result on screen:
Installing 'external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip'. . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
*****************************************
Google Apps for Android 4.4.2
*****************************************
Installing files . . .
Cleaning up and setting metadata . . .
Installation complete!
Upddating partition details . . .
. . .done
# Wipe cache/dalvik
# swipe to wpe
=> result on screen:
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# Back
# Reboot System
==> result:
BOOTING !
=> first time the phone is booting and installing the apps
=> results on screen:
process " . . . several during the boot . . ." was aborted
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
=> result after booting:
some com.google.processes were aborted, for example "com.google.phone"
# reboot in recovery twrp 2.8.4.2
# wipe
# data
# swipe to confirm
# reboot to system
==> result: BOOTLOOOOOOP
Can anyone tell me what's goin' on?
Click to expand...
Click to collapse
The Problem with the google apps is that u usd the ones for androdi 4.4.2, i guess u need the ones for android 5...

Sorry Mandy, i was wrong, it was not a faulty gapps Version. I dont know The nistake, but i will try to pull a logcat later when i got a little more battery
Sent from my RAZR HD using XDA Free mobile app

[ROM][STOCK][BUMP'd] LG D850 20F Lollipop 5.0.1 (+ extras)

Stock LG D850 20F Lollipop 5.0.1
This thread is based on my original post found in the AT&T G3 Lounge Thread..
What's new is I've just packed 20F into a flashable zip for those with TWRP already installed. It's not much.. but I know many would prefer not to use ADB or terminal.
What's this thread have to offer?
Flashable/BUMP'd D850 20F "rom" (system/boot)
Flashable D850 20F modem
Stock D850 20F partition images
Patched/BUMP'd D850 20F boot.img
Manual directions for installing TWRP if already on 20F
Manual directions for installing 20F if flashable zips aren't your thing
The above mentioned can all be downloaded HERE ON CODEFIRE
Flashable "rom" directions:
1. Put D850_20F_Lollipop_Stock.zip and D850_20F_2.0.1.c1.13-00050_Modem.zip on sdcard
--For root: Also grab the SuperSU zip from Chainfire HERE
2. Boot into TWRP
3. Hit install button and select each zip file you need
4. Swipe to flash... done. Rom flash will take a bit.. be patient.
5. Reboot phone when rom, modem, root is flashed. First Lollipop boot may take up to 5 minutes.
In some cases you may need to wipe cache/dalvik/data(factory reset) in TWRP if the phone gets stuck on boot animation or if things just aren't acting right. To avoid data loss be sure to use something like Helium or Titanium Backup prior to upgrading to Lollipop. TWRP backups/Nandroids don't hurt either.
Having issues with internal sdcard permissions afterwards? Having issues with downloads not saving? You may need to fix your sdcard permissions. In terminal emulator or adb shell enter:
Code:
su
restorecon -FR /data/media/0/
Some have mentioned external sdcard issues.. not sure if anyone has way to fix that? Maybe same command as above only pointing to ext-sd?
MD5:
85460a3ce5d0259477d2f03c64e867e9 D850_20F_Lollipop_Stock.zip
df2564aa824b35dbaf8bd886b5210b4a D850_20F_2.0.1.c1.13-00050_Modem.zip
Below I am including my original directions for manually flashing Lollipop.. whether completely stock and already on 20F... or already rooted/BUMP'd/TWRP'd.
You do not need to pay attention to any of this below if you are just flashing the rom above... these are the original manual directions only. #learn2read
If you want TWRP just downgrade aboot.img and laf.img to KK.. then BUMP'd TWRP will work. Must be rooted to be able to flash TWRP obviously. If not already rooted -- Root with THIS METHOD HERE or use THIS ONE-CLICK METHOD if typing an ADB command scares you.
If rooted and on stock 20F Lollipop follow #1
If already TWRP'd/BUMP'd on KitKat (or using AOSP) and want to manually update to rooted stock 20F follow #2
#1
Download D850 TWRP HERE and rename to twrp.img. download stock KK aboot and laf images HERE. Stick all 3 on root of internal sdcard. You'll also have to flash a patched stock 20F boot.img so that the Lollipop system still boots when using the downgraded aboot.img/laf.img. You can download the patched boot.img HERE. Stick it in the root of your internal sdcard.
Now issue the following commands with ADB shell. If using terminal app on phone do not use the "adb shell" command:
Code:
[SIZE="2"]adb shell
su
md5 /sdcard/aboot.img (confirm md5 = 348064a6d4f8d5b7d3eeec79d86de5bd before proceeding)
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/patched-20f-boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot[/SIZE]
You are finished and can now reboot back into the rom. You are now rooted, BUMP'd and TWRP'd on Lollipop!
#2
If already TWRP'd/BUMP'd and you want to upgrade manually to 20F Lollipop... download the patched boot.img HERE and stick it on the root of your internal sdcard.. along with the 20F modem.img and system.img. (@timmytim[/MENTION] shared system.img in the lounge thread HERE so be sure to thank him)
You may or may not have to "factory reset" in TWRP. YMMV.
[If flashing system.img you must be in TWRP, not the rom, while issuing these commands]
[May need the "Koush Universal ADB" drivers to get ADB goin' in TWRP]
Code:
[SIZE="2"]adb shell
su
dd if=/sdcard/patched-20f-boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system[/SIZE]
If flashing 20F system via this method you will also need to root since the system.img is stock. Download SuperSU zip from Chainfire HERE and flash the zip in TWRP AFTER flashing the system.img. You are finished and can now reboot back into the rom. You are rooted, BUMP'd and TWRP'd on Lollipop.
Click to expand...
Click to collapse

I used the method 1 since I am already on lollipop rooted. Is this method bumped o mean the bootloader is unlocked?

Sweet first in second in

autoprime said:
Stock LG D850 20F Lollipop 5.0.1
Click to expand...
Click to collapse
I used the method 1 since I am already on lollipop rooted. Is this method bumped o mean the bootloader is unlocked?

Testing now, wish me luck!
****UPDATE****
Downloading files: about 5min
Needlessly moving files to External SD: about 5min
Flashing all three files at once: about 4min
First Boot: about 7min
Optimizing apps YMMV
I wiped nothing
Began this method on Bumpd' 850 from this ROM http://forum.xda-developers.com/att-lg-g3/development/rom-liquidsmooth-v4-0-d850-12814-t2966409 rooted ('natch)

Right on nice job ???
Running On New Deadly Venom Note 4 v1.0

TonyStark said:
Sweet first in second in
Click to expand...
Click to collapse
you can still be first! feel free to remove netomel's first post (post #2) since he's gone and posted it yet again in post #4 as well.
:good:
netomel said:
I used the method 1 since I am already on lollipop rooted. Is this method bumped o mean the bootloader is unlocked?
Click to expand...
Click to collapse
Following method #1 downgrades your bootloader so that BUMP works. If you did method one(#1)... you are BUMP'd/TWRP'd...
BUMP = G3 unlocked bootloader method.
Any kernel's (and roms with new kernels) flashed thru TWRP on your phone will need to be BUMP'd from here on out unless you go back to 100% stock.. including proper bootloader. Most custom zips should already be pre-BUMP'd so that should not ever be a worry.
Anything that needs to be discussed further about BUMP or unlock does not belong here.
gpgon said:
Testing now, wish me luck!
Click to expand...
Click to collapse
Good luck! I don't have a D850 so wasn't able to test :fingers-crossed:
freaksavior said:
deodexed or odexed?
Click to expand...
Click to collapse
100% stock system.
no specified odex/deodex = odex
jaybird38 said:
If I flash this on a stock backup will I still be able to restore stock 4.4 or my cm 12 ROM.just don't want to loose them.
Click to expand...
Click to collapse
louvass said:
noob question. I am rooted kk can I just flash the Rom, modem and su..and I'll be good ? Thank you for bringing us this.
Click to expand...
Click to collapse
Yes to both of the above questions. @jaybird38 to make restoring 4.4/aosp nandroids effortless.. be sure to backup the modem as well. you may or may not need to reflash KK modem when using 4.4 roms. @louvass yes, that's exactly what the flashable zips are for.
rob219 said:
if im already on 5.0.2 illusion rom or any other 5.0.2 rom can't i just flash the rom and modem?
Click to expand...
Click to collapse
yes that's exactly what the directions say... flash rom zip, modem zip and supersu zip.
sandro100 said:
Hi my play store won't download anything, just stays stuck on downloading any help please
Click to expand...
Click to collapse
this can sometimes be fixed by running the following commands in terminal emulator or adb shell:
Code:
su
restorecon -FR /data/media/0
and perhaps a reboot after.
daw41 said:
@autoprime can you share the md5 of the rom zip and modem zip it continues to fail in twrp for me i just want to make sure I have a good copy
Click to expand...
Click to collapse
gordec said:
Can't get pass boot logo after 2 flashes. Can someone post the MD5 for the ROM? I feel the download was complete. Coming from Illusion AOSP ROM.
Click to expand...
Click to collapse
85460a3ce5d0259477d2f03c64e867e9 D850_20F_Lollipop_Stock.zip
df2564aa824b35dbaf8bd886b5210b4a D850_20F_2.0.1.c1.13-00050_Modem.zip
In teh future I may reply to people using this post rather than making a new post just to say "yes" or something...

Sorry to sound noob by it needed to be clarified since I did not see it anywhere but I suspected it was BUMP"d just wanted to be sure before start flashing away roms

deodexed or odexed?
edit: thanks for the update. I assumed it was odexed but wanted to verify. I'll hold off until there is one deodexed for modular packages then.

Flashed and booted up into the setup. Thank you very much!

Next challenge is to port D85520i and get it to pass security checks!
Great work, mate.

Just a heads up, thought most will already know this. Started process at ~100% and ended at 90% battery. Major heat increase during optimization (expected) and debilitating lag for the first ~10min (also expected.) Device is slowly settling down after a reboot.
***UPDATE***
Also probably no surprise to anyone but me, I had to reinstall busybox (even though I did a dirty flash)

Any advantage of the stock LG lollipop? I went straight to CM12 when I got the phone. Wonder if I should try stock out.

gordec said:
Any advantage of the stock LG lollipop? I went straight to CM12 when I got the phone. Wonder if I should try stock out.
Click to expand...
Click to collapse
I mean think about it ....... Stock camera which is always on point ... And now you have a rooted stock lollipop so you can use a lot of root access apps. Maybe XPOSED modules... There are advantages in stock rooted lollipop. Its user preference. I am on Illusion but will probably make a backup of this for safe keepings
Sent from my LG-D850 using XDA Free mobile app

shayneflashindaily said:
I mean think about it ....... Stock camera which is always on point ... And now you have a rooted stock lollipop so you can use a lot of root access apps. Maybe XPOSED modules... There are advantages in stock rooted lollipop. Its user preference. I am on Illusion but will probably make a backup of this for safe keepings
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah. I'm on Illusion too. It's pretty much bug free at this point.

gordec said:
Any advantage of the stock LG lollipop? I went straight to CM12 when I got the phone. Wonder if I should try stock out.
Click to expand...
Click to collapse
tbh, the only thing Stock got on AOSP is the camera. If you want a flawless camera experience then Stock, if you don't mind the average photos and limited options with the camera then I'll stay on AOSP

Appart from the aosp experience that you may like, there are some extra features packed in stock roms such as a better camera, remote controller, dual view, knock code, one handed operation, circle case support and so on... The better camera and remote controller itself are two of my most used features on the phone so stock lollipop is not an option but I have to admit that aosp lollipop has its strong points too such as a more cleaner interface, more battery life, more updated OS... So, it's a decition only you can make.

If I flash this on a stock backup will I still be able to restore stock 4.4 or my cm 12 ROM.just don't want to loose them.
Sent from my LG-D850 using XDA Free mobile app

noob question. I am rooted kk can I just flash the Rom, modem and su..and I'll be good ? Thank you for bringing us this.

eortizr said:
tbh, the only thing Stock got on AOSP is the camera. If you want a flawless camera experience then Stock, if you don't mind the average photos and limited options with the camera then I'll stay on AOSP
Click to expand...
Click to collapse
Exactly this. I've been hoping for cloudy for a long time, but I think i'm about to go back to a stock rom. I use my camera a lot, who doesn't, but the AOSP roms just don't quite cut it. If you do get something like CM, use the Lenovo camera, much better images.

[ROM][Flo][8/15/15] - Stock Rooted 5.1.1 - LMY48I - Root and BusyBox only!

AS the name implies this is a stock rooted Android 5.1.1 - LMY48I Lollipop ROM!
Features
100% Stock
Rooted / Powered by SuperSU by @Chainfire!
Busybox
Init.d Support
FSTRIM on install
Zip Aligned
No other edits
Notes:
Should update bootloader. It is attached as a flshable ZIP.
First boot is a loooooooooooong time! About 5 to 7 minutes!
You must be on Latest TWRP to enjoy this ROM. No other recoveries supported however they may work.
Install:
Copy ROM to storage
Reboot to TWRP recovery
Factory Reset (no other wipes needed)
Flash ROM
Reboot and Profit!
Troubleshooting
If you get no status bar reboot to recovery and clear all cache. If that doesn't work try flashing the factory image then flash TWRP again and then this ROM.
Getting Symlinks failed during install? Make sure /system is unchecked in TWRP mounts
Problems with internal storage? Look at THIS POST for fix by @freakzapster
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
[/CENTER]

Sharing Policy
You are free to use this ROM or any part of this ROM any way you like as long as you give proper credit!
Consider this your permission! Please do not PM me asking if its OK to build off this ROM. Permission granted!
However this does not include my CleanROM series of ROMS.
However, this ROM is not a CleanROM. Its a stock rooted and all yours!
Remember to give proper credit!
Hit Thanks!

NSDQ!

Please hit thanks on the OP and rate the thread 5 stars. Dont let the Nexus troll win!

Thanks, Scott, you are the good guy!

sensboston said:
Thanks, Scott, you are the good guy!
Click to expand...
Click to collapse
I try

Installed Scott's ROM, so far so good! "Thanks" one more time!

Thanks for the release; I've been looking forward to this update ever since getting the OTA notification. Did both my and my wife's tablet and it went off without a hitch.

Dirty flashed on top of previous version (LMY48G)- everything seems just great.
Thanks!
Sent from my Nexus 5 using Tapatalk

LMY47I?

.MoHaMaD said:
LMY47I?
Click to expand...
Click to collapse
Corrected. LM48I

I got an error about binary not updating, did I do something wrong?

wesley404 said:
I got an error about binary not updating, did I do something wrong?
Click to expand...
Click to collapse
More details? What binary? SuperSU? Busybox? Something else?
Sent from my Nexus 5 using Tapatalk

I also dirty flashed over the previous build and updated the bootloader. Zero issues!

Sorry for the delay, let me try it again and I will give the exact error I saw this morning.
Sent from my Nexus 6 using Tapatalk

The error states: E: Error executing updater binary in zip '/sdcard/ROM/N7-Stock-Root-LMY48I.zip
I have deleted and redownloaded from the link a few times in case I got a corrupted download previously and I get the same error and I have the latest bootloader installed also.

wesley404 said:
The error states: E: Error executing updater binary in zip '/sdcard/ROM/N7-Stock-Root-LMY48I.zip
I have deleted and redownloaded from the link a few times in case I got a corrupted download previously and I get the same error and I have the latest bootloader installed also.
Click to expand...
Click to collapse
Try unmounting /system prior to flashing.

quickdraw86 said:
Try unmounting /system prior to flashing.
Click to expand...
Click to collapse
I still havent figured out why some people have /system mounted on a fresh boot? Mind blowing.

I got the same error, but rebooting the recovery fixed it.
Sent from my Nexus 7 using XDA Free mobile app

Wiped davlik & cache, dirty flashed.
No problems.
Thanks Scott!