So here is the latest version of TWRP with AROMA touch working.
It is no longer based off of emwno repos so I think it is worthy of a new thread. Also aroma touch is now working after some kernel modifications.
Changelog:
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
What's new in 2.6.0.0:
Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
Download:
N5100: http://www.androidfilehost.com/?fid=23159073880936414
N5110: http://www.androidfilehost.com/?fid=23156208500211927
Now go touch all over those roms those roms!
Well here is a aroma demo zip to play around with until ROM Chefs utilize aroma touch.
Credit:
@sbrissen for original port of CM10.1/10.2 to n5110.
@Maui for original port of CM10.1 to n5100.
@Dees_Troy & TEAMWIN for making TWRP
Donations:
Kraszimir Sziderov - $.$$
it's fully working ? some bug apart the update-script ?
ps: thanks for your hard work !! thanks from my N5110 !!!
AFAIK, it should be working 100%.
N5110 now have a separate build.
The assert issue is because I build from n5100 device tree which has. "TARGET_OTA_ASSERT_DEVICE := kona3gxx,n5100,GT-N5100,kona3g"
so rom like sbrissen CM10.2 for N5110 has this lines:
assert(getprop("ro.product.device") == "konawifixx" || getprop("ro.build.product") == "konawifixx" ||
getprop("ro.product.device") == "n5110" || getprop("ro.build.product") == "n5110" ||
getprop("ro.product.device") == "GT-N5110" || getprop("ro.build.product") == "GT-N5110" ||
getprop("ro.product.device") == "konawifi" || getprop("ro.build.product") == "konawifi");
that assert will fail. so you can remove that line and it will flash until I build for N5110.
Thanks for the good work!
There is still no 'Mount USB Storage' button in the 'Mount Menu'
AROMA touch working fine (n5100)!
That is because it doesn't work. It is a TWRP problem outlined here: http://teamw.in/DataMedia
There is a way to get the phone in UMS mode in android though so might be doable in recovery. Even so we will only get the external sd card part. Wont be able to mount the internal storage.
Alright N5110 build is up. Cant test it because I don't have the device but should be good to go.
Just tried to install for the 5110 but received an update binary error - going to redownload directly and try again.
Yup, I did it again. lol Hopefully Link fixed now.
EDIT- Something funky was happening (buttons wouldn't work; I'd touch on one side of the screen and would hit a button apparently)after installing this, so I flashed back to the previous version.
On which version? Looks like the n5110 version. Yeah I have no way to test it for that device. I'll see what I can do.
Found Issue with n5110 version. Forgot to fix touch drivers. in that build. Fixing it now and will reupload in the next hour. Thanks for reporting
New build for n5110 http://www.androidfilehost.com/?fid=23156208500211927.
nickdollahz said:
On which version? Looks like the n5110 version. Yeah I have no way to test it for that device. I'll see what I can do.
Found Issue with n5110 version. Forgot to fix touch drivers. in that build. Fixing it now and will reupload in the next hour. Thanks for reporting
New build for n5110 http://www.androidfilehost.com/?fid=23156208500211927.
Click to expand...
Click to collapse
That one works perfectly! Thank you so much.
Nick I knew you would come through, you da man!!!
Works like a charm on my 5110. Thanks.
Yo, Nickdollahz. When will we see 2.6.3.6?
THX i flash the N5110 version and the touch is very responsive also in aroma but in aroma there is some problem to scroll up and down
Muffycheeks said:
Yo, Nickdollahz. When will we see 2.6.3.6?
Click to expand...
Click to collapse
Darn tapatalk...meant to quote instead of thank. Anyways, no ETA requests on XDA! It's like rule 1. Now you know.
Not really a request, but would there be one for 5120?
Sent from my Nexus 4 using Tapatalk
n5120 has different mount points and I dont have the device in question so I would not be able to test it at all. So most likely wont be seeing one of those soon until there is a developer with that device.
As far as updating, I think I'm gonna wait till there is a major release unless I get some spare time. Working with sbrissen to get the CM n5100 and n5110 trees combined and submitted to Cyanogenmod.
nickdollahz said:
n5120 has different mount points and I dont have the device in question so I would not be able to test it at all. So most likely wont be seeing one of those soon until there is a developer with that device.
As far as updating, I think I'm gonna wait till there is a major release unless I get some spare time. Working with sbrissen to get the CM n5100 and n5110 trees combined and submitted to Cyanogenmod.
Click to expand...
Click to collapse
Working on CM rom.....YES!!!!!:good:
Muffycheeks said:
Working on CM rom.....YES!!!!!:good:
Click to expand...
Click to collapse
also cm11 ?
Related
NOW THAT WE HAVE OFFICIAL NIGHTLY BUILDS I THOUGHT IT WARRANTED A PROPER THREAD NOT A KANG ANYMORECyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.0 (ICS), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Click to expand...
Click to collapse
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
SOURCES
General:
http://github.com/CyanogenMod
Device:
https://github.com/CyanogenMod/android_device_samsung_p4
https://github.com/CyanogenMod/android_device_samsung_p4-common
Kernel:
https://github.com/CyanogenMod/android_kernel_samsung_p4 (Official)
https://github.com/pershoot/galaxy-2636 (Unofficial)
What's working?
3G - Make sure you have the correct APN Settings for your carrier/region.
HWA Video - No all the formats are supported, Blame NVidia or ... the world - (YouTube does work)
What's not working?
Camera - This will only be fixed once we get an ICS Leaked ROM - Period, so stop asking!
I want feature X?
No - You will not get it or maybe you will, I have no Idea what feature will get implemented. This is not the place to ask.
First time installing CyanogenMod 9 to your Tablet (3g version), or coming from another ROM:
- Make sure you are rooted. (Plenty of thread available about how to do it)
- Make sure you're running a proper working ClockworkMod-Recovery version 5.5.0.4 not any other version (Recovery[UPDATED]). This is the latest (2012-05-24) that works with the device make sure you flash this recovery via ODIN.
IF YOU DO NOT INSTALL THIS RECOVERY YOU WILL NOT BE ABLE TO INSTALL CORRECTLY/YOU WILL GET UNKNOWN VERSION ABORTING INSTALL ERROR
- Copy GApps and CM9 ZIPs to your internal SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET (First Time Users)
- Flash CM9 zip
- Flash GApps zip
- Reboot
- Enjoy!
NOTICE:
IF YOU EXPERIENCE ANY ISSUE WITH THE ROM AND YOU HAVE OVERLCOCKED/MODDED THE ROM DO NOT REPORT THE ISSUE UNTIL YOU HAVE CONFIRMED THE ISSUE ALSO OCCURS WHEN NOT OVERCLOCKED/MODDED!
IF YOU EXPERIENCE ANY ISSUE AND YOU HAVE CONFIRMED IT IS AN ISSUE POST LOGS, USE PASTEBIN.COM IF YOU CANNOT ATTACH LOGS TO YOUR POST.
See second post on how to get logs to post logs!
Latest nightlies:
http://get.cm/?device=p4&type=nightly
Changelog
http://changelog.bbqdroid.org/#p4/cm9/next
Google Apps:
http://goo.im/gapps
HOWTO SEND PATCHES
Getting Started:
http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit
Example:
- cd ~/android/system
- repo start branchname CyanogenMod/android_device_samsung_p4
-- Make your changes at device/samsung/p4
- cd device/samsung/p4
- git add -A
- git commit -a
- cd ~/android/system
- repo upload CyanogenMod/android_device_samsung_p4
Navigate to http://review.cyanogenmod.com , click your commit and add the reviewers.
If you suffer from a rolling recovery fix available here:
# Catching up on APN updates. If your default APN is missing or inaccurate, be sure to drop a comment on http://goo.gl/aDur and we'll go about adding them to the OS.
If you experience an issue. Provide logs. If you have adb do this:
adb logcat >> logcat.log
adb logcat -b radio >> radio.log (if you experience 3g issues)
adb shell dmesg >> dmsg.log (got wifi issues or weird stuff happening)
If you have a reboot/kernel panic or such.
Get last_kmsg:
adb pull /proc/last_kmsg or if you not near a pc go to terminal emulator :
type su then enter.
cp /proc/last_kmsg /sdcard/
Exit terminal
You can then later extract last_kmsg and post it here.
Or you can download OS monitor here: https://play.google.com/store/apps/details?id=com.eolwral.osmonitor.tablet and get logs via the app. That is what I sometimes use personally.
Good idea. Recently found out about the nightlies myself. Do we know something about broken things?
Camera, and highres video playback
Skickat från min GT-P7500 via Tapatalk 2
ivarson_swe said:
Good idea. Recently found out about the nightlies myself. Do we know something about broken things?
Camera, and highres video playback
Skickat från min GT-P7500 via Tapatalk 2
Click to expand...
Click to collapse
This ROM ( or any other ) doesn't have nothing to do with HI-Res videos not working... It's Tegra2 fault and nVidia engineers who designed this chip and deside not to include some CPU instructions.
And for camera we must wait until samsung release their official ICS. After that CM team will just pull out drivers for camera from official build and we will have working cameras.
Sent from my GT-P7500 using Tapatalk 2
i've been using it. works great so far. i was using a kang build but i had terrible boot loop issues and the battery would die in hours. but since switching to these those are now gone!
**** the camera , stupid samsung is not care about us
I know.
But that sort of questions will be asked repeatedly, supplying it in first/second post will probably eliminate most such questions later on
Regarding 720p playback it worked like a charm on both stock- custom HC ROMS and also on CM9 nightlies until a couple of builds ago.
What I meant was that it should be posted, but it sounded more like a question I guess. See that some broken things are posted now. That's good
Skickat från min GT-I9100 via Tapatalk 2
Install Failure
AOKP_p4_milestone-4.zip
---------- Post added at 02:19 AM ---------- Previous post was at 02:07 AM ----------
Using a P7500 with AKOP ICS rom on it.
Just tried to update to update-cm-9-20120524-NIGHTLY-p4-signed.zip
Wiped Dalvik, wiped cache, factory reset.
Install Failure...
Installing update...
assert failed: getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4"
E:Error in /sdcard/1-CM9/update-cm-9-20120524-NIGHTLY-p4-signed.zip
(Status 7) Installation aborted.
Can someone please advise as to the why this fault is being generated?
Thanks in advance!
mpierce said:
AOKP_p4_milestone-4.zip
---------- Post added at 02:19 AM ---------- Previous post was at 02:07 AM ----------
Using a P7500 with AKOP ICS rom on it.
Just tried to update to update-cm-9-20120524-NIGHTLY-p4-signed.zip
Wiped Dalvik, wiped cache, factory reset.
Install Failure...
Installing update...
assert failed: getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4"
E:Error in /sdcard/1-CM9/update-cm-9-20120524-NIGHTLY-p4-signed.zip
(Status 7) Installation aborted.
Can someone please advise as to the why this fault is being generated?
Thanks in advance!
Click to expand...
Click to collapse
I have no AOKP ROM to check at the moment, but my guess is that in the AOKP ROM the "ro.product.device" and "ro.build.product" in the build.props are not set to "p4".
Simple solution is to remove the assert command from the updater-script. That would help you to get CM9 on your tablet.
Once you have the CM9 on your tablet, the two values will be "p4" and you will be able to flash any CM9 nightlies updates without problems.
[EDIT]
Just checked on a stock GT-P7500 ROM, there the values are set to
ro.product.device=GT-P7500
ro.build.product=GT-P7500
So there could be the same problem.
I saw as well in another thread (sorry, don't remember where) that there is a CWM recovery that allows you to flash even if the assert getprop command fails.
[/EDIT]
[EDIT 2]
In latest AOKP ROM the values are:
ro.product.device=p4
ro.build.product=p4
So that means my first assumption is wrong. Still my proposal to remove the assert getprop from the updater-script will work. Or you update to latest CWM recovery.
[/EDIT]
mpierce said:
AOKP_p4_milestone-4.zip
---------- Post added at 02:19 AM ---------- Previous post was at 02:07 AM ----------
Using a P7500 with AKOP ICS rom on it.
Just tried to update to update-cm-9-20120524-NIGHTLY-p4-signed.zip
Wiped Dalvik, wiped cache, factory reset.
Install Failure...
Installing update...
assert failed: getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4"
E:Error in /sdcard/1-CM9/update-cm-9-20120524-NIGHTLY-p4-signed.zip
(Status 7) Installation aborted.
Can someone please advise as to the why this fault is being generated?
Thanks in advance!
Click to expand...
Click to collapse
You need to get to latest clockwork recovery.
Sent from my GT-P7510 using XDA
Seagullbeagle said:
You need to get to latest clockwork recovery.
Sent from my GT-P7510 using XDA
Click to expand...
Click to collapse
Yes. I was unable to flash the nightly rom until I install this CWM (http://droidbasement.com/galaxy/recovery/cwm5/p4/2/recovery.tar.md5)
Strange, my CWM said it was v5.5.0.4 and was installed from this file, ClockworkMod_Recovery_v5.5.0.4_P75xx.tar using Odin v1.85
Followed the instructions you guys have given and installed the file, recovery.tar.md5 using Odin v1.85 and voila... she now works!
Thanks fellows!
---------- Post added at 05:31 AM ---------- Previous post was at 04:44 AM ----------
Couple of questions, it appears that network time is not working and that I have to set this manually. Is that correct or just me?
Can lockscreen shortcuts be enabled?
Do these nightlies have 3G working?
I just installed it and after setting up the APN, 3G is working on mine.
APN were set automatically on my device.
vibecatalin said:
APN were set automatically on my device.
Click to expand...
Click to collapse
Probably would be the case with everyone.
The reason that I have to set mine is that we are doing software development and we have to use a special sim.
mpierce said:
Probably would be the case with everyone.
The reason that I have to set mine is that we are doing software development and we have to use a special sim.
Click to expand...
Click to collapse
Also not working with my Softbank Japan SIM. I had to change the apns-conf.xml with my personal one to get the Softbank APN working.
The Softbank APN settings in the CM9 version do not cover my Softbank SIM card.
I will submit a patch following the instructions in post 1 in the next days.
You have to use the (Clockworkmod 5.4) that's why you getting this error it happens to me and I find out that if you use the lastest clockworkmod it won't work okay thank you luck
Sent from my SGH-T859 using xda premium
my question is simple:
why to go for CyanugenMod 9 Nightlies (P7500 3g) if I am already rooted with my stock ROM? in other way: which plus am I getting if I go to CM9 for my tab?
I've switched because on ICS is Tab much more smoother.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
INSTRUCTIONS
First time installing CyanogenMod 11.0 to your Galaxy Note 8 N5110, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM11.0 ZIPs to your SDCard
- Boot into Recovery
- Flash CM11.0 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 11.0:
- Copy CM11.0 ZIP to your SDCard
- Boot into Recovery
- Flash CM11.0 zip from SDCard
- Reboot
BUG LIST
-BT Voice Search
[Nightlies] http://download.cyanogenmod.org/?device=n5110
[GAPPS 4.4] http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
[CWM 6.0.4.4 w/ swipe] Heimdall: http://www.androidfilehost.com/?fid=23212708291675367
OUTDATED:
[11/11] ROM: http://www.androidfilehost.com/?fid=23212708291676598
CHANGES:
-Initial Release
[12/2] ROM: http://www.androidfilehost.com/?fid=23252070760972532
Changes:
- Upstream CM merges (yes home button recent apps is back)
- fixed internal sd / storage
[12/10] ROM: http://www.androidfilehost.com/?fid=23252070760974755
Changes:
- Upstream CM changes (includes fix for rotation distostortion)
Source: http://github.com/CyanogenMod
Yes this is an updated build from the one I posted in the 10.2 thread
A quick pointer to the PA Gapps thread:
http://forum.xda-developers.com/showthread.php?t=2397942
There's a lighter version of the Gapps package there if you don't use so many of the Google services, and it should always have links to up to date versions.
Don't forget to format your system partition and re-flash the whole ROM if you are changing between GApps versions, or you may have some leftovers from the previous version.
Wrong Thread......
testing the 11-11 built. Seems like there is a problem accessing files on the /storage/emulated/legacy (or 0).
Can't delete anything. Can't modify anything... but you can browse... Read Only almost like?
Thanks for quick work !
Code:
set_metadata_recurcive : some changes failed (status 7)
Even with a cwm 6.0.4
I'll update to the build from nov 11th in the next hours and going to give a feedback later too.
@sbrissen: maybe it does make sense to add my cwm6044.tar.md5 to the first post?! Or at least your img-file.
Edit: what's the difference between pa_gapps-full-4.4-20131111-signed.zip and gapps-kk-20131031.zip?
kingofcomedy said:
I'll update to the build from nov 11th in the next hours and going to give a feedback later too.
@sbrissen: maybe it does make sense to add my cwm6044.tar.md5 to the first post?! Or at least your img-file.
Click to expand...
Click to collapse
If you have a recovery that work with this build, could you share it here ?
thanks
kingofcomedy said:
I'll update to the build from nov 11th in the next hours and going to give a feedback later too.
@sbrissen: maybe it does make sense to add my cwm6044.tar.md5 to the first post?! Or at least your img-file.
Edit: what's the difference between pa_gapps-full-4.4-20131111-signed.zip and gapps-kk-20131031.zip?
Click to expand...
Click to collapse
Posted my heimdall in the OP, can you just shoot up a link to your odin copy?
The difference that I've noticed in the 2 are the PA gapps have the "OK google" feature. Maybe they both do but I noticed it after flashing the PA gapps
That's what I just did:
- boot into recovery (rename the attached file to recovery.tar.md5 and flash it with odin) (or download it from here: https://mega.co.nz/#!J18HxR7C!WJMuYhLvpYCPlN-giWs2u0Sr4wRzgBvajTNOP_L5gyU)
- "format /system"
- "format /cache"
- flash cm_n5110-ota-sbrissen_11-11.zip
- flash pa_gapps-full-4.4-20131111-signed.zip
Issues:
- back- and menu-button are not working (sometimes I can close popup-messages with the back-button)
- /storage/emulated/0 not writeable (as already stated by mbze430)
- gallery is not working
- no screenshots
- screen goes a bit crazy during rotations
Edit: I tried to install Root Explorer via the Play Store, but no keyboard showed up. Voice search did work. After I have started Root Explorer and set / to be rw the back- and menu-buttons are working and the keyboard showed up too.
PA GAPP definitely good for ART.. However one of the most important tool "TiBu" doesn't work with ART. That is like the biggest "WTF". lmfao. Seems like ConfigUpdate has been taken out from this new release.
Do we REALLY need torch.apk ? lol
Will the CM team ever accept this as an official? Would love to see nightlys
EDIT1: Almost ****ted in my pants... ExtSdCard is reading empty on the device... but I checked it with a PC... everything is there... so ExtSdCard isn't being read correctly? Also seems like Android 4.4 is dumping all kinds of txt files in the ExtSdCard. It is being recognized as "/mnt/media_rw/sdcard1" in Solid Explorer??
EDIT2: Definitely something is wrong with the partition permissions... Viper4Android no longer can write to the /system partition with 11-11 built.
PdroidAndroid said:
Thanks for quick work !
Code:
set_metadata_recurcive : some changes failed (status 7)
Even with a cwm 6.0.4
Click to expand...
Click to collapse
Hey
I got this same error, what I did was that I flashed the TWRP aroma touch recovery from the XDA thread for GT-N5110 and it worked like a charm!
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2483844
mbze430 said:
PA GAPP definitely good for ART.. However one of the most important tool "TiBu" doesn't work with ART. That is like the biggest "WTF". lmfao. Seems like ConfigUpdate has been taken out from this new release.
Do we REALLY need torch.apk ? lol
Will the CM team ever accept this as an official? Would love to see nightlys
EDIT1: Almost ****ted in my pants... ExtSdCard is reading empty on the device... but I checked it with a PC... everything is there... so ExtSdCard isn't being read correctly? Also seems like Android 4.4 is dumping all kinds of txt files in the ExtSdCard. It is being recognized as "/mnt/media_rw/sdcard1" in Solid Explorer??
EDIT2: Definitely something is wrong with the partition permissions... Viper4Android no longer can write to the /system partition with 11-11 built.
Click to expand...
Click to collapse
Checking the extSdCard issue now. CM just forked my repos last night, I'll start the process to get 10.2 nightlies going. They have not start 11.0 nightlies for any devices yet.
I can also confirm the sdcard not being writable. I'm thinking between that and the extSdCard strangeness perhaps the storage just gets mounted weirdly upon boot.
In addition, it seems to me that long pressing the home button no longer brings up the recent apps drawer.
This version installed without a hitch and aside from the SD card issue, works great!
Also, not that important but Im just curious- why can't I get the launcher looking like kitkat? It still retains jelly bean look even after third party launchers and what not.
Thanks and when the funds allow I'd be glad to donate!
Hi guys! First of all thanks a lot sbrissen for your work!!!! I've been waiting for CM working on my Note8 since I bought it.
Two questions I have:
- When it will be available to download from CM official site.
- Does all the s-pen features work with this build? (by features I mean the quick access, aerial preview, etc)
Thanks again!
titotito1983 said:
Hi guys! First of all thanks a lot sbrissen for your work!!!! I've been waiting for CM working on my Note8 since I bought it.
- Does all the s-pen features work with this build? (by features I mean the quick access, aerial preview, etc)
Thanks again!
Click to expand...
Click to collapse
Simple answer is no. From the way things look, it will never. You will need 3rd party apps to get some of those features back
Keep getting a status 7 error, any help?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Jaimemex said:
Keep getting a status 7 error, any help?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try the TWRP Aroma Touch recovery, it works like a charm and no error occured to me
Sent from my GT-N5110 using XDA Premium 4 mobile app
kinda quiet in here... did everyone jump back to 10.2?? lol
Unofficial crespo build of Omni-ROM using CM11 kernel. Flash at your own risk. Use latest CWM to flash. Don't know if it works with TWRP.
For additional information see post 2
Changelog 22.08.2014
- latest Omni sources (as of 21.08.2014)
- This is a 'blind' build. I couldn't test it out. So DO A BACKUP before flashing this build.
Changelog 23.07.2014
- latest Omni sources (as of 22.07.2014)
- adapted and added 'OmniTorch' to work on crespo
Changelog 25.06.2014
- latest Omni sources (as of 24.06.2014)
- Android 4.4.4
- ZRAM defaults to 96 MB
Changelog 13.06.2014
- latest Omni sources (as of 13.06.2014)
- Android 4.4.3
- removed all custom properties (original Omni code)
Notes on this release:
Due to the fact that Android has iterated to Version 4.4.3, i recommend to do a fresh installation. Use Gapps from here: http://forum.xda-developers.com/showthread.php?t=2397942 I personally used 'MICRO MODULAR PACKAGE' 4.4.3.
Changelog 30.04.2014
- latest Omni sources (as of 30.04.2014)
Changelog 31.03.2014
- latest Omni sources (as of 31.03.2014)
Changelog 17.03.2014
- latest Omni sources (as of 17.03.2014)
Changelog 28.02.2014
- latest Omni sources (as of 28.02.2014)
- new Bootanimation should work now
- This is a 'blind' build. I couldn't test it out. So DO A BACKUP before flashing this build.
Changelog 21.02.2014
- latest Omni sources (as of 21.02.2014)
- temporarily changed to old bootanimation
- once again back to self compiled kernel
- removed property 'ro.config.max_cached_apps'
Changelog 05.02.2014
- latest Omni sources (as of 05.02.2014)
- fixed camera
- fixed zram handling
Changelog 03.02.2014
- latest Omni sources (as of 03.02.2014)
- system and kernel seperated again
- fixed ART runtime
Changelog 24.01.2014
- latest Omni sources (as of 24.01.2014)
- system and kernel build from sources again.
Changelog 10.01.2014
- latest Omni sources
- seperated system and kernel building. Using latest CM11 kernel as 'default' now
- cache is back again on /cache
- internal apps2sd fixed
- fixed graphical glitches and 'sudden reboots'
- removed property 'ro.config.force_highgfx' (see 'High Mem settings' in post 2)
- added properties 'ro.config.max_recent_tasks' and 'ro.config.max_starting_bg' (see 'High Mem settings' in post 2)
- changed default wallpaper
Changelog 27.12.2013
- fixed kernel flashing error
- latest Omni sources
- fixed SIM-pin and security keypad layout
- enabled KSM like described here: http://source.android.com/devices/low-ram.html#ksm
- enabled memory cgroups in kernel for zram like described here: http://source.android.com/devices/low-ram.html#zram
- added possibility to enable zram (see post 2 for instructions)
- temporary linked /cache to /data/cache (due to kernel problems not mounting cache partition)
- reset build.prop props so that phone behaves as a 'low memory' device
Known issues:
- Performance/VM-Settings are reset to default values after reboot.
Standard Installation:
- Download ROM and GAPPS
- Boot into recovery
- Do a backup
- if not already done, do a backup..
- Wipe Data/Factory Reset
- Mounts and Storage -> format /system
- Flash ROM
- Flash GAPPS
- Reboot
ART runtime Installation:
- Download ROM and GAPPS
- Boot into recovery
- Do a backup
- if not already done, do a backup..
- Wipe Data/Factory Reset
- Mounts and Storage -> format /system
- Flash ROM
- Reboot and 'Setup'
- Enable developer settings in the usual way by quickly tapping on 'Build Number' several times in 'About Phone'.
- Enable ART in developer settings and let it reboot.
- Wait... It will take some time. After round about 5 minutes Omni logo should dissappear and you should see 'Optimizing ...'
- After ROM has booted, reboot to recovery
- Flash GAPPS
- Reboot
For root, flash SuperSu, which can be found here at XDA.
build 7 DOWNLOAD: HERE
build 8 DOWNLOAD: HERE
build 9 DOWNLOAD: HERE
build 10 DOWNLOAD: HERE
build 11 DOWNLOAD: HERE
build 12 DOWNLOAD: HERE
build 13 DOWNLOAD: HERE
build 14 DOWNLOAD: HERE
build 15 (final) DOWNLOAD: HERE
For GAPPS package for 4.4.2 builds search XDA or use this minimal GAPPS (from Mokee ROM): http://www.androidfilehost.com/?fid=23329332407566631
For 4.4.3 builds use a package from here: http://forum.xda-developers.com/showthread.php?t=2397942
For 4.4.4 builds use Gapps from here: http://forum.xda-developers.com/showthread.php?t=2397942 I personally used 'MICRO MODULAR PACKAGE' 4.4.3.
And now for some rules:
- I won't implement special wishes. So don't ask for it. I will simply ignore such requests.
- I'll try to update every 2 weeks, except there are significant changes or fixes from Omni team. But read again: 'i'll TRY..'.
- And please don't flood my PM box. If you have problems installing/running, search XDA first...
A big and warm 'Thank you' and Credits go to 'DerTeufel1980' for creating his kernel and allowing me to use it.
Enjoy, lagloose
Additional installation instructions
Naturally a clean install is always the best thing to do, but a 'dirty' flash shoud be ok, as long as you didn't install scripts or anything else which reside on /system partition. However, flashing a new release overwrites Gapps. So what you can try is:
!!! In every case make sure you are on 'dalvik' runtime before trying a dirty flash !!!
Without wiping anything:
- flash new release
- flash Gapps
- flash 'SuperSu'
- reboot
ROM should boot now and show you the usual 'updating' and 'optimizing' app's (blah.. blah...) dialog. Afterwards try if everything is like 'before'. Of course i'll can't guarantee
ZRAM
To enable zram i've integrated an 'init.d' script which looks for special properties in build.prop and enables or disables zram depending on the values of this properties. These properties are 'sys.zram.size' (in Mb) and 'sys.zram.swappiness'. If 'sys.zram.size' ist set to '0', zram will be disabled. For those who want to enable it, i'd recommend to reserve 64Mb of memory for zram. So set 'sys.zram.size=64' in build.prop. I'd recommend ro leave swappiness at 20 because this seems to be a good 'balanced' value, but if you want to try around with swappiness, feel free.
People who are not familiar with 'adb' and setting properties can download 'build.prop editor' here: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor from playstore. BUT DON'T CHANGE ANY OTHER VALUE THAN MENTIONED ABOVE, UNLESS YOU KNOW WHAT YOU ARE DOING !!! To check if and 'how' zram works you can use this one from playstore: https://play.google.com/store/apps/details?id=id.co.ptskp.android.zs (Note: there seems to be a bug in that app which fc's and gives you back a large negative number. Just wait some time and start the app again. It should work than.)
High Mem settings
Due to too much problems with using 'ro.config.force_highgfx=true' in conjunction with low_mem device setting i decided to remove this property. Instead i've added and used three other properties to get our Nexus S running in 'high mem' mode without loosing too much performance. To change to high mem mode i recommend to set/change the follwing properties in system/build.prop:
ro.config.low_ram=false
ro.config.max_recent_tasks=10
ro.config.max_starting_bg=2
This can be done by using 'adb' or 'build.prop editor' from Playstore. See notes on 'build.prop editor' in ZRAM section of this post. Additionally you should consider downloading and flashing 'Devil Kernel' from here: http://forum.xda-developers.com/attachment.php?attachmentid=2314244&d=1381362960
For people who know about OOM settings, I suggest to set OOM values to 2048,3584,14080,17920,21760,25600. I won't do bigger explanations here on what all this does. Those of you, who are able to read source code are free to inspect Android source to find out...
Anyway, I'd be glad if someone does a post in this thread what OOM settings are and how they can be set.
Battery life
to increase battery life, you don't have to turn off Location services completely. However, i strongly recommend to turn off Location reporting and Location history in 'Google location settings'. Also turn off 'Scanning always available' in Advanced Wi-Fi settings.
Nice to see new kitkat rom's on our old crespo
Mmmm.. That new ROM smell..
Sent from my Nexus S using XDA Premium 4 mobile app
This is the Rom that I'm waiting for try ...
Thx
There is problem with root
kkkhattak said:
There is problem with root
Click to expand...
Click to collapse
Maybe you haven´t flashed supersu after installing the ROM...??
Root works very fine here...:good:
greet´s
lagloose said:
For root, flash SuperSu, which can be found here at XDA.
Click to expand...
Click to collapse
kkkhattak said:
There is problem with root
Click to expand...
Click to collapse
Maybe flash SuperSu??...
Which gapps did you guys use ?
Sooo Setting.Out, how is Omni petrforming compared to CM11?
k-kuchen said:
Sooo Setting.Out, how is Omni petrforming compared to CM11?
Click to expand...
Click to collapse
I'll have an update soon... Check my thread..
Sent from my Nexus S using XDA Premium 4 mobile app
This is possible the best kitkat ROM unofficial?
Enviado do meu Nexus S using Tapatalk 4 @ JellyShot
Okay, I need to know what I am doing wrong.. I have downloaded this rom 4 times with both my computer and phone.. I have tried CWM 6.0.4.3, Philz 6.01.0 (cwm6.0.4.5), TWRP 2.6.3... I did full wipes each time, no error messages on flashing with CWM's, failed message on TWRP.. and when I try to boot, I am knocked to boot loader every time.. I just reflashed EuroSkank CM11 with no issues.. So, what didn't I do?..
( for anyone new, I have flashed a few thousand times and know how to do it..)
Setting.Out said:
Okay, I need to know what I am doing wrong.. I have downloaded this rom 4 times with both my computer and phone.. I have tried CWM 6.0.4.3, Philz 6.01.0 (cwm6.0.4.5), TWRP 2.6.3... I did full wipes each time, no error messages on flashing with CWM's, failed message on TWRP.. and when I try to boot, I am knocked to boot loader every time.. I just reflashed EuroSkank CM11 with no issues.. So, what didn't I do?..
( for anyone new, I have flashed a few thousand times and know how to do it..)
Click to expand...
Click to collapse
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-crespo.img
Flash the latest touch recovery in fastboot prior to flashing. It should flash after that.
Edit: Whether or not it boots is a another story. Mine's been sitting on the boot screen for 10 minutes.
Could I get a mirror please from someone who got it to boot??
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
Okay, I need to know what I am doing wrong.. I have downloaded this rom 4 times with both my computer and phone.. I have tried CWM 6.0.4.3, Philz 6.01.0 (cwm6.0.4.5), TWRP 2.6.3... I did full wipes each time, no error messages on flashing with CWM's, failed message on TWRP.. and when I try to boot, I am knocked to boot loader every time.. I just reflashed EuroSkank CM11 with no issues.. So, what didn't I do?..
( for anyone new, I have flashed a few thousand times and know how to do it..)
Click to expand...
Click to collapse
Same with me,
Always back to bootloader
Has anyone got this to boot yet?
treesurf said:
Has anyone got this to boot yet?
Click to expand...
Click to collapse
Nope. It stayed at boot logo for over 30 mins before I turned it off.
Sent from my Nexus S using Tapatalk
I have booted it and its an awesome rom
kkkhattak said:
I have booted it and its an awesome rom
Click to expand...
Click to collapse
So how did you install it? dirty/clean? what recovery?.. and can you make a mirror for your zip file?.. I can't download a ?good? copy...
Kali Nethunter For Lollipop
I am not the developer of that system I am only compiled it but thanks to the original developers
(Offensive Security , Binky Bear, Render kernel Developers)
My last thread I had a buggy system (Camera & alot FCs)
but with this update I hope most of the bugs are fixed and MultiBoot is Working
Instructions
( 1 ) Try to have the CM12S (YNG1TAS2I3) rom, I dont tried on nightly updates (update me on that)
( 2 ) Download the Rootfs and the Kernel Zips
( 3 ) Go to recovery (TWRP Recommened) and flash first the Rootfs (Take 30 Min) then the Kernel. * Works with MultiRom if you dont want it on your Primary rom
( 4 ) Wipe Davlik & Chache then boot and wait about 3-5 minutes then you have working kali
DownloadsRootfs Kernel
Screenshots
SourcesKali Nthunter - https://github.com/offensive-security/kali-nethunter
Kernel, Patches and External Drivers- https://github.com/binkybear
Kernel - https://github.com/RenderBroken/msm8974_OPO_render_kernel
xda Thread - http://forum.xda-developers.com/oneplus-one/orig-development/kernel-render-kernel-t3051518
Great stuff, much appreciated!
is it same as the one version 1.21 in the offciail website?
or its compiled by u also
https://www.offensive-security.com/kali-linux-nethunter-download/
Its compiled from the latest sources with version 1.21
oh thats great!
i already have cm12s on my primary rom with miui6 and hydrogen os on secodnary
does this work only on cm12s rom and not on other lollipop roms?
if not in that case i have to flash cm12s again to secondary then flash the net hunter files right as i wish to flash it to secondary rom..wondering if its fully supported on multirom.
anyway thanks for this post
keep it updated
Multiboot working good the screenshots I took from secondary CM12s with nethunter
about other roms I dont belive it will work because its based on render kernel for cm12s
Shapi300 said:
Kali Nethunter For Lollipop
I am not the developer of that system I am only compiled it but thanks to the original developers
(Offensive Security , Binky Bear, Render kernel Developers)
My last thread I had a buggy system (Camera & alot FCs)
but with this update I hope most of the bugs are fixed and MultiBoot is Working
Instructions
( 1 ) Try to have the CM12S (YNG1TAS2I3) rom, I dont tried on nightly updates (update me on that)
( 2 ) Download the Rootfs and the Kernel Zips
( 3 ) Go to recovery (TWRP Recommened) and flash first the Rootfs (Take 30 Min) then the Kernel. * Works with MultiRom if you dont want it on your Primary rom
( 4 ) Wipe Davlik & Chache then boot and wait about 3-5 minutes then you have working kali
DownloadsRootfs Kernel
Screenshots
SourcesKali Nthunter - https://github.com/offensive-security/kali-nethunter
Kernel, Patches and External Drivers- https://github.com/binkybear
Kernel - https://github.com/RenderBroken/msm8974_OPO_render_kernel
xda Thread - http://forum.xda-developers.com/oneplus-one/orig-development/kernel-render-kernel-t3051518
Click to expand...
Click to collapse
Does camera works with 4k video and slow mo
Shapi300 said:
Multiboot working good the screenshots I took from secondary CM12s with nethunter
about other roms I dont belive it will work because its based on render kernel for cm12s
Click to expand...
Click to collapse
Thanks for your work!
Tried it with katinatez CM12.1 temasek build and it didn't boot, propably because of the kernel, was just stuck in a bootloop, tried 2 times and waitet about 20 min each time. I also reflashed it each time and used multirom, i also made sure that cm12.1 succesfully booted before flashing nethunter.
Could/would you make a compatible build?
serialhacker said:
Does camera works with 4k video and slow mo
Click to expand...
Click to collapse
Honestly, if you know what Nethunter is used for, you wouldn't be interested in the camera... Well, maybe script kiddies would...
Anyway, camera works fine.
Even I bootlooped.
Tried on OwnRom. I'll try with CM12 later.
Does this rom work in multiboot with Exodus Rom as primary?
Got the ROM up and running, with multiRom. I was just wanting to know what external wifi card you use. I using a TL-WN821N and the light it on but it just loops the selection process in Wifite.
arunjitoberoi said:
Even I bootlooped.
Tried on OwnRom. I'll try with CM12 later.
Click to expand...
Click to collapse
Follow the instructions! It's for CM12S, not OwnRom and/or CM12.
Midzuel said:
Does this rom work in multiboot with Exodus Rom as primary?
Click to expand...
Click to collapse
Yes.
dbaler said:
Got the ROM up and running, with multiRom. I was just wanting to know what external wifi card you use. I using a TL-WN821N and the light it on but it just loops the selection process in Wifite.
Click to expand...
Click to collapse
I'm using TPLINK TL-WN722N. Works great.
Gamm86 said:
Honestly, if you know what Nethunter is used for, you wouldn't be interested in the camera... Well, maybe script kiddies would...
Anyway, camera works fine.
Click to expand...
Click to collapse
i know wat net hunter is used for, If i needed it solely for that purpose, i would have choose other alternative's.
Anyway i would like to utilize the camera, and don't want multi roms's
Just installed and it's working perfectly, however having difficulty rooting it at this point.
E:error opening /data/local/nhsystem/kali-armhf/dev/ram12
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram14
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram16
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram10
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram13
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram15
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/loop6
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram4
. this shown during all procedures in twrp , how to clear it ?
I i found my answer, what i did was
I delete nhsystem folder in roor data/local/nhsystem
Everything was fine.
Unable to download Rootfs and kernel files mentioned above
Download links
Can anybody help me.... post download links for Rootfs and kernel files mentioned in this site...
Thanks in advance...
Surya786 said:
Can anybody help me.... post download links for Rootfs and kernel files mentioned in this site...
Thanks in advance...
Click to expand...
Click to collapse
Does anybody even still have this version anyway?lost mine in HD failed, lol ate a lot of files.
Yet another TWRP for MI9
TWRP compiled from the latest omnirom 9.0 branch with decryption and opengapps support!
* During the testing "treble compatibility check" was disabled for supporting flashing the MIUI Global ROM, GSI's were also tested along with opengapps (you still need to manually flash vbmeta and resize the system partition).
Please give me your feedback, as I can't test all the things out there!
As always: Use on your own risk, nothing here is guaranteed to work!
Works:
- ADB
- Decryption of /data (TESTED ONLY WITH PATTERN)
- Screen brightness settings
- Correct screenshot color
- MTP
- Flashing (opengapps, roms, images, magisk and so on)
- Backup/Restore (Needs more testing)
- USB-OTG
...
TO-DO:
- Vibration support
Changelog:
v1:
* Initial release
v2:
* TWRP will now auto resize the system partition when it detects you're trying to flash opengapps
* Assert error issue flashing some roms (ie - error 7 : This package is for "cepheus" devices, this is a "") should be fixed now (NOT TESTED - so please let me know)
v3:
* Assert error issue flashing some roms (ie RevolutionOS - error 7 : This package is for "cepheus" devices, this is a "") should be fixed now
v4:
* Fixed USB-OTG
v5 (Third try, but this time I'm 100% sure it works as I flashed it):
* Assert error issue flashing some roms (ie RevolutionOS - error 7 : This package is for "cepheus" devices, this is a "") should be fixed now
v6:
* TWRP should now detect any gapps package and auto resize the system partition (opengapps, mindthegapps and so on...)
v7:
* Back to busybox for better compatibility with some old zips
v8:
* Updated to latest omni-twrp source code
* Android Q decryption support
* DTBO Image flashing support added
* PERSIST Image flashing support added
* F2FS support (not tested)
* PITCH BLACK theme included (created by me, inspired by a theme of a friend from the op5 days)
Download:
https://www.androidfilehost.com/?w=files&flid=294801
Source code:
https://github.com/siankatabg/android_device_xiaomi_cepheus-twrp
Credits:
The hard work did - @mauronofrio and @PeterCxy , so thanks to them
Just in case
Thanks! Will try it.
Edit: decryption is working great! (Pattern)
ROS 9.5.29
siankatabg said:
Yet another TWRP for MI9
TWRP compiled from the latest omnirom 9.0 branch with decryption and opengapps support!
* During the testing "treble compatibility check" was disabled for supporting flashing the MIUI Global ROM, GSI's were also tested along with opengapps (you still need to manually flash vbmeta and resize the system partition).
Please give me your feedback, as I can't test all the things out there!
As always: Use on your own risk, nothing here is guaranteed to work!
Works:
- ADB
- Decryption of /data (TESTED ONLY WITH PATTERN)
- Screen brightness settings
- Correct screenshot color
- MTP
- Flashing (opengapps, roms, images, magisk and so on)
- Backup/Restore (Needs more testing)
...
TO-DO:
- Vibration support
- USB OTG (? can't test it)
Download:
https://www.androidfilehost.com/?w=files&flid=294801
Source code:
Will be available tomorrow (My internet is too poor to upload it right now, sorry (for the mods: miui prebuilt kernel was used))
Credits:
The hard work did - @mauronofrio and @PeterCxy , so thanks to them
Click to expand...
Click to collapse
Thanks for the mention and credit, i'm waiting the device tree to check what was bad in the mine one, i think i was really near to a fully working twrp
happy new TWRP! No OTG, no encryption (password on GSI). Mindthegapps installed fine after resize.
One more talent coming to MI 9, thanks very much for this, will try as soon as I can, cheers
Sian here wow! Thanks.
Thank you! good:
I dont know why but mine still get encrypted using global dev 9.5.16 as base aosip gsi
mauronofrio said:
Thanks for the mention and credit, i'm waiting the device tree to check what was bad in the mine one, i think i was really near to a fully working twrp
Click to expand...
Click to collapse
Hey.
Of course I'll mention you, you did the hard work and afaik your work was the only public available one, so thank you!
I see you already found (unpacked my image?) the small things needed and made it work on your end, but yeah, you was really near
However, the source code is up and I'm sorry for the delay!
Have fun guys
siankatabg said:
Hey.
Of course I'll mention you, you did the hard work and afaik your work was the only public available one, so thank you!
I see you already found (unpacked my image?) the small things needed and made it work on your end, but yeah, you was really near
However, the source code is up and I'm sorry for the delay!
Have fun guys
Click to expand...
Click to collapse
I already have some things unmerged on my pc, but what did the tricks is the vendor.gatekeeper.disable-spu that it's something new on this sm8150. I already saw in in the stock kernel and when you pubblished the twrp i checked it was here already, so adding it all works. I will add you and peter to credits, when i will be from a pc. Thanks for the source in all cases
Getting error 7 : This package is for "cepheus" devices, this is a "" while flashing latest RevOS
New build is up!
Changelog:
* TWRP will now auto resize the system partition when it detects you're trying to flash opengapps
* Assert error issue flashing some roms (ie - error 7 : This package is for "cepheus" devices, this is a "") should be fixed now (NOT TESTED - so please let me know)
Have fun!
siankatabg said:
New build is up!
Changelog:
* TWRP will now auto resize the system partition when it detects you're trying to flash opengapps
* Assert error issue flashing some roms (ie - error 7 : This package is for "cepheus" devices, this is a "") should be fixed now (NOT TESTED - so please let me know)
Have fun!
Click to expand...
Click to collapse
Good work !
Unfortunately, the issue still occurs
Chrisgia said:
Good work !
Unfortunately, the issue still occurs
Click to expand...
Click to collapse
Thanks for the feedback, I'm looking into it :good:
Chrisgia said:
Good work !
Unfortunately, the issue still occurs
Click to expand...
Click to collapse
Can you try this one:
https://androidfilehost.com/?fid=6006931924117884668
siankatabg said:
Can you try this one:
https://androidfilehost.com/?fid=6006931924117884668
Click to expand...
Click to collapse
Nope still not working.
Kollachi said:
Nope still not working.
Click to expand...
Click to collapse
Can you please send me the updater-script from this rom, something is wrong there as the assertion works fine on any other rom and my internet is too slow to download it right now?
Thanks.
siankatabg said:
Can you please send me the updater-script from this rom, something is wrong there as the assertion works fine on any other rom and my internet is too slow to download it right now?
Thanks.
Click to expand...
Click to collapse
Sure.
btw this i could log with mauronofrios twrp when flashing ros. should be same issue you have.
New build is up!
Changelog:
* Assert error issue flashing some roms (ie RevolutionOS - error 7 : This package is for "cepheus" devices, this is a "") should be fixed now
It should work this time!
Have fun!