Database Develop

Need help trying to unlock bootloader on HTC One

So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.

First off, I barely know anything with regards to phones as I still learning. However, last night had a similar issue and ended up having to use cmd prompt to navigate to adb and then used it to see the device.
MrTechie890 said:
So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
Click to expand...
Click to collapse

New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.

BD619 said:
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
Click to expand...
Click to collapse
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?

MrTechie890 said:
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
Click to expand...
Click to collapse
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).

tdhite said:
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
Click to expand...
Click to collapse
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.

MrTechie890 said:
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
Click to expand...
Click to collapse
Then try this:
adb backup
That should create a backup file called: backup.ab

tdhite said:
Then try this:
adb backup
That should create a backup file called: backup.ab
Click to expand...
Click to collapse
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.

MrTechie890 said:
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
Click to expand...
Click to collapse
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.

tdhite said:
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
Click to expand...
Click to collapse
For me, doing it on Linux wouldn't be a huge issue but since I have a mac as my primary machine I'm trying to make due with it.

I think I just firgured it out actually. I just had to install the android sdk, I was using the abd files provided from a tutorial. anyhow, thanks for trying to help tdhite.

[SOLVED] problem WiFi hotspot

Finally found the solution with my z3c. Problem started with Lollipop. When I was using my phone as portable AP there was no Internet access on any device connected. There were many descriptions of solutions (manual settings, soft reset, deleting all APNs) but none of them worked for me.
My service provider suggested changing APN settings:
Use whatever APN you find working for you, and change "APN type" field from "default,supl" to "default,dun".
Now everything works just like it's supposed to.
Sorry if someone posted this already or if it's under wrong subject. This is my first thread. Thanks.

I use this solution and it works for me:
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
------------------------------------------------------------
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed (any modern adb.exe works, the one included with FlashTool, for example)
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
------------------------------------------------------------

BarajaVLC said:
I use this solution and it works for me:
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
------------------------------------------------------------
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed (any modern adb.exe works, the one included with FlashTool, for example)
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
------------------------------------------------------------
Click to expand...
Click to collapse
My post is about portable hot spot, not USB tethering. I'm not sure if your post is about the same thing
If yes, then I'm very glad that we have multiple solutions for the same problem

Whoa! My girlfriend had this same problem on a moto g 2014 she bought a year ago, so yesterday I changed her APN type as you said and now everything's working. Thanks a lot.
Sent from my D5833 using Tapatalk

dgaspa75 said:
My post is about portable hot spot, not USB tethering. I'm not sure if your post is about the same thing
If yes, then I'm very glad that we have multiple solutions for the same problem
Click to expand...
Click to collapse
Yes, the solution I provided makes portable WiFi hotspot work

APN Type change to "default,dun" worked like a charm for me.

'settings' is not recognized
i have same problem hotspot is not working i installed android studio 3.0.1 and ran command
settings put global tether_dun_required 0
i get error
C:\Users\log\AndroidStudioProjects\MyApplication>settings put global tether_dun_required 0
'settings' is not recognized as an internal or external command,
operable program or batch file.
any help please

APN Type change to "default,dun" worked like a charm for me...thanks brother

Thanks so much for this! Genius!!

How to Solve 'Unauthorize Device' in ADB

Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot

Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

speedyjay said:
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
What does the Android SDK do mate?
I never used it before, so would be great if u can give me some hints
Thanks

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.

android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).

I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

tdamocles said:
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
Click to expand...
Click to collapse
Le_Zouave said:
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
Click to expand...
Click to collapse
Hello sir, i've been trying all of this method, include the wipe the phone (except using another computer) but still no prompt re-appear. Another advice would be greatly appreciated.
Thanks

joho5 said:
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho

toughkid said:
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
Click to expand...
Click to collapse
Have you checked all of your USB ports? I know in the past (with other phones), problems arise if you're not using a direct USB port (one soldered into your MoBo).

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Go to Control Panel > Hardware and Sound > Device Manager > expand Universal Serial Bus controllers. Now connect your phone. You'll now see USB Mass Storage Device. Right click on it. Select Properties, then go to Details. In the Details section, under Property, select Hardware ids. You'll then see the device id. It will be shown something like this: USB\VID_2A70&PID_9011&MI_01. From this you have to take the 2A70 code ~ the code between the first _ and &. Now go to desktop and create a new text document and copy paste this using your device id as shown:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2A70
Now open the Save As menu. In Save As type select All Files. Save the file as adb_usb.ini
Copy this .ini file from desktop and paste it in C:\Users\YourPCName\.android
Disconnect your phone, reboot your pc. Now with USB Debugging turned on, connect your phone to your pc, you'll surely get the permission thingy popup in your phone.

For completion:
If you DO NOT have access to your phone for any reason but still want to use ADB you can simply boot your phone into TWRP and follow these steps.
Windows:
1. Open %userprofile%\.android
2. Copy "adbkey.pub" to your phone (adb push %userprofile%\.android\adbkey.pub /sdcard/adb_keys)
3. Switch to your phone.
4. Go to Advanced > Open Terminal
5. Type in "stop adbd"
6. Move "adb_keys" from /sdcard to /data/misc/adb (mv /sdcard/adb_keys /data/misc/adb/adb_keys)
7. Type in "start adbd"
8. Switch to computer
9. Type "adb shell setprop persist.service.adb.enable 1"
10. Type "adb shell setprop persist.sys.usb.config mtp,adb"
11. Reboot your phone - DONE
Linux / Maybe Mac:
Same steps, but use "~/" instead of "%userprofile%"
Please note:
You may have to repeat the steps 1-7 after boot when still not having permissions so it makes sense to use cp (copy) instead of mv (move) and only repeat steps 5-7.
Edit: Please also check if your drivers are all installed and enabled.
Sent from my OnePlus 2 using XDA Labs

?k

Bell, Telus, Koodo and Freedom Mobile Volte and Vowifi Calling Working *Update Android 11 Require Root*

Finally
I can confirm it worked on my Oneplus 7 Pro both Volte and Vowifi calling it also can work on oneplus 6, and 6T since I don't have a device so I can't test it.
some people are unable to activated so this method require additional step for them.
Install QPST: https://mega.nz/file/zQt3ESDA#dd69iA2r9xZaYwWvYrCvVHl-OmjucIWI4ETFBTO5bM8 (This tool only work on Oneplus 6,6t, 7 series. Oneplus has blocked this tool on oneplus 5 series)
Next steps:
find PDC tool from installed QPST and open
select device from drop-down menu, if it is empty, you will have to reinstall/choose another driver
now right-click on overseas commerical ds and select Deactivated - Sub0
now right-click on Commerical-TMO and select SetSelectedConfig - Sub0
and now button Activate
Restart your phone than apply following step:
Oneplus Usb driver (Dont install it if you already installed this before)
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
After unzipping pixel3.zip you need to go to: Pixel3\mcfg_sw\generic\Pixel\NA\Freedom\VoLTE and copy mcfg_sw.mbn file to folder where you will have your EfsTools saved. It will ask you to overwrite one that is in that folder. Press yes.
Now follow these steps:
This method doesn't required root.
0. Make sure that you just enabled the VoWiFi and VoLTE in your carrier first !!!
1. Download and install the oneplus LogKit and Engineering mode apk:
3. Type *#800# --> oneplus Logkit --> Function Switch --> enable VoLTE and VoWifi switch
4. Open Settings --> WiFi & Intenet --> SIM & netwok --> enable VoLTE and VoWifi switch
5. Connect your phone to PC
6. Type *#801# in Phone app and enable Full-port switch (if your computer unable to recognize COM PORT try installing qualcomm driver: https://mega.nz/file/jV9ByarL#lbryKSC6uk9D-GTErtJ0SHyVOfWKA2TIl-psXmhj4YU)
7. Download and unzip the EfsTools with config files includes. (Make sure copy mcfg_sw.mbn file from pixel3.zip freedom folder replace the file if already exit.)
8. Open CMD as Administrator on the PC, navigate to the folder where you extract the files (eg. cd c:\EfsTools-0.10-modded-1.2-win32)
9. Now execute the following commands:
EfsTools.exe efsInfo
If your Freedom sim in Slot 1 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
If your Freedom sim in Slot 2 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
Thats it. Commands with "1" on at the end are for the second SIM card.
You must register here in order to wifi calling work: https://vowifi.authenticateme.ca/
Credit goes to @popos1 and @astracd. Original Post: https://forums.oneplus.com/threads/freedom-mobile-wifi-calling-working.1284987/
You need These file:
Pixel 3 mbn file:
https://forum.xda-developers.com/showpost.php?p=78563337&postcount=4 (Recommend for oneplus 6 series)
Pixel 4 mbn file:
https://forum.xda-developers.com/pixel-4/help/mbn-files-pixel-4-request-t4050247 (Recommend for Oneplus 7 series)
Thanks for @asasanc
Oneplus logkit:
https://mega.nz/file/rZlADYzD#Pg8vLZI4tZ16VXe-v-JfPLCiCab9fTTWwFcPBI04oho
Efstool:
https://mega.nz/file/fQcnQAZT#i0dRA6PvsuK4_PmLHPVXSwhOZroSsR6P1CuUDHwHW8g
Enigneering Mode apk:
https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/
Join Telegram group:
https://t.me/joinchat/QOPwqkqivRqnI4YIW2bojA
Edit:
Alot of people have confirm this method working on Oneplus 6,6t, 7,7 pro, 7t, and 8. For some people VoLTE works right away but for some it take few day to provision as per freedom it could take somewhere 72-120 HR to provision.
Edit 2:
Pixel 2 mbn for oneplus 5. This is recommended for Oneplus 5 only.
https://mega.nz/file/HUsHVYqS#n7pDP-mEMIY5MXffqViAVoqPgF_Au3hzzm6s5dgBZu0
Update: 3/25/2021
This new method requires Root on Android 11.​Please note Engineering won't work on Android 11. you need to follow the following steps to open the ports.
you need Adb tool Platform-tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
1. Extract the Folder
2. Open the Platform Tool folder then hold the Shift key and right-click on empty space to open the Command Prompt in the same folder.
3. Then Type "ADB shell"
4. Then type "su" (This will ask root access on your phone)
5. Then type this command to open the port.
"setprop sys.usb.config diag,serial_cdev,rmnet,adb"
Then you have will access to EFStool and PDC tool to Flash mbn file using the above method

can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.

It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)

astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
does this trick only work on stock roms, or would it work on a custom rom as well?

What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...

omvir said:
can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.
Click to expand...
Click to collapse
Yes it does connect to band 13.

CrazedBoredom said:
What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...
Click to expand...
Click to collapse
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI

nabbasi said:
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
Click to expand...
Click to collapse
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\

This is awesome news. Thanks for sharing brother!

CrazedBoredom said:
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\
Click to expand...
Click to collapse
.
Did you run CMD as administrator if not try with that.

nabbasi said:
.
Did you run CMD as administrator if not try with that.
Click to expand...
Click to collapse
Yep, no dice.

astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.

darkknight200 said:
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.
Click to expand...
Click to collapse
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app

astracd said:
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app
Click to expand...
Click to collapse
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.

darkknight200 said:
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.
Click to expand...
Click to collapse
Full port is enough. You don't need serial. :good:

astracd said:
Full port is enough. You don't need serial. :good:
Click to expand...
Click to collapse
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.

darkknight200 said:
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.
Click to expand...
Click to collapse
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?

astracd said:
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?
Click to expand...
Click to collapse
Yes to both

Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.

astracd said:
Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.
Click to expand...
Click to collapse
stil no luck with renaming them and using different state from charging to file transfer mode

[GUIDE] [NOOB-FRIENDLY] Fix random "screen off" - problem

I had the problem, that my device started to turn off the screen randomly.
Sometimes 5 times in 15 seconds !
So i post this GUIDE for anybody with the same Problem.
Disclaimer:​This is not my brainwork, i just put the pieces together as a Guide.
All knowlegde for this came from:
@ThE_MarD (from this forum)
and
LuK1337 (from the LinageOS IRC channel)
Thank you both very much !!!!!!
This Guide has 2 parts:
1. Check the logcat -or- figure out if this Guide is for you
( You can skip this Part, because this fix is easy to revert)
2. The fix !
############################################
1. Check the logcat:​
You need to fetch a logcat while the random screen off happens.
There are official ways :
How to capture logs | LineageOS Wiki
wiki.lineageos.org
The first of this seems to work without rooting your device.
But you have to have your device connected and the PC while the "random screen off" happens.
I opted for another "easy" logcat solution: Install aLogcat from the f-droid.org store on your rooted device.
https://f-droid.org/en/packages/org.jtb.alogcat/
And when the "screen off" happens just turn the screen on (unlock the device) , open the app , start it (if not allready running)
by tapping the "PLAY button" and save the log (just in case something goes wrong).
Then pause logging.
Which logcat path you gonna follow is your choise, but then you have to look for a line like this one in the log:
I/PowerManagerService( 1456): Going to sleep due to lid_switch (uid 1000)...
Click to expand...
Click to collapse
The important part is marked in bold letters.
If you find this line, then somehow the (magnetic) hall sensor (which normally gets triggerd by a small magnet in the
lid of the phone-case) got triggerd.
In this case the following (reversable) workaround should help!
If this is not the case you could try it anyway
#############################################
2. the fix !​( Turn off the anoying sensor ! )
You could compile a new kernel with the hall sensor deactivated !!
But: I never figured out how to do so, because there is also an easy road to follow:
If you have mysteriously not installed adb , just do it:
How to Install ADB on Windows, macOS, and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
And enable USB-Debugging in "{} Developer options" as well(also use the ADB guide)
The "Developer options" is kinda hidden in LinageOS18.1, follow this route:
Settings -> System -> Advanced -> {} Developer options
Click to expand...
Click to collapse
Connect the Phone via USB-Cable with your PC.
On your PC:
Check if the devices gets recognized using:
adb devices
Click to expand...
Click to collapse
When your device shows up use this one*:
(*This tip was given to me in the LinageOS IRC channel. After half a day messing around with setting
up a new Ubuntu 20.4 Build enviroment for compiling a new kernel i was glad that i got this hint.)
adb shell settings put global lid_behavior 0
Click to expand...
Click to collapse
Thats is it. You are done. Everything should be fine from now on !
If you want to reverse the change (for whatever reason) just use the magic:
adb shell settings put global lid_behavior 1
Click to expand...
Click to collapse
I am not sure but i suppose this should also survive a System-Update !