Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.
PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image
DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.
Read this thread if you haven't...
blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.
lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.
rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.
PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked
If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.
Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.
Related
Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.
Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.
I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app
There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.
The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!
Do u guys have the most up to date version of whatever particular recovery that you're on?
Yep. I've flashed the stock recovery multiple times to no avail. :/
nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?
wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/
nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?
wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!
I've seen already this thread suggested by XDA thread locator.
https://forum.xda-developers.com/htc-one-m8/help/verizon-htc-one-m8-stuck-htc-logo-t3163088
But I'd try to explain as simple as possible the whole situation which happened hours ago.
Don't know what happened but my mothers phone went off and restarted with htc one logo on it and nothing else later.
Power button itself doesnt work and is not responding.
Configuration PWR + VOL UP gives me restart but no recovery mode, giving me sound effect of restarting phone and ONE logo on it without any other reaction whatsoever.
PWR + VOL DWN zero reaction
PWR + VOL UP & DOWN pressed together restarting the phone and then gives me HTC ONE LOGO and nothing else.
when Phone is plugged in to the computer and I'm forcing the phone to restart it shows me new Device on the computer as a CD Driver every time.
So I think there is still hope to get this guy back to life.
It's running on custom rom but unknown version because it was purchased as a refurb from ebay 2 years ago and it was running just fine utill this very day.
I'm absolutely noob with flashing twrping etc so please ELI5 if possible, any type of help will be much appreciated.
Thanks in advance.
Hey, I had this same problem a couple of days ago. Here's what I did to get the phone into fastboot, from where you can install a recovery, factory reset etc.
1. Hold the power button + vol up button for about 10-20 seconds. This should shut down the phone.
2. Hold the power button + vol down button to restart the phone back into fastboot.
If you can get into fastboot, there are plenty of guides which can help you flash a twrp image. If you want me to give you some instructions on that just reply and let me know. Good luck!
Note that this phone doesn't have download mode (as some other Android devices do); nor is there a button combo to go directly to recovery. But you can almost certainly still get to bootloader, and from there boot recovery. In the current condition, you can get to bootloader by:
1) Hold Power+ vol up (as you have been) to restart the phone.
2) Once the screen goes dark (signaling it is about to reboot) let go of the buttons, and only hold vol down
3) Don't let go of vol down until the bootloader screen appears.
4) If the above sequence fails, its virtually always because the user just didn't get the timing right (either started pressing vol down too late, or let go too early). Just repeat steps 1-3 until you get to bootloader.
Once in bootloader, try to reflash the ROM, or restore a TWRP backup (if you have one). Spontaneously stuck on HTC logo screen is often a result of the OS/ROM becoming corrupt or otherwise damaged, and flashing/restoring the ROM will often fix it.
Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
It's my mom's phone so basically reliabilty and robustness over flashing lights and numerous unnecessary functions.
Version of android doesn't really matter.
Thanks again for help so far.
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
TWRP might be extra helpful or the recovery it's functions are just fine?
Shewie said:
Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
Click to expand...
Click to collapse
I'd need to know more about the phone in order to give any suggestions.
With the phone connected to computer, boot into fastboot mode, and (assuming you have fastboot setup on your computer) do the command: fastboot getvar all
Then post the results (delete IMEI and serial number before posting).
Also, what version TWRP (if that is the recovery installed)?
Shewie said:
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
Click to expand...
Click to collapse
You will be able to flash a ROM from the SD card, if using TWRP.
Shewie said:
TWRP might be extra helpful or the recovery it's functions are just fine?
Click to expand...
Click to collapse
Not sure what is being asked here (can't quite understand). Are you saying that another recovery besides TWRP is presently installed?
@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
I wouldn't mind link to the pack with "must have" to complete the process
Shewie said:
@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
Click to expand...
Click to collapse
You have what is called the "stock recovery" or official HTC recovery.
You can't flash anything but OTA updates, or other official (HTC) signed zips with this. You need a "custom" recovery like TWRP in order to flash things like custom ROMs. So I'm curious what you meant before when you posted:
Shewie said:
Thanks [MENTION=660462]Sadly reflashing/factory reset failed few times due corrupted files.
Click to expand...
Click to collapse
What exactly were you trying to "reflash", what were the exact steps, and the results (specific error messages, etc.).
I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.
Shewie said:
I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.
Click to expand...
Click to collapse
Okay, so you're confusing the terms. Factory reset doesn't flash/reflash anything (flash meaning to install some firmware or software to the device). The only thing that factory reset does is wipe user data.
At this point, I'd suggest the best/easiest course of action in the current conditions (stock recovery, locked bootloader) would be to run the RUU intended for your device. Your device is the AT&T version, so the RUU can be found at the bottom of the page (and instructions on how to install): http://www.htc.com/us/support/htc-one-m8-att/news/
RUU is a complete factory image. You download to a PC (PC required, won't work on Mac or Linux) connect the phone (booted into bootloader-fastboot mode) then just run the RUU, and it will do the rest.
I'm confidant this will get the phone up and running. Your mom may not like all the AT&T branding and apps, if it wasn't there before, and AT&T is not her carrier (one of the main reasons for these devices to have custom ROM - to remove carrier branding). But we can cross that bridge (if need be), after we get the phone working.
Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?
Shewie said:
Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?
Click to expand...
Click to collapse
It just gets stuck sometimes. Just kill the process, and start the RUU again. It will probably work fine on the next try. It's a bit scary, as it says not to stop the process or disconnect the phone while it's running. But if it gets stuck like this, there isn't anything else you can do.
Good News, it's working. But it's bloated to the bones. How I can get rid of the carrier unnecessary software?
I was to afraid to kill the process during update to avoid scenario of bricking my phone completely.
But It's working!
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again
And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all
Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.
So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?
Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked
If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.
Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?
Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/
After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...
Are you going to be able to RMA it? Is it still under warranty?
Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse
Good news! I got an RMA!!
Thanks for your help everyone!
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
RuedasLocas said:
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
Click to expand...
Click to collapse
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
RandomUSA said:
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
Click to expand...
Click to collapse
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
RuedasLocas said:
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
Click to expand...
Click to collapse
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
RandomUSA said:
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
Click to expand...
Click to collapse
Try to don't mess with the audio chip!
Turn ON the phone with no cable connected.
Mine have that long boot only the 1st time, after that behaves normally.
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
Of course that until your phone boot completly you can't do any changes...
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
BTW... you install "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All" and "LGMobileDriver_WHQL_Ver_4.2.0" ? Maybe it helps to have those installed before flash.
Maybe it is the same in some devices (also depending on the phone Firmware version) to have those or others but, mine only work with those two installed.
Try this:
Re-flash with LGUP using the v20p again.
After the process is done and the long boot starts (wait 5 minutes or so), take out the battery, let the phone cool down for 10 minutes.
Insert the battery back on the phone and turn it ON.
Leave it until boot finish, go for a walk, watch some TV, forget about the phone.
Of course that if after 30 minutes stills without boot up, you can consider that you have a problem. And me out of ideas... sorry.
Wish you all the best luck on that, regarrds.
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
first of all: what model? we have 11 models for the g4 and not all behave the same way.
second: use SALT. SALT shows your previously installed firmware
third: try flashing custom ROMs instead of STOCK
fourth: I guess you know about http://bit.do/ilapofixg4 ?
.
steadfasterX said:
...
third: try flashing custom ROMs instead of STOCK
...
.
Click to expand...
Click to collapse
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
RuedasLocas said:
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
Click to expand...
Click to collapse
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
steadfasterX said:
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
Click to expand...
Click to collapse
Thanks for responding! I have a t-mobile h811 variant, LGUP/SALT currently shows my firmware as 20p, I decided to try updating to 20x using lg bridge, but the firmware is still listed as 20p despite the process being completed 'successfully'.
I know that flashing the KDZ worked because it overwrote my recovery and I no longer have access to TWRP. Before flashing the KDZ I tried several ROMS (stock 20p, aokp, lineage OS).
Now the phone is bordering on being a paperweight because I have no means of installing TWRP. I have an unlocked bootloader but there is no way for me to enter the bootloader. Is it possible to repackage a KDZ with a custom boot image or custom recovery?
Before flashing the KDZ and losing access to TWRP, I tried modifying the system boot.img to limit the number of cores that could be used to 4, and even 2 cores without any luck.
Right now, I don't think the phone has any bootloop issue or heat related problem because powering on the phone has become perfectly functional, the phone does not reboot itself (just stays at "Life's Good" with the blue blinking LED), recovery worked fine and handled a lot of load for hours reaching 40C+ on the CPU and with no issue.