yashsingh1/xdaforums huggingface dataset:
[LG V30 Questions & Answers] TPMJB:
Hey all,

So I read these forums for a bit, and I saw that the LG V30 can do "fast wireless charging" with a 15W wireless charging dock. Immediately I bought this bad boy:

https://www.amazon.com/gp/product/B07HD38582/ref=oh_aui_detailpage_o04_s01?ie=UTF8&psc=1

And it doesn't seem to work. It will blink red, then blue, charge for about a second, and then blink red again. Doesn't seem to matter if it's my case or not.

I'm on the Pixel Dust rom, using the latest vendor from LOS 15.1.

Any way I could test this?
[LG V30 Questions & Answers] zacharias.maladroit:
It works fine on LG Stock ROMs for you, right ?
[LG V30 Questions & Answers] TPMJB:
I found out the problem was a ****ty product. I plugged it into my wall adapter and usb cable and it worked just fine, though much slower than they were advertising.

Does anyone have any measurements in Accubattery for a "15W" wireless charge?

Edit: After reading these forums for about an hour, I've come across the truth to wireless charging on this device:

-This phone is capable of 15w wireless charging, however it heats up too much and instantly throttles to 5w (or lower)

-The Anker Powerwave has a max of 10w, but with the internal fan actually charges faster than "15W" chargers

Truly weird. Anyway, anyone searching, that's the truth as of 21NOV2018
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] mangurian:
I want to be sure all my data and passwords are gone gone gone.

Thanks,
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] jeffrey268:
Go into settings and search for backup and restore.
[Honor 8X Questions & Answers] Mikey_AK:
OK I know this issue has been seen before, let's figure out what's wrong.

I have an Honor 8X Max from China, model is ARE-AL00, was running 8.2. I unlocked the bootloader from https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below, then installed TWRP from https://www.filehosting.org/file/details/764535/twrp-kirin.img according to THIS guide: https://xdaforums.com/honor-8x/how-to/guide-how-to-unlock-root-honor-8x-t3864348.

I AM AWARE that this version of TWRP was designed for Honor 8X and not 8X Max.

Phone worked fine but wouldn't flash Magisk or Supersu, gave me lots of red "Failed to mount" messages. Today the phone decided it was time for a firmware update and now it only boots into TWRP. If I go to Factory Reset from TWRP, I get the same "Failed to mount" errors.

I would like to get a global/English ROM, or even some kind of custom ROM working on here, if that is possible, but for the time being I am comfortable settling for just having the phone working again. Willing to wipe if necessary. Any help is appreciated. Thanks!
[Honor 8X Questions & Answers] Mikey_AK:
It seems Huawei e-recovery came to the rescue and the device is working properly now... My data wasn't wiped, but I think TWRP is gone. Still, does anybody know what's going on with the "Failure to mount?" That seems to be the primary barrier for getting my phone rooted.
[Honor 8X Questions & Answers] hopkins31:
If you find out how to get this to work keep me posted I got the china 8x max with unlocked bootloader,did you try to manually mount system in settings?Also maybe it's pointing to the wrong mount route
[Honor 8X Questions & Answers] Mikey_AK:
I think if you install TWRP and try some of these diagnoses yourself you will probably make more progress than I, that being said, if and when I decide to install TWRP and try again I will let you know if I make any progress.

Nice to see someone else with the same model. I didn't have a clue what I was getting, I just wanted to a cheap phone with nice hardware.
[Honor 8X Questions & Answers] sithi.w:
I believe the problem is that the TWRP does not correspond to your device. Honor 8X uses Kirin chipset, whereas your Honor 8X max uses Snapdragon 636 (or 660 for the latest 6 GB RAM model). I understand that this is why it couldn't flash Magisk or Supersu. (I think it's lucky that you hadn't soft-bricked your device)

Regards
[OnePlus 6 Guides, News, & Discussion] Toni Moon:
This Dolby magisk mod works perfect in OOS 9.02, Thanks Repey6

[MM-P][6.0-9.0][Magisk]Dolby-ARISE-20181119 by repey6

https://androidfilehost.com/?fid=11410963190603854675

Original thread:

https://xdaforums.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
[OnePlus 6 Guides, News, & Discussion] mdl054:
Can confirm also working on latest Havoc release
[OnePlus 6 Guides, News, & Discussion] maaakn:
Its working!!!! Finally

:))
[OnePlus 6 Guides, News, & Discussion] klym.software:
just flash the zip in twrp?
[OnePlus 6 Guides, News, & Discussion] mdl054:
Actually, from the origional thread there are two versions. The first is a TWRP install yes, but the second and preferred method is the Magisk zip. The link OP referenced is the Magisk zip. Flash through Magisk directly. Before doing so, go into that thread and download the uninstaller just in case something goes wrong you can flash the uninstaller through TWRP and get back up and running.
[OnePlus 6 Guides, News, & Discussion] Toni Moon:
The working version it's the magisk mod, flash it from magisk or you can flash from twrp if you have magisk installed
[OnePlus 6 Guides, News, & Discussion] null0seven:
Works Fine on 6T port to oneplus 6 rom. Thank you.

The speaker of the phone sound Better ! Sound it's clean, natural, with some bass. Not only the high's like before.
[Touch Cruise General] akira28hk:
Check this registry in ur phone, if it is lower than 7 try change it to 7

HKey_Current_User\ControlPanel\SoundCategories\Ring\InitVol

The value of above registry was 2 in my friend's HTC Touch Cruise, I changed it to 7 and it make a big different, hope this help.
[Touch Cruise General] Space Aware:
Please excuse my ignorance... How do I get to HKey_Current...ect...ect...

Thanx
[Touch Cruise General] TheDisneyMagic:
You need to install a free piece of software called Total Commander.

That will give you access to the registry.
[Touch Cruise General] Space Aware:
Thanx...Anychance of a link?...Is that allowed in here?...Googled it downloaded like 3 versions...all are incompatible with my polaris orbit 2... ;)
[Touch Cruise General] ovidiaconescu:
This is the latest version (Total Commander CE/Pocket 2.5 public beta 3)

http://ghisler.fileburst.com/cebeta3/tcmdpocket25_armpubbeta3.exe

I'm running it for a while now and i had no problems with it.

If you want to go with the official release, get it form: http://ghisler.com/pocketpc.htm

In case you don't know by know, your Polaris processor is (ARM/XSCALE/PXA)
[Touch Cruise General] Carty:
What if you enter values over 7 ?
[Touch Cruise General] master athlon:
nice

nice tweak, thanks :)
[Touch Cruise General] sultanofsumar:
didn't do anything for me.
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Mod Edit: closed per OP request

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

:cool:

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 AppLock (yet)

- No Xposed (we need to wait for rovo89)

S9 (SM-G960F/DS/FD):

S9+ (SM-G965F/DS/FD):

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)

Known issues:

- [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 (re)install Magisk Manager as normall app - use ATTACHMENT (it is original apk from Magisk v17.3)

- 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.

Thanks to:

- all users mentioned in my main thread

- @ASHLEY117 for G960F dumps

- @geiti94 who first provided me update.zip and dump for G965F

- @SoLdieR9312 for ZRKA update.zip for G960F containing BL/CP
[Samsung Galaxy S9 & S9+ Cross Device Development] exocetdj:
I know nothing

Got no stones lol

Great work to you as well! ??
[Samsung Galaxy S9 & S9+ Cross Device Development] bobandar:
Just flashed the rom , clean install. Does not let me finish the setup screen because it is stating that a file has been removed ( regarding security or health ) in an unauthorized way . Not able to access anything after the setup screen only an option of emergency call is available.
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
No problem here (according to screenshots), but I have an idea... Please place attached options.prop file (decompress zip first) in the root directory of /sdcard or /external_sd and then try again

EDIT: Attachment removed! Please try updated ROM (r2) available in post #1. Please remove previously shared options.prop from /sdcard (/data/media/0) and/or from /external_sd before you try v.5.9_r2 !!!
[Samsung Galaxy S9 & S9+ Cross Device Development] bobandar:
Will surely do and let you know.
[Samsung Galaxy S9 & S9+ Cross Device Development] bobandar:
This is what I had got earlier. Will try flashing now with the solution you gave.
[Samsung Galaxy S9 & S9+ Cross Device Development] bobandar:
nah mate, still getting the same problem
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Still wondering how it is possible that for me it works...:confused:

Is there a person who managed it to work after clean install?
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Thread has been updated. If you used options.prop file from post #4 - please remove it from /sdcard (/data/media/0) and/or from /external_sd before you try v.5.9_r2 !!!
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Dirty flash. Working fine.
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
Which rom?
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Coming from 5.9 j8 g965f

Samsung thems not working
[Samsung Galaxy S9 & S9+ Cross Device Development] gitlygit:
They won't yet as its a Beta ROM. Stuff like that will be sorted out of Beta.
[Samsung Galaxy S9 & S9+ Cross Device Development] maglise:
Hi,

I use ledcover, is it working with the beta ?

Thank you for your work.

Maglisr
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Gallery dose not present the photos from camera on sd card.
[Samsung Galaxy S9 & S9+ Cross Device Development] exocetdj:
Again, known bug in Samsung software. I'm running stock beta and have this problem
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Due to the fact that I am still reading here and there with a high risk of FRP/RMM lock in Pie, the precise circumstances of which are still unknown - I have decided to upload v5.9_r3 which still contains Pie modem but

does NOT contain Pie BL anymore

.

Precise circumstances of FRP/RMM lock in Pie are unknown, but I believe that probability will be significantly reduced with Oreo BL (at least for those people who never flashed Pie BL yet) especially, that Pie beta seems to work well with Oreo bootloader & Pie modem.

Advice for those who have Pie bootloader already -

DON'T mess with it - let it be still Pie

!!! Also - I would NOT recommend you to jump beetween Pie -> Oreo if it is not absolutely necessary! After several attempts of restoring Oreo ROM & BL, which passed successfully, then updating again to Pie ROM & BL, then restoring again... -

unexpectedly, the problem has become to me

(my device is RMM locked - I lost OEM unlock toggle for 7 days, I hope...) :(

At the moment we can confirm only

2 scenarios which should end without problems

:

- Dirty flash Pie DevBase over Oreo DevBase (thanks to [MENTION=4616813]mevorach[/MENTION] for the try & report), but I would highly recommend you to set default (stock) theme and default (stock) icons before you try

- Clean flash (tested personally) but only if you never jumped beetween Pie -> Oreo in the past (no matter if it was clean downgrade or restoring Oreo backup)

IMO you should also assume

following scenarios as risky

:

- Jumping from Pie DevBase ROM -> SoLdieR9312's Pie ROM

- Jumping from SoLdieR9312's Pie ROM -> Pie DevBase ROM

EDIT: Vaultkeeper service has been removed from the kernel (starting from v5.9_r4). Should be more safe now, despite BL/CP are flashed again :)
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
So you don't suggest to switch over from SoLdieR9312's Pie ROM v1.1 to yours(dirty flash) & sdcard problem fixed v r3? I am on at

SoLdieR9312's Pie ROM v1.1.
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Nothing has been changed in sdcard support comparing to stock beta - such kind of issues should be solved by Samsung.

IMHO if you are still on Oreo BL (never flashed Pie bootloader in the meantime) and never jumped Pie -> Oreo then should be OK after flashing r3 (r3 also does not contain Pie BL)

Please let us know if you decide to try :)
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Flashing your 5.9 r2 , from oreo(j8) did not include the pie BL ?
[Samsung Galaxy S9 & S9+ Cross Device Development] WalterSilverio:
I own a galaxy s9, I am willing to get the files you need so that I can compile the version for G960F and other variants exynos, please tell me what I have to do.
[Samsung Galaxy S9 & S9+ Cross Device Development] Andrw0830:
Yeah I was wondering about this too? Can't we use the S9 untouched files that [MENTION=4860093]SoLdieR9312[/MENTION] provided in his thread? Hope I am not breaking the rules as I know this is [MENTION=5150393]_alexndr[/MENTION] thread, just wanted to point out to hopefully make it easy for everyone.
[Samsung Galaxy S9 & S9+ Cross Device Development] Juanig:
It's possible to fix sd problems (gallery and other apps) by forcing adoptable storage but please, read before about it.
[Samsung Galaxy S9 & S9+ Cross Device Development] aussiesausage:
Are you aware of what exactly that is and why not many people like to use adoptable storage?
[Samsung Galaxy S9 & S9+ Cross Device Development] Juanig:
You're right, I'll edit my post.
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
R2 contained Pie BL, r2 has been created before prenormal happened to me. But things seems not look as bad as I though. I have justified supposition that my problem is due to flashing official update.zip over stock rom (to make dumps) in combination with jumping between BL versions. However - my next beta ROMs will still not contain Pie BL (just in case)

Don't be scared to much :) there is a workaround for it - I just "solved" my problem but I'm stuck at Oreo BL

I will PM you with some warnings related to making Pie dumps, then you will decide if you are brave enough ;)

In my ROM concept I need S9 system dump, not just S9 files from another ROM (of course, I agree that in theory it would be possible to use S9+ system dump then replace necessary content, but I prefer original dump to avoid potential mistakes)

BTW. At the moment, if somebody need a quick workaround for SafetyNet - use SafetyPatch v2 module. In the next release I will include much better workaround into the ROM (SafetyPatch will not be necessary anymore) - thanks to [MENTION=4860093]SoLdieR9312[/MENTION] for the tip
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Thread has been updated :cool:

Changes in v5.9_r4 (comparing to v5.9_r3):

- removed supersu scenario - does not work in Pie

- removed vaultkeeperd service from the init.rc in the kernel's ramdisk

- BL/CP packages are flashed again - it should be safe at the moment

- changed ro.build.fingerprint and ro.bootimage.build.fingerprint to pass SafetyNet in beta FW (SafetyPatch v2 is not needed anymore)

Download link and other important info - see post #1

EDIT: Info for those who can't live without data encryption - it WORKS in Pie DevBase (just tested personally) :cool:
[Samsung Galaxy S9 & S9+ Cross Device Development] CynicalHeight00:
[MENTION=5150393]_alexndr[/MENTION]

Is it possible that I can have 2 roms(Your oreo rom and pie rom) in twrp? On the snapdragon s8+ twrp, I remember having the ability to have rom slots, but I cannot find in the s9+ exynos twrp.
[Samsung Galaxy S9 & S9+ Cross Device Development] sabresfan:
Safestrap or dual boot patcher is currently not available on the S9 or S9+.
[Samsung Galaxy S9 & S9+ Cross Device Development] shadowsami4:
Hi ! our n9 are not on pie ... Maybe with a pie exynos s9 rom we can do something for n960f ? any ideas ? can we modify this rom to use it on n9 ? thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
Changes in v5.9_r4 (comparing to v5.9_r3)

Install today & everything is working properly thank for your rom:D
[Samsung Galaxy S9 & S9+ Cross Device Development] zidane02:
Will Dual Sim + SD mod work when I dirty flash this over my current devbase oreo? TIA.
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
Use terminal emulator from play store

and write command

su

sm set-force-adoptable true

reboot

That's it you get working sd card.:D
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
No, it will not work. New modified Pie services.jar is needed.

It is known problem... The solution is described here:

https://xdaforums.com/showpost.php?p=78177346&postcount=2

Unfortunately, I have removed "noroot" scenario in v5.9_r4, but since it may be necessary to solve SdCard problem - I will put it again in the next release

It is not good solution, it is only a workaround ...

EDIT: After several tests I would recommend this solution :) It in fact doesn't enable adoptable storage but just activate dialog box so user can still choose "Mobile Storage" - it somehow solves problem - external sdcard still can be removed without issues despite information in this article:

https://www.androidcentral.com/adoptable-storage
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
Unfortunately, I have removed "noroot" scenario in v5.9_r4, but since it seems to be necessary to solve SdCard problem - I will put it again in the next release

It is not good solution, it is only a workaround ...

Please read disscussion #23-25:

https://xdaforums.com/showthread.php?p=78236308&postcount=23

...and here:

https://www.androidcentral.com/adoptable-storage[/QUOTE]

Yes I know but due to no root option in rom so it's working for me. Intelligent scan is not working fast can you solve this for faster unlock.:D
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
I must admit that it's a better (more convenient) solution and I would recommend it - especially if you dirty flashed Pie DevBase over Oreo DevBase.

It in fact doesn't enable adoptable storage but just activate dialog box so user can still choose "Mobile Storage" - it somehow solves problem - external sdcard still can be removed without issues despite info in linked article.

Just edited my previous post (#36) :)

NOTE: If you will see "Configure" option after opening SD Card Notifcation - it is important to choose "Mobile Storage"
[Samsung Galaxy S9 & S9+ Cross Device Development] PUMA007:
After flashing rom i lost SCS Contry code , i flash stock rom back but also is not SEE/SEE,SEE/XSG now i have only SEE/SEE,SEE ,how i cen back agein the Contry Code ?
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Info in the last position is only cosmetic/informational thing added by Samung to bootloader and it shows market the phone has been originally designated for - in your case it was XSG (United Arab Emirates). This value is never taken into account, it is only displayed in case of never rooted device (KNOX 0x0), nothing more...

So first of all - it is not an "issue" but cosmetic thing. As a proof - lack of info about original market does not even break OTA updates if you flash back stock ROM :)

Second - this "cosmetic thing" is not even specific to this ROM - it is common for (probably) all custom ROMs available here, where we are using TWRP to update firmware instead of Odin. Please read this disscussion:

https://xdaforums.com/galaxy-note-8/help/missing-product-code-t3855242
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
[MENTION=5150393]_alexndr[/MENTION]

Beta2 is out wait for new rom:D
[Samsung Galaxy S9 & S9+ Cross Device Development] ndahiya:
What about tmobile usa support? With the oreo debate, I had to always use Detonator to enable wifi calling. Since Detonator is not available for pie, not sure what solution might be available...

Thanks for all the good work!
[Samsung Galaxy S9 & S9+ Cross Device Development] MadSilence:
Does this ROM work with all banking apps and citrix secure hub etc?=)=)=) I want PIE samsung but "legal" in terms of being able to install all daily apps=)
[Samsung Galaxy S9 & S9+ Cross Device Development] hochocnua:
Hi [MENTION=5150393]_alexndr[/MENTION]

Do you have a plan to update G965FXXU2ZRKA_DevBase v5.9 to ZRKL ?

Here the link OTA G965F-ZRKA-ZRKL-OTA.zip

https://androidfilehost.com/?fid=11410963190603862630

G965F-ZRKL-ZRKN-OTA.zip

https://androidfilehost.com/?fid=11410963190603862738
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
I'm not able to test all apps in the world, but this ROM pass SafetyNet. My Banking app and Google Pay works

Work in progress since 2 days...

I'm working on something more than just re-based ROM (installer will be designated as v6.x) :cool:
[Samsung Galaxy S9 & S9+ Cross Device Development] MadSilence:
Oh? Can it be run without root? Or do you need magisk? Is knox present? I have the "luxury" of needing rmm via citrix and Pogo and bank id. ?? Just to make it difficult...
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
Work in progress since 2 days...

I'm working on something more than just re-based ROM (installer will be designated as v6.x)

Waiting patiently :D
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Thread has been updated - I present you DevBase v6.0 (Release Candidate #6) :cool:

CHANGELOG (recent changes):

v6.0

(starting from G96xFXXU2ZRKN DevBase):

- Introduced logging entire installation process (to devbase_install.log file, placed in /data or /cache in case of encrypted devices). These logs may significantly increase the possibility of my help in case of problems with/after installation

- Major imrovements/bugfixes/optimizations related to Android Pie support (e.g. takes care about special SELinux contexts for /odm content, introduced in Pie)

- Removed SuperSU support. Changed allowed "root" variable value in options.prop to true/false (backward compatible with old options.prop)

- Starting from RC8 bootloader will not be updated anymore by the DevBase ROM installer (it need to be flashed separately if necessary). Baseband/modem will be still updated as it is much more important. Please read also THIS POST

OTHER IMPROVEMENTS:

- External SD Card works "out of the box" with Magisk root scenario (tested with clean install) - it is enough to tap "configure" @ notifications panel etc..
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Thread has been updated for S9 (G960F) users :cool:

Big thanks to [MENTION=4128352]ASHLEY117[/MENTION] for G960F dumps :good:

Since nobody was able to dump ZRKN OTA update.zip for G960F - this ROM contains slightly older (ZRKA) bootloader, but I haven't noticed any issues related to using older bootloader in Pie ROM (ZRKN ROM works well even with BRJ6 Oreo bootloader)

EDIT: ROM for G960F has been re-uploaded with ZRKN bootloader