Develop Bugs

[SOLVED] Unable to flash SGS3 T999, phone hangs on system.img.ext4

Greetings:
I have an SGH-T999 SGS3. It was running ICS.
When using Kies, I was offered the upgrade to Jellybean (LJA). The Kies update hung at 23%, for hours, repeatedly, and never exited.
I've now downloaded the root66 LJA system, and am trying to flash with ODIN. ODIN has now been stuck for an hour at system.img.ext4.
Can anyone help me get *anything* flashed to this phone, so I can get out of recovery mode please?
Thanks in advance!
Click to expand...
Click to collapse
To anyone having this problem, I fixed it by:
1. Using Odin307 instead of Odin185 AND
2. Using a different USB cable.
I don't know which of those two things fixed it, since I tried both at once, but that fixed it.
The entire update took 6 minutes once I changed those two things.
Thanks!
Glen

It takes a lot of time to flash system.img.ext4. I think it may take less or more time based on your computer and other factors. Just let it flash and wait. Mine took about 1.5 hour.
Sent from my frozen SGH-T999

Still waiting after one hour so far...
HajmeR said:
It takes a lot of time to flash system.img.ext4. I think it may take less or more time based on your computer and other factors. Just let it flash and wait. Mine took about 1.5 hour.
Sent from my frozen SGH-T999
Click to expand...
Click to collapse
Okay, started at 3:34 PM Pacific time. Still stuck (but not failed, interesting) at 4:37 PM (one hour so far.) I will advise.
This is on an HP Pavilion dv7-2173cl with a fresh load of Windows 8, no bloatware other than the stock stuff. (A similar attempt on an HP dv7-2043cl running Windows 7 also appeared to stick at the same point, but I only waited 30 minutes before giving up.)
By comparison, and just for interest, my international SGS3, I9300, updated over Kies in about 4 minutes, on the same computer. So I would be interested to know why an I9300 goes so fast, and a T999 goes so slow, if there are any ideas...

SOLVED!
glenbarney said:
Okay, started at 3:34 PM Pacific time. Still stuck (but not failed, interesting) at 4:37 PM (one hour so far.) I will advise.
This is on an HP Pavilion dv7-2173cl with a fresh load of Windows 8, no bloatware other than the stock stuff. (A similar attempt on an HP dv7-2043cl running Windows 7 also appeared to stick at the same point, but I only waited 30 minutes before giving up.)
By comparison, and just for interest, my international SGS3, I9300, updated over Kies in about 4 minutes, on the same computer. So I would be interested to know why an I9300 goes so fast, and a T999 goes so slow, if there are any ideas...
Click to expand...
Click to collapse
To anyone having this problem, I fixed it by:
1. Using Odin307 instead of Odin185 AND
2. Using a different USB cable.
I don't know which of those two things fixed it, since I tried both at once, but that fixed it.
The entire update took 6 minutes once I changed those two things.
Thanks!
Glen

glenbarney said:
To anyone having this problem, I fixed it by:
1. Using Odin307 instead of Odin185 AND
2. Using a different USB cable.
I don't know which of those two things fixed it, since I tried both at once, but that fixed it.
The entire update took 6 minutes once I changed those two things.
Thanks!
Glen
Click to expand...
Click to collapse
I experience this problem when I use a non-samsung usb cable(Vibrant and S3). It would always freak me out, because it would stay for hours and would usually end up in a soft brick.

all I've used on any of my Android phones is a cheap Blackberry-brand usb cable from Amazon. I think it was $2.00 or so. Hasn't failed me yet :good:
I would bet that it was probably just your very old version of Odin, honestly.

Kalm_Traveler said:
all I've used on any of my Android phones is a cheap Blackberry-brand usb cable from Amazon. I think it was $2.00 or so. Hasn't failed me yet :good:
I would bet that it was probably just your very old version of Odin, honestly.
Click to expand...
Click to collapse
I would bet that it is the USB cable. I tried flashing stock on my Verizon Note 2 and nothing happened after 90 minutes. I spent three hours flashing nothing happened. I was using the box included Samsung cable, then I read this thread so I might as well try it. I got my sister's HTC Incredible 2 cable and what would you know it was done in under 5 minutes. :laugh: Next time i flash i am going to have a tower of cables next to me

Kalm_Traveler said:
all I've used on any of my Android phones is a cheap Blackberry-brand usb cable from Amazon. I think it was $2.00 or so. Hasn't failed me yet :good:
Click to expand...
Click to collapse
Me too!
Flashing a full image through Odin should take 10-15 minutes tops. Is the phone connected as a USB 2.0 device? Sometimes the buggy drivers will put it into 1.0 mode.

mattedwards2686 said:
I experience this problem when I use a non-samsung usb cable(Vibrant and S3). It would always freak me out, because it would stay for hours and would usually end up in a soft brick.
Click to expand...
Click to collapse
thanks for the help man it really helped me !!
:good:

SCH-I605 Flash Fails with Odin
I am having a similar issue with my Note II. I tried to flash a new bootloader to facilitate the installation of the KitKat based Ditto Note 3 rom. I, in my failure to read 6 posts down, used mobileOdin to try and accomplish this. My phone is now a plush, soft brick. I can get into download mode. Given this, I have been trying to flash my phone using Odin for windows only to have it fail every time. I have tried different roms, partitions, bootloaders, versions of Odin, PCs, cables and even a couple of different poses. I am not new to rooting and roms, every android device I own is rooted and running custom roms. Any help from those who are definitely more knowledgeable than myself (the XDA community) would be GREATLY appreciated.
Phone Information:
Was running MeanBeanICE
Verizon phone
In download (Odin) mode:
Product Name: GT-N7100
Custome Binary Download: no
Current Binary: Official
System Status: Custom
Warranty Bit: 0

talonzme said:
In download (Odin) mode:
Product Name: GT-N7100
Custome Binary Download: no
Current Binary: Official
System Status: Custom
Warranty Bit: 0
Click to expand...
Click to collapse
Wrong Device Forum bud. This is T Mobile Galaxy S3 Only. You are Looking for Note II on Verizon I believe. Here's the correct Forum,

Yup, you'll get better, more specific help there. But just fyi, if kies is on your computer, uninstall it. Also, when trying different version drivers, make sure you first uninstall old ones through device manager. See my sig for drivers. They should work for any sammy device.
Sent from my SGH-T999 using Tapatalk

Apologies
DocHoliday77 said:
Yup, you'll get better, more specific help there. But just fyi, if kies is on your computer, uninstall it. Also, when trying different version drivers, make sure you first uninstall old ones through device manager. See my sig for drivers. They should work for any sammy device.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Sorry for the erroneous post. I do have the latest Samsung driver and I have uninstalled Kies. Thank you for your time. I have made a post in the Note II section. Hopefully I will find some joy soon!

talonzme said:
Sorry for the erroneous post. I do have the latest Samsung driver and I have uninstalled Kies. Thank you for your time. I have made a post in the Note II section. Hopefully I will find some joy soon!
Click to expand...
Click to collapse
Actually, dont use the latest. Try a few versions back. The latest, while it should still work, was built for the S5/Note3/Gear. It included significant changes as I understand it. Also in your case driver version doesn't matter. Some have had to try several before getting it to work. Sometimes the original works better than any newer ones.
Good luck with it though!
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Actually, dont use the latest. Try a few versions back. The latest, while it should still work, was built for the S5/Note3/Gear. It included significant changes as I understand it. Also in your case driver version doesn't matter. Some have had to try several before getting it to work. Sometimes the original works better than any newer ones.
Good luck with it though!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I will give that a go.

talonzme said:
I will give that a go.
Click to expand...
Click to collapse
Did you ever solve this?

mrdunlop said:
Did you ever solve this?
Click to expand...
Click to collapse
I did it involved the out jtag repair. It that where i was unrecoverable by standard means.

life saver
glenbarney said:
To anyone having this problem, I fixed it by:
1. Using Odin307 instead of Odin185 AND
2. Using a different USB cable.
I don't know which of those two things fixed it, since I tried both at once, but that fixed it.
The entire update took 6 minutes once I changed those two things.
Thanks!
Glen
Click to expand...
Click to collapse
thanks bro
i used a different USB Cable it worked.........
thanks alot

[Q] RumRunner and 33MB Verizon update

Since Verizon pushed a small 33MB update, would that be an issue with not being able to achieve s-off? I've tried on 2 different Ubuntu machines with the same failed result. I have read about different users doing a system reset and others that haven't who still achieved s-off.

If you are talking about the update from several weeks ago, I actually had that force installed on mine after having my One replaced with a broken headphone jack. (Thanks Best Buy Guy for installing it without asking...)
I ran RumRunner on Windows 7 and had no issues with it. Poured 3 times, all was well.

irie27 said:
Since Verizon pushed a small 33MB update, would that be an issue with not being able to achieve s-off? I've tried on 2 different Ubuntu machines with the same failed result. I have read about different users doing a system reset and others that haven't who still achieved s-off.
Click to expand...
Click to collapse
The 33mb update shouldn't effect achieving s-off, i took the OTA before using rumrunner and i was able to achieve s-off with no problems. Although I haven't tried on Ubuntu machines, only windows 8.

SOLVED
Thank you both. I'll try again. I was sitting on pour 3 for over a half an hour when I noticed Ubuntu froze for some reason.

irie27 said:
Thank you both. I'll try again. I was sitting on pour 3 for over a half an hour when I noticed Ubuntu froze for some reason.
Click to expand...
Click to collapse
I installed the update then ran rumrunner. Worked the first time. Should work for ya. It was the easiest unlocking of an Android phone over ever done!! He is awesome.

jski711 said:
I installed the update then ran rumrunner. Worked the first time. Should work for ya. It was the easiest unlocking of an Android phone over ever done!! He is awesome.
Click to expand...
Click to collapse
It did, I ended up having to plug the usb cable in the back usb port, 2 pours later its done!

Touch screen not working, even after factory reset

My phone arrived last night. I immediately, following the instructions I found here, magisk'd it. As soon as I flashed the patched image and rebooted... I found that the touch screen had stopped working.
So I booted into recovery (which was hard, because I can't figure out any way to shut my phone down), and wiped data / factory reset. The bootloader is still showing as unlocked. And the touch screen is still not working.
Does anybody know why this might be or what I should do about it? Note that I didn't buy from Google, I bought new from a well-reputed ebay seller...

Send it back. It sounds like a hardware issue.

sic0048 said:
Send it back. It sounds like a hardware issue.
Click to expand...
Click to collapse
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?

DanHakimi said:
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
Click to expand...
Click to collapse
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:

Reflash the factory image and relock the bootloader... It is an official process from Google, if that fails contact the seller and RMA the unit.

Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!

As it's new and you've got nothing to worry about saving I'd just flash the latest factory image via fastboot and once it's up extract the boot from that image and patch it. The fellow above is probably correct but there is one other thing, use an A to C cord, not the C to C cord for all your flashing.

Bob nesta said:
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Click to expand...
Click to collapse
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.

DanHakimi said:
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
Click to expand...
Click to collapse
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
As far as Q - maybe? That's why I said "supposedly" it comes out the 3rd (https://www.theverge.com/platform/a...ndroid-10-pixel-september-3-release-leak-date) , but there are no guarantees in life (except death & taxes).

Again, just to be sure, you are using a USB A to C and not a C to C, correct?

DarkShadowMX said:
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
Click to expand...
Click to collapse
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...

krabman said:
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
Click to expand...
Click to collapse
Yes, A to C.

Bob nesta said:
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
Click to expand...
Click to collapse
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...

DanHakimi said:
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
Click to expand...
Click to collapse
Please do. I'm no dev & can probably offer little to no help, but if you post your errors someone else may be able to help you out.
It could just be a cable/driver/fastboot issue & not the phone, so please provide error info.

Ok, do the full smash. This assumes a basic familiarity with flashing mechanics.
1. Download and install the latest fastboot package.
2. Download the latest image from google again.
3 Use a known good A to C usb cord
4 Before flashing the image type all the following commands one by one in fastboot...
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
5 Flash the image using the flash all script.
6 Once you're up extract the boot from the image you flashed and patch it in magisk.
7 Flash the patched boot image.

DanHakimi said:
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
Click to expand...
Click to collapse
I don't either. I used a USB OTG cable

Had a **** ton load of issues trying to go from rooted and TWRP with custom rom to Android 10.. Every time I ran the flash-all.bat it would fail at one stage or another.. Finally grabbed the Pie Ota from the site, sideloaded it through TWRP then wiped everything through stock recovery and then took the Android 10 update. My point is, use the OTA and sideload it

I was rooted on Android 10 beta 6 and trying to download the OTA through the phone update failed every time. I uninstalled magisk and restored images..but still failed. I finally had to sideload the OTA image and it finally updated. That was the only way to get mine to work. Then I took the boot image from beta 6 that was already patched through magisk and re-flashed it because the boot image from Android 10 official patched through magisk would not give root...kept failing. Then when I re-flashed last months beta 6 image, upon reboot the screen would freeze and no apps would load. I then booted into recovery and did a factory reset and upon reboot magisk was identified and root was acquired....phone worked perfectly after that and no issues....weird. I then just reloaded all of my apps from backup and was on Android 10 official, rooted through magisk.

I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...

DanHakimi said:
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
Click to expand...
Click to collapse
I suspect you are running out of hard disk space on the computer that you are using to try to flash all this with. I ran into a similar issue once when the C drive of my computer was nearly full. The system file ends up needing a lot of disk space in order for it to be unpacked. The error you are getting is that you are running out of space and it cannot unpack it. Again, this isn't phone memory space, this is actual computer hard drive space.

Waiting for service..

Havent had this problem before. Flashed an old custom rom from June. And now my computer can't find My device, think im gonna factory reset and try that. ny other suggestion? Have used same usb cable and has always worked.
Since I don't have flashed twrp installer I don't be able to flash anything, or flash stock ROM.

Platform tools are up to date?

pa.pn2 said:
Platform tools are up to date?
Click to expand...
Click to collapse
Yes using homebrew with my Mac. And everything is up to date. Have uninstalled and re installed everything. Gonna try again tonight after work . Otherwise I'm gonna factory reset and try that.

tried my wifes pixel phone today with terminal, adb devices. and that phones shows up.
tired my again , still same problem. think i might have some problem with my usb port on my phone.

krabban said:
tried my wifes pixel phone today with terminal, adb devices. and that phones shows up.
tired my again , still same problem. think i might have some problem with my usb port on my phone.
Click to expand...
Click to collapse
There does seem to be a more frequent mention of port issues (failures) on our phone recently. In my case it was dust impacted in the port that kept the plug from seating fully. But I work in a paper factory so dust is an ever present enemy. Lol
Sent from my Pixel 2 XL using XDA Labs

Question Android 13 bootloop

Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?

Delete the cache in recovery if all else fails it should fix whatever the conflict is

Shipoftheline said:
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Click to expand...
Click to collapse
I can't enter to recocery after flashing android 13

Kirya27 said:
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Click to expand...
Click to collapse
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.

Lughnasadh said:
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Click to expand...
Click to collapse
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?

Kirya27 said:
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Click to expand...
Click to collapse
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.

Lughnasadh said:
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Click to expand...
Click to collapse
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?

Kirya27 said:
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Click to expand...
Click to collapse
Well, you didn't mention you were using the latest Platform Tools, so I suggested it as that's one of the 1st steps of troubleshooting in these situations. You also didn't specifically mention using Android Flash Tool, so I suggested that as well.

Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.

Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
This sounds interesting. I'll try it today when I get home and post the results here.

Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
I tried the method that you described and indeed, for some time the phone worked on Android 13 (however, when it was turned on, it wrote that this device was suddenly damaged due to something, photo below). True, after 15-20 minutes of use, phone rebooted into the bootloop, just for no reason at all. I flashed exactly as you said, separately in each slot ...

I have had this screen when I soft bricked after flashing lineage os. I fixed it with flashtool. My exact setup is windows 11, flashtool through Microsoft edge with the options to force flash and wipe device checked in flashtool. Flashtool has rescued my p6pro many times with this setup.

fil3s said:
У меня был этот экран, когда я завис после прошивки Lineage OS. Починил флештулом. Моя точная настройка — это Windows 11, flashtool через Microsoft Edge с параметрами принудительной прошивки и очистки устройства, отмеченными во flashtool. С помощью этой настройки Flashtool много раз выручал мой p6pro.
Click to expand...
Click to collapse
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes

Kirya27 said:
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Click to expand...
Click to collapse
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot

fil3s said:
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
Click to expand...
Click to collapse
I tired fastboot -w many times

Kirya27 said:
I tired fastboot -w many times
Click to expand...
Click to collapse
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android

fil3s said:
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
Click to expand...
Click to collapse
Tried. It turns out the same as on the stock firmware

I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update

apis903 said:
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
Click to expand...
Click to collapse
They clearly designed these phones to fail. They implied they would be usable for 6 years, but like all previous google phones, it will brick itself within 2. This 6 Pro is definitely the last product I buy from Google. I've had 3 other Nexus/pixel phones, none of which lasted. My sister is still using my hand-me-down iPhone 7 that I dropped off a cliff.
I can't do iphones though, and I don't want to support slave labor.. so my options are extremely limited. I'm only going to buy smartphones produced in the USA. It's dangerously cheap to produce phones using the less strict labor and material laws of foreign countries, phones are being treated as disposable, which is unacceptable. My modified Nexus 5X is perfectly usable despite having half the CPU disabled and being a 7 year old phone, thanks to overclocking. Companies should not release a new device unless it is a worthy upgrade over the previous one. It should happen every 3 years, not every year.
I just hope other nerds wake up and stop supporting Google. We have to boycott Google until they create desirable products. Pixel is so undesirable that they spend their ad money on woke bull**** that no one cares about except the sheep, but they like iPhones. Google is just burning our money and ignoring our needs.
Edit: I'm just salty that I got scammed by Google. They lost all of their people who cared. Google is full of corrupt people who want to make a buck. Pixel 7 is essentially the exact same as Pixel 6. The lack of a pro mode in the camera app perfectly represents Google's priorities. It would take one developer a couple days to add such a feature to the app. Google is not doing ANYTHING good.