Related
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
chokem said:
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
Click to expand...
Click to collapse
So, to sum up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Furies said:
So, to some up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Click to expand...
Click to collapse
OK, thanks very much. So I was indeed on the right track. I'll try your ROM recommendation as well as the modified CWM recovery.
I'm getting this error when trying to flash lollipop roms. I can flash Kitkat roms fine as I'm currently running xdabbeb VS982.5 1.0.0 (G3 rom), but it won't let me flash any lollipop rom. I installed twrp via the autorec program which installs 2.7.0.0 then I updated twrp within twrp with the flashable zip.
Please help
Thank you
Anyone?
Seriously no one knows? What is everyone else using that is flashing the latest 5.0.2 roms?
What am I getting this error?
Please help
Possible Fix
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Thanks for the suggestion. I'll give it a try. If there is no. Md5 what do I do then?
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
I tried resurrection remix and liquid lollipop roms. I had no issues with the initial 5.0 lollipop roms so I'm not sure what changed with 5.0.2.
So the md5 checker generates the .Md5 then you just put that on the SD card with the rom?
Resurrection remix should have an md5 on the download page right below the rom itself.
derekmt95 said:
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
Click to expand...
Click to collapse
Can you point me to the program to use on my computer? Do I just load the .zip file in the program to generate the .md5sum file then put both the zip and the .md5sum file on the sdcard before flashing?
Thanks
derekmt95 said:
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Click to expand...
Click to collapse
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
xxNiradxx said:
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
Click to expand...
Click to collapse
Try to reflash the TWRP.. or maybe is something wrong with the zip file
Use the TWRP compiled by blastagator
Nope, still getting same error with latest twrp.
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
xxNiradxx said:
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
Click to expand...
Click to collapse
How did you downgrade because I cannot seem to find a way to do it.
TheAnonymousButler said:
How did you downgrade because I cannot seem to find a way to do it.
Click to expand...
Click to collapse
just run AutoRec again and you are all set.
LG G2 cm-11 M12 : Error executing updater binary in zip (TWRP)
kashif87 said:
just run AutoRec again and you are all set.
Click to expand...
Click to collapse
Hi, I am having the same problem. Actually my LG G2 was stuck in boot loop with secure boot error. I used SRK tool to flash the partition files as well as TWRP recovery 2.8.6.1. I have wiped everything and there is no OS installed. I am stuck in TWRP recovery screen [cannot downgrade /upgrade]. I am using and OTG cable to flash the cm-11 custom ROM but it is giving me the same error. Can anyone help ?? It has been 10 days I am trying and my phone is dying please help...
Thanks in advance...
before flash 5.1.1 aosp lollipop rom u must to flash first lollipop bootstack
Hi,
I am assuming the reply was for me. Actually I am not installing lollipop. I am going for kitkat but nothing is working now. I have tried cm-10.2, cm-11 M12, cm-11 M7 but all are showing "error executing updater binary in zip". Please if someone can help me out....
Thanks is advance....
@[email protected] i think kk aosp room need jb bootleader
Hello everyone,
I am running a D802 on stock Lollipop and installed TWRP 2.8.6.0 via AutoRec. Now I booted into recovery, wiped System and Cache and got the Error message when installing CrDroid (Marshmallow 6.0.1). Now I tried installing TWRP 3.0.2.0, which succeeded and then downloaded the twrp 2.7.0.0 zip to try that as the ROM still wouldnt install. But it wont install the older TWRP. So I am asking for help to either
1) Install TWRP 2.7.0.0
or
2) Delete the getprop lines from updater-script (after I removed them I get an error 6 so i probably removed too much?)
Thank you in advance
(Guide for Error 7: http://forum.xda-developers.com/showthread.php?t=2522762)
EDIT: Someone said installing another Kernel might allow installation of the ROMs. Which Kernel could work for my phone?
EDIT 2: When flashing TWRP 2.7.0.0 it says "assert failed: run_program("/tmp/loki.sh")==0". So what exactly am I missing on my phone? Is Loki the MM Bootloader?
EDIT 3: Could it be that the build.prop was deleted when I wiped system? Would be weird if that was the cause, but I simply dont know..
Edit: Booted in Downloa Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now
Hey all, so I just came from fixing my Bricked G2 D800. I finally got it back up and running with D80020c. I really wanted to get the OTA updates but had no luck getting that to work, kept getting you are not registered error. Anyway, last night I rooted with towelroot and then installed TWRP with Autorec. I noticed though that the TWRP is 3.7 that was installed.
I decided to go with the resurection rom. I tried to flash and am getting "Can't install this package on top of incompatible data. Please try another package or run a factory reset." I am wondering if this is because of my version of TWRP or actually my underlying D80020c rom?
Sorry for a stupid question, I just do not want to mess my phone up again.
Thanks a ton!
Ithink that you have installed an outdated twrp. Install the latest 2.8.7.1 and try to download again the zip of resurrection rom. Remember to use the correct bootstack(for the resurrection choose the loki version)
android extreme said:
Ithink that you have installed an outdated twrp. Install the latest 2.8.7.1 and try to download again the zip of resurrection rom. Remember to use the correct bootstack(for the resurrection choose the loki version)
Click to expand...
Click to collapse
OK I was thinking it might have been the version of TWRP, its odd though. I used AUTOREC which people recommend and it only installs that version.
UGH, where am I worrying about the right bootstack? Sorry its been so long since I have been in the flashing scene and after just hard bricking this each step I want to verify like 5 times. I just wanted to get the OTA updates but that was a fail.
Where am I picking the bootstack? With the version of TWRP?
Thanks and sorry to sound dumb. I promise I am not.
Vector66 said:
OK I was thinking it might have been the version of TWRP, its odd though. I used AUTOREC which people recommend and it only installs that version.
UGH, where am I worrying about the right bootstack? Sorry its been so long since I have been in the flashing scene and after just hard bricking this each step I want to verify like 5 times. I just wanted to get the OTA updates but that was a fail.
Where am I picking the bootstack? With the version of TWRP?
Thanks and sorry to sound dumb. I promise I am not.
Click to expand...
Click to collapse
http://blastagator.ddns.net/twrp/2-8-7-1.php from here you can download the last twrp that can flash from your recovery(choose the right version for your phone ) http://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715 choose from here the right bootstack(if you unistall the resurrection remix choose the loki version if you install any other caf rom use the bumped version)
Thanks I appreciate the help
android extreme said:
http://blastagator.ddns.net/twrp/2-8-7-1.php from here you can download the last twrp that can flash from your recovery(choose the right version for your phone ) http://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715 choose from here the right bootstack(if you unistall the resurrection remix choose the loki version if you install any other caf rom use the bumped version)
Click to expand...
Click to collapse
OK So update TWRP
Install bootstack first before ROM? You recommended Loki, but it says something about jellybean on there. I am currently on KK.
Thanks
Loki is the exploit used to bypass the locked bootloader. The bootstack that use this exploit had a JB bootloader so don't worry. You must flash in this order: bootstack> ROM> gapps> reboot
Whelp, I think it is bricked again. UGH. I installed latest TWRP. Verified it was on there. Downloaded Bootstack. Went into TWRP, loaded the zips up to flash, saw it said again the error about Can't install this package on top of incompatible data. Please try another package or factory reset. Now it is just a black screen.
YEP, bricked again. I can get into the download mode at least this time and when I boot otherwise I get the QHSUSB_BULK issue. This is just wonderful, I have never had such issues with older phones as I am with this G2.
I feel I am back to square one again. I can go into download mode and install 20c again through the TOT but I have no idea what I did wrong. Obviously this time the bootstack is what seemed to destroy things, am I wrong?
Thanks
This's very strange. Nave you flashed the correct files for your model?
All the files I had downloaded were for the d800. Is it because I am on version d80020c vs latest 20y?
Could it be where I had the files located?
The error I am seeing is seeming like a version error.
A simple question: did you have this problem flashing any rom?
I havent tried any other ROMS yet with TWRP. Maybe I should Will try that.
Try a stock based rom (cloudly g2 2.2) that are the most stable and remember to flash a kk bootloader
I am already on KK with 4.4.2 I would still need another KK bootstrap to go to KK again? Sorry I just know this is where I am messing up. Could I not go to Cloudy 3.3?
Thanks so much for answering my dumb questions.
Hi there,
my 802 is running on TWRP after I updated to the latest stock ROM (30D Europe Open). Unfortunately due to problems mentioned in another thread I cannot install a custom ROM currently. Does anyone here have a mirror for me where I can download a TWRP backup of the stock ROM?
Thank you in advance
If you can't install a custom rom, what makes you think you can install a stock? It's pretty easy.
Very helpful... I flashed the latest KDZ on the G2, rooted it and installed TWRP 3.0.2.0, so far so good (believe it or not I flashed a dozen other android devices before). However when I try to install a Marshmallow ROM it gives me Error 7, so that means that getprop.device or so doesnt bring the correct value up. Now when I tried to switch to an older TWRP which is supposed to not have that Error 7 issue (2.7.0.0) I get an error saying I am missing the Loki files in the tmp folder. Now I do not know how to get around the Error 7 (the fix that is mentioned on here didnt work for me, brings up Error 6 instead) I would like to return to a stock backup.
How about giving me actual advice or leaving and letting other people help?
Edit: Booted in Download Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now
I tried to install a custom rom on a a6000. I installed the lolipop stock rom on top of the KitKat stock rom, and managed to boot to it without a problem. I then installed TWRP installed is: 3.3.1-0, and tried to install a custom rom (more specifically I tried this unofficial Lineage). For some reason, the installation fails with:
e3004: This package is for device: Kraft-T, a6000, K30-T,A6000, Kraft-W, Kraft-C, k30t, msm8916,Kraft-A6000,wt86518; this device is .
Updated process ended with ERROR 7
Click to expand...
Click to collapse
when booting into the stock lolipop rom installed I can see that the device is the A6000. I find it strange how the recovery doesn't write which device it is on this error message.
What am I missing here? Usually with other phones, as long as you manage to install a custom recovery then it's a breeze. I cannot figure out how the custom roms don't get installed. Any help appreciated
Managed to flash it in the end. The flash files contain assertions checking if the zip is okay to be flashed on the device (whether the model is the one intended for example).
I found it strange that the error message did not show the model of my device as I was 100% sure it is a A6000 and that is a ROM intended for it.
I ended up overriding the assertion in the file, which seemed to be straightforward to do and the image was flashed without any issues.
DO NOT TRY THIS AT HOME unless you are 10000% sure the image is intended for the device. ?
runningdap said:
I tried to install a custom rom on a a6000. I installed the lolipop stock rom on top of the KitKat stock rom, and managed to boot to it without a problem. I then installed TWRP installed is: 3.3.1-0, and tried to install a custom rom (more specifically I tried this unofficial Lineage). For some reason, the installation fails with:
when booting into the stock lolipop rom installed I can see that the device is the A6000. I find it strange how the recovery doesn't write which device it is on this error message.
What am I missing here? Usually with other phones, as long as you manage to install a custom recovery then it's a breeze. I cannot figure out how the custom roms don't get installed. Any help appreciated
Click to expand...
Click to collapse
Hi... Actually you can flash custom ROM on Lenovo a6000.
Im also using Lenovo a6000 and I'm running custom ROM.... feel free to Reply if u need any help..I'm glad to see that you will.?