yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Q&A, Help & Troubleshooting] thimprfct:
hey [MENTION=9021576]pandeyshreedhar[/MENTION],

one question: are you going to update/improve this rom further, or trying further to create a lineage rom

for this device?
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
that is not my work and not my project but i can handle and do many update for that Rom after some week..

i need someone who is ready to test and provide me screenshot and then i wll add his/her name in the work...

AND

that is correct link ------->>> https://mega.nz/#!EsYR3AzL!ecmndFpZjEb3SJN1jO7GQLvDYb7f1jhRd_Ukz9Vg4mQ
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
hello Guys can you help me to develop other Roms for I8200N/Q/L

I haven't that phone for few week because of repairing that phone

I can't test the any Rom develop by me in that phone. IF someone interest to help me then message here--->

I also add his/her name in the any Rom project.... give some [MENTION=622932]credit[/MENTION] [MENTION=1349260]help[/MENTION] of his/her name in project
[Galaxy S III Mini Q&A, Help & Troubleshooting] AlphaAnimal:
1. DEODEXROM-I8200N-ROOTED

The following error occurs when flashing with Philz and or TWRP Recovery:

PhilzTouch:

--Installing: /external_sd/DEODEXROM-I8200N-ROOTED.zip
Finding update package...
Opening update package...
Installing update...
E: Error in /external_sd/DEODEXROM-I8200N-ROOTED.zip
(Status 0)
Installation aborted.
press any key to continue.
E: Unable to create brightness sys file

TWRP:

Installing '/external_sd/DEODEXROM-I8200N-ROOTED.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Error executing updater binary in zip '/external_sd/DEODEXROM-I8200N-ROOTED.zip'
Error flashing zip "/external_sd/DEODEXROM-I8200N-ROOTED.zip'
Updating partition details...

2. The Nougat Theme Stock Rom with Android 4.2.2 is the one from youtuber technicandro shree

I've tested it, but it's really annoying:

menu settings are Spanish but the rest in my mother tongue

Android 7 display in the menu is fake

Virtual buttons
[Galaxy S III Mini Q&A, Help & Troubleshooting] thimprfct:
this is a guide for the custom nougat rom, if you're interested:

I circumvented it by unpack illyrianking kernel zip, unpack philz touch recovery zip, going into odin, untick auto reboot, flash illyrianking kernel, reboot manually again into download mode, flash philz touch recovery.

boot into philz.

in philz: wipe to install a new rom

now the rom can be installed! :)

I can only confirm this working from stock to custom rom!

illyrianking kernel also makes the device faster & has more tuning options.

here are the files:

(illyrianking kernel usually also can be downloaded on androidfilehost)
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
thanks for bug i will maintain/solve that error...

or

can you also try with new twrpv3.2.7 or not???

this twrp is only flash from recovery and language is different..
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
[MENTION=227448]@thimprfc[MENTION] your method is work for this Rom or not???

If work then i will add this kernel in that Rom..
[Galaxy S III Mini Q&A, Help & Troubleshooting] thimprfct:
only for the nougat rom, unfortunately.

would be great if you add that kernel in the rom, I find it's the best.

it works for the nougat rom mentioned above & that has the same problem.

I only can confirm it working from stock to custom rom.
[Galaxy S III Mini Q&A, Help & Troubleshooting] AlphaAnimal:
I've already tried, without success.

I am 100% sure that the kernel has nothing to do with flashing a custom rom. And since you haven't tested it either, I know the result.

The Nougat Theme Stock Rom I could also start with the Baroni Kernel.
[Galaxy S III Mini Q&A, Help & Troubleshooting] thimprfct:
I will test.

---------- Post added at 11:39 AM ---------- Previous post was at 11:38 AM ----------

ok, I test it for you.
[Galaxy S III Mini Q&A, Help & Troubleshooting] thimprfct:
[MENTION=9021576]pandeyshreedhar,[/MENTION] [MENTION=7223757]AlphaAnimal[/MENTION], you were so right,

back again. I've tested it & sorry, it did not work.:(

wish I could have told you something else.

but for the nougat rom it works. right done.

but I can only confirm it from stock to custom rom, not from custom to custom rom.

will edit the posts & describe it as a method for the nougat rom.

no, it's not a kernel thing, it only helps 'a little' sometimes, because it sets the binary to custom & that can sometimes help with flashing. the whole thing is more a recovery problem, this phone has much problems with custom recovery, unfortunately.

but the illyrianking kernel is nevertheless very good imho.

it was worth a try...

now you don't have to test it & be upset.
[Galaxy S III Mini Q&A, Help & Troubleshooting] thimprfct:
[MENTION=9021576]pandeyshreedhar[/MENTION],

thank you for trying to create a bloat-free rom for this phone! :)

I haven't flashed it yet, but viewed the zip & it helped me a lot to figure out which apps & libs are bloatware, from which I never thought they were...

will the custom nougat rom, you'll create, be the same way?
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
I wll publish another link for fix rom flash error but i can'nt test that bocz of phone is in repair in progress..

So any one interset to test it or not????

First backup everything including all....
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
remove the error but not test from me..don't have phone right now..

test at your self
[Galaxy S III Mini Q&A, Help & Troubleshooting] AlphaAnimal:
Thank you very much. I'll try tomorrow and report back here.

The DEODEXROM has shrunk by 191MB. Is there a changelog for this?
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
First build Rom link have put bloated file to see all guys what is bloated in Rom so i put there

But now in second link i remove that bloated files.
[Galaxy S III Mini Q&A, Help & Troubleshooting] AlphaAnimal:
I just did.

TWRP says:

E:Error executing updater binary in zip'/external_sd/DEODEXROM-I8200-ROOTED.zip
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
Thanks for bug

I will not do anything until my phone come

And i will make a work rom after full test in my phone

So wait till....

Update soon.............
[Galaxy S III Mini Q&A, Help & Troubleshooting] Dark-Yox:
I'm still waiting for this Update tbh :rolleyes:
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
can you try this my SystemUI.apk not work. IF you try and get any error then tell me

download form page-1

goto--- https://xdaforums.com/galaxy-s3-mini/help/deodex-rooted-busy-box-zipaling-apk-rom-t3929944
[Galaxy S III Mini Q&A, Help & Troubleshooting] Dark-Yox:
Thanks, it's working now :victory:
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
Welcome....

SystemUI work or not in my phone systemui only not work...
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
[MENTION=7223757]AlphaAnimal[/MENTION]
[MENTION=7747697]thimprfct[/MENTION]

download form first page..
[Galaxy S III Mini Q&A, Help & Troubleshooting] Coldtone:
When I try to flash, I get an fail on the odn.bin
[Galaxy S III Mini Q&A, Help & Troubleshooting] Coldtone:
Trying to flash the memory and getting RQT_CLOSE!! after NAND Write Start!!. This cause it to fail
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
rom is only flash form twrp recovery only

you need to flash twrp from odin.
[Galaxy S III Mini Q&A, Help & Troubleshooting] Fearless(SP):
use twrp recovery only..
[Galaxy S III Mini Q&A, Help & Troubleshooting] Coldtone:
It fails when I try to flash twrp as well
[Huawei Mate 20 Questions & Answers] ZTNL:
I compared the sound on my older smartphone vs mate 20, but on sound quality, my htc m8 win because i installed viper4android app and sony mdr xb950bt headphones.. I need to know the steps for how get root and install this equalizer for my mate 20.

Thanks and regards.
[Fire TV Q&A, Help & Troubleshooting] TimmyP:
EDIT: Nevermind it just started working.

I swear it worked before with older versions.

I am almost positive I used to be able to select "2 speakers" in the firetv settings, which resulted in AAC being transcoded to AC3 5.1 in Kodi without any problem.

Now, those options in native firetv settings are gone. I can get it working via kodi by enabling "best match, 2.0" which forces the AAC track to be encoded to 5.1 ad then select transcoding (the options for DD arent there with any other settings in kodi)... but its choppy and slow audio. Even on lowest everything.

What happened? Did they prevent AAC->AC3? Did they get in bed with Apple? I cannot seem to get it now and it worked perfect before (when I was able to select the speaker config in firetv official settings). Now no 5.1 in AAC? Wtf?

Tell me its gone and I will have a compute stick immediately.

EDIT: Nevermind it just started working.
[General Questions and Answers] swaggdroid:
I have the S10 and in settings I turned off all Accessibility options. I want to keep all Accessibility Services turned off because I hear they slow down your phone (among other things).

But I strongly suspect that some app is still using overlays or Accessiblity Services. Is there any way to check for sure that my phone is not at all using Accessibility Services?
[Android Q&A, Help & Troubleshooting] yametekudasai:
So i notice in my developer settings this thing called 'srgb' should i turn this on? Btw my phone has ips lcd display.
[General Questions and Answers] MissLaniS:
I had an app on my phone that was used to hide photos. I used it for several years and no problems. Today I go to open the app and it was acting like it was my first time ever using it... then I look in the Private folder and its completely EMPTY. I had over 800 very important photos in there and I can not find them. I looked in google play for the app... and its gone. I even talked to Google Help people and they said the app is no longer in the app store.

So what am I supposed to do?

I looked in the phone, and I found a folder called .photosafe and another called .photosafe_DoNotDelete

i opened the donotdelete one and it has a camera folder in there, i open that folder and there is an images folder, a videos folder and 2 files. So i click on images and i believe its all my pictures but when i click on one to open it it asks what app i wanna open it with and i tried several and none work. i think they are just text files.

how can i get the pictures back? can i change the files to something so i can open them?

please help. I am completely devestaed. The p;ictures are very important to me.
[General Questions and Answers] Gvann:
.photosafe_DoNotDelete

Did you ever find a solution to this issue?

I have the same problem
[General Questions and Answers] James_Watson:
Do you remember the exact name of that app?

If yes, try to google with it for some clues.

You can also post a thread for help about that app on sub-reddits, AndroidApps.

Good luck to you.
[Upgrading, Modifying and Unlocking] Bayerberg:
2 Skins for GSPlayer

Aera - based on Aero colors

Berg - grey and classy

ps. next two on their way

hope you like it
[Upgrading, Modifying and Unlocking] neoarroyo:
Would you be able to post a WVGA version of the gray theme? Thanks.
[Magisk] BostonDan:
Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and then reapply, but this still needs to be confirmed

Without further ado, here is my process:

1) download a SQL database editor. I used

https://play.google.com/store/apps/details?id=com.tomminosoftware.sqliteeditor&hl=en_US

2) download a terminal emulator program. I used terminus but any terminal emulator should work.

3) make sure Google pay is forced close, if it is open.

4) open SQL editor. Navigate to /data/data/com.google.android.gms/databases

5) open dg.db

6) change any value that lists "attest" in the name (first column) to 0 in the third column. Mine was showing a value of 10 in the third column for each of these values. (Column c for sqlite database editor I used)

7) open the terminal emulator.

8) get root access (su)

9) cd /data/data/com.google.android.gms/databases

10) type: chmod 440 dg.db

This makes dg.db read only (for owner and group, and no access for world.)

11) reboot

I have Magisk 19.1 with GMS and Google Pay hidden. Also, I am using a custom kernel but others have reported using a stock kernel with this working.

I suspect when gms is updated, one will have to go back to steps 10 and 11 and chmod 660 dg.db to allow new keys to be written to the database, and then go back and redo all these steps to reset the attestation values back to 0.

If there is still an error, verify in sqlite database editor that all attest release keys values in dg.db are 0 when dg.db is read only (owner and group).

Again, YMMV but this worked for me, so I give it back to the community now.

Edit: people should know this by now, but GMS updates have not required any reapplication of this process.

Edit2: After much time, it was determined that all one has to do is apply the chmod 440 to dg.db before launching google pay for the first time after clearing gms data. No need to change any keys in the dg.db file. If it does not work, you may have to clear gms (Google play services) before applying chmod.

Cheers,

B.D.
[Magisk] HamsterHam:
Added my card just now. Didn't hide Google Pay etc in Magisk apart from the default GMS one.

I'll test it out later and see if I can pay

Nice one ??????
[Magisk] HorrorLemons:
Thank you! I don't have to freeze Play Store anymore! ?
[Magisk] s1mpleful:
Thank you, it works!
[Magisk] sliding_billy:
Outstanding work! Added a card and PayPal on a recently clean flashed P3XL and a P3 that had been used in the past with GPay. Now just need to try both phones at the store.
[Magisk] mando41:
[MENTION=2449699]BostonDan[/MENTION]. It works just paid using your method. Thanks
[Magisk] Freshek:
Will you mind if I add a way to automate the whole process to my GMS Toolbox app?
[Magisk] BostonDan:
Freshek,

I have no issues if you want to incorporate this into gms toolbox and appreciate you asking me.

I also appreciate your gms toolbox app as well. Thank you for your development.

Cheers,

B.D.
[Magisk] thx84:
Does your method work with the 2.88 Google Pay update?
[Magisk] Bidalos:
Man! It works! Can I donate you??????

---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------

My version is 2.88.246232551 and it works!
[Magisk] rwanek:
Looking forward for your updated tool!

Thanks!

Pixel 2 XL via Tapatalk
[Magisk] BostonDan:
No donations asked. I have gotten so much from others that this is my gift to the community!

Cheers,

B.D.
[Magisk] karnasw:
Thanks, after 3 months Google pay works again. ?
[Magisk] czoppers:
Sadly it didn't work for me, I'm kinda newbie in magisk related stuff. I suspect my ctsprofile false to be the problem here.

P.s. can someone link or explain me what is this gms toolbox app?

Wysłane z mojego LG-H870 przy użyciu Tapatalka
[Magisk] mslezak:
Thanks! How exactly did you figure this out?
[Magisk] Ramone360:
I'm stuck at step 9. When entered says not found

Can someone help?thanks
[Magisk] loadie:
cd "space" /data
[Magisk] Ramone360:
Thank you! Worked like a charm

---------- Post added at 12:05 AM ---------- Previous post was at 12:00 AM ----------

Has anyone tried this on Android Q Beta 3?
[Magisk] denzel09:
I am trying these magisk module in all the ways but the db.dg permissions are always 660. Why? i don't know what i need to do.. thanks for help

I feel like it executes too early. The script manually works but it doesn't in init.d or with magisk
[Magisk] robbalmbra:
I tried the original script on my Samsung N960F and some of the commands failed to work, give this a try and see if it works. I do believe it is working fine on my phone. But if people can test it, that would be great.

#!/system/bin/sh
# Do NOT assume where your module will be located.
# ALWAYS use $MODDIR if you need to know where this script
# and module is placed.
# This will make sure your module will still work
# if Magisk change its mount point in the future

# Tested with Samsung N960F
# Warning - I had to specify within busybox to install it to /system/xbin/ as chattr wasnt found on my device

MODDIR=${0%/*}

sqlpath=/system/bin

# Check where sqlite is
if [ -f /data/data/com.termux/files/usr/lib/sqlite3 ]
then
sqlpath=/data/data/com.termux/files/usr/lib
elif [ -f /system/xbin/sqlite3 ]
then
sqlpath=/system/xbin
fi

/system/bin/am force-stop /data/data/com.google.android.apps.walletnfcrel
/system/xbin/chattr -i /data/data/com.google.android.gms/databases/dg.db
chmod 777 /data/data/com.google.android.gms/databases/dg.db
$sqlpath/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
chmod 440 /data/data/com.google.android.gms/databases/dg.db
/system/xbin/chattr +i /data/data/com.google.android.gms/databases/dg.db

exit
[Magisk] EnoAk:
Seems to work fine. Thank you :)
[Magisk] 73sydney:
Cheers, [MENTION=4834466]robbalmbra[/MENTION] 's script is technically slightly more correct with the -f <path> testing for the sqlite file :)

Though he can drop the opening sqlpath=/system/bin as its included in his if else loop :)

It was late when i threw mine together and i should have done it that way :)

Ill change to it (edited to remove the opening sqlpath=/system/bin) and re-upload my zip

New script:

#!/system/bin/sh
# Do NOT assume where your module will be located.
# ALWAYS use $MODDIR if you need to know where this script
# and module is placed.
# This will make sure your module will still work
# if Magisk change its mount point in the future
MODDIR=${0%/*}

# Check where sqlite is
if [ -f /data/data/com.termux/files/usr/lib/sqlite3 ]
then
sqlpath=/data/data/com.termux/files/usr/lib
elif [ -f /system/xbin/sqlite3 ]
then
sqlpath=/system/xbin
fi

# On to the main show the SQL commands and database permissions
/system/bin/am force-stop /data/data/com.google.android.apps.walletnfcrel
/system/xbin/chattr -i /data/data/com.google.android.gms/databases/dg.db
chmod 777 /data/data/com.google.android.gms/databases/dg.db
$sqlpath/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
chmod 440 /data/data/com.google.android.gms/databases/dg.db
/system/xbin/chattr +i /data/data/com.google.android.gms/databases/dg.db

exit

Zip updated
[Magisk] EnoAk:
Great, maybe you could quote me or just post again once you upload the new zip
[Magisk] 73sydney:
Already done :)
[Magisk] robbalmbra:
Also this should help as I couldn't find chattr in any default folders/

if [ -f /data/data/com.termux/files/usr/bin/applets/chattr ]

then

chattrpath=/data/data/com.termux/files/usr/bin/applets

else

chattrpath=/system/xbin

fi

$chattrpath/chattr -i /data/data/com.google.android.gms/databases/dg.db

...

$chattrpath/chattr +i /data/data/com.google.android.gms/databases/dg.db
[Magisk] 73sydney:
Sometimes i just wish people would use anything than termux, like a normal person :)

We all done now, no more edits from left field ? :) :)

Updated to (and (re)uploaded)):

#!/system/bin/sh
# Do NOT assume where your module will be located.
# ALWAYS use $MODDIR if you need to know where this script
# and module is placed.
# This will make sure your module will still work
# if Magisk change its mount point in the future
MODDIR=${0%/*}

# Check where sqlite is
if [ -f /data/data/com.termux/files/usr/lib/sqlite3 ]
then
sqlpath=/data/data/com.termux/files/usr/lib
elif [ -f /system/xbin/sqlite3 ]
then
sqlpath=/system/xbin
fi

# Check where chattr is
if [ -f /data/data/com.termux/files/usr/bin/applets/chattr ]
then
chattrpath=/data/data/com.termux/files/usr/bin/applets
else
chattrpath=/system/xbin
fi

# On to the main show the SQL commands and database permissions
/system/bin/am force-stop /data/data/com.google.android.apps.walletnfcrel
$chattrpath/chattr -i /data/data/com.google.android.gms/databases/dg.db
chmod 777 /data/data/com.google.android.gms/databases/dg.db
$sqlpath/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
chmod 440 /data/data/com.google.android.gms/databases/dg.db
$chattrpath/chattr +i /data/data/com.google.android.gms/databases/dg.db

exit

Thanks to [MENTION=4834466]robbalmbra[/MENTION] for the edits/suggestions/monkeying around :)
[Magisk] denzel09:
Like written before, with this magisk module dg.db permissions are always not changed.

I realized that the script is executed too soon, in fact the same script with tasker works perfectly, the permissions are changed in read-only correctly.

So why for me in magisk it doesn't work?

---------- Post added at 10:47 PM ---------- Previous post was at 10:22 PM ----------

Are you using this script in Magisk and dg.db permissions are correctly changed in read only ( r r r )?
[Magisk] EnoAk:
Yes

r r -. But I realized the module doesn't change the "10" to "0".
[Magisk] jcmm11:
It's a timing issue. Move the script to service.d and have the first command be "sleep 30".

30 should be more than enough. You definitely need to move it out of post-fs-data.d though.
[Magisk] denzel09:
It works! Without magisk. Move the script only in service.d folder adding sleep 30 command in script. Thank you :highfive:
[Magisk] thom@s:
The Magisk module doesn't work on my Pixel 3 / unlocked / Magisk 19.2 / GPay 2.89. Already tried to uninstall + reinstall GPay. I will try the "direct script" method.

edit: with this method it worked like a charm

1. Install your favorite terminal emulator (I use Termux)

2. Enter Termux, then type "su" (Magisk might ask you for permission of root access, allow it.)

3. Enter following command line by line: (this is Titanium backup version)

am force-stop /data/data/com.google.android.apps.walletnfcrel
chmod 777 /data/data/com.google.android.gms/databases/dg.db
/data/data/com.keramidas.TitaniumBackup/files/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
chmod 444 /data/data/com.google.android.gms/databases/dg.db

4. Reboot

5. Profit!

Thank you sooooo much ?
[Magisk] Groteski:
Noob here. I really don't understand what this mean. How do you do this?
[Magisk] pbanj:
that for the one with or without killing the stuff?
[Magisk] denzel09:
From Magisk install these 2 modules: Busybox for Android and Init.d Injector

Reboot the phone

With for example Root Explorer go in /sbin/.core/img/.core/

Here you will see 2 folders, you will use the service.d folder in this case.

Now unzip the package Magisk Google Pay SQL Fix, the last one from the user [MENTION=9317193]73sydney[/MENTION] :

https://dl.dropboxusercontent.com/s/so1xtp4y3enf30m/Magisk Google Pay SQL Fix.zip

In the common folder you will found the script: post-fs-data.sh, move it on desktop, open it and add this: sleep 30

Now save it and for a better comprehension renamed it in gpay.sh and copy and past it in previoulsy wrtitten path: /sbin/.core/img/.core/service.d/gpay.sh

Give it right permissions always with root explorer for example, i simply add all execute etc.. to the end will be 0777, important that execute permissions are given.

Now save it, delete .bak and reboot. Enjoy..
[Magisk] Groteski:
Thank you so much!
[Magisk] jcmm11:
You don't need init.d injector. I'd suggest 755 rather than 777. Or even just 700. I really don't think you need to force stop anything, but it also shouldn't hurt anything if you do.
[Magisk] denzel09:
How without?
[Magisk] jcmm11:
Anything executable in service.d or post-fs-data.d will run at boot. Post-fs runs earlier in the cycle and has some timing restrictions.
[Magisk] denzel09:
Yeah, but w/o magisk module Init.d Injector i haven't those folders: post-fs-data.d and service.d

So i think all works the same.
[Magisk] jcmm11:
You should have them. Look in /data/adb

They get mapped to /sbin/.magisk/modules/.core/