Hi guys,
I want to present you freshly cooked fork of The Pure Nexus Project ROM compiled with UBERTC 4.9.4 and flags from JustArchi's commit.
Features:
Built on Ubuntu 14.10
Switched host toolchain to 4.8
Switched ROM & kernel toolchain to UBERTC 4.9.4
JustArchi's Optimizations included
For all ROM features go to orginal thread
Click!
Download:
removed
Changelog:
26082015
New switches in settings
25082015
25082015 r2
Updated WebView
25082015
Initial Release
Highly recommended kernel:
Blu_Spark built with UBERTC 4.9.4 and few more optimization flags
Click!
Credits:
JustArchi for Optimization commit
BeansTown106 for Pure Nexus
Cl3Kener for UBERTC
me for free time
If you want to support student and his work:
Dirty flash when we come from original?
abalam said:
Dirty flash when we come from original?
Click to expand...
Click to collapse
I don't recommend this, for best result go for clean install.
mastero9017 said:
I don't recommend this, for best result go for clean install.
Click to expand...
Click to collapse
Yeah thought so, the golden rule. Tnx for building!! Report later.
screenshot please
support RRO or CM?
michelemascia7 said:
screenshot please
Click to expand...
Click to collapse
Added in OP. For more go to orginal thread
http://forum.xda-developers.com/google-nexus-5/development/rom-pure-nexus-project-layers-t3158484
holigan360 said:
support RRO or CM?
Click to expand...
Click to collapse
For all features go to this thread
http://forum.xda-developers.com/google-nexus-5/development/rom-pure-nexus-project-layers-t3158484
mastero9017 said:
Added in OP. For more go to orginal thread
http://forum.xda-developers.com/google-nexus-5/development/rom-pure-nexus-project-layers-t3158484
For all features go to this thread
http://forum.xda-developers.com/google-nexus-5/development/rom-pure-nexus-project-layers-t3158484
Click to expand...
Click to collapse
sorry I don't realize that it was based on this rom ! Fantastic , thanks!
Nice! The original Pure Nexus cured my flash addiction because it's such a great ROM - now the addiction is back.
Will definitely try this one. Thanks for building this!
Has this been updated with the latest inclusions? or is it based on the 17/08 release? Thanks
What are the benefits of building with Uber toolchain?
I'm also curious if the latest layers commits were included here or not.
hi,
I was on MinimalOS, dnlded zip from OP.
Booted in TWRP latest
Factory Reset, Wipe cache, Dalvik
loaded Rom ZIp
flashed
on log it was written - chking MD5 - no MD5 found (I have tried 3 times and all the time I see - Checking for MD5 no MD5 found)
and thereafter, it jz dosent finish.
I waited for 15 min and then rebooted ph into bootloader and then again to TWRP. But this time with red text E: Unable to mount System.
I am not able flash any rom neither able to boot.
can any one help me?
I have solved this by below method.
EDIT: Go to wipe select partition one by 1
Select System - Click Change or Repair partition
Select Data - Click Change or Repair partition (Will Wipe all of ur N5 SD Card)
Select any Rom Zip (just rom zip, flash gapps after 1st successful boot). Your N5 partitions are ready.
any link of gapps?
sandy7874 said:
hi,
I was on MinimalOS, dnlded zip from OP.
Booted in TWRP latest
Factory Reset, Wipe cache, Dalvik
loaded Rom ZIp
flashed
on log it was written - chking MD5 - no MD5 found (I have tried 3 times and all the time I see - Checking for MD5 no MD5 found)
and thereafter, it jz dosent finish.
I waited for 15 min and then rebooted ph into bootloader and then again to TWRP. But this time with red text E: Unable to mount System.
I am not able flash any rom neither able to boot.
can any one help me?
I have solved this by below method.
EDIT: Go to wipe select partition one by 1
Select System - Click Change or Repair partition
Select Data - Click Change or Repair partition (Will Wipe all of ur N5 SD Card)
Select any Rom Zip (just rom zip, flash gapps after 1st successful boot). Your N5 partitions are ready.
Click to expand...
Click to collapse
The same happend here.
But I rebooted into TWRP, did a factory reset, wiped manually cache, dalvik cache, system and data....unmounted system...and restored my nandroid.
No losses of data from sd card
I hope that it will be fixed soon
Konsumhaus said:
The same happend here.
But I rebooted into TWRP, did a factory reset, wiped manually cache, dalvik cache, system and data....unmounted system...and restored my nandroid.
No losses of data from sd card
I hope that it will be fixed soon
Click to expand...
Click to collapse
Even I did no loose anything as I did not wiped Data. I was about to do that but thought of giving a shot at Repairing through TWRP.
Just pushed new build of Pure Nexus. Today i included first specific feature to this ROM which are switches for wifi, bluetooth and data in settings.
Enjoy!
Shiesh1 said:
Has this been updated with the latest inclusions? or is it based on the 17/08 release? Thanks
Click to expand...
Click to collapse
Latest sources up to 25 August.
FooBazza said:
What are the benefits of building with Uber toolchain?
Click to expand...
Click to collapse
Commit i used to build this ROM which is main boost
http://forum.xda-developers.com/showthread.php?t=2754997
RoyJ said:
I'm also curious if the latest layers commits were included here or not.
Click to expand...
Click to collapse
All is up to date with Pure Nexus.
sandy7874 said:
hi,
I was on MinimalOS, dnlded zip from OP.
Booted in TWRP latest
Factory Reset, Wipe cache, Dalvik
loaded Rom ZIp
flashed
on log it was written - chking MD5 - no MD5 found (I have tried 3 times and all the time I see - Checking for MD5 no MD5 found)
and thereafter, it jz dosent finish.
I waited for 15 min and then rebooted ph into bootloader and then again to TWRP. But this time with red text E: Unable to mount System.
I am not able flash any rom neither able to boot.
can any one help me?
I have solved this by below method.
EDIT: Go to wipe select partition one by 1
Select System - Click Change or Repair partition
Select Data - Click Change or Repair partition (Will Wipe all of ur N5 SD Card)
Select any Rom Zip (just rom zip, flash gapps after 1st successful boot). Your N5 partitions are ready.
Click to expand...
Click to collapse
I'm really sorry for this problem. but i think it's not connected with this specific ROM, rather random error.
wana7262 said:
any link of gapps?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24052804347782348
Has anyone tried xposed yet with this rom? I know on some roms built with uber it will bootloop, while with others, like chroma, it works
Sent from my Nexus 5
sandy7874 said:
hi,
I was on MinimalOS, dnlded zip from OP.
Booted in TWRP latest
Factory Reset, Wipe cache, Dalvik
loaded Rom ZIp
flashed
on log it was written - chking MD5 - no MD5 found (I have tried 3 times and all the time I see - Checking for MD5 no MD5 found)
and thereafter, it jz dosent finish.
I waited for 15 min and then rebooted ph into bootloader and then again to TWRP. But this time with red text E: Unable to mount System.
I am not able flash any rom neither able to boot.
can any one help me?
I have solved this by below method.
EDIT: Go to wipe select partition one by 1
Select System - Click Change or Repair partition
Select Data - Click Change or Repair partition (Will Wipe all of ur N5 SD Card)
Select any Rom Zip (just rom zip, flash gapps after 1st successful boot). Your N5 partitions are ready.
Click to expand...
Click to collapse
I had same problem, so maybe it is not a random error.
mastero9017 said:
Highly recommended kernel:
Blu_Spark built with UBERTC 4.9.4 and few more optimization flags
Click!
Click to expand...
Click to collapse
r16 is out now.
Edit: Just downloaded today's build but it doesn't seem to flash, just like the others reported. It's stuck at "Skipping MD5 check: no MD5 file found..." forever but then finally moves on after about 10 minutes.
Related
I777 Builds: http://dl.omnirom.org/i777/ [courtesy of @Entropy512*]
ChangeLog: https://changelog.omnirom.org/#/i777/next
ChangeLog: http://omni.cmxlog.com/4.4/i777/
Wiki: http://docs.omnirom.org/Main_Page
Gerrit: https://gerrit.omnirom.org/
Butracker: http://jira.omnirom.org
G+ community
Be Advised:
=================
- Root access is not included by default. Flash SuperSU for root (Step 4 below)(also see "SURVIVAL" note).
- Feel free to leave bug reports on the bugtracker.
- This firmware will install TWRP as your device recovery. (To use OpenDelta with CWM, disable [secure] in {system updates})
-o- internal sd-card files are located at "emmc"
-o- to get back to CWM, see notes below.
Recovery requirement (prior to flashing this firmware):
================
CWM 6.0.4.4+
--OR--
TWRP 2.6.3.0+
-Renderbroken's OmniROM kernel
-or- Flash Omni's Boot.IMG via MobileOdin
--------------------------------
SGH-S959G; (courtesy of @mr-cook)
TWRP 2.6.3.0.zip
--OR--
CWM 6.0.4.5.zip.
Initial Installation:
=================
FLASH:
1) mr-cook's ROM wipe script
2) OmniROM: http://dl.omnirom.org/i777/
3) 4.4 Gapps: >PA 0 day< MICRO recommended (see GApps note)
4) ROOT access: Super-SU (optional)
Updating Nightlies (manual or OTA):
=================
FLASH:
1) OmniROM: http://dl.omnirom.org/i777/ (See "SURVIVAL" note)
-Happy Flashing
-Cyril
*Ownership:
Entropy512 said:
I'll create an official thread for this eventually... I suck at XDA threads for the devices I work on, as anyone who has seen the i777 CM threads can attest.
Yeah, I'm the one that did the bringup for the I777 (with help from many of the n7000 guys for general 4.4 bringup stuff).
Just as a warning the device is pretty low on my priorities list - it's kind of in automode. Of course, submissions to Omni gerrit are always welcome![...]
Click to expand...
Click to collapse
KNOWN ISSUES:
Attaching picture from camera folder crashes messaging
http://jira.omnirom.org/browse/OMNI-740
Click to expand...
Click to collapse
Repeated/frequent voice typing on AOSP keyboard causes soft reboot
http://jira.omnirom.org/browse/OMNI-739
Click to expand...
Click to collapse
menu-button unlocks device when feature is disabled UNTIL feature is toggled on and off again
http://jira.omnirom.org/browse/OMNI-138
Click to expand...
Click to collapse
Music player stops playing music from sd after some time
http://forum.xda-developers.com/showthread.php?t=2612329&page=18
http://forum.xda-developers.com/gal...l-cm11-omni-4-4-slimkat-t2222843/post51005727
Best workaround as of 2014, April 5: http://forum.xda-developers.com/showpost.php?p=51657055&postcount=304
Also, formatting both internal and external SD cards to exfat seem to solve the immediate issue, but do not solve the root fuse-daemon problem.
The internal SD card of the i777 can be formatted via ADB console in windows, or using exfat-utils in ubuntu
Click to expand...
Click to collapse
NOTES:
GApps: The size of full Gapps packages crowds /system, preventing the use of other /system based units (art, xposed, etc). Micro Gapps + google play installation of desired addons is a more efficient approach considering the resources available.
Click to expand...
Click to collapse
SURVIVAL: Go to super SU settings and install backup script. Root will survive updates. As for gapps, most installs include backup scripts. You don't need to re-flash them.
in system/addon.d, you should have a 99-supersu.sh, and 70-gapps.sh backup scripts, which survive the Rom update.
The script backs up beforehand and will restore after the flash.
From the backup script..
#!/sbin/sh
#
# /system/addon.d/99-supersu.sh (root:root 755)
# During an upgrade, this script backs up SuperSU-related files,
# /system is formatted and reinstalled, then the files are restored.
#
(info collected from this G+ conversation)
Click to expand...
Click to collapse
How to install CWM from TWRP?
3men2 said:
Boot into TWRP recovery
choose Install
Go to emmc to acces the internal sdcard and go to where you have the kernel with cwm( Siya, AJK, STI)
Flash the Kernel, when finished DON'T TOUCH REBOOT SYSTEM, Just go back to previous screen and choose the reboot to recovery option.
You will boot into CWM now and will be able to wipe everything without issues...
Click to expand...
Click to collapse
MobileOdin Install:
(procedure verified working (running SHOstock & Jeboo Kernel, & AT&T stock-rooted firmware) as of 2013-12-13 12:49):
With your phone on fully booted into (whatever ROM)
1) Gather all necessary flash files onto internal sdcard before performing these steps.
---a) Boot.IMG (extracted from omni-4.4.x-latesti777-nightly.zip)
---b) MrCook's ROM wipe.zip
---c) Omni-nightly.zip
---d) PA GApps (optional)
---e) SuperSU (optional)
2)Mobile-odin flash Omni's boot.img
>>the phone will try to reboot, but will likely fail. Three-finger salute (with the USB cable UNPLUGGED), until you are in TWRP recovery<<
3) [install] > [COOK'S ROM WIPE.zip] > [add more zips] > [omni-4.4.x-latesti777-nightly.zip] > [add more zips as desired] >>swipe to confirm flash>> [reboot system]
Click to expand...
Click to collapse
Spinergy02 said:
[...]"In system root data folder (/data) make a blank file named local.prop
Edit the file and add qemu.sf.lcd_density=195 I set my density to 195.
Set permissions to 644 (rw/r/r)"
So apparently settings in local.prop override build.prop and aren't lost when flashing a new nightly. I'd guess this would work for any settings that you wanted to retain between flashes. [...]
Click to expand...
Click to collapse
cyril279 said:
http://dl.omnirom.org/i777/
-Happy Flashing
-Cyril
Click to expand...
Click to collapse
Thanks! I will flash and test it out!
Running this as I type. So far so good. I'm on ST version
Sent from my SGH-959g using Tapatalk 2
Can this ROM dance with the AJK kernel?
atvspecialties said:
Running this as I type. So far so good. I'm on ST version
Sent from my SGH-959g using Tapatalk 2
Click to expand...
Click to collapse
What gapps did you flash?
BInspirinG said:
What gapps did you flash?
Click to expand...
Click to collapse
I myself flashed ParanoidAndroid's 4.4 GApps.
Untitled87 said:
Can this ROM dance with the AJK kernel?
Click to expand...
Click to collapse
Unfortunately, as of v4.9, it is not compatible with KitKat in general.
azeem40 said:
I myself flashed ParanoidAndroid's 4.4 GApps.
Unfortunately, as of v4.9, it is not compatible with KitKat in general.
Click to expand...
Click to collapse
Could you provide the steps in which you flashed this rom? I wiped both flashes, system and data. I've tried flashing 3 times now, but the only thing it'll do is reload and then go back into recovery mode.
I've always noticed that it says:
"script succeeded: result was [/system]"
Any help with the direction I should take?
Steps:
1) mr cook's ROM wipe script
2) Flash Omni
3)Flash PA 4.4 Gapps
BInspirinG said:
Could you provide the steps in which you flashed this rom? I wiped both flashes, system and data. I've tried flashing 3 times now, but the only thing it'll do is reload and then go back into recovery mode.
I've always noticed that it says:
"script succeeded: result was [/system]"
Any help with the direction I should take?
Click to expand...
Click to collapse
BInspirinG said:
Could you provide the steps in which you flashed this rom? I wiped both flashes, system and data. I've tried flashing 3 times now, but the only thing it'll do is reload and then go back into recovery mode.
I've always noticed that it says:
"script succeeded: result was [/system]"
Any help with the direction I should take?
Click to expand...
Click to collapse
I factory reset, wiped cache, wiped dalvik, installed Omni, installed Gapps, and rebooted phone.
I used the gapps linked in RenderBroken's 4.4. I also had to use the supersu option as root didn't show up. :thumbup::thumbup::thumbup::thumbup:
Sent from my SGH-959g using Tapatalk 2
azeem40 said:
I factory reset, wiped cache, wiped dalvik, installed Omni, installed Gapps, and rebooted phone.
Click to expand...
Click to collapse
BInspirinG said:
Could you provide the steps in which you flashed this rom? I wiped both flashes, system and data. I've tried flashing 3 times now, but the only thing it'll do is reload and then go back into recovery mode.
I've always noticed that it says:
"script succeeded: result was [/system]"
Any help with the direction I should take?
Click to expand...
Click to collapse
You may also need to update your recovery by flashing the last CM Nightly. Thats what i did and I had no issues.
I'll create an official thread for this eventually... I suck at XDA threads for the devices I work on, as anyone who has seen the i777 CM threads can attest.
Yeah, I'm the one that did the bringup for the I777 (with help from many of the n7000 guys for general 4.4 bringup stuff).
Just as a warning the device is pretty low on my priorities list - it's kind of in automode. Of course, submissions to Omni gerrit are always welcome!
And if any I9100ers drop by and wonder why there is no I9100 yet - I don't own one, and I'm not sure what happened to xplodwild's... I think his might be dead.
OmniRom nightlies for i777 use TWRP RECOVERY
I haven't been this happy about a release in god knows how long. I just did a FULL-ON HAPPY DANCE!
@Entropy512, I didn't mean to steal your thunder, I was excited to share your released work with the community.
I have tried manually wiping and formatting, along with using the rom script by cook. Both yields the same results for me. All 4 tried have been from the 11/26 CM 10.2 nightly.
Basically, after my wiping and flashing processes, the phone just reboots into recovery again.
I'm running this one.
http://dl.omnirom.org/i777/omni-4.4-20131127-i777-NIGHTLY.zip
These gapps
http://d-h.st/PbA
Sent from my SGH-959g using Tapatalk 2
I'm running the 1127 nightly with PA-Gapps (Modular Full).
When you're playing music on either the built-in player or Google Music, you get a ~1sec audio error (not a skip, more like a digital stutter) when the screen goes off and when you unlock.
I also switched to ART to see if it made any difference in the above. It didn't.
Not huge, just reporting.
auTONYmous said:
I'm running the 1127 nightly with PA-Gapps (Modular Full).
When you're playing music on either the built-in player or Google Music, you get a ~1sec audio error (not a skip, more like a digital stutter) when the screen goes off and when you unlock.
I also switched to ART to see if it made any difference in the above. It didn't.
Not huge, just reporting.
Click to expand...
Click to collapse
Idk why, but whenever I switch over to art with that same gapps package, I get force closes left and right. Weird...
---------- Post added at 04:05 PM ---------- Previous post was at 03:46 PM ----------
I have noticed that this ROM give me pretty bad battery life. Otherwise, performance is great. I will report back tomorrow night for my final verdict on battery life.
auTONYmous said:
I'm running the 1127 nightly with PA-Gapps (Modular Full).
When you're playing music on either the built-in player or Google Music, you get a ~1sec audio error (not a skip, more like a digital stutter) when the screen goes off and when you unlock.
I also switched to ART to see if it made any difference in the above. It didn't.
Not huge, just reporting.
Click to expand...
Click to collapse
Yepp that basically ear-raped me the first time it happened. And the second. Thats when I stopped listening to my music hahaha.
More customization coming soon?
Will the security element emulation for wallet become implemented? I always wanted to use NFC payment on this phone
Sent from my SGH-I777 using Tapatalk
Hi mates. I've gotten a problem on flashing any AOSP based roms. Any time I try to flash these roms I will get this error shown in the screenshot attached. I had this error with Haxynos 5.1.1 rom and aokp.
No answer?
C'mon there must be a way guys. I really need this.
Why were you trying to install an older build over the newer one? That is the source of the error I think.
Jericho Arcelao said:
Why were you trying to install an older build over the newer one? That is the source of the error I think.
Click to expand...
Click to collapse
I installed haxynos marshmallow build a month ago. And I always clean flash everything except internal storage before a rom flashing so there shouldn't be any problem with that. The error it give me is cause of an unknown file from flashing that marshmallow rom that I flashed before as I think. So maybe an address to delete that file can help me. And downgrading is something normal in rom flashing. There shouldn't be any error with it. I always can downgrade Cyanogenmod based roms. It is a matter for me to be able to downgrade. But I can't format my internal storage. and I can't boot that marshmallow rom from haxynos even!?!
Have u wiped ur system before installing?
---------- Post added at 09:40 AM ---------- Previous post was at 09:40 AM ----------
Tell me fast
JohnSmit268 said:
Hi mates. I've gotten a problem on flashing any AOSP based roms. Any time I try to flash these roms I will get this error shown in the screenshot attached. I had this error with Haxynos 5.1.1 rom and aokp.
Click to expand...
Click to collapse
wipe data system dev & cache then try agian this will work :good:
I always clean internal storage before doing any flashes. There is still app cache left even if you do a factory reset, resulting in data incompatible with other ROMs. Those caches might be those files you were talking about. And that is also why I have an extsdcard to store my rom stuff
AdvaitT17 said:
Have u wiped ur system before installing?
---------- Post added at 09:40 AM ---------- Previous post was at 09:40 AM ----------
Tell me fast
Click to expand...
Click to collapse
Yes of course I did. Plz look at that screenshot!!! I posted it for you guys.
Jericho Arcelao said:
I always clean internal storage before doing any flashes. There is still app cache left even if you do a factory reset, resulting in data incompatible with other ROMs. Those caches might be those files you were talking about. And that is also why I have an extsdcard to store my rom stuff
Click to expand...
Click to collapse
App cache can be deleted in recovery by wiping cache and I know where app caches are stored. I always delete them. And anyway no app cache can make a rom not to get flashed like this!!!
ibra993 said:
wipe data system dev & cache then try agian this will work :good:
Click to expand...
Click to collapse
As I said I always clean flash. Means wiping these things you said.
Anyway c'mon guys, you didn't even look at the screenshot, I wiped these as shown in that screenshot
JohnSmit268 said:
App cache can be deleted in recovery by wiping cache and I know where app caches are stored. I always delete them. And anyway no app cache can make a rom not to get flashed like this!!!
Click to expand...
Click to collapse
Its weird it happens to me. Like when I install FB and I clean data but not internal there's a folder named com.facebook.katana or something like that still staying there. And there's cache inside. Anyway I remember now that my flash back then was ok even though it was only a ROM migration and not a migration of android version. Just try wiping internal for once. It might just help
Im also got this error while flashing aokp rom
AdvaitT17 said:
Im also got this error while flashing aokp rom
Click to expand...
Click to collapse
I'm also getting it on flashing Haxynos 5.1.1
[SOLVED] Solved it myself. Thank you all.
Hi guys. I solved it myself. I remembered that I used to edit the apps that gapps zip files remove from my ROM by editing this file: META-INF>>com>>google>>Android>>updater-script
So I opened my aokp ROM zip and opened that file and see this line in the top of the script:
(!less_than_int(1413593113, getprop("ro.build.date.utc"))) || abort("Can't install this package (Sat Oct 18 02:45:13 CEST 2014) over newer build (" + getprop("ro.build.date") + ").");
that will request the build date and match it with the ROM and if the build date was newer it won't flash the ROM. So I edited the updater-script and removed this lines from it and save the zip and voila! It get flashed and booted. Anyway I think putting this line to the updater-script is a cruel action. Maybe somebody have problems with the current ROM and wanna revert!!
JohnSmit268 said:
Hi guys. I solved it myself. I remembered that I used to edit the apps that gapps zip files remove from my ROM by editing this file: META-INF>>com>>google>>Android>>updater-script
So I opened my aokp ROM zip and opened that file and see this line in the top of the script:
(!less_than_int(1413593113, getprop("ro.build.date.utc"))) || abort("Can't install this package (Sat Oct 18 02:45:13 CEST 2014) over newer build (" + getprop("ro.build.date") + ").");
that will request the build date and match it with the ROM and if the build date was newer it won't flash the ROM. So I edited the updater-script and removed this lines from it and save the zip and voila! It get flashed and booted. Anyway I think putting this line to the updater-script is a cruel action. Maybe somebody have problems with the current ROM and wanna revert!!
Click to expand...
Click to collapse
So it was just with the updater-script. Well good for you
Well I decided to repartition my i9100 so I could get GAPPS with CM13...
Used oden to reformat with a pit = i9100_Preload_Area_Moddified_Pit_Files_-_NOT_FOR_STOCK_ROMS! (3)\I9100_12GB data - 45mb preload.pit per site upgrade, and PDA = samsung1012\kk-kernel-04-02-CWM-for ODIN.tar . Now it all only works with CM 11.XX with gapps. If I go to upgrade to later releases 12 or try 13 I get the CG face forever.
I am really frustrated as it was all ok under 13.xx minus gapps and I wanted to use Google apps.
Thanks.
wgibbons said:
Well I decided to repartition my i9100 so I could get GAPPS with CM13...
Used oden to reformat with a pit = i9100_Preload_Area_Moddified_Pit_Files_-_NOT_FOR_STOCK_ROMS! (3)\I9100_12GB data - 45mb preload.pit per site upgrade, and PDA = samsung1012\kk-kernel-04-02-CWM-for ODIN.tar . Now it all only works with CM 11.XX with gapps. If I go to upgrade to later releases 12 or try 13 I get the CG face forever.
I am really frustrated as it was all ok under 13.xx minus gapps and I wanted to use Google apps.
Thanks.
Click to expand...
Click to collapse
You are using a pit file with unmodified /system. You need a pit file such as i9100_1gb_6gb.pit where the 1gb is the new /system size
noppy22 said:
You are using a pit file with unmodified /system. You need a pit file such as i9100_1gb_6gb.pit where the 1gb is the new /system size
Click to expand...
Click to collapse
Ok where can I find such. The system is rooted and CM 13 has worked ...my noob mistake.
wgibbons said:
Ok where can I find such. The system is rooted and CM 13 has worked ...my noob mistake.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162
noppy22 said:
http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162
Click to expand...
Click to collapse
Clearly I am doing something wrong I plug this pit int ODEN I91001GB_6GB.pit and this into PDA
kk-kernel-04-02-CWM-for ODIN.tar
format/reboot are set. Now it loops.
wgibbons said:
Clearly I am doing something wrong I plug this pit int ODEN I91001GB_6GB.pit and this into PDA
kk-kernel-04-02-CWM-for ODIN.tar
format/reboot are set. Now it loops.
Click to expand...
Click to collapse
I am stuck
wgibbons said:
I am stuck
Click to expand...
Click to collapse
Once you have flashed the pit file and kernel, switch off the phone.
Then -
1. Reboot to recovery(CWM)
2. Format sdcard0(internal sd card), preload, system, data, cache
3. Wipe dalvik/art cache
4. Install rom + gapps etc. as per rom thread instructions
5. Reboot and wait for a good 10-15 minutes if needed for system to install
wgibbons said:
I am stuck
Click to expand...
Click to collapse
what rom and gapps. cm 13.xx
wgibbons said:
what rom and gapps. cm 13.xx
Click to expand...
Click to collapse
Whatever rom/gapps you want to flash. The bigger 1gb /system is required for CM13(or any MM rom) with gapps. If you use pico gapps(open gapps) you can install most LP roms without modifying /system, but it is recommended anyway
I have the same issue. Have flashed multiple pit files (1GB/3GB, 1GB/6GB etc) and tried cm12 and cm13 and they both are not working. Have tried flashing the TWRP recovery etc. CM11 is working fine, 12 and 13 not
three2five said:
I have the same issue. Have flashed multiple pit files (1GB/3GB, 1GB/6GB etc) and tried cm12 and cm13 and they both are not working. Have tried flashing the TWRP recovery etc. CM11 is working fine, 12 and 13 not
Click to expand...
Click to collapse
I am sorry, I need to take a break as this is all so problmatic. I love my samsung but starting to wonder. What might seem easy an straight forward to some can be hard for others thinking they are somehow inadequate. sorry.
noppy22 said:
Whatever rom/gapps you want to flash. The bigger 1gb /system is required for CM13(or any MM rom) with gapps. If you use pico gapps(open gapps) you can install most LP roms without modifying /system, but it is recommended anyway
Click to expand...
Click to collapse
Can you please link a gapps that works with I9100 and cm 13.XX. Much appreciated
wgibbons said:
Can you please link a gapps that works with I9100 and cm 13.XX. Much appreciated
Click to expand...
Click to collapse
http://opengapps.org/
arm; 6.0; pico
or http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
marshmallow base package
I have di=one what you suggested and have CM13 and gapps working but have one odd sympton. SD1 (external) is fine. System seems fine repartitioned but it shows SD0 as unformatted? I wa ssure to reformat I believe when I went through the process. Is this tyical?
Thank to the help of this forum my Galasxys2 is running perfectly 6.1 with gapps and reformatted. I did this again :
Once you have flashed the pit file ie: home, down power - Connect via usb (with correct samsung drivers) to P.C running oden 3.4 with these preloadsd flas the pit file and kernel, (reformat selected in Ooden) , Up key teh phone and when done switch off the phone.
Then -
1. Reboot to recovery(CWM) with Home, up, power.
2. Format sdcard0 (internal sd card), then data, cache, system, preload,
3. Wipe dalvik/art cache
4. Install rom (CM13) latest release + gapps(6.1) per above etc. as per rom thread instructions pre installed on my SD1 in a dedicated folder in the phone.
5. Reboot and wait for a good 10-15 minutes if needed for system to install
The trick I found was the sequence of formats after doing the pit remap and initial load. I tried and got failure on "preload formatt so did in the order above and it worked. Thanks PPL. esp Noppy22. A 64 YO bloke repartitioning and flashing his phone. 26 YO son simply went and bought a new nexus.
Format
Spoke too soon The internal SD 0 will not format and the camera and other stuff that uses it won't work. CM13 and gapps all great. What can I do.
Doh. I had the wrong kernel and formatted the sd0 xfat and all works now.
Introduction
Hello all, this is my version of TWRP for the Nexus 6P, which includes the ability to convert your /data and /cache partitions to F2FS. This will stay inline with TWRP's changes for the most part, the changes will be listed below.
What in the world is F2FS?
From Wikipedia:
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
F2FS was designed on a basis of a log-structured file system approach, which it adapted to newer forms of storage. Jaegeuk Kim, the principal F2FS author, has stated that it remedies some known issues of the older log-structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. In addition, since a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), it supports various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Click to expand...
Click to collapse
Before diving into this, I would recommend reading the official F2FS documentation to understand why this may be good for you. This is potentially unstable, F2FS is a file system that is very much in active development. There is a reason that most OEMs go with ext4 out of the box. But I digress, I am NOT here to sell you on F2FS; it makes zero difference to me if you use it or not, I am merely providing you with a tool to do so.
Changelog + differences
Differences:
f2fs-tools bumped to 1.7.0 (Omni's 6.0 branch is on 1.4.0)
TWRP app installation offer disabled by default
Conversion procedure
Download TWRP from the link above
Grab a kernel that supports F2FS (I use my own as I know it works)
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, you may need to ask your ROM developer to merge the two commits below.
Bug reports
You are NOT in ANY circumstance to report ANY bugs to the TWRP team.
If you have an issue with flashing something in TWRP, copy the recovery log to your sdcard and post it here.
If swapping to F2FS does not stick, try formatting your data with TWRP (Wipe > Format Data) or fastboot format userdata first.
If your phone does not boot after swapping to F2FS, either your kernel or ROM does not have proper support; post in their thread.
Additionally, check out some of these helpful posts:
https://forum.xda-developers.com/showthread.php?p=70699197
https://forum.xda-developers.com/showthread.php?p=71074016
Adding support to ROM
In order to properly support the initial conversion to F2FS, please add these two commits to your source:
https://github.com/omnirom/android_system_core/commit/1c6700a8fb31c6e314df4f031fa23fa9178c7ca7
https://github.com/omnirom/android_system_vold/commit/c879edb2fecae709f404c2d71c1d47ceac3a325e
The reason some people have issues converting is fs_mgr will try to read the block device as ext4 and destroy the f2fs block. This commit skips that check, allowing F2FS to pass through.
Sources
TWRP is licensed under GPLv3, meaning my changes must be disclosed. I also inline a custom kernel so that source is included as well. I also add in the other repos I modify.
Recovery: https://github.com/nathanchance/android_bootable_recovery/tree/android-7.1
Kernel: https://github.com/nathanchance/angler/tree/7.1.2-flash
Device tree: https://github.com/nathanchance/twrp_device_huawei_angler/tree/android-6.0
f2fs-tools: https://github.com/nathanchance/android_external_f2fs-tools/tree/android-6.0
First!
Thanks for the recovery. Been using it with flash kernel. I see considerable performance improvement in asphalt Xtreme game( idk if its the f2fs or kernel ).
Nice !!! :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you, and thank you for the exemplary GPL compliance. It's noticed and appreciated.
Now this is awesome... On it, will report soon
Much appreciated!
Sent from my Nexus 6P using Tapatalk
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Nitrogen : yes
Somebody must report it and i will update my post.
ThNks
ariefabuzaky said:
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Somebody must report it and i will update my post.
ThNks
Click to expand...
Click to collapse
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Worked perfect! Thanks Flash!!!
I tried this with PN and am now stuck in a boot loop. I flashed the twrp with F2FS support then tried to change the file system followed by installing the latest vendor, latest flashable bootloader+radio, latest pure nexus and gapps, flash kernel, and latest su. Didnt work. Im not stuck in a boot loop I cant get out of. Ive tried every combination of the above. I also tried restoring my backup but that gives me an error. I also tried changing the file system back to ext4. Nothing works. Anyone experience this or have any suggestions?
---------- Post added at 09:09 AM ---------- Previous post was at 08:58 AM ----------
jochem86 said:
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Click to expand...
Click to collapse
Im in the same boat.....what steps did you do to get back to stock?
Data keeps reverting back to ext4 after 1st boot.
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
Mine too....Im stuck in a bootloop. Are you?
Whats also weird is switching too f2fs wiped my storage but once the data reverted back to ext4....my original storage came back too!! Im not sure how or why that is happening either.
I just followed OP and formatted everything first, now i have SAOSP running with flash on f2fs..
Works great, so far it doesn't feel like a huge improvement though..
Sent from my Nexus 6P using XDA-Developers Legacy app
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
What makes you say that?
Back then when I was using Temasek on my Note 3, he incorporate a script that automatically format the system partition to F2FS when flashing his ROM. That is if the system partition is already in f2fs and I think that was pretty amazing but short live. I wonder if other ROM developer could go the same route if formatting F2FS system was popular enough. That would make updating new rom one step easier. Just for thought.
---------- Post added at 09:38 AM ---------- Previous post was at 09:16 AM ----------
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
minhgi said:
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
Click to expand...
Click to collapse
I wish you told this earlier....This is exactly what happened and I had to clean install
NoobInToto said:
I wish you told this earlier....This is exactly what happened and I had to clean install
Click to expand...
Click to collapse
It wouldn't matter though, I get a warning that the backup was made with EXT4 and that backup may not boot unless changed back to it
Iceburn1 said:
What makes you say that?
Click to expand...
Click to collapse
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
Exactly doing the same....
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
That's too bad its not working for you, its working on my side no problem, did you format in twrp if its not sticking? Im on RR with Flash kernel.
THREAD CLOSED!!!
[G531F] CS-Rom v3.2 (android 5.1.1) by Adi [FIXED ALL BUGS!]
Features:
-Pre-Rooted,
-Xposed Framework installed,
-Busybox installed,
-Customizable Status Bar,
-Customizable Notification Bar,
-Deodexed,
-Debloated,
-Deknoxed,
-Some Xposed Modules,
-Added SU.D Support,
-Added Custom Bootanimation,
-Now it's Zipaling,
-Added Init.D Support,
-Much more...
Installation:
Flashable Zip Version:
-Download ZIP,
-Move ZIP to SD Card or Internal Storage,
-Boot into TWRP,
-Wipe: Cache, Dalvik, Data, System,
-Flash ZIP,
-Reboot.
Backup Version:
-Download ZIP,
-Extract ZIP.
-Move TWRP folder to SD Card or Internal Storage,
-Boot into TWRP,
-Restore backup,
-Reboot.
DOWNLOAD:
-Flashable ZIP without TouchWiz (NougatLauncher):
https://drive.google.com/uc?id=0B2OyU1OLo9sjbmRuakExMXRrVGs&export=download
-Flashable ZIP with TouchWiz:
https://drive.google.com/uc?id=0B2OyU1OLo9sjc2xsSFh6RjdwX0E&export=download[/B]
-TWRP Backup without TouchWiz (NougatLauncher):
https://drive.google.com/uc?id=0B2OyU1OLo9sjQXFXa2ZSNEd4Q3M&export=download[/B]
-TWRP Backup with TouchWiz:
https://drive.google.com/uc?id=0B2OyU1OLo9sjNTJRZEZJcWFtaGs&export=download[/B]
Special Thanks to Imioł (XDA nick : Sh0peN) for lending the device.
FINALLY!
Perfect!
Hope it works fine, waiting so long..
You might need to flash GApps...
EDIT:Just flash the 5.1 GApps for OpenGApps, if it doesn't work.
does this rom have any issue
Destroyer08 said:
does this rom have any issue
Click to expand...
Click to collapse
Probably not.
At last...thank you very much
what version of recovery do you use?
melc70 said:
what version of recovery do you use?
Click to expand...
Click to collapse
TWRP 3.0.2-0
error
Destroyer08 said:
does this rom have any issue
Click to expand...
Click to collapse
error extractfork() process ended witherror 255
[email protected] said:
error extractfork() process ended witherror 255
Click to expand...
Click to collapse
idk whats wrong... do full wipe or something
[email protected] said:
error extractfork() process ended witherror 255
Click to expand...
Click to collapse
Now I'm working on 2.0 version...
adiJ5FN said:
TWRP 3.0.2-0
Click to expand...
Click to collapse
That version never existed for SMG-531F as far as I'm aware.
In addition, I followed all the instructions, but TWRP won't detect the backup.
Version : TWRP : 2.8.7
Any ideas about how to fix that ? I have been waiting for a custom ROM for two years now.
?
TWRP 2.8.7 Cant see the file when i press Restore
just create a boot backup, write the folder name and delete it if you want, rename the rom folder.
!
Perfect rom...thanks....
Can i get rid of FRP lock after flashing this rom?
Hi,
I'm new and amateur with this thing, but can someone tell me cause I own G531F with Android 5.1.1, if I do everything from this few steps posted in the first link, will I have Android 6 on my phone or do I need to do something more beside that?
Thanks!
Incognito493 said:
That version never existed for SMG-531F as far as I'm aware.
In addition, I followed all the instructions, but TWRP won't detect the backup.
Version : TWRP : 2.8.7
Any ideas about how to fix that ? I have been waiting for a custom ROM for two years now.
Click to expand...
Click to collapse
TWRP 3.0.2-0 Just flash via odin...
https://forum.xda-developers.com/attachment.php?attachmentid=3955426&d=1480666661
Important
I can't make this work, I don't have enough storage because it's too big, i got 8 gb internal and 2gb. Compress it or maybe do it as a install from twmp not restoring it.