yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 8 Questions & Answers] athos.dourado:
Samsung wearables app does not appear in Xiaomi mi8

Apart from the Bluetooth connection problems, the Samsung wearables app is not downloading from the Google play store displaying the message "version not compatible with this device". Guys, "ok Google" command does not work, Netflix app does not work, and now Samsung wearables app is not working either. I am putting my Mi8 for sale right now. If this is a strategy from Xiaomi, I can assure it is suicidal!
[Xiaomi Mi 8 Questions & Answers] Way Lyan:
Problem Solved - Can connect my gear S2 to my Mi 8 lite again

I have updated all three applications to latest version.

1. Galaxy wearble 2. Gear S2 plugin and 3. Samsung accessory service

I give all android permissions in the setting menu of these three apps.

And, I set the battery optimization to "no restrictions" for all three apps.

And, boom. I can now connect my phone again to my Gear S2.

My android version is 9 pie and my MIUI is 10.3.5 global and my phone is not rooted.

Welcome back my galaxy.

PS. You need to update the galaxy wearable first and then Galaxy wearable will automatically download the suitable gear s plug in for the watch.
[Xiaomi Mi 8 Questions & Answers] daffrev:
thanks for solution... its work (set the battery optimization to "no restrictions" for all three apps)

now i can use gear s3 on my Mi 9

:p:p
[Xiaomi Mi 8 Questions & Answers] barefoot_nz:
Make sure Galaxy Wearable is installed too

I have a Redmi 8 running Android 10 MIUI Global 11.0.2 and a Samsung Watch. I gave the apps all permissions but it still didn't detect from Samsung Health -> Settings -> Accessories. I think the BT actually did pair but Samsung Health did not take it further. I went into BT settings and told it to unpair.

In my case, Galaxy Wearable (used to be call Samsung Gear) is somehow missing from the Google Play Store. The Galaxy Watch Plugin is available though but after installing, it would hide so I cannot run it. The same happens with Samsung Accessories Service. Looking into Settings -> App Settings, the apps show up as installed.

I ended up extracting the Galaxy Wearable APK from my old phone (a SONY) using APK Extractor, selecting it from ES Explorer, and then sending it through Bluetooth to my Redmi 8, installing it from APK. Then I ran Galaxy Wearable and was able to pair it with the watch. I lost my downloaded watch faces in the process though. Good luck.
[Samsung Galaxy S7 Questions and Answers] Xslash:
Hello, I am from Romania.

I just upgrade my phone to the last version of firmware, 8 oreo,

PDA version is G930FXXU2ERD6, it's stable but I miss some of the old features from 7 like sleep app and info app from long press on app icon.

I would like to ask if it's possible to downgrade to version 7

PDA version G930FXXS2DRDI, but without trip knox.

I read a lot of downgrade post and it says that if it has 2 in firmware name, it means that it has bootloader version 2 and is compatible with the one from oreo.

I know how to use Odin (basic), I'm just asking if I will downgrade from 8 version to 7 version,will this trip knox?

Thanks!
[Samsung Galaxy S7 Questions and Answers] lushulean:
Downgrade is possible without tripping knox, just make sure you flash a firmware with bootloader 2 binary and perform a hard reset after
[Samsung Galaxy S7 Questions and Answers] Xslash:
Yes, I know that. The question was: if this firmware PDA version G930FXXS2DRDI has bootloader 2 binary.

Because I don't know if this firmware is safe to flash it over G930FXXU2ERD6.

Thanks!
[Samsung Galaxy S7 Questions and Answers] lushulean:
Yes, that version should work ok
[Samsung Galaxy S7 Questions and Answers] Xslash:
Thank you for the information!
[Samsung Galaxy S7 Questions and Answers] cristibuliga:
de ce nu mai pot reveni de la ultimul android 7.0 la primul 6.0???

Buna

Ce .... au blocat desteptii de la samsung de nu se mai poate reveni de la 7.0 la 6.0 ? Am un s7. Stie cineva solutia????

Multumesc

---------- Post added at 07:29 AM ---------- Previous post was at 07:25 AM ----------

I tryed many times to downgrade from 7.0 to 6.0 but odin failed. I don.t know way. Maybe because of last samsung securyty update in 01.2018.

Any advices?
[Samsung Galaxy S7 Questions and Answers] Beanvee7:
Might need to turn on OEM unlock, it shouldn't trip knox unless you flash custom software
[Samsung Galaxy S7 Questions and Answers] cristibuliga:
Tks. The knox is 1. No problem abaut that.
[Samsung Galaxy S7 Questions and Answers] maninho159:
downgrade binario 3

ola boa noite, gostaria de saber como fazer um downgrade da 8.0 para 7.0 no meu s7 g930f np binario 3, teve uma atualizaçao da fabricante e perdi o sinal de rede e queria voltar mais nao consigo porq está no binario 3 me ajudem por favor nao sei mais oq fazer.
[Galaxy Note II Q&A, Help & Troubleshooting] Shehbazahmed:
Can anyone port custom rom flyme os for gt-n7105
[Galaxy Note II Q&A, Help & Troubleshooting] Shehbazahmed:
Please respected developer kozmo1 option sir please port
[Galaxy Note II Q&A, Help & Troubleshooting] Shehbazahmed:
Regional wibsites flymeos only available gtn7100
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
[IMG="logo"]https://i.postimg.cc/RhqzTdSD/Xtnd-Rec-png.png[/IMG]

/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

Xtended Recovery is just another recovery based on TWRP source code with 2 Extra Features and aggressive Red Theme
​

Based on TWRP version: 3.4.0

Authors build: TWRP Team

Developers: HolyAngel & SuperDroidBond

Special Thanks: Red Wolf Recovery Project Team

Some differences to the official version:

- always up-to-date with the latest TWRP changes
- custom eas kernel compiled inline with the recovery
- added wipe option for Substratum or any other overlays
- added Flashlight on Lockscreen logo (Rw Recovery Project)
- added screenshot for lockscreen as well
- added Volume Up + Power for Torch

Downloads:-

Xtended Recovery

NOTES:-

[B]
1) Please do share your feedback & reports of bugs, if encountered any.
[/B]

XDA:DevDB Information

[RECOVERY][OP3 - 3T ][Stable][v3.4.0] Xtended Recovery, Kernel for the OnePlus 3

Contributors

SuperDroidBond, mady51, mukesh22584, HolyAngel

Source Code: https://github.com/SuperDroidBond/android_bootable_recovery/

Kernel Special Features: Overlays Wipe Options & Flashlight on TWRP Lockscreen

Version Information

Status: Stable

Current Stable Version: v3.4.0

Stable Release Date: 2020-07-01

Current Beta Version: v3.4.0

Beta Release Date: 2018-06-17

Created 2018-06-17

Last Updated 2020-07-01
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
Credits & Thanks

Credits & Thanks

First Thing First - A Big Thanks to Team TWRP

Second For the Legends - Team CyanogenMod / Team LineageOS

Special Thanks to the Team RedWolfRecovery Project @ATG Droid & @dadi11 for the help

1) @dianlujitao & [MENTION=1211160]HolyAngel[/MENTION] for his Device Tree of TWRP

2) @martinusbe - I used his fstab.

3) @maxwen - As we're using Omni repos for building recovery.

4) @mady51 - I have used his kernel's image.gz-dtb

Overall it's a mix effort from everyone's work. So all thanks to them.....

Kindly do let me know if I have forgot anyone. I would be happy to included your credits.
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
TWRP-X v1 Stable

Xtended Recovery Based on TeamWin Official v3.4.0.0 Sources

​

Functions

-:

1) All TWRP Functions

2) Added Delete Subs Overlay Option from RedWolf

3) Added Torch Option on Lock Icon

4) Added Torch on Vol Up + Power for Torch.

5) Now screenshot works on locked screen as well

6) Few Optimization of @HolyAngel

Sources are same as Official TeamWin & RedWolf

Best Regards

Bond
[OnePlus 3 & 3T Cross Device Development] Jigneshg:
Fantastic. Can this be replaced with Bluspark TWRP?
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
Yes it can be. Just make sure to have backup and report back if you encountered some bugs.

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] @krishne35:
Wew red and black

Lit af
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
2 days back I used this on mido and it was awesome. So thought to bring it for OP3/3T.

Btw, there's no feedback or reports from anyone. I would appreciate if everyone using this recovery can share their feedback....

For every new thing, feedback is very much necessary...

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] MarcoLK:
Flashlight isnt working
[OnePlus 3 & 3T Cross Device Development] dewa5227:
As far as i know, redwold recov have tendency bugs like flashlight broken and encryption not working.
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
Flashlight is based on Kernel so will fix it by tonight or tomorrow.

For encryption, it already have password protection which works good. So now you can set different password for recovery. Isn't it good.

BTW Thanks for reporting.

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
Release v2

Hi Brothers,

Releasing RedWolfRecovery v2 for OP3/3T -

1) Fixed Flashlight not working issue.

2) Few things adjusted to stay cool (only a bit) while flashing n all.

Link in 1st post. Let me know if there's some other bug you encounter.

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
Hey brothers,

Can anyone please confirm if there's anything that's not working other than delay in rebooting.

Also, I can see 70+ download but 1 feedback only. I would appreciate if everyone can test things and report if there's anything to do.

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] mady51:
Dont worry bro, we always release stable one. So there wont be any issues lol
[OnePlus 3 & 3T Cross Device Development] shawek:
All good here.your first build was fine,second one is also fine.for me,everything that I need from twrp is working.I flashed lots of zips with it.maybe there are some small things that I didn't notice, but for now:good:
[OnePlus 3 & 3T Cross Device Development] jamescable:
I get the led bug on Oreo ROMs...I'll reboot system...And no boot animation but the led notification lights up
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
Can you please elaborate...

Your flashing process, what all you flash, Custom ROM or OOS or based ROMs.

Without info, it's hard to solve issues.

Thanks for the report. Do point out if you found some issues that's not in 1st post. I would try getting it resolved for sure.

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] jamescable:
So, I flashed the xtended ROM, madys kernel, and magisk beta 14.6...went into ROM to see what it was, rebooted to recovery, flashed opengapps....reboot system setup the ROM, noticed magisk was NOT installed so rebooted to recovery, flashed magisk again and went to oneplus bootlogo then black screen with led lights on...I had to reboot recovery and wipe data and cache and then booted like normal

*****Also, twrp had this bug on Oreo ROMs also, bu t they ended up fixing it****
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
Problem is in your process not in any recovery. Why not flash ROM+Kernel+Gapps+Magisk at the same time. What harm it does. Also magisk has been doing good with v16.4. please update.

Try my way n let us know.

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] shawek:
Never hepended here,but I know what your talking about.

I flashed stock rom with this twrp,beta 29 I think(latest for op3t),busybox.zip,custom kernel,magisk sistemles-boot was fine,all good.

Also i tried Nos rom,Omni rom,with busybox.zip,magisk sistemles,"open gapps nano" or with "mindthegapps", lots of magisk modules( like V4A,selinux,and many more).

Maybe,just maybe,your MAGISK version is old.

Or your data is encrypted,some roms don't like encryption(like DOTos) and wont show internal storage and have problems with neverendig booting.
[OnePlus 3 & 3T Cross Device Development] android extreme:
After the recovery flash (for the first time) coming from the official TWRP tried to format data from ext4 to f2fs unsuccesfully (no encryption). Seems the same error that happens on official TWRP of 2/01. Am i missing some step or it is a bug?

Attached screenshot of the error

EDIT: found another problem(this one is more aesthetic) there is a delay of some second when you select the option "reboot system" after flashing something
[OnePlus 3 & 3T Cross Device Development] :
Wow, i just know this thread.

Thank you for making the unofficial version, sure from now on bug fixing will be blazing fast, i'll bookmark this thread.

Bugs known on the official:

- When using nougat based rom

- When trying to change the file system to f2fs

- Decrypting fail
[OnePlus 3 & 3T Cross Device Development] ZeroKool76:
You have to be there only person i know, who is actually trying to format TO f2fs and not from it ? you realize it's unstable, right?
[OnePlus 3 & 3T Cross Device Development] amuzavali:
Working good
[OnePlus 3 & 3T Cross Device Development] gFknQ:
Nicely done guys. Great to see redwolf finally brought up to date for Oreo on our device!
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
Release v3

Please v3 and check if the issues is resolved or not.

There's no issues in decryption. It's nothing about luck. It was issue in 024 and it's fixed by the team long back. f2fs was issue from my side, it's fixed as well and nougat ROM, I am sorry but can't check that. I have no intention leave Xtended even for a minute. You have to check the same yourself.

The issue for formatting is fixed. Kindly check n confirm. For the aesthetic bug you mentioned, I have already mentioned in OP. The delay is because it does a security check and from 028 onwards Team RWR will remove that check.

New Release v3

-:

Changelog

:-

1. Fixed Cache and Internal Storage formating error.

2. Used Mady's kernel to build recovery

3. Sultan thermals have been included by [MENTION=7072514]mady51[/MENTION] in the script to keep it cool. Thanks to both [MENTION=4800121]Sultanxda[/MENTION] & [MENTION=7072514]mady51[/MENTION]

RedWolf-027-OP3-3T-v3

So for everyone having f2fs issues, please try flashing v3 and confirm the same if its going smooth or not. Thanks to [MENTION=6927767]ps_minky16[/MENTION] for testing all recovery builds, wiping Internal & flashing OOS again n again.

Thanks to everyone for feedback and reports as well as for using this recovery.

We can now call it stable.

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] vishruthys:
When I used the v1 of this recovery experienced very high idle drain. Not sure if it was due to the recovery but just wanted to report.
[OnePlus 3 & 3T Cross Device Development] nihilista:
Tried this recovery, seems great but one thing: It didnt save any settings i change. I deactivated theme from stock twrp, but after every reboot i'm on english and all settings are lost....
[OnePlus 3 & 3T Cross Device Development] android extreme:
[MENTION=8829870]SuperDroidBond[/MENTION] tried , with the new recovery, to format data to f2fs and ended with the same error as before
[OnePlus 3 & 3T Cross Device Development] :
I have a feeling from those words you have some kind of anger to me, while in the first place that post is not meant for you..

So yeah, thanks for the new build... i don't have any problem with you in the first place..
[OnePlus 3 & 3T Cross Device Development] DigiGoon:
[MENTION=8829870]SuperDroidBond[/MENTION] mkfs.f2fs doesn't have any -r attrib so have to remove -r along with its value, to format the partition as f2fs.

Workaround: run that error command in terminal in recovery without the -r and it will go through. :)
[OnePlus 3 & 3T Cross Device Development] budbay:
Finally got a chance to use this, so here is my experience so far. I was in need to wipe everything for a fresh start so I decided that would be a good time to test out red wolf as well. I used red wolf to wipe all partitions, then I formated my data partition from f2fs to ext4, used mtp to load some things to storage, flashed a new ROM with magisk, everything went perfect. I haven't tried backups yet. I love that chmod 644 was added to file actions, I forgot how much I missed having that command readily available. The delay when pressing reboot gave me a small heart attack, I know it was mentioned and its not a complaint but it is a little unsettling when there are boot delays that your not used to. This is my first experience with red wolf so it looks like there are some features I need to educate myself about. Overall I would say this is a refreshing change, everything I tried worked as it should and it seems to have many features that could make this even more useful. Great work and thank you.
[OnePlus 3 & 3T Cross Device Development] jerryhou85:
Dear all,

I have to remove some off-topic posts from this development thread. Please focus on topic related to development and feedback developers with your experiences.

Stay with our rules and respect each other's opinions.

Thanks for your contribution to XDA.

Regards

Jerry

Forum Moderator
[OnePlus 3 & 3T Cross Device Development] nihilista:
Sorry for quoting myself here, but i couldn't fix that issue with non-saved settings till now.... Is it a known issue or did someone know how to fix?
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
I guess we discussed this on Telegram. So I am not saying anything here. Let's keep it secret.....:p

The only time XDA would have seen me angry is when someone disrespect any dev, irrespective of team, region, or anything else. Do not worry, I said it straight to test and I meant that only.

Yeah, But I guess it's same in all TWRP available for us. We're still working on it and will update it when it's done.

What exactly you mean by theme issue. It's already themed recovery with some extra function and most daring color combinations (Red on Black, my all time favorite).

Please do clarify what exact issue you're getting. I saved time zone, brightness, vibrations n all and everything seems working good.

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] nihilista:
I'm using stock twrp with materialized theme, so i thought it could have something to do with that. I deleted old .twrps file (seems thats the settings file), too, booted in red wolf recovery, did my settings, set language to german and rebooted recovery.....but after that all settings are at default values again. Did that 2 or 3 times, but no luck...
[OnePlus 3 & 3T Cross Device Development] nihilista:
OK, tested another time, installed red wolf, rebooted directly to recovery, did all settings, rebooted again.....and all settings are gone again. but if i click on reboot again, it didnt reboot and brings me to top screen and now my settings are there....curious...and after next reboot they are not present again. And i found another thing: If i click on recover, it brings me to top of sd folder, i can't choose one of my backups....

Did i miss something or can anybody reproduce that?
[OnePlus 3 & 3T Cross Device Development] SuperDroidBond:
As far I remember, this recovery only has 1 issue -:

Which is wiping f2fs and it's same as official one. Reboot to anything (system, recovery, bootloader) takes 5 sec to take the action as there's a check that runs in background.

I am using it personally, and so far no issues other than delay as I don't have any interest in f2fs things. I keep on flashing and testing stuffs but never faced this issue.

But as a solution I would request you to backup everything on PC. Then flash OOS once and format internal. After that flash RWR through adb and test again.

Regards

Bond
[OnePlus 3 & 3T Cross Device Development] nihilista:
Nah, i don't want to do this big procedure for an recovery, stock twrp works normally. But it will be interesting to know what could produce this issue...i didn't say it was a bug of your recovery.

As i said before, i used materialized theme with twrp, and that has some settings, too. So my first idea was that there is a problem, especially cause you use same theme base. Maybe you know where original theme saves its additional settings that are not in stock theme? As i said, first click on reboot leads me to Top screen with my settings enabled, for me it seems like some settings file that couldn't be read while starting recovery or something like that, i'm sure its nothing that needs complete wipe...
[OnePlus 3 & 3T Cross Device Development] Maxillofacial surgeon:
I am also having the same issue...... Pls help me out
[OnePlus 3 & 3T Cross Device Development] nihilista:
Did you set other than english language and/or using z31s1g's material theme before? Just to see if it has something to do with that? Encrypted data partition with password at twrp start? Maybe we could find the problem....
[OnePlus 3 & 3T Cross Device Development] Maxillofacial surgeon:
I dnt change d language preference nor did I use any theme bfor nor did I change theme...... My device is encrypted nd password at start of twrp...... Dats all but hav all d above prblm like settings not staying nd recovery folder needs to b searched etc as mentioned in earlier post by fellow xda member...... Pls help m to sort it out...... No issue while flashing etc...... Only these hiccups
[OnePlus 3 & 3T Cross Device Development] nihilista:
So it seems i'm not the only one with this...
[OnePlus 3 & 3T Cross Device Development] osrox:
Hi,

the official twrp on my OnePlus 3, running RR rom, is having some problem.

it fails to recognize the "encryption password", (i think this happened because, i dirty flashed open beta 37 firmware+modem, during last dirty flash of RR rom update).

so i cannot access the memory & flash rom updates.

if i boot phone normally, the encryption password works fine.

i still have magisk root on my phone, so i can flash other recovery using Flashify app,

& i tried flashing bluespark recovery, but it too did not accept the encryption password.

if "Red wolf recovery" is more advanced than official twrp, will flashing this help, or is there a chance, it might brick my phone ?

****************************

Update...

**********

SOLVED

**********

A huge Thanks to the RedWolf Recovery team [MENTION=8829870]SuperDroidBond[/MENTION] [MENTION=8393345]ATG Droid[/MENTION] [MENTION=3792100]dadi11[/MENTION]

Yesterday, i had been locked out of my phone as well, when i changed lockscreen lock from PIN to Password.

which meant, that i lost access to my phone too.

so i tried fastboot flash multiple recoveries (OOS/twrp official/bluespark),

& when i had lost all hope.

I tried Red Wolf recovery.

it accepted my encryption password.

so now i finally got access to phone memory through recovery.

i flashed OOS Firmware 5.0.3, then latest RR rom build, & deleted lockscreen.db from /data/system.

Reboot to system.

Entered Encryption Password.

My Phone now booted to system without lockscreen lock.
[OnePlus 3 & 3T Cross Device Development] nihilista:
For the problem with backups that are not found i found whats going on: This recovery uses a folder called "WOLF" for that, should'nt that be mentioned in changelog or feature list?

But settings are not saved even with existent "WOLF" folder, torch seems not to work. And interesting thing, if i reboot to recovery, settings are lost, but if i tick "/reboot/theme, all settings are there.... Didn't find a possibility to get to terminal output, so i don't know if i could help, but this nasty bug holds me from using redwolf for now....

Thx