Develop Bugs

My Desire doesn't power on, doesn't recharge when plugged to AC

I've got a new (or refurbished, can't tell) Desire from HTC customer care yesterday, i rooted/s-off, and was playing with it withoout any issue. Then i booted in fastboot mode, trying to flash a custom splash image, but fastboot got stuck on the message "waiting for device". I waited for a while, then chose the option "reboot bootloader". Tried using fastboot again, but still the same. Tried to reboot into recovery, but the phone was stuck at the alpharev splash screen. I waited some minutes, pulled off the battery and put it back in. The phone doesn't power on. When plugged to pc or AC, the led does not turn on. I also tried removing the sim card, the sd and the battery and plugging it again to AC, but it's still not working. Seems totally dead. Is there something i can try before sending it to HTCfor repair (again!!!)? Will they be able to tell that the phone was rooted even if it is practically impossible to boot it?

did you try to press the power button and the down volume key for about 20 seconds? sometimes that kicks it on. Also htc will not be able to tell if it is rooted or not. I sent one in for repair that was s-off and a custom rom and the same one came back fixed and reflashed with proper rom. I had to s-off and root again. Hope this helps.

I tried holding vol- and power for about 30 seconds twice, but nothing happened. I'll send it for repairs tomorrow. Thanks anyway for the advice.

Sorry your having problems. Good luck.

Sent it to an authorized lab for repairs... It took 3 weeks the first time... Another 3 weeks without my phone! >_>

c4p3fi3rr said:
Sent it to an authorized lab for repairs... It took 3 weeks the first time... Another 3 weeks without my phone! >_>
Click to expand...
Click to collapse
Rule #1 when rooting and flashing..... always have a back-up phone. (I keep 3)

[Q] "Unfortunately, the process com.android.phone has stopped."

Hi guys, I'm very sorry if this has been solved already but I've been searching a lot now and none of the methods seemed to help me. I'm running a One X International. Until yesterday, I was running one of the older Cyanogenmod 10 Nightly builds but due to some performance issues and whatnot (nothing major), I decided to finally put in some work to update my phone to 10.1. My HBOOT was still on one of the older versions so after searching around, it seemed reinstalling the stock ICS and then doing some OTA updates would be the easiest way (for a n00b like me).
After doing so, I unlocked my bootloader again, re-rooted my phone, installed a newer version of CWM Recovery and finally flashed the latest stable build of CM 10.1. My first problem came after rebooting, where it would just hang at the Cyanogenmod ring loop and nothing else. I booted back to recovery and wiped everything (cache, data, dalvik etc.) and did a factory reset then reflashed the rom. This time it booted up but then, the "Unfortunately, the process com.android.phone has stopped." kept popping up. I literally can't do anything (there's a microsecond of space after I click OK before it would pop up again). I have read some people suggesting to others that they need to do a factory reset but I've tried doing that and it still didn't work. I've even tried installing the latest Nightly build of CM10.1 but it still didn't seem to make any difference.
Could someone please offer some advice? Thanks a lot in advance.

I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...

MarcusJKX said:
Could someone please offer some advice? Thanks a lot in advance.
Click to expand...
Click to collapse
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?

matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
I'm hoping that it's not and somehow I doubt it since I didn't have any problems like this until what I described earlier.
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
Click to expand...
Click to collapse
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.

MarcusJKX said:
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
Click to expand...
Click to collapse
he means
Code:
fastboot flash boot boot.img

matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
matt95 said:
he means
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.

MarcusJKX said:
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
Click to expand...
Click to collapse
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly

have a good read on how to flash a rom
http://forum.xda-developers.com/showthread.php?t=2069904

ll_r1d0_ll said:
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
Click to expand...
Click to collapse
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.

MarcusJKX said:
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
Click to expand...
Click to collapse
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging

ll_r1d0_ll said:
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
Click to expand...
Click to collapse
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?

MarcusJKX said:
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
Click to expand...
Click to collapse
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you

ll_r1d0_ll said:
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
Click to expand...
Click to collapse
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).

MarcusJKX said:
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
Click to expand...
Click to collapse
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/

ll_r1d0_ll said:
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
Click to expand...
Click to collapse
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...

MarcusJKX said:
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
Click to expand...
Click to collapse
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go

ll_r1d0_ll said:
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
Click to expand...
Click to collapse
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!

MarcusJKX said:
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
Click to expand...
Click to collapse
glad to know that your htc one x is running like a fire well that method is just to show the current battery level nothing else ...and i had flashed the boot.img after the room but it worked for me cux i did fix permission wipe davlik cache and partition cache too...on some roms it works for me and on some roms it doesnt..well its better if you flash the boot.img before installing the room well um glad to help you and sort out your problem

Hard bricked? Bootloop can't get past bootloader unlocked warning

Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.

nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
Click to expand...
Click to collapse
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/

ZVNexus said:
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.

nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
Yeah might just have to wait until it dies.

nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
This has never failed!!! .. Unless its hardware
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
Turnoff.. hold the power button and both v+ and v-
For about 10secs.. hope it works for you

nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
Click to expand...
Click to collapse
Sorry for replying old post. I have been facing this critical scenario for last two days. The phone never turned off, always looped through unlock warning. No, button working. Can you please share , what about your findings at the end ??

Help! Pixel 3 XL wont turn on after Android Q Beta 6 OTA Update

Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?

wincaffeine said:
Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
Click to expand...
Click to collapse
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.

boe323 said:
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
Click to expand...
Click to collapse
I have tried what you suggested. Still nothing.
If I can I'd try to resolve this without returning the thing but yeah, it may really be a hardware fault. Guess I have to wait for a miracle to happen (like the phone turning on by itself after several hours, like with some posts that I have found around).
If all else fail, maybe I'd just ask Google to replace it.
Thanks anyway :good:

You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk

kentek said:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk
Click to expand...
Click to collapse
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks

wincaffeine said:
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
Click to expand...
Click to collapse
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)

boe323 said:
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
Click to expand...
Click to collapse
Because of warranty?

Question Pixel 6 Pro won't boot / Pixel Rom recovery

Hello hello,
Someone on another website told me to visit you guys here!
My Problem is as follows:
So around 6 hours ago my Pixel 6 pro decided to just turn itself off. I tried various methods of starting it, pressing different button combinations etc but it is completely unresponsive. I tried charging it for several hours but that also didn't do anything. The screen won't turn on at all.
The only sign of life that I have is when connecting my phone to my PC via USB and pressing all 3 buttons (Power, Volume up and down) then a device called "Pixel Rom Recovery" will pop up for a little bit. It disappears when letting go of the power button or after around 20 seconds. If I keep pressing the buttons it will apear again and do the same thing.
What I basically wanna know is:
Is there a way to still recover my data?
Is there a way for me to save my device?
I got some more or less important stuff on my phone and it would be a shame if it all was gone.
How ****ed am I?
Thank y'all for all your help!

Hi,
If you cannot turn on your phone, it'll be difficult to help you. Pressing other 30 sec power button doesn't run ?
In parallel did you contact the Google pixel support ?
It's not to scare you, but I had the same issue on a old Samsung S8 and it was the motherboard 🫤
Hope it's not the case for you !!

Fadey_Fadington said:
Hello hello,
Someone on another website told me to visit you guys here!
My Problem is as follows:
So around 6 hours ago my Pixel 6 pro decided to just turn itself off. I tried various methods of starting it, pressing different button combinations etc but it is completely unresponsive. I tried charging it for several hours but that also didn't do anything. The screen won't turn on at all.
The only sign of life that I have is when connecting my phone to my PC via USB and pressing all 3 buttons (Power, Volume up and down) then a device called "Pixel Rom Recovery" will pop up for a little bit. It disappears when letting go of the power button or after around 20 seconds. If I keep pressing the buttons it will apear again and do the same thing.
What I basically wanna know is:
Is there a way to still recover my data?
Is there a way for me to save my device?
I got some more or less important stuff on my phone and it would be a shame if it all was gone.
How ****ed am I?
Thank y'all for all your help!
Click to expand...
Click to collapse
So this is in fact just an undocumented Emergency Download Mode that Google Custom Exynos SoC has natively built into it in case of the rare event of a bad boot loader.
I’ve been doing an extreme amount of research lately about bootROM’s, how they communicate, the Driver rule support for interfacing with the phone while it’s Pixel ROM Recovery. The viewable name for the Exynos USB DownLoading mode.
Can I get you to dm me on Telegram? It might be helpful to have more people. I’ll be glad to help in getting this figured out. It could help a lot of other people who don’t have a Pixel 6 too

I have the same issue after trying to update to 1205. I see the Pixel ROM Recovery and a COM port.

If you cannot enter fastboot mode, no way to recover your phone.

Was there a solution to this? The same thing happened to me. When I get to the bootloader and hit recovery the screen just goes black.

redplayer5 said:
Was there a solution to this? The same thing happened to me. When I get to the bootloader and hit recovery the screen just goes black.
Click to expand...
Click to collapse
if u can boot into fastboot just flash the latest factory image from google

w_tapper said:
if u can boot into fastboot just flash the latest factory image from google
Click to expand...
Click to collapse
Can I do that even though my device is locked?
Is there a tutorial?

redplayer5 said:
Can I do that even though my device is locked?
Is there a tutorial?
Click to expand...
Click to collapse
nvm i dont think u can do it if bootloader is locked