Develop Bugs

[Q] Bricked? Can't switch on after deleting digital clock via Titanium

Hi
I seem to have bricked th phone...argh!
Delete system app DigitalClock.apk via Titanium. The phone restrted and showed an image of a opened box with an arrow and a moving bar underneath., After a few seconds all DARK and the phone is unresponsive.
Also tried to plug it and go to flash mode but nothing not led will switch on.
Any idea?
Alex

No idea what has happened, but simply removing that app didn't cause it.
You will probably have to reflash I'm afraid.
Sent from my LT15i using XDA App

Yea just from deleting the clock it wouldnt have bricked it flash a ftf again mate through flashtool
Sent from my HTC Desire using XDA Premium App

what you saw was the OTA screen.so you have accepted the OTA update.
locked or unlocked bootloader?
Regards
Sent from my LT15i using Tapatalk

Actually I did not. I just did what I said in the previous post and then the phone rebooted and bricked.
I already had fallen into the OTA update problem so I know what it is (see also my messages in the proper forum post. I assure you this was not it. It might be the problem but I did not accept any OTA update, it just went on its own from Titanium to that screen to brick.
I will try reflash tonight.
Cheers
Alex

[solved...almost]
I followed the procedure to unbrick the phone that apparently went into the FOTA update on its own. The phone works! But...
I can't install or update my apps.It says no spcace in the phone but I have 90Mb left. I also can't run Fix permission from ROM manager it says
"An erro occured while attempting to run provoleged commands!"
Ideas??
Thanks

SandroV1972 said:
I followed the procedure to unbrick the phone that apparently went into the FOTA update on its own. The phone works! But...
I can't install or update my apps.It says no spcace in the phone but I have 90Mb left. I also can't run Fix permission from ROM manager it says
"An erro occured while attempting to run provoleged commands!"
Ideas??
Thanks
Click to expand...
Click to collapse
try reflashing it with the flash tool

Do you mean reflash with the flashtool to unbrick it or reflash the entire firmware?

You'd be better of starting from scratch imo, so yes, re-write the whole firmware.

I feared you'd say that. I really don't understand why though this happens. I uninstalled the updates of my Market and now it doesn't install or update but it doesn't give me any error.
I get SU privileges but can't fix permissions from RomManager.

Flashed Firmware it works now!

Hi lord Bin4ry,
it seems we were both right. I installed the new firmware and out of curiosity tried to uninstall Chinese keyboard via Titanium. I got a message saying that it had to reboot twice to uninstall as NAND:
first rebott and...image of a box with a arrow coming out of it
then nothing, bricked again...
Si I did not accept any OTA update it seems to get into this state anytime I try to remove a system app via Titanium
Any idea?

That is weird bug. Do you have branded FW or Generic FW?

You fellow are rebooting into recovery mode, that much is certain.
Possible you have set up your Titanium to always reboot into recovery to make new nandroid backup?
I am browsing in CWM myself now, so what you speak of is so obvious. The question is now then why does your phone boot into recovery? What have you done to make it do that?

SandroV1972 said:
I installed the new firmware and out of curiosity tried to uninstall Chinese keyboard via Titanium. I got a message saying that it had to reboot twice to uninstall as NAND:
Click to expand...
Click to collapse
When removing apps with TB, it should be a short tap, I assume you're long pressing then "force removing"?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

New update for Canadian Optimus G users?

There seems to be an OTA update, and it's 10h.
Still ICS but comes with some bug fixes.
Anyone get their updates yet?

gbssengo said:
There seems to be an OTA update, and it's 10h.
Still ICS but comes with some bug fixes.
Anyone get their updates yet?
Click to expand...
Click to collapse
Bell/rogers/telus?
E971, E970, E973?
Unlocked with freegee?
did you update?
edit: im on rogers e971 and i also disabled/froze the LG update software

Nothing for Telus's E973...

Nothing here....Sastel E973

Have a Rogers E971, woke up to a software update.
Tried to update and was told that I could not due to root, removed root via SuperSU. Ran update again, update seemed to run but then rebooted and got a security error, Boot Certificate (I had unlocked boot loader via FreeGee, couldn't restore the FreeGee backup so decided to give it a go and see what happened).
Anyways, managed to recover via the "How to unbrick your optimus G" thread (http://forum.xda-developers.com/showthread.php?t=2010624), the software update now appears to be applied (at least it's no longer detecting an update but I'm not sure what version the update changed it to so I'm not sure how to check).
Obviously my bootloader is no longer unlocked and my device is no longer rooted. Tried to root again with the same method as before (Korean Batch File) and it no longer works. The device gets to the first reboot and then when it comes back up the cmd window says something about "access denied, is your device rooted?" and "Press any key to continue", at which point it exits.
Just my experience.

jpom18 said:
Have a Rogers E971, woke up to a software update.
Tried to update and was told that I could not due to root, removed root via SuperSU. Ran update again, update seemed to run but then rebooted and got a security error, Boot Certificate (I had unlocked boot loader via FreeGee, couldn't restore the FreeGee backup so decided to give it a go and see what happened).
Anyways, managed to recover via the "How to unbrick your optimus G" thread (http://forum.xda-developers.com/showthread.php?t=2010624), the software update now appears to be applied (at least it's no longer detecting an update but I'm not sure what version the update changed it to so I'm not sure how to check).
Obviously my bootloader is no longer unlocked and my device is no longer rooted. Tried to root again with the same method as before (Korean Batch File) and it no longer works. The device gets to the first reboot and then when it comes back up the cmd window says something about "access denied, is your device rooted?" and "Press any key to continue", at which point it exits.
Just my experience.
Click to expand...
Click to collapse
thanks for the heads-up man
in my opinion:
nope nope nope
also maybe try the latest version of Bin4ry's
http://forum.xda-developers.com/showthread.php?t=1886460
might help
---------- Post added at 11:06 AM ---------- Previous post was at 10:58 AM ----------
http://mobilesyrup.com/2012/12/18/s...rings-stability-and-performance-improvements/
seems this is the update they are talking about
for bell and rogers atm

jpom18 said:
Have a Rogers E971, woke up to a software update.
Tried to update and was told that I could not due to root, removed root via SuperSU. Ran update again, update seemed to run but then rebooted and got a security error, Boot Certificate (I had unlocked boot loader via FreeGee, couldn't restore the FreeGee backup so decided to give it a go and see what happened).
Anyways, managed to recover via the "How to unbrick your optimus G" thread (http://forum.xda-developers.com/showthread.php?t=2010624), the software update now appears to be applied (at least it's no longer detecting an update but I'm not sure what version the update changed it to so I'm not sure how to check).
Obviously my bootloader is no longer unlocked and my device is no longer rooted. Tried to root again with the same method as before (Korean Batch File) and it no longer works. The device gets to the first reboot and then when it comes back up the cmd window says something about "access denied, is your device rooted?" and "Press any key to continue", at which point it exits.
Just my experience.
Click to expand...
Click to collapse
Can you take a couple of pictures with ISO @ Auto to see if they fixed it?
Thanks!

t1mman said:
Can you take a couple of pictures with ISO @ Auto to see if they fixed it?
Thanks!
Click to expand...
Click to collapse
I can do that, is there anything specific that I should be looking for or that you would like to see? I almost never take pictures and have never used the camera on here, I didn't even know that there was an issue.

t1mman said:
Can you take a couple of pictures with ISO @ Auto to see if they fixed it?
Thanks!
Click to expand...
Click to collapse
any work around if we dont want to update yet

I got fed up for I cannot restore the KDZ (Not responding stuff). I tried the hard mode method of using LG's support tool and it downloads a whole ROM! Will keep you posted.
EDIT: Yes you cannot root ATM.

BloodBaron said:
any work around if we dont want to update yet
Click to expand...
Click to collapse
I used Titanium Backup pro to freeze the Software Update app. Seems to take away the notification and no problems thus far.
If you don't have TBpro, you can just slip into the app info in the settings menu and disable it from there. (Settings > Apps > List All, find Software Update, disable.
Freezing is the same as disabling as far as I can tell.

yes and you cannot root atm....LOL!

So its safe to say disable the lg update software?
Sent from my LG-E971 using xda premium

BloodBaron said:
So its safe to say disable the lg update software?
Sent from my LG-E971 using xda premium
Click to expand...
Click to collapse
yes just "Disable" via Settings > Apps > Software Update > Tap Disable.
Not Freeze via any root apps.
So I am gonna suffer from being unrooted ATM but no biggy. Good thing LG (and most manufacturers) has a stock app back-up tool in place of TB.

Absolutely nothing for TELUS OGs.. -_-

For those that are wondering what is in the update (for Bell at least):
Code:
Short description
A software update is now available for the LG Optimus G, and Bell strongly recommends that customers update their device to ensure the best possible experience.
Dates
Start date: Tuesday, December 18, 2012
Description
Software update version [V10h] includes device improvements to stability and performance including:
•Google security patch
•Improved touch response while charging
•Fixed exchange email setup to avoid customer confusion
Procedure

Has anyone successfully backed up su by copying it to various directories before updating?
I've put a copy in /system/etc, /system/bin, /data, /data/data, & /cache. I'm hoping one of those will still be there after the update.
Problem for me right now is no update is showing up when I check.
Anyone wanting to try doing this backup make sure you copy the su binary with the - p flag to keep setuid/setgid. I'd also recommend renaming the backup to something other than 'su'.

xxbeanxx said:
Has anyone successfully backed up su by copying it to various directories before updating?
I've put a copy in /system/etc, /system/bin, /data, /data/data, & /cache. I'm hoping one of those will still be there after the update.
Problem for me right now is no update is showing up when I check.
Anyone wanting to try doing this backup make sure you copy the su binary with the - p flag to keep setuid/setgid. I'd also recommend renaming the backup to something other than 'su'.
Click to expand...
Click to collapse
IMHO, the software update wipes /system and /cache (not /data in my experience) so everything you put in those directories will be wiped out. Those SU files though are in the zip if you used Bin4ry's rooting tool, and you can download it from androidsu.com (just unzip these files and you should be able to see them).

jpom18 said:
I can do that, is there anything specific that I should be looking for or that you would like to see? I almost never take pictures and have never used the camera on here, I didn't even know that there was an issue.
Click to expand...
Click to collapse
Something collorfull with not much lights, to see if it gets a grainy feel like this (with AutoISO)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or colourfull clean image like this (with Manual Iso)
Thanks!

gabby131 said:
IMHO, the software update wipes /system and /cache (not /data in my experience) so everything you put in those directories will be wiped out. Those SU files though are in the zip if you used Bin4ry's rooting tool, and you can download it from androidsu.com (just unzip these files and you should be able to see them).
Click to expand...
Click to collapse
The problem is that some people are reporting that Bin4ry's recovery exploit is no longer working after the update.

[Q] GT-N7105T - Telstra (Australia) Note 2, stalled during CF-Auto-Root

Hi All,
Just trying to find some people who've managed to root the Australian version of the Note 2 successfully? I have the Telstra Galaxy Note 2 (GT-N7105T) and sat down this afternoon to root using CF-Auto-Root.
I got to the part where the phone is in download mode after pressing the volume up to proceed (other option is to press volume down for exit & reboot). I did not change any settings in Odin, plugged the Note 2 into USB and hit Start in Odin (after selecting the CF-Auto-Root package... everything exactly as the instructions state), then it took a few minutes before it gave the "<ID:0/003> Added!" message. Since then it's been sitting for about an hour at the same screen both on the Note 2 and in Odin... getting a bit worried because Chainfire said this should only take 30 seconds..?!
Current Odin screenshot, it's been about 1 and a half hours now on this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hoping some others with rooting experience can help out – did I miss a step? In any case I don't think it's going to progress, so how should I exit out? Hit Reset in Odin? Just unplug the USB cable and try to reboot? Or a hard reset?
Cheers for any advice!

you have used the tar for normal lte version not telstra version.
if you have a nandroid then restore it.
i am not sure if you should or shouldn't disconnect cable of your phone...

Cheers for the reply UtkarshGupta.
I did a bit more research and found that I needn't have been so worried... I thought that maybe it had froze part way through flashing, but the ID:COM shows that it had only just connected with the device and hadn't done anything else! (Of course I only knew this after doing more research on Odin.) Probably because I plugged in the USB then clicked Start in Odin - the PC was still installing drivers and ID:COM wasn't lit up yellow at that stage, soo... it was okay to pull the USB cable, then I just held the power button to exit download mode.
But now the experience has me spooked - not sure if I should try again, or whether I should wait for a Telstra-specific root method that's been tested. After all this variant phone was only released two days ago here in Australia...

mugget said:
Cheers for the reply UtkarshGupta.
But now the experience has me spooked - not sure if I should try again, or whether I should wait for a Telstra-specific root method that's been tested. After all this variant phone was only released two days ago here in Australia...
Click to expand...
Click to collapse
I don't believe you have a problem with the ROM. Your problem is that you're running an old version of Odin3.
I received my N7105T the same day as you did and performed the root procedure first thing, using the same ROM as you have but Odin3 v3.04. No problem.
Two things though:
1) Be sure that you've installed the latest Kies to ensure the latest and greatest drivers are running.
2) Make sure after you've installed Kies that it's not running as it will otherwise not allow connection to the COM port established through the USB lead.
You shouldn't have any problems performing the procedure based on this information.

Hey Artstar,
Thanks for the info. After you mentioned the process you used (the same CF Auto Root package) I was more confident that wasn't the problem.
I have just successfully rooted using the same process as previously, except for waiting to be sure that COM was established (yellow COM box), and I also did install Kies for the USB drivers just to be sure (then uninstalled Kies).
The only thing now is that I get a message when trying to use Triangle Away (Play store version), it says "Could not find hidden partition. Are you not using ICS?" How did you get around that? I have not upgraded or done anything to the phone, it's still running Android 4.1.1.

How did you go?
I just got the note 2 LTE as well and want to root it.

Hey shawn, everything is a-okay now as far as the binary count goes... There have since been a couple of updates to Triangle Away and one of them was for compatibility with GT-N7105T (which is the model I have). So I ran Triangle Away and there were no problems there since the update. Although I haven't actually checked the binary count myself... but I got to the stage where I would rather have root, I didn't really care about the counter.
Depending how badly you want to root, you may just want to go ahead. There shouldn't be any problems there (just make sure you use a compatible package/method for your phone). However if you want to still get back to warranty you might want to double-check your exact phone model with some others who've rooted the same phone. (I'm not sure how many different models of LTE Note 2's are out there.)
Hope that helps!

[Q] Bricked, and Broken (mentally)

Hello internet, I'm a noob, so excuse my noobiness. Basically, I've managed to "brick" my SGH-T989D, also known as a Samsung Galaxy S2X, or Hercules; I'm on the Koodo network, and using 4.1.2 which I acquired from Kies. I was attempting to flash TWRP to achieve root using Odin as suggested by this website:
http://www.androidayos.com/2013/04/29/root-t989dtlumc4-samsung-galaxy-sii-sgh-t989d-teluskoodo-jelly-bean-4-1-2/
I followed the instructions, but Odin failed in the middle of the flashing. Now I'm stuck with this screen (not my picture):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One of the attachments is a screen shot of my "About Device" information from before I was bricked. I've tried flashing multiple stock ROMs through Odin, typically with a name similar to "T989DTLUMC4_T989DOYBMC4_KDO", but it consistently fails. The point at which it fails varies, and I'm not confident about what's causing the failure, but I've noticed it tends to hang up on "<ID:0/003> SetupConnection..", or fails at "<ID:0/003> Complete(Write) operation failed.". I'll attach a screenshot of what Odin looks like upon failure with the message box clearly visible. I don't have any recovery files, because, ironically, I was bricked while flashing a recovery to prevent bricking. Also, I'm open to trying things other than Odin.
I'd like assistance to get my phone back to a usable state (at least able to make calls, and text). I would be especially grateful if it ended up rooted, and/or with a safe method of flashing, and trying custom ROMs (I eventually wanted to have Cyanogen mod 10.1, and Clockworkmod Recovery). However, any help is appreciated; Thank you for your time.

TRY
You need to search for ODIN version 1.85... hard to tell what you're using but it looks very different from mine. ill try to attach a good copy of it. The one i used was nice.
In the mean time... have you gone into Kies and at the top select "tools" and "emergency recovery" or somethign similar to those words? that WILL restore your device to a usable state... that's guaranteed.

Droid8Apple said:
You need to search for ODIN version 1.85... hard to tell what you're using but it looks very different from mine. ill try to attach a good copy of it. The one i used was nice.
In the mean time... have you gone into Kies and at the top select "tools" and "emergency recovery" or somethign similar to those words? that WILL restore your device to a usable state... that's guaranteed.
Click to expand...
Click to collapse
Hey! thanks for the reply. I was using Odin v3.07. I have a couple of screenshots for you. Kies wants me to provide a recovery code (screenshot), which is not given to me. I believe that option only works if your phone was bricked while updating using Kies. Also, Kies doesn't seem to be connecting to my phone. It never advances from the connecting screen (screenshot), and seems to give up when I navigate to different menus. This is probably due to the current state of my phone. Lastly, I downloaded Odin v1.85, but the flashing failed with a similar error (screenshot). I hope you have more ideas.

IT WORKED!! (screenshot) I don't know what's changed since the last time I tried it; why is Odin so inconsistent? Regardless, thank you to Droid8Apple, and XDA forums. There is a lot for me to learn in unlocking the potential of my android device.

Coltonkoop said:
IT WORKED!! (screenshot) I don't know what's changed since the last time I tried it; why is Odin so inconsistent? Regardless, thank you to Droid8Apple, and XDA forums. There is a lot for me to learn in unlocking the potential of my android device.
Click to expand...
Click to collapse
You have to make sure Kies is disabled before using Odin, it'll cause Odin to either not recognise or fail.
T989D
latest CM10.1
latest Uber nightly

noob41 said:
You have to make sure Kies is disabled before using Odin, it'll cause Odin to either not recognise or fail.
T989D
latest CM10.1
latest Uber nightly
Click to expand...
Click to collapse
Thank you for the advice; I'll certainly remember that. By disabled do you mean simply closed (clicking the red "X" at the top right), or is there something further I need to do like kill processes in the task manager, for example?

How to downgrade from Android Q beta

My Pixel 2XL has locked bootloader and from yesterday I'm having some issues with touchscreen not responding. I spill some coffee on display - just a few drops of cold coffee - but quickly wiped out. The phone was OK, but in the evening the touchscreen stopped working. My first impression was that's a beta issue and so I manually wiped device but it didn't help, the screen is still not reacting.
So before I tear device to see it's not a hardware issue I would like to try to downgrade to stable android 9. Because bootloader is locked my only option is to update/downgrade via ADB, but because official OTA for Android 9 is older ADB is not allowing me to downgrade.
From what I read, rolling back to stock involves sing-off from the beta program on Google's website and wait for another OTA to revert to stock, but because I wiped the device and can't even set the system up and running I won't get it.
Maybe someone can provide such OTA file? Or maybe I'm doing something wrong.
Please, guys, help me out.

Files are here https://developers.google.com/android/images

Droid_Nut said:
Files are here https://developers.google.com/android/images
Click to expand...
Click to collapse
Because my bootloader is locked I just can't flash system image and so far there's no method to unlock Verizon variant. Only OTA newer than Q beta4.

What happens when you try to wipe/format data from the recovery partition? Having a corrupt system/OS shouldn't have affected the recovery partition and/or the ability to format and wipe it to a stock state...
But, if anything, you might have some luck downloading the OTA system image (can still be found at the developers site of Google's), loading up the stock recovery (don't worry if you get a dead droid with an exclamation/triangle, it's supposed to show that, you just need to hold Power + Volume-Up at the same time), and running through the selection of "Apply update from update" and/or "Apply update from .zip" where you can now either point to the OTA .zip manually or "push" the file onto your device...
Using the stock recovery to either wipe/format the device or manually applying the OTA seems to be the only rescue method available to locked bootloader devices...
Good luck to you and I hope this helps...

Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770

Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.

Edmontonchef said:
Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.
Click to expand...
Click to collapse
My touchscreen doesn't work, so I can't pass the initial set-up.
I just hope Google will release DP5 within a couple of weeks. Or maybe the touchscreen is broken? I guess I have to wait.
BTW Now I'm rocking old Lumia 550 on WM10 and it's a real pain in the a.ss without google services.

lywyn said:
Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770
Click to expand...
Click to collapse
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.

Maybe someone could upload it's "un-roll" OTA. So I could try to flash it and find out is it software or hardware issue.

adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...

adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."

lywyn said:
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."
Click to expand...
Click to collapse
I know that, but IP rating doesn't mean that your phone is absolutely 100% safe, and maybe this time I got run out of luck.
I'm just patiently waiting for beta 5 to be announced and then we'll see.

simplepinoi177 said:
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...
Click to expand...
Click to collapse
It's exactly like You said. I'm able to flash Android Q beta DP4 OTA, but after rebooting I'm stuck at welcome screen and the touchscreen doesn't work.
But once, when I removed the SIM card and popped it right back, a popup window for SIM unlock appeared and I was able to input pin (after that screen got frozen), so I believe that's not a hardware issue. I just have to wait for DP5 and find out is it gonna help or not.

Use an external mouse via USB adapter to pass the welcome screen etc

siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
I didn't know that. Thanks for the tip.

siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
So I did. With the mouse, I was able to sign in Google account and unroll from the beta program. I immediately received OTA with android 9 form June, but after a downgrade, my touchscreen still doesn't work.
How the heck is it possible? The screen is connected to the motherboard with only one ribbon, so if that ribbon would be defective, the screen should not turn on or have some artifact.
So far it's working OK, except for some strange glitch with "day widget".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any suggestions? Should remove the screen and see what's inside? I guess that's the only option left.

Probably your screen is broken and you need a new one. Warranty?

siggey said:
Probably your screen is broken and you need a new one. Warranty?
Click to expand...
Click to collapse
Nop, device bought in Best Buy i NY. So would have to bring it overseas from Europe, because in my country Google doesn't sell devices.