hello, @dieter42 I meet the same probleme. So I tried to made the fastboot flash, but i received this answer : Sending 'aop_a' (180 KB) OKAY [ 0.010s] Writing 'aop_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions') fastboot: error: Command failed Perhaps i miss something...

@yuu-ä3 System settings offered the upgrade and unwisely I applied it only to find the phone more-or-less bricked. After a few false starts (see my posts) I was able to restore 20.04. My advice: DON'T TOUCH 24.04 on OP6 or 6T until there is an announcement about the port (Unless you are able to contribute to the porting work)

@CyBerT said in Onepluse6T change adduser and change password not work, passwd: Authentication token manipulation error: did have to change the ownership of the home folder, Glad you got it solved. But the above is never necessary. Maybe start another thread describing the issue you were facing that made you think you needed to solve it in this way. It might be possible to solve Inna different way, that will not break the system.

@RandomUser Yes

@TheTrench It's 20.04 OTA-10. 24.04 is not supported (yet, I hope) on this device.

Ok I found a solution that solves the headphone problem. Using nano, I add "rate=48000" parameter in the module-load line in /etc/pulse/touch.pa like this: ###Automatically load the Pulseaudio Droid .ifexists module-droid-discover. so load-module module-droid-discover rate=48000 voice_virtual_stream=true hidl_args='helper=false' .endif then I restart pulse with: systemctl --user restart pulseaudio.service I make rootfs writable with UT Tweak Tool (v1.0.0) Now wired headphones work properly! Thank you All

By following the method mentioned above, the GPS can be turned on.

@MrT10001 I did not use trwp just local update. But I did get it to go. I reset the phone, used the zip from the XDA link you put, then used a different computer with a fresh ubuntu install, flash UB24 from there it booted into recovery, I then flashed UB20 from the installer and was able to update to 24. Not sure why that worked but it did. Thank you for helping. EDIT so I posted that while it was updating to 24.0 and it rebooted right back to recovery and that was it, I was able to re flash 20.0. So I assume 24.0 just does not work on the 6t as of yet, which is cool since it is still new.

Hi @darshpreets I cannot be sure about your specific device. But phones are usually only able to be either an access point or a client, but rarely both. As for Ubuntu Touch being able to handle this case on such compatible hardware, I'm not sure. That would be something to test.

@marlboro50 Ah, sorry, missunderstood. Good luck!

I wonder if could be related to a faulty charging port or cable? I was having connectivity issues with my OP5t, and it seemed like sometimes it was sometimes charging at a lower rate, despite using the Dash charger adapter or whatever. But then it became hard to charge at all, and eventually I had to replace the port (which thankfully wasn't too hard). Anyway, just a thought. Maybe try another cable for starters?

@James-T What you surmised is quite correct. To shutdown the OP6 and 6T you have to either leave it a while, or use the key combo to het to fastboot mode and power off from there.

@MrT10001 oh, cool, that is the good news, thanks your research,so the solution that I need change the more better OTG hub, I will try it, thanks your effort again.

@ikoz I search in internet and find below solution, but not work, even memory fully used, but swap used still is 0, I don't know why. sudo fallocate -l 8G /userdata/swapfile sudo chmod 600 /userdata/swapfile sudo mkswap /userdata/swapfile sudo swapon /userdata/swapfile sudo sysctl vm.swappiness=80

@ancientsounds in my experience the mediaplayer app only plays mp4 videos encoded in a special manner. If you're lucky, they work, or they just don't. Maybe you were lucky until now. I encode or re-encode my video files with Handbrake with standard settings. There was no file yet, the media player didn't play... Maybe this helps...

@MrT10001 Your suggestion to discharge the battery completely was the solution. Phone has been working fine since then. Many thanks!