Develop Bugs

Getting error on new update LG8

I got the little pop up that there was an update so I installed it and it said the phone was going to boot in 6 seconds or whatever, after that the phone booted into CWM and it said it failed install. Now every time I check for an update it says there's no update right now. Am I the only one with this problem? How do I fix it? Is it because I'm rooted? I'm on the stock rom by the way.

jordan23945bulls said:
I got the little pop up that there was an update so I installed it and it said the phone was going to boot in 6 seconds or whatever, after that the phone booted into CWM and it said it failed install. Now every time I check for an update it says there's no update right now. Am I the only one with this problem? How do I fix it? Is it because I'm rooted? I'm on the stock rom by the way.
Click to expand...
Click to collapse
Yes, it is because you are rooted. Download the stock rooted DeOdex one done by freeza. Good stuff.
Sent from my SPH-L710 using xda premium

Naddict said:
Yes, it is because you are rooted. Download the stock rooted DeOdex one done by freeza. Good stuff.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I need to flash the Lg8 firmware and Other parts? Or does it not work if I don't? I have never flashed anything using Odin, could I get steps? Thanks. Also what if I want to flash another rom? Do I need to flash the lg8 firmware and other parts again?

jordan23945bulls said:
I need to flash the Lg8 firmware and Other parts? Or does it not work if I don't? I have never flashed anything using Odin, could I get steps? Thanks. Also what if I want to flash another rom? Do I need to flash the lg8 firmware and other parts again?
Click to expand...
Click to collapse
see here http://forum.xda-developers.com/showthread.php?t=1743923
you don't need to flash the modem if you don't want to. Although I think (opinion only, and they vary between user) LG8 is a very good modem right now.
Once you flash modem, you will keep it until you revert or flash a newer modem or a rom specifically tells you it also provides it.

Naddict said:
see here http://forum.xda-developers.com/showthread.php?t=1743923
you don't need to flash the modem if you don't want to. Although I think (opinion only, and they vary between user) LG8 is a very good modem right now.
Once you flash modem, you will keep it until you revert or flash a newer modem or a rom specifically tells you it also provides it.
Click to expand...
Click to collapse
Alright, so I don't need to flash the moden or the other parts if I'm flashing an lg8 rom.

Naddict said:
Yes, it is because you are rooted. Download the stock rooted DeOdex one done by freeza. Good stuff.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So flash the DeOdex version via CWR.
Then flash the Modem.zip via CWR.
Then use Odin and flash "Other Parts" .tar file and that's it?
Will there be any differentiation between going this route versus unrooting -> OTA update -> re-rooting?

The way I flash I got the legit update and flash with custom recovery and before the reboot flash the team win root file and ur done then reboot and ur done u have the hole update and firmware and radio and rooted and u keep your custom recovery
Sent from my SPH-L710 using xda premium

ZV8 to ZVA Modified OTA (Flash in TWRP)

Thanks to everyone working on the OTA, such as Savoca and Autoprime checking the OTA status.
The ZVA update has a lot of good and some bad things. I've "tinkered" with Samsung OTAs before and gotten them to flash but there was always a problem with Sprint's Chameleon implementation on Samsung that caused things not to behave the same when flashing the modified zip.
Fortunately, that doesn't seem to be the case with LG. :good:
So here are two ZIPs for your use. Use at your discretion and as usual, I give my standard disclaimer: Your phone, your flash, your responsibility.. not mine.
Link to ZIPs:
http://www.rwilco12.com/downloads.php?dir=Files/Garwynn Projects/LS980/ZV8toZVA
Why two versions? Both skip recovery and revert aboot image so that Loki can still work.
But during first set of tests I received an assert error on magazines.odex.
If you get this try the second one, in which I removed that assert and update.
If you get a build.prop assert error on the second you'll want to try and find yourself a stock version and flash again.
For me I had to do the TOT again to get it to work.
Now the other bits of information:
1) Both remove the device assert because TWRP doesn't use that model ID. So make sure you only use this on the SPRINT model.
2) I do recommend taking a backup before as I had some funky results after the update. One time system disappeared... another time took especially long to restart. After doing a second time it does seem to be working properly. So may not hurt to back up right after flashing the zip so that you have a good copy of ZVA to work off of.
3) You can stay rooted and you do not need to re-root afterwards. The first time I got a prompt from SuperSU to update the su binary, but not the second time. In either case root was not checked during OTA so you don't need to mess with it.
Any questions feel free to let me know. Again thanks to all and enjoy!
(Added 10:50 CST)
I want to also caution one thing at the moment. Those wanting to keep using AOSP ROMs should not flash ZVA at the moment.
At the moment it's causing a boot loop and several of us are trying to figure out what the cause is.

Awesome! Testing this now, I'll post my own results too.
Sent from my LG-LS980 using xda app-developers app

One other precaution because it seems a person just bricked testing radio packages...
Don't be a hero. If it's acting up, go back to recovery and restore a backup or flash the ZV8 TOT.
Updates are cool and everyone wants it, but it's not worth bricking over.

garwynn said:
Thanks to everyone working on the OTA, such as Savoca and Autoprime checking the OTA status.
The ZVA update has a lot of good and some bad things. I've "tinkered" with Samsung OTAs before and gotten them to flash but there was always a problem with Sprint's Chameleon implementation on Samsung that caused things not to behave the same when flashing the modified zip.
Fortunately, that doesn't seem to be the case with LG. :good:
So here are two ZIPs for your use. Use at your discretion and as usual, I give my standard disclaimer: Your phone, your flash, your responsibility.. not mine.
Link to ZIPs:
http://www.rwilco12.com/downloads.php?dir=Files/Garwynn Projects/LS980/ZV8toZVA
Why two versions? Both skip recovery and revert aboot image so that Loki can still work.
But during first set of tests I received an assert error on magazines.odex.
If you get this try the second one, in which I removed that assert and update.
If you get a build.prop assert error on the second you'll want to try and find yourself a stock version and flash again.
For me I had to do the TOT again to get it to work.
Now the other bits of information:
1) Both remove the device assert because TWRP doesn't use that model ID. So make sure you only use this on the SPRINT model.
2) I do recommend taking a backup before as I had some funky results after the update. One time system disappeared... another time took especially long to restart. After doing a second time it does seem to be working properly. So may not hurt to back up right after flashing the zip so that you have a good copy of ZVA to work off of.
3) You can stay rooted and you do not need to re-root afterwards. The first time I got a prompt from SuperSU to update the su binary, but not the second time. In either case root was not checked during OTA so you don't need to mess with it.
Any questions feel free to let me know. Again thanks to all and enjoy!
Click to expand...
Click to collapse
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!

Any chance this will for stock based ROMs?
Sent from my LG-LS980 using xda app-developers app

@garwynn do you have the stock build.prop from the zv8 update? not the one from the stock rooted rom.

mrrogers1 said:
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!
Click to expand...
Click to collapse
If you have debloated the ROM, it probably won't work. I ended up flashing the TOT (pure stock) to get it to flash.
I want to also caution one thing at the moment. Those wanting to keep using AOSP ROMs should not flash ZVA at the moment.
At the moment it's causing a boot loop and several of us are trying to figure out what the cause is.

youdug said:
@garwynn do you have the stock build.prop from the zv8 update? not the one from the stock rooted rom.
Click to expand...
Click to collapse
Sorry, didn't pull it before I flashed. Really should have.
If I flash it again today I'll pull it.

garwynn said:
Sorry, didn't pull it before I flashed. Really should have.
If I flash it again today I'll pull it.
Click to expand...
Click to collapse
im not sure if ill need it but might as well grab it just in case before i start.
thanks man.

mrrogers1 said:
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!
Click to expand...
Click to collapse
Sorry, didn't clarify the second. I tried stock odex ROM and didn't work. That's why I went the TOT route.

Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app

Williek113 said:
Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
i flashed testupdate 2 no problems here

Williek113 said:
Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
What rom were you on?
latoso said:
i flashed testupdate 2 no problems here
Click to expand...
Click to collapse
and what rom were you on?

mrrogers1 said:
What rom were you on?
and what rom were you on?
Click to expand...
Click to collapse
i was on stock rom

latoso said:
i was on stock rom
Click to expand...
Click to collapse
Stock rooted with just TWRP or Stock rooted Odex or Deodex that @youdug provided here >>> http://forum.xda-developers.com/showthread.php?t=2560115?

latoso said:
i was on stock rom
Click to expand...
Click to collapse
All stock with twrp right?
Sent from my LG-LS980 using xda premium

mchlbenner said:
All stock with twrp right?
Sent from my LG-LS980 using xda premium
Click to expand...
Click to collapse
yes stock rom with twrp

Flashed from stock rom with TWRP 2.6.3.3 using testupdate.zip with no issues. Did not need to use update 2.

If someone that has NOT ran this yet could, please post or PM me their build.prop from the stock + TWRP rom before doing the update?
Thanks:good::good:

garwynn said:
One other precaution because it seems a person just bricked testing radio packages...
Don't be a hero. If it's acting up, go back to recovery and restore a backup or flash the ZV8 TOT.
Updates are cool and everyone wants it, but it's not worth bricking over.
Click to expand...
Click to collapse
RIP @dougie187
:victory:

Nexus 7 OTA Error

Well, I used a factory reset tool to reset my rom back to stock. However, when I try to do a system update, it goes all the way to the end and says Error. Note that I can get into my tablet before I launch the update, but afterwards it just boots into recovery and I have to hard reset and reset my device using the aforementioned factory reset tool. Basically all I want to know is if it has anything to do with me recovering from the tool, or are OTA's iffy? I bought the device yesterday and I love it. I rooted it, unlocked the bootloader, etc. So yes it is modified. However It is not in anyway bricked. I just want to know if it's possible to do an official OTA from System Update, or do I have to use the one provided on the Index of the Nexus 7 Flo forum? Thanks for any help. Like I said, It's not bricked, I'm not complaining. Just a few questions

SwiftLeeO said:
Well, I used a factory reset tool to reset my rom back to stock. However, when I try to do a system update, it goes all the way to the end and says Error. Note that I can get into my tablet before I launch the update, but afterwards it just boots into recovery and I have to hard reset and reset my device using the aforementioned factory reset tool. Basically all I want to know is if it has anything to do with me recovering from the tool, or are OTA's iffy? I bought the device yesterday and I love it. I rooted it, unlocked the bootloader, etc. So yes it is modified. However It is not in anyway bricked. I just want to know if it's possible to do an official OTA from System Update, or do I have to use the one provided on the Index of the Nexus 7 Flo forum? Thanks for any help. Like I said, It's not bricked, I'm not complaining. Just a few questions
Click to expand...
Click to collapse
Well, without much detail about the error, it's hard to help. Are you just stock rooted with stock recovery? If so, you should be able to take an OTA no problem, although you'd lose root. But you can always flash supersu to get it back. Did you install a custom recovery to root? Or did you use a toolkit? Lots of questions. If you have a custom recovery, you'd have to fastboot flash the stock recovery from the factory image. If you still have the stock recovery and are just stock rooted, you've probably modified the system in some way. In that case, you can just fastboot flash the stock system image.

charesa39 said:
Well, without much detail about the error, it's hard to help. Are you just stock rooted with stock recovery? If so, you should be able to take an OTA no problem, although you'd lose root. But you can always flash supersu to get it back. Did you install a custom recovery to root? Or did you use a toolkit? Lots of questions. If you have a custom recovery, you'd have to fastboot flash the stock recovery from the factory image. If you still have the stock recovery and are just stock rooted, you've probably modified the system in some way. In that case, you can just fastboot flash the stock system image.
Click to expand...
Click to collapse
Stock Rooted with Stock Recovery. It downloads the OTA no issue, but when in download mode, it gets to the very end and says Error!. I used CFAutoRoot for rooting. I used fastboot to unlock the bootloader and install custom recovery.

SwiftLeeO said:
Stock Rooted with Stock Recovery. It downloads the OTA no issue, but when in download mode, it gets to the very end and says Error!. I used CFAutoRoot for rooting. I used fastboot to unlock the bootloader and install custom recovery.
Click to expand...
Click to collapse
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app

charesa39 said:
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Exactly what I was wondering!

charesa39 said:
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Stock.

SwiftLeeO said:
Stock.
Click to expand...
Click to collapse
Since you have stock recovery, there's probably an app that modified your system that's not allowing it to install the update because it detects a change in one of your system files. Fastboot flash the system image from the stock factory image. Then, it should update.
Sent from my Nexus 7 using xda app-developers app

charesa39 said:
Since you have stock recovery, there's probably an app that modified your system that's not allowing it to install the update because it detects a change in one of your system files. Fastboot flash the system image from the stock factory image. Then, it should update.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You wouldn't happen to have one of those lying around would you? The img file I mean.

SwiftLeeO said:
You wouldn't happen to have one of those lying around would you? The img file I mean.
Click to expand...
Click to collapse
I'm assuming you're on 4.3 since you're trying to update? Either way, you can find the factory images here: https://developers.google.com/android/nexus/images.
Just download the the one for the version you're currently running on your N7. MAKE SURE YOU DOWNLOAD THE CORRECT ONE. Then, just extract the files from the tar.gz file. There's another zip file in that tar.gz file. Extract that one, and there's a system.img file. Fastboot flash it in the bootloader.
Sent from my Nexus 7 using xda app-developers app

charesa39 said:
I'm assuming you're on 4.3 since you're trying to update? Either way, you can find the factory images here: https://developers.google.com/android/nexus/images.
Just download the the one for the version you're currently running on your N7. MAKE SURE YOU DOWNLOAD THE CORRECT ONE. Then, just extract the files from the tar.gz file. There's another zip file in that tar.gz file. Extract that one, and there's a system.img file. Fastboot flash it in the bootloader.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help

SwiftLeeO said:
Thanks for the help
Click to expand...
Click to collapse
Anytime. :thumbup:
Sent from my Nexus 7 using xda app-developers app

[Q] Trying to accept 3.31.651.2 ota, fails because of chromewithbrowser?

I relocked the bootloader, flashed the stock recovery, and I get a message that something was wrong with chromewithbrowser and the install couldn't continue.
Any ideas?
Also, what is even in the recent OTA anyway? Anything of worth?
I added init.d support to the stock kernel. Would that cause the issue?

johnequickiii said:
I relocked the bootloader, flashed the stock recovery, and I get a message that something was wrong with chromewithbrowser and the install couldn't continue.
Any ideas?
Also, what is even in the recent OTA anyway? Anything of worth?
I added init.d support to the stock kernel. Would that cause the issue?
Click to expand...
Click to collapse
Use a stock kernel and a stock recovery with your proper nandroid and do the OTA. You can do a reset of the device than do the OTA

chromewithbrowser isnt changed by the kernel. you need :
100% stock ROM
kernel
recovery
then you can update.

Ok. That's where I'm going wrong then, because I added init.d support to the stock kernel. Thanks. I'll try it again tomorrow.
Sent from my HTC M8 using XDA Premium 4 mobile app.

but you can keep your boot loader unlocked. no need to relock it for ota purposes

Mr Hofs said:
but you can keep your boot loader unlocked. no need to relock it for ota purposes
Click to expand...
Click to collapse
Where might I find the stock kernel for 3.30.651.2? I have the recovery and I never opted for another rom, so I'm on stock still.

I just can't seem to find where I may download the stock kernel from. Been looking everywhere.

johnequickiii said:
Where might I find the stock kernel for 3.30.651.2? I have the recovery and I never opted for another rom, so I'm on stock still.
Click to expand...
Click to collapse
If you're totally on stock than you should be using the stock kernel already unless you flashed a custom kernel?

I modified the kernel by adding init.d support to it. I'm supposing that in itself made the kernel non stock. I flashed the stock recovery and even locked the bootloader, but it still wouldn't let me install the OTA.
Stock recovery reported some kind of error involving ChromewithBrowser, so that didn't really make sense to me.
Sent from my HTC M8 using XDA Premium 4 mobile app.

Bobbi lim said:
If you're totally on stock than you should be using the stock kernel already unless you flashed a custom kernel?
Click to expand...
Click to collapse
sorry....had tot laugh so hard about this !

johnequickiii said:
I modified the kernel by adding init.d support to it. I'm supposing that in itself made the kernel non stock. I flashed the stock recovery and even locked the bootloader, but it still wouldn't let me install the OTA.
Stock recovery reported some kind of error involving ChromewithBrowser, so that didn't really make sense to me.
Sent from my HTC M8 using XDA Premium 4 mobile app.
Click to expand...
Click to collapse
what you must do is backup what you need. go to the general section and check for the collection of stock backups. download the appropriate matching backup and restore it (it has the stock kernel and modules in it) then flash back the stock recovery and update the phone.

FYI: http://forum.xda-developers.com/showthread.php?p=52894276
obviously something is wrong with "chromewithbrowser" (whatever that is)

Mr Hofs said:
sorry....had tot laugh so hard about this !
Click to expand...
Click to collapse
Didn't notice that he added inti.d into the kernel

Bobbi lim said:
Didn't notice that he added inti.d into the kernel
Click to expand...
Click to collapse
how could you not, you where the first that responded to it. how do you form an answer to a post if you don't read it ?
:sly:

Not sure how to go about making the phone accept an OTA now though without the possibility of going back to stock, and I definitely don't want to do that.
I do have the stock recovery ready to go, just can't seem to find the stock kernel to accompany it. Maybe with both, it'll allow it to go through.
Although, if the update isn't really anything helpful or important, I can just stop worrying about it altogether. I plan on snagging the M9 when it's out, so the need for an OTA goes out the window if this one isn't necessary and the Lollipop one is due around the same time of the next flagship release.
Sent from my HTC M8 using XDA Premium 4 mobile app.

Question about rooting

If i root my M8 am i still able to do ota updates to my phone like normal.
for some background i have rooted phones before i have dabbled in flashing custom roms before but it has been a while. thankyou guys for the answer

Being rooted won't prevent OTA updates. You WILL need the stock ROM, unchanged system partition(no edited build.prop etc) and stock recovery to perform updates.
So best to make backups in case there aren't any backups for your device.

BerndM14 said:
Being rooted won't prevent OTA updates. You WILL need the stock ROM, unchanged system partition(no edited build.prop etc) and stock recovery to perform updates.
So best to make backups in case there aren't any backups for your device.
Click to expand...
Click to collapse
Thank you for you're reply is it true that with supersu there is a full unroot option as well? Does that actually do justice I literally only want to root my phone no flashing custom Roms or kernels
Sent from my 831C using XDA Free mobile app

Itsvictor said:
Thank you for you're reply is it true that with supersu there is a full unroot option as well? Does that actually do justice I literally only want to root my phone no flashing custom Roms or kernels
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Yeah there's a full unroot, there's also a unsupersu file in the "Return to stock 100%" thread, somewhere in the general section.
But even so, like mentioned, being rooted won't prevent OTA's. If you're not going with custom ROMs and Kernels then just make sure you have the stock recovery back when doing OTA's else it'll fail.

Itsvictor said:
Thank you for you're reply is it true that with supersu there is a full unroot option as well? Does that actually do justice I literally only want to root my phone no flashing custom Roms or kernels
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Don't forget unlocking the bootloader @HTCDev will wipe the phone and you loose some apps in the process
to take the OTA these missing apps must be restored also same as stock recovery.
At least that's how it was on the M7 pretty sure it's the same on the m8