I've made a terrible mistake.
Unlocked the bootloader successfully then tried flashing superuser, then wiped all, then tried installing CM11
Apparently I never got root successfully and now the device has no ROM at all.
It won't write CM11 and I can't throw a stock rooter tmobile rom in the TWRP directory to try that.
"Error executing binary in zip"
did I just wreck the device?
theartialmartist said:
I've made a terrible mistake.
Unlocked the bootloader successfully then tried flashing superuser, then wiped all, then tried installing CM11
Apparently I never got root successfully and now the device has no ROM at all.
It won't write CM11 and I can't throw a stock rooter tmobile rom in the TWRP directory to try that.
"Error executing binary in zip"
did I just wreck the device?
Click to expand...
Click to collapse
You might try to run the RUU 5.14.531.11 of course it will wipe all of your data if you didn't save it before your issue. If you are S-ON, you will need to lock your bootloader after you successfully run the RUU you can unlock it again using your same unlock code.
@theartialmartist
You might try this: HTC Unbricking Project
Related
Hey everyone, I've been using my hox+ rooted for some time now, never flashed a ROM and was wondering if I update to the new att software will I lose root?
Yes. Just make sure you have a custom recovery and flash the root installer zip. Or if you have TWRP, after a the flash, it will ask to install root.
Hey thanks for the response, I'm running twrp 2.4 the thing is I don't know whether to to let the phone update through its regular way of updating or do I flash this http://forum.xda-developers.com/showthread.php?t=2235248, the problem with flashing this is I don't
Know how to flash boot IMG. Sorry I'm a noob any help would be greatly appreciated.
Use this command in fastboot.
fastboot flash boot /location/of/boot.img
If your bootloader is unlock and your phone has a custom Recovery, the official AT&T update won't install on your phone. If you want the update, or you wait for a custom ROM with the update to be available, or you relock bootloader, and flash the latest RUU to recover the original state of your phone. Then you can still unlock with the same token and install a custom recovery to root your device.
Thanks much fellas, you've been a great help!
Hello, I'm trying to flash CM on to my Samsung GS4 but am having trouble getting past recovery. My phone has build KOT49H.I545VRUFNC5. I gained root access using towelroot and verified through terminal using the SU command (the prompt became #). I installed Clockwork Mod and flashed recovery 6.0.4.7 but when i reboot into recovery (whether manually or through CWM) the phone still goes into stock recovery. I also tried installing recovery through ADB sideload. On the PC terminal window it shows 100% and on the device shows: (and it does this twice before showing installation aborted)
Finding Update package
Opening Update package
Verifing update package
E:footer is wrong
E:signature verification failed
I've tried two different packages from CWM and one from TWRP all with the same results.
recovery-clockwork-touch-6.0.4.7-jfltevzw.img
recovery-clockwork-6.0.4.7-jfltevzw.img
openrecovery-twrp-2.8.0.1-jfltevzw.img
I've read this post on CM (http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw) and it mentions installing an alternate kernal but I have not done so because it warns up top that you must be on I545VRUAMDK or this process will not work and brick your phone. So I'm going around in circles here. Any guidance would be appreciated.
kylo77 said:
Hello, I'm trying to flash CM on to my Samsung GS4 but am having trouble getting past recovery. My phone has build KOT49H.I545VRUFNC5. I gained root access using towelroot and verified through terminal using the SU command (the prompt became #). I installed Clockwork Mod and flashed recovery 6.0.4.7 but when i reboot into recovery (whether manually or through CWM) the phone still goes into stock recovery. I also tried installing recovery through ADB sideload. On the PC terminal window it shows 100% and on the device shows: (and it does this twice before showing installation aborted)
Finding Update package
Opening Update package
Verifing update package
E:footer is wrong
E:signature verification failed
I've tried two different packages from CWM and one from TWRP all with the same results.
recovery-clockwork-touch-6.0.4.7-jfltevzw.img
recovery-clockwork-6.0.4.7-jfltevzw.img
openrecovery-twrp-2.8.0.1-jfltevzw.img
I've read this post on CM (http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw) and it mentions installing an alternate kernal but I have not done so because it warns up top that you must be on I545VRUAMDK or this process will not work and brick your phone. So I'm going around in circles here. Any guidance would be appreciated.
Click to expand...
Click to collapse
You are on NC5. Clockwork Mod and TWRP are not compatible with our device. Nor are pure AOSP ROMs such as CyanogenMOD. Our bootloader is still locked and we can only use Safestrap as our recovery and safestrap compatible ROMs. I am surprised you have not at least soft bricked your phone yet.
Thanks, that explains a lot.
Not saying you missed a detail, but even mdk isn't unlocked, just bypassed.
I got a replacement Tab from sony and I'm having trouble rooting it with the updated firmware. Seems the only real way to do it is to have a custom recovery installed, however I am having trouble with that. When I try installing a recovery through fastboot flash command I get an error FAILED: Remote: Command not Allowed.
The installer version of XZDual just hangs at install.
Has anyone else on Verizon tab found any other ways of rooting after the latest update?
Varekai said:
I got a replacement Tab from sony and I'm having trouble rooting it with the updated firmware. Seems the only real way to do it is to have a custom recovery installed, however I am having trouble with that. When I try installing a recovery through fastboot flash command I get an error FAILED: Remote: Command not Allowed.
The installer version of XZDual just hangs at install.
Has anyone else on Verizon tab found any other ways of rooting after the latest update?
Click to expand...
Click to collapse
You have to downgrade firmware off 4.4.4 and root,
Got it working. I didn't know I had to have the unknown sources checked. Also I didn't realize I was plugged into a 3.0 port in the back of my PC, so that didn't help. Thanks for the help.
I have a Verizon Z2 LTE SGP561 with the latest update of 4.4.4 and i managed successfully to Root it with the latest KingRoot apk.
It was very easy - just download the KingRoot apk to your device , run it from the device and it will do the work.
After it will complete you will have KingRoot user which is the superuser app for permission, no need to install SuperUser of SuperSU.
I checked with root-checker to verify and indeed it was rooted.
even though the bootloader is locked you are rooted.
I managed to remove all Verizon bloatware apps.
You can find the latest KingRoot apk in the following link:
http://downloadandroidapkget.blogspot.co.il/2015/05/download-kingroot-apk-latest-version.html
Varekai said:
I got a replacement Tab from sony and I'm having trouble rooting it with the updated firmware. Seems the only real way to do it is to have a custom recovery installed, however I am having trouble with that. When I try installing a recovery through fastboot flash command I get an error FAILED: Remote: Command not Allowed.
The installer version of XZDual just hangs at install.
Has anyone else on Verizon tab found any other ways of rooting after the latest update?
Click to expand...
Click to collapse
Thanks, I'll try this if I get another replacement device. This one has a dead pixel in it.
So, here I'm stuck with the z3v after my 6plus sold to my uncle. Running E.44 and the root method seem not working, I already install the king root and can't replace with the superSu, keep saying "fail to update, reboot"... and trying to degrade firmware and the flash tool keep said "can't reconize device, check the driver....." Saw topic with instruction to kkng root temperary and "dual recovery" what's the dual recovery is it?
Is it possible that verizon will open bootloader for z3v??
install kingoroot and then recovery and then install prerooted firmware through recovery
no need to unlock boot loader... it's direct method
member_android said:
So, here I'm stuck with the z3v after my 6plus sold to my uncle. Running E.44 and the root method seem not working, I already install the king root and can't replace with the superSu, keep saying "fail to update, reboot"... and trying to degrade firmware and the flash tool keep said "can't reconize device, check the driver....." Saw topic with instruction to kkng root temperary and "dual recovery" what's the dual recovery is it?
Is it possible that verizon will open bootloader for z3v??
Click to expand...
Click to collapse
Follow my guide as worded. You've done the first step in rooting it with Kingroot. Now you need to use the dual recovery installer to install the custom Android recovery, TWRP. Then you flash my prerooted Lollipop.
Hi everyone, I just purchased a used thor from ebay and am excited about flashing custom roms for it. It came with TWRP 2.8.6 and HDX nexus (4.0.5) already installed, so a great plus and I was able to flash the newest refresh, Fire Nexus rom, BUT with a slight hiccup as it gave me an error, "E:Error executing updater binary in zip". I followed the advice from a google search result that said to reboot back into recovery after the failed attempt and try again, but without wiping. This time it worked.
My question is, if I have a custom recovery TWRP 2.8.6 and now a custom rom, fire nexus with root, does this mean the bootloader is unlocked? I guess a bit confused. Also, would the TWRP error message be an indication of an outdated TWRP or something else?
At some point I would like to move to to CM 14.1, but realize I would need to update TWRP and have an unlocked bootloader to achieve this. Thanks everyone. I am a complete noob to flashing!
- Current Recovery: TWRP 2.8.6
- Current Rom: kk-fire-nexus-rom-thor-20161017
- Rooted
- Made a backup of HDX Fire Nexus
- SuperSU required a binary update, done automatically by TWRP.
Verify the hash value of the ROM , just to confirm it's not corrupted. If it is fine boot into in twrp under "mount" options de-select system and try reflashing. You may need to reboot after deselecting it.
Mr McBoatface said:
Verify the hash value of the ROM , just to confirm it's not corrupted. If it is fine boot into in twrp under "mount" options de-select system and try reflashing. You may need to reboot after deselecting it.
Click to expand...
Click to collapse
Thanks for the reply. Rom was ok I think..I checked the zip in es file explorer before flashing and all the directories and files were intact. I checked the mount as you said and the system had previously been deselected. I did read that selecting and then deselecting might work. The next time I flash a rom I will def try this method again.