Hi, so today I rooted my Note 4 and installed the official TWRP app, I made the mistake of flashing the Note 4 Edge recovery firmware directly from the TWRP app and when I rebooted my phone updated and now the touch screen heavily distorts where I touch the screen in order to compensate for the edge that is not there. My phone is basically unusable but with some effort I can get into TWRP to try to restore to the back up I made before doing this but it doesn't fix the problem. The phone will also not boot into any sort of recovery mode and is not recognized by odin anymore. I don't know what to do here.. if anyone has any tips for me I'd be very appreciative. Thank you so much.
slothandtorpor said:
Hi, so today I rooted my Note 4 and installed the official TWRP app, I made the mistake of flashing the Note 4 Edge recovery firmware directly from the TWRP app and when I rebooted my phone updated and now the touch screen heavily distorts where I touch the screen in order to compensate for the edge that is not there. My phone is basically unusable but with some effort I can get into TWRP to try to restore to the back up I made before doing this but it doesn't fix the problem. The phone will also not boot into any sort of recovery mode and is not recognized by odin anymore. I don't know what to do here.. if anyone has any tips for me I'd be very appreciative. Thank you so much.
Click to expand...
Click to collapse
Try pulling the battery at least one minute, reinstall battery and boot directly to recovery or download mode. But if you can boot to system, you could install the Official TWRP Manager from Google Play and download the right TWRP image and flash it with the same app.
In the app, search "Samsung Galaxy Note 4" and scroll to bottom and select "...Qualcomm -- trlte", then "...Americas...". The file you need is twrp-3.1.1-0-trlte.img to flash with TWRP or the the recovery flash option in the app.
I've read many posters have flashed wrong recovery (Note Edge) but not corrupted partitions. But you may need to flash the stock tar if getting right TWRP recovery flashed, boot and opening dialer and dialing *#2663# and pressing the top left update button doesn't work.
{
"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"
}
Alternately, you can download this app and use the left tab to select secret codes and select code 2663 (if the dialer code doesn't work).
http://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
The 2663 secret code is to correct the touch screen calibration. You need to use your S-pen to open dialer or navigate until touch is restored.
Sent from my SM-N920P using Tapatalk
Thank you so much man I had done everything up to entering that last secret code and that did it for me. It's a damn shame I already have a new phone coming in the mail but thank you so so much.
wow, spoke a little too soon on this one. Now normal booting is failing and it goes straight to recovery, that and I can't get my computer to detect it in Odin
slothandtorpor said:
wow, spoke a little too soon on this one. Now normal booting is failing and it goes straight to recovery, that and I can't get my computer to detect it in Odin
Click to expand...
Click to collapse
When boot fails, do you see eMMC read or write failure (component failure)? If you see that, Samsung Support may offer to repair it for $75 USD and a week or more turnaround. Unless you have a warranty...
Your phone not detecting on PC could be a bad Samsung USB driver. Try reinstalling it; download it from Samsung Support for your model number. But give Odin and PC time if you're trying to install stock tar; it takes a minute or longer to verify the md5, then it may add your phone in COM tab on Odin as highlighted. You may see a comment in Odin log (view log while running), like please wait during this verification. Don't try to proceed without md5 verification and COM added.
Sent from my SM-N920P using Tapatalk
Tried again today and after a few restarts I got my phone to read in odin and wrote a stock tar.gz to it. I'm still updating as we speak but it looks like it's gonna work out thanks a bunch man.
samep said:
When boot fails, do you see eMMC read or write failure (component failure)? If you see that, Samsung Support may offer to repair it for $75 USD and a week or more turnaround. Unless you have a warranty...
Your phone not detecting on PC could be a bad Samsung USB driver. Try reinstalling it; download it from Samsung Support for your model number. But give Odin and PC time if you're trying to install stock tar; it takes a minute or longer to verify the md5, then it may add your phone in COM tab on Odin as highlighted. You may see a comment in Odin log (view log while running), like please wait during this verification. Don't try to proceed without md5 verification and COM added.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Related
Hello XDA, haven't been on these forums for a while.
I have a slight issue with a Galaxy SIII I just picked up off a friend.
The S3 goes to this screen every time I try to boot it with the power button:
{
"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"
}
And I AM able to get to the download mode screen:
I've tried to flash a Stock Rooted Firmware onto the phone using Odin 3.07, and all it does is say it failed.
Another thing to note is that I CAN'T boot into recovery, and that I do not have Clockworkmod installed.
Also, I am not sure if my device is rooted as it was given to me by someone else..
Any help on trying to solve this issue will be much appreciated!! Thank you! ��
EDIT: if you can't see the images for some reason, it is just a photo of the "Firmware Upgrade Encountered an Issue" screen and a photo of the download mode screen.
More info:
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: custom
SYSTEM STATUS: official
QUALCOMM SECURE BOOT ENABLE
When you try to flash with Odin, what does it say in the message box after it fails?
Also, what firmware are you trying to flash?
DocHoliday77 said:
When you try to flash with Odin, what does it say in the message box after it fails?
Also, what firmware are you trying to flash?
Click to expand...
Click to collapse
This is the firmware I am trying to flash: root66_TMO_T999UVDLJA.tar.md5
It's basically a rooted stock ROM for the SIII T-Mobile.
And this is the message I receive when trying to flash:
Please note I have tried to flash other firmwares as well, getting the same message.
One thing that DID work was flashing a custom recovery through odin.
Thanks for the reply!
UPDATE:
I've now gotten the phone to get stuck at the Samsung boot logo (the one where it glows blue) instead of giving me the firmware issue message.
I did this by flashing CWM through odin. In Odin, it said the flash was successful but when I boot into recovery on my phone, it just goes to the stock Samsung recovery.
One thing I did notice was that when I try to factory reset the phone, it gives me a BUNCH of errors in red text.. doesn't seem normal.
Thanks again!
Yeah. Im afraid that doesn't sound good. But before getting too negative, try flashing the firmware again, but this time use the PIT file as well. In case the local one on your device is corrupted, use one from our thread in the General section.
http://forum.xda-developers.com/showthread.php?t=1848267
Download the correct one for your device. If the link in the op isn't working check my last few posts for a mirror.
Now in Odin do exactly as before, but also click the PIT button and select the file you just downloaded. Then make sure that re-partition is checked. Click start.
If something corrupted your partition layout, theres a chance this will fix it. If it doesn't work, theres a good possibility the memory is going bad....
DocHoliday77 said:
Yeah. Im afraid that doesn't sound good. But before getting too negative, try flashing the firmware again, but this time use the PIT file as well. In case the local one on your device is corrupted, use one from our thread in the General section.
http://forum.xda-developers.com/showthread.php?t=1848267
Download the correct one for your device. If the link in the op isn't working check my last few posts for a mirror.
Now in Odin do exactly as before, but also click the PIT button and select the file you just downloaded. Then make sure that re-partition is checked. Click start.
If something corrupted your partition layout, theres a chance this will fix it. If it doesn't work, theres a good possibility the memory is going bad....
Click to expand...
Click to collapse
Same thing happens this time, same error message. It seemed like the PIT file did not make a difference at all..
BUT! Now, I went into the stock recovery and tried to do a factory reset. NO ERRORS!
And when it began to boot, it made the little ringtone "jingle" and FINALLY BOOTED UP TO THE SETUP SCREEN!!
YOU, MY FRIEND, ARE AMAZING. THANK YOU SO MUCH!!
So for all future references: the PIT file may seem to do nothing at all, but once you do a factory reset it will work like a charm.
Once again, thanks! Bought the phone for $20, now I can sell it for around $100, lol.
Glad i could help!
Hello,
I received my phone back from LG to fix the motherboard issue and it did not have an OS. Actually it did have an OS called Mini OS. The boot loader is locked and it won't verify proper google firmware when I adb sideload because it's using "test keys".
I was able to get root and adb into the device. Two questions:
1. Considering that I have root to the device, how can (is it possible) I put firmware to get back to a working state?
2. Because I have root on my device which is loaded with their keys and pre-OS flashed firmware, is there any value for the community here'?
Please forgive me if this is forbidden discussion and remove this post. I haven't been on XDA for more than a couple of years and don't know how things have changed.
Thank you.
FYI I fixed this issue. If you have this problem you can fix it by pushing twrp or other recovery to the device and dd-ing it to the boot loader block.
Let me know if you want help on this.
Also let me know if you want the system image I pulled from the stock weird LG manufacturer device.
Would be interesting to see, doubt it would be all that useful but interesting nonetheless
https://www.reddit.com/r/LGG3/comments/4g8d0p/g3_flash_tool_stuck_on_mini_os_screen_please_help/ This seems to be it running on a G3
https://www.youtube.com/watch?v=k8VWVzJJ0-U and on a G Flex2
This happened to me when i flash tot and unplug it before.
Sent from my Pixel using Tapatalk
Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.
AFK269 said:
Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.
Click to expand...
Click to collapse
{
"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"
}
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification
konceptz said:
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification
Click to expand...
Click to collapse
I think that you will need to make a call to the service center to tell your situation.
I followed this and it booted just fine.
I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .
picodot said:
I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .
Click to expand...
Click to collapse
Hi @picodot , which bullhead image version did you use?
Hi, I was trying to flash a kdz to my LG G3 in order to downgrade the phone to 5.0. However, while the program start flashing and the progress bar on the phone reach 5%, the program shows " cannot reach the sever". The flashing process then stopped, no matter I keep clicking "retry".
As a result, I took out the battery and put it back attempt to get back to download mode.
However, the LG G3 do have a starting up screen as usual, but the phone didnt go in download mode, but get into black screen. The notification light is repetitively flashing blue and red color for couple second.
THe computer cannot detect the phone.
Any idea how I can save the phone ~_~?
{
"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"
}
Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana
Bananaphone64 said:
Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana
Click to expand...
Click to collapse
It can go into the recovery mode but not the normal OS. But what I can do in the recovery
voot566 said:
But what I can do in the recovery
Click to expand...
Click to collapse
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana
Bananaphone64 said:
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana
Click to expand...
Click to collapse
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"
voot566 said:
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"
Click to expand...
Click to collapse
drivers installed?
Bananaphone64 said:
drivers installed?
Click to expand...
Click to collapse
Yes, driver is installed :crying:
but windows doesnt seems to have detected my phone
Hm... i recently havent the stock recovery installed. I allways hat the possibility to use TWRP.
Thx so much, Bananaphone64.
I think what the real problem now is, the computer cannot recognize the phone. Anyone else have an idea?
In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana
Bananaphone64 said:
In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana
Click to expand...
Click to collapse
I have attempted on another computer, but the other computer also doesnt recognize the phone.
What is a SS?
A Screenshot or Picture from the Recovery Menu
Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS
I have seen that screen! 3 days before!
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!
yosmz1112 said:
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!
Click to expand...
Click to collapse
Yes. it was completely not able to enter into the download mode...........
Wh0CaREs said:
Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS
Click to expand...
Click to collapse
It is factory recovery. let me check the link, thx so much
deleted
I install Android 7.0 custom ROM on my S6 Sprint, and I change screen solution to 1280*720.
I get an FRP lock after I restart my phone, I can't open a phone or access to recovery mode.
I download and install latest stock ROM from sammobile.com via Odin 3.12.5,
but It boot loop after show big Samsung logo on wrong screen resolution.
Now, I can open Download mode. I try to fix screen resolution by ADB commands but doesn't work.
It can't find a phone in download mode .:crying::crying::crying:
Thank you for helping me! :laugh:
First off, make sure that your phone is an SM-G920P. Then get the latest TAR file from my thread here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Be sure to check the MD5 (instructions in the thread on how to do that. Sometimes the downloads from Sammobile are incomplete or corrupted. Flash that with Odin.
koop1955 said:
First off, make sure that your phone is an SM-G920P. Then get the latest TAR file from my thread here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Be sure to check the MD5 (instructions in the thread on how to do that. Sometimes the downloads from Sammobile are incomplete or corrupted. Flash that with Odin.
Click to expand...
Click to collapse
{
"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"
}
It still has big Samsung logo.
I'm sorry for creating a thread in the wrong category. I just see that.
If you have been able to flash the TAR, try going into Recovery and doing a factory reset.
koop1955 said:
If you have been able to flash the TAR, try going into Recovery and doing a factory reset.
Click to expand...
Click to collapse
I'm not able to flash recovery.
It looks like your phone is an Edge, SM-G928P. Is that correct? If that is the case, that is why you can't flash the firmware. Have you tried flashing this: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G928P/
koop1955 said:
It looks like your phone is an Edge, SM-G928P. Is that correct? If that is the case, that is why you can't flash the firmware. Have you tried flashing this: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G928P/
Click to expand...
Click to collapse
My phone is 920P. It look like 928 because it have slash line in zero
nutgothic said:
My phone is 920P. It look like 928 because it have slash line in zero
Click to expand...
Click to collapse
Okay, at least then we have the right firmware.
You did download the Nougat firmware from my thread, and checked the MD5? Is it still failing for you in Odin? If that is the case, not sure what to tell you.
koop1955 said:
Okay, at least then we have the right firmware.
You did download the Nougat firmware from my thread, and checked the MD5? Is it still failing for you in Odin? If that is the case, not sure what to tell you.
Click to expand...
Click to collapse
Your firmware is work good while install. when phone start, it show big Samsung in the wrong resolution(First picture)
I tried to open recovery mode and flash recovery by Odin, but it doesn't work because FRP lock.(Second picture)
I think I have to buy a new phone. :crying::crying::crying:
nutgothic said:
Your firmware is work good while install. when phone start, it show big Samsung in the wrong resolution(First picture)
I tried to open recovery mode and flash recovery by Odin, but it doesn't work because FRP lock.(Second picture)
I think I have to buy a new phone. :crying::crying::crying:
Click to expand...
Click to collapse
If that firmware installed, then you can get to recovery either by powering down (shut off) and then holding Volume Up, Home and Power. Or by using ADB. Don't try to flash anything other than the firmware through Odin. In Recovery, select Factory Reset.
Look at this: https://www.digitaltrends.com/mobile/how-to-factory-reset-galaxy-s6/
See the second option.
Thank you. everything works great!!!
nutgothic said:
Thank you. everything works great!!!
Click to expand...
Click to collapse
That is GREAT! So glad that we were able to get you sorted out and thanks for letting us know.
So, I had left it plugged into the usbc port on my desktop overnight, probably not a good idea. In the morning I glanced at it, and it was doing a sort of charging boot loop, like showing the charging icon in the middle, then rebooting. Before it booted everytime, it showed a red light at the top, I assume because the battery was dead dead from boot looping.
So, I figured maybe I could just reset everything. No go. Couldn't get into the system at all. Kept showing the battery charging icon every time I tried to turn it on, then it would shut right off. Same thing over and over every time I tried to turn it on. Even Volume down + Power resulted in the battery charging icon.
So then I tried volume down + power while plugged into the computer with a different cable and different port, and I was able to get into the bootloader screen as shown. But this is as far as I cant go. I can't get into recovery, it just gets stuck at the google screen. Trying to boot into system gets stuck at the google screen."
I then tried various methods of flashing, live booting, whatever I could find on the matter, and resulted in the following errors, and getting stuck again on the google screen or sometimes staying on the bootloader screen. Is it a fair guess that maybe the flash chip died somehow? Or is that a bit out there? Only guessing that cuz usbc port on computer, less regulated than the standard chargers, idk just a theory. I've never had a problem like this before, but also never left a phone in that port all night.
{
"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"
}
Fortunately, your bootloader is unlocked, so your chances of fixing this are pretty good.
Please provide more information about the circumstances. Are you running a custom ROM?
From the logs you posted, it appears you're trying to flash incorrect firmware. A/B slot devices like the Pixel series do not have bespoke recovery partitions; the recovery kernel is contained in /boot, along with the system kernel. If you flash a recovery image to /boot, your device will only boot to recovery. Generally, the proper way to use custom recoveries on these devices is to live boot the recovery image; do NOT flash it.
As far as reflashing your phone, make sure you're using the correct firmware. The firmware for your device is here, notice the code name "marlin". Direct link for the latest firmware is here.
Make sure you are using the latest ADB Platform Tools.
If you need more information, please see my guide on the Pixel 3 here, as the concepts involved are exactly the same; the only difference is the firmware. Please note that the Android Flash Tool only works with Pixel 2 and newer.
V0latyle said:
Fortunately, your bootloader is unlocked, so your chances of fixing this are pretty good.
Please provide more information about the circumstances. Are you running a custom ROM?
From the logs you posted, it appears you're trying to flash incorrect firmware. A/B slot devices like the Pixel series do not have bespoke recovery partitions; the recovery kernel is contained in /boot, along with the system kernel. If you flash a recovery image to /boot, your device will only boot to recovery. Generally, the proper way to use custom recoveries on these devices is to live boot the recovery image; do NOT flash it.
As far as reflashing your phone, make sure you're using the correct firmware. The firmware for your device is here, notice the code name "marlin". Direct link for the latest firmware is here.
Make sure you are using the latest ADB Platform Tools.
If you need more information, please see my guide on the Pixel 3 here, as the concepts involved are exactly the same; the only difference is the firmware. Please note that the Android Flash Tool only works with Pixel 2 and newer.
Click to expand...
Click to collapse
Hey thanks for the reply, soo, I followed all steps of any guide I came across. When I try to just boot any twrp recovery, it will show the TWRP logo loading, and then go black, and try to boot up normal, getting stuck at the google screen again. Anything I've tried usually ends up back at that frozen google logo.
Yiggs said:
Hey thanks for the reply, soo, I followed all steps of any guide I came across. When I try to just boot any twrp recovery, it will show the TWRP logo loading, and then go black, and try to boot up normal, getting stuck at the google screen again. Anything I've tried usually ends up back at that frozen google logo.
Click to expand...
Click to collapse
It's generally easier to provide help if I know what's going on. Please answer the questions I asked.
Sorry, I thought I did when I said I follow all the correct steps. No custom rom. Was there anything else you needed to know?
No custom rom
Followed steps in your guide and others
Everything is correct for software
Anyone have anymore thoughts on this?
Sorry I didn't see your response to this. I don't have any suggestions unfortunately