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

OnePLus two with NO OS and Oneplus recovery

Hey, yesterday i tried to clean flash RR ROm (already was using it) and when i flashed the rom zip file, it showed patching system image uncondtionally , and flashing file 1 of 1 for like 30 min then i turned off my device. And from then, i have been stuck with oneplus logo, sometime twrp sometime oneplus recovery https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Tried this method bcz i thought my device was bricked but the last step failed. No i again got back to twrp through fastboot method
https://forums.oneplus.net/threads/...-custom-recovery-root-efs-backup-more.345478/
And one more thing, when i am copyingthe rom files from pc to device, the progress bar goes well upto like 50% and then suddenly closes. But copied file size is same as of original. Is this the main problem?
file not getting copied properly?
Now i am in twrp and cant even start the flash proces as it now says E: error executing updater binary in zip ' ROM Name' error flashing zip.
What should i do now? Just want to turn on my phone, no matter if its RR ROM or OOS rom . Please help.
Also again went to oneplus recovery using that unbrick method and then tried to install OOS 2.2.1 using adb sideload method, but it stops at 47% everytime. What could be the reason? Should i go to service center tomorrow because from wednesday i will be having my exams and i want my phone up and running by tomorrow evening. Please help me . It's an emergency. Also asked for help at xda RR ROm forum but no such help yet .
And is my motherboard damaged ? No, right?

g530h keeps getting detected as hm2014811

I installed the twrp 2.8.4.0 on my rooted G503H, but when i tried to install a custom rom, it shows: "error executing updater binary in zip" and says that the package is for g530h, and that my device is detected as HM2014811 (XIAOMI REDMI 2). I rooted the phone using the Mohan metod described here: http://forum.xda-developers.com/grand-prime/general/successfully-rooted-galaxy-grand-prime-t2935607
Thanks in advance for the help
edit: I reflashed stock and the twrp again but not rooted, yet i still have the same problem, unfortunately the TWRP.V2.8.4.0.tar.md5 is the only i found flashable in my galaxy prime, even the zip one didn't work

Same problem with me, anyone can help ?

zchronos said:
I installed the twrp 2.8.4.0 on my rooted G503H, but when i tried to install a custom rom, it shows: "error executing updater binary in zip" and says that the package is for g530h, and that my device is detected as HM2014811 (XIAOMI REDMI 2). I rooted the phone using the Mohan metod described here: http://forum.xda-developers.com/grand-prime/general/successfully-rooted-galaxy-grand-prime-t2935607
Thanks in advance for the help
edit: I reflashed stock and the twrp again but not rooted, yet i still have the same problem, unfortunately the TWRP.V2.8.4.0.tar.md5 is the only i found flashable in my galaxy prime, even the zip one didn't work
Click to expand...
Click to collapse
Instead using mohan root, you could actually use latest supersu flashable zip to get root, and there's twrp v2.8.7.0 on this grand prime subforum , you can get a guaranteed rooted device with no errors
---------- Post added at 11:24 AM ---------- Previous post was at 11:21 AM ----------
D.R-Ult.Googler said:
Instead using mohan root, you could actually use latest supersu flashable zip to get root, and there's twrp v2.8.7.0 on this grand prime subforum , you can get a guaranteed rooted device with no errors
Click to expand...
Click to collapse
Before doing my suggestion, flash stock firmware first then factory reset and wipe cache partition using stock recovery to avoid errors

zchronos said:
I installed the twrp 2.8.4.0 on my rooted G503H, but when i tried to install a custom rom, it shows: "error executing updater binary in zip" and says that the package is for g530h, and that my device is detected as HM2014811 (XIAOMI REDMI 2). I rooted the phone using the Mohan metod described here: http://forum.xda-developers.com/grand-prime/general/successfully-rooted-galaxy-grand-prime-t2935607
Thanks in advance for the help
edit: I reflashed stock and the twrp again but not rooted, yet i still have the same problem, unfortunately the TWRP.V2.8.4.0.tar.md5 is the only i found flashable in my galaxy prime, even the zip one didn't work
Click to expand...
Click to collapse
Step No 1:- First, download the TWRP Package (TWRP-SMG530H.tar), Odin tool (Odin v3.10.7) and SuperSU (SM-G530H-SuperSU-v2.46.zip) files on the desktop of your PC for Grand Prime.
Step No 2:- Copy/paste the SuperSU file to the internal storage of your device.
Step No 3:- Extract the TWRP file to get the file with .tar extension and Odin flashing tool also to get the Odin3_v3.10.7.exe file.
Step No 4:- Switch off the Galaxy Grand Prime in order to boot into the Download Mode.
Step No 5:- Switch on the device while pressing and holding Volume UP + Home + Power buttons at the same time. Once a warning screen with a yellow triangle sign appears, press the Volume Up button to enter into Download Mode.
Step No 6:- Run Odin as administrator on the PC.
Step No 7:- Connect the phone using its USB data cable with the PC.
Step No 8:- Once the Grand Prime is connected successfully with the PC, the ID:COM port will turn Blue on Odin and you’ll see “Added!!” message.
Step No 9:- Click on the AP button on Odin and locate the firmware file (TWRP-SMG530H.tar) that you have already extracted. Select it.
Step No 10:- Ensure that the Auto Reboot and F. Reset Time options are checked and the Re-Partition option should be unchecked.
Step No 11:- Begin the TWRP installation by clicking on the Start button in Odin. This process may take a few minutes.
Step No 12:- A PASS! message will be displayed on Odin after the TWRP installed successfully and the device will restart.
Step No 13:- Disconnect the device and turn it OFF to boot into TWRP recovery mode.
Step No 14:- Turn ON the phone by pressing and holding the Volume Up + Home + Power buttons altogether to boot into the TWRP recovery.
Step No 15:- Tap the Install button in TWRP and select the SM-G530H-SuperSU-v2.46.zip.
Step No 16:- After the installation is completed, reboot the system.
Links -
TWRP - http://www.4shared.com/file/XQAlhoclce/TWRP-SMG530H.html?
Super Su - http://www.4shared.com/zip/0vuOXMLvba/SM-G530H-SuperSU-v246.html?
Odin - http://www.androidblog.gs/download-odin-rom-flashing-tool-for-all-samsung-smartphones/
And install SAMSUNG USB DRIVERS on your PC before doing anything - http://www.mediafire.com/?8tigkfg2oczvguv
Good Luck.
Note : I'm not responsible for any kind of negative Issues. Do it on your own risk.

zchronos said:
I installed the twrp 2.8.4.0 on my rooted G503H, but when i tried to install a custom rom, it shows: "error executing updater binary in zip" and says that the package is for g530h, and that my device is detected as HM2014811 (XIAOMI REDMI 2). I rooted the phone using the Mohan metod described here: http://forum.xda-developers.com/grand-prime/general/successfully-rooted-galaxy-grand-prime-t2935607
Thanks in advance for the help
edit: I reflashed stock and the twrp again but not rooted, yet i still have the same problem, unfortunately the TWRP.V2.8.4.0.tar.md5 is the only i found flashable in my galaxy prime, even the zip one didn't work
Click to expand...
Click to collapse
same problem what should i do next , i dont have any stock rom for doing the same... pls help me the phone is rooted and the recovery is set ok
---------- Post added at 04:12 AM ---------- Previous post was at 03:57 AM ----------
ashrose said:
same problem what should i do next , i dont have any stock rom for doing the same... pls help me the phone is rooted and the recovery is set ok
Click to expand...
Click to collapse
i will tell u the actual incident happened:
My friend gave his galaxy grand prime with kitkat 4.4 and the built no SM-G530H to root it and install an custom os such as resurrection remix. I rooted the smartphone and installed recovery twrp recovery successfully and wiped out dalvik cache, data and internal storage which led to deletion of the OS from the system so whenever i reboot the phone stays in the initial boot where it shows the samsung logo so i downloaded custom roms from xda dev site XDA Member kn06497
Tweet Like +1
[ROM] [G530H] ResurrectionRemix 5.1.1 [STOPPED][STABLE][UPDATE][2016/09/29] , but none of the ROMS seems to work as the flashing was not possible as it gives the error message "error executing updater binary in zip" now what should i do now..
pls help me i m in great distress.
At least give me any rom which can be flashed successfully.:crying::crying:

flash stock with odin, and flash latest twrp ( 3.1.0.0 )

plz help for redmi 2 prime lolipop 5.1.1

plz help
whenever i am going to flash any zip file in twrp it showing error
This package is for "HM2014811" devices; this is a "wt88047
i have flashed file wt88047_stock_recovry.img
how to change device name in twrp..
plz reply.....

Viraj007 said:
plz help
whenever i am going to flash any zip file in twrp it showing error
This package is for "HM2014811" devices; this is a "wt88047
i have flashed file wt88047_stock_recovry.img
how to change device name in twrp..
plz reply.....
Click to expand...
Click to collapse
dont change in recovery...
only edit your build.prop and change device name...

​
saurabh1234 said:
dont change in recovery...
only edit your build.prop and change device name...
Click to expand...
Click to collapse
Sir,
it not worked for me. Device is stucked on MI logo after reboot. I have flashed again rom to recover.
however i have flashed yesterday wsmtool.zip(xposed) file.after that flashed twrp
after that i think the device name changed. It was for redmi 1s i think.
so hw to unistall that file.

Viraj007 said:
​
Sir,
it not worked for me. Device is stucked on MI logo after reboot. I have flashed again rom to recover.
however i have flashed yesterday wsmtool.zip(xposed) file.after that flashed twrp
after that i think the device name changed. It was for redmi 1s i think.
so hw to unistall that file.
Click to expand...
Click to collapse
which file?? xposed??
flash xposed uninstaller

plz anybody provide xposed unistaller file

Viraj007 said:
plz anybody provide xposed unistaller file
Click to expand...
Click to collapse
Just search for Redmi 2 XPosed Uninstaller
On google, of course

The easiest solution I can provide is, use philz recovery. I've used twrp too but when it comes to flashing MIUI, it throws that error of "Unsupported device", philz never did that. Been using philz for more than 6 months now and never had any problem flashing MIUI or any other custom ROM

saurabh1234 said:
dont change in recovery...
only edit your build.prop and change device name...
Click to expand...
Click to collapse
Thanks for the information, it worked for me (despite I had to change all appearances of HM2014811 to wt88047, found in 4 different files, and zip it again before flashing through twrp)
I used the above to install a xiaomi.eu rom in my Redmi 2 in order to have my own language (spanish) :good:

Problems with flashing custom roms

Hi all
I have a Smasung Galaxy note 3 (sm-n9005 htle)
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
so i googled for this error. and found a fix.. so i deleted the first lines in the updater-script... after that i tried it again. But it ditent work. It fails with the massage: could not found the binary file.
I wiped and formated the Smartphone as well.
I spend allready the whole day to install any custom rom...
Im really sad about this... maybe someone can help me.
And sorry for my bad english.

Did you confirm the phone's model # in download before flashing TWRP?

audit13 said:
Did you confirm the phone's model # in download before flashing TWRP?
Click to expand...
Click to collapse
Do you mean, that i downloaded the TWRP for my device model? Yes i did
Otherwise what do you mean?

Before flashing anything, especially if I got the phone used, I boot the phone into download just to confirm that the model # matches the label under the battery.
Only after confirming the model # in download do I start flashing files to the phone.
Does the error 7 happen with all custom ROMs?

audit13 said:
Before flashing anything, especially if I got the phone used, I boot the phone into download just to confirm that the model # matches the label under the battery.
Only after confirming the model # in download do I start flashing files to the phone.
Does the error 7 happen with all custom ROMs?
Click to expand...
Click to collapse
The Modelnumber in the downloadmode and the number under the battery are the same.
Yes i tried maybe five custom roms.

Fail is usually user fails to read instructions .
Error one .
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
Aroma installer does not work and thats why instructions tell you to use the older TWRP .
Instructions .
>>>Get a good recovery. TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
>>>TWRP recovery recommended, 2.8.7.0. Newer versions are not supported

JJEgan said:
Fail is usually user fails to read instructions .
Error one .
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
Aroma installer does not work and thats why instructions tell you to use the older TWRP .
Instructions .
>>>Get a good recovery. TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
>>>TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
Click to expand...
Click to collapse
Thanks for it.
I tried now the TWRP 2.8.7.0. For my device there are two versions. The twrp-2.8.7.0-hlte-4.3.img.tar and twrp-2.8.7.0-hlte-4.4.img.tar.
First i tried now the twrp-2.8.7.0-hlte-4.4.img.tar but still gives me an error :
Updating partition deteils...
... done
Full SELinux support is present.
MTP Enabled
Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data.
Please try another package or run factory reset
E:Error executing updater binary in zip '/external_sd/cm-23.1-20161016-NIGHTY-hlte.zip'
Updating partition details...
...done
The other version of TWRP doesent work. It ends up in a reboot circle.

Try Philz Recovery .
That fails flash a clean stock rom
BUT FIRST
.Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'
Can't install this package on top of incompatible data.
Please try another package <<<< or run factory reset >>>
---------- Post added at 11:57 AM ---------- Previous post was at 11:43 AM ----------
You would be best flashing stock rom through Odin and then if you have problems post exact details .
What rom flashed etc .

JJEgan said:
Try Philz Recovery .
That fails flash a clean stock rom
BUT FIRST
.Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'
Can't install this package on top of incompatible data.
Please try another package <<<< or run factory reset >>>
---------- Post added at 11:57 AM ---------- Previous post was at 11:43 AM ----------
You would be best flashing stock rom through Odin and then if you have problems post exact details .
What rom flashed etc .
Click to expand...
Click to collapse
Hell Yeah!
Thanks a lot it finaly worked with Philz Recovery...
I wiped my phone several times before intsalling the rom... but with Philz Recovery it worked!
Thanks so much! Im really happy now... its not the first device with a custom rom... but the first with problems
Thanks thanks thanks