Related
I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.
gstoliby said:
I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.
Click to expand...
Click to collapse
try disabling signature verification in your recovery
chromium96 said:
try disabling signature verification in your recovery
Click to expand...
Click to collapse
I can't even figure out how to do that!
gstoliby said:
I can't even figure out how to do that!
Click to expand...
Click to collapse
Which recovery are you using? In clockwordmod the option is located in the advacned menu
chromium96 said:
Which recovery are you using? In clockwordmod the option is located in the advacned menu
Click to expand...
Click to collapse
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.
gstoliby said:
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.
Click to expand...
Click to collapse
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.
chromium96 said:
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.
Click to expand...
Click to collapse
I'll have to give it a try when I get to my personal computer.
My Nexus 5 is rooted. It downloaded the 4.4.3 update. It tries to restart and Team Win Recovery opens. I enter my password and it decrypts the data andI get the Team Win Recovery options. I don't see where to install the update from though?
I manually downloaded it from the link and I'm not seeing where Chrome put it either.
What am I missing? I'm certain I'm in the right folder which is downloads. It looks like it is only looking for a .zip file, but when I go to file viewer it looks like it downloaded a .tar.
How do I just tell the system to install the file it downloaded?
You need the OTA update. Sounds like you downloaded the full image. AP has the links.
Sent from my Nexus 5
rye&ginger said:
You need the OTA update. Sounds like you downloaded the full image. AP has the links.
Sent from my Nexus 5
Click to expand...
Click to collapse
What is AP?
I'm running the stock ROM and I am only running Xposed
ETA - I searched and found a link here. Is this what I need? http://www.droid-life.com/2014/06/03/download-android-4-4-3-ota-update/
Now my pc won't see the Nexus 5 and I tried downloading the Nexus 5 USB driver for windows 8 and it's saying it's not the right one.
Have a read of this thread:
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
It lists many different scenarios whereby you need to do different things depending on how your phone is loaded up for the update.
For the USB drivers you can get them from here:
http://developer.android.com/sdk/win-usb.html
brichardson1991 said:
Have a read of this thread:
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
It lists many different scenarios whereby you need to do different things depending on how your phone is loaded up for the update.
For the USB drivers you can get them from here:
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I uninstalled Xposed from apps. I went to try to redownload the update, but it now says my phone is up to date but it's running 4.4.2
Now that I have xposed uninstalled, when the update is shown again (or hopefully I can force it since I'm sure it downloaded it and stored it somewhere) will it just run the update properly? Or is it still going to boot into team win and then not do anything?
brichardson1991 said:
Have a read of this thread:
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
It lists many different scenarios whereby you need to do different things depending on how your phone is loaded up for the update.
For the USB drivers you can get them from here:
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
This is the USB driver I have but it keeps saying it can't find one for my device
save yourself a headache and some time, update it manually. download it yourself and install it.
simms22 said:
save yourself a headache and some time, update it manually. download it yourself and install it.
Click to expand...
Click to collapse
I just downloaded the .zip file that is the update using my phone. I went into Team Win and clicked on install. Went to downloads and it errors. I have tried downloading it and installing it 3x and it always says E: Error executing updater binary in zip'/sdcard Error flashing zip'/sdcard/download/filename
wiping the cache/dalvik does nothing
mobileboost said:
I just downloaded the .zip file that is the update using my phone. I went into Team Win and clicked on install. Went to downloads and it errors. I have tried downloading it and installing it 3x and it always says E: Error executing updater binary in zip'/sdcard Error flashing zip'/sdcard/download/filename
wiping the cache/dalvik does nothing
Click to expand...
Click to collapse
flash stock recovery. or grab one of the many uploaded 443 stock+root roms available now in the android development section.
simms22 said:
flash stock recovery. or grab one of the many uploaded 443 stock+root roms available now in the android development section.
Click to expand...
Click to collapse
Wait. There is a stock rom with root already in it now so I don't have to money around to root anymore?!
I don't want to lose my data though.
mobileboost said:
Wait. There is a stock rom with root already in it now so I don't have to money around to root anymore?!
I don't want to lose my data though.
Click to expand...
Click to collapse
yup http://forum.xda-developers.com/google-nexus-5/development/flashable-stock-4-4-3-supersu-t2771010
you can try dirty flashing first, it should be fine. just make a backup in recovery beforehand, just in case.
simms22 said:
yup http://forum.xda-developers.com/google-nexus-5/development/flashable-stock-4-4-3-supersu-t2771010
you can try dirty flashing first, it should be fine. just make a backup in recovery beforehand, just in case.
Click to expand...
Click to collapse
How do I dirty flash it? I'm still not certain why I can't just run the update file I downloaded as it errors on me.
simms22 said:
yup http://forum.xda-developers.com/google-nexus-5/development/flashable-stock-4-4-3-supersu-t2771010
you can try dirty flashing first, it should be fine. just make a backup in recovery beforehand, just in case.
Click to expand...
Click to collapse
The dirty flash worked perfect. It seems that is the only file that I need? Since I did the 4xx MB ROM?
I wish Google would make it easy to update while rooted on the nexus phones. I'm only so smart
I am using a Nexus 5, and I tried to flash the CyanogenMod 11s from OnePlus One to my Nexus following instructions from here:
http://www.ibtimes.co.uk/nexus-5-gets-port-cyanogenmod-11s-featuring-android-4-4-4-1458608
My phone was not rooted, I performed a root and apparently succeeded, because I saw SuperSU installed on my device. I then proceeded to follow the instructions from the site mentioned above, performed a factory reset, and selected the ROM I downloaded to flash. The flashing failed and I am currently stuck in bootloop, afraid to proceed further and brick my phone.
Some of the signs I noted with my phone:
At the ROM installation screen, it says 'checking for MD5 file... Skipping MD5 check: No MD5 file found', 'symlink: some symlinks failed', ' E: Error executing updater binary in zip '/sdcar', and 'Error flashing zip '/sdcard/CyanogenMod_11S_ham'
At Reboot menu, upon tapping on 'Recovery' option it says 'No OS installed! Are you sure you wish to reboot?'
Please help me out, I'm sick at the moment, guess it is not a good idea to flash a ROM when you're sick huh? Been trying to find a solution and can't seem to find it, not sure if because I'm sick and too tired to read through or there really isn't a situation like this...
Thank you!
first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it. second option, flash the factory img via fastboot while youre in the bootloader. it has nothing to do with being sick, it has everything to do about learning all about your device and how to take care of it, before you start modding your device.
All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.
I build my own ROM even when I'm sick, what do you mean?
Try redownloading as it had flashing issues before
jackhayden said:
All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.
Click to expand...
Click to collapse
no, you didnt actually. you could have had a bad download, that happens often enough(but i dont think its the case, as it wouldnt remove your rom), you also could have experienced a recovery bug, that also can happen from time to time. btw, did you mention which recovery youre using?
I'm using TWRP.
jackhayden said:
I'm using TWRP.
Click to expand...
Click to collapse
well, try to download it again, and push it to your drvice with adb, then reflash it. or try pushing another rom. or, you always have the failsafe of flashing the factory img. btw, did you happen to make a backup in recovery before you flashed? you should always make a backup in recovery if flashing something new, just in case. in your case, it would make thing extremely easy.
Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.
jackhayden said:
Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.
Click to expand...
Click to collapse
you need to bring up the ui for typing.. on my old windows computer at work, i find an empty space on the same page that adb is located on your computer, then i left click and press the shift button on that empty space, then i get a few option that pop up, and i press the option. but im using windows from like 2004-5, lol.
Wow, that's really old.
I saw one of the commands available is 'adb push 'file name', should I try that?
Sorry for the troubles!
yup. first do "adb devices" to make sure adb sees your phone.
Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.
jackhayden said:
Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.
Click to expand...
Click to collapse
is the rom zip in the same folder as adb is located? it should be if not. and did adb see your device in with adb devices?
Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.
jackhayden said:
Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.
Click to expand...
Click to collapse
hmm.. well, i dont know that error, ive never seen it
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
Flash gapps
jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
"first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it."
as @Lethargy said, gapps(google apps), you need to flash them. the google apps are not open source, they are owned by google, and cm isnt allowed to add them to the rom. but you are allowed to flash them separately
Thanks a lot for all the helps given. Really appreciate them! :good:
Hi Guys,
I have tried many of the ROMs available however, for the most part, I get this error "error executing updater binary" in TWRP. I have also tried CWM and Philz recovery. The only ROM that installs is CM11. Does any one know what is the issue? Anyone got a solution? Thanks.
Current Recovery: TWRP 2.7.1.1
I'm the only one experiencing this issue?
Specifically which ROMs have you tried?
Transmitted via Bacon
I've tried the following:
AOSP from the Oneplus homepage
AOSP flapped
mahdi-rom
Team GUMMY
Are you checking the md5 when you download?
Transmitted via Bacon
No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.
bill1clinton said:
No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.
Click to expand...
Click to collapse
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon
Well, just re-downloaded AOSP from the oneplus homepage and flapped AOSP. I also checked their md5 hashes; they match. I will report back.
I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.
timmaaa said:
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon
Click to expand...
Click to collapse
Just tried to flash both, both times I get the "error executing updater binary" error. I do not have the technical expertise to try to correct this.
Anyone else with any ideas?
Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?
demkantor said:
Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?
Click to expand...
Click to collapse
The ROM that works is CM11 nightly and the one that I would like to install is pure AOSP. Are you certain that their update binary files would/could be interchangeable?
And how to do you "set to store"? I use 7zip.
I have the international 64GB. And I am not sure how to check my bootloader.
I really do apologize for my newb-ness on this matter.
There shouldn't be an issue, but of course I can't promise as I don't know what specifically is going on in your case
When you choose zip, there you will have different compression options, choose store
Try
fastboot oem device-info
Write down output here
No worries, we all are noobs in our own ways
did anyone figure this out? im having the same issue trying to install lollipop roms
Same problem here
jlinn75 said:
did anyone figure this out? im having the same issue trying to install lollipop roms
Click to expand...
Click to collapse
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.
viriatis said:
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.
Click to expand...
Click to collapse
I get the exact same error, as you I can only flash CM-11, strange cause I was running Euphoria OS Lollipop!
Someone must know the cause!
sad problem
doe or die said:
I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.
Click to expand...
Click to collapse
I'm having exactly same problem. So is this common problem or what? I had multirom and xposed framework but after uninstalling them both I get the same error again. I hope this does not happen when we are getting the Lollipop-update. Sry for bad enklish.
Anyone help?
Device: Samsung Galaxy S7 SM-G930W8
TWRP Version: 3.0.2-2
Tried downloading the file to get around the DM-verity boot loop linked in the guide a couple times thinking it may have got corrupt downloading or transferring however nothing has changed.
flashing with TWRP worked fine, and for the sake of curiosity if maybe it was just having an issue with .zips and i should re-flash,
i attempted to install the SU file also linked in the guide linked below. however that was successful.
i have not attempted to fully re-start the phone as its been ages since i last owned, and rooted an android device. so I'm un-sure if the DM-Verity thing will lock me out of getting back into TWRP or not.
This is as far as it gets when attempting to install the .zip to fix DM-verity
-dumping & unpacking original boot image…
-Error: unpacking boot image failed
-Aborting…
Failed to patch boot image!
Updater process ended with ERROR: 1
Any help would be greatly appreciated. Thanks.
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
I have the EXACT same error, I followed the steps and I'm not new at all to rooting Samsung devices.
I believe the error is that they tell you to flash SuperSU first, on my girlfriends' s6 this wasn't necessary.
I have wiped data and factory reset, reflashed TWRP etc etc etc, I can't get this dm-verity to flash! I rebooted into system and everything seems to work OK though, I just installed the XPosed framework and it's booting again now so I believe that maybe because you first flashed the SuperSU this prevents the dm-verity stuff to work?
Anyone else have any idea?
CidHighwind said:
Device: Samsung Galaxy S7 SM-G930W8
TWRP Version: 3.0.2-2
Tried downloading the file to get around the DM-verity boot loop linked in the guide a couple times thinking it may have got corrupt downloading or transferring however nothing has changed.
flashing with TWRP worked fine, and for the sake of curiosity if maybe it was just having an issue with .zips and i should re-flash,
i attempted to install the SU file also linked in the guide linked below. however that was successful.
i have not attempted to fully re-start the phone as its been ages since i last owned, and rooted an android device. so I'm un-sure if the DM-Verity thing will lock me out of getting back into TWRP or not.
This is as far as it gets when attempting to install the .zip to fix DM-verity
-dumping & unpacking original boot image…
-Error: unpacking boot image failed
-Aborting…
Failed to patch boot image!
Updater process ended with ERROR: 1
Any help would be greatly appreciated. Thanks.
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Click to expand...
Click to collapse
Guys i had the same problem, then i searched on youtube for some help and i found this site where to download the zip file...it worked for me !!!
http://downloadandroidrom.com/file/tools/SuperSU/no-verity-opt-encrypt.zip
Hope it helps
I can't seem to find where you download anything on that page. every link just re-directs you to a bunch of spam.
CidHighwind said:
I can't seem to find where you download anything on that page. every link just re-directs you to a bunch of spam.
Click to expand...
Click to collapse
Scroll all the way down to "CLICK HERE to Download"
I downloaded this dm-verity zip and noticed it's about 100kb smaller than the one I got yesterday. Up until now my S7 has been working flawless even without this dm-verity zip. On my S6 this was absolutely necessary.. Can anyone comment on this?
I will probably try to flash this later today after I took a backup.
CidHighwind said:
I can't seem to find where you download anything on that page. every link just re-directs you to a bunch of spam.
Click to expand...
Click to collapse
CobyBE said:
Scroll all the way down to "CLICK HERE to Download"
I downloaded this dm-verity zip and noticed it's about 100kb smaller than the one I got yesterday. Up until now my S7 has been working flawless even without this dm-verity zip. On my S6 this was absolutely necessary.. Can anyone comment on this?
I will probably try to flash this later today after I took a backup.
Click to expand...
Click to collapse
Exactly
It opens a new page couple of times and then the dwl starts...
Sent from my herolte using XDA Labs
Flashing this new zip worked flawlessly, booted immediately. However now I'm seeing the "Kernel is not SEAndroid Enforcing" message on top. I didn't have this before flashing this even though I was rooted (Stock rom) and had TWRP installed
CobyBE said:
Flashing this new zip worked flawlessly, booted immediately. However now I'm seeing the "Kernel is not SEAndroid Enforcing" message on top. I didn't have this before flashing this even though I was rooted (Stock rom) and had TWRP installed
Click to expand...
Click to collapse
For me it was the same but looks like it's the only way to have a "working" rooted phone...when i rooted with cf-autoroot i couldn't flash the Roms because i couldn't have access to memory and wipe after flashing...like this you have the red string but you can wipe
Sent from my herolte using XDA Labs
Anyone have the download somewhere?
I went to the page post here but it just opens a window to "mirror31.downloadandroidrom.com/download/tools/SuperSU/no-verity-opt-encrypt.zip?token=640936718"
then just goes to a page that says ":An error occurred.
Sorry, the page you are looking for is currently unavailable.
Please try again later.
If you are the system administrator of this resource then you should check the error log for details.
Faithfully yours, nginx."
I've been trying for a couple hours to download it.
So right now I have a phone that I can't use, really need to fix this.
Updated zip
Ok guys, I've been working on a better zip that fixes the "Kernel is not SE Android enforcing" and also doesn't disable Force Encrypt. My reasoning is that it can interfere with "fully encrypting the phone" functionality which is required by some companies when registering your email. Anyway, if you wish to bring it back, just copy over 01-opt-encrypt and put it in patch.d folder.
alexceltare2 said:
Ok guys, I've been working on a better zip that fixes the "Kernel is not SE Android enforcing" and also doesn't disable Force Encrypt. My reasoning is that it can interfere with "fully encrypting the phone" functionality which is required by some companies when registering your email. Anyway, if you wish to bring it back, just copy over 01-opt-encrypt and put it in patch.d folder.
Click to expand...
Click to collapse
Found this when i was searching for DM-Verity disabler for my Redmi Note 7 pro with Stock MIUI ROM, just wondering if this will also works on Redmi Note 7 pro (encrypted, android 9).
Tks.
ne0t said:
Found this when i was searching for DM-Verity disabler for my Redmi Note 7 pro with Stock MIUI ROM, just wondering if this will also works on Redmi Note 7 pro (encrypted, android 9).
Tks.
Click to expand...
Click to collapse
I think it might work fine since all it does to stop the warning is to inject an echo command to the kernel. So in theory it should work. If it fails, the system isn't changed.
alexceltare2 said:
I think it might work fine since all it does to stop the warning is to inject an echo command to the kernel. So in theory it should work. If it fails, the system isn't changed.
Click to expand...
Click to collapse
Tks forn the quick reply.
One more question, what partition and (what files) do I need to backup in case something unexpected happened.
ne0t said:
Tks forn the quick reply.
One more question, what partition and (what files) do I need to backup in case something unexpected happened.
Click to expand...
Click to collapse
The Kernel partition. Use TWRP for that.
alexceltare2 said:
The Kernel partition. Use TWRP for that.
Click to expand...
Click to collapse
Sorry, can't find the KERNAL partition..do you mean BOOT?
There are Boot, Recovery, System, Data, Vendors, ...
ne0t said:
Sorry, can't find the KERNAL partition..do you mean BOOT?
There are Boot, Recovery, System, Data, Vendors, ...
Click to expand...
Click to collapse
Yes, I meant to say Boot. Boot and Kernel are the same.
alexceltare2 said:
Updated zip
Ok guys, I've been working on a better zip that fixes the "Kernel is not SE Android enforcing" and also doesn't disable Force Encrypt. My reasoning is that it can interfere with "fully encrypting the phone" functionality which is required by some companies when registering your email. Anyway, if you wish to bring it back, just copy over 01-opt-encrypt and put it in patch.d folder.
Click to expand...
Click to collapse
Thank you very much!!