Hi there. I've been trying to find a way to repair IMEI on my Xperia XZ1 Compact and could use some guidance.
The methods I came across describe putting the phone into Diagnostics mode before the following steps can be taken, but no explanations or dial numbers on how to enable it for Sony Xperia models are provided; in two cases, it is stated that root is needed and following commands can be used to enter Diagnostics mode:
Code:
su
setprop sys.usb.config diag,adb
I tried running them through Terminal Emulator app and via adb on laptop, in both cases allowing root after the first command but getting nowhere with the second one. I'm assuming these instructions are no good for Xperias?
@4qx Thread closed as duplicate of
[CLOSED] del
del
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Related
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
mikeew83 said:
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
Click to expand...
Click to collapse
This is the way its done. Sorry up front for quoting myself but I have responded to this issue in the past:
Download the file from this post
http://forum.xda-developers.com/showpost.php?p=8752645&postcount=5
Follow the steps with this post
http://forum.xda-developers.com/showpost.php?p=14199959&postcount=11
Profit!
Holy run on sentence Batman.
Sounds like a drivers issue, or that you don't have USB debugging enabled on the phone.
Open the Dalvik Debugging Monitor Service (DDMS) that came with the Android SDK.
Does it recognize the phone at all in DDMS?
If yes, then does it say "online"? If yes, then you have something blocking adb from talking to your phone from your computer. (firewall?)
If no, then you have a driver or USB connectivity issue. (bad driver installation, usb debugging not enabled on phone, bad usb cable, plugged usb cable into a port not directly on the motherboard)
EDIT: Looks like the post above me could understand the run on sentence more than I could.
You can also run the command lsusb and it should tell you if your system is seeing the device.
What Linux distro your running?
Sent from an Epic with 4G
ok to recap
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
tried your directions again
I have tried them again and they do not work.
Try the usb cable for the droid x. Its a really good one.
if that were an option
I have an incredible cord i can try that is about the only one but i dont see how it has anything to do with the usb cable when lsusb recognizes the device plugged in just adb will not list it on devices so that i dont think is the answer but thank you for the suggestion.
mikeew83 said:
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
Click to expand...
Click to collapse
You should only have 1 rules file, my suggestion, delete the 15 one and keep the 99.
Make sure the permissions are configured correctly, the biggest issue to run this type of operations in linux is the permissions and the ownership on the config files
Sent from an Epic with 4G
thanks
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
mikeew83 said:
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
Click to expand...
Click to collapse
Let me go over what to do:
After downloading the rules file on the above post, for example I have the SDK (adb) installed on my PC on the following path: ~/android/tools/, so go to your SDK folder (where adb is located) and run the chmod a+rwx adb command.
After this, take the rules file you downloaded from the above post and moved it to the /etc/udev/rules.d/ folder (logged as root, NOT SUDO). After doing this, run the following commands:
make sure that 51-android.rules file has the following permissions -rw-r--r (read and write for owner, group + others read only)
su [then placed the password] (Once again DO NOT USE SUDO)
chown root:root 51-android.rules
Once done, restart the PC and it should be working 100%. Before connecting the phone, make sure USB Debugging is active, and restart your phone.
Connect your phone via USB and run the lsusb command to confirm the connection of the device and then run ./adb devices and check for the positive return!
Note: if you have never had a password on su, run the following command: sudo passwd and change the password and try running the series of command above.
Note2: add your user to the plugdev group on your computer
Note3: sometimes while performing the ./adb devices command will return a response stating that a device by the name ?????????????? is connected, this is OK, you can connect via ./adb shell and you will see your device file structure, if you request SU permissions you will have to authorize it on the phone via the SUPERUSER app that gets installed when rooting the device.
IMPORTANT: The password for ROOT (su) user is not the same as the password you enter for the SUDO command (your user) unless you make them the same!
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
SweetBearCub said:
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
Click to expand...
Click to collapse
Though this is good info (thanks for pointing it out), I would highly suggest to leave UART as Modem, and just change USB to PDA.
Sometimes you may have issues with Tethering if you set the UART to PDA.
I have been a bit busy I appreciate the run down and will try it here tomorrow or its 2am so later today I also checked the 8778 and my usb is already set to what was specified.
Sent from my SPH-D700 using Tapatalk
I am determined to downgrade and root my phone on my own, as opposed to paying someone on CL to do it for me. I just moved from Sacramento, CA to Cleveland, OH and I just got my comp unpacked and connected to the internet.
I Just downloaded SDK w/ all of the platform tools, ect. I have also been reading up on ADB and the appropriate commands. My only problem is my comp isnt recognizing the platform tools. it is located at the root of my C:\. Am I missing something? I was going to post in the development forum, but because I am new I can't. Can someone help me out please? I know I am close.
Thanks
How did you typed the command?
First of all be very grateful you can't post in the development sections because if you did it would only of lead to problems with these hungry users that are always ready to flame someone... Anywho...
Follow this guide to downgrade:
Downgrading
Follow this guide to downgrade and root the phone after that you can flash cyanogen if you want or anyother rom that u chose (((HINT: Black Unicorn Resurrected v4.1.1)))
lol, thanks for the heads up.
Does anyone have a link to a thread that shows step by step what to type and what the correct returns would look like?
The all seem to be a little different, and maybe im just an idiot but its pretty confusing seeing so many different ways to accomplish this
Ok, so I am going to try the wiki way to downgrade and root my phone. Hopefully this works.
Thanks for the help
TurboBrickMike said:
I am determined to downgrade and root my phone on my own, as opposed to paying someone on CL to do it for me. I just moved from Sacramento, CA to Cleveland, OH and I just got my comp unpacked and connected to the internet.
I Just downloaded SDK w/ all of the platform tools, ect. I have also been reading up on ADB and the appropriate commands. My only problem is my comp isnt recognizing the platform tools. it is located at the root of my C:\. Am I missing something? I was going to post in the development forum, but because I am new I can't. Can someone help me out please? I know I am close.
Thanks
Click to expand...
Click to collapse
So you have your platform-tools folder in C:\platform-tools? right?
Go into that platform-tools folder under command prompt, and type adb shell, see if it can detect the device.
Try this thread for adb help:
http://forum.xda-developers.com/showthread.php?t=928370
Thanks
Thank you guys for all of your help. It worked! My phone is now downgraded back to Froyo. Next is Root w/ S-Off and Cyanogen Mod.
KEarlier I saw a thread that demonstrated a python wrapper for the adb command. I remembered a while ago that adb uses a TCP protocol (duh it's written in the docs)
I had some spare time today so I decided to write a script for you all (I know how redundant it is, but hey why not)
This script incorporates the core functionality of adb into it, such as detecting your device... that's pretty much it at this stage..
so here it is. PyAdb​
I doubt this will brick anyone's devices... but just in case..
disclaimer:
if this bricks your device, it was not my fault. you used this at your own risk.
I don't care if this crashes your computers, or shoots you in the foot. you used it, not me
Click to expand...
Click to collapse
The general concept with how this works is below:
firstly, you have to choose your command from this list
secondly: the length of that command (in hexadecimal) needs to be prefixed before the command is sent. This is probably to do with security so the adb server on the device only reads the right amount of data
thirdly:... well there's not much more to it. just enjoy, tinker with it, and remember to contribute!!
note about getting device detected:
You need to ensure that the Android Debugging Bridge driver is installed for your device. this is normally supplied with standard device drivers. please refer to your device forums for instructions on how to install these
You also need to make sure your pc is authorised with stock adb, otherwise you won't be able to connect with PyAdb (for 4.2 upwards)
note about the current shell integration:
I now have a threaded interactive console, however single commands are still not read from a thread. If you want to use grep or kmsg, launch a full session
page not found!
Fixed link: https://github.com/cybojenix/PyAdb/
Looks like OP removed the file he linked to and forgot to change the link.
404 page not found?
cybojenix said:
Earlier I saw a thread that demonstrated a python wrapper for the adb command. I remembered a while ago that adb uses a TCP protocol (duh it's written in the docs)
I had some spare time today so I decided to write a script for you all (I know how redundant it is, but hey why not)
This script incorporates the core functionality of adb into it, such as detecting your device... that's pretty much it at this stage..
so here it is. PyAdb​
I doubt this will brick anyone's devices... but just in case..
disclaimer:
The general concept with how this works is below:
firstly, you have to choose your command from this list
secondly: the length of that command (in hexadecimal) needs to be prefixed before the command is sent. This is probably to do with security so the adb server on the device only reads the right amount of data
thirdly:... well there's not much more to it. just enjoy, tinker with it, and remember to contribute!!
note about getting device detected:
You need to ensure that the Android Debugging Bridge driver is installed for your device. this is normally supplied with standard device drivers. please refer to your device forums for instructions on how to install these
note about the current shell integration:
I haven't added a threaded data capture method yet, purely because I don't have time at the moment. it will (should) work with single commands. it isn't reliable for commands that take a while to run (such as grep)
Click to expand...
Click to collapse
404 page not found?
omegavesko said:
Fixed link: https://github.com/cybojenix/PyAdb/
Looks like OP removed the file he linked to and forgot to change the link.
Click to expand...
Click to collapse
lol yeah thanks. I did some file changes and forgot I linked to the file in the thread rather than the repo
Does anyone know if the Essential phone has a dial code, application, or method that will allow me to turn on Qualcomm Diagnositic Mode with RMNET and ADB?
I have RF testing software for my PC that interfaces with phones but I cannot get the Essential phone to be discovered because I cannot find those settings. I know on many other devices either the 0808 or 7284 dial codes worked.
I've already worked with the software developer, they support the chipset, but getting the phone to be recognized by the software is on me.
Any help would be appreciated.
abs0lutezer0 said:
Does anyone know if the Essential phone has a dial code, application, or method that will allow me to turn on Qualcomm Diagnositic Mode with RMNET and ADB?
I have RF testing software for my PC that interfaces with phones but I cannot get the Essential phone to be discovered because I cannot find those settings. I know on many other devices either the 0808 or 7284 dial codes worked.
I've already worked with the software developer, they support the chipset, but getting the phone to be recognized by the software is on me.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi, where you able to solve this? I'm having the exact same problem
Hey! I was able to find the solution for this.
First you will need to root the phone with Android 7.1.1 Nougat (you can find the procedure in the forum or in youtube).
After phone is rooted, run the following ADB commands:
su
setprop persist.sys.usb.config diag,serial_cdev,rmnet,adb
setprop sys.usb.state diag,serial_cdev,rmnet,adb
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Please note after entering "su" (super user) you'll need to grant superuser permissions (prompt shown on the phone).
After doing this, TEMS Investigation can detect and activate the phone, as you'll can see here. I assume other software (Nemo, XCAL, etc) should work as well.
Hope this helps!!
I can't unlock my Xperia L1, simply because fastboot won't recognize the phone
Expora9 said:
I can't unlock my Xperia L1, simply because fastboot won't recognize the phone
Click to expand...
Click to collapse
Watch on yt how to download Sony Xperia drivers, the video should tell you to use an application called flashtool
installing xperia companion tool will install all the necessary drivers if your on windows or mac.
https://www.sony.co.uk/electronics/support/mobile-phones-tablets-mobile-phones/xperia-l1/articles/00236877
don't want sony's tool then you can do it yourself by following the instructions here.
https://developer.android.com/studio/run/oem-usb
Tools Here https://developer.android.com/studio/releases/platform-tools
bigrammy said:
installing xperia companion tool will install all the necessary drivers if your on windows or mac.
https://www.sony.co.uk/electronics/support/mobile-phones-tablets-mobile-phones/xperia-l1/articles/00236877
don't want sony's tool then you can do it yourself by following the instructions here.
https://developer.android.com/studio/run/oem-usb
Tools Here https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I have companion already
Expora9 said:
"I can't unlock my Xperia L1, simply because fastboot won't recognize the phone"
"I have companion already"
Click to expand...
Click to collapse
Following Sony's guide is normally all that's needed. Ensure you have followed it to the letter.
How to unlock bootloader - Open Devices - Sony Developer World
developer.sony.com
One liners don't cut it here. This is a forum not a chat tweet or some other form of limited intelligence media
Please feel free to add some details and elaborate on what you have tried, your settings on device like usb debugging, oem unlock, etc. Things like does adb work? Post the output of the cmd prompt add some screenshots etc etc.
If you want help it should not be up to those willing to help you to draw the information from you.
We are not mind readers sadly.