Fold F900F uefi shell - Samsung Galaxy Fold Questions & Answers

Samsung galaxy fold F900f uefi, and boot successfully, so far I can not connect any USB device to disable the verification of the digital signature of the driver

Hello @Ost268 I received your request to close this thread. I don't think it is necessary to close this, but in the interest of providing information to others, could you please describe what you were doing and what the solution was for your problem?

Related

[Q] Bluetooth dongle with Nexus 7 - is it possible?

I have been looking online for some time to see if there's a custom ROM for the Nexus 7 2013 , a HOW-TO guide, or an app which would allow me to use a bluetooth dongle via an OTG cable. Unfortunately I have yet to find anything.
I tried to recompile a Cyanogenmod kernel with btusb (one attempt within the kernel and the other as a module). The compile failed saying that btusb is returning an invalid pointer type.
My questions are, has anyone succeeded in doing this? I have seen posts about people discussing inserting the btusb module for other devices.
Is the Nexus 7 (2013) device unable to utilise this kernel module? Can anyone suggest what I may try or where I should look.
More details of what I've done to date are on request. I didn't want to write a long-winded post in the unlikelihood it will be answered.
Thank you.
I've (similarly) asked this question several times across a number of different fora with no response to date.
Is asking for external usb bluetooth support for a Nexus 7 (2013) a 'taboo' topic?
Sorry if I offended anyone.
The best I've managed to-date was to attempt a kernel recompile with btusb included (both in-built and as a module) but without success, ie. compilation ends in error. Is the btusb module incompatible for this architecture?

Incompatibility Samsung active watch 19d3 and xiaomi mi 10 t lite

Hello someone could help me? They continuing to lost connection. I download the plug in and set the muiu references to always on but the pairing switch off continuing.
Anyone could help me?

Bluetooth traces/logs with A3 2017

Hi All,
Could anyone please share a verified step-by-step method of tracing Bluetooth for a rooted A3 2017 running Android 8 Oreo, i.e. obtaining a trace that can be viewed in Wireshark? Variables BtSnoopLogOutput and BtSnoopFileName aren't there in /etc/bluetooth/bt_stack.conf (they were there in A3 2016 though) and adding them there doesn't make any difference.
Thanks in advance!
Looks like the "Debugging with bug reports" section here answers it:
Verifying and Debugging | Android Open Source Project
source.android.com
Note: the script (btsnooz.py) seems to be implied for use on Linux as when running on Windows it writes 0D0A instead of every 0A, causing Wireshark parsing errors.

Can't install TWRP on A5 2017 with Android 8.0.0

Hello All:
I'm new here, so please forgive me if I accidentally have bad etiquette or break any rules. Also, please forgive the length of the post - I'm trying to include as much useful info as possible.
I'm trying to install TWRP on my refurbished Samsung A5 2017 I'm following the LineageOS instructions at https://wiki.lineageos.org/devices/a5y17lte/install. The TWRP images I've tried to install can be found at https://dl.twrp.me/a5y17lte/.
When I try to install "twrp-3.5.2_9-0-a5y17lte.img", Heimdall ends with "Uploading RECOVERY 100% RECOVERY upload successful Ending session... Releasing device interface...". So everything looks good, but the progress bar on the phone never changes even after 6 hours. When I hold Volume Down and Power buttons the phone reboots into the OS that came with it.
When I try to install an older version, ("twrp-3.5.0_9-0-a5y17lte.img"), the behaviour is slightly different. Heimdall returns the same success messages, but the phone immediately reboots into the OS without me pressing any buttons.
I've done some searching on XDA and via Google and found problems that sound similar to mine, but the descriptions aren't close enough for me to be confident that they're the same problem. My searching so far makes me think that one of the software updates that occurred before I purchased the phone made it either more difficult, or impossible, to put LineageOS on the phone. I also got the impression that I might need to install an earlier official Samsung ROM before I proceed, but that safe and reliable ones are hard to find.
Here is (I hope) all the information needed for some of you wizards to figure out what I should try next:
Phone: Galaxy A5 2017
Model Number: SM-A520W
Android Version: 8.0.0
Samsung Experience version: 9.0
Branding: Telus
Baseband version: A520WVLSECTJ1
Kernel: 3.18.14-16556433-QB35318982
Android security patch level: Nov. 1 2020
Used for installing images: Linux Mint Ulyana and Heimdall via command line commands
Other possibly relevant info:
-"Secure Download : Enabled" shows on 'Downloading' screen
-Seems to be a Telus branded phone
-OEM Unlock is ON
-USB Debugging is ON
-All other switches under 'Developer Options' are OFF
-No SIM installed yet
-Phone has never been connected to WiFi or Cellular Data since I received it.
Thanks in advance for any help you can give!
jenningsthecat said:
Hello All:
I'm new here, so please forgive me if I accidentally have bad etiquette or break any rules. Also, please forgive the length of the post - I'm trying to include as much useful info as possible.
I'm trying to install TWRP on my refurbished Samsung A5 2017 I'm following the LineageOS instructions at https://wiki.lineageos.org/devices/a5y17lte/install. The TWRP images I've tried to install can be found at https://dl.twrp.me/a5y17lte/.
When I try to install "twrp-3.5.2_9-0-a5y17lte.img", Heimdall ends with "Uploading RECOVERY 100% RECOVERY upload successful Ending session... Releasing device interface...". So everything looks good, but the progress bar on the phone never changes even after 6 hours. When I hold Volume Down and Power buttons the phone reboots into the OS that came with it.
When I try to install an older version, ("twrp-3.5.0_9-0-a5y17lte.img"), the behaviour is slightly different. Heimdall returns the same success messages, but the phone immediately reboots into the OS without me pressing any buttons.
I've done some searching on XDA and via Google and found problems that sound similar to mine, but the descriptions aren't close enough for me to be confident that they're the same problem. My searching so far makes me think that one of the software updates that occurred before I purchased the phone made it either more difficult, or impossible, to put LineageOS on the phone. I also got the impression that I might need to install an earlier official Samsung ROM before I proceed, but that safe and reliable ones are hard to find.
Here is (I hope) all the information needed for some of you wizards to figure out what I should try next:
Phone: Galaxy A5 2017
Model Number: SM-A520W
Android Version: 8.0.0
Samsung Experience version: 9.0
Branding: Telus
Baseband version: A520WVLSECTJ1
Kernel: 3.18.14-16556433-QB35318982
Android security patch level: Nov. 1 2020
Used for installing images: Linux Mint Ulyana and Heimdall via command line commands
Other possibly relevant info:
-"Secure Download : Enabled" shows on 'Downloading' screen
-Seems to be a Telus branded phone
-OEM Unlock is ON
-USB Debugging is ON
-All other switches under 'Developer Options' are OFF
-No SIM installed yet
-Phone has never been connected to WiFi or Cellular Data since I received it.
Thanks in advance for any help you can give!
Click to expand...
Click to collapse
Doh! I solved the problem myself by watching a YouTube video. The LineageOS directions are correct but a bit confusing - the video clarified the procedure by showing someone doing it with phone in hand and computer connected. Case closed!
Hello Friend! I have the same problem! Could you provide the video that helped you? thankful!
Giropedal said:
Hello Friend! I have the same problem! Could you provide the video that helped you? thankful!
Click to expand...
Click to collapse
Sure! The video is here:
. There are no verbal instructions - the soundtrack is just music. As I watched the video I was pausing it and following the written instructions on the LineageOS site: https://wiki.lineageos.org/devices/a5y17lte/install. I forget what it was now that I had missed, but the combination of the video and the instructions got me sorted out. Good luck! And if you you find an earlier version of LineageOS for the A5 2017 please post it. My phone works great, but I find Oreo really annoying and I'd like to install a more sensible version.

[FIRMWARE d2s] I will do this myself /OR/ Must go to service

Hello everyone, for some time I have been looking for an answer to the question related to the removal of Root Magisk from my Samsung Galaxy Note 10+ Exynos [SM-N975F | d2s] because I would like to go back to the original software that runs Secure Folder, Samsung Health, etc ... I tried to do it according to this guide: Link but after restarting and flash the phone shows information that it was previously Rooted.
On Friday I called the samsung hotline where I got the number to the nearest service center, by calling the service I found out that they can fix it but I will have to bear the costs.
I am asking for a hint because I don't have the strength to look for it anymore, maybe I'm doing something wrong?
I install and root my phone witch this tutroial: Link
NickOne94 said:
Hello everyone, for some time I have been looking for an answer to the question related to the removal of Root Magisk from my Samsung Galaxy Note 10+ Exynos [SM-N975F | d2s] because I would like to go back to the original software that runs Secure Folder, Samsung Health, etc ... I tried to do it according to this guide: Link but after restarting and flash the phone shows information that it was previously Rooted.
On Friday I called the samsung hotline where I got the number to the nearest service center, by calling the service I found out that they can fix it but I will have to bear the costs.
I am asking for a hint because I don't have the strength to look for it anymore, maybe I'm doing something wrong?
I install and root my phone witch this tutroial: Link
Click to expand...
Click to collapse
The root is hardware fused. there is no getting back to stock. You can look up some software that can mask the previous root to start Health and some other apps, secure folder will never work again but there is a alternative.
Sorry M8
Not sure about android 11+ but on 9 i have root and secure folder working.....never tried health though. I think i remember 10 was able to get secure folder working, I'd guess 11 does or will, but can't say for sure.
This might help to get health app working
[RESTRICTIONS-REMOVED] Samsung Health Monitor - WearOS - 1.1.3.002 - Root, Age, Country & Device Restriction Removed - 19th April 2023
Hello Everyone, I hope you all are fine... ~~~ WearOS WATCHES ONLY ~~~ ~~~ FEATURES, BUGS & FUTURE WORKS~~~ FEATURES: Works on Samsung Watch4 and Watch5 (as mentioned Samsung WearOS Watches), Multilanguage, no root detection, no country...
forum.xda-developers.com

Categories

Resources