I'm using Debian GNU/Linux trixie (well, the Devuan equivalent to be exact), and am working on a Samsung SM-P900 Galaxy Note 12.2 Pro tablet. As part of possibly flashing it, I need to make sure the bootloader is unlocked. I have adb and fastboot installed. What I see is:

# adb devices
List of devices attached
5200b47af69a4247	device

# fastboot devices

so, visible with adb, not with fastboot. I found this question: https://android.stackexchange.com/questions/221634/fastboot-connection-problem which said I can't see the device at the same time with both adb and fastboot, and that I should reboot it like so:

adb reboot bootloader

but when I do that - it reboots as usual, and I still see it only with adb. I also tried the following: 1. Booted into recovery mode (using Power + Center-bottom button + Volume Up) 2. Chose "reboot to bootloader" ... that also resulted in a regular boot (showing my homescreen and apps), and device was still invisible with fastboot. What can I do to get my tablet to be fastboot-visible (so I can flash it)?

I've gotten an abandoned Samsung Galaxy Note SM-P900 tablet, which is supposed to go to charity. Unfortunately, it sports an Android 5.0.1, a lot of APKs don't install, and many websites can't be accessed by Samsung's bundled browser due to not having a valid security certificate. Can I upgrade the Android version and otherwise make the life of this device's user less miserable? I understand there are no relevant official updates, as explained here: https://android.stackexchange.com/questions/226636/how-to-upgrade-my-android-device-to-latest-android-version But I don't mind flashing this device, and obviously don't mind losing anything stored on it (I've already reset to factory settings anyway). I have a PC running Linux with adb installed, I have some USB cables, and I have a bit of time to spare. ---- Oh, I should mention a constraint: No use of any Google or Samsung account during this process.

I was asked by a friend to try to get an (abandoned?) Samsung SM-P900 tablet into working order. (This is not my device, just an illustration.) The device does not exhibit any physical damage, and only has a bit of wear on the silvery bezel. The stylus is missing though. The tablet has a (thin, wide, indented in the middle), so I'm trying to charge it with a cable from a WD Elements I have, which is USB-A on one side and USB-B Micro SuperSpeed on the other. It's been charging for a while already - but I see nothing on screen, nor a LED light up. Pressing the power button for a few seconds also does nothing. Questions: 1. Is my cable choice "legit", or should I try charging some other way? 2. Is there something else I can do, other than look for some technician, to bring the tablet back to life? 3. Can this behavior indicate battery failure, as opposed to another kind of hardware failure? 4. Is it likely that the tablet is simply full-dead and I shouldn't bother with it?

When I use a Galaxy Note together with an Apple Wireless Keyboard, pressing Shift+Space switches keyboard layout. This is really annoying. Is it possible to disable it?

I recently installed Microsoft Intune company portal on my Samsung Galaxy Note 10+ for work. Unfortunately, doing so resulted in the following change to my USB debugging settings: "Block - Prevent devices from using the USB debugging feature" . Once I discovered this, I fully uninstalled and unenrolled from the Intune company portal, however the USB debugging block remains. I did notice that I can toggle on and use USB debugging for 2-4 minutes after rebooting my phone, but after that, the switch instantly goes back to off when I try to enable it. I've tried resetting my phone settings, re-enabling developer options, and then trying to turn on USB debugging, but the setting still behaves the same. I've also tried the solutions here , but the setting remains disabled. Any help undoing what the company portal did to my phone would be massively appreciated. Note: I already disabled/uninstalled several apps potentially related to the issue via adb shell commands during the first few minutes after rebooting. If I knew which lingering app was responsible for enforcing the USB debugging block, I think uninstalling it would fix the issue. I've disabled several so far with no effect. Hoping to avoid a factory reset. Phone details/bug screen recording: https://drive.google.com/drive/folders/1uyIRKBnrpW4RH5hmlKJ2mAOMmJXt8j5d?usp=sharing

- Phone: Samsung Galaxy Note 3 (hlte) - LineageOS: 18.1-20230923-nightly-hlte-signed - Gapps: Open GApps arm 11.0-micro - Recovery: TWRP 3.7.0_9-0 The phone boots until the welcome screen. Then an error message appears, but it is shown only short, so I can't see it. It is covered immediately by a window saying „factory data reset“. Only seconds later it boots into recovery. LineageOS doesn't seem to be totally broken, as it reaches the welcome screen. But it always issues that message about doing a factory reset. What should I do next? Trying a different GApps package? Or did I miss something important? E.g. LineageOS provides a recovery for hlte, as well, but I was thinking an actual TWRP should be good as well, shouldn't it?

After water damage, my phone camera had to be replaced. The camera worked after replacement, for a day or so. Then it came up with a black screen (menus are there, just no image). A reboot fixed that for a day, but now it's back and rebooting (even to safe mode) doesn't help. It's been long enough that it's dry but I know there could be residual damage. I'd just like confirm whether it's hardware or software. Is there a log that might provide a clue? And can I view it without root?

Yesterday, I bought a Galaxy Note 10 5G smartphone that was previously used but it looks like a new one. I inspected the phone before buying it and everything was alright. However, after inserting the sim , there was a problem in the signal that was too low even though the 4 lines sometimes appear full. I tried almost every method of solving the issue after googling it like restarting the phone, resetting network settings, deeping into the safe mode and manually choosing a network operator. Yet, restarting my phone seemed to work for several seconds but the issue remained. Is there a fix to it ? Keep in mind that when I moved to the city centre, the signal improved significantly (but still not perfect). And note that my previous phone used to have a really consistent signal with the same sim card in all circulstances.

I have a Samsung Note 20 Phone and a Samsung Watch 46mm. I have it set up so that the watch vibrates if it loses connection with the phone. This happens about 4 times a day, even when I have both in my possession. I havent been bothered by it. Unfortunately, this also happens when I am sleeping. It ignores the **Do Not Disturb** and wakes me at all sorts of hours. Normally I ignore it and try to go back to sleep. I finally looked at it at 4amish. Its losing connection. I dont have any automation type software installed, so nothing should be fiddling with bluetooth. **Why would the watch lose bluetooth connection with the phone ?**

My Samsung Galaxy Note N7000 on Android 4.1.2 seems to have somehow managed to brick itself. I was using it for WiFi tethering via USB to my laptop. All was good until I unplugged it. It started restarting itself but never fully starting, so I was guessing maybe the battery was messing up. Anyways, I've come to the conclusion that it's bricked. It starts up, displays its model, and reboots before it even reaches the Samsung logo. The phone has its original firmware and has never been rooted or anything. It starts up but boot loops after displaying its model. I tried accessing the recovery menu by pressing home + volume up + power but it doesn't work. I also tried vol up + vol down + power but that doesn't work either. I'm kind of losing hope because I'm pretty certain it's hard-bricked. Somehow the OS must have gotten corrupted. It charges normally and I can turn it on but it boot loops. I tried connecting it to my laptop today via USB and it's not connecting properly, the phone just charges and doesn't connect. I really need to go on my phone because I have an important number on there.

I had P1 Turbo with 5000mah battery. It's SC-13 could 0-100 in under a hour even with wifi enabled. The charger is broken but I keep the cable. I use a third party 2.1A charger with dual ports. The weird thing is. My G7102 and Note 3 N9000 gets charged slowly with that cable compared to the original cable of Ace 2. Ampere says Samsung cable gives more than 2 times amperage. Why is that? I don't know electronics can someone explain it to me why is that?

I was browsing https://twrp.me/Devices/ wondering if TWRP is available for Samsung Galaxy Note 1 (GT-N7000, or GT-N7000B in my specific case). Only the T-Mobile (quincytmo) and AT&T (quincyatt) versions are listed there, which seems strange to me as the international version should be more common. Am I doing something wrong, or is TWRP not available for the GT-N7000? If so, what should I use instead?

Hi I am searching for the factory folder tree for Samsung Galaxy Note 1. I want the folder tree, so I can perform adb shell commands to access these directories. In a quest of recovering data. e.g. cd /sdcard/music/ QtADB hangs. On ADB cmd prompt, there's nothing happening after following command. Android commander needs root access too..

I recently purchased a *Samsung Galaxy Note GTN7000.* When connected it to Kies it shows as galaxy note SHV-E160l. I tried to flash Indian Samsung official JellyBean 4.1.2 update to it via ODIN. I have sufficient drivers (actually I went through a video tutorial). But ODIN shows fail. When I bought this device it was running JellyBean 4.1.2, but I have serious heating issues, camera problems etc. That's why I decided to install official JellyBean. But failed. How can I proceed and get it working? Model number-gt-n7000 Base band version-N7000LXKJ8 Build number -JZO54.LXKJ8.F2A238.2JIA68

I switched to a different carrier and I want to use my old Verizon Note 8 as a simple MP3 player. I did a factory reset on it and when it boots up it wants to go through a whole setup process including signing into my Google account and restoring everything. I don’t want to do this but there seems no way around it. I just want a blank phone, basically, a WiFi connection and an MP3 player (I like GMMP best) so I can have as much space for mp3 files as possible. Do I need to root the phone? Is that the best way to accomplish this? I have never rooted a phone before, so I don’t really know what that entails.

I am having issues with battery drain and not sure what to do, my note will lose about 30% battery overnight(about 7-8 hours) and last night it lost about 50%. At first it said that google app used a lot of battery so I disabled the recommended things online (it's location and such), now it isn't draining as much. Also my location doesn't use GPS, at night I always have maximum reception and yet I lose a lot of battery to cell reception, also the other 2 you can see in the picture. Hope someone can help, and thank you!

I bought on ebay a refurbish Galaxy Note N-7000. Once I received it I put my chip and for my surprise there was no signal. After checking It I noticed it has on the back of the phone N-7000 but when I see on the software it says SHV-160K. Right now, I don't know what else to do with this phone because it simply doesn't recognize any network, it just displays a NO SyMBOL where it should display the carrier signal bars. I'm posting to see if there is any way this phone can be use or IF I should ditch it. This is what It lists on the about device page Model: SHV-E160K Android Version: 4.1.2 Band Base: E160KKKJLL6 Kernel version: 3.0.31 - 10034927 se.infra@SEP-93 #1 SMP PREEMPT Fri Mar 22 12:43:28 KST 2013 Compilation: JZO54K.E160KKKJMC3

With the previous version, 4.1.2, no problem to discover and pair with my Bluetooth speakers. However, after 4.2.2 upgrade, the Note 8 cannot find them when scanning. My phone, a Galaxy S4,(version 4.3), can however discover my Note and the speakers. Note that the "multi-window" option was also greyed out after the upgrade, and only a factory reset could get it activated again. Can't find a similar question on this forum so are there any ideas before I revert to a previous version.

I have recently purchased the Samsung Galaxy Note S20 Ultra. When I'm trying to login into spotify, then it is giving a message - **Something went wrong, please try again**. I also checked from my other device, i.e, iPhone. I'm able to login from that device. I tried all the methods like clearing cache, re-installating the app and so on. But the issue still persists. What is the actual issue ? Is this issue caused due to One UI ? Please help.

Models: Samsung Galaxy Note 10.1, GT-N8013 (WiFi) and SCH-I925 (4G LTE) Android version 4.1.2 I've been experiencing problems with the overly aggressive Samsung soft keyboard popping up whenever I touch the screen to select an input field, even though I am using a Bluetooth keyboard, and only intend to use a Bluetooth keyboard with this device. Constantly having to dismiss the soft keyboard is a major hindrance to filling out complex forms. In an attempt to work around the problem, I tried installing the *Null Keyboard* app from Google Play. This works for a while, however whenever the Bluetooth connection is lost and reestablished, the Samsung soft keyboard, even though not selected as the default, pops up the following message: > Change input Method. To use Bluetooth keyboard, change input method to > Samsung QWERTY The Samsung soft keyboard then resets itself as default input method. I have tried other workarounds, such as using the *Perfect Keyboard* app and decreasing its size to the bare minimum, but unfortunately the Samsung keyboard still watches like a hawk and pops up its insipid dialog and resets itself as the default every time a Bluetooth keyboard connection is established...and then proceeds to pop itself up at the first opportunity. This is irresponsible behavior. The Samsung soft keyboard *knows* the Bluetooth keyboard is there, yet not only can't it just go away when the Bluetooth keyboard is active, it insists on resetting itself as the default input method regardless of which alternative keyboard you may have selected. Yes, I know I could root it and disable the otherwise undisableable Samsung keyboard, but unfortunately I need to be able to deal with this solution on about two dozen units in field deployment, so I pretty much need to keep things safe and simple. I'm not trying to do anything crazy - just use a Bluetooth keyboard for one of the primary reasons for which they were created - to be able to type without taking up screen real estate with a soft keyboard. ***Has anybody found a workaround for this yet?***