RMA'd 12w19 problems - Xperia Play Q&A, Help & Troubleshooting

Got an RMA'd Xperia Play 4G (r800at) straight from Sony and went to go follow my usual steps to root it from the unupdated firmware and it just doesn't work. Flashtool reports no connected device and ADB Shell doesn't connect. I can't do anything but flash in flash mode, and on different firmwares I get the same issue. I got it to connect once with Flashtool and it said "Root Access Allowed" and that was when I first got it. I haven't been able to do much with it since I got this one.
It's a 12w19.

Doesn't seem to be a phone problem, you just need to get adb to recognize your device. Did you check to make sure you enabled USB Debugging and installed the correct ADB drivers provided with Flashtool? You might also need to change from MTP mode to MSC.
I recommend flashing this firmware: http://forum.xda-developers.com/showthread.php?t=1591398

eksasol said:
Doesn't seem to be a phone problem, you just need to get adb to recognize your device. Did you check to make sure you enabled USB Debugging and installed the correct ADB drivers provided with Flashtool? You might also need to change from MTP mode to MSC.
I recommend flashing this firmware: http://forum.xda-developers.com/showthread.php?t=1591398
Click to expand...
Click to collapse
Yes, Debugging and MSC are on.
It does the same thing in multiple firmwares, including that one.

Related

HTC Unlocked, but ADB ain't workin'

I'm on a Mac running Lion.
So, I successfully HTC-Unlocked my INC2, but now when I try to move on to the next steps toward rooting, I run into some issues: I tried to use ADB to flash CWM, but my device refuses to be recognized and so that plan is moot. That's the first issue.
Secondly, I tried an alternate method of flashing CWM via a "PG32IMG.zip" file (that is obviously just a compressed CWM .img) HBOOT, but then my HBOOT just hangs after it recognizes the file and tries to flash.
I've returned to the ABD method, but my phone just is not being picked up in Charge-only mode. The Mac itself recognizes it fine, and Disk-Drive mode works flawlessly. Any suggestions on getting ADB to realize my phone is there?!
P.S. debugging is on.
natemup said:
I'm on a Mac running Lion.
So, I successfully HTC-Unlocked my INC2, but now when I try to move on to the next steps toward rooting, I run into some issues: I tried to use ADB to flash CWM, but my device refuses to be recognized and so that plan is moot. That's the first issue.
Secondly, I tried an alternate method of flashing CWM via a "PG32IMG.zip" file (that is obviously just a compressed CWM .img) HBOOT, but then my HBOOT just hangs after it recognizes the file and tries to flash.
I've returned to the ABD method, but my phone just is not being picked up in Charge-only mode. The Mac itself recognizes it fine, and Disk-Drive mode works flawlessly. Any suggestions on getting ADB to realize my phone is there?!
P.S. debugging is on.
Click to expand...
Click to collapse
Did you unlock using the HTC method that they provide? Or our way on the forums.
I would double check to ensure that your drivers are good to go first. ADB should be recognizing your phone with debugging on.
Also look into EasyADB and see if that helps. Does typing 'adb' in command prompt output anything?
HTC's. I don't think Macs need drivers for this, if my memory serves me correctly. The phone is recognized by the Mac itself just fine, BTW. What's EasyADB? I'm googling, and seeing stuff about the Nook...

R800i Issues with USB Driver and Bootloader!

Hi Guys,
Any help would be great! i do have google talk if anyone is willing to help me out!
My R800i Is rooted and has a version of recovery but not sure which version, i am wanting to update my phone with a better kernel and rom since the current one i have installed is giving me issues ( not being able to receive incoming calls for example )
Another problem is i reformatted the phone since i was having issues with receiving calls but now when i connect my phone to ANY computer via the USB cable the computer trys to install MTP or MSC driver ( depends on which connection type i select ) the Installer fails and i cant even take any files off my phone.
Provided details below. i want to somehow get into the current bootloader and install the ROM thats on my SD card! i do have flashtool installed and Android tool SDK installed but still no success in phone wanting to talk to my laptop.
I am running windows 7 64 bit. i am starting to think the phone is belond repair since i cant get any software to work between the phone and computer.
does anyone know what buttons i need to push on the Xperia Play to enter into the boot loader, i have tried pressing the back button and search button on phone boot but nothing happens apart from the phone starts up normally.
would a factory reset delete the boot loader and other config-ed software off the phone is this why i cant enter the boot loader or am i not pressing the right buttons on boot.
Any help would be really appreciated!
IMEI:
357302043579712
IMEI Software Verson
49
Available Speech Codecs
HR, FR, EFR, AMR_HR, AMR_FR
Working Bands
GSM850, GSM900, GSM1800, GSM1900, UMTS_BC1, UMTS_BC8
Rooting Status Bootloader Unlocked Allowed: Yes
Phone Software Version
1245-8821_4.0.1.A.0.283
S1 Boot Version
1241-3656 R9A021
EST Software Version
1242.5099_10
Android Version
2.3.4
Baseband Version
8x55A-AAABQMAZM-203028A-49
Kernel Version
2.6.32.9-perf
Build Number
4.0.1.A.0.283
If you want to change the kernel you must unlock your bootloader. If your Xperia Play is a SIM free one, you can do it for free in this link: http://unlockbootloader.sonymobile.com
For SIM locked devices I think you must find another ways to do it. There are some online sites that unlock bootloader to SIM locked devices for a fee.
Once you have unlocked your bootloader, turn off the phone, hold on the search button, plug the USB cable in the computer, release the search button (power button LED will be blue) and install this driver: http://drivers.softpedia.com/progDownload/Google-USB-Driver-Revision4-Download-139077.html
Now you are ready to flash any kernel you want with Flashtool or any other app.
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
PsychoShaft said:
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
Click to expand...
Click to collapse
I have tried what you said but having problems with connecting my phone to my Windows 7 Laptop!
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
jcarbox said:
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
Click to expand...
Click to collapse
Hi I tried what you said, i Turned off my phone and holded the search button and turned it back on, the light went blue and the computer popped up trying to install fast boot i point to the SDK folder to update the driver but it fails.
do you have google talk might be easier on there to talk! cheers!
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
jcarbox said:
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
Click to expand...
Click to collapse
Thanks for the download link, i going to try this in a bit and get back to you! thanks for the support guys! :good:
Just tried, i put my phone into Media Transfer Mode.. my computer tried to install the MTP usb device and i directed the installation to the driver you linked..
Update Driver Software says: the best driver software for your device is already installed MTP USB DEVICE, there is a small yellow triangle on the icon and in MTP USB Device Properties it says: This device cannot start. (Code 10)
i need someone to Teamviewer with me, for the record i don't have the Sony Ericsson software installed on my Computer because that still wont install the drivers for my phone, i also know its not needed for installing new kernel and roms.
i tried connecting this phone to a bunch of pcs including my friends and it still fails to install any drivers!!! i think i am just going to bin this phone! i have had enough (
You must install that driver when you plug the phone in fastboot mode. It shouldn't work in any other case. In other words, when you plug your Xperia Play being powered on and Android is running it needs one driver, and when you boot it in fastboot mode you need other driver.
Please, install the driver following the steps previously posted with your phone in fastboot mode (blue LED).
Hello, i put my phone into fastboot mode, my device manager shows 1 device not installed S1Boot Fastboot, i right click go to properties and click update driver...
then i browse my computer for driver software i point the location to usb_driver_rev4\usb_driver and it says: Windows was unable to install your s1Boot fastboot!
Ok, let's see...
Try to update the driver using the "choose from a list" option to force the installation, point to the driver folder and select "Android ADB Interface" from the list. If Windows shows a warning message don't worry about it and go ahead.
i tryed this and its not wanting to work (
Sorry to hear that because I don't have any more ideas for your problem.
Maybe you may spend some minutes searching in the forum to find some detail that can help you.
i need someone with teamviewer to help me go though the setup process again, if anyone is willing to get my phone working i will happy pay them some money!
Thanks Jcarbox for all your support!
Regards
Paul
I just check the Windows device manager with my phone plugged in bootloader mode and it appears as Android Bootloader Interface, so this is the device you must choose from the list when you install the driver.
Hope this helps you.
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
This may work
PsychoShaft said:
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
Click to expand...
Click to collapse
hi PsychoShaft,
I had similar problems. I don't know how to fix it permanently. but i do this to make it work for some time.First, download flashtool and install it.Open your device manager and select view->show hidden drivers.Then, delete all your drivers related to xperia play. like the adb interface, semc flash ,etc. All of them in all categories. then reboot your computer into safe mode with administrator and connect your device with flashtool running in your windows in safe mode. then the flashtool will indicate that you don't have the drivers. then,open the drivers folder in flashtool and use the setup to install arc-play-...,flashmode drivers and fastboot mode drivers.then after the installation is over windows will ask you to reboot.now reboot with your mobile connected. after boot windows will automatically install the drivers. then unplug your phone and turn off it and connect in flash/fastboot mode.it will automatically install drivers.wait for windows to say drivers installed successfully or installation failed. don't unplug it in the middle of the process then you will have to start from first.sometimes it will not work in the first time ,then reboot into safe mode and try again installing the drivers and rebooting into safe mode itself and connecting your device.at one point of time flashtool will say your device is connected in flas/fastboot mode.then continue with flashing
Gladwin.
Thanks for the support guys i managed to solve the issue!
^^^^ Glad i could help
Sent from my GT-I9300

[Q] USB Debugging Mode not recognized

I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Metaception said:
I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Click to expand...
Click to collapse
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Tigerlight said:
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Click to expand...
Click to collapse
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
Yes the toolkit uses ADB to automate the reboot into fastboot mode.
And my understanding is that enabling USB Debugging changes the drivers required so that you can access the ADB interface.
I rooted and installed my first ROM using the toolkit, idk y it's different now.
I will try to flash via fastboot and then ask in the toolkit thread as well since these driver are the ones that the came with the toolkit.
EDIT: Whhhhooaa, did it! Cheers for fastboot
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
If you want adb usb drivers, i prefer to install moborobo from Moborobo.com.
Start application,
Plug your device with usb debugging on.
and it will do the work.

[Q] Can someone provide me a guide how to root my T3??

I think i'm not the only one who wants to root the T3. There are many guides which are very complicated for people who are no software developers...
http://forum.xda-developers.com/xperia-t3/general/root-firmware-18-1-1-21-t2889847
If this is too complicated then probably you shouldnt even consider rooting - procedure cant be any easier. There isnt also any other way to root T3 ATM.
And yes, this works also with .25 (4.4.4 KK). And for different ver. of T3 (5102 for example) use software for your model as base.
Ditarius said:
http://forum.xda-developers.com/xperia-t3/general/root-firmware-18-1-1-21-t2889847
If this is too complicated then probably you shouldnt even consider rooting - procedure cant be any easier. There isnt also any other way to root T3 ATM.
And yes, this works also with .25 (4.4.4 KK). And for different ver. of T3 (5102 for example) use software for your model as base.
Click to expand...
Click to collapse
I think I know what to do. Can i use the sony Emma thing as the flash tool?
what to do now
I've installed adb drivers fastboot drivers and successfully flashed the .14 kernel then switched on the phone and trying to root using Xperia rootkit is not detecting my device and stuck like this(as shown in the screen shot) what to so and PC companion is also not detecting my t3 (but while am on .32kernel it works fine)
I've flashed the .32kernel (cause am on 4.4.4) again and repeated everything but same problem,, redownloaded the kernels but same problem,,
Why rootkit is not detecting my phone ??? Plz help
need help
While m on .14 kernel rootkit or PC companion were not able to detecting my phone. On switched off state(.14kernel) flash tool displayes that the USB debugging is off and the phone is connected in mtp mode..
But before flashing .14 kernel(while am on .32kernel) I turned on USB debugging and set the USB connection mode to MSC mode (otherwise flashtool wouldn't flash kernel)... So why am facing this problem???...
After flashing .14 kernel I switched on the phone and wait at least 10 minutes then (the screen shots only Sony logo and goes black) after ten minutes when I connect the phone to the PC and lunch rootkit its not detecting showing waiting for device PC companion is also not detecting:crying:...... What to do now
avayrocks said:
While m on .14 kernel rootkit or PC companion were not able to detecting my phone. On switched off state(.14kernel) flash tool displayes that the USB debugging is off and the phone is connected in mtp mode..
But before flashing .14 kernel(while am on .32kernel) I turned on USB debugging and set the USB connection mode to MSC mode (otherwise flashtool wouldn't flash kernel)... So why am facing this problem...
After flashing .14 kernel I switched on the phone and wait at least 10 minutes then (the screen shots only Sony logo and goes black) after ten minutes when I connect the phone to the PC and lunch rootkit its not detecting showing waiting for device PC companion is also not detecting:crying:...... What to do now
Click to expand...
Click to collapse
Hi. Before you flash .14 you need to enable usb debugging in your phone, connect it to your pc via usb cable and check the "allow always..." checkbox in your phone:
P.D. If the popup is not showing when you plug your phone, then open a terminal (cmd in windows), launch adb devices command and you should see the popup in your device. If does not, unplug the phone, stop adb, plug the phone again and try launching adb command.
did it
pepinliria said:
Hi. Before you flash .14 you need to enable usb debugging in your phone, connect it to your pc via usb cable and check the "allow always..." checkbox in your phone:
P.D. If the popup is not showing when you plug your phone, then open a terminal (cmd in windows), launch adb devices command and you should see the popup in your device. If does not, unplug the phone, stop adb, plug the phone again and try launching adb command.
Click to expand...
Click to collapse
Rooted bro thnkx for help

No ADB. No TWRP. No Magisk. Am I screwed?

Basically, I installed Havoc OS, tried flashing a couple kernels, kept getting systemui crashes, so I decided to dirty flash HavocOS again, and forgot to flash TWRP again before I exited TWRP.
Next, I boot back into my phone, opened Magisk Manager to find that Magisk is not installed, just the manager. I can't install Magisk as I have no TWRP...Which leads me to my next point, trying to boot into recovery brings me no avail as I forgot to flash TWRP. I have zero recovery right now.
Thirdly, HavocOS Suffers from the whole issue of needing SELinux set to permissive, for ADB to work...I can't do that, because I don't have Magisk/root.
Please tell me that someone has an idea here? I'd like to get TWRP back, or back to 100% stock and I can start over, or something other than a custom rom with serious SystemUI crashes and no root...
SOS!
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
As d-m-x stated boot twrp with fastboot boot not fastboot flash. Twrp will load into the phone then you can flash twrp and magisk.
I'd tried Fastboot already, will try again momentarily though.
D-m-x said:
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
Click to expand...
Click to collapse
Fastboot hasn't worked either. Unless I'm doing something wrong, but I just get "waiting for any device" despite having adb on/off, being in bootloader/fastboot mode or being booted into android, etc.
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
D-m-x said:
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
Click to expand...
Click to collapse
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Have you tried different USB A to USB C cables and ports?
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Az Biker said:
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Click to expand...
Click to collapse
Spoke with Google; getting the phone RMA. Blatantly told the guy it was rooted previously, bootloader unlocked, and running a custom ROM. He said it didn't matter. I will report back on this thread once I have new phone in hand, just to confirm all went well.
Reporting back.
Brought phone to virgin mobile, obviously still heavily modified.
Was given a loaner phone. Signed a paper saying I'd pay 150 for the loaner if it broke. Broke loaner screen same day.
Just picked up a brand new pixel 2 xl they shipped (phone only) because mine was considered unrepairable. I was charged 169 for the loaner phone, to my account with virgin. No cash transaction.
All in all, they honoured googles view of not minding the modifications so long as it's an issue they don't feel is related.
Cheers.

Categories

Resources