• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Sprint update LS855ZVC kills root. Solutions?

Okay since the last post, i got kdz working, I just had to run it with the phone off, then turn it on.

Successfully went back to stock ZV9, rooted, CWM installed. Then I flashed Sprintupdate.zip and verified it was ZVC, all is well, rooted and CWM.

Here is the next problem: So my next step, I flashed to Playfulgod Undeniable ROM. I received notification about a system update so I looked in my info and it said mine is still on ZV9. So I rebooted into cwm and install sprintupdate.zip.

Now my phone hangs at the LG logo and the soft key leds are blinking. Still have cwm and backups but wondering what I did wrong? Was I suppose to differently? "apply update from sdcard" rather than install zip from sd? How do I get Undeniable with ZVC?

I'm not sure he released undeniable ZVC version yet. I know his rom is deodexed so maybe that is why you are having issues? I think the ZVC update that was modded was for the stock ZV9 software so you can root. By applying the update to undeniable would be counter productive wouldn't it? You get all the bloat software and isn't deodexed. For sprint users I think either stick with the stock software with the mod update patch of ZVC so you can root or run undeniable and wait for an update that removes the bloatware.
 
I'm not sure he released undeniable ZVC version yet. I know his rom is deodexed so maybe that is why you are having issues? I think the ZVC update that was modded was for the stock ZV9 software so you can root. By applying the update to undeniable would be counter productive wouldn't it? You get all the bloat software and isn't deodexed. For sprint users I think either stick with the stock software with the mod update patch of ZVC so you can root or run undeniable and wait for an update that removes the bloatware.
Could use Marky Beats v1.2zvc for Sprint:
http://androidforums.com/marquee-al...-zvc-marky-beats-v1-2-beta-updated-4-6-a.html
 
I tried that one for sprint for some reason the camera button (aux button) wouldn't operate the camera, bluetooth wasn't working either. Maybe I did something wrong when I had to replace the build.prop to correct the sprint build that was set for boost mobile.
Well it is still in Beta stage.. It was just an alternate option over stock.. I myself have MB v1.2zvc beta for boost and there are a couple issues but, I find it better compared to stock.
 
Thanks for clearing that up. I'll check out Marky Beats. But if I decide to stay with Undeniable, how could I get rid of the system update prompt?
 
Thanks for clearing that up. I'll check out Marky Beats. But if I decide to stay with Undeniable, how could I get rid of the system update prompt?
Install the update that downloads to your phone when your using undeniable. The update will fail when you try to install and you wont get bothered by the pop up msg anymore.
 
*If you already installed the update only*
Can also try going into CWM and first doing a cache wipe, then go to advanced and choose fix permissions. (may take a little time with fixing permissions, just give it time.) See if that helps..

Sent from my LG-LG855 using Tapatalk 2 Beta-5
 
Okay since the last post, i got kdz working, I just had to run it with the phone off, then turn it on.

Successfully went back to stock ZV9, rooted, CWM installed. Then I flashed Sprintupdate.zip and verified it was ZVC, all is well, rooted and CWM.

Here is the next problem: So my next step, I flashed to Playfulgod Undeniable ROM. I received notification about a system update so I looked in my info and it said mine is still on ZV9. So I rebooted into cwm and install sprintupdate.zip.

Now my phone hangs at the LG logo and the soft key leds are blinking. Still have cwm and backups but wondering what I did wrong? Was I suppose to differently? "apply update from sdcard" rather than install zip from sd? How do I get Undeniable with ZVC?

When you flashed Playfulgod Undeniable ROM, the build.prop was changed back to ZV9 (from ZVC to ZV9). If you go to Settings->About Phone, it reads the version from build.prop. So that's what you're experiencing.

If you have ZVC already, you shouldn't install Playfulgod's ROM, because that is based off the old ZV9. You're just really re-installing an old ROM over a newer ROM. If anything, if you have ZVC and want to flash a ROM that is ZVC-based, use Monster's MB ROM; he's already updated his ROM to base off ZVC's update.

One way to disable the system update message (since you have ZV9 after updating to Undeniable ROM) is to edit build.prop and change ZV9 to ZVC; you will need to use Root Explorer or something similar to mount /system as R/W so that you can edit build.prop. I haven't tried this but I think this should work; the system update is checking the version in build.prop to see if you have ZVC, if not, it will bring up the update notification message.
 
I am trying to downgrade with kdz and my phone is not found i have installed lg pc suite and it fails to get my imei ive disabled the virtual modem tried different ports and cords all of the suggestions listed and still nothing the phone does not show under usb serial controllers which was advised but im not sure how to do that any suggestions??
 
The update seems to be more harm than good on my end. How do I stop the update notification from coming up after reverting back?
You can delete the update zip in your /cache folder. No guarantees it will not come back, though. Have you tried the updated zips that allow you to keep superuser and CWM?
Sprint update
Boost update

Just out of curiosity, what type of problem are you having with the update? I didn't have problems with the original firmware aside from the intermittent call lock-up bug. I haven't had any troubles with the update.
 
You can delete the update zip in your /cache folder. No guarantees it will not come back, though. Have you tried the updated zips that allow you to keep superuser and CWM?
Sprint update
Boost update

Just out of curiosity, what type of problem are you having with the update? I didn't have problems with the original firmware aside from the intermittent call lock-up bug. I haven't had any troubles with the update.

So my girl tried updating her phone while we were on vacation last week to ZVC. For some reason only the baseband updated while the software stayed at ZV9. I still have root, CWM intact however whenever I flash that sprintupdate.zip, the s/w version stays at ZV9 and I get these errors as stated before

E: can't mount /cache/recovery/command
E: can't mount /cache/recovery//log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log

and the market ("google play") has that insufficient memory error. So I reverted back to the backup I made.
 
So my girl tried updating her phone while we were on vacation last week to ZVC. For some reason only the baseband updated while the software stayed at ZV9. I still have root, CWM intact however whenever I flash that sprintupdate.zip, the s/w version stays at ZV9 and I get these errors as stated before

E: can't mount /cache/recovery/command
E: can't mount /cache/recovery//log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log

and the market ("google play") has that insufficient memory error. So I reverted back to the backup I made.


cmon man...its only few posts back on how to fix this. try reading through the entire thread before posting

thx to mbdw for updating the following post:
http://androidforums.com/marquee-all-things-root/524903-sprint-update-ls855zvc-kills-root-solutions-2.html#post4188471

& ndno for this one:
http://androidforums.com/marquee-all-things-root/524903-sprint-update-ls855zvc-kills-root-solutions-2.html#post4190780
 
cmon man...its only few posts back on how to fix this. try reading through the entire thread before posting

thx to mbdw for updating the following post:
http://androidforums.com/marquee-all-things-root/524903-sprint-update-ls855zvc-kills-root-solutions-2.html#post4188471

& ndno for this one:
http://androidforums.com/marquee-all-things-root/524903-sprint-update-ls855zvc-kills-root-solutions-2.html#post4190780

If you read my other posts you would've known I've tried those already.
 
So my girl tried updating her phone while we were on vacation last week to ZVC. For some reason only the baseband updated while the software stayed at ZV9. I still have root, CWM intact however whenever I flash that sprintupdate.zip, the s/w version stays at ZV9 and I get these errors as stated before

E: can't mount /cache/recovery/command
E: can't mount /cache/recovery//log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log

and the market ("google play") has that insufficient memory error. So I reverted back to the backup I made.
You're on baseband ZVC, but SW version ZV9 now, right? Just making sure I understand what state your phone is in now :o
Did the sprintupdate.zip give any errors when you installed, or only after it was installed? I've had the same errors after install, but like others, mine was fixed with wiping cache and fixing permissions.
The radio is one of the last things to get flashed in the update, and if you're running baseband ZVC, I would think it flashed successfully. For some reason is seems that the actual files for the SW update didn't go through?
 
So my girl tried updating her phone while we were on vacation last week to ZVC. For some reason only the baseband updated while the software stayed at ZV9. I still have root, CWM intact however whenever I flash that sprintupdate.zip, the s/w version stays at ZV9 and I get these errors as stated before

E: can't mount /cache/recovery/command
E: can't mount /cache/recovery//log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log

and the market ("google play") has that insufficient memory error. So I reverted back to the backup I made.
I am not sure about the Update, though I am on Boost, have had the same errors.. I was talking about it in this >Post<.
As for the Google Play Store.. You can try going to Settings>Applications>All and then Navigate to these 3 items: Download Manager, Google Services Framework, and Google Play Store. Select them one at a time and go to force stop and clear data. Then reopen Google Play store. Should be like opening it for the first time and should work. If not you could also try booting into CWM Recovery and Navigate to Advanced and then Fix Permissions (Takes a minute, don't worry just hang tight), then go back to CWM Main Page and wipe cache then Reboot. Hope this may be of some help.
__________________
=================
Helpful? Hit Thanks :)
=================
 
If you read my other posts you would've known I've tried those already.

I don't see in any of your posts that you wiped cache AND wiped data AFTER installing the sprintupdate.zip

1) back up your apps w/ Titanium Backup
2) put sprintupdate.zip onto your zip card
3) install zip from sdcard & choose sprintupdate.zip
4) wipe cache partition
5) wipe data/factory reset

see if that works...if not, have you done ANYTHING else that you haven't posted here??
 
I don't see in any of your posts that you wiped cache AND wiped data AFTER installing the sprintupdate.zip

1) back up your apps w/ Titanium Backup
2) put sprintupdate.zip onto your zip card
3) install zip from sdcard & choose sprintupdate.zip
4) wipe cache partition
5) wipe data/factory reset

see if that works...if not, have you done ANYTHING else that you haven't posted here??

I just did this and after flashing the baseband still says LS855ZVC while SW Version is still LS855ZV9. I think this is my 5th time flashing and it still hasn't updated.

I'm gonna try flashing back to pure stock.
 
I just did this and after flashing the baseband still says LS855ZVC while SW Version is still LS855ZV9. I think this is my 5th time flashing and it still hasn't updated.

I'm gonna try flashing back to pure stock.

If you use the original /system/build.prop (no tweaks, hacks, etc) that came with ZV9, the update should correctly patch the build.prop to say it's ZVC. Most likely, you have tweaked your build.prop before the ZVC update for whatever reasons (tweaks, zeppolinrox patches, etc); if that's the case when you update to ZVC, the process won't patch the build.prop correctly and hence it still says it's ZV9 in build.prop. This is what happened to me so I used the original stock build.prop before the ZVC update.

One way to stop the nagging pop-up update screen is to use root explorer (or anything equivalent that can mount /system as R/W) and edit the build.prop and change any "ZV9" references to "ZVC". You may need to reboot and wipe cache. I haven't tried this but I think it should work. The updating service is probably reading /system/build.prop and seeing if it ZVC is in there (even though you updated everything through the zip file); it not, it keeps popping up that window to tell you to update.
 
If you use the original /system/build.prop (no tweaks, hacks, etc) that came with ZV9, the update should correctly patch the build.prop to say it's ZVC. Most likely, you have tweaked your build.prop before the ZVC update for whatever reasons (tweaks, zeppolinrox patches, etc); if that's the case when you update to ZVC, the process won't patch the build.prop correctly and hence it still says it's ZV9 in build.prop. This is what happened to me so I used the original stock build.prop before the ZVC update.

One way to stop the nagging pop-up update screen is to use root explorer (or anything equivalent that can mount /system as R/W) and edit the build.prop and change any "ZV9" references to "ZVC". You may need to reboot and wipe cache. I haven't tried this but I think it should work. The updating service is probably reading /system/build.prop and seeing if it ZVC is in there (even though you updated everything through the zip file); it not, it keeps popping up that window to tell you to update.

I think you were right. Yes, I have made some tweaks in the past. I flashed back to stock and it finally took the update.
 
I think you were right. Yes, I have made some tweaks in the past. I flashed back to stock and it finally took the update.

Glad it worked out for you. I looked at the sprintupdate.zip and it doesn't replace the build.prop but instead patches it; this means it expects the build.prop to be original (if you know Linux, patches don't always work unless the original file is as close to what it expects, otherwise it will fail patching that file, in this case, it didn't update the version and hence the updating process constantly thinks you're still on version ZV9 even though all the other updates went through).
 
INFORMATION OVERLOAD hah... anyone download the upgrade on a stock lg marquee (besides root) and get your root back ? if so hook me up with a step by step... id like to be of more help but im just a rookie
 
Back
Top Bottom