[URGENT] Stuck on "Firmware Upgrade Encountered an Issue" - T-Mobile, Samsung Galaxy SIII

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!

Related

[Q] Yet another non booting SGS3 T999 - Please Help

I sent off for a warranty replacement as my phone had the crackle/popping sound while playing music. The new phone should be here by tonight or tomorrow, so I wanted to put my current handset back to factory. Well, I flashed the stock kernel and also the stock rom from the samsung site (for model T999) and it gets stuck at the pulsating samsung logo. I came from Paranoid Android ROM
I am able to get into download mode, but not recovery mode. I have tried everything from multiple flash attempts of the stock rom+kernel to flashing recovery (cwm) through ODIN with no results. I need to get this bad boy back to factory settings before I send it back to T-mo or they might charge me retail pricing for the exchange.
Is there a way to wipe everything (including counter) from ODIN? I've searched several forums, but I haven't found an answer.
Any ideas on how to get this done will be greatly appreciated.
Well, you need to get an absolute factory image (That includes EVERYTHING), I believe the sticky one in the Development section should do the trick.
But before that, in order to reset your counter, you have to use an app developed by Chainfire called, Triangle Away.
As I believe if you ODIN an official package/image, the counter doesn't go up.
theexel said:
Well, you need to get an absolute factory image (That includes EVERYTHING), I believe the sticky one in the Development section should do the trick.
But before that, in order to reset your counter, you have to use an app developed by Chainfire called, Triangle Away.
As I believe if you ODIN an official package/image, the counter doesn't go up.
Click to expand...
Click to collapse
I have been looking through the threads and don't see one labeled absolute factory image. A link would be greatly appreciated
1. Download this: http://samsung-updates.com/get/2144/Samsung_Firmware_SGH-T999_TMB_T999UVALH2_Android_4_0_4.html
It is the FULL stock firmware. t's roughly 720MB. It will be in a compressed format.
2. While that's downloading, you can Triangle Away your phone. (Note: Do it at your own risk.)
Download Link: http://forum.xda-developers.com/showthread.php?p=22463153 (Thanks to Chainfire.)
3. Run Triangle Away on your phone, it'll give you a warning message, and yadayadayada, click Reset Counter.
4. Once your download (Stock Firmware) is complete, extract the .tar.md5 file from the first link I gave you. (Use WinRAR or a similar program.)
{
"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"
}
That is the file you will ODIN to your phone (Add it to the PDA part of ODIN.)
5. Put your phone into download mode. (Confirm that the count is set at 0)
6. Odin like you normally would.
When you initially add it to ODIN, it will look like it gets stuck at <OSM> Please wait..
But it's only because it's a big file, wait it out.
It should finally continue and now it should say:
<OSM> T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
And you should be ready to press Start.
Note: My phone isn't connected, but I took screenshots to help you out. You should see the yellow COM light up and whatnot when you have your phone connected.
Edit: I just realized you can't boot into a ROM to reset your counter, lol.
You'll prolly have to follow my steps twice.
Do steps 5 to 6 first, root your phone.
Then start over from step 1. (Of course you won't have to download the image again, but you know what I mean.)
I truly appreciate all of the effort you put into this, theexel. From the screen shots to the diagrams... It's people like you that make this community thrive.
On another note - that is exactly what I tried before, and it still won't boot. I downloaded the ROM from Samsung, and flashed it with Odin and it just gets stuck at the Samsung pulsating logo. Not sure where to go from this point as I can't get into recovery. Getting somewhat frustrated as I have flashed many-a-Rom on a multitude of devices and this has me stumped...
Any other ideas are welcomed. I have 7 days to figure this out before I have to mail back this phone in exchange for the new one I just received.
You sure you downloaded the file I provided?
The OP in that thread isn't updated and the download may have been the wrong one.
Yeah, I'm sure. I downloaded it again afterwards just to make sure. Still stuck on the sammy logo.
I just downloaded the new version of Odin, as I saw your post and it had v3.07, and I had the older v3.04 and tried again with no luck... I wonder what the hell happened to this phone?
It is possible to reset counter?
Sent from my MB525 using Tapatalk
Fixed it!
Damn, this was a booger.... For some reason traces of CWM were still on the phone, and I had to flash the stock recovery through Odin. After that I wiped cache and factory reset through the stock recovery, and BAM! Booted up like a charm. Now I only have to root, use triangle away to get rid of the flash counter, unroot, and send this thing back to T-Mo. Ridiculous... The pains and glory of flashing custom Roms :victory:
Thanks again, theexel!
zencoran - download "Triangle Away" by chainfire and you can reset your counter. theexel linked it in an above post.
behappy said:
Fixed it!
Damn, this was a booger.... For some reason traces of CWM were still on the phone, and I had to flash the stock recovery through Odin. After that I wiped cache and factory reset through the stock recovery, and BAM! Booted up like a charm. Now I only have to root, use triangle away to get rid of the flash counter, unroot, and send this thing back to T-Mo. Ridiculous... The pains and glory of flashing custom Roms :victory:
Thanks again, theexel!
zencoran - download "Triangle Away" by chainfire and you can reset your counter. theexel linked it in an above post.
Click to expand...
Click to collapse
this has to be throw into the sticky instructions to flash stock, i was having the same issue, used the sgs3 toolkit to get the recovery file and flash with odin. thanks XDA!!

[Q] Need Help! Soft brick with Screen resolution and FRP lock

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.

Accidentally flashed Note 4 Edge recovery image to Note 4 Official app, need help..

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

[HELP] SM-A520 stuck in Bootloader after trying to unbrick by installing Stock Rom

Hey guys, my Phone is stuck in the Bootloader after trying to install the Stock Rom with Odin.
I had to try to unbrick it because I wanted to unlock FRP and at least everything I tried has failed.
The last method I tried, bricked the Phone and now it's stuck in the Bootloader despite flashing the Stock Rom with Odin.
{
"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"
}
Please help, I don't now what to do anymore...
Hifty said:
Hey guys, my Phone is stuck in the Bootloader after trying to install the Stock Rom with Odin.
I had to try to unbrick it because I wanted to unlock FRP and at least everything I tried has failed.
The last method I tried, bricked the Phone and now it's stuck in the Bootloader despite flashing the Stock Rom with Odin.
Please help, I don't now what to do anymore...
Click to expand...
Click to collapse
Does Odin say the operation succeded? I think you just need to restart the phone lol
Baseminge said:
Does Odin say the operation succeded? I think you just need to restart the phone lol
Click to expand...
Click to collapse
Yes, the process got no problem, Odin said succeded.
I already tried restarting the phone multiple times... for example the phone stays in Bootloader for over an hour at the moment.
Hifty said:
Yes, the process got no problem, Odin said succeded.
I already tried restarting the phone multiple times... for example the phone stays in Bootloader for over an hour at the moment.
Click to expand...
Click to collapse
For "bootloader" you mean download mode or what? Cause I cannot see anything in your "this my screen now". Try to resent pic
Baseminge said:
For "bootloader" you mean download mode or what? Cause I cannot see anything in your "this my screen now". Try to resent pic
Click to expand...
Click to collapse
I mean the pre-boot screen, where the where model name, powered by android and so on stands.
https://imgur.com/a/eDI8PNr
Hifty said:
I mean the pre-boot screen, where the where model name, powered by android and so on stands.
https://imgur.com/a/eDI8PNr
Click to expand...
Click to collapse
Ok, It's download mode. I think you just need to press and hold vol- and power button simultaneously and when screen come black, waiting for the boot.
If won't work:
-Check you downloaded the correct firmware for your phone
-It's recommended to use Odin v3.13.1 and UNTICK auto-reboot
-Try to restart first in recovery and boot phone by recovery
Baseminge said:
Ok, It's download mode. I think you just need to press and hold vol- and power button simultaneously and when screen come black, waiting for the boot.
If won't work:
-Check you downloaded the correct firmware for your phone
-It's recommended to use Odin v3.13.1 and UNTICK auto-reboot
-Try to restart first in recovery and boot phone by recovery
Click to expand...
Click to collapse
Well, at first I took the newest Firmware Update, could it help to install an older version?
And how do I restart the Phone safely after installing the stock rom?
Hifty said:
Well, at first I took the newest Firmware Update, could it help to install an older version?
And how do I restart the Phone safely after installing the stock rom?
Click to expand...
Click to collapse
Now it seems to be stuck in Bootscreen...

Pixel XL randomly bricked itself overnight?

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

Categories

Resources