Develop Bugs

LG Phone returned from repair without OS

Hello,
I received my phone back from LG to fix the motherboard issue and it did not have an OS. Actually it did have an OS called Mini OS. The boot loader is locked and it won't verify proper google firmware when I adb sideload because it's using "test keys".
I was able to get root and adb into the device. Two questions:
1. Considering that I have root to the device, how can (is it possible) I put firmware to get back to a working state?
2. Because I have root on my device which is loaded with their keys and pre-OS flashed firmware, is there any value for the community here'?
Please forgive me if this is forbidden discussion and remove this post. I haven't been on XDA for more than a couple of years and don't know how things have changed.
Thank you.

FYI I fixed this issue. If you have this problem you can fix it by pushing twrp or other recovery to the device and dd-ing it to the boot loader block.
Let me know if you want help on this.
Also let me know if you want the system image I pulled from the stock weird LG manufacturer device.

Would be interesting to see, doubt it would be all that useful but interesting nonetheless
https://www.reddit.com/r/LGG3/comments/4g8d0p/g3_flash_tool_stuck_on_mini_os_screen_please_help/ This seems to be it running on a G3
https://www.youtube.com/watch?v=k8VWVzJJ0-U and on a G Flex2

This happened to me when i flash tot and unplug it before.
Sent from my Pixel using Tapatalk

Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.

AFK269 said:
Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification

konceptz said:
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification
Click to expand...
Click to collapse
I think that you will need to make a call to the service center to tell your situation.

I followed this and it booted just fine.

I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .

picodot said:
I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .
Click to expand...
Click to collapse
Hi @picodot , which bullhead image version did you use?

Trying To Recover Data - recovery and system partitions wont boot

Hey all,​
Question: Can anyone offer any help recovering my data partition?
Problem: system and recovery partitions wont boot.
Why: I failed to fix a boot loop problem I was having. I tried to restore my system and recovery partition that I had backed up through TWRP. The restore failed and now I cannot boot into recovery mode (let alone system).
What I've Tried:
1. booting into a TWRP (booting TWRP image via fastboot off my desktop PC). FAILED
downloading boot.img completes ok.
I get an error when it tries to boot the image: "FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)"
my guess is my recovery partition system is broken.
Thoughts:
Can I flash my bootloader and recovery partitions from a stock ROM without interfering with my data?
can i do a partial flash (not a flashall.bat)? How?
I am not super familair with doing a partial flash. I have only ever ran flashall.bat on Google's stock ROMs.
Question: Does anyone have any ideas?
If you can help me out, I would love to buy you a 6 pack of beer!

I am recreating this thread in its proper place.
@XDHx86
XDHx86 said:
Can you boot to bootloader? Does fastboot detect your device?
Yes, fastboot detects the device. It lists my Pixel 3 XL a fastboot device and the Pixel 3 XL properly executes commands like fastboot reboot bootloader.
Other things I just tried:
I also tested the connection and I was also able to fastboot a TWRP.img (sailfish version--Pixel 1) for my Pixel 1 just now. So everything looks good on my desktop end. However, when I boot a TWRP.img (crosshatch version--Pixel 3) on the Pixel 3, the boot fails and gives the error i posted above.
I also tried three different TWRP.img revisions (including the oldest and newest revisions for the Pixel 3XL). None of the twrp.img images will load.

Here is the fastboot command and error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also have the latest platform-tools installed.
I was able to flash the bootloader for latest Pixel 3 XL build for Android 9 (the version I had installed). However, I still cant boot into the TWRP image.

pritchfest said:
Here is the fastboot command and error.
View attachment 5254701
I also have the latest platform-tools installed.
I was able to flash the bootloader for latest Pixel 3 XL build for Android 9 (the version I had installed). However, I still cant boot into the TWRP image.
Click to expand...
Click to collapse
I used this script when I ran into a similar issue before, you can use it to flash TWRP or sovle your bootloop.

@XDHx86
Thanks for the tip.
I will definitely bookmark this and give it a try if I run into a bootloop issue. I am not sure what was wrong but I ended up doing a falsh-all.bat. the worst part about modding your phone is that when it goes out, you really needed to get fixed asap
This might or might not have worked, i'm not sure. I thought it was also weird that the yellow triangle with the exclamation mark on the fastboot screen was red. I've never seen it change colors. Not exactly sure what that means.

pritchfest said:
@XDHx86
Thanks for the tip.
I will definitely bookmark this and give it a try if I run into a bootloop issue. I am not sure what was wrong but I ended up doing a falsh-all.bat. the worst part about modding your phone is that when it goes out, you really needed to get fixed asap
This might or might not have worked, i'm not sure. I thought it was also weird that the yellow triangle with the exclamation mark on the fastboot screen was red. I've never seen it change colors. Not exactly sure what that means.
Click to expand...
Click to collapse
"This might or might not have worked". As in "I already got my device to the point of no return"?
If your device is bricked, there is no way to unbrick it that I'm aware of. As you can't find firehose files for google devices. So you can't boot to EDL mode.
Your options are to boot to bootloader and flash stock ROM, you can also use the script to flash TWRP and see if ti works.
Needless to say, flashing a ROM means loosing all your data.

XDHx86 said:
"This might or might not have worked". As in "I already got my device to the point of no return"?
If your device is bricked, there is no way to unbrick it that I'm aware of. As you can't find firehose files for google devices. So you can't boot to EDL mode.
Your options are to boot to bootloader and flash stock ROM, you can also use the script to flash TWRP and see if ti works.
Needless to say, flashing a ROM means loosing all your data.
Click to expand...
Click to collapse
oh, no. As in, your suggestion might have worked but I didn't get to try it because I really needed to have my phone working for work. I didn't get to try your suggestion because in my haste I opted to just flash-all.bat and forefit the opportunity to recover my data.
After trying to flash several partitions separately and failing, including just the bootloader--and later just the recovery partition--, I kept getting the same error I wrote about above.

So you still get this error?? Even though you used the script, you still get the error?
Are you sure you have latest adb tools and device driver?
What about setting active partition first?
Try fastboot set_active a
Then fastboot boot twrp.img

As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.

pritchfest said:
As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.
Click to expand...
Click to collapse
I can confirm I had the latest ADB setup.
I did not try your fastboot set_active a command before trying to fastboot into twerp.img. I can't say this wouldn't have worked.
The only other information I have is that on the fast boot screen, The triangle with an exclamation mark in it was colored red. Normally this triangle is a yellow color.
Hope that helps.

pritchfest said:
As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.
Click to expand...
Click to collapse
Oh you already solved it.
In this case write "[SOLVED]" in the beginning of the thread title and edit the first post to include the solution.

XDHx86 said:
Oh you already solved it.
In this case write "[SOLVED]" in the beginning of the thread title and edit the first post to include the solution.
Click to expand...
Click to collapse
No, I did not solve it.
I never came up with a solution to recover my data. The question was how can I recover my data. Instead, I had to wipe my whole phone and lose all my data by running flash-all.bat because my boss was getting mad I didn't have a phone.

pritchfest said:
No, I did not solve it.
I never came up with a solution to recover my data. The question was how can I recover my data. Instead, I had to wipe my whole phone and lose all my data by running flash-all.bat because my boss was getting mad I didn't have a phone.
Click to expand...
Click to collapse
Yeah I meant the bootloop, I mean looking at the bright side I saw worse. So just be happy with what you got, of course this is just my opinion.

Y
XDHx86 said:
Yeah I meant the bootloop, I mean looking at the bright side I saw worse. So just be happy with what you got, of course this is just my opinion.
Click to expand...
Click to collapse
Yeah, it could be worse :/

Question I think i may have bricked my device help pls

Hey guys i think i may have bricked my device, i keep getting this error whenever i try to use miflash to flash back to stock rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone know how to fix this? i keep bootlooping back into fastboot mode and whenever i try to restart system it says no os installed

Try redownloading the ROM and the latest version of Mi Flash. Reboot PC and phone.
Go to Mi Flash's Configuration and check "Verbose" and "Erase all", and remove the argument in "CheckPoint".
Also, "Clean All and Lock" is selected in the bottom right corner, keep that in mind, because it'll lock your bootloader once the Flash succeeded.
If you don't want that happening, check "Clean All".
Make sure there are no spaces in the whole ROM path, and perhaps also try a different USB port, or a different cable.
Also, plug in the USB cable after you rebooted Fastboot Mode. Fastboot Mode may stop accepting input after an initiated Flash, so to try and flash again you may need to reboot Fastboot Mode again.
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com

newbo1211 said:
Hey guys i think i may have bricked my device, i keep getting this error whenever i try to use miflash to flash back to stock rom
View attachment 5405925
Does anyone know how to fix this? i keep bootlooping back into fastboot mode and whenever i try to restart system it says no os installed
Click to expand...
Click to collapse
Lucky that it failed... Always remember to disable lock before flashing otherwise you will really brick the phone.
Try a different firmware like eea 12.5.3, that one is the only one I can confirm to be working in all circumstances

Rstment ^m^ said:
Lucky that it failed... Always remember to disable lock before flashing otherwise you will really brick the phone.
Try a different firmware like eea 12.5.3, that one is the only one I can confirm to be working in all circumstances
Click to expand...
Click to collapse
No it doesn't brick the phone. It only locks the bootloader when the flash succeeded.

dreamytom said:
No it doesn't brick the phone. It only locks the bootloader when the flash succeeded.
Click to expand...
Click to collapse
Man off my dik. Ur setting this guy up for a massive headache , yes It bricks it the phone , the hardest way possible when you have no idea what you're doing and are following advices like this. Using community tool to lock bootloader ( Your only way of interacting with this phone ) when you don't even know how the flash went is pure fkin stupidity.
Locks bootloader assuming the phone is fully functional but what if it's not? Then you can't try again , you're screwed. No flashing anymore.
CRC bypass for example like what he's having issues with will flash just fine , report 0 problems but phone doesn't boot. What if he follows one of the many guides out there , removes CRC and then goes flashing ?
Therefore your answer above is nothing but bs. Bad flash is soft brick , locking bootloader after bad flash is a much harder brick

Rstment ^m^ said:
Man off my dik. Ur setting this guy up for a massive headache , yes It bricks it the phone , the hardest way possible when you have no idea what you're doing and are following advices like this. Using community tool to lock bootloader ( Your only way of interacting with this phone ) when you don't even know how the flash went is pure fkin stupidity.
Locks bootloader assuming the phone is fully functional but what if it's not? Then you can't try again , you're screwed. No flashing anymore.
CRC bypass for example like what he's having issues with will flash just fine , report 0 problems but phone doesn't boot. What if he follows one of the many guides out there , removes CRC and then goes flashing ?
Therefore your answer above is nothing but bs. Bad flash is soft brick , locking bootloader after bad flash is a much harder brick
Click to expand...
Click to collapse
No, I agree that he shouldn't accidentally lock his bootloader.
However, choosing to lock the bootloader in Mi Flash won't brick the device.
The command for locking the bootloader comes only at the end.
If any errors occur before that, the script will terminate.
If any of the commands prior to "fastboot oem lock" don't execute successfully, it simply will not lock the BL.
The .bat-files are the logic behind the Flashing-process in Mi Flash.
It's not necessary to use Mi Flash. You could use the naked .bat-files, but I wouldn't recommend it. Mi Flash provides additional info.
About removing the CRC commands to skip CRC errors: I don't have a ROM on my drive to check what those exact commands are, but it's probably not recommended.
I think it's only safe to remove the Anti-Rollback Commands.
I do agree that there's a lot of misinfo out there, and that you need to be careful.

Pixel XL randomly bricked itself overnight?

So, I had left it plugged into the usbc port on my desktop overnight, probably not a good idea. In the morning I glanced at it, and it was doing a sort of charging boot loop, like showing the charging icon in the middle, then rebooting. Before it booted everytime, it showed a red light at the top, I assume because the battery was dead dead from boot looping.
So, I figured maybe I could just reset everything. No go. Couldn't get into the system at all. Kept showing the battery charging icon every time I tried to turn it on, then it would shut right off. Same thing over and over every time I tried to turn it on. Even Volume down + Power resulted in the battery charging icon.
So then I tried volume down + power while plugged into the computer with a different cable and different port, and I was able to get into the bootloader screen as shown. But this is as far as I cant go. I can't get into recovery, it just gets stuck at the google screen. Trying to boot into system gets stuck at the google screen."
I then tried various methods of flashing, live booting, whatever I could find on the matter, and resulted in the following errors, and getting stuck again on the google screen or sometimes staying on the bootloader screen. Is it a fair guess that maybe the flash chip died somehow? Or is that a bit out there? Only guessing that cuz usbc port on computer, less regulated than the standard chargers, idk just a theory. I've never had a problem like this before, but also never left a phone in that port all night.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Fortunately, your bootloader is unlocked, so your chances of fixing this are pretty good.
Please provide more information about the circumstances. Are you running a custom ROM?
From the logs you posted, it appears you're trying to flash incorrect firmware. A/B slot devices like the Pixel series do not have bespoke recovery partitions; the recovery kernel is contained in /boot, along with the system kernel. If you flash a recovery image to /boot, your device will only boot to recovery. Generally, the proper way to use custom recoveries on these devices is to live boot the recovery image; do NOT flash it.
As far as reflashing your phone, make sure you're using the correct firmware. The firmware for your device is here, notice the code name "marlin". Direct link for the latest firmware is here.
Make sure you are using the latest ADB Platform Tools.
If you need more information, please see my guide on the Pixel 3 here, as the concepts involved are exactly the same; the only difference is the firmware. Please note that the Android Flash Tool only works with Pixel 2 and newer.

V0latyle said:
Fortunately, your bootloader is unlocked, so your chances of fixing this are pretty good.
Please provide more information about the circumstances. Are you running a custom ROM?
From the logs you posted, it appears you're trying to flash incorrect firmware. A/B slot devices like the Pixel series do not have bespoke recovery partitions; the recovery kernel is contained in /boot, along with the system kernel. If you flash a recovery image to /boot, your device will only boot to recovery. Generally, the proper way to use custom recoveries on these devices is to live boot the recovery image; do NOT flash it.
As far as reflashing your phone, make sure you're using the correct firmware. The firmware for your device is here, notice the code name "marlin". Direct link for the latest firmware is here.
Make sure you are using the latest ADB Platform Tools.
If you need more information, please see my guide on the Pixel 3 here, as the concepts involved are exactly the same; the only difference is the firmware. Please note that the Android Flash Tool only works with Pixel 2 and newer.
Click to expand...
Click to collapse
Hey thanks for the reply, soo, I followed all steps of any guide I came across. When I try to just boot any twrp recovery, it will show the TWRP logo loading, and then go black, and try to boot up normal, getting stuck at the google screen again. Anything I've tried usually ends up back at that frozen google logo.

Yiggs said:
Hey thanks for the reply, soo, I followed all steps of any guide I came across. When I try to just boot any twrp recovery, it will show the TWRP logo loading, and then go black, and try to boot up normal, getting stuck at the google screen again. Anything I've tried usually ends up back at that frozen google logo.
Click to expand...
Click to collapse
It's generally easier to provide help if I know what's going on. Please answer the questions I asked.

Sorry, I thought I did when I said I follow all the correct steps. No custom rom. Was there anything else you needed to know?
No custom rom
Followed steps in your guide and others
Everything is correct for software

Anyone have anymore thoughts on this?

Sorry I didn't see your response to this. I don't have any suggestions unfortunately

Pixel XL boot looping for no apparent reason.

Hi all, so I had bought a Pixel XL to back up my photos to GPhotos forever for free, but it seems like it had other ideas. After I had backed up 100k+ photos to GPhotos, I let my device sit without turning it on for about 4~5 months. I had rooted the device to allow limiting the charge to 80% so that it doesn't overheat. However, now that I'm trying to turn on the device, it keeps boot looping. It turns on, gives the "can't check for corruption" message, shows the Google logo, and then reboots. Things I have already tried:
Flashing stock ROM
Letting the phone completely drain then trying to turn it on again
Hit the phones power button repeatedly on the side of a table/press it rapidly after applying some alcohol on it
locking/unlocking the bootloader.
using various fastboot commands such as erase, and continue boot
changing partitions and flashing stock ROM in each of them
flashing lower version of stock ROM
Unfortunately, none of the methods helped me boot the phone. I can enter the bootloader menu just fine, but whenever I try to start the phone, or enter recovery mode, it just shows the Google logo and then reboots, restarting the boot loop process. Any help would be appreciated! The device is unlocked.

icyyesboi said:
Hi all, so I had bought a Pixel XL to back up my photos to GPhotos forever for free, but it seems like it had other ideas. After I had backed up 100k+ photos to GPhotos, I let my device sit without turning it on for about 4~5 months. I had rooted the device to allow limiting the charge to 80% so that it doesn't overheat. However, now that I'm trying to turn on the device, it keeps boot looping. It turns on, gives the "can't check for corruption" message, shows the Google logo, and then reboots. Things I have already tried:
Flashing stock ROM
Letting the phone completely drain then trying to turn it on again
Hit the phones power button repeatedly on the side of a table/press it rapidly after applying some alcohol on it
locking/unlocking the bootloader.
using various fastboot commands such as erase, and continue boot
changing partitions and flashing stock ROM in each of them
flashing lower version of stock ROM
Unfortunately, none of the methods helped me boot the phone. I can enter the bootloader menu just fine, but whenever I try to start the phone, or enter recovery mode, it just shows the Google logo and then reboots, restarting the boot loop process. Any help would be appreciated! The device is unlocked.
Click to expand...
Click to collapse
You could have done this with rooting on a non Google pixel. But, what happenes when flash stock firmware? Error message?

Arealhooman said:
You could have done this with rooting on a non Google pixel. But, what happenes when flash stock firmware? Error message?
Click to expand...
Click to collapse
I can back up to Google Photos unlimited using another Android device? I read online that it had been patched. Was it false news? Also, I'm able to flash stock ROM without getting any error messages. I just tried to flash custom ROM again and here's the output of the CMD window:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From what I can tell, flashing has been successful with no errors. But the only way I can flash is if I enter the bootloader menu (Where you can enter recovery mode), which allows my PC to detect the phone and flash the stock ROM.

icyyesboi said:
I can back up to Google Photos unlimited using another Android device? I read online that it had been patched. Was it false news? Also, I'm able to flash stock ROM without getting any error messages. I just tried to flash custom ROM again and here's the output of the CMD window:
View attachment 5808203
From what I can tell, flashing has been successful with no errors. But the only way I can flash is if I enter the bootloader menu (Where you can enter recovery mode), which allows my PC to detect the phone and flash the stock ROM.
Click to expand...
Click to collapse
nope not patched

Arealhooman said:
nope not patched
Click to expand...
Click to collapse
Could you point me to how to enable it on other devices? I have a spare android phone sitting around, would be helpful for that. Also, do you have any idea what to do for the Pixel XL, or are you out of ideas as well?

icyyesboi said:
Could you point me to how to enable it on other devices? I have a spare android phone sitting around, would be helpful for that. Also, do you have any idea what to do for the Pixel XL, or are you out of ideas as well?
Click to expand...
Click to collapse
You could see is pixel flasher somehow does it better, but I doubt. The pixelify or pixel icy Google photos module for magisk and exposed framework would work

Arealhooman said:
You could see is pixel flasher somehow does it better, but I doubt. The pixelify or pixel icy Google photos module for magisk and exposed framework would work
Click to expand...
Click to collapse
Thanks for pointing out that software! Unfortunately, it didn't help at all, and now I'm just looking into how to flash Pixel firmware or whatever into my other Android phone (Samsung A32 5G). I hope I'm able to at least root that device and get unlimited photo backup. Thanks for your help!

icyyesboi said:
Hi all, so I had bought a Pixel XL to back up my photos to GPhotos forever for free, but it seems like it had other ideas. After I had backed up 100k+ photos to GPhotos, I let my device sit without turning it on for about 4~5 months. I had rooted the device to allow limiting the charge to 80% so that it doesn't overheat. However, now that I'm trying to turn on the device, it keeps boot looping. It turns on, gives the "can't check for corruption" message, shows the Google logo, and then reboots. Things I have already tried:
Flashing stock ROM
Letting the phone completely drain then trying to turn it on again
Hit the phones power button repeatedly on the side of a table/press it rapidly after applying some alcohol on it
locking/unlocking the bootloader.
using various fastboot commands such as erase, and continue boot
changing partitions and flashing stock ROM in each of them
flashing lower version of stock ROM
Unfortunately, none of the methods helped me boot the phone. I can enter the bootloader menu just fine, but whenever I try to start the phone, or enter recovery mode, it just shows the Google logo and then reboots, restarting the boot loop process. Any help would be appreciated! The device is unlocked.
Click to expand...
Click to collapse
What methods are you utilizing to flash the stock firmware and which ROM is it?