Help Hoping This Isn't A Virus...

EvoVAlpha · Sep 13, 2015

As google is providing nothing with what I'm about to post and y'all aren't pipin up about it either, I'm thinking this could be a virus.

For the last couple weeks I've been unable to download the LS660ZV5_01_update.zip. The reason being that there's insufficient space to DL the zip file. Well there is more than enough space on the internal and external for the 70 meg file, but it still won't let me DL. Naturally the icon won't go away as well. So like I said, as I didn't find anything on this issue, yet, I wonder if this is a real system update. If so, any ideas how to actually get it? If not, virus!?!

Thanks in advance guys!

EvoVAlpha · Sep 13, 2015

So yeah, gonna update and ignore the fact that literally, as I posted this thread, I went to a tab I had opened up about the ACTUAL UPDATE, which I clearly should have read as opposed to posted this first! Soooo, bypassing that little embarrassment, obviously this isn't a virus, though I still can't DL it, so any ideas would be great, and or legit sources on the net.

HasH_BrowN · Sep 14, 2015

For the notification read the 5th post on this page
http://androidforums.com/threads/lg-tribute-stock-zv5-deodexed-unmodified-4-4-2.922509/page-7

About the download, is yours a Walmart phone? We got my wifes phone from there. From straight out of the box and activating, to getting notification about the update about 1 hour later. Nothing was installed prior, yet there wasnt any room for the 73 mb update. So I rooted it, then uninstalled some bloatware from the system and freed the space necessary (plus some). Update downloaded and installed fine. Read the 9th post on this page.
http://androidforums.com/threads/zv6-ota-released.943636
BTW when the update is downloaded it is stored in the root of internal SD, which is the system partition (1.37 GB), in /cache.

Indigaz · Sep 14, 2015

The LS660ZV6 update comes in at over 600MB or so, even though it says "73MB" needed for the download.

I had a hell of a time trying to get it worked out so that I could actually download it. Once I cleared some backups that were sitting on my "/storage/internalSD", I was finally able to get the update downloaded. The weird part, after downloading and installing the update, it went into a boot loop (which was cured with the process here) and fixed in TWRP. However, after finishing the ZV6 update, my phone still shows the current software version as ZV5. Even going into "System updates" and forcing a check with "Update LG software", it tells me that "Your system is up to date". Well, actually you're not Android, as I know there was a ZV6 OTA downloaded and installed.

Would someone have an idea as why it would still show ZV5 after multiple reboots and a "##72789#" done? Or perhaps a link to a side-loadable update?

Thanks!

HasH_BrowN · Sep 14, 2015

Indigaz said:
The LS660ZV6 update comes in at over 600MB or so, even though it says "73MB" needed for the download.

I had a hell of a time trying to get it worked out so that I could actually download it. Once I cleared some backups that were sitting on my "/storage/internalSD", I was finally able to get the update downloaded. The weird part, after downloading and installing the update, it went into a boot loop (which was cured with the process here) and fixed in TWRP. However, after finishing the ZV6 update, my phone still shows the current software version as ZV5. Even going into "System updates" and forcing a check with "Update LG software", it tells me that "Your system is up to date". Well, actually you're not Android, as I know there was a ZV6 OTA downloaded and installed.

Would someone have an idea as why it would still show ZV5 after multiple reboots and a "##72789#" done? Or perhaps a link to a side-loadable update?

Thanks!

The update is 73 mb, thats it!! I updated offline. What is being downloaded is the Virgin Mobile software, just open up the zip and you'll see.
I wrote the thread thats about the bootloop fix. Glad it helped you.
What I think happened is you got the zv5 update instead. Try wiping cache and dalvik, erasing the update in /cache and reboot. Wait and see if it updates again. Seriously though the update is only 73mb and thats large for just a "STAGEFRIGHT FIX".

EvoVAlpha · Sep 15, 2015

@HasH_BrowN - First thank you for the info! Second, I almost got it at Walmart but Best Buy instead, a bit cheaper. So then it's not all that important to worry about? I did uncheck the GPS notification but which took care of the icon. Thanks again!

HasH_BrowN · Sep 15, 2015

EvoVAlpha said:
@HasH_BrowN - First thank you for the info! Second, I almost got it at Walmart but Best Buy instead, a bit cheaper. So then it's not all that important to worry about? I did uncheck the GPS notification but which took care of the icon. Thanks again!

Really the stagefright fix is just the build.prop edit as fae as I know, the rest is files already there. The files on our device have a date of 2008, whereas the update files are from 2012. Im not really impressed with the update on my wifes phone, so I wont be updating mine. I already edited my build.prop.

Indigaz · Sep 15, 2015

That's odd, because I couldn't get the download until I had almost a GB freed up. When I first started attempting to get the update, I was at 470+MB free on my internal storage and it still wouldn't go. Perhaps I had it confused with the LG ZV6 source. BTW, where did you get the offline update?

Also, I was already at ZV5 before I started. I've had this phone since March or April. Everything had been fine and dandy and then I saw a notice for the OTA a couple days ago. I clicked on the notice and it went to the updater. I'm fairly certain that it had actually worked the first time as it went into the boot loop after it finished. In my panic, and before I had located the fix that you had written, I was certain that something was serious bad with it. I had a daily backup, so I simply wiped it to see if that would fix it. It did not fix the boot loop. So I Googled some and came across a XDA post that had the same fix as you posted. Ran the terminal commands and was back at my home screen. I checked the software version and it still showed ZV5, so I was sure that it didn't actually patch, so I restored my backup, checked again, still ZV5, tried to get the update forced, it keeps hanging saying that I had "insufficient space" when I had at least 5x the space it says it needs. That's when I started removing old files and moving a backup off the /storage/internalSD and after that and a few days of this, it finally does the download and patching again. Checked version, it still says ZV5 and says I'm current when I tell it to look again. While I was stuck at the "not-wanting-to-download" part, my battery was disappearing at an alarming rate, which I attributed to the fact that it was constantly attempting to download the patch. After all of this and getting the phone sorta back to the way it was before this boondoggle, the drain seems to be cured for the most part. For months now, I would generally go all day and only use 10% battery on average. It was shocking to see -10% in 30 minutes for the past couple days.

HasH, do you have a link for the offline ZV6 install? I've been trying to find it to no avail. Thanks again for your guide earlier! I didn't bookmark my first find of the instructions, so those were invaluable.

HasH_BrowN · Sep 15, 2015

Sorry for your issues. I should have clarified about the update, it was downloaded first online and then installed offline. The source code is ~683 mb, which when compiled becomes 73 mb.
The XDA post is also by me, should be post # 2055 in that monster thread on page ~204. I will upload the update to Mediafire later today for you. Itll be labeled "update.zip" @ 73 mb.
Go into /cache and delete any .zip, turn off notifications in Google Play Services app info page in your app manager. You can long press the notification to get there too. Itll stop the nag notification.

Indigaz · Sep 15, 2015

I appreciate your help HasH and look forward to dl'ing the update so I can eliminate the OTA issues I am having. Thanks!

HasH_BrowN · Sep 15, 2015

Here is the zv6 update directly from Virgin. (Untouched, lol...virgin-untouched). The only thing I did was rename it.
http://www.mediafire.com/?611tl6wg8bzec9v

Wesley Slaughter · Sep 17, 2015

I got a notification saying that I didnt have enough space. I cleared up some space and there was a button saying "Restart And Install" when i clicked it it took me to the recovery screen and theres no way out of it. Ive tried to reboot, take the battery out for a day, and even factory reseted it and its still stuck on the recovery screen. BTW I got it from walmart. It would be great if someone can solve this problem for me thanks.

HasH_BrowN · Sep 18, 2015

Wesley Slaughter said:
I got a notification saying that I didnt have enough space. I cleared up some space and there was a button saying "Restart And Install" when i clicked it it took me to the recovery screen and theres no way out of it. Ive tried to reboot, take the battery out for a day, and even factory reseted it and its still stuck on the recovery screen. BTW I got it from walmart. It would be great if someone can solve this problem for me thanks.

Read this thread I wrote
http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/
If it works for you, hit the like button on that page.

It works for Walmart versions as well.

Please read the comments as well to help you. If you have any issues after reading, then please post them @ link provided above.

siryoink · Oct 4, 2015

Indigaz said:
The LS660ZV6 update comes in at over 600MB or so, even though it says "73MB" needed for the download.

I had a hell of a time trying to get it worked out so that I could actually download it. Once I cleared some backups that were sitting on my "/storage/internalSD", I was finally able to get the update downloaded. The weird part, after downloading and installing the update, it went into a boot loop (which was cured with the process here) and fixed in TWRP. However, after finishing the ZV6 update, my phone still shows the current software version as ZV5. Even going into "System updates" and forcing a check with "Update LG software", it tells me that "Your system is up to date". Well, actually you're not Android, as I know there was a ZV6 OTA downloaded and installed.

Would someone have an idea as why it would still show ZV5 after multiple reboots and a "##72789#" done? Or perhaps a link to a side-loadable update?

Thanks!

I was having this same issue, and searched everywhere for help. Was keeping up with this thread, but nothing worked. When I finally fixed mine, I signed up for this forum hoping I could help others. I had even done a Titanium backup and factory defaulted the phone, but it still wouldn't install.

If you have root and have ever had link2sd installed, the following will apply to you. If you have never used link2sd, skip to step #8 below.

If you check your last_log file after reboot, or if you tried to manually install the recovery, you will see a message indicating the update failed on a checksum check of file \system\bin\debuggerd . The problem lies in modifications link2sd made to this file that DO NOT get replaced during an uninstall, or even a factory reset.

The fix:
1. If you still have link2sd, uninstall it.
2. Use ES File Explorer or reboot browser and browse to \system\bin
3. Do you have a debuggerd and a debuggerd.bin in this directory?
4. Open debuggerd in a text editor and verify there is a line that says #added by link2sd
5. Rename debuggerd to debuggerd.old
6. Rename debuggerd.bin to debuggerd
7. Reboot
8. Go to Settings>Apps>All and open Google Play Services
9. Click "Manage Space" then "Clear all date"
10. Go to "System Updates" and "Update LG software"
11. Update will install

HasH_BrowN · Oct 4, 2015

siryoink said:
I was having this same issue, and searched everywhere for help. Was keeping up with this thread, but nothing worked. When I finally fixed mine, I signed up for this forum hoping I could help others. I had even done a Titanium backup and factory defaulted the phone, but it still wouldn't install.

If you have root and have ever had link2sd installed, the following will apply to you. If you have never used link2sd, skip to step #8 below.

If you check your last_log file after reboot, or if you tried to manually install the recovery, you will see a message indicating the update failed on a checksum check of file \system\bin\debuggerd . The problem lies in modifications link2sd made to this file that DO NOT get replaced during an uninstall, or even a factory reset.

The fix:
1. If you still have link2sd, uninstall it.
2. Use ES File Explorer or reboot browser and browse to \system\bin
3. Do you have a debuggerd and a debuggerd.bin in this directory?
4. Open debuggerd in a text editor and verify there is a line that says #added by link2sd
5. Rename debuggerd to debuggerd.old
6. Rename debuggerd.bin to debuggerd
7. Reboot
8. Go to Settings>Apps>All and open Google Play Services
9. Click "Manage Space" then "Clear all date"
10. Go to "System Updates" and "Update LG software"
11. Update will install

The link2sd wouldn't be the cause of the failed install, unless your linking system files - which you shouldn't do.
For those without link2sd, clearing the Google Play Services is not a definitive solution to not updating.

Failed install reasons

Deleted system files (missing)
Edited system files (changed)
Deodexed rom (incompatibilities)

I don't know why everybody is so set on this update. Its not anything more than a build.prop edit, that has got a radio.img (boot.img replacement) that breaks data connectivity and other things. It doesn't fix anything really, it more or less screws everything up. All the bloatware from the carrier is reinstalled. But hey its your phone.

siryoink · Oct 4, 2015

HasH_BrowN said:
The link2sd wouldn't be the cause of the failed install, unless your linking system files - which you shouldn't do.

This is absolutely false. Link2SD uses the debuggerd file as its insertion point for the script it uses to mount sd cards at boot time. It renames your existing debuggerd file to debuggerd.bin, and creates a new debuggerd file that runs the mount script and then launches debuggerd.bin to resume the normal startup process. This has absolutely nothing to do with linking system files, or even having any files linked - it's just how link2sd works. But this modified system file will cause your install to fail.

HasH_BrowN said:
For those without link2sd, clearing the Google Play Services is not a definitive solution to not updating.

Failed install reasons

Deleted system files (missing)

Edited system files (changed)

Deodexed rom (incompatibilities)

I don't know why everybody is so set on this update. Its not anything more than a build.prop edit, that has got a radio.img (boot.img replacement) that breaks data connectivity and other things. It doesn't fix anything really, it more or less screws everything up. All the bloatware from the carrier is reinstalled. But hey its your phone.

The real reason most of us want to install it is so the annoying install reminders will stop. I've had no connectivity issues since installing it, and it didn't load any bloatware back onto mine. I have the Sprint version, so any bloatware you're referring to is possibly from Virgin?

HasH_BrowN · Oct 4, 2015

siryoink said:
This is absolutely false. Link2SD uses the debuggerd file as its insertion point for the script it uses to mount sd cards at boot time. It renames your existing debuggerd file to debuggerd.bin, and creates a new debuggerd file that runs the mount script and then launches debuggerd.bin to resume the normal startup process. This has absolutely nothing to do with linking system files, or even having any files linked - it's just how link2sd works. But this modified system file will cause your install to fail.

The real reason most of us want to install it is so the annoying install reminders will stop. I've had no connectivity issues since installing it, and it didn't load any bloatware back onto mine. I have the Sprint version, so any bloatware you're referring to is possibly from Virgin?

I used link2sd on my wife's tribute, updated with out any fail/errors. There were connectivity issues but those are related to the radio.img. I also used Apps2sd by Vicky Bonick, also without update errors. There must be something else that's causing you error. Aside from checking/reinstalling bloatware, the updates are identical. This update was rushed out the door, there was no Q.C.. That's just poor strategic planning. Meanwhile in the aftermath we have to fix their laziness.
The bloatware reinstalled was on Virgin, so you guys on Sprint got lucky on that one.

As to the nag notification (which is not a reason to update, just a lack of user initiative and resourcefulness)

Settings>Apps>All tab>
Scroll to G.P.S. - Google Play Services
Unchecked notifications

Or this way
(The way I found out)

Long press notification
Tap app info
Uncheck notifications

No more nag notifications

siryoink · Oct 4, 2015

HasH_BrowN said:
I used link2sd on my wife's tribute, updated with out any fail/errors. There were connectivity issues but those are related to the radio.img. I also used Apps2sd by Vicky Bonick, also without update errors. There must be something else that's causing you error. Aside from checking/reinstalling bloatware, the updates are identical. This update was rushed out the door, there was no Q.C.. That's just poor strategic planning. Meanwhile in the aftermath we have to fix their laziness.
The bloatware reinstalled was on Virgin, so you guys on Sprint got lucky on that one.

HasH_BrowN said:
As to the nag notification (which is not a reason to update, just a lack of user initiative and resourcefulness)

^ Seriously?

HasH_BrowN said:
Settings>Apps>All tab>

Scroll to G.P.S. - Google Play Services

Unchecked notifications

Or this way
(The way I found out)

Long press notification

Tap app info

Uncheck notifications

No more nag notifications

Congrats to you for not having the problem. I already fixed mine, and signed up specifically to try to help others who do have the issue. I'm not speculating as to what caused it, I looked at the error logs and found the problem, at least in my case, to have been caused by link2sd. I posted how to fix it for anyone else who wanted to know. Yes, we could disable notifications, but I'd much rather fix the problem.

Came here offering assistance to someone, met with what is apparently the forum's most argumentative user tossing thinly veiled personal insults at me. I won't be logging in here again, good luck to anyone who still has this problem.

HasH_BrowN · Oct 4, 2015

siryoink said:
^ Seriously?

Congrats to you for not having the problem. I already fixed mine, and signed up specifically to try to help others who do have the issue. I'm not speculating as to what caused it, I looked at the error logs and found the problem, at least in my case, to have been caused by link2sd. I posted how to fix it for anyone else who wanted to know. Yes, we could disable notifications, but I'd much rather fix the problem.

Came here offering assistance to someone, met with what is apparently the forum's most argumentative user tossing thinly veiled personal insults at me. I won't be logging in here again, good luck to anyone who still has this problem.

Wow... who pissed in your Wheaties.
I stated my results.

How about post your logfile so others can see it.

As far as argumentative...no not in the least. You don't even state what the debuggered file is. A lot of people come here for advice and want to know each thing that they do, also what it does.
Thanks for you little tirade. I hope you feel better after venting.

Now are you willing to share the logfile? There are others that would like to dig into something like that. But that's up to you.

WarrantyVoider · Oct 8, 2015

OK, just sharing what I think I know here. Please correct me if I am wrong.

Re: Stagefright.
You can check whether the stagefright fix is applied with this:
https://play.google.com/store/apps/details?id=com.zimperium.stagefrightdetector
Build.prop edits don't fix the libs, which need to be patched to really fix the bugs.

Re: Phone showing ZV5 even after ZV6 update.
The update changes the version number in build.prop from ZV5 to ZV6 (the stagefright settings are still enabled, since the vulnerability is patched now). The change to build.prop occurs in the last step, after radio.img. If you were using TWRP to update, my guess is the update stopped at the radio.img step. I think not updating radio.img is fine, but that probably means build.prop is not updated.

Re: Link2SD causing update failure.
I have no experience with Link2SD. I have read elsewhere that one of the ways Link2SD triggers mounting of external partition at boot is by inserting itself as debuggerd. (My own SD hack uses vold, but I've also experimented with using debuggerd in the past.) If so, the update will not proceed because debuggerd is one of the files to be updated. The update first checks the files to be patched and it won't proceed if they have been modified. So uninstall Link2SD and/or restore the original debuggerd first. After successfully applying the update, reinstall Link2SD and/or restore the Link2SD modification.

Re: Space.
I am not sure about this, but I think maybe the cache partition is used for the update. If I'm right, clearing some cache space might help with this issue. The system partition obviously needs to have enough space, but that's automatically checked during the update process.

HasH_BrowN · Oct 8, 2015

@WarrantyVoider can the lib files for stagefright fix be manually updated?

Is using vold hack better than the debuggered way?

WarrantyVoider · Oct 8, 2015

HasH_BrowN said:
can the lib files for stagefright fix be manually updated?
Is using vold hack better than the debuggered way?

You can modify the official update.zip by removing commands that might cause issues. If you want to do this, I can look it up later.

I use vold as an entry point because it loads earlier than debuggerd. From a user's perspective, it doesn't matter much how a hack achieves its goal. How well a hack works in terms of user experience is probably more relevant. In other words, I am not advocating one approach over another. Using vold was what I decided to do to solve the problem (i.e. getting the hack to load at boot).

HasH_BrowN · Oct 8, 2015

WarrantyVoider said:
You can modify the official update.zip by removing commands that might cause issues. If you want to do this, I can look it up later.

I use vold as an entry point because it loads earlier than debuggerd. From a user's perspective, it doesn't matter much how a hack achieves its goal. How well a hack works in terms of user experience is probably more relevant. In other words, I am not advocating one approach over another. Using vold was what I decided to do to solve the problem (i.e. getting the hack to load at boot).

Yes I think having the "bad" commands removed from the update would straighten out some issues that arising.

So vold in essence, plays better with linked apps? Being that it starts at boot, not after. Can the vold approach be used to link a majority of system (non-critical) apps, without load issues? Or is there a better method? [Sorry for going off topic]

WarrantyVoider · Oct 8, 2015

HasH_BrowN said:
Yes I think having the "bad" commands removed from the update would straighten out some issues that arising.

So vold in essence, plays better with linked apps? Being that it starts at boot, not after. Can the vold approach be used to link a majority of system (non-critical) apps, without load issues? Or is there a better method? [Sorry for going off topic]

OK, let's see...
From updater-script of the zv6 update.zip, remove:

Code:

ui_print("Unpacking new recovery...");
package_extract_dir("recovery", "/cache/recovery");

and

Code:

ui_print("Writing radio image...");
assert(qcom.install_radio(package_extract_file("radio.img")));

Obviously, the 1st part skips the recovery installation and the 2nd part skips radio.img. TWRP should be able to complete the update if space isn't an issue.

As for your questions, well, both vold and debuggerd start at boot before the Android framework is loaded. vold just starts a bit before debuggerd. So using vold can be better or worse. It depends what problems you run into. Can vold be used to link system apps? Sure. It can probably be used to link most critical apps too. I am not sure what load issues you meant though. Is there a better method? I think so, but I'm obviously biased since I have my own method. I am not going to claim one approach is better than another. Just different. For example, my solution has no concept of linking apps, so it's a bit hard to answer your questions if you're strictly asking about linking apps. I've written a lot on this topic before. If you're really interested, you can find my SD hack thread. There's a link in the first post to the original idea/concept thread containing technical discussions about my implementation.

Help Hoping This Isn't A Virus...

Member

Member

Android Expert

Lurker

Android Expert

Member

Android Expert

Lurker

Android Expert

Lurker

Android Expert

Lurker

Android Expert

Lurker

Android Expert

Lurker

Android Expert

Lurker

Android Expert

Android Enthusiast

Android Expert

Android Enthusiast

Android Expert

Android Enthusiast

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads