tombob
Well-Known Member
Use adb to reboot into recovery then restore your backup.
-
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?
- Thread starter JesusMuhammad
- Start date
-
- Tags
- lg marquee
lMonsterl
Android Expert
if you dont have cwm recovery you will need to downgrade back using kdzu
sik00
Android Enthusiast
http://androidforums.com/marquee-all-things-root/499597-stock-recovery.html#post4077658
Follow the instructions in the xda post to reflash LS855ZV9 if you're unable to access CWM.
Also, I would refrain from installing ROM Manager, and use the basic CWM image.
Edit: Ninja'd by Monster
ndno
Well-Known Member
Guys this is an update with a lot of changes to system so you need to let it sit for a while to allow the apks to install. If you wipe data then it will take even longer. Mine sat at that screen over 5 mins. Be patient and let the update do its thing
tombob
Well-Known Member
Good point, although I had let mine sit for 15+ minutes before I gave up on it. I'll probably give it another try tonight and see what happens. Thanks.
I went and took a shower while it rebooted, so it was somewhere around 15-20 minute with no response.
Anyway, currently doing trying the KDZ recovery technique, but it's not completing. At some point after it connects to the phone, I'm getting "Upgrade Error WParam: 100 LParam: 55" as an error message, and "MOD UpTestEX MFC Application has encountered a problem and needs to close".
lMonsterl
Android Expert
do it with your phone completely off then start kdz
Thanks, got everything restored, and then went through the process again for Asadullah's update (this time directly through CWM instead of ROM Manager). Version number now reports LS855ZVC, thank you very much.
I was on rooted sprint stock with CWM installed.
I flashed Asadullah's zip from CWM, and though it seemed to install fine, my software version wasn't showing the ZVC version and I was still being prompted to install the updated. (The radio did show ZVC version though).
I remembered I had tried a couple of mods on build.prop, so I restored the original build.prop. After I flashed the zip again, I am now seeing ZVC software version and no more update notices!
So reminder to build.prop modders, restore the original before you flash the zip. Thanks to Asadullah!
I flashed Asadullah's zip from CWM, and though it seemed to install fine, my software version wasn't showing the ZVC version and I was still being prompted to install the updated. (The radio did show ZVC version though).
I remembered I had tried a couple of mods on build.prop, so I restored the original build.prop. After I flashed the zip again, I am now seeing ZVC software version and no more update notices!
So reminder to build.prop modders, restore the original before you flash the zip. Thanks to Asadullah!
I tried Asadullah's method multiple times last night, but afterward I couldn't download from market b/c it would say "insufficient space." Reading about that error said that it could be a CWM issue, but I'm not sure of that, especially since nobody else is reporting this error.
Anyways, I eventually gave up and just updated to ZVC via Stock and the phone runs very fast and smooth. I don't use root features that often so it'll be alright. I will probably try to root again later when more methods/roms/info is available.
Never the less, thanks Marquee tweakers for your efforts!
Anyways, I eventually gave up and just updated to ZVC via Stock and the phone runs very fast and smooth. I don't use root features that often so it'll be alright. I will probably try to root again later when more methods/roms/info is available.
Never the less, thanks Marquee tweakers for your efforts!
ndno
Well-Known Member
Same problem here. I can't install titanium pro, it said out of space. I searched and people said it may be related to the market. I tried uninstalling the Google play update and now it won't run. I may switch to imonster MB rom. By the way I didn't clear data because I didn't want to lose my settings. That may have been the issues there
mbwd
Member
I have the same problem. Was able to upgrade to ZVC using Asadullah's method, but then couldn't access market because of "insufficient space."
If it helps anyone figure out the problem, after using the Asadullah update, I got these errors in CWM:
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
I checked and it is not the case that my internal memory is fried.
Also, every time I boot into the ZVC with root, I get an "Update Firmware" screen stating that it is "Checking for Firmware update" - but it eventually says no firmware update found.
UPDATE: So I was able to "fix" this by rebooting into CWM, wiping the cache and repairing permissions. So far, so good. Can download and install apps from the Play store.
If it helps anyone figure out the problem, after using the Asadullah update, I got these errors in CWM:
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
I checked and it is not the case that my internal memory is fried.
Also, every time I boot into the ZVC with root, I get an "Update Firmware" screen stating that it is "Checking for Firmware update" - but it eventually says no firmware update found.
UPDATE: So I was able to "fix" this by rebooting into CWM, wiping the cache and repairing permissions. So far, so good. Can download and install apps from the Play store.
Bionic Chronic
Android Enthusiast
Just wanted to chime in on this for a second, though I am on Boost, I did use |Monster|'s Update Method and at the end of installing boostupdate.zip I also received the same errors:
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
So far everything seems to be running ok though, had no issues with Google Play Store. I have noticed that I cannot send E-mails via Gmail.apk, but can receive them. I am sure that will get ironed out at some point. Just thought I would mention it.
Great to hear! I also had those errors in CWM. I'm in no hurry to try this again as I spent at least 4hrs on it yesterday(my 16GB sdcard wasn't playing nice either), but I'll give it another go in the coming days.
ndno
Well-Known Member
Finally gave in and just did a data factory reset wipe under cwm and everything is good again. I can now install titanium pro and restore my apps and data and other customizations
mbwd
Member
Just wanted to post that there are some lingering problems in case anyone else is experiencing the same. I will update as I work through them:
1) can't seem to keep Launcher Pro as default launcher. I've changed it a number of times using home switcher. But Android's default keeps coming back.
2) Update firmware screen comes back every few reboots.
1) can't seem to keep Launcher Pro as default launcher. I've changed it a number of times using home switcher. But Android's default keeps coming back.
2) Update firmware screen comes back every few reboots.
tombob
Well-Known Member
I use LauncherPro also, but have not experienced either of these problems.
ndno
Well-Known Member
X
If you have titanium backup just back up your data and apps. Then boot to cwm, do a data factory reset wipe, then install the update, the restore your apps and data after you boot up. I had miscellaneous problems without doing a wipe.
You may need to use the original build.prop before the update to eliminate the update message. I had tweaked mine and was getting the same lingering update message until I tried again with the stock build.prop
If you have titanium backup just back up your data and apps. Then boot to cwm, do a data factory reset wipe, then install the update, the restore your apps and data after you boot up. I had miscellaneous problems without doing a wipe.
You may need to use the original build.prop before the update to eliminate the update message. I had tweaked mine and was getting the same lingering update message until I tried again with the stock build.prop
I've never used KDZ before so didn't know if it worked because I got an error, then force close. Also some of the things mentioned in the README did not happen like the phone going into emergency mode and rebooting. Seems nothing changes on the phone during the process. This is what it looked like.
Is everything looking like it should be? Also should I have selected CDMA or CDMA-smartphone(wm) rather than 3GQCT?
Is everything looking like it should be? Also should I have selected CDMA or CDMA-smartphone(wm) rather than 3GQCT?
I've never used KDZ before so didn't know if it worked because I got an error, then force close. Also some of the things mentioned in the README did not happen like the phone going into emergency mode and rebooting. Seems nothing changes on the phone during the process. This is what it looked like.
Is everything looking like it should be? Also should I have selected CDMA or CDMA-smartphone(wm) rather than 3GQCT?
I've used that recovery twice now with good luck. I have used 3GQCT -SmartPhone(WM ..........as stated in the post on XDA Reflashed stock firmware on LG Marquee - xda-developers
I'm on Sprint, hopefully someone with boost could also chime in.
ethanhunteg
Newbie
I don't know if its your issue, but probably don't run the program nor have the kdz firmware file located on a different device. Copy it over to your hard drive first and run it from there
mbwd
Member
Thanks. The firmware update stopped showing up on reboot.
The Launcher Pro issue did not resolve -- though I did a restore from a Titanium Backup backup -- until I deleted the stock Android launcher. Now its fine. Not that it has any choice in the matter.
I haven't noticed that the snappier response that some folks report using ZVC. I just played with my overclocked Optimus S for a bit, and its still much more responsive than the Marquee.
The Launcher Pro issue did not resolve -- though I did a restore from a Titanium Backup backup -- until I deleted the stock Android launcher. Now its fine. Not that it has any choice in the matter.
I haven't noticed that the snappier response that some folks report using ZVC. I just played with my overclocked Optimus S for a bit, and its still much more responsive than the Marquee.
ndno
Well-Known Member
Yeah, I don't think this is a performance improvement update. It probably fixed a few things and update the radio firmware. There may be other enhancements but that doesn't necessarily mean speed improvement. If you want speed maybe try imonster's MB rom . I'm still using stock with tweaks and launcher pro which is pretty fast
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?
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?