With TWRP, on almost every operation I get > Failed to mount '/preload' (Invalid argument) My device currently can not boot, and this may have something to do with it, /preload is currently in /etc/fstab, I can see the entry here with /dev/block/mmcblk0p16 /preload ext4 rw 0 0 When I try to mount it, I get mount preload/ mount: mounting /dev/block/mmcblk0p16 on /preload failed: Invalid argument Is there anyway to fix this problem? From my recovery.log, I have /preload | /dev/block/mmcblk0p16 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB Flags: Can_Be_Mounted Can_Be_Wiped IsPresent Primary_Block_Device: /dev/block/mmcblk0p16 Display_Name: preload Storage_Name: preload Backup_Path: /preload Backup_Name: preload Backup_Display_Name: preload Storage_Path: /preload Current_File_System: ext4 Fstab_File_System: ext4 Backup_Method: files I'm trying to flash LineageOS, but I'm really just curious about resolving this error message.

Can the Samsung Galaxy Note 10 do video over USB-C to HDMI? I called one of the companies that makes a USB-C hub with HDMI, and they said no. They said my phone does not support DisplayPort Alt Mode, but [the Samsung website](https://www.samsung.com/uk/support/mobile-devices/i-smashed-my-screen-and-cannot-use-the-touchscreen-is-there-any-way-to-access-my-data/) shows an adapter like that. I talked to Samsung reps, and they gave me a wide array of answers. From "yes", to "no", to "yours was an earlier model and only the new 10s support it", then back to "yes and no". Even got "it depends on your monitor". So I was hoping someone here has a real answer How can I display my Note 10 on a monitor or TV? My Note 10 screen is broken, so I can't make any changes on the phone.

When inputing otg cable it does not switch to the selected deviceId using getUserMedia on mobile browsers. It keeps using the default speakerphone on samsung galaxy note8 and note 10. I am using secure connections https and the browser version: Desktop browser Chrome: Version 114.0.5735.198 (works) Mobile browser Chrome: version 126.0.6478.188 (does not work) I set up something that processes live surrounding audio (picked up by the microphone) and is replayed almost in real time from the phone's speakers. However, this is producing feedback as the phone's microphone picks up the sounds that are just produced by the phone's speakers. tried buying a new cable for connecting microphone, still does not switch. tried using headphones and the same thing happend. I am using MediaDevices: getUserMedia() method. code: https://stackoverflow.com/questions/78797554/how-to-make-navigator-mediadevices-getusermedia-audio-true-work-on-mobile

I haven't yet come across a situation where factory reset didn't resolve the issue. This one is very intriguing to me as I could not conclude why the phone could stay in the partial flight mode (faded blue). It may be a coincidence, but it happened sometime after the firmware update. However, it doesn't look like a widespread issue to assume it is a bug. I have attached an image that shows flight mode in faded blue. It stays that way until I switch to Wi-Fi calling or remove the SIM card from the tray. I cannot select networks from the settings - "Error while searching for networks." Here are the steps I have taken so far: 1. Wipe cache partition 2. Clear SIM cache, grant permissions, network rest, restart device 3. Multiple resets with flight mode on and off, finally did a Factory rest 4. Used ODIN flashed with latest stock ROM 5. Used ODIN flashed with a year-old ROM - system performed updates as well 6. Used ADB shell to enable cell in airplane mode, no impact. ADB mode shows flight mode was off. 7. Replaced with new SIM card, no difference Based on the above steps, it looks like this is probably a hardware issue, but I would be relieved if it comes from experts. No drops or physical damages to the phone. I haven't read anywhere that partial flight mode results from hardware failure. However, neither ADB made any difference to conclude it as a software/GUI issue. If there aren't solutions left, I can make peace with my phone. I would appreciate your comments and inputs.

A little background on me: I'm a professional cartoonist and have been working digital for about 20 years. I've had numerous Wacom devices & currently enjoy a Cintiq 21UX (older model). I also have the ASUS EP121 Slate. I think I understand Wacoms pretty well and generally don't panic about computer stuff. The Samsung Note 10.1 S Pen is using Wacom's *penabled* tech. Same kind of hardware in the ASUS EP 121. With every Wacom device I've used to date, either Mac or Windows, there is a control panel dialogue box that allows you to tweak the pressure settings of the pen so that the artist/user has the best control for them. The S Pen does not have this and I want it! :) I have called Wacom. They said they provided the hardware but do not provide support for it. I called Samsung who said it was an Android operating system issue. Before I begin another round of waiting on hold hoping for Android support I thought I'd try here. Any assistance or at least firm Android tech suppport numbers I could call would be much appreciated. I realize the Note 10.1 is brand new tech and a proper driver solution may be a few updates away but I am willing to be a squeaky wheel and/or early adopter to help this happen :)

My note 10 screen does not display anything. So I cannot see any note 10 pop up prompts. In windows 10 settings bluetooth and other devices. When I connect my note 9 it gives the name of my phone that I choose. When I connect my note 10 it says samsung android. When I turn off my note 9 and connect it does not say anything. Based on this I can assume my note 10 is on. But why does my pc not show real name of my note 10? Why generic?

My Note 10 screen no longer works. When I connected it to my laptop it asked me to install Dex and I did that. But nothing happens. Smart switch says connect the device but when I do nothing happens. Do I need to approve on my note 10? I can't see the screen so how do I get dex or smart switch or anything to get the files out of the note 10

My Samsung Note 10 went green lines and now it does not turn on. But sometimes when I connect power supply it vibrates. When put on the wirless pad it also vibrates. The phone not the pad. How can I backup the device? Tried connecting to computer it did not pick up the note 10. How can I backup? Can I remove memory from it and plug it in to something elae? I need my old texts and data. Please help? Any good method helps. Thanks!

I am following [this guide from Cyanogenmods](http://www.cyanogenmods.org/forums/topic/install-twrp-recovery-android-using-fastboot/) to install TWRP on a Samsung Note 10.1 with Android 5.1.1 installed. I have activated *USB Debugging* in *Developer options* and connected the tablet to my computer, accepting the connection in the dialogue that pops up in the tablet. I then issue the adb command: $ adb reboot bootloader There is no error message, either on the computer or the tablet, and the tablet reboots. I then issue the *flash* command: $ fastboot flash twrp-3.0.2-0-lt03wifiue.img And nothing else happens. The tablet remains silent and the command line in my computer is stuck. How do I move on from here? **Update I**: This is the system and software in my computer: $ uname -a Linux ENG-PAVIL-PC2 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ apt policy adb adb: Installed: (none) Candidate: 1:6.0.1+r16-3 Version table: 1:6.0.1+r16-3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ apt policy fastboot fastboot: Installed: (none) Candidate: 1:6.0.1+r16-3 Version table: 1:6.0.1+r16-3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages **Update II**: The bootloader version on this tablet is: P600XXUDQA1 **Update III**: heimdall was referenced below as an alternative to fastboot, but it is not able to communicate with the Samsung Note 10.1: $ heimdall flash --no-reboot --RECOVERY twrp-3.0.2-0-lt03wifiue.img Heimdall v1.4.1 Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au/ This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: http://www.glassechidna.com.au/donate/ Initialising connection... Detecting device... ERROR: Failed to detect compatible download-mode device. $ adb devices List of devices attached 4300ee259691c037 device **Update IV**: Still trying it out with heimdall, which so far is the only tool providing any bit of hope. For some reason it sometimes fails to identify Download mode - that is the reason for the error messages in Update III. By plugging in/out the USB cable and using the detect option one can eventually make sure it acquired the device: $ heimdall detect Device detected Then the flash command succeeds: $ heimdall flash --no-reboot --RECOVERY twrp-3.0.2-0-lt03wifiue.img Heimdall v1.4.1 Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au/ This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: http://www.glassechidna.com.au/donate/ Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... Protocol initialisation successful. Beginning session... Some devices may take up to 2 minutes to respond. Please be patient! Session begun. Downloading device's PIT file... PIT file download successful. Uploading RECOVERY 100% RECOVERY upload successful Ending session... Releasing device interface... Now things get tricky. If the tablet is rebooted normally after TWRP is flashed, the stock bootloader (I believe) will replace it automatically. In this case when the tablet is rebooted into recovery mode it will just run the stock Android recovery programme. It took me a while to figure this one out... After flashing TWRP, the tablet must be rebooted directly into recovery mode. The problem is, it shows an error in the booting screen: > Could not do normal boot. Invalid KERNEL LENGTH! TWRP does not load and the tablet just shuts down. That is how far I am right now.

I have a new Samsung Galaxy Note 10.1. I recently bought it online. It was working fine, but now the tablet is not charging and keeps giving the error 'battery temperature low'. I tried charging it by switching the tablet off, but then it gives a yellow error sign.

My tablet is stuck booting. I can't get it into recovery. When I hold Power+VolumeUp it goes into "Custom OS ..." with exclamation sign in yellow triangle. Then I press VolumeUp again to go into ODIN download mode. But when I try to flash CWM recovery (or anything else) it goes into "waiting for debugging mode" or "waiting for adb mode". Windows ODIN shows COMM and allows to flush boot loader, but without any difference. I tried everything, including opening up the unit and disconnecting the battery. I can't even turn it off - the screen turns off but when I press power again - it comes right back to Samsung logo. Please help! Thank you.

I have recently changed carriers and never had this problem before. I havent changed anything yet but the new carrier claims I should be able to use both (1) pc connected over wifi to hotspot on my phone, 2)my phone as usual). But as soon as I enable 'wifi hotspot' on my Samsung Note 10, newest Android, all of a sudden I cant get email/notifications/data on my phone, until I disconnect. Then everything arrives.

If I'm going to buy used note 10 lite, what's the way to check is original and not fake?

I've used Galaxy Note 10 for about 6 months and one of the major issues that I have experienced was related to my gmail notification. I’d go several hours without receiving any emails and just think to check the app and as soon as I open the app then I’d have like 20 emails just sitting there that I had never received a push notification. Do you know any easy fix for this?

Samsung Galaxy Note Pro [12.2](https://en.wikipedia.org/wiki/Samsung_Galaxy_Note_Pro_12.2) ((https://www.samsung.com/uk/tablets/galaxy-note-pro-12-2-p900/SM-P9000ZKABTU/) , (https://www.samsung.com/latin_en/business/tablets/galaxy-note-pro-12-2-p900/sm-p9000zkltpa/)) bought used for diversity of Android tests during app development. Died suddenly a year later. Would still like to keep it running. It now has no sign of life when plugged in, but because the battery was still holding a 3-hour charge when last used, I suspect that the sudden death is not caused by the battery. The battery would have dwindled more slowly. 1. Net [chatter](https://forums.androidcentral.com/samsung-galaxy-note-pro-12-2/693393-best-battery-replacement-model-samsung-galaxy-note-pro-12-2-sm-p901.html) suggests that the USB connector is prone to breaking. Have you been there? Is this repairable? 2. I am content to use it with the power cord attached. Yet replacement battery sellers suggest that presence of a working battery is necessary. Have you been there? Can you confirm one way or the other? I used the 10.1 tag because the 12.2 is identical in build quality (or lack thereof) to the 10.1. Your experience with the Samsung Galaxy Note pro 10.1 is likely very relevant.

I have an SM-P600, when I download TWRP it shows lt03wifiue for the build name. When I download LineageOS it shows [n1awifi](https://wiki.lineageos.org/devices/n1awifi) for the build name. Are these two the same builds?

I get this message while surfing established websites. I press "OK" and website comes back and I can continue but message keeps reapearing. Very annoying. Any clue to fix ?

VLC has [two versions listed for ARM,](https://nightlies.videolan.org/) * Android (ARMv7-A) * Android (ARMv8-A) I'd rather not install with the PlayStore. Both of these versions when downloaded say "Can't open file" when I click then in the File Manager. For comparison, I also download [F-Droid](https://f-droid.org/en/) clicking it open up a prompt for me to install with the option INSTALL and CANCEL. I am using a Samsung SM-P600 UD.

I'm having a problem where every time I boot a rom on an SM-P600, I get a boot halt. I would like to know how to verify which version I have. LineageOS has a build for, * [n1awifi](https://wiki.lineageos.org/devices/n1awifi/) * [lt03lte](https://wiki.lineageos.org/devices/lt03lte)

My Note 10.1 (N8010) won't boot - sticks at the "Samsung Galaxy Note 10.1" logo. Power+VolUp does not take me to the recovery (just reboots), but Power+VolDown *does* take me to "ODIN MODE", so I presume my options are limited to things I can do from ODIN MODE. Fortunately there is no data on the tablet that I need. I would like to perform a factory reset. My best guess is that I need to erase the cache (and possibly data) partitions. Can I erase these from ODIN? If I need a cache.img or other images, where can I get or how can I create one? I use Linux so I cannot use Kies. I have Heimdall which appears to do this sort of thing. I have flashed TWRP (using ODIN) in the hope that it would boot into that recovery, but it does not.