My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Queentus said:
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Click to expand...
Click to collapse
try this one here
if not, call harware support for a possible rma
reyscott said:
try this one here
if not, call harware support for a possible rma
Click to expand...
Click to collapse
Won't work cause I can't even get to the bootloader. Thx anyway.
call google support to initiate RMA.
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
Thanks for the reply.
My Pixel is already on it's way to RMA.
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Same thing happened to me last night. RMA is on its way, but this month old Pixel XL is dead.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
do you have an advanced guide to fix it? I have pixel past warranty that has the same problem
JimSmith94 said:
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Click to expand...
Click to collapse
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
fiverings said:
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
Click to expand...
Click to collapse
My post was over three months ago and as I said, I got a refurb replacement, which I have since sold and have a Pixel 2 XL. Guess I should have said that although my computer recognized it, adb didn't. That's why I was asking if there was any other way to retrieve the data. I ended up using a week old backup so it wasn't too bad.
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
Click to expand...
Click to collapse
I was able to get it to boot into twrp. Should be OK from here. Thank you.
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
I was able to get it to boot into twrp. Should be OK from here. Thank you.
Click to expand...
Click to collapse
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
I'm sorry I should have responded sooner. I don't remember much, but I had a feeling that it was still running because it was warm so I left it alone for a couple hours to see if it would die and then I could try to boot it again it's exactly what I did but what was funny was that it still had battery life when I turned it back on I hope you had some some luck.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
perfectswanson said:
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
Click to expand...
Click to collapse
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
nikinnikin said:
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
Click to expand...
Click to collapse
You gotta be kidding me. Last time I left the phone alone, and my hunch was that it would run out of power, and then you can atleast get into the bootloader. I fixed it before. I wish I could get a hold of software those guys use to repartition, or however they do it. We have Pixel 3 leaks, but no repair software. All I did was install TWRP, and it said no OS installed. It just kept booting up into TWRP. Then I switched slots to see if that would change it, but I think that might have been what screwed it up.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
What version of TWRP did you use?
---------- Post added at 01:50 PM ---------- Previous post was at 01:37 PM ----------
I just got back into the bootloader. After a dozen times I just held down and power for like five seconds. Should I try recovery and try to remove Magisk, or should I just try to flash 9.0?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
What I did this time that was different, and I don't know if this is what helped or what, but this time I plugged in headphones and held power and vol down.
Putting the headphones in worked, or maybe it was just a fluke, but it worked on the first try. I got into Bootloader, "fastboot boot twrp.img", then I flashed the magisk uninstaller zip, the booted back to bootloader, and did flash-all.bat. It said it failed on the vendor partition, but everything still works.
Related
Please help urgently! So I just S-OFF'd my phone (right after unlocking my bootloader via htcdev) and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Louis118 said:
Please help urgently! So I just S-OFF'd my phone and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Click to expand...
Click to collapse
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Aldo101t said:
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Click to expand...
Click to collapse
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Louis118 said:
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Click to expand...
Click to collapse
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
you still have TWRP INSTALLED, do you have a backup.
Aldo101t said:
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
you still have TWRP INSTALLED, do you have a backup.
Click to expand...
Click to collapse
How do you expect me to boot into it? I told you, pressing any other mode besides power off, causes the blue screen loop
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
try powering it off then go back to bootloader and try to get to recovery again
Aldo101t said:
try powering it off then go back to bootloader and try to get to recovery again
Click to expand...
Click to collapse
Nope, still does the blue loop.
Louis118 said:
Nope, still does the blue loop.
Click to expand...
Click to collapse
well, that's the sh^ts, I don't know at this point.maybe someone else can chime in here that can help.
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
iElvis said:
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Louis118 said:
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Click to expand...
Click to collapse
Uh Oh protection isn't available in the UK.
As you unlocked your bootloader and got S-OFF, they will almost certainly charge you for repairs as this isn't a hardware issue and was actually caused by you flashing your phone.
Sent from my HTC One M9 using Tapatalk
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
LLegion said:
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
Click to expand...
Click to collapse
I'm able to enter the boot loader menu (with the options to reboot, power down, download mode and bootloader). Unfortunately, clicking any of the options (apart from power down) causes the blue screen boot loop to continue.
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
LLegion said:
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
Click to expand...
Click to collapse
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Louis118 said:
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Click to expand...
Click to collapse
You said before that fastboot wasn't working. It's working now? Does it show up in fastboot devices?
If so, you might try running a RUU from bootloader.
The trixk is to flash and just after reboot press power and down vol to wnter immediatly into rexovery twrp just as it says in the link...just do it and will go into twrp once you have entered justflash any nandroid or flash a zip ruu from sd card in a sexond boot
I'm not able to enter RUU mode...
TWRP for U Play
WARNING: SOME USERS ARE EXPERIENCING BOOTLOOP AFTER OTA UPDATING WITH TWRP.
DO NOT FLASH THIS RECOVERY INSTEAD USE FOR TEMPORARY BOOT IF YOU WANT OTA UPDATE
For direct booting without installation use
"fastboot boot twrp-3.1.1-0-alpine.img" in the bootloader menu (white screen )
If you want permanent installation follow these steps
NOTE: Please Check the partition table for your model and flash recovery to that block,
using wrong block can brick your device
use this command in terminal emulator or adb to check partition table
Code:
cat proc/emmc
for me its mmcblk0p39
Boot twrp from bootloader
Code:
fastboot boot twrp-3.1.1-0-alpine.img
now that your booted into twrp open adb and use these commands
Push Recovery Image to phone
Code:
adb push twrp-3.1.1-0-alpine.img /data/local/tmp
Set permission for recovery image
Code:
adb shell chmod 777 /data/local/tmp/twrp-3.1.1-0-alpine.img
Backup Current Recovery Image (in case you want to go back or failed)
Code:
adb shell dd if=/dev/block/mmcblk0p39 of=/sdcard/backup.img
Copy recovery to block
Code:
adb shell dd if=/data/local/tmp/twrp-3.1.1-0-alpine.img of=/dev/block/mmcblk0p39
Download
Source
Github
Can someone of devs create roms for our htc u play??
dranzer006 said:
TWRP for U Play
Click to expand...
Click to collapse
Has this been tested? I tried another twrp recovery and it's left my phone in a bootloop after trying to do a system update
Dutty106 said:
Has this been tested? I tried another twrp recovery and it's left my phone in a bootloop after trying to do a system update
Click to expand...
Click to collapse
yes i have used it however you need to have s off to install it. Else you can just boot it temporary ( fastboot boot )
OTA updates might crash the system
dranzer006 said:
yes i have used it however you need to have s off to install it. Else you can just boot it temporary ( fastboot boot )
OTA updates might crash the system
Click to expand...
Click to collapse
Thanks for that, how do you recover after OTA crashes the system? I wish I'd known, I'm trying to see if I leave it off for about 72 hours if it will switch back on as advised in another forum. How do you get S-OFF on HTC U Play? I've only managed to unlock bootloader
Dutty106 said:
Thanks for that, how do you recover after OTA crashes the system? I wish I'd known, I'm trying to see if I leave it off for about 72 hours if it will switch back on as advised in another forum. How do you get S-OFF on HTC U Play? I've only managed to unlock bootloader
Click to expand...
Click to collapse
try connecting the phone to pc and see if adb/fastboot reboot commands work Also try holding power key for 10-15secs.
you will have to flash stock rom zip back to get OTAs
For now there isn't any s off available
htc u play
installing twrp on installing twrp then black scren and vibrates around.can you help me please thanx
dranzer006 said:
try connecting the phone to pc and see if adb/fastboot reboot commands work Also try holding power key for 10-15secs.
you will have to flash stock rom zip back to get OTAs
For now there isn't any s off available
Click to expand...
Click to collapse
I've tried all of that I'm afraid as soon as it gets a bit of power the cycle happens and the PC doesn't have time to recognize the device before it reboots, it doesn't respond to the power key or any combination of key pressing, just keeps on in the boot loop. From what I've learned I'm assuming the problem is that 52MB TWRP image, it doesn't work on this phone, the update will be trying to boot the phone into recovery but because the recovery doesn't work it creates a bootloop..so far it's been 48hrs, will try switch it back on on monday as suggested here https://forum.xda-developers.com/an...g-failures-t3596427/post74189767#post74189767 . In the meantime we need to spread the word and shame whoever uploaded that TWRP image, evil!!!
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
martinsimir said:
installing twrp on installing twrp then black scren and vibrates around.can you help me please thanx
Click to expand...
Click to collapse
You're another victim of this TWRP image, sorry mate. Check this out..https://forum.xda-developers.com/an...g-failures-t3596427/post74189767#post74189767
Dutty106 said:
I've tried all of that I'm afraid as soon as it gets a bit of power the cycle happens and the PC doesn't have time to recognize the device before it reboots, it doesn't respond to the power key or any combination of key pressing, just keeps on in the boot loop. From what I've learned I'm assuming the problem is that 52MB TWRP image, it doesn't work on this phone, the update will be trying to boot the phone into recovery but because the recovery doesn't work it creates a bootloop..so far it's been 48hrs, will try switch it back on on monday as suggested here https://forum.xda-developers.com/an...g-failures-t3596427/post74189767#post74189767 . In the meantime we need to spread the word and shame whoever uploaded that TWRP image, evil!!!
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
You're another victim of this TWRP image, sorry mate. Check this out..https://forum.xda-developers.com/an...g-failures-t3596427/post74189767#post74189767
Click to expand...
Click to collapse
52mb ???? the image i have posted is around 14mb only.
if your able to restart the device then press the volume down key while booting (you will feel the vibration )
Brick htc u play
I know what i did. I just wanted to know what happened to the phone.thank you for your help, even if it's going to happen, so there's nothing going on, on Monday comes a new htc at play.people are learning mistakes.
---------- Post added at 07:11 PM ---------- Previous post was at 06:27 PM ----------
dranzer006 said:
52mb ???? the image i have posted is around 14mb only.
if your able to restart the device then press the volume down key while booting (you will feel the vibration )
Click to expand...
Click to collapse
black screen and vibrating all the time .can not even connect to the PC
martinsimir said:
I know what i did. I just wanted to know what happened to the phone.thank you for your help, even if it's going to happen, so there's nothing going on, on Monday comes a new htc at play.people are learning mistakes.
---------- Post added at 07:11 PM ---------- Previous post was at 06:27 PM ----------
black screen and vibrating all the time .can not even connect to the PC
Click to expand...
Click to collapse
I won't recommend you this but you can try pulling off the back panel and removing the battery cable (its the black one)
https://www.youtube.com/watch?v=KcNNGpsn7JY
dranzer006 said:
52mb ???? the image i have posted is around 14mb only.
if your able to restart the device then press the volume down key while booting (you will feel the vibration )
Click to expand...
Click to collapse
i feel vibration but black screnn
---------- Post added at 09:50 PM ---------- Previous post was at 09:46 PM ----------
dranzer006 said:
I won't recommend you this but you can try pulling off the back panel and removing the battery cable (its the black one)
https://www.youtube.com/watch?v=KcNNGpsn7JY
Click to expand...
Click to collapse
thanx mate on Monday I will see a new htc at play.but am try this
I dismantled it, but it does not help the same problem again black screen and vibrating .I put it in the garbage can
dranzer006 said:
52mb ???? the image i have posted is around 14mb only.
if your able to restart the device then press the volume down key while booting (you will feel the vibration )
Click to expand...
Click to collapse
Hi, I'm refering to this one "twrp-3.0.3-1_UNOFFICIAL-U Play.img" Not yours.. I flashed twrp-3.0.3-1_UNOFFICIAL-U Play.img and I'm now stuck and panicking, I hope I can have me phone back again .. The device tries to reboot itself into recovery repeatedly after you try a system update, no combination of button pressing etc works, the PC doesn't even have time to pick up the phone..Like I've said in previous posts, I'm trying to see if I leave it off for some days and then recharge and try to switch it back on if it will work..So far that's the only solution I've seen from anyone.. I hope this clears up my problem and suggestions..
Dutty106 said:
Hi, I'm refering to this one "twrp-3.0.3-1_UNOFFICIAL-U Play.img" Not yours.. I flashed twrp-3.0.3-1_UNOFFICIAL-U Play.img and I'm now stuck and panicking, I hope I can have me phone back again .. The device tries to reboot itself into recovery repeatedly after you try a system update, no combination of button pressing etc works, the PC doesn't even have time to pick up the phone..Like I've said in previous posts, I'm trying to see if I leave it off for some days and then recharge and try to switch it back on if it will work..So far that's the only solution I've seen from anyone.. I hope this clears up my problem and suggestions..
Click to expand...
Click to collapse
i am not sure what problem your having but if you try to press the volume up or down key while booting up you will boot into download mode. or else try pressing volume up and down both while the phone starts
Is there a possibility that comes out a working version.?
Dutty106 said:
Hi, I'm refering to this one "twrp-3.0.3-1_UNOFFICIAL-U Play.img" Not yours.. I flashed twrp-3.0.3-1_UNOFFICIAL-U Play.img and I'm now stuck and panicking, I hope I can have me phone back again .. The device tries to reboot itself into recovery repeatedly after you try a system update, no combination of button pressing etc works, the PC doesn't even have time to pick up the phone..Like I've said in previous posts, I'm trying to see if I leave it off for some days and then recharge and try to switch it back on if it will work..So far that's the only solution I've seen from anyone.. I hope this clears up my problem and suggestions..
Click to expand...
Click to collapse
Hi, did you have any luck? I'm stuck in the same boot loop.. I even took off the case and removed the black battery cable over night but still same boot loop, did running down battery help?
Hi, don't dismantle it or any of that other stuff suggested above, let it bootloop til the battery is flat, leave it, do not charge it or do anything to it for 11+ days, then charge it and it will switch back on, no problem, you'll have your phone back.
Ok thanks, it's been about 5 days off so far from dying from the boot loop, I'll give it another 10 days before charging it and see how it goes..
Thanks again for your response..
online4yourmind said:
Ok thanks, it's been about 5 days off so far from dying from the boot loop, I'll give it another 10 days before charging it and see how it goes..
Thanks again for your response..
Click to expand...
Click to collapse
No problem :good: it will definitely work
Geez i wish haahwhahai would have a working erecovery. This is maddening.
I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.
johncro13 said:
I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.
Click to expand...
Click to collapse
Do you have a link to this method of restoring kind sir?
Thanks!
If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.
johncro13 said:
If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.
Click to expand...
Click to collapse
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.
lowspeed said:
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.
Click to expand...
Click to collapse
Is your bootloader unlocked?
smokinjoe2122 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Relocked
lowspeed said:
Relocked
Click to expand...
Click to collapse
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?
smokinjoe2122 said:
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?
Click to expand...
Click to collapse
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....
lowspeed said:
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....
Click to expand...
Click to collapse
Well most of the time, if it's a software issue, it's fixable. I don't know as much about this phone as I'd like, but I do know there's update packages out there you can use to your benefit if you can get the bootloader unlocked. I believe the Update.APP can even be unzipped or decompiled to get the main imgs from it, such as boot, recovery, and system.
im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp
darkmage1991 said:
im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp
Click to expand...
Click to collapse
Which files did you flash in DC Phoenix?
Thanks for posting this!
JDBarlow said:
Which files did you flash in DC Phoenix?
Thanks for posting this!
Click to expand...
Click to collapse
downloaded the latest update on firmware finder for my device(l24) and used winrar to pull the update.app from the zip. then you select that in dc phoenix to do the restore/flash
Hello.
Yesterday my pixel xl (non-carrier-locked model) suddenly rebooted and got into a bootloop. It never gets past the white google loading screen.
It's fully stock, running the latest Pie + update. Bootloader is locked and the allow oem unlock in developer mode is also disabled.
I though I could just get into bootloader and swap the active partition using fastboot --set-active=(a or b) whichever works. But I soon realized that this is not allowed when the bootloader is locked. I can't unlock the bootloader using fastboot flashing unlock because oem unlocking is disabled in the developer settings. I can't obviosly get to the developer options without getting my phone to boot.
As an alternative I thought I could simply factory reset / erase user data from the recovery. However, when I try to get into android recovery from the bootloader, the phone reboots!
Things at the moment are looking grave. I don't have much data to lose on the device. What are my options given this predicament?
Thanks.
blueren said:
Hello.
Yesterday my pixel xl (non-carrier-locked model) suddenly rebooted and got into a bootloop. It never gets past the white google loading screen.
It's fully stock, running the latest Pie + update. Bootloader is locked and the allow oem unlock in developer mode is also disabled.
I though I could just get into bootloader and swap the active partition using fastboot --set-active=(a or b) whichever works. But I soon realized that this is not allowed when the bootloader is locked. I can't unlock the bootloader using fastboot flashing unlock because oem unlocking is disabled in the developer settings. I can't obviosly get to the developer options without getting my phone to boot.
As an alternative I thought I could simply factory reset / erase user data from the recovery. However, when I try to get into android recovery from the bootloader, the phone reboots!
Things at the moment are looking grave. I don't have much data to lose on the device. What are my options given this predicament?
Thanks.
Click to expand...
Click to collapse
Have you tried rebooting with Volume down+ power held in? Or has the battery died? Also what exactly were you doing when this happened?
same issue happeend now to me. any updates?
hey whats weird... ive got the same issue, December security patch stock pie....
---------- Post added at 05:01 AM ---------- Previous post was at 05:01 AM ----------
ive tried other stock pie, stock oreo, custom kernels, I cant even boot into twrp... anything I try to boot up it just bootloops.
Apologies for such a long delay in my response.
Phalanx7621 said:
Have you tried rebooting with Volume down+ power held in? Or has the battery died? Also what exactly were you doing when this happened?
Click to expand...
Click to collapse
ferydaboss said:
same issue happeend now to me. any updates?
Click to expand...
Click to collapse
godkingofcanada said:
hey whats weird... ive got the same issue, December security patch stock pie....
---------- Post added at 05:01 AM ---------- Previous post was at 05:01 AM ----------
ive tried other stock pie, stock oreo, custom kernels, I cant even boot into twrp... anything I try to boot up it just bootloops.
Click to expand...
Click to collapse
The only thing that loads up fine is the bootloader menu via vol down + power. I can't even get into the recovery from there. When I do, the phone simply reboots and continues it's bootloop.
I've already tried reflashing the latest stock rom on both the slots. Still no juice. The same thing happens. Powers on, I see the white google logo screen with the small unlocked icon to the bottom. Then reboots into the same screen forever. I thought doing a clean flash would most certainly fix this issue. But seems like I was wrong.
Looks like hardware (eMMC, main board) fail, not soft brick...
Hi there,
Did anyone tried to heat their phone a bit with a hair dryer or something to see if the phone boot? Could be another bootloop fiasco similar to LG crap and Nexus 6P chip solder getting loose?!
People got their Nexus 6P temporary booting heating the device...
If nothing else works, you guyz could try it? ?
Good luck...
I gave up. I opened the phone and looted it for parts.
My pixel xl(1st gen) purchased from Google store in Jan 2017, and in bootloop a week ago.
I contact google support, they told me my device out of the 1-yr warranty, and redirect me to UbreakIfix for repair, cost on myself.
I contacted UbreakIfix, get a quote for 300+ to change motherboard.
As of today, the Pixel XL only worth $130 trade-in value, and the condition need to be perfect.
So clearly I won't spend $300 to save a device only worth $130.
About the issue, I had some level of experience with fastboot/adb command:
* tried re-image all latest Google Stock Image of Android 7/8/9 individually with boot-loader unlocked, no luck;
* tried adb sideload ota image of Android 7/8/9 individually, with boot-loader locked/unlocked, no luck;
* tried change active slot to a and b with combination of above two items, no luck;
* checked the recovery logs, the boot-loader did take whatever Android stock image I feed to to it, and I do almost every time can get in to both boot-loader or recovery-mode successfully, and has no limit to run any fastboot/adb commands, but these are all I can do, and still not to get the phone boot into Android OS.
* in a very few times, the static "Google" in the white screen did spinning into a big rainbow "G", but it was frozen right after, and eventually reboot again.
I don't know if it worth spend more time on it, and feel very frustrated about spending my time on this doomed device and dealing with the Giant company as a individual customer.
I am not a picky guy, I accept the device running slow, or buggy sometime, but doesn't accept it dead in 2 years as a premium phone.
What do you think, guys?
By the way, many thanks to XDA forum, I learnt a lot from many brilliant and kind people here.
It's not acceptable, but it's the norm. Look at buying a new tv - Some mfg warranties are like 90 days labor and 6 months to a year on parts...It's a shame you pay all that money for something that could be a paperweight in a year.
Acceptable for a phone, or any gadget worth $800 to die in 21 months? LMAO. If this acceptable to some group of people, please redirect them to the best psychic facility available on this planet.
Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk
lafester said:
Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I used my Pixel as a regular way, never root it, never even boot into bootloader before the bootloop issue, always use ota in os to get update. No water spilt, never get drop or hit. In another word, I never "abuse" the phone, and the phone has no accident.
Yeah, whatever, for the phone issue, I'm just having bad luck, like you said, many people have no issues. What I upset about is a $800 phone became a brick within 2 years with a normal usage, and Google not even give this case as an exception to cover it out of warranty.
You may say, or like Google said, then what the warranty stands for, right? I say, if only a few people got this issue, then as a Giant company, should cover since no fault on customer, and it would be a small cost to Google; if a lot of people got this issue, then still Google need to cover, since it becomes a general issue to this phone, which indicates this is a failed model at all.
Please don't think I'm a cheap guy, and trying to take advantage from Google, just trying to think the logical here. BTW, I'm not just complaining Google without putting in effort to solve the issue by myself, I did a little bit research and pickup learning, regard this issue, I'm not alone, many other users have the same issue as well, some of them get it "resolved" by reimage, but the other just has no luck like me.
You don't have to agree with me, I'm a kind of guy would love to discuss with people no matter they have same point view as mine or not.
What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?
Phalanx7621 said:
What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?
Click to expand...
Click to collapse
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
I'm having the exact same issue and Phalanx7621 tried helping me out but unfortunately it looks like there's no solution for it.. Just like your issue, everything successfully flashes, but I got a little past the Google logo a couple of times, but no more. My phone wasn't dropped, never wet, nothing at all. Yesterday morning I woke up and the screen was just black and it started boot looping.
Funnily enough, 2 weeks after I paid the phone off. 1 week after Verizon called to let me know they had open enrollment on their insurance plans and I turned it down since, yanno, I don't mistreat my phone.. "Coincidence" I guess..
My post btw https://forum.xda-developers.com/pixel-xl/help/possibly-bricked-t3861057#post78033420 if any of that helps you hopefully.
That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.
Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
Phalanx7621 said:
That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.
Click to expand...
Click to collapse
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.
premedicated said:
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.
Click to expand...
Click to collapse
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
Sure. Gimme a couple minutes and I'll report back
---------- Post added at 08:15 PM ---------- Previous post was at 07:40 PM ----------
Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
So it loaded up TWRP, then I remembered that I didn't set a pin after the latest reflash. So I went into software and setup a pin and moved the TWRP files over onto the phone as well as the kernal before it restarted. But now I can't get 'fastboot boot twrp.img' to actually load TWRP on the phone.. Command prompt says "downloading boot.img, booting, finished. And then on the phone it loads up the google logo and then just freezes and restarts.. I'll dink with it some more and see if i can make it work
Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.
Phalanx7621 said:
Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.
Click to expand...
Click to collapse
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?
premedicated said:
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?
Click to expand...
Click to collapse
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.
Phalanx7621 said:
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.
Click to expand...
Click to collapse
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!
premedicated said:
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!
Click to expand...
Click to collapse
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..
premedicated said:
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..
Click to expand...
Click to collapse
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?
Phalanx7621 said:
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?
Click to expand...
Click to collapse
Well here's the deal.. Right after I posted that it started bootlooping again. It went through about 6 bootloops before I said 'eff it' and then just plugged it into the charger and walked away. I came back to it a little bit ago and according to the Kernel manager, it has an uptime of an hour and 32 minutes. So I grabbed it and was dinking around for a minute with it. Downloaded hulu, no problems. Downloaded netflix, no problems and then I was writing out a text and all of a sudden it froze and rebooted. Bootlooped once, then on the second try it started up. It's been up for about half an hour now.
Are there some sort of .log files with Android that could possibly show exactly what it is that's causing it to restart? Maybe something in the Kernel manager could help?