you can only restore efs and carrier partitions.I have a F model too. took me a good 4hrs to restore a twrp backup after losing IMEI issue. i wont flash it till its all good on other users.
you can only restore efs and carrier partitions.I have a F model too. took me a good 4hrs to restore a twrp backup after losing IMEI issue. i wont flash it till its all good on other users.
It is tested without any issuesI have a F model too. took me a good 4hrs to restore a twrp backup after losing IMEI issue. i wont flash it till its all good on other users.
Yup... dirty flashing was never good on any thing and always causes issuesNow I'm getting a different error but that's probably my problem. CSC and force commands like _xposed work now.
I now get an error saying can't mount new /system after installing with no OS installed after flashing but I don't think that's your files but rather me not wiping and dirty flashing for example or my TWRP isn't working really well..
This ROM is only made for N960F/FD onlytested on my n960n and fails right at the beginning by script check so no idea why people with F had issues.
No need to do anything except that you need to do full wipe then flash my ROM... it already have vendor on it same as original DevBase ROMMy note 9 is f/ds model and on dev based android pie rom. If I would like to flash this rom, what will be the procedure. Do I need to flash oreo firmware first then flash your rom? Do I need to flash vendor partition too? Please advise. Thank you.
You mean wipe system, data and also do i need to flash ARL BL?No need to do anything except that you need to do full wipe then flash my ROM... it already have vendor on it same as original DevBase ROM
Enjoy
YesYou mean wipe system, data and also do i need to flash ARL BL?
I don't suffer from any bluetooth pairing issues... I have my own smartwatch and I pair with it without any issuesHmm. I am still facing the whole rooted Oreo Bluetooth pairing issues on this ROM. All rooted Oreo ROMs have this and the magisk module doesn't fix it. I think it's cause it moves the files to /system/vendor/lib when they have to be in /system/lib. And it doesn't disable securestorage in build.prop.
I manually placed the files and edited build.prop so it should work now. Can only test this on my car stereo when I'm off from work.
I will also upload the BL from ARL4 if you haven't done it yet when I get home this afternoon. I still have the .md5 on my PC ready for Odin flashing so.. no big deal.
There is a module in magisk meant for the s9 which I did have active but it didn't help. Might also be my cheap car stereo that just isn't very cooperative hehe. If my manual fix works I'll just leave it be for now.I don't suffer from any bluetooth pairing issues... I have my own smartwatch and I pair with it without any issuesI have a specific magisk module I personally use it... it is made by @Eamo5 so... it is not found in magisk store or repo
I will provide it later today with the BL file but first... let me ask Eamo5 permission because he is the one who made itif he accepts... I will include magisk module download link in the main post
![]()
I mainly use L Speed for performance & battery tweaks... some people dislike this app but... to my experience with it.. the difference is night & day.. you just need to know which settings you must enableThere is a module in magisk meant for the s9 which I did have active but it didn't help. Might also be my cheap car stereo that just isn't very cooperative hehe. If my manual fix works I'll just leave it be for now.
For the rest your ROM is running very well, nice and snappy, battery is fine as I don't use any tweaks like L Speed. I do use Endurance Kernel but also untweaked. Amy recommendations in terms of tweaks i should do?
Then I guess you don't have any idea of flashing ROMs :silly: mount invalid argument error usually related to dirty flashinghellow,I ve flahed bootloader,then your rom...ir doesn t work (unable to mount invalid argument)
i m on F version...
so i get back to O8 again...
maybee with a aroma installer...
have a nice day
and ,how after flashing bootloader via odin,there was no system installed in my phone...Then I guess you don't have any idea of flashing ROMs :silly: mount invalid argument error usually related to dirty flashing
Have a nice day...
in twrp manually mount all partitions b4 zip.and ,how after flashing bootloader via odin,there was no system installed in my phone...
and I can run ketan s aroma rom,and not your...?
i ve got rooted phones since my first htc,so what?
tks i ll give it a tryin twrp manually mount all partitions b4 zip.
if still an issue, then manually UNmount all partitions b4 zip.
so if its a mount issue ull know. also check if system or internal data is not 0 size
it doesn t work for me...I tried everthing but...tks i ll give it a try![]()
well for starters it clearly says ure rom zip is corrupt.it doesn t work for me...I tried everthing but...