Database Info

[SOLVED] Soft Brick on rooted N5 running 4.4.2

All,
I got myself into a bit of pickle and could use some advice.
First, device information:
Nexus 5 Hammerhead D821(E)
Hw version rev_11
Bootloader version HHZ11k
Secure boot enabled
lock state unlocked
I think it's 4.4.2 or 4.4.3. I haven't installed KitKat.
Also running some xposed modules and Teamwin recovery but haven't flashed a rom or kernel
The issue
About an hour ago I got into the com.android.systemui. The screen keeps flashing and I'm lucky if I can power off the device. No chance of starting an app or getting into settings. When the device is powered up I can not access file folders through Explorer, in bootloader the device is not even recognized.
I figure I need to do a factory reset but seeing that I can't reach settings I don't know how to do this exactly (I assume it's OK to do with a rooted device that's still running the custom ROM?) Should I do it through TWRP? And if so, how do I proceed? I've read a few threads that deal with similar issues but I haven't found a manual that I feel fits completely which make some uncomfortable to try.
Thanks very much in advance,
T
Also, I just found this one: http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Would that be the right way to go?

First of all there isn't such thing as a "soft brick" It's either bricked or it's not.
You said you haven't "installed KitKat", well 4.4.x is KK. You sure you know what you're doing?
I suggest you see the first link of my signature and read some threads before you proceed with doing anything further to your device. You should be able to reflash factory images.

Lethargy said:
First of all there isn't such thing as a "soft brick" It's either bricked or it's not.
You said you haven't "installed KitKat", well 4.4.x is KK. You sure you know what you're doing?
I suggest you see the first link of my signature and read some threads before you proceed with doing anything further to your device. You should be able to reflash factory images.
Click to expand...
Click to collapse
Thanks for the swift reply Lethargy,
I referred to softbrick as in I can still boot but it gets into a loop I can't get out of. Apologies for the confusion re KitKat, I meant I hadn't installed 4.4.4.
I actually just ran the One click recover in the thread I mentioned and it worked like a charm, can use the phone again so marking this as solved!

Taeglian said:
Thanks for the swift reply Lethargy,
I referred to softbrick as in I can still boot but it gets into a loop I can't get out of. Apologies for the confusion re KitKat, I meant I hadn't installed 4.4.4.
Click to expand...
Click to collapse
That would be a "bootloop" or non-boot, not a "soft-brick".
Taeglian said:
I actually just ran the One click recover in the thread I mentioned and it worked like a charm, can use the phone again so marking this as solved!
Click to expand...
Click to collapse
Cool. But I do still suggest you have a look at various threads in the first link of my signature to learn a little more.

[Bootloader][d800][JB/KK/LP][2015.07.29] Flash JB/KK/LP Bootloader

Easily Switch Between JB/KK/LP Bootloader
!! d800 ONLY !!
Make sure you flash the right model!​
With the advent of BUMP, we can now use the KK bootloader. A lot of projects preserved the old JB bootloader, since that was needed due to loki. This is the easy way to update your JB bootloader to the new KK bootloader.
Inspired by @dorimanx who did this for the d802. I followed suit and made this for the d800.
What this is:
As it simply says, it upgrades (or downgrades) the bootloader. This includes several other small partitions, in addition to aboot and sbl1.
Sources:
10d & 20c - Extracted from TOT file
20y & 30f - I started with 20d, then did FOTA to 20y and extracted the partitions. Then I did FOTA to 30f and again extracted the partitions.
What this is NOT:
This does not touch your boot, recovery, or modem/radio partitions. You must make sure those are compatible BEFORE flashing this.
WARNING: You can easily brick your phone if you mess this up! This is for d800 ONLY!!! Also, you must have BUMPed boot and recovery images already on your phone to use KK bootloader or you will get fastboot error (or it just won't boot). JB supports BUMP images and LOKI images. KK only supports BUMP.
Lollipop Information:
Special LOLLIPOP WARNING: At this time, the Lollipop BL is not exploitable. Therefore, if you flash Stock LP BL, you will probably brick, or at a minimum, you will lose access to recovery.
To use a BUMPED lollipop ROM, you should install the Lollipop Bump bootstack on my site. It is all of the 30f Lollipop partitions, with a 20y aboot (so bump will work).
Download:
Did you read the warning above? If not, DO NOT DOWNLOAD.
Did you read it twice? If not, DO NOT DOWNLOAD.
Do you understand everything it says? If not, DO NOT DOWNLOAD.
Do you know how to recover if you mess your phone up? If not, DO NOT DOWNLOAD.
I do not want any posts saying "HALP I MESSED THIS UP."
Which bootloader am I currently on?
The only sure way to know is to flash one, or know which one you flashed last.
You can get an idea of your bl when you use the button combo to enter recovery (VolDwn+Pwr, release and repress when LG logo comes up, hold until menu comes up) the screen looks different. On JB the phone asks you to repeatedly press power for factory reset. On KK the phone has you use the volume rocker to pick different menu options.
Download:
https://www.gregtwallace.com/lg-g2/d800_d801-bootloaders/
Again, thanks to @dorimanx.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal

Update 2015.07.29
-Version 1.1 does NOT flash misc partition.
+Misc contains things like MAC addresses and doesn't need to be flashed.
Update 2015.05.12
I have added the 20y KK bootloader, which appears to be different than the originally posted 20c. Both are now posted.
Additionally, I added the LP 30f bootloader. WARNING: This bootloader is not (yet?) exploitable! Flashing it will likely brick your device, or at the very least it will break your recovery. You have been warned!

Reserved2
Reserved2

Cool thing! And nice work! I was just looking around to learn more stuff about bootloaders ..did dorimanx made a thread for d802?
Your awesome version of TWRP is bumped, dorimanxs kernel is bumped too thats all i need to switch on kk bootloader

raulx222 said:
Cool thing! And nice work! I was just looking around to learn more stuff about bootloaders ..did dorimanx made a thread for d802?
Your awesome version of TWRP is bumped, dorimanxs kernel is bumped too thats all i need to switch on kk bootloader
Click to expand...
Click to collapse
No he didn't, but he posted the d802 version under his kernel thread, which is linked in my signature.

Great initiative, @blastagator!
Now... On to the actual bootloader... stuff.
EDIT : Nevermind. Just noticed that this is for the D800 only... and I have a D802, lol.

You, sir, are a badass. Thank you for this
Sent from my LG-D800 using XDA Free mobile app

Formhault said:
Great initiative, @blastagator!
Now... On to the actual bootloader... stuff.
EDIT : Nevermind. Just noticed that this is for the D800 only... and I have a D802, lol.
Click to expand...
Click to collapse
As stated in the OP, dorimanx made exactly the same zip for the d802 to update the bootloader and the other necessary partitions.
You'll just need a bumped recovery + bumped kernel.
Just in case you would like to upgrade to KK bootloader
I'm just waiting for render to release bumped R26 and the first thing I'll do is update the bootloader

Could someone please be kind enough to make one for vs980? I tried making one myself by picking the same exact files off of vs980 kdz but it didn't work.

Voltaine said:
I'm just waiting for render to release bumped R26 and the first thing I'll do is update the bootloader
Click to expand...
Click to collapse
Me too, I guess :silly:

idoluvizsick said:
Could someone please be kind enough to make one for vs980? I tried making one myself by picking the same exact files off of vs980 kdz but it didn't work.
Click to expand...
Click to collapse
I used this: http://forum.xda-developers.com/showthread.php?t=2600575
Extract the partitions out of the stock tot, then just use a simple flash script. Again, if you don't know what you're doing - it is VERY easy to mess up and DIFFICULT to recover from.

Noticing this says bumped boot and recovery required in the op. Was wondering even if I'm on stock everything, boot included, do I still need to be bumped. I would say yes on the recovery due to the nature of how autorec worked. But what about boot, since it is bone stock? Thanks for the info. Thanks for your work on this phone.

Yikes I tried this with 12/5 AICP 5.0 drgravy d800, Render5, and blastagators bumped TWRP 2.8.2.0.
Installed the KK-20C bootloader, the device spent a long time on on the LG logo with a few vibrates, then it blackscreened. While blackscreened plugging into PC started charging and gave me access to Internal Storage. Tried a power off and back on again with same result.
Luckily, manually going into TWRP and flashing the JB-10D bootloader got things back to normal.
EDIT: Just dawned on me that I had the dr87 Working Rotation JB Baseband installed. Perhaps I should have tried with the KK Baseband?

buffal0b1ll said:
Yikes I tried this with 12/5 AICP 5.0 drgravy d800, Render5, and blastagators bumped TWRP 2.8.2.0.
Installed the KK-20C bootloader, the device spent a long time on on the LG logo with a few vibrates, then it blackscreened. While blackscreened plugging into PC started charging and gave me access to Internal Storage. Tried a power off and back on again with same result.
Luckily, manually going into TWRP and flashing the JB-10D bootloader got things back to normal.
EDIT: Just dawned on me that I had the dr87 Working Rotation JB Baseband installed. Perhaps I should have tried with the KK Baseband?
Click to expand...
Click to collapse
I don't think it works with JB based kernels.

sr20ryda said:
I don't think it works with JB based kernels.
Click to expand...
Click to collapse
I used Render 5 which is a L Kernel. Is this JB based?

buffal0b1ll said:
I used Render 5 which is a L Kernel. Is this JB based?
Click to expand...
Click to collapse
Yes. All the LP builds have JB based kernels AFAIK.

sr20ryda said:
Yes.
Click to expand...
Click to collapse
Is there a bumped kernel that d800 can use on L with KK bootloader then?

I don't believe so.

It works only with dorimanx on stock based rom, no cm aosp aicp et
_____________________________Write less read more and be smart

siggey said:
It works only with dorimanx on stock based rom, no cm aosp aicp et
_____________________________Write less read more and be smart
Click to expand...
Click to collapse
After reading ALOT of info heres where i am. I think our good guy render is trying to get his kernel working bumped for KK bootloader and lollipop builds.. heres where i got sad.
It seems recently there is ALOT of dev arguements on the nature of opensource bump so much so that the the orginators have actually closed down and stopped development on the project. lets not go any further with that disucssion, there are other threads for that if you care to read.
So basically i dont have a build environment right now to try to bump any kernels using the instructions and I'm not sure what to think right now considering what i HAVE read. I actually stay away from posting alot of things on XDA that i do on my own, because of this very nature i have seen pop up to many times to count. So to summerize:
Dont have a build environment where i am right now to try...even when i get home im not sure how i will feel since i do respect the codefire guys but understand why someone would have done what they did. If i am successful getting someone elses work say renders kernel, to finally boot ill let him know but im sure render will figure it before i even do that :highfive:

Needing rom flashing advice

The phone is not fully booting.

What?

aholeinthewor1d said:
What?
Click to expand...
Click to collapse
Just because my Verizon pixel ran into a boot loop after Resurrection rom a change grom purenexus. I've known issues from the past to be about build, ( European, ECT.) Or order of operations. Even supersu, usually after the fact for supersu. As a junior member with some xp I started this thread anyway after an Odin to stock. What did I do wrong,? Google pixel, Verizon, NOF26V, unlocked. I flashed twice, then Odin. Still looped.

April fool's ... ? Odin ... Really

piperx said:
April fool's ... ? Odin ... Really
Click to expand...
Click to collapse
I was thinking the same thing

Right so... I wanted to flash Resurrection rom. I did that with TWRP duh. And pixel won't finish it's boot for 30plus minutes after. So what do I do? I Odin stock NOF26V in download mode to get my phone running again. Comprehend?

piperx said:
April fool's ... ? Odin ... Really
Click to expand...
Click to collapse
Yeah, Odin. Download mode. That's how to save a phone from a bad rom flash

alladinscastle said:
Yeah, Odin. Download mode. That's how to save a phone from a bad rom flash
Click to expand...
Click to collapse
Odin is a Samsung thing. Fastboot mode or recovery or bootloader mode are the usual terms for a Google phone.

alladinscastle said:
Right so... I wanted to flash Resurrection rom. I did that with TWRP duh. And pixel won't finish it's boot for 30plus minutes after. So what do I do? I Odin stock NOF26V in download mode to get my phone running again. Comprehend?
Click to expand...
Click to collapse
I comprehend just fine, the real question though:
Do you have any idea what your doing ?

piperx said:
I comprehend just fine, the real question though:
Do you have any idea what your doing ?
Click to expand...
Click to collapse
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?

alladinscastle said:
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
Click to expand...
Click to collapse
Really?
https://forum.xda-developers.com/pixel-xl/development/rom-t3548615

If im running 7.1.1 and Resurrection is 7.1.0. could the downgrade from flashing cause my problem?

alladinscastle said:
If im running 7.1.1 and Resurrection is 7.1.0. could the downgrade from flashing cause my problem?
Click to expand...
Click to collapse
wipe your data and cache partitions.

alladinscastle said:
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
Click to expand...
Click to collapse
How in the hell do people flash things they know nothing about?
Do you read at least the op of anything you flash?
I'm still tryin to get over the Odin post

Answer this. Resurrection's thread title says 7.1.1. The Op says 7.1.0r7. " users are now asking if the new build will be 7.1.2. " What is is the current build based on. If the Op is outdated, what good is it?
P.s. I have seen some op updates on the rom thread... ok, some things are still outdated.
Your attitude needs work, maybe consider not replying. I do know some things about rom flashing. It is unnecessary to be rude. It is ok to make corrections about a post.

piperx said:
How in the hell do people flash things they know nothing about?
Do you read at least the op of anything you flash?
I'm still tryin to get over the Odin post
Click to expand...
Click to collapse
Do you enjoy showing off? At be more class at it.......

alladinscastle said:
Do you enjoy showing off? At be more class at it.......
Click to expand...
Click to collapse
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science

piperx said:
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
Click to expand...
Click to collapse
I agree on this. I do the same, read, read, and read some more until I understand what I am doing. I used to root phones that aren't "google" versions and learned how much of a pain it was.. therefore I am owned the last Nexus brand, and the first Pixel. Using a Google phone is so much easier! But yeah, reading is key. I hopped into this thread to see if someone needed some help, read through the posts, and was so lost as to what this user is doing.. Odin? If the user who is having issues is reading this, just boot your phone to bootloader, use fastboot and format userdata the device (wipe/format) and then fastboot flash the stock 7.1.2 image and wait for custom ROMs to update.

piperx said:
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
Click to expand...
Click to collapse
Alright moving on. Just generic crap on my thread here

Great news. I'm am now running Resurrection ROM. All I did differently for my Verizon pixel was move from 26V to 27B build. I flashed the rom and twrpRC1, Then I rebooted to bootloader mode and flashed the vender using the adb fastboot command. "Fastboot flash vendor vendor.img" need more specific instruction. See me!!! No more problems here.

Defective ONnePlus 7 ? Help me out pls

Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .

The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.

@PriPhaze is your device stock(bootloader locked) or modified in any way?

aaycce said:
The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.
Click to expand...
Click to collapse
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
strongst said:
@PriPhaze is your device stock(bootloader locked) or modified in any way?
Click to expand...
Click to collapse
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.

PriPhaze said:
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.
Click to expand...
Click to collapse
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?

strongst said:
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?
Click to expand...
Click to collapse
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.

PriPhaze said:
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.
Click to expand...
Click to collapse
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.

strongst said:
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.
Click to expand...
Click to collapse
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS

PriPhaze said:
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS
Click to expand...
Click to collapse
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.

strongst said:
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.
Click to expand...
Click to collapse
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.

PriPhaze said:
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.
Click to expand...
Click to collapse
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...

strongst said:
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...
Click to expand...
Click to collapse
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US

PriPhaze said:
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US
Click to expand...
Click to collapse
Yes, everything is on board. It's the worst case for, sadly...
Or you buy a device with broken screen and exchange the board /display. Depends how much you have to spent for this at all.

PriPhaze said:
Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .
Click to expand...
Click to collapse
Ah yes, the common misconception that power shuts it off. Nope, not this phone. You have to hold power and volume up together to power off the phone when it crashes. Make sure you're using the latest platform tools (adb/fasboot) to unlock your phone. Make sure oem unlocking is enabled in developer settings after you've unlocked, having it disabled for some reason does screwy things. Mine was disabled once when I downgraded to Android 9 using the all in one tool available on xda, I thought I bricked the phone because it wouldn't boot after a reboot. Flash the latest oos twice through the system local upgrade feature, this will put the current oos on all partitions. Use the correct twrp, the unified versions found on xda 3.3.1-75 and 3.3.1-76 work well for me. The installer zip for those can be used in magisk to flash twrp after an OTA update before reboot. So, local upgrade 100% -> magisk modules "+" twrp 3.3.1-75 unified installer zip -> reboot to recovery -> flash magisk 20.3 at least (20.4 is available now). Do this twice so that everything is the same version on all the partitions. Lastly restore apps with swift backup without data, I know it's not ideal but may be necessary because some app's data may be corrupt and causing this. Good luck. Of course at any time you have it running you can reboot in safe mode (touch and hold restart until the dialogue pops up) and see how long you can use it without any third party apps to confirm that it is an app you installed.

Man I had the exact same problem as you and I got it fixed this morning after nights of fastboot commands trial and error found this thread forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Tried a few times before it worked but saved my phone all I had was fastboot mode and no recovery make sure to manually flash all fastboot commands you will then get stock recovery back wipe using all 3 options go 1st 2nd 3rd and then 1st wipe again after reboot phone might hang just force reboot and fixed

I really appreciate all the replies really but hmm im guessing there's a misunderstanding on what im saying.
I do know how to flash and recover one plus devices using MSM tool if neccesary, also to flash the fastboot rom .
The thing here is that everytime i recover the phone and all seems stable and working good , after a2 days more less it will random freeze of death and you cant even reboot holding power button NOTHING! is completely freezed.
So yea, thats pretty much it, i have tried already all that you said so far :c.

Question Wow.. I actually bricked it?

I am a very experienced ROM enthusiast and owned plenty of Xiaomi/Oneplus devices.. This is my first pixel device. I loved the phone, more than the other mentioned companies. My pixel 7 Pro was my prized possession.. I've came close a couple of times botching a ROM flash, even once with my p7p (installing evo with February firmware instead of Jan, phone would boot to bootloader for a total of 2 seconds before dying again, had to spam flash phone in pixel flasher app until it recognized and luckily it did) but this time, trying to go from latest feb build to jan before flashing evo, my ****ing cable did something in the middle of flashing the second partition (b partition) and was almost to system, the partition it flashes before booting.. it was flashing the product partition.. literally already flashed every other partition except partition and system on the b slot. A slot was fully flashed.. phone literally wont respond to plugging into computer, into charger, holding down every combination of buttons... doesn't matter. I'm stumped how flashing a factory rom could have gone this horribly.. especially so late into the flashing process..
Beware guys; Make sure the cable you're using to flash is stable!
attached in this post is the logs I have pulled from the pixel flasher app.. if someone could bounce some ideas off of me or somehow make this make sense to me, it would be gladly appreciated.

Holding down the down volume button when starting doesn't enter bootloader? If it does, use Google's online Android Flash tool to go back to stock.

Try a different cable.
Try a different USB port.
Try another computer as well.
If any of these prompt some response, I think there's hope. Also try booting into fastboot from bootloader as well as recovery.

Prob hard brick.

im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?

xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.

Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.

xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)

Arealhooman said:
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Click to expand...
Click to collapse
A battery for my desktop PC?

xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Google for "uninterruptible power supply" ...

xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Yeah, no idea.

Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?

xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
The real answer to this is why google and the android community as a whole is pushing away from having a supporting third party recovery menu (implementing new partitions like init_boot and vendor_boot for recovery, also no working twrp). Why do you think Evolution ROM pushes so hard to be different and when flashing their newest build you do it not through the usual scary tedious bootloader way (THE SAME WAY WE ARE SUPPOSED TO FLASH OUR FACTORY ROMS) to making their own recovery, which obviously means only flashing one partition, and adb sideloading the rom. its like google wants you to break your phone and they are making it more convenient for third party roms to package theirs the same way. i should have never left evo.. haha.
Oh, and sorry for the late reply. I thought I would leave my phone alone for a little to see if it would help; I'm accident prone and lose things constantly, and what do ya know I just lost my phone that I can't even call to find lmao. Ill keep updated on everyones opinions on what i should try whenever i find it

krakout said:
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
Click to expand...
Click to collapse
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.

EtherealRemnant said:
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
Click to expand...
Click to collapse
Ah I see, makes sense.

xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Oh brother, how often does that actually even happen?

HipKat said:
Oh brother, how often does that actually even happen?
Click to expand...
Click to collapse
Sure, not really often. But when it does..

Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.

zacattackkc said:
trying to go from latest feb build to jan before flashing....
Click to expand...
Click to collapse
It sounds like you may have tripped some anti-downgrade code.
EDIT: I can confirm that the bootloader version was changed in the FEB image as compared to the JAN image.

96carboard said:
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
Click to expand...
Click to collapse
Well, I use Samsung, so I am assuming fastboot is similar…