Related
I have a t-mobile Galaxy s4 that is rooted and uses TWRP 2.6.3.0. The recovery keeps hanging at the Teamwin Blue screen. I downloaded the flashable TWRP 2.5 which is said to be more stable so can I just flash this with Goo Manager or will I have to remove the TWRP 2.6.3.0 first. If so how can I downgrade
Just flash in twrp like you would a Rom but don't do any wipes
No Boot into revcovery
I flashed the TWRP but when I try to go into recovery it opens to the Samsung screen with the blue writing and then it turns off, vibrates twice and boots normally. I did not wipe as you instructed
josephh71 said:
I flashed the TWRP but when I try to go into recovery it opens to the Samsung screen with the blue writing and then it turns off, vibrates twice and boots normally. I did not wipe as you instructed
Click to expand...
Click to collapse
Download 2.5.0.2 version tar here http://www.teamw.in/project/twrp2 click on Get TWRP for your device and type s4 and click on T-Mobile version jfltetmo, you should flash it through Odin. Whenever you flash another recovery to your phone, it replaces the older recovery.
Where did you get the 2.5 twrp? I flash between different versions of twrp and cwm often.
Here is the post for twrp 2.5.0.2 zip also. http://forum.xda-developers.com/showpost.php?p=43469920
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
jd1639 said:
Where did you get the 2.5 twrp? I flash between different versions of twrp and cwm often.
Click to expand...
Click to collapse
SERIOUSLY?!?!
I just explained to you in the post, did I just waste my time? You can get it by yourself in the future by following my instructions, ANY version, tar or img is on their site.
josephh71 said:
I flashed the TWRP but when I try to go into recovery it opens to the Samsung screen with the blue writing and then it turns off, vibrates twice and boots normally. I did not wipe as you instructed
Click to expand...
Click to collapse
Some people have huge issues with TWRP I know I did. You might want to flash CWM touch. I did and haven't had a problem since. You can easily download and flash from Rom manager. You can get that from play store. It will give you latest version of cwm touch. Easily. It should solve your recovery problems.i know it solved mine. Don't know why some can use twrp and others have nothing but problems with it. I know I couldn't use it.i needed a stable recovery and twrp was NOT stable for me. CWM touch had never given me a problem once..it might be time to give CWM touch a try...it worked out really great for me.
norml said:
Here is the post for twrp 2.5.0.2 zip also. http://forum.xda-developers.com/showpost.php?p=43469920
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
SERIOUSLY?!?!
I just explained to you in the post, did I just waste my time? You can get it by yourself in the future by following my instructions, ANY version, tar or img is on their site.
Click to expand...
Click to collapse
What? that was meant for the op
jd1639 said:
What? that was meant for the op
Click to expand...
Click to collapse
Why don't you use features like "reply , like you just did by quoting me, or is this a special thread for just you two? San Fransisco thing going on here, LOL? You can just ask any question and everyone automatically knows who it is directed to?
norml said:
Why don't you use features like "reply , like you just did by quoting me, or is this a special thread for just you two? San Fransisco thing going on here, LOL? You can just ask any question and everyone automatically knows who it is directed to?
Click to expand...
Click to collapse
You snuck you post in on me while I was writing lol. No worries
jd1639 said:
You snuck you post in on me while I was writing lol. No worries
Click to expand...
Click to collapse
If you two want to be alone, hey, to each their own. JK
Working great!
Thanks for the update. I finally got it installed and working. I really appreciate your help
Thank you
thanks for all the help. I finally got it working. I initially got the dl from another link in the help section but when I flashed it I couldnt get into recover so I just followed the instructions and now it works.
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Thanks for the reply.
Are you sure what happened to is exactly what happened to you? Because I tried the ToolKit and it is not working. I tried both the versions of the TWRP and Stock recovery.
If you know anything else about this issue that would help me. I'd love to hear it.
SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Also. Does encryption affect this in anyway, because I did it. I don't want to factory reset my phone because this is my primary phone and I don't have another phone. And I don't want to risk it, at least for a few days.
malachiseelam said:
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Click to expand...
Click to collapse
Modified TWRP version should do it
Same, when I flashed cm 14.1 I also got blank TWRP.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Then, what did you do?
LS.xD said:
Modified TWRP version should do it
Click to expand...
Click to collapse
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
malachiseelam said:
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
Click to expand...
Click to collapse
Thanks it worked!
Please try the modified TWRP, 3.0.2-22
I am looking for some testers for my rom on Pixel XL, we currently have a build up on https://temp.bbqdroid.org/
It is a flashable zip and you should have a backup from twrp on your pc before flashing.
To keep TWRP you will likely need to flash ROM + Gapps, TWRP zip and then supersu.
Tester hangout: https://hangouts.google.com/group/5Ymr3GHPJdMUcf5j1
I'm getting page cannot be displayed.
pro_b said:
I'm getting page cannot be displayed.
Click to expand...
Click to collapse
Same here brother...I'm guessing we should give it a little more time?
pro_b said:
I'm getting page cannot be displayed.
Click to expand...
Click to collapse
BakedTator said:
Same here brother...I'm guessing we should give it a little more time?
Click to expand...
Click to collapse
sorry correct link is https://temp.bbqdroid.org
Thanks. Downloading now. I've been off the aosp scene for a while. Would anyone have a link to the gapps needed for this rom?
pro_b said:
Thanks. Downloading now. I've been off the aosp scene for a while. Would anyone have a link to the gapps needed for this rom?
Click to expand...
Click to collapse
Try opengapps aroma, 7.1 arm64, you may need to install webview, if you need further assistance there is a hangouts group https://hangouts.google.com/group/5Ymr3GHPJdMUcf5j1
mdalexca said:
Try opengapps aroma, 7.1 arm64, you may need to install webview, if you need further assistance there is a hangouts group https://hangouts.google.com/group/5Ymr3GHPJdMUcf5j1
Click to expand...
Click to collapse
Matt, will that flash in TWRP? Wasn't sure a payload OTA could be recovery flashed. At least not without modification of the script.
---------- Post added at 05:44 AM ---------- Previous post was at 05:26 AM ----------
pro_b said:
Thanks. Downloading now. I've been off the aosp scene for a while. Would anyone have a link to the gapps needed for this rom?
Click to expand...
Click to collapse
Just a heads up. I looked at the script and if you want to flash it , you'll need to adb sideload it as the script needs modification for TWRP.
How well does the build work? OMS Full? As on the 6P?
Or better asked, what does not work? I like the Rome on the N6P and would like to use it here but at the moment much work and no time to test. A short answer would be nice, thanks.
Tylog said:
How well does the build work? OMS Full? As on the 6P?
Or better asked, what does not work? I like the Rome on the N6P and would like to use it here but at the moment much work and no time to test. A short answer would be nice, thanks.
Click to expand...
Click to collapse
flash it and you will see
Sent from my Google Pixel XL using XDA Labs
I am working on a new build right now.
Ok:good:
Sent from my Pixel XL using XDA Labs
Will there be a pixel build?
freddienuxx said:
flash it and you will see
Click to expand...
Click to collapse
Read what I say and understand.
zaksimmermon said:
Will there be a pixel build?
Click to expand...
Click to collapse
Yeah, just getting marlin working first since I have the device
I tried flashing the zip in TWRP RC1 and there were no errors but TWRP says there is no OS installed.
Can't seem to get ADB sideload working on my computer to try that method.
---------- Post added at 03:30 PM ---------- Previous post was at 03:03 PM ----------
No OS installed after doing ADB sideload either.
HTML:
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>adb devices
List of devices attached
HTxxxxxxxxx sideload
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>adb sideload uber_marlin-2016-12-20.zip
Total xfer: 1.00x
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>
EDIT: My file size is only 215MB so I probably got a bad download. doh.
EDIT 2: Nope, re-downloaded and got same exact file size.
CZ Eddie said:
I tried flashing the zip in TWRP RC1 and there were no errors but TWRP says there is no OS installed.
Can't seem to get ADB sideload working on my computer to try that method.
---------- Post added at 03:30 PM ---------- Previous post was at 03:03 PM ----------
No OS installed after doing ADB sideload either.
HTML:
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>adb devices
List of devices attached
HTxxxxxxxxx sideload
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>adb sideload uber_marlin-2016-12-20.zip
Total xfer: 1.00x
C:\Users\xx\AppData\Local\Android\sdk1\platform-tools>
EDIT: My file size is only 215MB so I probably got a bad download. doh.
EDIT 2: Nope, re-downloaded and got same exact file size.
Click to expand...
Click to collapse
That's how TWRP always reads, it even has this problem with DU from what I read, I am working on a new build, I just need to upload it now
mdalexca said:
That's how TWRP always reads, it even has this problem with DU from what I read, I am working on a new build, I just need to upload it now
Click to expand...
Click to collapse
If you wipe system then flash the rom when you go to reboot it will say no OS installed. When you flash the rom it's flashing to the other partition so no need to wipe system and when you reboot it switches slots. If you just factory reset you won't get the no OS installed message.
Interesting.
Yeah, I did wipe /system.
Guys, its a bit ot but i had the following issue with installing DU on my sailfish:
I wiped System, data, Cache, flashed DU and so on... Then twrp said no OS installed. Ich accidentally rebooted system and did not reboot bootloader.
Screen turned off, hard brick because twrp (or what Else?) swapped boot partition to b (no bootloader installed).
As you can imagine, im pretty frightened to flash anything but weta rom for now on my new pixel (google rma...).
Is this caused by twrp, du or what?
blaze9090 said:
Guys, its a bit ot but i had the following issue with installing DU on my sailfish:
I wiped System, data, Cache, flashed DU and so on... Then twrp said no OS installed. Ich accidentally rebooted system and did not reboot bootloader.
Screen turned off, hard brick because twrp (or what Else?) swapped boot partition to b (no bootloader installed).
As you can imagine, im pretty frightened to flash anything but weta rom for now on my new pixel (google rma...).
Is this caused by twrp, du or what?
Click to expand...
Click to collapse
It's impolite to talk about an issue with DU in the thread dedicated for a totally different ROM.
You may want to post this question over in the TWRP thread.
In the Sailfish forum, btw. You're in the Marlin forum right now. lol
Mi 5
Fastboot 1709M
http://bigota.d.miui.com/7.1.19/gem...19_20170119.0000.00_7.0_global_409e0dc1a0.tgz
Recovery 1438M
http://bigota.d.miui.com/7.1.19/miui_MI5Global_7.1.19_668b027f8d_7.0.zip
Any success with recovery so far? I'll test in a few hours and report back
Installed the latest version via updater app few hours agi. So far everything is fine, no noticable differences.
Can I flash this over LineageOS? Or I need to revert back to MIUI 6.11.10 and then this one through updater?
And, is it nougat based?
verma.avesh said:
Any success with recovery so far? I'll test in a few hours and report back
Click to expand...
Click to collapse
I can't install via recovery... A few of attempts and was impossible ? ...always gave me errors very confused.
neodante said:
I can't install via recovery... A few of attempts and was impossible ? ...always gave me errors very confused.
Click to expand...
Click to collapse
If possible, try flashing 6.11.10 and update this over MIUI. Hope that'll help. I might have tested anyways, but exam on Monday so..
verma.avesh said:
If possible, try flashing 6.11.10 and update this over MIUI. Hope that'll help. I might have tested anyways, but exam on Monday so..
Click to expand...
Click to collapse
Well, maybe days later, just configured other rom.
After OTA update to 7.1.19 , 4K video is, flickering , i tried all 4 settings (50 ,60hz ,none and auto) . Only on 4K video . Before update in same lighting condition I have no problem
Ok guys
After update to this rom I'm bit lost
I was on custom 7.1.1 with TWRP before.
I did fresh start and tried flash this rom from TWRP. No luck
Then I have flashed xiaomi.eu_multi_MI5_6.10.27_v8-6.0.zip and after boot I have rebooted to recovery (still TWRP) and I have flashed the above rom and this time with luck. After successful boot, I have noticed few FC on for example Music.
No I have lost TWRP, can't go back to my TWRP backup.
Wish I never try lol
How do I start again? How do I flash TWRP?
Thanks
demo84 said:
Ok guys
After update to this rom I'm bit lost
I was on custom 7.1.1 with TWRP before.
I did fresh start and tried flash this rom from TWRP. No luck
Then I have flashed xiaomi.eu_multi_MI5_6.10.27_v8-6.0.zip and after boot I have rebooted to recovery (still TWRP) and I have flashed the above rom and this time with luck. After successful boot, I have noticed few FC on for example Music.
No I have lost TWRP, can't go back to my TWRP backup.
Wish I never try lol
How do I start again? How do I flash TWRP?
Thanks
Click to expand...
Click to collapse
Fastboot flash recovery recovery.img
Yeah after few hiccups I'm back to main TWRP backup
Glad I did keep that on my Pc
I had problem with TWRP and encryption that lead me to clear off my phone ?
demo84 said:
Ok guys
After update to this rom I'm bit lost
I was on custom 7.1.1 with TWRP before.
I did fresh start and tried flash this rom from TWRP. No luck
Then I have flashed xiaomi.eu_multi_MI5_6.10.27_v8-6.0.zip and after boot I have rebooted to recovery (still TWRP) and I have flashed the above rom and this time with luck. After successful boot, I have noticed few FC on for example Music.
No I have lost TWRP, can't go back to my TWRP backup.
Wish I never try lol
How do I start again? How do I flash TWRP?
Thanks
Click to expand...
Click to collapse
That happened to me too... Thank goodness that I did not lose the recovery and then installed a 6.0.1 rom ( AICP )
I AM DEFINITELY TIRED OF TO TEST NOUGAT MI5 ROMS !! All have performance problems and bugs, there isn't any that works as good as marshmallow roms.
flashing the fastboot rom will lock the bootloader ?
Ok so I thought full TWRP backup (over 6GB) will back up my photos
Nope I lost all my data
Did anybody has stuttering issue on this after flashing SuperSU?
Is this Nougat based?
Bimalhort said:
Is this Nougat based?
Click to expand...
Click to collapse
Yes... Android 7.0
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
demo84 said:
Ok so I thought full TWRP backup (over 6GB) will back up my photos
Nope I lost all my data
Click to expand...
Click to collapse
TWRP backs up the system partition not the internal storage
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
chhapil said:
Did anybody has stuttering issue on this after flashing SuperSU?
Click to expand...
Click to collapse
No issues here
I made OTA upgrade . After hard reset problems remaining are bad GPS precision and banding only in 4k video at inside light (I tested all anti band settings)
harrez said:
flashing the fastboot rom will lock the bootloader ?
Click to expand...
Click to collapse
Only if you tell MiFlash to do so after flashing.
So I messed up my Pixel 3 XL. When trying to root, I flashed TWRP on the device and it gave all kinds of problems. I could not boot at all.
I then flashed what I thought to be stock boot.img. Now it boots (only while unlocked) and takes me to the welcome screen. It boots with no issues but now the touchscreen doesn't work.
I've tried to revert back to stock many, many times using the guide here & factory image. All is successful except the boot.img - says FAILED.
I suspect that I need to flash boot.img again but no clue how....
Any help is greatly appreciated!
Flash the factory image, wipe and start over.
or
Flash the factory image with wipe removed, backup what ever you forgot.
Then
Flash factory image with wipe and start over.
parakleet said:
Flash the factory image, wipe and start over.
or
Flash the factory image with wipe removed, backup what ever you forgot.
Then
Flash factory image with wipe and start over.
Click to expand...
Click to collapse
Trying now. Like I said though, I have tried to flash the factory image, wiping and not wiping. I am not concerned about backup data, just want it to work.....
Thanks for the input!
Even though this is the 20th time I've done that, still the touch screen does not work when bootloader is unlocked but boots to welcome screen. Once bootloader is locked, it says no operating system found and will not boot. Anyone else with a suggestion?
rpolito73 said:
Even though this is the 20th time I've done that, still the touch screen does not work when bootloader is unlocked but boots to welcome screen. Once bootloader is locked, it says no operating system found and will not boot. Anyone else with a suggestion?
Click to expand...
Click to collapse
Try flashing the binaries from google.
biggiesmalls657 said:
Try flashing the binaries from google.
Click to expand...
Click to collapse
Going to google how to. Any guides on how to? Thanks for the input!
I think this is what I need. I bet the touch sensors are in the Qualcomm pack. Just dont know how to flash....
rpolito73 said:
Going to google how to. Any guides on how to? Thanks for the input!
I think this is what I need. I bet the touch sensors are in the Qualcomm pack. Just dont know how to flash....
Click to expand...
Click to collapse
You can't flash a binary. They're there to build custom roms. I always ask because so many people miss this, but do you have the latest sdk platform tools, r28?
Sent from my [device_name] using XDA-Developers Legacy app
This same thing happened to me. Make sure you're using the latest versions of ADB and Fastboot and try flashing the factory image again. I think that is what fixed mine.
rpolito73 said:
So I messed up my Pixel 3 XL. When trying to root, I flashed TWRP on the device and it gave all kinds of problems. I could not boot at all.
I then flashed what I thought to be stock boot.img. Now it boots (only while unlocked) and takes me to the welcome screen. It boots with no issues but now the touchscreen doesn't work.
I've tried to revert back to stock many, many times using the guide here & factory image. All is successful except the boot.img - says FAILED.
I suspect that I need to flash boot.img again but no clue how....
Any help is greatly appreciated!
Click to expand...
Click to collapse
Have you tried using this??
https://forum.xda-developers.com/pi...ool-crosshatchdb-one-pixel-3-xl-tool-t3864644
rpolito73 said:
Trying now. Like I said though, I have tried to flash the factory image, wiping and not wiping. I am not concerned about backup data, just want it to work.....
Thanks for the input!
Click to expand...
Click to collapse
... slow down and read more. double check the basics... and for God's sake stop re-locking the bootloader! Leave it unlocked or you may very easily brick your device. ONLY re-lock the bootloader when you know exactly what you are doing and have a good reason to do so. With your bootloader unlocked, plenty of folks here can help you and there will always be a way out. :good:
jd1639 said:
You can't flash a binary. They're there to build custom roms. I always ask because so many people miss this, but do you have the latest sdk platform tools, r28?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes sir - doubled checked!
lucky_strike33 said:
Have you tried using this??
https://forum.xda-developers.com/pi...ool-crosshatchdb-one-pixel-3-xl-tool-t3864644
Click to expand...
Click to collapse
Will try now. Thanks!
lucky_strike33 said:
Have you tried using this??
https://forum.xda-developers.com/pi...ool-crosshatchdb-one-pixel-3-xl-tool-t3864644
Click to expand...
Click to collapse
Can't get this to work. I'm still stuck in same position as stated in OP.
rpolito73 said:
Can't get this to work. I'm still stuck in same position as stated in OP.
Click to expand...
Click to collapse
You may need to re setup fastboot and adb again. I would delete all files that you have and then setup with a new install.
Use the tool to have it setup adb for you so that it is up to date.
---------- Post added at 09:03 AM ---------- Previous post was at 08:54 AM ----------
lucky_strike33 said:
You may need to re setup fastboot and adb again. I would delete all files that you have and then setup with a new install.
Use the tool to have it setup adb for you so that it is up to date.
Click to expand...
Click to collapse
Once you get adb set up again go to google firmware: https://developers.google.com/android/images
download and extract the file and then open the file. Extract image file. Open the image file and drag boot.img to your fastboot folder.
Run both commands in fastboot:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then this should start up your phone as it will wipe out twrp. Hope this works for you.
lucky_strike33 said:
You may need to re setup fastboot and adb again. I would delete all files that you have and then setup with a new install.
Use the tool to have it setup adb for you so that it is up to date.
---------- Post added at 09:03 AM ---------- Previous post was at 08:54 AM ----------
Once you get adb set up again go to google firmware: https://developers.google.com/android/images
download and extract the file and then open the file. Extract image file. Open the image file and drag boot.img to your fastboot folder.
Run both commands in fastboot:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then this should start up your phone as it will wipe out twrp. Hope this works for you.
Click to expand...
Click to collapse
Flashed both with no problem. Phone boots to welcome screen, touchscreen still unresponsive. :crying:
rpolito73 said:
Flashed both with no problem. Phone boots to welcome screen, touchscreen still unresponsive. :crying:
Click to expand...
Click to collapse
Its a hardware problem and now you will need to contact google to get it exchanged
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
rpolito73 said:
Flashed both with no problem. Phone boots to welcome screen, touchscreen still unresponsive. :crying:
Click to expand...
Click to collapse
When you are at the welcome screen, does your cell service pop up or anything that acts weird?
Do you know which slot you are booted in? A or B? Maybe try booting into a different slot??
lucky_strike33 said:
Its a hardware problem and now you will need to contact google to get it exchanged
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
When you are at the welcome screen, does your cell service pop up or anything that acts weird?
Do you know which slot you are booted in? A or B? Maybe try booting into a different slot??
Click to expand...
Click to collapse
Nothing acts weird. I have Pixel 3 too and boots up the same. It doesn't show my cell service, just battery on top right.
I don't know which slot it is booting from. I just contacted Google and they are having a specialist contact me.... Oh boy.
rpolito73 said:
Nothing acts weird. I have Pixel 3 too and boots up the same. It doesn't show my cell service, just battery on top right.
I don't know which slot it is booting from. I just contacted Google and they are having a specialist contact me.... Oh boy.
Click to expand...
Click to collapse
https://thedroidguy.com/2018/11/how...3-xl-touchscreen-not-responding-issue-1094388
Try that and do you have a sim card in the phone?
lucky_strike33 said:
https://thedroidguy.com/2018/11/how...3-xl-touchscreen-not-responding-issue-1094388
Try that and do you have a sim card in the phone?
Click to expand...
Click to collapse
On it and no I have no sim in it currently. The only step I haven't done in that article is the boot to safe mode. Those instructions def dont take me to Pixel 3xl safe mode. I tried to boot in safe in recovery but there isn't an option. I don't believe it can be a 3rd party as I have wiped it in recovery multiple times.
rpolito73 said:
On it and no I have no sim in it currently. The only step I haven't done in that article is the boot to safe mode. Those instructions def dont take me to Pixel 3xl safe mode. I tried to boot in safe in recovery but there isn't an option. I don't believe it can be a 3rd party as I have wiped it in recovery multiple times.
Click to expand...
Click to collapse
Have you talked with google? what happened?