Database Users

[ROM][5.0.2][TEST][LOLLIPOP][n7000]RESURRECTION REMIX LP 5.2.5

I Have opened this thread for test purposes only
THIS is a thread of Ressurection Remix 5.2.5 android 5.0.2
LINK to rom here
LINK TO gapps Here
Link to raw kernel here
FIRST YOU NEED the compaitble recovery and kernel ,the same one that cm12 uses
Refer THIS Thread
installing:
copy Rom+Google Apps to sdcard
boot into recovery
(factory reset) (if you get fc's or bootloops after updating from an older rom)
flash the rom and gapps zip file
reboot
now remember always take a nadroid backup of previous rom
some users report this error
Code:
error status 7
assert failed: package_extract_file("boot.img", "/tmp/boot.img")
somebody knows how to fix this error please feel free to share here and test the ROM

status 7 error as I have always seen is related to incompatible recovery.
People got it while trying to flash kk ROMs coming from JB using a non SE Linux recovery.
Maybe try raw kernel?
remember not to boot system after flashing that kernel but reboot to recovery.
REVENGE SOLVES EVERYTHING

Help needed
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17

please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.

tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so

varund7726 said:
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so
Click to expand...
Click to collapse
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING

tysonraylee said:
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)

tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
unfortunately I can't this the only phone I had, my S plus are not with me currently,
anyway, I'm not sure any of this issue causing the error are appear to be mine only, but I'm sure it is
status 7 error failed to write..bla..bla "/tmp/boot.img.."
I already forgot how's the error,
I'll try again in some time, currently at work and kinda busy, :crying:
so sorry guys,
hopefully others help too, :highfive:
please :good:

varund7726 said:
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)
Click to expand...
Click to collapse
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING

tysonraylee said:
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
goodluck buddy! :highfive: :victory: :highfive:
I heard 4.2.2 is going to landed on our device by old sammy, seems nice for forest kernel development! :victory:

kazuna69 said:
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17
Click to expand...
Click to collapse
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps

TouchLeclouds said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps
Click to expand...
Click to collapse
Status 7 here is due to se linux recovery

varund7726 said:
Status 7 here is due to se linux recovery
Click to expand...
Click to collapse
I had the same issue before, my problem was solved by changing the update script

TouchLeclouds said:
I had the same issue before, my problem was solved by changing the update script
Click to expand...
Click to collapse
So can we change bauner update script and check the possibility

mjrifath said:
So can we change bauner update script and check the possibility
Click to expand...
Click to collapse
you can try that, but also keep in mind that this issue could be caused anything else. i just gave the solution that worked for me

Ok i got it to boot.thanks for the help guys.ill open a thread in the dev section and close this one

Error executing updater binary in zip (TWRP)

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

Error executing updater binary

Hi i'm trying to flash Albe95 S6 PORT 3.5 on my i9505 using the latest TWRP. When I try to flash it, I get the error "error executing updater binary in zip". I have done a full wipe and have re downloaded and tried to flash again but to no success, any one have any ideas on how to fix this? I have also tried CWM

What version of TWRP? 2.8.7.0 is the latest.

i9506
Strephon Alkhalikoi said:
What version of TWRP? 2.8.7.0 is the latest.
Click to expand...
Click to collapse
I have the same problem
Mobile Samsung i90506 5.1
Installed twrp 2.8.7
And flashed supersu 2.4.6
I try ed 2 times
Help

hello,
Same problem here with i9500 and latest TWRP. In a OnePlus thread: ..."simply changes the "name" of your device for it to be compatible with the ROM you flash. Most ROM's have the codename for OPO specified as "A0001", while the phone itself reads as "bacon".
So when flashing in TWRP if the ROM's target codename does not match the name given by the device it reads it as incombatible device and cancels the flashing. That flashable zip to my knowledge fixes it so the device now reads as A0001 instead of bacon and then it matches the code string in most ROMs so there is no error when installing. Thanks to @4nlimited3dition for the explanation" simply changes the "name" of your device for it to be compatible with the ROM you flash. Most ROM's have the codename for OPO specified as "A0001", while the phone itself reads as "bacon".

I get an error everytime I try to flash a ROM

Hi, I have this problem that it's driving me crazy, everytime I flash a ROM TWRP gives me this error:
Code:
Updater process ended with ERROR: 7
Error installing zip file: etc
My phone is a SM-J500FN with TWRP Recovery 3.1.0-0 by Zonik, so far I tried LineageOs (both 13.1 and 14.0) and Resurrection Remix, I get always the same error.
edit: also tried with AospExtended, no luck whatsoever.

Odin Eidolon said:
Hi, I have this problem that it's driving me crazy, everytime I flash a ROM TWRP gives me this error:
Code:
Updater process ended with ERROR: 7
Error installing zip file: etc
My phone is a SM-J500FN with TWRP Recovery 3.1.0-0 by Zonik, so far I tried LineageOs (both 13.1 and 14.0) and Resurrection Remix, I get always the same error.
edit: also tried with AospExtended, no luck whatsoever.
Click to expand...
Click to collapse
You need to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms which are based on AOSP/Lineage (cm).
TWRP 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844.
If you still have errors when flashing, then choose in TWRP "Copy log to sdcard" (something like that) and post the recovery.log .

#Henkate said:
You need to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms which are based on AOSP/Lineage (cm).
TWRP 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844.
If you still have errors when flashing, then choose in TWRP "Copy log to sdcard" (something like that) and post the recovery.log .
Click to expand...
Click to collapse
So first I need to downgrade my stock ROM then I can flash Lineage/whatsoever ROM?

Odin Eidolon said:
So first I need to downgrade my stock ROM then I can flash Lineage/whatsoever ROM?
Click to expand...
Click to collapse
Yes. Just like i told you in my previous post, you have to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms based on AOSP/Lineage (cm).

#Henkate said:
Yes. Just like i told you in my previous post, you have to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms based on AOSP/Lineage (cm).
Click to expand...
Click to collapse
Bad news, it doesn't work.
Downgraded to 5.1.1, installed the TWRP linked by you, but still error 7 when I try to flash a ROM.
edit: ok, this time I tried to flash LineageOS 13.1 and it worked. Now I have to figure out how to flash Lineage 14

Odin Eidolon said:
Bad news, it doesn't work.
Downgraded to 5.1.1, installed the TWRP linked by you, but still error 7 when I try to flash a ROM.
edit: ok, this time I tried to flash LineageOS 13.1 and it worked. Now I have to figure out how to flash Lineage 14
Click to expand...
Click to collapse
I've told you:
If you still have errors when flashing, then choose in TWRP "Copy log to sdcard" (something like that) and post the recovery.log.
Click to expand...
Click to collapse
In recovery.log you can see what's the problem.

#Henkate said:
I've told you:
In recovery.log you can see what's the problem.
Click to expand...
Click to collapse
Yeah, you're right, sorry.
But good news, flashed LOS 14 on the old 13.1, everything works fine.
Thanks for your help!

'E:2001 Failed to update vendor' Error:7 while flashing ROMs using TWRP

How to fix this error. I can only flash AOSiP ROM.
I have tried by clearing assert lines using notepad++.
I am using TWRP 3.2.1
Please help me ASAP

Anuraj KR said:
How to fix this error. I can only flash AOSiP ROM.
I have tried by clearing assert lines using notepad++.
I am using TWRP 3.2.1
Please help me ASAP
Click to expand...
Click to collapse
Download new recovery for latest roms. Else you wlll face problems. You should be on latest firmware before flashing custom roms

sk.vyshak said:
Download new recovery for latest roms. Else you wlll face problems. You should be on latest firmware before flashing custom roms
Click to expand...
Click to collapse
Thanks for reply?

Still getting error 7.
I have deleted "assert" command. I'm using twrp 3.2.I hope it's the latest for k6 power.But evert time I flash AICP oreo and DOT oreo roms,I'm getting "Failed to update vandor image" and "Error:7".
Why guys??I've tried somany times.Please help me.