Develop Bugs

My next step...

I recently came into the possession of an Xperia Play and I have been left confused by the situation. The touch screen does not work but the buttons do... It is running the default modded Sony version of Android, It is a few months old and I have a feeling that it is a software problem rather than a hardware problem. I am wondering if there is any rooting method that would be suitable for my situation or should I just give up on the phone?
Any help would be appreciated

flash back to stock and check the touchscreen,

fma965 said:
flash back to stock and check the touchscreen,
Click to expand...
Click to collapse
It's not rooted and it's already running the stock version of aneroid. I'm trying to figure out if I could root it without being able to access the phone's settings. I believe installing third party apps is enabled. Should I just try superoneclick or would I risk bricking it

Yii don't need to have it rooted to flash back to stock...just download the stock.ftf and flash it via flashtool
Here is the link for flashtool http://forum.xda-developers.com/showthread.php?t=1351299
Here some stock fw http://www.xperiagamer.com/XXX-Zone/Stock-Roms/

cippi21 said:
Yii don't need to have it rooted to flash back to stock...just download the stock.ftf and flash it via flashtool
Here is the link for flashtool http://forum.xda-developers.com/showthread.php?t=1351299
Here some stock fw http://www.xperiagamer.com/XXX-Zone/Stock-Roms/
Click to expand...
Click to collapse
There's a problem with that too. Flashtool wont recognise that there's a device connected since I can access the "Allow USB" on my phone Can you think of any ways around that?

Pup_Skag said:
There's a problem with that too. Flashtool wont recognise that there's a device connected since I can access the "Allow USB" on my phone Can you think of any ways around that?
Click to expand...
Click to collapse
you realise flashtool requires the device to be in flashmode right? its either back or search during usb connected but i always get confused which 1 it is
Sent from my Samsung N130 Netbook powered by Android-x86

fma965 said:
you realise flashtool requires the device to be in flashmode right? its either back or search during usb connected but i always get confused which 1 it is
Sent from my Samsung N130 Netbook powered by Android-x86
Click to expand...
Click to collapse
Of course... that's embarrasing Right , ok ... I flashed 2.3.3 on it and the touchscreen still isn't working! hmmm... should I just give up on it or is there anything else I could do?

Pup_Skag said:
Of course... that's embarrasing Right , ok ... I flashed 2.3.3 on it and the touchscreen still isn't working! hmmm... should I just give up on it or is there anything else I could do?
Click to expand...
Click to collapse
my vote is hardware issue
Sent from my R800i using Tapatalk 2

agree possibly digitizer issue...in that case u can buy a cheap one on ebay

Root without micro-USB port

It's possible root my Xperia Arc without using the cable? My port don't work, the pins are broken.
I can connect to it by SSH, but idk if this helps...
Thanks.

Only if you have unlocked bootloader or a recovery(CWM) installed in the ROM's /system folder.
1st can not be done without micro-USB port, 2nd can be installed via Play Store.

Hmm, if the phone wasn't updated to latest gb or ics (no need to downgrade via flashtool) maybe it is possible to use wireless adb.
[email protected] S

wzearsdcx said:
Hmm, if the phone wasn't updated to latest gb or ics (no need to downgrade via flashtool) maybe it is possible to use wireless adb.
[email protected] S
Click to expand...
Click to collapse
I have the last version of official ICS of Sony.
It's possible to connect with ADB wirelessly without root, but I need to pair it before, connecting it with USB, and that's not an option for me.

elm390 said:
I need to pair it before
Click to expand...
Click to collapse
You don't need usb for wireless adb. But! You are updated so it won't help
[email protected] S

Just like they said, try wireless adb and execute script by bin4ry. With a little amount of luck you may succeed.
And BTW, thread moved to Q&A

Its possible do it with a non-rooted phone without conecting it before?? How can I do it? I didn't found a solution...

EDIT: See my next post.

I didn't found anithing about this. Its impossible connect with ADB by wireless if you are not root or you don't pair the device with the cable. I searched about this on Google hundreds of times, and there's no way!! If anyone another way, post it here pls.. But i repeat... i didn't found anything...

elm390 said:
If anyone another way, post it here pls.. But i repeat... i didn't found anything...
Click to expand...
Click to collapse
Well if you found nothing, no one else going to, so looks like the answer to your original question, is no.

elm390 said:
I searched about this on Google hundreds of times, and there's no way!! If anyone another way, post it here pls.
Click to expand...
Click to collapse
I said before - you have updated phone so nothing to do without flashtool downgrade. I forgot that wireless adb need root - my mistake.
Another way - repair phone. Don't waste more time trying, someone will install new usb port in few minutes for few $.
[email protected] S

Have you tried "z4root"?
http://forum.xda-developers.com/showthread.php?t=833953
::Neebz::

Moto z play stuck in fastboot

So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?

Somebodyz said:
So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?
Click to expand...
Click to collapse
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696

KrisM22 said:
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
Click to expand...
Click to collapse
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s

Somebodyz said:
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s
Click to expand...
Click to collapse
What version of RSD do you have - it's on the top bar when you stat RSD.

KrisM22 said:
What version of RSD do you have - it's on the top bar when you stat RSD.
Click to expand...
Click to collapse
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?

Somebodyz said:
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?
Click to expand...
Click to collapse
yes, now try a number of different cables. Make sure your phone is in fastboot mode.

That work?

KrisM22 said:
That work?
Click to expand...
Click to collapse
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?

Somebodyz said:
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?
Click to expand...
Click to collapse
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.

KrisM22 said:
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.
Click to expand...
Click to collapse
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?

Try to reflash the latest TWRP

mijing said:
Try to reflash the latest TWRP
Click to expand...
Click to collapse
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?

Somebodyz said:
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?
Click to expand...
Click to collapse
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it ?

mijing said:
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it
Click to expand...
Click to collapse
as i said i did try to reflash it and it gave me that message. and yea i did unlock the bootloader first.

Somebodyz said:
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?
Click to expand...
Click to collapse
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.

KrisM22 said:
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.
Click to expand...
Click to collapse
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message

Somebodyz said:
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message
Click to expand...
Click to collapse
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.

KrisM22 said:
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.
Click to expand...
Click to collapse
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)

Somebodyz said:
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)
Click to expand...
Click to collapse
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.

KrisM22 said:
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.
Click to expand...
Click to collapse
So adb devices doesnt let me see my device. but adb sideload works. only problem is, is: This package supports bootloaders: 0xc105, 0xC106, 0xC107, 0xC112, 0xC113 and this device has bootloader 0xc014. do i need an older version then or what should i do?
i just found this https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91, is that a good thing for me to do?

Help for Pixel 2 xl ota update

Hello everybody.
My pixel 2 xl non rooted with unlocked bootloader.
So, Is it possible to flash latest OTA update directly through the phone via stock recovery?
As you aware that with the known and common pixel 2 xl issue which you can't get it connected to PC.
I'm stuck on October update and I'd be glad if someone could help me out on this matter.
thanks in advance.

ahadon1 said:
Hello everybody.
My pixel 2 xl non rooted with unlocked bootloader.
So, Is it possible to flash latest OTA update directly through the phone via stock recovery?
As you aware that with the known and common pixel 2 xl issue which you can't get it connected to PC.
I'm stuck on October update and I'd be glad if someone could help me out on this matter.
thanks in advance.
Click to expand...
Click to collapse
Can't do OTA with unlocked bootloader you'll need to re lock it to do that

ahadon1 said:
Hello everybody.
My pixel 2 xl non rooted with unlocked bootloader.
So, Is it possible to flash latest OTA update directly through the phone via stock recovery?
As you aware that with the known and common pixel 2 xl issue which you can't get it connected to PC.
I'm stuck on October update and I'd be glad if someone could help me out on this matter.
thanks in advance.
Click to expand...
Click to collapse
tylermrsh said:
Can't do OTA with unlocked bootloader you'll need to re lock it to do that
Click to expand...
Click to collapse
Unfortunately, if you can't get pc to phone recognition, your kinda stuck. Have you tried revoking USB debugging to your pc then add it again? Tried uninstalling/installing your drivers? Tried multiple USB 2.0 cables and usb ports and/or another pc? If you can get into fastboot and install twrp you could flash the OTA that way as well. Best of luck to you.

Yes i did revoked it and tried many workaround solutions but unfortunately without luck.
So i thought if might be there's a solution without PC.
Thank you guys for the replies.

Badger50 said:
Unfortunately, if you can't get pc to phone recognition, your kinda stuck. Have you tried revoking USB debugging to your pc then add it again? Tried uninstalling/installing your drivers? Tried multiple USB 2.0 cables and usb ports and/or another pc? If you can get into fastboot and install twrp you could flash the OTA that way as well. Best of luck to you.
Click to expand...
Click to collapse
Tried all above but no luck ?
If someone could suggest any solution would be appreciated.

ahadon1 said:
Tried all above but no luck
If someone could suggest any solution would be appreciated.
Click to expand...
Click to collapse
You may have a broken usb-c port. You need to fix that first, and then re-lock.
My suggestion is that you send your Pixel for repair. If you search google with pixel 2xl usb-c port repair, you will certainly find some repair center near you.

when is the new security update for August out guys?

Just wondering when the new security update will be out as I feel the last one is making my battery drain quite a lot. Tried all the normal routine stuff and still nothing specially after two factory resets. Here is hoping that with the new software it will be fixed

Hey Goku80, judging solely by past-trends, it should most certainly be out today.

It's live guys! https://dl.google.com/dl/android/aosp/crosshatch-pq3a.190801.002-factory-15db810d.zip

Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?

BoboBrazil said:
Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?
Click to expand...
Click to collapse
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually

ota is not here yet

Goku80 said:
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually
Click to expand...
Click to collapse
The OTA can be flashed using stock recovery. No wipe.

spotmark said:
The OTA can be flashed using stock recovery. No wipe.
Click to expand...
Click to collapse
True but means I need to use ADB which I don't have a pc

Goku80 said:
True but means I need to use ADB which I don't have a pc
Click to expand...
Click to collapse
You can flash it as long as your BL is unlocked. It has nothing to do with root. You still need to use the flash-all batch file though, so a computer is still necessary.