Don't want the OTA right now?
Tired of deferring the update?
How can you stop it or get rid of it before or after it downloads to the device?
Answer:
M7vzw OTA Killer - Flash in Recovery
Enjoy! :good:
santod040 said:
Don't want the OTA right now?
Tired of deferring the update?
How can you stop it or get rid of it before or after it downloads to the device?
Answer:
M7vzw OTA Killer - Flash in Recovery
Enjoy! :good:
Click to expand...
Click to collapse
Awesome thanks! Is there a way to get OTAs back after flashing this? Just curious.
Cares said:
Awesome thanks! Is there a way to get OTAs back after flashing this? Just curious.
Click to expand...
Click to collapse
Flash my full odex stock rom...they won't apply to much else anyhow.
santod040 said:
Flash my full odex stock rom...they won't apply to much else anyhow.
Click to expand...
Click to collapse
I am going to flash this with Bonestock. Shouldn't be a problem right?
Cares said:
I am going to flash this with Bonestock. Shouldn't be a problem right?
Click to expand...
Click to collapse
You can flash this on any rom.
santod040 said:
Flash my full odex stock rom...they won't apply to much else anyhow.
Click to expand...
Click to collapse
which rom of yours is full odex stock?? i;d love to try it
sant0d, you are da best. Not that I need this, but you've done a lot to ontribute to this model phone. So thank you.
This work with your KitKat ROMs too?
I just went through and flashed your Odex Debloated KitKat ROM, and downloaded this to block the OTA from happening. However, I just noticed the last update of this is from December. Is it still OK to flash this on top of the KitKat ROM, or is that going to muck up things? (Or did you already "bake" it in by getting rid of some of the stuff in the debloat process?).
Thanks again!
Robert
Robertjm said:
I just went through and flashed your Odex Debloated KitKat ROM, and downloaded this to block the OTA from happening. However, I just noticed the last update of this is from December. Is it still OK to flash this on top of the KitKat ROM, or is that going to muck up things? (Or did you already "bake" it in by getting rid of some of the stuff in the debloat process?).
Thanks again!
Robert
Click to expand...
Click to collapse
It should still work fine on KK.
But the debloated rom already has the OTA stuff removed.
Look in Settings > see anywhere to even check for a software update? No you won't...
It's already been removed.
santod040 said:
It should still work fine on KK.
But the debloated rom already has the OTA stuff removed.
Look in Settings > see anywhere to even check for a software update? No you won't...
It's already been removed.
Click to expand...
Click to collapse
Thank you so much!!!!! Finally something that actually works to get rid of the OTA Thank you so much Santod045 you are the best!
Oh yeah. Will this still work with sense 6.0?
Sent from my HTC ONE.
onthehole said:
Oh yeah. Will this still work with sense 6.0?
Sent from my HTC ONE.
Click to expand...
Click to collapse
Yes, it should work just fine.
santod040 said:
Yes, it should work just fine.
Click to expand...
Click to collapse
It does indeed!
Thank you very Much :good:
Stock Un-Rooted HTC One..?
My husbands phone (which he refused to let me root when we had the chance, has been giving him a lot of grief with this latest OTA. It keeps downloading, attempting to install, and there errors 410 update failed, and exits software update. When I checked his phone after the latest attempt by the phone to install 4.4.3 to see if the download was still ON his device, it had disappeared with the failure of the update.
My question is, he's just sick of getting the prompt, error, and reboot - as a temp fix, can I push this OTA Killer onto his phone even though it isn't rooted and have it work, or do I need to find a signed RUU of the 4.4.3 and flash in bootloader (as I was originally planning on doing, but came across this...)
Thanks in advance!!!
xenacick said:
My husbands phone (which he refused to let me root when we had the chance, has been giving him a lot of grief with this latest OTA. It keeps downloading, attempting to install, and there errors 410 update failed, and exits software update. When I checked his phone after the latest attempt by the phone to install 4.4.3 to see if the download was still ON his device, it had disappeared with the failure of the update.
My question is, he's just sick of getting the prompt, error, and reboot - as a temp fix, can I push this OTA Killer onto his phone even though it isn't rooted and have it work, or do I need to find a signed RUU of the 4.4.3 and flash in bootloader (as I was originally planning on doing, but came across this...)
Thanks in advance!!!
Click to expand...
Click to collapse
If he has a custom recovery installed, then it will work. Have you tried downloading the OTAzip to his SD card and running the ota directly from stock recovery?
Get into recovery, select install update from SD, select OTAzip.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
If he has a custom recovery installed, then it will work. Have you tried downloading the OTAzip to his SD card and running the ota directly from stock recovery?
Get into recovery, select install update from SD, select OTAzip.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
NO, no custom recovery installed, everything is 100% stock. He spent a good part of 3 hours with tech support with Verizon and HTC and they were both dumbfounded....go figure!
Problem is because it's a virtual SD, I have no way of verifying (without root) that it's even downloaded to the virtual one on the M7. Would it hurt anything to take a shot at it from stock recovery.....?
Or is there a link someone could suggest to a download to the OTApkg file?
xenacick said:
NO, no custom recovery installed, everything is 100% stock. He spent a good part of 3 hours with tech support with Verizon and HTC and they were both dumbfounded....go figure!
Problem is because it's a virtual SD, I have no way of verifying (without root) that it's even downloaded to the virtual one on the M7. Would it hurt anything to take a shot at it from stock recovery.....?
Or is there a link someone could suggest to a download to the OTApkg file?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55244412
@dottat uploaded it to his android file host account.
Sent from my HTC6500LVWBLU using XDA Free mobile app
would this help my problem??
I recently read a post, I don't know where now, but it had to do with a hidden Trojan/malware. That was started in 2013... After reading, thinking back to when this really started affecting me Feb,26, 2015. I noticed some strange things mentioned in my service log from around that date. The post mentioned how it places a high tracker in some obscure app. Unfortunately I got the bug, BAD!!! So not knowing about this until I made it worse by plugging my phone into my computer... I'm sure you can figure out the rest. My everything is screwed now. My HTC one m7, is the only device I can use period, now. I tried to root, and couldn't. Then downloaded another root checker, and it said my device was already rooted. Is there anything I can do(on my knees begging). This has to be the worst inter-web experience ever. Any and all ideas, advice, similar problems, links, and time are greatly appreciated. Thank you
Related
I am running stock sense on a rooted phone. I only rooted so I could tether and run adfree, and actually like stock sense very much. Is there a way to install the ota without ruining my phone?
I'm wondering this, too. I'm all stock, rooted with S-OFF, removed crapware. I'm running ClockworkMod 2.5.0.5 though, and I believe I've read that OTAs won't install if you're not running stock recovery. I'm kind of at a loss as to what to do now.
Run the OTA
Reflash your recovery
Done. Re-rooted. OTA doesnt turn s-on.
Smokeey said:
Run the OTA
Reflash your recovery
Done. Re-rooted. OTA doesnt turn s-on.
Click to expand...
Click to collapse
Will the OTA install if I'm using ClockworkMod?
I'm in the same boat as thevoiceless, and I'm curious of the same thing; I don't want to brick my phone >.>
And is there a link to download the ota?
I love my skyradier 3.3.3 final Rom and I am not interested in this update how do I get It to stop bothering me every half hour to update. It's annoying.
Sent from my ADR6300 using XDA App
johndiblasi said:
I love my skyradier 3.3.3 final Rom and I am not interested in this update how do I get It to stop bothering me every half hour to update. It's annoying.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Um... why did you post in this thread?
And to make it stop, I found this in another thread:
Code:
Get your build.prop from your /system/ folder
edit it
put this line in, not add it but replace the line that starts like this ro.build.fingerprint=verizon_wwe/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Replace it with this
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
Replace your build.prop and reboot. I did it by just using root explorer, copying it to the sdcard, editing on my PC, then copying it back to the /system/ folder then reboot. It might nag you once more upon reboot, but ignore and close it and it wont ask anymore.
Thank you. Sorry I posted it here I could not find anything relevant to my problem .
Sent from my ADR6300 using XDA App
Here you go
Applying November 2010 OTA to STOCK 2.2/FroYo rooted Incredible
Bob Denny said:
Here you go
Applying November 2010 OTA to STOCK 2.2/FroYo rooted Incredible
Click to expand...
Click to collapse
Bob.... thanks a ton. As the brits say "you're a star".. just did it and everything went nice and smooth (well...except the link to the update itself... I kept getting an error when trying to apply it. Found the update on my phone and just used that)
Just did a backup... and removed the crapware again. Thanks a ton!
Can someone link to the crapware apk's? I didn't back them up before I removed them.
Bob, you saved my life. Thank you so much!
Thanks Bob, worked perfectly for me. I copied over some of my disabled apps to the wrong folder, so I got an error the first time trying to install the update. Moved them to the right folder, and the update worked perfectly!
Thanks for the info, it helped me as well! I knew being S-Off would come in handy!
Thanks Bob, worked perfectly for me as well
Question about the "** STOCK 2.2 ONLY - READ MY LIPS SUCKA! **" statement...
Does ODEX vs DEODEX matter?
I got a question regarding the link that Bob posted. in the step 13 where you need to Copy ClockWork Recovery 2.5.0.5 (PB31IMG).zip to just plain PB31IMG.ZIP on the SD root.
When I do that and boot into HBOOT nothing is happening and when i go to recovery it just shows a red triangle and exclamation point.
am i doing something wrong or what? i am S-OFF and the update installed smoothly, i didn't have any of those apps running and i didn't remove my crap ware so i didnt' have to restore that either.
newbie question
What steps would be different if you were trying to do this on a Mac?
I rooted my Incredible using unrEVOked one click root to get wireless tether, that's all I have done. I would like the OTA, but still leery of doing this until I know what is different.
I'm reading all the posts trying to figure out what would be different. Can anyone help me.
Thanks in advance from a total newbie.
So I'm in the same boat as some. I removed (through titanium backup) all the crap-ware including FriendStream. Unfortunately, I can no longer reinstall the apps via titanium so I need to know how to get them back on the phone. When I try to run the update, I always get the error that it was aborted because of FriendStream odex blah blah blah. Help please!
UPDATE!
Problem solved. I downloaded the new RUU which includes the November update and just went from there. Yeah, it wiped the phone and I had to reinstall everything but it was worth it.
Jikkan said:
So I'm in the same boat as some. I removed (through titanium backup) all the crap-ware including FriendStream. Unfortunately, I can no longer reinstall the apps via titanium so I need to know how to get them back on the phone. When I try to run the update, I always get the error that it was aborted because of FriendStream odex blah blah blah. Help please!
UPDATE!
Problem solved. I downloaded the new RUU which includes the November update and just went from there. Yeah, it wiped the phone and I had to reinstall everything but it was worth it.
Click to expand...
Click to collapse
For future reference, this is what you were looking for: http://www.chadhaney.com/droidIncDefault/
I have a rooted Galaxy S3 with stock rom.
I keep getting a pop up for a system update, but cant update.
Please tell me how to manually update, and (where) I can find the latest stock updated software
Thanks
Voodoo8648 said:
I have a rooted Galaxy S3 with stock rom.
I keep getting a pop up for a system update, but cant update.
Please tell me how to manually update, and (where) I can find the latest stock updated software
Thanks
Click to expand...
Click to collapse
Take a look in the android dev sections to this forum. If you ever update once rooted, you should be flashing a new ROM (clean or dirty flashing) to receive the next update. Running stock ROM in between a Sammy update and while having the older ROM without the newest update will yield that result.
Xontic said:
Take a look in the android dev sections to this forum. If you ever update once rooted, you should be flashing a new ROM (clean or dirty flashing) to receive the next update. Running stock ROM in between a Sammy update and while having the older ROM without the newest update will yield that result.
Click to expand...
Click to collapse
I dont know what any of that means.. I just want to update my phone. This cant be brain surgery.
Voodoo8648 said:
I dont know what any of that means.. I just want to update my phone. This cant be brain surgery.
Click to expand...
Click to collapse
This might be a foolish question, but why root your phone to leave it as is?
Xontic said:
This might be a foolish question, but why root your phone to leave it as is?
Click to expand...
Click to collapse
Wonderful question. I would LOVE to unroot my phone :good:
lol, well if you want to read up on installing a custom ROM, then that is your ticket to experiencing the world of rooted phone glory. If not, I recommend looking up the unroot method...
Xontic said:
This might be a foolish question, but why root your phone to leave it as is?
Click to expand...
Click to collapse
There are plenty of reasons for rooting but remaining stock (such as: tethering, Droid wall, Titanium Backup to allow me to backup and restore app data, removing bloat, etc).
I have flashed custom rooms in the past on my Evo but right now I am happy with my S3 at stock.
Sent from my SPH-L710 using xda app-developers app
Xontic said:
lol, well if you want to read up on installing a custom ROM, then that is your ticket to experiencing the world of rooted phone glory. If not, I recommend looking up the unroot method...
Click to expand...
Click to collapse
Oh, okay, Thanks for the help!
Voodoo8648 said:
I have a rooted Galaxy S3 with stock rom.
I keep getting a pop up for a system update, but cant update.
Please tell me how to manually update, and (where) I can find the latest stock updated software
Thanks
Click to expand...
Click to collapse
I was in the same boat at you. I put it off for a while but finally decided to update tonight. I followed the steps posted here.
You can update your baseband by flashing a properly packaged official baseband zip, or flash from recovery tool (my preference), like the one here: http://forum.xda-developers.com/showthread.php?p=29820376. There are also unofficial, or leaked basebands, available to flash from all-in-one zips, such as the one here: http://goo.im/devs/freeza/Galaxy-S-fre3-LIGFirmwareModemAIO.zip.
As far as the build version goes, that does not have to match your baseband (modem). Most of the ICS ROMs are LG8, although there are some LI3 ICS ROMs to choose from. There's also a leaked build of Jellybean, builds LIF & LIG, with a third leak LIH reportedly coming out tomorrow. Once rooted, you can update your build version by flashing the ROM of your choice, based upon the build of your choice.
One of the top developers, and probably the greatest asset to this community, is freeza. He explained the difference very well here: http://forum.xda-developers.com/showthread.php?p=32095775
That's a long-winded response, but I hope it answered your original question, and helps you out.
Have fun!
Edit: Once you're rooted, you'll still receive OTA update notifications, which will continually annoy you until you choose to update and reboot. Once you reboot, the update will fail because of your custom recovery (you will NOT lose root) and the notification will go away....until the next OTA...
Sent from my SPH-L710 using xda premium
m20120 said:
I was in the same boat at you. I put it off for a while but finally decided to update tonight. I followed the steps posted here.
Click to expand...
Click to collapse
Excuse me for my stupidity but I'm new to android. I'm also using the sprint variant of the s3 and have it rooted with stock rom. However my build number is IMM76D.L710VPALF9. I'm assuming the last 3 are the update versions. What is the current version and how do I update to it?
Also, I'm rooted with Clockwork mod 5.5.0.4. How do I upgrade this to version 6.0.1.2? Will I have to unroot then root again?
Thanks for clearing anything you can up. Don't mean to pirate the OP but I figured I'd post in this thread rather than make a new one. Thanks again.
johnnygabe89 said:
Excuse me for my stupidity but I'm new to android. I'm also using the sprint variant of the s3 and have it rooted with stock rom. However my build number is IMM76D.L710VPALF9. I'm assuming the last 3 are the update versions. What is the current version and how do I update to it?
Also, I'm rooted with Clockwork mod 5.5.0.4. How do I upgrade this to version 6.0.1.2? Will I have to unroot then root again?
Thanks for clearing anything you can up. Don't mean to pirate the OP but I figured I'd post in this thread rather than make a new one. Thanks again.
Click to expand...
Click to collapse
You can flash a new recovery using ODIN, or Mobile ODIN. I use Mobile ODIN. There's a thread on recoveries here: http://forum.xda-developers.com/showthread.php?p=31894089
As far as the versions, see my previous post on this thread.
Sent from my SPH-L710 using xda premium
Can anyone tell me how to just UNROOT?
Maybe step by step instructions and where to get the software?
Thanks
Voodoo8648 said:
Can anyone tell me how to just UNROOT?
Maybe step by step instructions and where to get the software?
Thanks
Click to expand...
Click to collapse
There is a link to a video of the unroot process in this post.
I just discovered a reason NOT to unroot...
I just found out that I can tether free wifi hotspot!
Zoing!:victory:
Voodoo8648 said:
I just discovered a reason NOT to unroot...
I just found out that I can tether free wifi hotspot!
Zoing!:victory:
Click to expand...
Click to collapse
That is one of the reasons that I am rooted... so I can use WiFi Tether. I do not it much. Hardly any data at all. But when I am in a spot and need a wireless connection and I only have my phone it comes in handy.
Some other reasons:
- DroidWall: Lets me block individual apps from accessing the internet.
- AddFree: Block ads in some apps.
why would you do that?
Xontic said:
This might be a foolish question, but why root your phone to leave it as is?
Click to expand...
Click to collapse
so you don't have to pay Sprint 12 dollars a month to teather.
Hello everyone.
I've been having this problem for quite some time now, actually since i first rooted my phone back in summer 2011. Since then, whenever a new update was released I was unable to install it. I keep recieving an error i've not yet been able to find answers to. So now I'am kindly asking if any of you can help me get rid of it. I wont do a clean install "again"...
Here's the related screenshots: (same album)
imgurDOTcom/a/keZcZ#DH3LOOP
imgurDOTcom/a/keZcZ#u1Y1gMB
Thanks in advance.
Drixi said:
Hello everyone.
I've been having this problem for quite some time now, actually since i first rooted my phone back in summer 2011. Since then, whenever a new update was released I was unable to install it. I keep recieving an error i've not yet been able to find answers to. So now I'am kindly asking if any of you can help me get rid of it. I wont do a clean install "again"...
Here's the related screenshots: (same album)
imgurDOTcom/a/keZcZ#DH3LOOP
imgurDOTcom/a/keZcZ#u1Y1gMB
Thanks in advance.
Click to expand...
Click to collapse
You have modified a system file. This causes an OTA update to fail. Get the original applicationsprovider.apk for you current stock image and try again.
Drixi said:
Hello everyone.
I've been having this problem for quite some time now, actually since i first rooted my phone back in summer 2011. Since then, whenever a new update was released I was unable to install it. I keep recieving an error i've not yet been able to find answers to. So now I'am kindly asking if any of you can help me get rid of it. I wont do a clean install "again"...
Here's the related screenshots: (same album)
imgurDOTcom/a/keZcZ#DH3LOOP
imgurDOTcom/a/keZcZ#u1Y1gMB
Thanks in advance.
Click to expand...
Click to collapse
You are either not running a stock ROM, or you are trying to flash a takju update on a yakju ROM. Have a look at the OTA update thread in the General section. There are instructions on how to replace the system files. (Easiest would be to flash the system.img file from the factory image of the version you are currently running, and then the update will install.)
By the way, the GNex was not even out in summer 2011...
Petrovski80 said:
You have modified a system file. This causes an OTA update to fail. Get the original applicationsprovider.apk for you current stock image and try again.
Click to expand...
Click to collapse
efrant said:
You are either not running a stock ROM, or you are trying to flash a takju update on a yakju ROM. Have a look at the OTA update thread in the General section. There are instructions on how to replace the system files. (Easiest would be to flash the system.img file from the factory image of the version you are currently running, and then the update will install.)
By the way, the GNex was not even out in summer 2011...
Click to expand...
Click to collapse
2012* Typo ftw But thanks.
I'am using a stock ROM, unless the website was trolling and changed the filename on a non-stock ROM And I'am pretty sure that I did not mix up takju/yakju. I went trough everything a couple of times back then because I didnt want to mess up my phone - Look how that went -.-'
Anyway. A modified system file seem possible. How this happened, I'am unsure off, but I wont disagree that I didnt do something that might have caused this. I'll try the related solution tomorrow and post results.. Thanks guys - Amazingly fast answers
Drixi said:
2012* Typo ftw But thanks.
I'am using a stock ROM, unless the website was trolling and changed the filename on a non-stock ROM And I'am pretty sure that I did not mix up takju/yakju. I went trough everything a couple of times back then because I didnt want to mess up my phone - Look how that went -.-'
Anyway. A modified system file seem possible. How this happened, I'am unsure off, but I wont disagree that I didnt do something that might have caused this. I'll try the related solution tomorrow and post results.. Thanks guys - Amazingly fast answers
Click to expand...
Click to collapse
Note that a deodexed ROM is not stock, regardless of whether someone calls it stock or not.
efrant said:
Note that a deodexed ROM is not stock, regardless of whether someone calls it stock or not.
Click to expand...
Click to collapse
Could this can happen on source built, deodexed ROMs when build.prop is edited (product name, model, build) to match stock aka factory images?
Edit: the OTA update I mean
Sent from my Nexus
bk201doesntexist said:
Could this can happen on source built, deodexed ROMs when build.prop is edited (product name, model, build) to match stock aka factory images?
Edit: the OTA update I mean
Sent from my Nexus
Click to expand...
Click to collapse
Since stock ROMs are Odexed I don't see it making a difference.
063_XOBX said:
Since stock ROMs are Odexed I don't see it making a difference.
Click to expand...
Click to collapse
it wouldnt make a difference. the rom does not match what the OTA is expecting.
during the apply_patch process, a check is run to make sure everything matches what it should.
063_XOBX said:
Since stock ROMs are Odexed I don't see it making a difference.
Click to expand...
Click to collapse
Yes, but it would receive the notification, right? Hmm, I need to remove update system.
Sent from my Nexus
bk201doesntexist said:
Yes, but it would receive the notification, right? Hmm, I need to remove update system.
Sent from my Nexus
Click to expand...
Click to collapse
yes it would receive the update notification.
Do u have cwm installed? If so that would also caused your ota to fail.
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Do u have cwm installed? If so that would also caused your ota to fail.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
no it doesnt.
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:
Hey Guys,
I'm trying to apply the OTA update to move to KitKat but I've tried it twice now and both times before it even starts doing anything on the installation after turning off, I get a dead android icon with a red triangle and an exclamation point. I figured this issue was due to me removing some packages to uninstall bloat but I restored all the ones I backed up and I'm not sure if I'm missing something. I'm rooted using the saferoot on 98.30.1.XT907.Verizon.en.US. How can I get my phone to update? I'm aware that I'll lose root but it's not imperative for me. I really only use it to get rid of ads using AdAway. Thanks in advance!
Is there a way to get the apk's for all the system installed apps that come with the Droid RAZR M? I could go through and install the ones I'm missing that way. I thought I backed up any ones that I was removing so that this wouldn't happen when a new OTA came out but apparently not.
Your best bet will likely be to RSD back to stock and then take the OTA.
Sent from my Nexus 7 using XDA Free mobile app
Coronado is dead said:
Your best bet will likely be to RSD back to stock and then take the OTA.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
So I would just want to use RSDLite from here - http://www.4shared.com/zip/uOa2HVb9/RSDLite616.html
And then download the same version of Android I have now (98.30.1.XT907.Verizon.en.US) from here - http://sbf.droid-developers.org/phone.php?device=8 and install that?
You could flash the new firmware right away.
http://forum.xda-developers.com/showpost.php?p=52755934&postcount=229.
lem22 said:
You could flash the new firmware right away.
http://forum.xda-developers.com/showpost.php?p=52755934&postcount=229.
Click to expand...
Click to collapse
Would that do a factory reset in the process? I just want to know if I need to backup my pictures before hand. I haven't had a problem with doing OTA's and losing pictures but I guess if there's some in there I want to keep I should back them up anyways. I don't really use my phone for many pictures though.
Using the linked files it shouldn't delete user data (wipe), but some system settings will get reset.
Please see this thread.
gjriehl said:
Hey Guys,
I'm trying to apply the OTA update to move to KitKat but I've tried it twice now and both times before it even starts doing anything on the installation after turning off, I get a dead android icon with a red triangle and an exclamation point. I figured this issue was due to me removing some packages to uninstall bloat but I restored all the ones I backed up and I'm not sure if I'm missing something. I'm rooted using the saferoot on 98.30.1.XT907.Verizon.en.US. How can I get my phone to update? I'm aware that I'll lose root but it's not imperative for me. I really only use it to get rid of ads using AdAway. Thanks in advance!
Click to expand...
Click to collapse
I would use house of moto. It reflashed the system, boot.img, etc, and I kept all of my data. When it booted up, I took the update just fine. Here's a link to the forum: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-22/
Sent from my XT907 using xda app-developers app
lem22 said:
You could flash the new firmware right away.
http://forum.xda-developers.com/showpost.php?p=52755934&postcount=229.
Click to expand...
Click to collapse
Well I went this route and it worked great. Thanks!
gjriehl said:
Well I went this route and it worked great. Thanks!
Click to expand...
Click to collapse
So we can follow the instructions for this coming from any rom?
romma1 said:
So we can follow the instructions for this coming from any rom?
Click to expand...
Click to collapse
I'm not sure on that. I was on the stock rom to begin with but I had removed some bloat (thought I had backups for everything but I guess not) and after restoring it all it wouldn't install. Tried it twice to no avail. Then just grabbed the KK update zip file and RSD'ed it over and it was done in about 5-10 min. Phone was running slow while Google Play went and downloaded updates for all my apps but it's running beautifully now.
romma1 said:
So we can follow the instructions for this coming from any rom?
Click to expand...
Click to collapse
Yes, as long it's the same or a newer system version you're flashing: You can restore your version, you can upgrade it to a newer one, but to downgrade the bootloader has to be unlocked.
lem22 said:
Yes, as long it's the same or a newer system version you're flashing: You can restore your version, you can upgrade it to a newer one, but to downgrade the bootloader has to be unlocked.
Click to expand...
Click to collapse
I am unlocked. Thank you...
Truth be told, I never tried to downgrade from KitKat, so maybe there's something different now, but I believe it works, just as a downgrade from JB to ICS.