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

Root How to take zv6 update without breaking root.

spaceshipmax said:
Found it for jelly here:
http://repo.xposed.info/module/com.ceco.gm2.gravitybox

I accidentally installed the kk version 1st and dont know how to uninstall it. As things are, both gravitybox say gravitybox system framework not responding ?
Click to expand...
I abandoned the gravitybox thinggy and
After i made enough room for the system update to download it started. I deleted the zip file mid way put it in airplane mode and restarted. Now no more notification!
 
ShapeShifter499 said:
Which TWRP do you have? I have tried 2.8.7.0 and 2.8.1.0 and I get

"/system/bin/debuggerd" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/update.zip'
Error flashing zip '/sdcard/Download/update.zip'
Updating partition details...
...done"

Nothing actually is flashed and I'm stuck at ZV5

EDIT: I WAS ABLE TO FLASH, PEBKAC ISSUE!

I hadn't known that if Link2SD cannot find init.d support it will make a 'debuggerd' script that mounts the extra partition then calls the 'real debuggerd' so all I had to do was reverse it and move the backed up debuggerd to it's correct location.
Click to expand...
I've tried 10 times & can't use the update. Zip for some reason I keep getting the same error message but nothing about debuggers anything! It just says in red system update failed etc. I even redownloaded the updatezip but no luck.
 
mjhealy1978 said:
I've tried 10 times & can't use the update. Zip for some reason I keep getting the same error message but nothing about debuggers anything! It just says in red system update failed etc. I even redownloaded the updatezip but no luck.
Click to expand...

You've got a debuggered file that doesn't match the SHA1 checksum that the .zip file's assert is expecting.

You wouldn't by chance have installed and used Chainfire's Live Boot app (which shows kernel or logcat messages during boot-up) would you? I had the same debuggerd mismatch when using this on my N7 a long while back.

edit: meh--I just installed that app on my N5 and don't see that the debuggerd file was touched or a backup version was made. I know I was involved in threads where this app was discussed re. the debuggerd file, but that might have been coincidence or perhaps an older version of the app used to touch that file? Dunno. Regardless, you still have a mis-matching file that you'll have to replace/update before that .zip will flash.
 
Last edited:
scary alien said:
You've got a debuggered file that doesn't match the SHA1 checksum that the .zip file's assert is expecting.

You wouldn't by chance have installed and used Chainfire's Live Boot app (which shows kernel or logcat messages during boot-up) would you? I had the same debuggerd mismatch when using this on my N7 a long while back.

edit: meh--I just installed that app on my N5 and don't see that the debuggerd file was touched or a backup version was made. I know I was involved in threads where this app was discussed re. the debuggerd file, but that might have been coincidence or perhaps an older version of the app used to touch that file? Dunno. Regardless, you still have a mis-matching file that you'll have to replace/update before that .zip will flash.
Click to expand...
Here's a screenshot of what's happening!
uploadfromtaptalk1442028730449.png
 
Yeah, sounds like you've got several files that are non-stock (debuggerd and the build.prop file so far from what you've reported).

The "<filename>" has unexpected contents warning is exactly what a typical updater-script file will output/express when an apply_patch_check expression fails (it's double-checking the SHA1 sum of the file it's testing against the known SHA1 sum (digest) of the file it will likely later patch (which requires a matching file) or replace.

You're not running a custom ROM are you? If not and you do have a stock, but rooted device, there surely have been some other customizations done by you that are accounting for this warnings you're seeing.

(note: I am not an LG Volt user, but I do have a bit of experience with OTAs, edify, etc.)
 
scary alien said:
Yeah, sounds like you've got several files that are non-stock (debuggerd and the build.prop file so far from what you've reported).

The "<filename>" has unexpected contents warning is exactly what a typical updater-script file will output/express when an apply_patch_check expression fails (it's double-checking the SHA1 sum of the file it's testing against the known SHA1 sum (digest) of the file it will likely later patch (which requires a matching file) or replace.

You're not running a custom ROM are you? If not and you do have a stock, but rooted device, there surely have been some other customizations done by you that are accounting for this warnings you're seeing.

(note: I am not an LG Volt user, but I do have a bit of experience with OTAs, edify, etc.)
Click to expand...
How do I check for these files?
 
Your Build prop has been edited and it is failing the assert check. You'll have to restore an original copy of the build prop before it'll install. The update checks the integrity of multiple system files / apps and if they are changed or removed the update will fail.
 
kwknott said:
Your Build prop has been edited and it is failing the assert check. You'll have to restore an original copy of the build prop before it'll install. The update checks the integrity of multiple system files / apps and if they are changed or removed the update will fail.
Click to expand...
Is there a "for dummies" guide to editing your build prop back to normal?
 
kwknott said:
No.. You'll have to get your hands on a stock unedited copy.

Edit.. Try this one.. https://mega.nz/#!DRkUTIBa!vPx2TpwBH8aoznpjVbEV6nNg5C3PMERWNPalaVouiys

Make backup in TWRP first then copy it to proper location (/system/) with root file browser to overwrite old one and then set permissions to match as below

3ed8fd98f06685ed114f5f7c2becd7a2.jpg


Then reboot
Click to expand...
OK got it downloaded to my sdcard, so you say put it in system, I have rom toolbox pro and it wanted to flash the script via twrp, but you seem to use a file root manager/browser I also use ea file manager, maybe that can do it? Please help, I'm almost there. So I'll start by making a backup in twrp like you said, than hopefully I'll hear back with a few more hints! Again thank you all very much kwknott you too!
 
I am about to try the update.zip on a rooted zv5, but wanted to double-check first. If I am using link2sd, do I need to uninstall that (or move the apps back to the internal sd card) first? Or will it work with that?
 
nyc said:
I am about to try the update.zip on a rooted zv5, but wanted to double-check first. If I am using link2sd, do I need to uninstall that (or move the apps back to the internal sd card) first? Or will it work with that?
Click to expand...
YOU DO NOT NEED TO REMOVE LINK2SD

Just check to see if you have both a /system/bin/debuggered AND /system/bin/debuggerd.bin If there is no /etc/init.d support, Link2SD likes to create a 'fake' debuggerd that is actually a mount script which in turn calls the true debuggerd which was moved to debuggerd.bin. This is because debuggerd is given a higher priority than SU and the system doesn't do any checks in KitKat if that debuggerd is correct or not, it just runs it.

IF SO use a terminal app or run 'adb shell' on a connected computer and run the following

Code: 
su
mount -o rw,remount /system
rm /system/bin/debuggerd
cp /system/bin/debuggerd.bin /system/bin/debuggerd

First line gets the shell root access which may prompt you on screen if you use SuperSU (agree but I'd only make it a 15 minute limit for security reasons)
Second line remounts the read only /system so we may make changes
Third line removes the Link2SD script mount script (the update doesn't like this), this will temporarily cause apps to disappear during next boot including icons on the home screen which you could add again later.
Fourth line copies back the true debuggerd so the update script is happy.

Reboot into TWRP and flash the update.zip

Root will partially break so go back to SuperSU to flash the SU binary again. If SuperSU still complains, reboot into TWRP and flash SuperSU manually by downloading the zip here, http://download.chainfire.eu/supersu After reboot go to Link2SD, it should complain that mount scripts need to be recreated, do that and reboot once more. At this time everything 'should' be ok but if you have any further issues let us know.

EDIT: Clarified how to fix root when lost after upgrading to ZV6
 
Last edited:
ShapeShifter499 said:
YOU DO NOT NEED TO REMOVE LINK2SD

Just check to see if you have both a /system/bin/debuggered AND /system/bin/debuggerd.bin If there is no /etc/init.d support, Link2SD likes to create a 'fake' debuggerd that is actually a mount script which in turn calls the true debuggerd which was moved to debuggerd.bin. This is because debuggerd is given a higher priority than SU and the system doesn't do any checks in KitKat if that debuggerd is correct or not, it just runs it.

IF SO use a terminal app or run 'adb shell' on a connected computer and run the following

Code: 
su
mount -o rw,remount /system
rm /system/bin/debuggerd
cp /system/bin/debuggerd.bin /system/bin/debuggerd

First line gets the shell root access which may prompt you on screen if you use SuperSU (agree but I'd only make it a 15 minute limit for security reasons)
Second line remounts the read only /system so we may make changes
Third line removes the Link2SD script mount script (the update doesn't like this), this will temporarily cause apps to disappear during next boot including icons on the home screen which you could add again later.
Fourth line copies back the true debuggerd so the update script is happy.

Reboot into TWRP and flash the update.zip

Root will partially break so go back to SuperSU to flash the SU binary again. After reboot go to Link2SD, it should complain that mount scripts need to be recreated, do that and reboot once more. At this time everything 'should' be ok but if you have any further issues let us know.
Click to expand...

Thank you very much for the detailed steps. I got it to work, the only thing I needed to do differently was relating to the SuperSU. When I went back into SuperSU it just gave an error message and then closed the app. I didn't seem to be able to redownload the binary. So I re-rooted using DP Tools which then allowed me to get into SuperSU fine.

On zv6 now and no issues with my external SD partitions.
 
nyc said:
Thank you very much for the detailed steps. I got it to work, the only thing I needed to do differently was relating to the SuperSU. When I went back into SuperSU it just gave an error message and then closed the app. I didn't seem to be able to redownload the binary. So I re-rooted using DP Tools which then allowed me to get into SuperSU fine.

On zv6 now and no issues with my external SD partitions.
Click to expand...

I forgot.... you could have just flashed the root since you still had a custom recovery.

For future readers, just download the SuperSU zip from the official site, http://download.chainfire.eu/supersu, and flash it when you loose root. Assuming you still have an custom recovery like TWRP.
 
When I run either the OTA update or the one attached toward the beginning of this thread I instantly get an error "This package is for "x5" devises: this is a "lg_ls740v3". I'm running the rooted stock version of v5. I could remove the check in the updater-script and try again, but I'm wondering why I'm seeing this and nobody else is?
 
kwknott said:
You have to delete it then reboot, but it will stop for a while. Or at least until it downloads again.

From what I saw online the fix was mainly just to fix the stage fright vulnerability. But knowing LG they slip some other junk into it.
Click to expand...

I kinda wish they would slip some other junk into it. Like a fix for the corporate email app that constantly loses the ability to authenticate with my company's exchange server... but only on Wi-Fi. While on 3g/4g it never has a problem.

On another thread on this forum it was mentioned that you can take the update and it wont break root. It does break TWRP though and you need to reflash it with flashify. I've not tried it yet though.
 
Apologies..getting a bit confused...just got update notification....am rooted on original stock rom...dont want to loose root so if I run update it sounds like u dont loose root...Is that correct?
 
iram said:
Apologies..getting a bit confused...just got update notification....am rooted on original stock rom...dont want to loose root so if I run update it sounds like u dont loose root...Is that correct?
Click to expand...

Not sure, I lost root when going from ZV4 to ZV5 then from ZV5 to ZV6 but it wasn't difficult to root it again with the LG One Click Root tool.
 
You must log in or register to reply here.
Back
Top Bottom