I managed to get TWRP 2.7.0.0 using AutoRec. I'm trying to get it upgraded to version 2.8.x.x but can't do it manually using adb or with TWRP manager, or any other methods.
I'm trying to install CM11 and it fails every time, from what I've read, I need a higher version of TWRP to achieve this without getting the error executing update binary in zip msg.
Anyone else running into this problem?
Verizon LG G2
VS98026A baseband
4.4.2 stock rom
EDIT: One thing I noticed, the only versions that show up as compatible using an app like TWRP Manager are the one's labeled with g2vzw
Example - The techerrata downloads for twrp
All the downloads that work are the g2vzw downloads. All the new downloads labeled vs980.zip won't work. I've tried renaming and still have the same problem.
centrix said:
I managed to get TWRP 2.7.0.0 using AutoRec. I'm trying to get it upgraded to version 2.8.x.x but can't do it manually using adb or with TWRP manager, or any other methods.
I'm trying to install CM11 and it fails every time, from what I've read, I need a higher version of TWRP to achieve this without getting the error executing update binary in zip msg.
Anyone else running into this problem?
Verizon LG G2
VS98026A baseband
4.4.2 stock rom
EDIT: One thing I noticed, the only versions that show up as compatible using an app like TWRP Manager are the one's labeled with g2vzw
Example - The techerrata downloads for twrp
All the downloads that work are the g2vzw downloads. All the new downloads labeled vs980.zip won't work. I've tried renaming and still have the same problem.
Click to expand...
Click to collapse
You should be able to flash the version posted here in recovery.
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
mjones73 said:
You should be able to flash the version posted here in recovery.
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Click to expand...
Click to collapse
That did it, thanks!
Nightly build of CM11 still won't install, know anything about that?
centrix said:
That did it, thanks!
Nightly build of CM11 still won't install, know anything about that?
Click to expand...
Click to collapse
Nevermind, I forgot to wipe first. All is well.
Thanks again!
Related
Same exact issue as described in this thread: http://forum.xda-developers.com/showthread.php?t=2366663
Except I downloaded the latest version of SuperSU (1.86 I believe) and when I went to flash it in TWRP I got a "Failed" message, so it did not fix my issue like it did in that thread. I'm running TWRP 3.6.0.0 and Android Revolution 31.6, on a Sprint HTC One. Any help would be greatly appreciated!
Thanks!
Try flashing CWM recovery instead of TWRP. SuperSU should be able to correctly update the binary using CWM recovery. That worked for me, at least.
BlackHayze said:
Same exact issue as described in this thread: http://forum.xda-developers.com/showthread.php?t=2366663
Except I downloaded the latest version of SuperSU (1.86 I believe) and when I went to flash it in TWRP I got a "Failed" message, so it did not fix my issue like it did in that thread. I'm running TWRP 3.6.0.0 and Android Revolution 31.6, on a Sprint HTC One. Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
The correct version of TWRP for your Sprint phone is 2.6.3.0
openrecovery-twrp-2.6.3.0-m7wls.img
clsA said:
The correct version of TWRP for your Sprint phone is 2.6.3.0
openrecovery-twrp-2.6.3.0-m7wls.img
Click to expand...
Click to collapse
Sorry I had a brain fart, that is the versions of TWRP that I'm using. And I fixed the issue by reflashing using Superuser, but now am having issues with Sense 5 Toolbox and Xposed in general. I think I'm just gonna have to switch ROMs.
I have the device attached, it shows up in fastboot, but when I do "adb devices" it shows nothing. Therefore I cannot sideload a ROM. The reason I have to sideload is because there is currently no system to boot into.
Is it because I have to find the correct drivers or something? I tried installed HTC Sync manager but that didn't install the drivers. Is there anything I can do to get my device showing up to ADB? I have CWM installed and I went into recovery, enabled sideload and still no results.
Thanks for any help you can offer.
I have a ROM on my sd card already but it won't install. It says error in data/media/0/paranoidota/ROM.zip when trying to install.
Edit: The phone is S-OFF and all that, as I said, the device shows up via fastboot, is there something I can do there?
This had me stumped too.
Look in the device manager and you'll see a device called one. Manually force the drive to android device bridge and try again. Adb devices will return sideload next to the device id
RED_ said:
I have the device attached, it shows up in fastboot, but when I do "adb devices" it shows nothing. Therefore I cannot sideload a ROM. The reason I have to sideload is because there is currently no system to boot into.
Is it because I have to find the correct drivers or something? I tried installed HTC Sync manager but that didn't install the drivers. Is there anything I can do to get my device showing up to ADB? I have CWM installed and I went into recovery, enabled sideload and still no results.
Thanks for any help you can offer.
I have a ROM on my sd card already but it won't install. It says error in data/media/0/paranoidota/ROM.zip when trying to install.
Edit: The phone is S-OFF and all that, as I said, the device shows up via fastboot, is there something I can do there?
Click to expand...
Click to collapse
1- you should switch to TWRP, if you have m7_u / ul then 2.6.3.3 or 2.6.3.4, other versions seem to have problems with 4.4+ ROMs
2- check faq #2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
btw, it's in the FAQ sticky last post
nkk71 said:
1- you should switch to TWRP, if you have m7_u / ul then 2.6.3.3 or 2.6.3.4, other versions seem to have problems with 4.4+ ROMs
2- check faq #2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
btw, it's in the FAQ sticky last post
Click to expand...
Click to collapse
Thanks. I'm able to sideload now but the ROM won't install
"E: error executing updater binary in zip /data/"
More trouble! I'll try a few different ROMs to see if there is an issue with the ROM.
RED_ said:
Thanks. I'm able to sideload now but the ROM won't install
"E: error executing updater binary in zip /data/"
More trouble! I'll try a few different ROMs to see if there is an issue with the ROM.
Click to expand...
Click to collapse
you're in the UK, so safe to assume you have an m7_ul model, did you switch to TWRP 2.6.3.3 or .4?
nkk71 said:
you're in the UK, so safe to assume you have an m7_ul model, did you switch to TWRP 2.6.3.3 or .4?
Click to expand...
Click to collapse
Yeah it's M7_ul, I put on TWRP 2.6.3.3
Delete the file and sideload again. I couldn't flash a zip, but sideloaded again and it was fine. I assume md5's are correct in the PC
craiglay said:
Delete the file and sideload again. I couldn't flash a zip, but sideloaded again and it was fine. I assume md5's are correct in the PC
Click to expand...
Click to collapse
Still no results. Same error. Deleted the file, tried a sideload again.
This is the full script of what it shows:
"Installing /data/media/0/sideload.zip"
Checking for MD5 file...
Skipping MD5 check: No MD5 file found.
E: Error executing updater binary in zip /data/
Sorry, what i meant was have you checked the md5 of the file you're transfering on the pc against the download site? It sounds like either the file is corrupt or your recovery can't process it
craiglay said:
Sorry, what i meant was have you checked the md5 of the file you're transfering on the pc against the download site? It sounds like either the file is corrupt or your recovery can't process it
Click to expand...
Click to collapse
I tried a different ROM where I did an MD5 check but with everything OK I still get this error. This is the ROM I tried :http://forum.xda-developers.com/showthread.php?t=2472604
Edit: The guys in the Paranoid Android ROM thread say I need a 2.7.0.8 TWRP, That was the ROM I was initially having trouble with and trying to sideload.
I used the most recent twrp available. Think its 2.7.1.1
craiglay said:
I used the most recent twrp available. Think its 2.7.1.1
Click to expand...
Click to collapse
Yeah I just put that one on. Now we're back to the original problem, it doesn't show my devices when I try to sideload. This is a right pain.
RED_ said:
Yeah I just put that one on. Now we're back to the original problem, it doesn't show my devices when I try to sideload. This is a right pain.
Click to expand...
Click to collapse
If it shows up in the device manager on your pc, try go back one version of twrp. It should come up as an adb device
craiglay said:
If it shows up in the device manager on your pc, try go back one version of twrp. It should come up as an adb device
Click to expand...
Click to collapse
I was able to 4.3 B-ETA2 of paranoid android installed and working. On the TWRP suggested in this thread, the Paranoid Android thread lot are saying to get 4.4 I need the most up to date TWRP, so I guess now I can update twrp and load the latest version onto the phone without needing to sideload, hopefully.
Edit: Yup that's what happened. Worked perfectly. I basically needed to update TWRP to the latest version, after flashing an old ROM on via a sideload beucase ParanoidAndroid 4.4 needs the latest TWRP. Thanks for the advice in there. Will hit the thanks button in a sec!
Edit: Limited to 8 thanks a day, how terrible!
I have an HTC One Remix that I just recently s-offed using Sunshine. After flashing TWRP I am attempting to flash the su binaries through TWRP, but it doesn't seem to be working correctly. TWRP doesn't report any errors, but after rebooting my phone, there is no indication that the binaries were installed, and the SuperSU app cannot find the binaries. Is there something else I ought to be doing?
Txjacob said:
I have an HTC One Remix that I just recently s-offed using Sunshine. After flashing TWRP I am attempting to flash the su binaries through TWRP, but it doesn't seem to be working correctly. TWRP doesn't report any errors, but after rebooting my phone, there is no indication that the binaries were installed, and the SuperSU app cannot find the binaries. Is there something else I ought to be doing?
Click to expand...
Click to collapse
try flashing super user manually with trwp. find zip file and flash. works better.
SuperUser.zip (may not be latest version but you can always update in play google
Apologies, but that's what I've been trying. I downloaded the zip file from chainfie's website, but there is no change after flashing.
any luck? running into the same issue with mine...
I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
Code:
E:footer is wrong
E:signature verification failed
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)
Deleted
Anyone have any suggestions?
Bump
Someone has to have some sort of suggestions I could try... would flashing a custom rom on do anything or is this related to the KNOX security stuff?
Are you using twrp? if so, did you turn off zip verification and md5 verification?
Nergal di Cuthah said:
Are you using twrp? if so, did you turn off zip verification and md5 verification?
Click to expand...
Click to collapse
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors
lordofbeond said:
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors
Click to expand...
Click to collapse
Not in manager in actual twrp
Nergal di Cuthah said:
Not in manager in actual twrp
Click to expand...
Click to collapse
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.
This thread is probably your answer
lordofbeond said:
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-framework-install-galaxy-s4-sch-t3425615
lordofbeond said:
I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)
Click to expand...
Click to collapse
Hola. i just did this on vz GS4 i545:
use FlashFire for everything. make sure you have a titanium backup of your apps and data for after you flash new ROM. here are the steps:
1. Flash Fire Zip or OTA stock of1 deodexed ROM from here: http://forum.xda-developers.com/gal...1-keeproot-t3182544/post62413212#post62413212
it will spend 10 to 15 minutes on the red Verizon splash screen.
2. reload from titanium at this point.
3. install xposed 3.0alpha4.apk from the xposed forum page.
4. flashfire zip or ota Arter97's xposed v65 sdk21 arm arter97 V5 krait.zip
this last step took about 35 minutes to upgrade all 260 plus apps i have.
make sure you have the proper uninstaller loaded too just in case. i put mine on the ext sd card in case i needed to load it from recovery. though that might not work because of the unsigned issue.
So i have a htc one phone but...i tried every root programs,none work
Is there an toolkit or some thing i am doing wrong?
cod3_r3mors3 said:
So i have a htc one phone but...i tried every root programs,none work
Is there an toolkit or some thing i am doing wrong?
Click to expand...
Click to collapse
Don't use any programs, just flash SuperSU.zip
Sent from my One using XDA Labs
cod3_r3mors3 said:
So i have a htc one phone but...i tried every root programs,none work
Is there an toolkit or some thing i am doing wrong?
Click to expand...
Click to collapse
You should give more information like your bootloader version, recovery version, what programs have you tried etc.
Usually to root m7 you'll need:
1 - htc dev unlocked bootloader
2 - custom recovery like TWRP
3 - Supersu.zip to flash in recovery
macicgangsta said:
3 - Supersu.zip to flash in recovery
Click to expand...
Click to collapse
I'll also add "make sure to use the latest supersu version" because old versions are known to cause bootloops when used on Lollipop+ roms. :good:
So i tried installing supersu with twrp but it was giving errors,I saw that i needed to wipe cache and stuff and so i did...Plus my stock htc one os.Now i am trying to install AOKP rom on my device but its giving error with the zip file and binaries
tried wiping still not worked.Please help me asap
bump
cod3_r3mors3 said:
So i tried installing supersu with twrp but it was giving errors,I saw that i needed to wipe cache and stuff and so i did...Plus my stock htc one os.Now i am trying to install AOKP rom on my device but its giving error with the zip file and binaries
tried wiping still not worked.Please help me asap
bump
Click to expand...
Click to collapse
You haven't provided any information about your phone yet, like suggested by @macicgangsta. Please post the output of "fastboot getvar all" (hide your IMEI and SerialNo). What twrp version are you using and what supersu version? What was the errors when flashing supersu? When flashing the rom? What rom version is it exactly...? ideally post a link to that rom and/or everything else you've tried to flash.
reporting problems precisely = fast & efficient troubleshooting :good: