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

Problem with CM/C-rom or any kind or ROM for my Nexus 4

Hello,
I'm new on this forum and I wanted to ask something (Newbie).
Ok so my Nexus 4 was KitKat 4.4.2 and then I changed my rom to C-Rom through a official nexus root site (tryed to root the nexus 4) didn't work and I was stuck without Gapps and without Root for almost a year and a half, about a half a year ago a friend of mine showed me a video of how to upgrade to Lollipop using ADB/ADT stuff, So I flashed my phone and it automaticly installed for me Lollipop 5.0, a little bit after that I found a Nexus Root Toolkit and installed root with TWRP, then I wanted a black theme badly on my phone so I installed cyanogenmod 12 and it worked but again without gapps so I reflashed my nexus back to lollipop (I must say that without backuping files it's annoying to flash your phone).
Is there any way to install Cyanogenmod 12 for the nexus 4 with gapps?
Please replay, thanks
- Titanate

1.Download CM12 latest nightly + PA 5.0 full gapps.
2.Create .gapps-config file on same folder with app names to exclude(required for stock pa gapps package- due to data partition size limit)
3. OK now boot into TWRP. Wipe - flash CM12 - Wipe - flash gapps - Reboot
These are the basic steps I tried.

lahirulakshi said:
1.Download CM12 latest nightly + PA 5.0 full gapps.
2.Create .gapps-config file on same folder with app names to exclude(required for stock pa gapps package- due to data partition size limit)
3. OK now boot into TWRP. Wipe - flash CM12 - Wipe - flash gapps - Reboot
These are the basic steps I tried.
Click to expand...
Click to collapse
"2.Create .gapps-config file on same folder with app names to exclude(required for stock pa gapps package- due to data partition size limit)"
Again Newbie, didn't understand this, how do I make a config? and I've downloaded this version of gapps and CW
gapps-lp-20141212-signed.zip
cm-12-20150226-NIGHTLY-mako.zip‬

Titanate said:
"2.Create .gapps-config file on same folder with app names to exclude(required for stock pa gapps package- due to data partition size limit)"
Again Newbie, didn't understand this, how do I make a config? and I've downloaded this version of gapps and CW
gapps-lp-20141212-signed.zip
cm-12-20150226-NIGHTLY-mako.zip‬
Click to expand...
Click to collapse
I'm not sure whether your downloaded gapps are compatible with CM12. Try PA Gapps package from this link: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
.gapps-config file is required only if you're using the stock gapps package ~ 400mb. Creating one is a bit tricky. Open notepad and type the names of apps that you need to exclude. You can find the names in FAQ section in above mentioned post. Then save the file as .gapps-config at same location of gapps package. Now you can flash gapps without getting insufficient storage error.

Titanate said:
Hello,
I'm new on this forum and I wanted to ask something (Newbie).
Ok so my Nexus 4 was KitKat 4.4.2 and then I changed my rom to C-Rom through a official nexus root site (tryed to root the nexus 4) didn't work and I was stuck without Gapps and without Root for almost a year and a half, about a half a year ago a friend of mine showed me a video of how to upgrade to Lollipop using ADB/ADT stuff, So I flashed my phone and it automaticly installed for me Lollipop 5.0, a little bit after that I found a Nexus Root Toolkit and installed root with TWRP, then I wanted a black theme badly on my phone so I installed cyanogenmod 12 and it worked but again without gapps so I reflashed my nexus back to lollipop (I must say that without backuping files it's annoying to flash your phone).
Is there any way to install Cyanogenmod 12 for the nexus 4 with gapps?
Please replay, thanks
- Titanate
Click to expand...
Click to collapse
You didn't flash a gapps package? Most custom ROMs do not include (more accurately, cannot include due to licensing issues) gapps so you need to flash a gapps package after flashing a ROM.

jr67 said:
You didn't flash a gapps package? Most custom ROMs do not include (more accurately, cannot include due to licensing issues) gapps so you need to flash a gapps package after flashing a ROM.
Click to expand...
Click to collapse
Thanks so much I have now cm12 with lollipop 5.0.2

GAPPS crash with crdroid Rom, how to install ?

Hello,
I am new on this forum but I used different roms (Omega rom) on my phone, a samsung S4 I9505.
As the last version of Omega Rom didn't work on my phone (boot couldn't succeed), i Installed CrDroid jfltexx 5.1.1
(http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-crdroid-t3017844)
I want to have some of the Google Apps like the Play Store... so i downloaded on OpenGapps the package ARM / 5.1 / Mini. Yet after I installed it in the recovery mode, and i booted. As i was configuring the phone, the Google apps were crashing as i followed the instructions...
Now i i did another complete install of the phone WITHOUT the GAPPS. How should i proceed to get at minimum the Play Store ?
Thanks !
First time installing crDroid to your i9505, or coming from another ROM:
- Make sure you're running a proper working Recovery (CWM or TWRP)
- Copy GApps and crDroid zip to your internal SDCard
- Boot into Recovery
- Wipe system,dalvik,data and cache
- Flash crDroid zip
- Flash GApps zip
- DO A DATA WIPE / FACTORY RESET
- Reboot
Click to expand...
Click to collapse
[ROM][Official **crDroid**][][Marshmallow - 6.0.1][CM13-based][14/12]

Leonard26000 said:
Hello,
I am new on this forum but I used different roms (Omega rom) on my phone, a samsung S4 I9505.
As the last version of Omega Rom didn't work on my phone (boot couldn't succeed), i Installed CrDroid jfltexx 5.1.1
(http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-crdroid-t3017844)
I want to have some of the Google Apps like the Play Store... so i downloaded on OpenGapps the package ARM / 5.1 / Mini. Yet after I installed it in the recovery mode, and i booted. As i was configuring the phone, the Google apps were crashing as i followed the instructions...
Now i i did another complete install of the phone WITHOUT the GAPPS. How should i proceed to get at minimum the Play Store ?
Thanks !
[ROM][Official **crDroid**][][Marshmallow - 6.0.1][CM13-based][14/12]
Click to expand...
Click to collapse
Lately Opengapps is giving me lots of trouble. Try using a different gapps package
For example:
http://download.dirtyunicorns.com/files/gapps/banks_gapps/

Thank you.
Do you have a version for android 5.1.1 ?
To install it, i boot in recovery mode and install it ?

maybe try with another gappsy version

ter4bite said:
maybe try with another gappsy version
Click to expand...
Click to collapse
Thank you for you proposition.
Finally, I used the 6.0 rom and Gapps are running fine.
Yet, MMS/SMS don't work... Should I change the bootloader and modem ? I use SM_Modem_XXUHOB8_and_LTE_Modem_XXUHOB8 and BL_I9505XXUHOB8_user_low_ship_MULTI_CERT
Cheets

VertexOS 1.9 [UNOFFICIAL][2017/2/11] [KIPPER] [AOSP+LOS]

HI ALL! With new Rom
VertexOS aims to provide a simple but enhanced near-stock AOSP experience with carefully selected features and an emphasis on stability and smoothness.​
what doesn't work ?
everything is working perfectly.
Coming from another ROM, OR if a CLEAN FLASH is required
1) Download the Vertex... .zip file.
2) Download a 7.1 GApps package.
3) Boot into recovery (TWRP)
4) Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
5) Flash the Vertex... .zip file
6) Flash Nougat-compatible GApps : http://opengapps.org/ / ARM64,7.1,pico
7) Reboot
Download:https://www.androidfilehost.com/?fid=745425885120707303
enjoy!
Credits:
- LineageOS
- AOSPA
- Citrus-CAF
- DU
- PureNexus
- Zephyr-OS
IF YOU LIKE MY WORK PLEASE HIT THANKS .
-IMPORTANT- : To install this rom you must have installed TWRP-3.0.3.0 , download from here https://www.androidfilehost.com/?fid=529152257862697990
To easy install from TWRP recovery :
1- open "install" section.
2- SELECT "install img" in the bottom .
4- Chose the place of TWRP-3.0.3.0.
5- install as RECOVERY , then reboot to recovery.
XDA:DevDB Information
ROM [AOSP + LOS], ROM for the Wileyfox Storm
Contributors
PS-DEV
Source Code: https://github.com/VertexOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP + LOS
Version Information
Status: Stable
Created 2017-02-11
Last Updated 2017-02-20

Received

Received !

Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.

Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.

Cannot inatall gapps (Wrong Architecture)
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck

Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.

I installed fine with the nano apps and 64 bit, no issues

miSAKe said:
Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.
Click to expand...
Click to collapse
Check the first post . i have been edit.

Chron0s said:
Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.
Click to expand...
Click to collapse
show your PM.

Chron0s said:
Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.
Click to expand...
Click to collapse
NO NO
ARM64 ARMv8 .

ChuckeCheese said:
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck
Click to expand...
Click to collapse
1- check to wipe this partitions :
- SYSTEM
- CACHE
- Dalvick-cache.
- DATA
and dont forget to factory reset .
2- first install rom then Gapps. download from here http://bit.ly/2kQf3Le

PS-DEV said:
Check the first post . i have been edit.
Click to expand...
Click to collapse
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.

miSAKe said:
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.
Click to expand...
Click to collapse
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?

PS-DEV said:
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?
Click to expand...
Click to collapse
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.

miSAKe said:
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.
Click to expand...
Click to collapse
The phone boot to rom or not ??

PS-DEV said:
The phone boot to rom or not ??
Click to expand...
Click to collapse
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.

miSAKe said:
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.
Click to expand...
Click to collapse
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .

PS-DEV said:
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .
Click to expand...
Click to collapse
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.

miSAKe said:
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.
Click to expand...
Click to collapse
Stock firmware or what? ,, to install version 13 Bootloader , just install any nightly cm13 then back to recovery and install TWRP 3.0.3.0 ??.

Unable to flash (bootloop) android 10 & 11 rom

I have been currently facing trouble in flashing android 10 & 11 rom, where it always ended with continous bootloop.
*i did flash the relevant firmware version
*there is no problem when flashing android 9 rom
*i use the latest orange fox R11

hilmih said:
I have been currently facing trouble in flashing android 10 & 11 rom, where it always ended with continous bootloop.
*i did flash the relevant firmware version
*there is no problem when flashing android 9 rom
*i use the latest orange fox R11
Click to expand...
Click to collapse
I would try TWRP and see if that helps.

hilmih said:
I have been currently facing trouble in flashing android 10 & 11 rom, where it always ended with continous bootloop.
*i did flash the relevant firmware version
*there is no problem when flashing android 9 rom
*i use the latest orange fox R11
Click to expand...
Click to collapse
Make sure you get an official stock ROM by here https://c.mi.com/oc/miuidownload/detail?device=1700360
Steps to flash without MiFlash:
1) you will need twrp, if you dont know how go here https://www.xda-developers.com/how-to-install-twrp/
2) install the official ROM in your pc and transfer it in your phone while in twrp (the pc will detect phone while in twrp)
3) go to main menu of twrp > install > select the file that you transferred the ROM.zip file in
4) select it and flash it
5) reboot to system
6) Enjoy miui 12 and android Q