[Q] Acclerometer (G-sensor) not level while phone is level - Milestone XT720 General

Hi,
I have experienced that the accelerometer (G-sensor) is not level while I hold the phone horizontally to play racing game. The car just veer to the right.
I used the app "Bubble" and confirm that the accelerometer is off by 4 degrees to the right when the phone is level in the horizontal axis.
I duplicated this problem on another XT720. Is this a batch problem? Does anyone face the same problem?

Many phones have this, even with stock firmware. So it's not just our model.

So we just live with it? Can the factory calibrate them?

There is calibrating-setting in the 2.1 stock ROM.
But if that doesn't help, you just have to live with it. Lots of people with different phones have this. Dunno what te problem is, maybe insensitive sensors. But that can't be fixed unless you start modeling the phone all over again.

hi,
I came across the following link where a Galaxy S user faced the same problem and resolve it.
Will any experts here be able to adapt this to XT720?
Hi Guys,
I noticed that when i played a few games – the g-sensor / accelerometer (whatever you'd like to call it) was off to the left – on a flat surface.
Can be easily checked if yours is off by going into keypad and typing in:
*#0*# – And then selecting Sensor
Mine was y: -24, xx: 0, z: -216 (the z axis is fine)
Some games had a calibration option, some did not like Hyper Jump.
To fix this (please note, your phone must be rooted, it's not that difficult):
1. Install the Drivers for your phone
http://forum.xda-developers.com/showthread.php?t=728929
2. Download the latest SDK for Android
http://developer.android.com/sdk/index.html
3. Extract the Archive
4. Enable debugging for your phone
– Settings
– Application
– Development
– Enable USB Debugging
5. Plug in USB
– DO NOT MOUNT, just leave it plugged in, if you mounted it, unmount from the phone
6. Open CMD and CD to the directory where you extracted the SDK.
– e.g. cd C:\android-sdk-windows\tools
5. Once you have done so type in the following:
adb shell
su
/system/bin/sensorcalibutil_yamaha
6. Ensure your phone is on a flat surface
7. Press enter in the CMD Window
– Should tell you it is complete
8. Type in the CMD Window
reboot
9. Your phone will reboot and your calibration issue will be fixed.
Please Note: I have done this and my phone is still working. If you so happen to break your phone, I am not liable, and will not accept any responsibility.
If you have any questions, please feel free to PM me.
Credit goes to to vitalij
http://forum.xda-developers.com/showpost.php?p=6999499&postcount=8​
nhc

nhc said:
hi,
I came across the following link where a Galaxy S user faced the same problem and resolve it.
Will any experts here be able to adapt this to XT720?
Hi Guys,
I noticed that when i played a few games – the g-sensor / accelerometer (whatever you'd like to call it) was off to the left – on a flat surface.
Can be easily checked if yours is off by going into keypad and typing in:
*#0*# – And then selecting Sensor
Mine was y: -24, xx: 0, z: -216 (the z axis is fine)
Some games had a calibration option, some did not like Hyper Jump.
To fix this (please note, your phone must be rooted, it's not that difficult):
1. Install the Drivers for your phone
http://forum.xda-developers.com/showthread.php?t=728929
2. Download the latest SDK for Android
http://developer.android.com/sdk/index.html
3. Extract the Archive
4. Enable debugging for your phone
– Settings
– Application
– Development
– Enable USB Debugging
5. Plug in USB
– DO NOT MOUNT, just leave it plugged in, if you mounted it, unmount from the phone
6. Open CMD and CD to the directory where you extracted the SDK.
– e.g. cd C:\android-sdk-windows\tools
5. Once you have done so type in the following:
adb shell
su
/system/bin/sensorcalibutil_yamaha
6. Ensure your phone is on a flat surface
7. Press enter in the CMD Window
– Should tell you it is complete
8. Type in the CMD Window
reboot
9. Your phone will reboot and your calibration issue will be fixed.
Please Note: I have done this and my phone is still working. If you so happen to break your phone, I am not liable, and will not accept any responsibility.
If you have any questions, please feel free to PM me.
Credit goes to to vitalij
http://forum.xda-developers.com/showpost.php?p=6999499&postcount=8​
nhc
Click to expand...
Click to collapse
There doesn't seem to be any files named sensor in /system/bin on the XT720:
Code:
# cd /system/bin
# ls | busybox grep sensor
nothing is listed

Tech support has change out my motherboard and the fault persist.
They claim that they can't do anything.
I am wondering why is it so difficult for them to do a calibration on the sensor?
I tried to do more research on the net and found there are a lot of reported similar symptoms with other phones, some with solutions. (Search under G-sensor)
But for XT720, it seems that I am the only one reporting this symptom.

The G-Sensor is related to the auto-rotation? because in my xt720 this function does not work

Alguien ha podido dar en la tecla con este tema?
saludos

Related

Obtain MSL code on Linux/Unix

How to find the MSL for your Photon Q
chrisngrod posted a tool for getting the MSL from logcat (http://forum.xda-developers.com/showthread.php?p=31765156) but is in the form of a .bat script, which isn't very useful for Mac or Linux users. I'm a decently regular reader, but I guess I've never posted. So sorry that this isn't in the dev section.
I'm assuming a couple things here
You have the android SDK installed, or at least adb available to you
You have a Motorola Photon Q (on Sprint?) plugged into your computer and appropriate drivers installed (if needed--not sure)
USB Debugging is enabled on your device
You know what a terminal is, or at least how to use one
You are in the current directory of adb. If it's in your path, omit the "./"
Make sure your computer sees your phone
Code:
./adb devices
You should see something like
Code:
List of devices attached
T*******Y device
where *'s are numbers. If you don't see any devices, make sure nothing else is interfering (tethering apps on computer, etc)
Now, go to the dialer on your phone, and dial ##DATA#. A menu should pop up, tap on Data Profile, then the three dots at the top right, and finally Edit. Enter 6 random digits, and click Verify.
Now go back to your computer and run this
Code:
./adb logcat -b radio -d | grep "grde"
Hopefully you'll only see one line. If there's more than one, look for one that looks like this
Code:
09-21 21:56:38.837 360 360 E RIL-MOTEXT: NV Read 32, length 6, data length 6, grde - 313934333230
The last set of numbers is what we care about. Your MSL is encoded in the even digits (in counting i.e. 2, 4 ,6 ,8 ..). Mine happened to be hidden in some 3's. So this phone's MSL is 194320.
Test it out by going back to your phone and typing it in.
This worked for me, and I haven't found anywhere else that talked about doing it for the Photon Q, so please correct any incorrect information.
asinginglamp said:
How to find the MSL for your Photon Q
Now go back to your computer and run this
Code:
./adb logcat -b radio -d
Hopefully you'll only see one line. If there's more than one, look for one that looks like this
Code:
09-21 21:56:38.837 360 360 E RIL-MOTEXT: NV Read 32, length 6, data length 6, grde - 313934333230
The last set of numbers is what we care about. Your MSL is encoded in the even digits (in counting i.e. 2, 4 ,6 ,8 ..). Mine happened to be hidden in some 3's. So this phone's MSL is 194320.
Click to expand...
Click to collapse
I was able to do this with only the phone and connectbot. Putting in a false code and then looking over logcat for the NV Read 32, Mine was also hanging out with a group of 3s.
KitsunePaws said:
I was able to do this with only the phone and connectbot. Putting in a false code and then looking over logcat for the NV Read 32, Mine was also hanging out with a group of 3s.
Click to expand...
Click to collapse
Nice. I tried doing it with aLogcat, but didn't see anything. Didn't think to try connectBot.
with me it was between the 3's, i copied the msl.bat to the ADB-platform tools folder what i use for compiling-decompiling apk's, and it worked.
This Is Cray
Gojira-r32 said:
with me it was between the 3's, i copied the msl.bat to the ADB-platform tools folder what i use for compiling-decompiling apk's, and it worked.
Click to expand...
Click to collapse
err
i tried this method the only thing i see on the transcript using adb logcat is checksubsidylockpasswrdcomplete<>errorno=RIL_OEM_CDMA_GENERIC_FAILURE..
Like ive tried everything, any suggestions..besides call sprint
batzluminatti said:
err
i tried this method the only thing i see on the transcript using adb logcat is checksubsidylockpasswrdcomplete<>errorno=RIL_OEM_CDMA_GENERIC_FAILURE..
Like ive tried everything, any suggestions..besides call sprint
Click to expand...
Click to collapse
Do you get anything with adb logcat?
???
asinginglamp said:
How to find the MSL for your Photon Q
chrisngrod posted a tool for getting the MSL from logcat (http://forum.xda-developers.com/showthread.php?p=31765156) but is in the form of a .bat script, which isn't very useful for Mac or Linux users. I'm a decently regular reader, but I guess I've never posted. So sorry that this isn't in the dev section.
I'm assuming a couple things here
You have the android SDK installed, or at least adb available to you
You have a Motorola Photon Q (on Sprint?) plugged into your computer and appropriate drivers installed (if needed--not sure)
USB Debugging is enabled on your device
You know what a terminal is, or at least how to use one
You are in the current directory of adb. If it's in your path, omit the "./"
Make sure your computer sees your phone
Code:
./adb devices
You should see something like
Code:
List of devices attached
T*******Y device
where *'s are numbers. If you don't see any devices, make sure nothing else is interfering (tethering apps on computer, etc)
Now, go to the dialer on your phone, and dial ##DATA#. A menu should pop up, tap on Data Profile, then the three dots at the top right, and finally Edit. Enter 6 random digits, and click Verify.
Now go back to your computer and run this
Code:
./adb logcat -b radio -d | grep "grde"
Hopefully you'll only see one line. If there's more than one, look for one that looks like this
Code:
09-21 21:56:38.837 360 360 E RIL-MOTEXT: NV Read 32, length 6, data length 6, grde - 313934333230
The last set of numbers is what we care about. Your MSL is encoded in the even digits (in counting i.e. 2, 4 ,6 ,8 ..). Mine happened to be hidden in some 3's. So this phone's MSL is 194320.
Test it out by going back to your phone and typing it in.
This worked for me, and I haven't found anywhere else that talked about doing it for the Photon Q, so please correct any incorrect information.
Click to expand...
Click to collapse
The first command works..Recognizes dev, then the logcat command works ONLY when i leave off at the -d. When i do the process i see the RI-MOTEXTem Hook header type 0, requestcode 0x2000016...blah blah blah..how do i write the second part of the comand..?
msl
I ran into that error- OEMRequestunlock thingy.... I tried looking through myself with alogcat, but nothing... at the time I thought I fixed it by downgrading the android OS... then the .bat still didn't work... I figured out that that was because of the path statement not including the location of findstr.exe (grep in this linux example) but now I think that maybe the .bat file didn't work originally because of the path statement and I maybe didn't have to downgrade the OS, but if you're straight up doing it by typing the command into terminal and with grep no less and encountering the problem, then I'll bet it was necessary to downgrade the OS.
So what I'm saying is- you probably have to downgrade the Android OS to one that has the MSL in the ril. Also, it might not be showing up in aLogcat because you'd have to tell it to read the radio log (which is what the -radio switch does)
Hope this helps
I made one phone call to Sprint tech support and simply asked for my MSL, and the lady gave it to me. No questions asked.

Kyocera-E4710

the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Kyocera-E4710 - T-Mobile Tethering
I too have purchased one of these excellent flip phones. I really want to be able to tether using T-Mobile's service. Has anyone risen to the challenge yet?
kotton666 said:
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Click to expand...
Click to collapse
Rooting Kyocera E4710
Is it possible to root this phone? I would like to install an Android SIP client, the operator said it's not possible to install anything on it. Even though I enabled apps from Unknown Sources.
kotton666 said:
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Click to expand...
Click to collapse
Not sure if anyone still needs to remove the AT&T address book on this phone without root BUT I managed to do it.
Enable Developer mode on the phone by clicking:
"Menu" from the home screen. Choose Settings-->System-->About Phone.
Scroll down to "Build Number" and hit the "ok" button a few times until it tells you that you're a developer.
Back up one menu and go into "Developer Options".
Enable USB Debugging. (I also enabled OEM Unlocking but I don't think this is necessary)
Next install the Universal ADB drivers onto your computer. Google will help you find them. (I used the ones from clockworkmod but I'm sure any of them would be fine.)
Connect your phone and ALLOW any of the prompts that come up.
Open up an administrative command prompt/terminal and then type "adb devices". Make sure you can see a device listed. I'll look something like:
* daemon started successfully *
6689467283 device
Next run the command:
adb uninstall --user 0 com.borqs.aabsync
You should see a "success" below.
If so run the command: adb reboot
Your phone will reboot and you can disconnect the phone from the computer at this point.
Give it a moment to start up and then hit the "down" arrow on the keypad as normal. You will likely see an empty contact list. Press the key for "Options" then choose "Contacts to display" and choose wherever you have the contacts saved. Let it load them in and you're done.
Hope this helps someone!
david11717 said:
Not sure if anyone still needs to remove the AT&T address book on this phone without root BUT I managed to do it.
Enable Developer mode on the phone by clicking:
"Menu" from the home screen. Choose Settings-->System-->About Phone.
Scroll down to "Build Number" and hit the "ok" button a few times until it tells you that you're a developer.
Back up one menu and go into "Developer Options".
Enable USB Debugging. (I also enabled OEM Unlocking but I don't think this is necessary)
Next install the Universal ADB drivers onto your computer. Google will help you find them. (I used the ones from clockworkmod but I'm sure any of them would be fine.)
Connect your phone and ALLOW any of the prompts that come up.
Open up an administrative command prompt/terminal and then type "adb devices". Make sure you can see a device listed. I'll look something like:
* daemon started successfully *
6689467283 device
Next run the command:
adb uninstall --user 0 com.borqs.aabsync
You should see a "success" below.
If so run the command: adb reboot
Your phone will reboot and you can disconnect the phone from the computer at this point.
Give it a moment to start up and then hit the "down" arrow on the keypad as normal. You will likely see an empty contact list. Press the key for "Options" then choose "Contacts to display" and choose wherever you have the contacts saved. Let it load them in and you're done.
Hope this helps someone!
Click to expand...
Click to collapse
Thanks for posting your solution above.
Unfortunately for me I got as far as installing the adb drivers on my PC, reconnecting the phone, and no prompts came up, neither on the phone nor the PC.
I opened a command prompt window and typed "adb devices" and got the following message:
adb devices is not recognized as an internal or external command,
operable program or batch file.
Any suggestions?
As long as ADB driver isn't made system-wide accessible ( i.e. got added to PATH environment variable of Windows OS ) you get the message mentioned.
My Kyocera E4710 outer screen has an alarm that I can't get to go away. I can't see who is calling me because the alarm blocks the caller info. I have a few alarms but they are all turned off and there is not a way to delete them. I've gone through the user manual and it doesn't show how to get rid of this alarm (which shouldn't show since there isn't one enabled). Does anyone know how to get rid of this alarm on the outer screen? Thanks.

VOLTE Success, Activation without Firmware Replacement (Sony Mobile withdrawal area)

I wrote the method in 1 II for your reference.
The Qualcomm Diagnostic Port command in Xperia 1&5 is as follows.
(setprop sys.usb.config rndis,eng_mode,adb)
And use the EFSTOols.exe program.
It's easier than I mk2.
Screenshot is
1&5 and 1 MK2
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.
Interesting. I wonder if the OpenDevice Modem on AOSP works without that Hack in the same Way. Would be cool to know... Pixel Experience for Example enabled VoLTE, Wifi Calling and Video Calls over Carriers on My Xperia 5 without any additions or extra work. It detects the SIM and loads the needed Configs for it on the Modem. Pretty handy hack from the SONY Community to get extended functionality over AOSP or GSIs

Change Android settings with ADB?

Hi, I'd like to know if it's possible (and if so, how) to directly change android settings via adb commands.
My wife has broken the LCD screen on her phone (OnePlus 7T HD1907, Android 11, rooted with Magisk). I'm having a lot of trouble getting screen mirroring and USB OTG input devices to work at the same time; I have a USB v3 hub, and a USB OTG connector, but I've only been able to consistently get either screen mirroring or input devices to work, not both at the same time. The screen on the phone has now completely failed so I can no longer switch back and forth between the two to make changes on the phone. When I did have it working briefly I turned on the "experimental desktop mode on secondary displays" in Developer Settings, which just made things worse because Android settings don't seem to be available in desktop mode.
I have an identical phone to which I can refer, if needed.
Feenix0 said:
Hi, I'd like to know if it's possible (and if so, how) to directly change android settings via adb commands.
My wife has broken the LCD screen on her phone (OnePlus 7T HD1907, Android 11, rooted with Magisk). I'm having a lot of trouble getting screen mirroring and USB OTG input devices to work at the same time; I have a USB v3 hub, and a USB OTG connector, but I've only been able to consistently get either screen mirroring or input devices to work, not both at the same time. The screen on the phone has now completely failed so I can no longer switch back and forth between the two to make changes on the phone. When I did have it working briefly I turned on the "experimental desktop mode on secondary displays" in Developer Settings, which just made things worse because Android settings don't seem to be available in desktop mode.
I have an identical phone to which I can refer, if needed.
Click to expand...
Click to collapse
I don't know if it contains your specific setting, however, many settings can be read/stored/modified using the foillowing commands from a shell/ADB. using
Code:
# read settings, there are three partitions. Secure, System & Global
settings list secure;
settings list system;
settings list global;
# to read a specific one
settings get secure "sleep_timeout";
# to change a setting
settings put secure "sleep_timeout" "-1";
# there's another command for delete, but I cnat remember it for certain, so dont wish to guess and lead you astray ;) and I am sure you know how to do a web search
The above is for a shell, adding adb shell to the front would run it explicitly from adb.
Trying to change system settings requires Android is rooted.
xXx yYy said:
Trying to change system settings requires Android is rooted.
Click to expand...
Click to collapse
It is.
DiamondJohn said:
I don't know if it contains your specific setting, however, many settings can be read/stored/modified using the foillowing commands from a shell/ADB. using
Code:
# read settings, there are three partitions. Secure, System & Global
settings list secure;
settings list system;
settings list global;
# to read a specific one
settings get secure "sleep_timeout";
# to change a setting
settings put secure "sleep_timeout" "-1";
# there's another command for delete, but I cnat remember it for certain, so dont wish to guess and lead you astray ;) and I am sure you know how to do a web search
The above is for a shell, adding adb shell to the front would run it explicitly from adb.
Click to expand...
Click to collapse
Would I simply type "adb shell" to start the shell after connecting to the device? I'm assuming that this would be a linux shell.
xXx yYy said:
Trying to change system settings requires Android is rooted.
Click to expand...
Click to collapse
I am pretty sure that not ALL settings require root to be changed.
Feenix0 said:
It is.
Click to expand...
Click to collapse
Well, that makes it hypothetical in this case
Feenix0 said:
Would I simply type "adb shell" to start the shell after connecting to the device? I'm assuming that this would be a linux shell.
Click to expand...
Click to collapse
There are many ways to do things.
Personally (if not using the app I created and listed below), I start a shell with adb shell and I am running windows, so that is run from a command shell.
At that point, you enter the ANDROID shell (Not linux, its an android device)
I then change to a root shell with su; Only because anything worth doing usually requires root, and at least some of these will.
And then I can run any of the statements above. I would suggest you run a list of each and save that off as a backup.
Another option to see many of these in action and generate a "restore" of the existing, is using the app I created called TeMeFI
You can find these under the menu Current State>Settings>*

One plus 6: display black, can't see nothing try to connect via adb to enable function and use OTG cable to television or something else

Hi to all,
how are you?
It's still a very long time i don't wirte here.
So i was a happy owner of a oneplus 6 from may 2019. I haven't problem and all works so well.
During a trip with fog and rain, the phone was wet and full of humidity, i had to use it during the rain 2 times to find the way to come back. When i was in home the display never respond. I tried to dry with a hairdryer but i won't go. In the meantime i buyeg a motog22 waiting to adjust my oneplus.
I'm using the original oneplus os, with last updates of august
So i remember i enabled the developers mode on my phone and i hoped also usb debugging and otg was enabled to cast the screen with this: https://plugable.com/products/uga-4khdmi (there are also the displaylink driver that tart at trhe phone startup), but i won't activate, don't no why.
Then i decided to try via adb to unblock wifi and other thing and make it usable with otg or thing like this: https://github.com/Genymobile/scrcpy
When i started abd i got this:
D:\myfolder\platform-tools>adb devices
List of devices attached
phonenumber unauthorized
I read some xda and stackoverflow posts but can't find a solution.
To authorize it i tried to delete adbkey inside .adroid folder, kill and start server but nothign working also cause the phone want an authorization that i can't give cause i can't see my display even if the display vibration is working and maybe also the touch.
Then i tried this:
adb reboot recovery
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
So i tried to restart the phone in boot recovery trying to see if the authoriaztion is enabled by default, but nothing happen.
I just wanted to push the keys to my phone and then using adb to reactivte wifi and something else almost to cast my phone or make a backup of some application (like google auth or microsoft auth...)
Are there an extreme solution or i have to wait the display and change it? I know this is the best solution but without this phone i have some activities...bloked It's incredible!
Thnks in advance for you help!
Bye

Categories

Resources