I'M NOT RESPONSIBLE FOR ANY DAMAGE AND/OR DATA LOSS AS A RESULT OF FLASHING THIS ROM !!!
PLEASE PERFORM FULL BACKUP IN THE MICRO SD CARD OR IN AN EXTERNAL STORAGE BEFORE YOU TRY !!!
Do you need reliability and predictability? Then better stay with THIS ROM
I have decided to create a separate thread because:
- I would like to distinguish PIE BETA bug reports from my normal (OREO stable) thread, mentioned above
- It is normal that there will be definitely much more "bad reports" here, because most of them will be "beta related"
This thread will be closed when Samsung will release stable Android Pie (One UI)
Everything you will need to know about DevBase ROM in general - you will find in my stable thread (mentioned above)
Differences comparing to stable Oreo DevBase ROM:
- No Xposed (we need to wait for rovo89)
Note 8 (SM-N950F/DS):
>> N950FXXU2ZSB2_DevBase_v6.0.zip << (MEGA)
>> N950FXXU2ZSB2_DevBase_v6.0.zip << (AFH)
Click to expand...
Click to collapse
Dirty flash over my Oreo DevBase ROM SHOULD WORK WITHOUT ISSUES but before you try - I would highly recommend you to set default (stock) theme and default (stock) icons !!! However - I would recommend you clean install (Wipe -> Swipe to Factory Reset is enough).
Please REMOVE custom options.prop file if you have any in /sdcard or external sdcard (mainly because of debloat list which causes more issues in Pie).
Known problems:
- [CLEAN INSTALL] Magisk Manager may not appear after clean install despite Magisk has been installed without errors during install - if you notice that there is no Magisk Manager - DO NOT flash Magisk, it is enough to install Magisk Manager as normal app (use ATTACHMENT - it is original apk from Magisk v18.1), then REBOOT device (important!)
- OEM unlock toggle seems to be disabled in the Developer Options but it is not true (otherwise you would not be able to use TWRP and this ROM). It is side effect of protection I put in the kernel against "KG State: Prenormal" in the DM mode. It is not real issue, just ignore it. EDIT: starting from ZSAB - OEM unlock toggle has been HIDDEN to avoid further confusion! Don't worry about that
SafetyNet PASS in this ROM
Thanks to:
- @corsicanu for share me untouched N950F dump
- all persons mentioned in my main thread
Wow wow wow
Sent from my SM-N950F using XDA Labs
Altarnatif link pls. thnx
HorstiG said:
Wow wow wow
Click to expand...
Click to collapse
Absolutely true
Hako06 said:
Altarnatif link pls. thnx
Click to expand...
Click to collapse
Done... AFH mirror has been added
Why Magisk 17.3?
Sent from my SM-G955F using XDA Labs
HorstiG said:
Why Magisk 17.3?
Sent from my SM-G955F using XDA Labs
Click to expand...
Click to collapse
This ROM flashes Magisk v17.3 in case of clean install or v18.0 in case of dirty flash - it is because known problem with sudden reboot at the end of setup wizard with v18.0 and clean install. So my recommendation is - DO NOT update Magisk until you pass setup wizard.
So... that only means that you performed clean flash When you finish initial setup - just install attached magisk.apk, then update via Magisk Manager. Next time (dirty update) it will install v18.0
I have another problem, OEM Toggle is off and I get this message after each reboot.
Sent from my SM-G955F using XDA Labs
CSC is okay
Sent from my SM-G955F using XDA Labs
HorstiG said:
I have another problem, OEM Toggle is off and I get this message after each reboot.
Sent from my SM-G955F using XDA Labs
Click to expand...
Click to collapse
Have you read post #1 (known problems) ?? Just ignore that it is off position (it is not true, it just reads real state wrong due to strong RMM/KG state protection I put in the kernel). Every time you will try to enable it - it will force you to wipe data, nothing more - will stay in off position (only visually)
Sorry, According to the message, says there is a problem with the device, I should contact the Manufacturer
Sent from my SM-G955F using XDA Labs
---------- Post added at 11:09 PM ---------- Previous post was at 10:49 PM ----------
After flashing Magisk same problem. But everything works
Sent from my SM-G955F using XDA Labs
What about going back to Oreo? Is the Pie BL working for Oreo?
Can I flash this rom for note korean n950n?
_alexndr said:
Done... AFH mirror has been added
Click to expand...
Click to collapse
Glad to see this up! Keep up the amazing work!
why do i keep getting this error from the first biot if this rom?
and whats the meaning of it?
it's a bit scary notification
p.s: full wipe and clean install
I have the dolby atmos button ,but i can't activate it. Does it work dolby atmos?
HorstiG said:
[...] After flashing Magisk same problem. But everything works
Click to expand...
Click to collapse
Alivevil said:
why do i keep getting this error from the first biot if this rom?
and whats the meaning of it?
it's a bit scary notification
p.s: full wipe and clean install
Click to expand...
Click to collapse
Nothing wrong with your device, really It is side effect of changed "ro.build.fingerprint" in build.prop to pass SafetyNet (thanks to @corsicanu for the hint & tests)
If it is really annoying to you - you can restore original line in build.prop, as follow:
Code:
ro.build.fingerprint=samsung/greatltexx/greatlte:9/PPR1.180610.011/N950FXXU5ZSA5:user/release-keys
... but then SafetyNet will fail and most of banking apps + GooglePay + some other apps that check SafetyNet - will not work anymore
_alexndr said:
Nothing wrong with your device, really It is side effect of changed "ro.build.fingerprint" in build.prop to pass SafetyNet (thanks to @corsicanu for the hint & tests)
If it is really annoying to you - you can restore original line in build.prop, as follow:
Code:
ro.build.fingerprint=samsung/greatltexx/greatlte:9/PPR1.180610.011/N950FXXU5ZSA5:user/release-keys
... but then SafetyNet will fail and most of banking apps + GooglePay + some other apps that check SafetyNet - will not work anymore
Click to expand...
Click to collapse
nice explanation! And from the other side: what value should have ro.build.fingerprint to pass safetyNet?
Do I get it right that there's no publicly available Pie kernel sources, and thus there's absolutely no way to get SELinux permissive until the official release?
_alexndr said:
Nothing wrong with your device, really It is side effect of changed "ro.build.fingerprint" in build.prop to pass SafetyNet (thanks to @corsicanu for the hint & tests)
If it is really annoying to you - you can restore original line in build.prop, as follow:
... but then SafetyNet will fail and most of banking apps + GooglePay + some other apps that check SafetyNet - will not work anymore
Click to expand...
Click to collapse
I have a boarding computer in my car that shows me at launch I need to service. The master says no problem, drive quietly on. It totally annoys though. I have the bug fixed, but I can't refuel anymore. This is a bad solution and must work differently.
Sent from my SM-N950F using XDA Labs
Related
Hello and welcome to my Thread,
I want to share with you the daily driver for my brothr. I'm not a Brain my some other gus here .
Stock+ (HyperStock) is only a factory image based Rom. I cook it with SuperR's Kitchen and I only debloated it, add bootanimation and "steal" ah I mean add some Mods. Even the bootanimation is ripped.
WHY MAGISK?
Becouse my Brother like to play Pokemon GO and Magisk is the easiest way to hide root for some Apps like Pokemon or Snapchat.
Disclaimer:
#ReadMe
We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
Features:
lastest OnePlus Image (OxygenOS 3.6.1)
Odex
Magisk v14.3
Busybox 1.27.2
no force encryption
removed dm-verity checks
init.d support
insecure boot image
Marvel VS DC bootanimation
AdAway v3.2
HTC Gallery
HTC Music Player
Xposed Installer
build.prop Tweaks
zipalign APK's
2,4 GHz WiFi improved
enable Miracast
disabled ADB Icon
uncolored Powersafer Mode
headphone volume warning disabled
heavy debloated
system/app/AntHalService*
system/app/BookmarkProvider*
system/app/BTtestmode*
system/app/btmultisim*
system/app/Chrome*
system/app/DMAgent*
system/app/DivesIconPack*
system/app/Drive*
system/app/Duo*
system/app/EngineeringMode*
system/app/EngSpecialTest*
system/app/FaceLock*
system/app/Galaxy4*
system/app/Hangouts*
system/app/HoloSpiralWallpaper*
system/app/LiveWallpapers*
system/app/Maps*
system/app/ModemTestMode*
system/app/Music2*
system/app/NFCTestMode*
system/app/OemAutoTestServer*
system/app/OEMLogKit*
system/app/OPBugReport_Complete*
system/app/OpenWnn*
system/app/OPWallpapers*
system/app/PartnerBookmarksProvider*
system/app/Photos*
system/app/PrintSpooler*
system/app/PhaseBeam*
system/app/RifonIconPack*
system/app/Stk*
system/app/SensorTestTool*
system/app/SwiftKey*
system/app/SwiftKeyFactorySettings*
system/app/talkback*
system/app/Videos*
system/app/WifiRfTestApk*
system/app/YouTube*
system/priv-app/OnePlusGallery*
system/priv-app/OPSimContacts*
system/reserve/Forum*
system/reserve/OPMusic*
system/reserve/SoundRecorder*
system/etc/usb_drivers.iso*
system/etc/recovery-resource.dat*
system/recovery-from-boot.p*
Click to expand...
Click to collapse
Chancelog:
- rebased on OxygenOS 3.6.1
- updated to magisk & magisk manager
- removed gms (Play Service) from Doze Whitelist
- updated Xposed Installer
Click to expand...
Click to collapse
Download:
-> Stock+ OOS 3.6.1
-> OOS 3.6.1 Firmware+Radio
-> LiveWallpaperPicker (<- If you need it)
Installation
From OOS 3.5.X:
- Download the ROM & copy it on your phone
- Do a factory wipe
- Flash the ROM and wait
- Enjoy
From not OOS based roms
-Flash the lastest OOS image
- Follow the intruction from the OOS part
FAQ:
#ReadMe
#1 DPI
if you want to change the dpi you need to flash the Zip from [email protected] ZIP. OxygenOS have some issues with changing the DPI.
#2 Xposed Installer don't work with Magisk Xposed
If you use the Xposed Module from Magisk Manager, you need to use the systemless Xposed Installer from here
if you like the ROM rate it and hit thanks
if you realy like it buy me a kebap
Special Thanks:
- Google
- XDA
- OnePlus
- SupeR
- Chainfire
- osm0sis
- Mentalmuso
- SyCreed
- NevaX1
- dh.harald
- Christian Tailor (for Marvel VS DC GIF)
- B!Gguy
- all I forgot
XDA:DevDB Information
HyperStock OxygenOS , ROM for the OnePlus 2
Contributors
Sh0X31
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: OOS 3.5.X
Version Information
Status: Stable
Created 2017-04-17
Last Updated 2017-04-17
I've been looking for something similar.... Will definitely give it a try
Can you change the dpi without problem? In stock is out of place some icons, use 360 ​​dpi:laugh:
Sent from my OnePlus 2 using XDA Labs
hey i just wanna ask that if you have installed exposed frameworks , is pokemon go still playable ??
Zyubi said:
hey i just wanna ask that if you have installed exposed frameworks , is pokemon go still playable ??
Click to expand...
Click to collapse
I don't know, I build the ROM but I have to ask my bro if he use Xposed or not
hpbrasil said:
Can you change the dpi without problem? In stock is out of place some icons, use 360 ​​dpi:laugh:
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Try it and report
Sh0X31 said:
I don't know, I build the ROM but I have to ask my bro if he use Xposed or not
Try it and report
Click to expand...
Click to collapse
No, the status bar icons are the same ... And the icons in the power off menu are the same, out of place. :crying:
Sent from my OnePlus 2 using XDA Labs
Almost removed every app which was causing android system battery drain:laugh: very excited to flash this one.... Nice job....
Anyway you can make the notification slider have custom settings
Do you mean custom Tiles?
Sh0X31 said:
Do you mean custom Tiles?
Click to expand...
Click to collapse
No I mean the slider button on the left side of the phone
Nice..works great..
Post edited
hpbrasil said:
No, the status bar icons are the same ... And the icons in the power off menu are the same, out of place. :crying:
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Yeah... this is a crazy weird issue since every build of Oxygen has been able to correctly allow changing of the DPI without any issue. I was discussing this in another thread somewhere far, far away since I don't recall where. But I think it has something to do with a specific frameware file or something to do with the frameware.. it's damn strange that all of a sudden we can't adjust the DPI. I do know a quick-fix-hack is to use an Xposed module that will allow you to change the DPI of specific apps but it still disfigures the whole system if you do it systemwide..
jbarcus81 said:
Yeah... this is a crazy weird issue since every build of Oxygen has been able to correctly allow changing of the DPI without any issue. I was discussing this in another thread somewhere far, far away since I don't recall where. But I think it has something to do with a specific frameware file or something to do with the frameware.. it's damn strange that all of a sudden we can't adjust the DPI. I do know a quick-fix-hack is to use an Xposed module that will allow you to change the DPI of specific apps but it still disfigures the whole system if you do it systemwide..
Click to expand...
Click to collapse
Waiting edition framework :highfive:
Charging speed is very slow unlike oos 3.5.8 it took 4 hours... For 10-100
Cable is new and was working fine with oos 3.5.8... So no problems in hardware part...
Installing this rom will replace TWRP?
Anyone tested ?
hoppingpanda said:
Installing this rom will replace TWRP?
Anyone tested ?
Click to expand...
Click to collapse
No..
mackhenri said:
Nice..works great..
Post edited
Click to expand...
Click to collapse
Significant performance /battery improvement.?
QQRaju said:
Significant performance /battery improvement.?
Click to expand...
Click to collapse
It's snappy compared to stock.. Battery lasts a little longer then stock
Is there any mirror available? I can't download from mega.nz it doesn't seems to work
yousuf.shareef said:
Is there any mirror available? I can't download from mega.nz it doesn't seems to work
Click to expand...
Click to collapse
same for me... there is quota exceeding message.
can somebody add another link?
EDIT: solved by creating free Mega account
Build 2017/11/12 #OPO
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOPO
#TugaPower O 1.0 RC LineageOS #laos #OnePlus #Android 8.0.0 #OMS #SubstratumRootLess
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
Please be sure you are using one TWRP that can handle firmware flash. ( http://forum.xda-developers.com/oneplus-one/development/unofficial-twrp-3-0-x-tugapower-t3398366 )
Also be sure you are using proper firmware. The one recomended its the one from cm 13 nighly, you can find here: https://meocloud.pt/link/c1d9a297-e3f7-480b-9567-1bc601c073dd/TugaPowerFirmwareCM13_v4.zip/ , altough people also have good results using the c7 firmaware
Relative to gapps, testing open gapps 8.0 nano package, working without issues
http://opengapps.org/?api=8.0&variant=nano
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
V4A for the time being its not working so its removed.
Kcal Support ( use Color Control app to adjust colors )
Gello removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Call Record ( Not yet ported )
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
Kernel permissive
PoGO: Gonna catch then all
Full support to Substratum OMS RootLess without Andromeda
Powered by Magisk root v14.x and Magisk Manager 5.0.x versions
Replaced Trebuchet with latest Lawnchair beta ( https://github.com/Deletescape-Media/Lawnchair )
What does not works:
Check post 2
Let me know to add there
Also make a clean install, do not attempt to flash over Nougat rom or other based OREO roms, it will probably fail or have problems.
Change log O 1.0 RC:
Android r30
November Patch
Initial build of TugaPower ROM based on Lineage Oreo
Stuff will be added in future, little patiente, also be in mind this is a Release Candidate and stuff could be not working at all.
Report if you find something not working.
Thanks all for the support.
Download: https://androidfilehost.com/?fid=745849072291688147
MD5: 9c4f663a02943d111d7325db3c19f396
Please dont mirror for now the roms zips, thanks
A big thanks to @jhalayashraj for the help and patiente
Sources :
Rom:- https://github.com/LineageOS
Device:- https://github.com/Fabulous-Oreo/device_oneplus_bacon
Kernel:- https://github.com/Fabulous-Oreo/kernel_oneplus_msm8974
Bugs
Buttons configuration its not possible.
Use apk as workround to config
https://play.google.com/store/apps/details?id=com.irishin.buttonsremapper
Privacy Guard does not work.
Block orientation in horizontal does not work
Tips:
https://forum.xda-developers.com/showthread.php?p=74496475
Woww first one to comment..downloading the rom right now
Damn, I've been eagerly awaiting the Oreo ROM blessed by Daniel. Thanks man, can't wait to get it flashed.
Awesome work. Thanks.
Does this require a clean flash? It would it work a dirty flash over N52?
Sent from my A0001 using Tapatalk
Thanks for this awesome Oreo ROM! :good:
Downloading now. . .
KlotX said:
Awesome work. Thanks.
Does this require a clean flash? It would it work a dirty flash over N52?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Clean flash needed....
slimbullet said:
Clean flash needed....
Click to expand...
Click to collapse
Thanks
Sent from my A0001 using Tapatalk
are there any known bugs?
camera is oos？
lilzad said:
are there any known bugs?
Click to expand...
Click to collapse
Buttons for now are not configurable...
BB～ said:
camera is oos？
Click to expand...
Click to collapse
Camera is using sultan blobs, because its the only one for now that works on oreo
Daniel, not the hero we deserve but the hero we need!
Please
can i use the data backup from N52 after a clean flash?
Or should i create new datas?
danieldmm said:
Buttons for now are not configurable...
Camera is using sultan blobs, because its the only one for now that works on oreo
Click to expand...
Click to collapse
Wait so cm blob doesn't even work?
ludskyrider said:
Please
can i use the data backup from N52 after a clean flash?
Or should i create new datas?
Click to expand...
Click to collapse
Everithing that its system related do not backup/restore, its asking for problems, user apps and user apps data should not be an issue.
DeadFox-xda said:
Wait so cm blob doesn't even work?
Click to expand...
Click to collapse
Over Lineage camara would not even work.
danieldmm said:
Everithing that its system related do not backup/restore, its asking for problems, user apps and user apps data should not be an issue..
Click to expand...
Click to collapse
Well, i was just talking about a data backup
Wooooowww Tuga power
danieldmm said:
Camera is using sultan blobs, because its the only one for now that works on oreo
Click to expand...
Click to collapse
I'm afraid that's not entirely true.Aex oreo is not using sultan's hals and camera still works fine except for the video recording,which is bound to fix soon.
Mr.Ak said:
I'm afraid that's not entirely true.Aex oreo is not using sultan's hals and camera still works fine except for the video recording,which is bound to fix soon.
Click to expand...
Click to collapse
Good for him, even on mine was facing the video recording issue, the fix was easy on my case.
Just need to change some paths of audio.
Code:
$(LOCAL_PATH)/audio/audio_platform_info.xml:system/vendor/etc/audio_platform_info.xml \
$(LOCAL_PATH)/audio/audio_policy.conf:system/vendor/etc/audio_policy.conf \
$(LOCAL_PATH)/audio/mixer_paths.xml:system/vendor/etc/mixer_paths.xml
Its all moved to vendor folder in my case. This fixed audio sound problems and video camera recording.
first of all, thanks for developer, it is the step forward and anyway like it or not, it just another one rom at the popular base (oreo), so we can think that our device is still not forgotten. 3 oreo roms here,,,
then i'd like to share my exp with this rom.
- it's very fast and simple to install, i've just flashed twrp under my cm13 and wiped data, cache and system, no storage wipe, no format. just a few moments and it works without boaring startup wzrd.
- i've got less SOD situations at first use. may be i can see it after installantion of progs (and their services), but other roms (except stock) shows much worse results, and i even suppose i'll be able to use it in casual life (no custom roms can do it before: hydrogen 7.12., flyme 6. oreo - even didn't started properly).
- the fail is that the buttons are not configurable, i hope i can use something like mi-pop or other soft-button app.
- i see, there are some other bug can be, there is a first build, so, feel free to write you first looks.
Mod Edit:
Thread closed due to no link provided, as well as rude, disrespectful OP statement.
So apart from F/DS devices, would it work on a N?
How about vendor, is it included?
Thanks
bober10113 said:
So apart from F/DS devices, would it work on a N?
How about vendor, is it included?
Thanks
Click to expand...
Click to collapse
I don't believe it would work on an N because the firmware I used is specifically for an F/DS device. Has it even been released on the N yet?
The vendor needed for Android Pie *is* included, as is modem, kernel, etc.
chrisaw said:
I don't believe it would work on an N because the firmware I used is specifically for an F/DS device. Has it even been released on the N yet?
The vendor needed for Android Pie *is* included, as is modem, kernel, etc.
Click to expand...
Click to collapse
Usually Fs and Ns are identical hardwarewise except system partition size is a tad smaller I believe.
I'll give it a shot and report back.
edit:
i checked script and bootloader and mdem are being flashed wich is a big no no for N devices.
plus as i can see there have been a complaint so...
chrisaw said:
If anyone takes offence to this ROM for any reason - please let me know and I'll take it down immediately.
Click to expand...
Click to collapse
Yes I have objection.
You can not use my modified images. You want to make your own then there is one thread in geneneral section. Get pie beta on your device and then dump it yourself.
Its my request to remove my work and meanwhile you make your own, remove the link.
chrisaw said:
Description
I really love this new Android 9.0 beta from Samsung with the One UI. I also really love DevBase!
With that in mind - I've created PieBase which is simply a combination of:
- Latest DevBase release (from here - thanks _alexndr)
- Latest Magisk release (from here - thanks topjohnwu)
- Latest Samsung Pie firmware (from here - thanks drketan)
If anyone takes offence to this ROM for any reason - please let me know and I'll take it down immediately. As soon as official DevBase is released - I'll remove this post and direct any visitors to his thread. I'm not even remotely interested in stealing people away from DevBase - it's an awesome ROM - just looking to fill the void for now.
SafetyNet Pass
In order to get SafetyNet to pass with Magisk you will need to:
Download Busybox magisk module
Download MagiskHide Props Config magisk module
Reboot your device
Download and open a terminal app of your choice
Switch to root by entering the "su" command
Enter "props" then enter: 1, f, 13, 24, y, y
Once your device has done rebooting - you should now be passing SafetyNet. The reason this is needed is simply because beta versions of Samsung ROMs never pass SafetyNet so we're claiming to be an 8.0 running device to Google so they'll pass us as running a known Samsung ROM.
Warnings
App names and dependencies have changed around a lot in this release so your old configs likely wont work!
You are welcome to try to attempt to dirty flash this ROM but it's VERY likely you will need to clean flash (sorry!)
If you have a /sdcard/devbase directory - rename this before flashing.
If you have a /sdcard/options.prop file - rename this before flashing.
This ROM is for F/DS ONLY!!!
Download
Mod Edit: Link removed
Click to expand...
Click to collapse
Hi. Ur rom is almost copy of Dr. Ketan rom. Does not sounds legitimate. Suggest u to rethink & close the thread.
Sent from my SM-N960F using XDA-Developers Legacy app
I'M NOT RESPONSIBLE FOR ANY DAMAGE AND/OR DATA LOSS AS A RESULT OF FLASHING THIS ROM !!!
PLEASE PERFORM FULL BACKUP IN THE MICRO SD CARD OR IN AN EXTERNAL STORAGE BEFORE YOU TRY !!!
Do you need reliability and predictability? Then better stay with THIS ROM
I have decided to create a separate thread because:
- I would like to distinguish PIE BETA bug reports from my normal (OREO stable) thread, mentioned above
- It is normal that there will be definitely much more "bad reports" here, because most of them will be "beta related"
This thread will be closed when Samsung will release stable Android Pie (One UI)
Everything you will need to know about DevBase ROM in general - you will find in my stable thread (mentioned above)
Differences comparing to stable Oreo DevBase ROM:
- No Xposed (we need to wait for rovo89)
S8 (SM-G950F/FD):
>> G950FXXU4ZSB9_DevBase_v6.0.zip << (MEGA)
>> G950FXXU4ZSB9_DevBase_v6.0.zip << (AFH)
Click to expand...
Click to collapse
S8+ (SM-G955F/FD):
>> G955FXXU4ZSB9_DevBase_v6.0.zip << (MEGA)
>> G955FXXU4ZSB9_DevBase_v6.0.zip << (AFH)
Click to expand...
Click to collapse
Dirty flash over my Oreo DevBase ROM SHOULD WORK WITHOUT ISSUES but before you try - I would highly recommend you to set default (stock) theme and default (stock) icons !!! However - I would recommend you clean install (Wipe -> Swipe to Factory Reset is enough).
Please REMOVE custom options.prop file if you have any in /sdcard or external sdcard (mainly because of debloat list which causes more issues in Pie).
Known problems:
- [CLEAN INSTALL] Magisk Manager may not appear after clean install despite Magisk has been installed without errors during install - if you notice that there is no Magisk Manager - DO NOT flash Magisk, it is enough to install Magisk Manager as normall app - use ATTACHMENT (it is original apk from Magisk v18.1) and then reboot device (important!!!)
- OEM unlock toggle seems to be disabled in the Developer Options but it is not true (otherwise you would not be able to use TWRP and this ROM). It is side effect of protection I put in the kernel against "KG State: Prenormal" in the DM mode. It is not real issue, just ignore it. EDIT: starting from ZSAC - OEM unlock toggle has been HIDDEN to avoid further confusion! Don't worry about that
SafetyNet PASS in this ROM
Thanks to:
- @corsicanu, @piyushkohli97 & @OnikdudeX for share untouched G950F dump
- @cobrax05 & @Leejhay1714 for share untouched G955F dump
- all persons mentioned in my main thread
Testing Now.
Could anyone upload to another server?Coz I downloaded other file from mega and it says bandwith limit exceeded.I have to wait 4hrs...
edweder said:
Could anyone upload to another server?Coz I downloaded other file from mega and it says bandwith limit exceeded.I have to wait 4hrs...
Click to expand...
Click to collapse
I will upload it to AFH, stay tuned
EDIT: Done
_alexndr said:
I will upload it to AFH, stay tuned
Click to expand...
Click to collapse
Thank youuu :good:
This is what im waiting for, devbase ?% stock thanks a lot
Sir give us pie for s8??
So after samsung release stable pie, you will make new thread?
Waiting for the S8
ROM has been re-uploaded - removed "There's an internal problem with your device" popup at start (thanks to @corsicanu for the tip)
Ogy77 said:
Sir give us pie for s8??
Click to expand...
Click to collapse
Kirazz said:
Waiting for the S8
Click to expand...
Click to collapse
I need a dump (does anybody have a link?) or help from an experienced user who can update his phone with OTA update.zip, then make the dump (I can send detailed instruction via PM)
_alexndr said:
ROM has been re-uploaded - removed "There's an internal problem with your device" popup at start (thanks to @corsicanu for the tip)
I need a dump (does anybody have a link?) or help from an experienced user who can update his phone with OTA update.zip, then make the dump (I can send detailed instruction via PM)
Click to expand...
Click to collapse
I wonder if the one from this thread works? link
_alexndr said:
ROM has been re-uploaded - removed "There's an internal problem with your device" popup at start (thanks to @corsicanu for the tip)
I need a dump (does anybody have a link?) or help from an experienced user who can update his phone with OTA update.zip, then make the dump (I can send detailed instruction via PM)
Click to expand...
Click to collapse
Same downlink in the first page?
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
Dirty flash will be fine?
I did, no problem.
_alexndr said:
ROM has been re-uploaded - removed "There's an internal problem with your device" popup at start (thanks to @corsicanu for the tip)
I need a dump (does anybody have a link?) or help from an experienced user who can update his phone with OTA update.zip, then make the dump (I can send detailed instruction via PM)
Click to expand...
Click to collapse
Am I assuming right that we can dirty flash the 'fixed' ROM?
Apart from that, I have another request: Could you maybe include a script into your ROMs that when I dirty flash it detects what apps I deleted from system and not restore them?
Gesendet von meinem SM-G955F mit Tapatalk
_alexndr said:
I need a dump (does anybody have a link?) or help from an experienced user who can update his phone with OTA update.zip, then make the dump (I can send detailed instruction via PM)
Click to expand...
Click to collapse
I can help, pm me the instructions...
xPr0metheus said:
Am I assuming right that we can dirty flash the 'fixed' ROM?
Apart from that, I have another request: Could you maybe include a script into your ROMs that when I dirty flash it detects what apps I deleted from system and not restore them?
Gesendet von meinem SM-G955F mit Tapatalk
Click to expand...
Click to collapse
Yes, you can dirty flash fixed rom over previous
About your request - there is the solution already included in the ROM - just extract options.prop form ROM's zip, then edit it according to your needs (add your favorite removal list to physical debloat section), then place your custom options.prop file in the root directory of /sdcard (or in external SD card if your data are encrypted). When installer will find a custom options.prop in one of mentioned locations (/sdcard or external microSD card) - it will use YOUR file instead of default file (included in ZIP)
piyushkohli97 said:
I can help, pm me the instructions...
Click to expand...
Click to collapse
Thanks Check PM
Thank u
Oem toggle is off cannot on
_alexndr said:
ROM has been re-uploaded - removed "There's an internal problem with your device" popup at start (thanks to @corsicanu for the tip)
I need a dump (does anybody have a link?) or help from an experienced user who can update his phone with OTA update.zip, then make the dump (I can send detailed instruction via PM)
Click to expand...
Click to collapse
I can help with that.
_alexndr said:
Thanks Check PM
Click to expand...
Click to collapse
Uploaded, check your PM for the link.
Thread has been updated for S8 (G950F) users
(thanks to @piyushkohli97 for the dump)
Iyaadali said:
Thank u
Oem toggle is off cannot on
Click to expand...
Click to collapse
I thought it is enough to explain it in post #1 but seems like it isn't
OEM unlock toggle will be hidden in the next release for G955F to avoid confusion (it is done already in just uploaded DevBase for G950F). Of course, it can be easy un-hidden in any time, but for what? To see it seemingly disabled? (it just displays wrong state)
Update: NFC payments has been fixed in Los 17.1 (and probably in all other ROMs) so this module is no longer required.
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
Click to expand...
Click to collapse
Havoc OS added it in the latest build (20202602) too I think in the future all ROMs will include the fix from NOS sources.
Thanks to NOS devs and to you guys! :good:
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
Click to expand...
Click to collapse
Great! But... Where is the module?
mvalda01 said:
Great! But... Where is the module?
Click to expand...
Click to collapse
Lol!
I accidentally created a duplicate thread and the attachment was in the other thread.
I've now added to the OP.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24[/QUOTE
Hai bill,
I have problem with NFC. Now iam using Havoc OS 10 v3.3 QQ2A.200305.003.
So i just flash this patch via twrp for problem solving?
I use redwolf recovery, is it possible to flash this module? And do I have to install the magisk before or can I install this module without the magisk?
Click to expand...
Click to collapse
uutucherenz said:
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24[/QUOTE
Hai bill,
I have problem with NFC. Now iam using Havoc OS 10 v3.3 QQ2A.200305.003.
So i just flash this patch via twrp for problem solving?
I use redwolf recovery, is it possible to flash this module? And do I have to install the magisk before or can I install this module without the magisk?
Click to expand...
Click to collapse
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Click to expand...
Click to collapse
Can you recommend a forum to discuss lineage on oneplus3 / 3T? And the link to download ROM Lineage OS?
Click to expand...
Click to collapse
uutucherenz said:
Can you recommend a forum to discuss lineage on oneplus3 / 3T? And the link to download ROM Lineage OS?
Click to expand...
Click to collapse
Check out the threads in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development and make sure you read the first post (OP - original post) in the thread your interested in.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Click to expand...
Click to collapse
Hai bill,
What are the steps to install this NFC patch fix? I tried to install it directly via redwolf recovery but failed, "error: 1" ...
Click to expand...
Click to collapse
uutucherenz said:
BillGoss said:
Hai bill,
What are the steps to install this NFC patch fix? I tried to install it directly via redwolf recovery but failed, "error: 1" ...
Click to expand...
Click to collapse
I've always flashed it using the TWRP mentioned in the OP of the Los 17.1 thread (aka SAR TWRP) https://forum.xda-developers.com/on...ageos-17-0-oneplus-3-3t-t3990061/post80652281
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
FWIW, definitely don't flash this on top of an LOS ROM; caused a bootloop for me that I couldn't get out of, had to clean wipe and start over. My own darn fault for not reading everything through the first time or making a backup first, just a warning for others :silly:
Click to expand...
Click to collapse
Joshmccullough said:
BillGoss said:
FWIW, definitely don't flash this on top of an LOS ROM; caused a bootloop for me that I couldn't get out of, had to clean wipe and start over. My own darn fault for not reading everything through the first time or making a backup first, just a warning for others :silly:
Click to expand...
Click to collapse
I've updated the OP to say that the module is no longer needed.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse