Newbie here.
How can I enable f2fs in arter's kernel? What would be the procedure? and how can I have both f2fs+supersu?
Is there any downside of it?
Thanks in advance.
ShiShTuBaBu said:
Newbie here.
How can I enable f2fs in arter's kernel? What would be the procedure? and how can I have both f2fs+supersu?
Is there any downside of it?
Thanks in advance.
Click to expand...
Click to collapse
I used f2fs on RR ROM a while back. It doesn't have any noticeable performance improvement over ext4. Plus you will have to incompatibilities with custom ROMs and kernels.
I used official RR Rom With blue spark kernel.
Kernel Link: http://forum.xda-developers.com/oneplus-3/development/kernel-t3404970
As I said before you won't notice any improvements but if you want to give it a try :good:
Prince Chandela said:
I used f2fs on RR ROM a while back. It doesn't have any noticeable performance improvement over ext4. Plus you will have to incompatibilities with custom ROMs and kernels.
I used official RR Rom With blue spark kernel.
Kernel Link: http://forum.xda-developers.com/oneplus-3/development/kernel-t3404970
As I said before you won't notice any improvements but if you want to give it a try :good:
Click to expand...
Click to collapse
True. I didn't notice any improvements in arter97's kernel too. tried to revert back to my OOS backup and now my home button isn't working. any solution?
ShiShTuBaBu said:
True. I didn't notice any improvements in arter97's kernel too. tried to revert back to my OOS backup and now my home button isn't working. any solution?
Click to expand...
Click to collapse
Flash the correct firmware version from http://forum.xda-developers.com/oneplus-3/development/firmware-updates-oos-3-1-2-3-5-2-t3465312
Check your OxygenOS version in Settings > About Phone
kgs1992 said:
Flash the correct firmware version from http://forum.xda-developers.com/oneplus-3/development/firmware-updates-oos-3-1-2-3-5-2-t3465312
Check your OxygenOS version in Settings > About Phone
Click to expand...
Click to collapse
I have flashed OOS op3lite rom and everything working good. But recently I'm seeing my phone is encrypted. I have to give my pattern everytime while accessing twrp and system.
any solution for this? Thanks.
fastboot erase userdata
You will lose data
kgs1992 said:
Flash the correct firmware version from http://forum.xda-developers.com/oneplus-3/development/firmware-updates-oos-3-1-2-3-5-2-t3465312
Check your OxygenOS version in Settings > About Phone
Click to expand...
Click to collapse
if I restore my oos 3.2.7 backup and then flash 3.2.6 firmware over it will my home button work? and will this firmware change anything of my backup rom?
Thanks again.
ShiShTuBaBu said:
if I restore my oos 3.2.7 backup and then flash 3.2.6 firmware over it will my home button work? and will this firmware change anything of my backup rom?
Thanks again.
Click to expand...
Click to collapse
Flash 3.2.7 firmware if you restore a 3.2.7 backup.
Stock firmware is compatible only with it's corresponding stock ROM.
Custom ROMs are compatible mostly with firmware <=3.2.6 & 3.5.0 (varies with ROM).
Also, take a look at this if you have problems with unlocking your phone after restore.
This thread has gone way off-topic. Please post your questions here.
Related
I'm using nijel8's Unofficial LineageOS 14.1 and am really pleased with it. My previous rom was the weekly Xiaomi.EU rom for Xiaomi Mi Max Helium.
When I updated my Xiaomi.EU Rom, I would reboot into recovery and then:
1. Backup > system/data/boot
2. Install new ROM.zip
3. Wipe > Advanced Wipe > Dalvik /ART Cache and Cache
4. Reboot.
Is it the same process with LineageOS 14.1? There are FIRMWARE.zips and I installed one during my initial installation of the rom. Do I need to updated the firmware again, then install the rom, or do I just skip it and install the ROM.zip?
I didn't think it was appropriate to litter the main thread with this question, so I'm hoping I get an answer here.
Thanks in advance.
Yep, same procedure + gapps, firmware update is up to you. You can skip it if you don't have problems but in general is good to be on the same firmware as the MIUI base.
nijel8 said:
Yep, same procedure + gapps, firmware update is up to you. You can skip it if you don't have problems but in general is good to be on the same firmware as the MIUI base.
Click to expand...
Click to collapse
OK. I will flash the new firmware and the rom update. Cheers!
But gapps? Can't I just leave the updating of Google stuff to the play store?
EDIT: I did some more Googling and now understand why. All is good. I backed up, flashed the most recent firmware just to be safe. Worked fine. Then I flashed the updated ROM and the Gapps I installed before and rebooted. Smooth as silk.
Is screen cast / Miracast working for you on this ROM?
nijel8 said:
Yep, same procedure + gapps, firmware update is up to you. You can skip it if you don't have problems but in general is good to be on the same firmware as the MIUI base.
Click to expand...
Click to collapse
sebr said:
Is screen cast / Miracast working for you on this ROM?
Click to expand...
Click to collapse
I don't use those features. Sorry.
Tried search and nothing found.
Is there a custom rom on lollipop or nougat where the big cores have been disabled in the kernel?
I've been using the stock firmware with the 2 big cores disabled for some time and the phone working fine.
Thanks
Looking for the same, mine is H811 and there is no tot file to disable the Big Cores
I'm trying to flash with H810 kdz and install the tot file for the H810 too, i think doing that, i'll solve the problem but now is another problem, HOW CAN I DO IT?! Hehe
Use kernel auditor on any rooted ROM and disable yourself
dpgc213 said:
Tried search and nothing found.
Is there a custom rom on lollipop or nougat where the big cores have been disabled in the kernel?
I've been using the stock firmware with the 2 big cores disabled for some time and the phone working fine.
Thanks
Click to expand...
Click to collapse
NestorRamUre said:
Looking for the same, mine is H811 and there is no tot file to disable the Big Cores
I'm trying to flash with H810 kdz and install the tot file for the H810 too, i think doing that, i'll solve the problem but now is another problem, HOW CAN I DO IT?! Hehe
Click to expand...
Click to collapse
Imperium kernel has a version for marshmallow with disabled big cores, Titan kernel has a version for nougat. But your bootloader has to be unlocked to use them.
ufocus said:
Imperium kernel has a version for marshmallow with disabled big cores, Titan kernel has a version for nougat. But your bootloader has to be unlocked to use them.
Click to expand...
Click to collapse
I already have my bootloader unlocked!
Can you help me to install this kernel on it?
I'll be pleased to get your help man!
NestorRamUre said:
I already have my bootloader unlocked!
Can you help me to install this kernel on it?
I'll be pleased to get your help man!
Click to expand...
Click to collapse
Imperium kernel v7.3c (marshmallow aka v20 firmwares) with disabled BIG cores
https://androidfilehost.com/?fid=745849072291682063
Flash it in TWRP then wipe dalvik/ART cache, cache and your good to go.
ufocus said:
Imperium kernel v7.3c (marshmallow aka v20 firmwares) with disabled BIG cores
https://androidfilehost.com/?fid=745849072291682063
Flash it in TWRP then wipe dalvik/ART cache, cache and your good to go.
Click to expand...
Click to collapse
Where you recommend me to install the kernel, on stock android or Imperium Rom?
Can i intall it on LineageOS or RR too?
NestorRamUre said:
Where you recommend me to install the kernel, on stock android or Imperium Rom?
Can i intall it on LineageOS or RR too?
Click to expand...
Click to collapse
You can on both, it's your decision to make, Imperium kernel is for stock and stock based custom ROMs only.
Titan has a version for stock and another for LOS, AOSP, RR LOS based... etc. BUT there's only three ROMs compatible with Titan for LOS and LOS based for now.
ufocus said:
You can on both, it's your decision to make, Imperium kernel is for stock and stock based custom ROMs only.
Titan has a version for stock and another for LOS, AOSP, RR LOS based... etc. BUT there's only three ROMs compatible with Titan for LOS and LOS based for now.
Click to expand...
Click to collapse
Man i've tried many times and it won't install the kernel, i've been trying to install it on LineageOS, ResurrectionRemix and a cople more but is just says "Installing kernel", and it won't pass from there
And i want to install stock but i don't know how
ufocus said:
Imperium kernel v7.3c (marshmallow aka v20 firmwares) with disabled BIG cores
https://androidfilehost.com/?fid=745849072291682063
Flash it in TWRP then wipe dalvik/ART cache, cache and your good to go.
Click to expand...
Click to collapse
Man thanks you so much!
What i did was, install Stock KDZ (H81120v_00_0425) and having already TWRP installed i flashed Imperium Kernel (KERNEL - h815_imperium-7.3c_4cores_TWRP-flashable) and BOOM! IT WORKED PERFECTLY! Now my phone is living again without bootloop issues!
I think this is the only way to fix H811 bootloop issus:
1. Try to boot your device, at least 1 minute to active Developer Options and inside it active USB Debugging and OEM Unlock, after it turns off again.
2. Install TWRP, and flash 4cores Imperium Kernel.
3. Done! Your phone will be back to life again!
NestorRamUre said:
Man thanks you so much!
What i did was, install Stock KDZ (H81120v_00_0425) and having already TWRP installed i flashed Imperium Kernel (KERNEL - h815_imperium-7.3c_4cores_TWRP-flashable) and BOOM! IT WORKED PERFECTLY! Now my phone is living again without bootloop issues!
I think this is the only way to fix H811 bootloop issus:
1. Try to boot your device, at least 1 minute to active Developer Options and inside it active USB Debugging and OEM Unlock, after it turns off again.
2. Install TWRP, and flash 4cores Imperium Kernel.
3. Done! Your phone will be back to life again!
Click to expand...
Click to collapse
Glad you've figured it out and posted it.
Hi everybody ! I have a simple question please. I have a Op 3 with custom Rom based on Oos name FreedomOs. if I make a nandroid of all my Rom. Before I Factory reset my Op 3 and flash another Rom type lineageOs and use it. but if I don't like it ! I can restore my nandroid backup of FreedomOs ? thank you.
ggkameleon said:
Hi everybody ! I have a simple question please. I have a Op 3 with custom Rom based on Oos name FreedomOs. if I make a nandroid of all my Rom. Before I Factory reset my Op 3 and flash another Rom type lineageOs and use it. but if I don't like it ! I can restore my nandroid backup of FreedomOs ? thank you.
Click to expand...
Click to collapse
Yes just make sure you disable any lock screen passwords and fingerprints before creating your nandroid backup because sometimes when restoring your nandroid it will say the password is wrong...
Xceeder said:
Yes just make sure you disable any lock screen passwords and fingerprints before creating your nandroid backup because sometimes when restoring your nandroid it will say the password is wrong...
Click to expand...
Click to collapse
Thank you For your support
It's nice.. I want test another Rom !!! Just for see
Yes remove my password !!! And just see if the Rom are compatible with f2fs because I had format my Data in f2fs.
ggkameleon said:
Thank you For your support
It's nice.. I want test another Rom !!! Just for see
Yes remove my password !!! And just see if the Rom are compatible with f2fs because I had format my Data in f2fs.
Click to expand...
Click to collapse
And always use the latest recovery by blu_spark it has the best compatibility with different ROMs ...
If I have helped please leave a thumbs up on my posts i truly appreciate it ...
Xceeder said:
And always use the latest recovery by blu_spark it has the best compatibility with different ROMs ...
If I have helped please leave a thumbs up on my posts i truly appreciate it ...
Click to expand...
Click to collapse
Thank's :good:
Exactly I use always The TWRP Modified "blu_spark" by "eng-stk"
I always use too, the Custom Kernel ElementalX with the ElementalX manager App and apply the Profile Akt.
I use this config For more than a year and it works very well and above all it is very stable.
But I want to try other Rom and Kernel to change a bit. I never use the blu_spark Kernel but I think is similar of ElementalX !?
I want use the Render "Kernel Oos-N-EAS-R2" because use EAS and it's different.
Thank you for your post. I go to make my Nandroid and test other Rom/Kernel
Xceeder said:
And always use the latest recovery by blu_spark it has the best compatibility with different ROMs ...
If I have helped please leave a thumbs up on my posts i truly appreciate it ...
Click to expand...
Click to collapse
Thank's :good:
Exactly I use always The TWRP Modified "blu_spark" by "eng-stk"
I always use too, the Custom Kernel ElementalX with the ElementalX manager App and apply the Profile Akt.
I use this config For more than a year and it works very well and above all it is very stable.
But I want to try other Rom and Kernel to change a bit. I never use the blu_spark Kernel but I think is similar of ElementalX !?
I want use the Render "Kernel Oos-N-EAS-R2" because use EAS and it's different.
Thank you for your post. I go to make my Nandroid and test other Rom/Kernel
(Sorry for my bad english)
This Rom is the OFFICIAL 8.1 STOCK rom, heavly debloated and flasheable via TWRP. Based on J730FM but functional on any J730XX
Instructions (twrp)
1-download zip
2-wipe cache, system and data
3-flash the rom
Kernel: STOCK
BUGS WITH STOCK Kernel J730G: Fingerprint and bluethoot.
If anyone can help fixing those bugs we would all appreciate it.
TIP: The rom work perfectly with Helios Kernel by Ananjaser
DOWNLOAD: https://drive.google.com/file/d/1dK3r720bEENQKYgnZB6hsDTwVfKxJI-F/view
Credits: Miguel Escalante
This link is for STOCK 8.1 ROM WITH ALL BLOATWARE. But works perfectly
Link: https://mega.nz/#!z0MSwQIZ!Kp1nVdfo8YxXuuFu45sMlKsBt3QaSjZJBxIOwlnJGME
Man, I'm on stock kernel, but no problems with fingerprint and bluetooth, no problems with usb or anything. What's wrong with custom rom?
ion1s said:
Man, I'm on stock kernel, but no problems with fingerprint and bluetooth, no problems with usb or anything. What's wrong with custom rom?
Click to expand...
Click to collapse
You are on This Rom? And you no have bugs?
I'm on stock 8.1.0 from J730FM and I have J730F, but everything works fine with stock kernel.
ion1s said:
I'm on stock 8.1.0 from J730FM and I have J730F, but everything works fine with stock kernel.
Click to expand...
Click to collapse
The bugs is in J730G
Where did you get the official 8.1 rom from?
quanghuy226 said:
Where did you get the official 8.1 rom from?
Click to expand...
Click to collapse
From J730FM
lite rom with (1,3GB)
xloolx said:
lite rom with (1,3GB)
Click to expand...
Click to collapse
Hi, I'm Miguel Escalante.
A super lite version (1.1Gb) you can find in EDOS V2.
In this rom there are many features (themes without limit time, goodloock, call records, etc), you can see in this post
https://forum.xda-developers.com/ga...m-oreo-8-1-j7-pro-exynos-7870-f-fm-g-t3842058
will it work on j730gm???
sgrkoirala said:
will it work on j730gm???
Click to expand...
Click to collapse
My girlfriend have this model and dont have problems
sgrkoirala said:
will it work on j730gm???
Click to expand...
Click to collapse
yes, its working and i am using J730gm only
So if i used helios kernel, bluetooth and fingerprint will work in my j730g? Is that what you mean?
eugene15 said:
So if i used helios kernel, bluetooth and fingerprint will work in my j730g? Is that what you mean?
Click to expand...
Click to collapse
Everything is working fine when you install Helio kernel along with the rom
can fix it the touchscreen issue?
Princepaul12 said:
can fix it the touchscreen issue?
Click to expand...
Click to collapse
I am using this rom for a week and i dont encounter any problems bro. Volte(Jio) is working very good and there is no touch screen issues still
From time to time loudsreaker is silent! Helps only to tern off and then tern on/
works excellent Thanks !
I have a J7 2017 (J730F) and it does not let me flinch by Odin but I do through TWRP and I would like to know if I can somehow convert the 4 files of the original stock ROM into a single file flashed by TWRP.
HUGE thanks to @giri45 for actually providing the fix!
What's this?
A Unity installer ensures that you can use this module with any kind of root solution (as long as it supports init.d)! If you have Magisk, flash the module through the Magisk Manager, but if you don't have Magisk, just flash the module through TWRP. When you want to uninstall the module, flash it again in Magisk Manager or TWRP.
As for the module itself, it provides a fix for LiveDisplay/Night Light on the Moto G5/G5S for anyone running an AOSP-based ROM running Android 9 or higher, and enables Camera2 API + EIS if you wish so.
Do NOT attempt to install this on other devices, or ROMs based on Android <9! Device and Android version checks have been applied to make sure this module will not install on incompatible devices. This module assumes that you are using the latest stock Oreo firmware (including bootloader, GPT and etc.)! Do not report issues if you are not on the latest firmware.
Tested ROMs:
Havoc OS 2.2
Pixel Experience 9.0
AOSPExtended 6.3
crDroid 5.0
Known issues:
Fix doesn't work on Nougat firmware. You must have fully flashed the stock ROM/flashed it via OTA, for this fix to work.
Downloads:
Download from Magisk Repo.
Flash via Magisk Manager or TWRP. Make sure you have a root solution which supports init.d!
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Ænimal said:
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Click to expand...
Click to collapse
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
JarlPenguin said:
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
Click to expand...
Click to collapse
Deleted
PE 9.0LOG is attached
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Ænimal said:
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Click to expand...
Click to collapse
It's an internal build. You can test it out here: https://t.me/montanadevelopment
JarlPenguin said:
It's an internal build. You can test it out here: https://t.me/montanadevelopment
Click to expand...
Click to collapse
I'm running this build now and tried the fix but to no avail, still (xt1794)
Ænimal said:
I'm running this build now and tried the fix but to no avail, still (xt1794)
Click to expand...
Click to collapse
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
JarlPenguin said:
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
Click to expand...
Click to collapse
Nougat firmware and Oreo baseband, screen is original. Do you think that partition table is the problem?
Ænimal said:
Nougat firmware and Oreo baseband. Do you think that partition table is the problem?
Click to expand...
Click to collapse
Okay, I think I have found the problem now. What have you not upgraded?
JarlPenguin said:
Okay, I think I have found the problem now. What have you not upgraded?
Click to expand...
Click to collapse
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Ænimal said:
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Click to expand...
Click to collapse
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
JarlPenguin said:
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
Click to expand...
Click to collapse
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Ænimal said:
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Click to expand...
Click to collapse
That's weird... One thing I know that is that this fix doesn't work on Nougat firmware.
Working flawlessly on crDroid 9.
Thank you devs!
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Arn'oh said:
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Click to expand...
Click to collapse
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
zahidm said:
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
Click to expand...
Click to collapse
I had updated to Oreo official beta test with fastboot commands
Arn'oh said:
I had updated to Oreo official beta test with fastboot commands
Click to expand...
Click to collapse
Did you flash everything? Try fully flashing Stock Oreo via Fastboot and then install TWRP, custom ROM and this fix.