Database Info

[Q] Nexus S i9020A Bricked due to failing power button - Odin seems the last hope?

Hi everyone,
INTRO:
So the power button on my Nexus S broke. No big deal, I remapped it to the search button and used the volume rocker to wake the device; an option that was embedded in Cyanogenmod9.
Then I upgraded to CM10... since I did that on top of CM9, my volume rocker option was still enabled, but the option is no longer in CM10's GUI.
I had some annoying issue and thought maybe I should wipe my phone; which I did.
Sadly, I realized that my "wake using volume rocker" option was no longer enabled, and there is no GUI to turn it back on.
I then found a .zip package that was supposed to enable the option but, I guess I went too fast, now my phone is stuck on a bootloop.
THE PROBLEM:
Since my power button is broken, I cannot navigate in the fastboot menu to recovery and fix the ROM.
Worst, since the power button is somehow shorted (i.e.: it powers on automatically when I insert the battery) Fastboot is not working properly and my PC never sees my phone, so you can forget about fastboot boot recovery.img
So: boot loop, power button broke, no recovery, no fastboot. =(
I searched quite a bit and found out you could get the Nexus S in download mode and get it to work with ODIN using a USB JIG.
I made myself such a JIG and successfully put the phone in some kind of download mode where my PC sees it, fastboot devices yields nothing *but* ODIN sees the phone!
So a glimmer of hope except for the fact that finding the .tar files for the Nexus S seems impossible...
Thoughts? Suggestion? TIA!
Francis // XC3N

Oh BTW:
-Yes I saw the other posts, but none of them mention the odin files
-Yes, I know fastboot is better; but it's not working and:
-No, I can't see the device on 3 different PCs using 3 different OSes and 3 Different cables when in fastboot mode
I mean by that last line that *nothing* shows in device manager in Win7 or XP and *nothing* shows in lsusb on ubuntu
So unless someone has an idea it looks like Download mode is the only way my PC sees my phone...

My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
I think it's something to do with the micro switches giving out after a certain number of uses.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
In short, tap it until it works, once you have control of fastboot plug the usb in and your pc should detect it
Hope this helps, Good Luck
Sent from my U20i using xda app-developers app

Muckyfox said:
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
Click to expand...
Click to collapse
Hey MuckyFox thanks for your reply!
Unfortunately, that would've worked back when the power button was flimsy and still working once in a while... I did try the tapping thing but really nothing works... the button seems entirely dead and shorted. I guess at this point I might've to bring it in for repair... if the power button isn't broken then I'll be able to easily fix everything in recovery or fastboot. Sucks because I feel like I'm so close to getting it to work without spending money XD I just can't find the files for odin even though they really do seem to exist.

Allright so I found some odin files which were said to work with the i9020a
I flashed them... at some point it said "RESET!" and then odin no longer saw the device. The device is now not booting at all. FML

So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar

My power button started failing over the last couple of days. First when I would set the phone to standby it would ask me if I wanted to switch off the device, then later on it wouldnt respond at all.
Really weird solution - boot into recovery, factory restore, clear dalvik cache, voila, works good as new! (aside from losing all my settings)
Note, I barely managed to get into recovery. The power button fully stopped working halfway through and I had to take the battery out and try it a couple of times.
Oddly, even during this uber-broken phase, the power button would always switch on the device when fully switched off (not just standby) indicating to me that it wasnt just a physical broken connection.

I've mentioned this before, but a full casing for the phone with all the buttons is around $10 on eBay
Sent from my Nexus S using xda app-developers app

XC3N said:
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
Click to expand...
Click to collapse
You need stuff for SOJUA, and just the fact CSC has EUR meaning Europe in it would scare the crap out of me. Possible you just flashed stuff meant for i9020T and not i9020A.

In case anybody comes back here, I'm just gonna drop this in.

Only capacitive keys blink. Help.

Guys, I had bought options 3d about 11 months back. It was already rooted and had custom recovery installed. It was on 2.3. After sparingly using it for a couple of months. I gave it to my brother in law. He used it for a about 2-3 months.
One day while he was trying to watch some video through whatsapp, the phone screen suddenly went off. Only capacitive keys blink.
He brought the phone to me two days back.
I had a look at the phone. When I start it some starting sound is there and after a few seconds the capacitive keys blink and stay there for a few seconds and go off. If I push the power button the keys blink again. I tried booting into recovery and also I hard resetting with a few key combos. Seems it goes to recovery but I cannot see anything on the screen.
Is this some screen display or dizitizer problem or some software problem. Kindly guide me.
Today I installed lgunited drivers and started software tool. Software tool said update available. I clicked on update but it said phone battery low. I have put the phone to charge now.
Is trying to update while lg software update tool safe while the phone is rooted and having custom recovery. ( I was trying to update via tool with some wishful thinking that some magic might happen and phone will boot normally thereafter.

[Q] Phone Keeps Rebooting After It Dropped

My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.

Getting the power button fixed isn't too expensive. Hopefully that's all you need. ?

whyareallusernamestaken said:
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Click to expand...
Click to collapse
I have had this issue for the past 4 days. After many attempts of trying to bang the phone a lil onto my hand (for where the power button is located at), sometimes the phone will boot fine, for as long as you do not click the power button again it won't act up.
(I am pretty sure I didn't drop my phone when I was napping in the car, it just started out of nowhere after I have been using lollipop 5.0 with franco kernel for like 2 months without any problem).
Same sypmtoms, bootloop (looked like the power button defective / boot IC on mobo defective), can't even stay on recovery/bootloader screen/system for longer than 5 sec.
Try these :
- spam click power button, until it is able to boot into system, you will have to keep clicking, for every click you either screen on/off you will realize Power Off options may pop up, it looks like the power button has been holded for few sec to trigger the power off, but all you do was spamming the click to keep the button active, you have to click until you feel that certain point the power off doesn't pop up, then stop clicking ( remember never to touch that power button again for NOW), if after a few sec of using the phone and it doesn't force shut down (result from power button defective where it sense its being clicked and hold for like 8-15 sec). Then you are good to carry on whatever I am to tell here.
- go to about phone, click the build number for 5-10 times until you get the unlocked developer mode
- back, click on developer options, enable usb debugging mode (this will pop another message asking you if you want the device to memorise your pc's mac address) that way it is synced with your pc.
- before you proceed with any other thing, go to playstore, download power button to volume button, enable volume power, check start volume power on bootup, check screen off. This will help you greatly for not touching the power button to unlock the screen when you are working on your pc.
- if you have all the correct nexus usb driver installed onto your pc, you need to get Minimal ADB and Fastboot installed onto pc. After installing, run Minimal adb and fastboot, a command prompt windows will pop out and is automatically redirected to the minimal adb folder. key in this command
"adb devices" to see if it detects your device or not. There should be at least a device listed if you have the usb driver installed correctly
- now you can make use of adb commands to reboot into bootloader/recovery to do any flashing of system, backup all your data that you needed to PC. Download official 5.0.1 nexus 5 image and extract it into the Minimal ADB folder.
- is your bootloader unlocked? if not do adb reboot-bootloader
- fastboot oem unlock (this will wipe all your data on the phone)
- fastboot reboot after the wipe is done
After that you can actually carry on with flashing back to stock images. Look at this link http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for flashing to stock factory image.
I am not sure which step has actually solved my problem, because on my first flashing of factory image, booting into system as a brand new device (no extra softwares, yet to recover any of my data). the problem persists as long as I clicked on power button once, it'll act up again random power off and bootloop.
I actually was on a follow-up cases with google play support team from Aus as my device was bought from Aus. After the last step of factory image setting, doesn't help, I intended to ship it back for RMA as my device is still under warranty and I suspected it was the hardware issues from power button too. They will send me another refurbished device. After ending the call, they sent me link to proceed with warranty claims where I need to fill in several forms and ship the device back to them.
I decided to give it one more try, due to my phone was previously unlocked, rooted, changed to franco kernel.
By restoring to stock images made my device unroot, I was afraid of google will accuse me for unlocking bootloader voided the warranty and not willing to replace another unit for me. I locked back the bootloader, then I remembered in bootloader, fastboot oem device-info shows that a record of a phone if it has been unlocked, it will show Tampered status as True, google probably can use that to track if a device has been unlocked before. So I unlocked my bootloader again (which causing another wipe for whatever data is in the device).
So I looked up on google again and found source for changing that tampered status to False in addition to locking the bootloader again, but to change that tampered status, I need to use TWRP to run the scripted zip file, so I used fastboot boot path (it is stated in the link I gave you above) to boot into TWRP images temporarily from my desktop and ran the zip file, I always practice wiping data, cache and everything before I boot the device back into a brand new factory image.
So I went to wipe dalvik cache. Rebooted the system - it was running the Optimizing x numbers of Applications.
Upon finished with that. I was surprised that, after a few clicks of power button, the random power off issues is no longer there. I even test clicking on the power button for entire day. The symptom isn't coming back. So I emailed google play support team to cancel my warranty ticket and close the case for now.
Should there be any problem again I will probably then claim the warranty for replacement.
Its been more than 24 hours now that I am using the device without any problem of random power off and on or stuck in bootloop due to power button defective.
I suspect it is either the 5.01/5.0 lollipop with ART that is causing something wrong with the boot IC / power button defective in a long run.
Or maybe it was some settings I have changed in franco kernel ? but it was running fine for 2 months which made me doubt that it is franco kernel
Or it could be some of the apps I used to tweak my phone settings - LLama and tactile player (which I have set something condition and actions for power button) but I doubt it is caused by these either.
I will observe and see if the problem comes back after some time of using the 5.0.1 stock image now.
Oh I am also back to using franco kernel, unlocked bootloader and rooted again. Haha...
Hopefully you are able to solve the problem by trying some factory reset method + wiping cache, partition and dalvik.
If not, you probably may have the hardware issues, I have seen some other forum/websites with n5 users upon replacing the mobo, no longer encounter such problem.
Regards,
Kean

Thanks for the replies. My girlfriend was able to get the power button repaired for $80 and replaced the external button for $7 + tax, she paid $98. At least it's cheaper than a new phone.

Can't boot, restarts constantly

Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock

Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.

a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!

Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/

Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed

jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:

A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.

Question Pixel 7 Pro bricked?

I've tried flashing patched boot.img file from the December update with the january rom, because patched boot.img file from january update wasn't working. The phone rebooted twice, displayed a message that the phone failed to boot and gave me options to either restart and try again or factory reset. I chose restart and the phone is since then bricked. Black screen, occasionally if i hold some buttons it flashes faintly but thats all. If i connect it to a pc, it is able to connect after holding some buttons for 2-3 seconds as a COM device, but then it disconnects again.
Also apparently i forgot that p7p was different and did the whole thing with boot.img instead of init_boot.img.

iplux said:
I've tried flashing patched boot.img file from the December update with the january rom, because patched boot.img file from january update wasn't working. The phone rebooted twice, displayed a message that the phone failed to boot and gave me options to either restart and try again or factory reset. I chose restart and the phone is since then bricked. Black screen, occasionally if i hold some buttons it flashes faintly but thats all. If i connect it to a pc, it is able to connect after holding some buttons for 2-3 seconds as a COM device, but then it disconnects again.
Also apparently i forgot that p7p was different and did the whole thing with boot.img instead of init_boot.img.
Click to expand...
Click to collapse
Is it out of battery?

mackdacre said:
Is it out of battery?
Click to expand...
Click to collapse
sadly no, around 60-80% maybe

hello have you tried pixel flasher?

jejemc said:
hello have you tried pixel flasher?
Click to expand...
Click to collapse
i will try now, but i dont think it'll work since the pc doesn't recognize the phone. i can make the phone somehow connect to the pc for 2 secs, but it connects as COM device and instantly disconnects after that.
Edit: it did not work

and holding the power button and volume up or down for a while does nothing?

jejemc said:
and holding the power button and volume up or down for a while does nothing?
Click to expand...
Click to collapse
correct. power + vol up, power + vol down, all 3 buttons pressed at the same time - nothing, all nothing. I'm able to make the screen for a brief second if i connect the phone to charge and press all 3 buttons or volume down + power, but that's all.

iplux said:
correct. power + vol up, power + vol down, all 3 buttons pressed at the same time - nothing, all nothing. I'm able to make the screen for a brief second if i connect the phone to charge and press all 3 buttons or volume down + power, but that's all.
Click to expand...
Click to collapse
alas it means sending it sav I don't see what else to do.

jejemc said:
alas it means sending it sav I don't see what else to do.
Click to expand...
Click to collapse
small update, i just noticed that the phone is slightly warm, so its definitely on and doing something in the background with the screen completely off. I will give it a night to completely discharge and see if i can get it to show literally anything on the screen. If not, i gotta think of a way to ship it to the UK so it can get fixed, because i'm in a non supported region sadly.

Have you tried holding down the power button for 15 seconds?

febo17 said:
Have you tried holding down the power button for 15 seconds?
Click to expand...
Click to collapse
yup, sometimes that makes the screen flash for a split second and then nothing. tried pretty much any combination for up to 30 secs. sometimes its a single screen flash, sometimes it flashes twice. It's barely visible.

iplux said:
yup, sometimes that makes the screen flash for a split second and then nothing. tried pretty much any combination for up to 30 secs. sometimes its a single screen flash, sometimes it flashes twice. It's barely visible.
Click to expand...
Click to collapse
Just to see if I understand better, so the phone is on but the screen doesn't work as it should?

Try it even longer than 30 seconds (up to maybe 60 seconds) , I also had some problem with my P7P stuck and needed to push it really long

febo17 said:
Just to see if I understand better, so the phone is on but the screen doesn't work as it should?
Click to expand...
Click to collapse
i was on december android update with magisk installed. i tried today to install january update today - i patched the boot.img file (yes, i know it should've been init_boot.img), replaced the original boot file with the patched one on my pc and flashed the new january rom with "-w" parameter removed. That however didn't work (obvious reasons), i had no root. I then decided that the new boot.img file from the january update might have some issues , and decided to flash the january update with replaced boot.img patched from december update (again with -w parameter removed). The phone took it all, then the google logo popped up... after a few seconds it restarted and the google logo popped up again... it once again didnt boot, and restarted, but after the 3rd restart i was greeted with a message from the bootloader (i assume) that the system failed to load twice, and i was presented with 2 options - "restart and try again" or "factory reset the system". I chose restart, and the screen went black and that was all. (it was only after all of this happened when i realized that everything happened because i was patching the boot.img instead of init_boot.img).
Now the screen is black, no matter which button combination i am trying. Sometimes the screen flashes once or twice when i hold some buttons, but that aside- nothing. I assume the phone is still doing something in the background, because if i leave it on my bed sheets and touch it after awhile, the back is a bit warm, so obviously something is working, but im certain its not the OS.

iplux said:
i was on december android update with magisk installed. i tried today to install january update today - i patched the boot.img file (yes, i know it should've been init_boot.img), replaced the original boot file with the patched one on my pc and flashed the new january rom with "-w" parameter removed. That however didn't work (obvious reasons), i had no root. I then decided that the new boot.img file from the january update might have some issues , and decided to flash the january update with replaced boot.img patched from december update (again with -w parameter removed). The phone took it all, then the google logo popped up... after a few seconds it restarted and the google logo popped up again... it once again didnt boot, and restarted, but after the 3rd restart i was greeted with a message from the bootloader (i assume) that the system failed to load twice, and i was presented with 2 options - "restart and try again" or "factory reset the system". I chose restart, and the screen went black and that was all. (it was only after all of this happened when i realized that everything happened because i was patching the boot.img instead of init_boot.img).
Now the screen is black, no matter which button combination i am trying. Sometimes the screen flashes once or twice when i hold some buttons, but that aside- nothing. I assume the phone is still doing something in the background, because if i leave it on my bed sheets and touch it after awhile, the back is a bit warm, so obviously something is working, but im certain its not the OS.
Click to expand...
Click to collapse
I hope you solve it, good luck and stay tuned

Since this is a very new device, I suggest contacting Google for warranty repair, because that will be much easier than trying to diagnose what works and what doesn't, as well as trying to recover the device. You have a warranty; use it.

oko17 said:
Try it even longer than 30 seconds (up to maybe 60 seconds) , I also had some problem with my P7P stuck and needed to push it really long
Click to expand...
Click to collapse
just tried:
pwr
pwr + vol up
pwr + vol down
pwr + vol up + vol down
each for more than a minute, no response.

V0latyle said:
Since this is a very new device, I suggest contacting Google for warranty repair, because that will be much easier than trying to diagnose what works and what doesn't, as well as trying to recover the device. You have a warranty; use it.
Click to expand...
Click to collapse
I most likely will, i just don't want to because im in Bulgaria (a country where they dont sell the phone) which means i have to find a way to send the phone to the UK, and they will probably refuse to ship it back.

iplux said:
I most likely will, i just don't want to because im in Bulgaria (a country where they dont sell the phone) which means i have to find a way to send the phone to the UK, and they will probably refuse to ship it back.
Click to expand...
Click to collapse
Ah. Well...without the screen working, there isn't much you can do, beyond seek repair in your own country. If the screen isn't working, it's usually due to either of 2 reasons, both of which require specialty repair:
The screen and/or display controller are defective and must be replaced
The bootloader is corrupted and the mainboard must be replaced
The tools required to rescue a device with a corrupted bootloader are not publicly available, unfortunately.

This is kinda crazy....
this is probably the first time/instance I've seen where tripping up the init_boot partition (with the boot.img used instead) caused this bad of a problem! Since the Pixel 7's changed things to init_boot, there have been very many people that have gotten tripped up flashing the boot.img to it, but it usually just results as a bootloop and a simple reflashing of the stock init_boot properly fixes things!
Are you sure you tried completely draining the battery? A hard reset can sometimes do wonders...
If Google doesn't "play ball", I'm sure you could find some 3rd party repair company/shop that would -- of course this will also cost money though...
Hopefully it works out for you OP!