Possible fix for Pixel XL Bootloop Issue - Google Pixel XL Questions & Answers

I bought a Pixel XL yesterday from the local marketplace. It was being sold for cheap and mentioned that after an update the device doesn't start. I bought it for experimentation. When I brought it home it was completely discharged so I hooked it up to a wall charger and tried to turn it on. It turned on but was stuck in bootloop. I left it on charge for about 12 hours or so. After that I picked it up and saw that it was still in bootloop but now it was giving the "no command" screen as opposed to the Google splash screen that it was showing up in the morning. I pressed some buttons and went into recovery. I was completely unfamiliar with the issue at this point. I downloaded the official firmware matching the firmware version with the one being displayed at the top of the recovery screen. I put the phone into the "adb sideload" mode and started the sideload. After it completed the device booted up. I was really happy that I fixed the issue so easily.
However, I immediately got the prompt to update to Android 10 so without doing anything with the phone, I started the update process. I left it to update and after a few minutes I noticed the device was again stuck in the bootloop with the google splash screen. At this point, no matter what I tried, I could not boot into recovery mode but could easily boot into bootloader. After that I did the following things:
-> Tried installing the factory firmware from fastboot using the flash_all.bat file. It failed with an error saying could not update partitions table or something like that
-> I tried to boot into recovery using twrp recovery img but that failed as well, kept getting the Google splash screen
-> I flashed the boot.img from the factory firmware zip (that matched my firmware version) to both the partitions a and b using this command: fastboot flash boot_a path/to/file and fastboot flash boot_ab path/to/file. It did the flashing alright but the device just won't boot into recovery.
-> In short, I exhausted all the options but could not boot into recovery. When powered on with volume up button pressed, the device stayed on a black screen and when I let go the volume up button, the device would start bootlooping again
I hooked up the device to the charger and slept. When I woke up, the device was again stuck in bootloop. I went into bootloader and selected the option to power off. Since the device was on charge it showed the charging battery symbol and automatically landed onto the no command screen. I went into the recovery from there and again sideloaded the factory firmware hoping that the device will boot once done but upon restart it again got stuck into bootloop. I again exhausted all my options but could not get the device boot into the OS. I was however able to boot into twrp recovery and tried to do a complete wipe there but it gave error while wiping the dalvik cache and stopped there without completing the wipe. I pushed the twrp recovery.zip through adb into the device and tried installing, it got stuck while installation was in progress and started rebooting again. I could not get into the recovery again after that point onward. I flashed the factory boot.img to slots a and b but still couldn't get into it.
Now I have hooked up the device to the charger again and left it there. I am hoping after going through the bootloop for another 3 or 4 hours, it will boot into recovery once again. I will provide my results on this.
At this point, does anybody want to share their thoughts on this and suggest something that I should try? One option that I can think off is to disconnect the battery and reconnect it. It may break the loop but I don't want to disassemble the device at this point as I may break something and then won't be able to play with this anymore.

Related

Trying to fix an M8

So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
TMartin said:
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
Click to expand...
Click to collapse
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
xunholyx said:
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
Click to expand...
Click to collapse
I can get into TWRP but it won't mount the data partition. Are you saying I should try flashing another ROM the normal way through TWRP or try the sideload option? I tried to fastboot flash stock recovery. It says it worked but then continues to boot to TWRP.
I can get into bootloader. I'm pretty sure it's a 4.16.401.x ROM but I'll have to double check when I get home. I've tried to flash stock everything but it you know how it restarts through the process? When it restarts, it seems to want to restart to OS.
I'm about 99% sure the OS is there because it boots into Android but only gets me to the "Decrypt storage" screen.

Nexus 5 stuck in the worse bootloop [tnks 4 the help in advance]

Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED <remote: flash write failure>
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
Cheers
Mattia
Did you update to the latest sdk tools? I think fastboot has been updated. Also, make sure you are using a good cable in a good port. I had trouble flashing with a USB 3.0 cable in a USB 3.0 port. It worked in a USB 2.0 port just fine.
I suspect your device is in a dirty state- it wants to wipe data to unlock the bootloader, but it didn't complete, so it is unwiped, but still considered encrypted. Maybe try flashing the stock system using fastboot -w update some-update.zip. The update zip is inside the factory image- you'll need to untar it. This is a destructive flash and will erase your data! If it works, let the system boot up since it will take a while to encrypt so that it is in a sane state.
I think download mode is for factory programming. I've been there a few too many times already, and I think it is vol up and power. It'll tell you not to disconnect the cable and the percentage bar will be stuck at 1%. I'll let you guess on how to get out of it.
Make sure you update android sdk like ^ he said, I spent 3 hours trying to get back to stock and trying to figure why fastboot system image wasn't workking -_-

[Help] Softbricked phone

[HELP] I unlocked the bootloader, did a live boot into TWRP and followed the steps- it wouldn't let me decrpyt the data partition, so I hit cancel, clicked agree on the next screen and then I was in the TWRP recovery. I attempted to reboot the phone without making any changes, at which point it just spins away trying to reboot but doesn't (after several minutes). It doesn't appear I can get into the recovery mode or the bootloader either- the screen flashed on and off "no command" and the volume + pwr button do nothing. I can however still get into fastboot and windows recognizes it. Is there a way to flash the factory image from here? Will the steps in this video get me back to factory?
https://www.youtube.com/watch?v=bqvr5kHwxlw&t=98s
Yes, You can restore your stock system with this process 100%.
Then you can add your further process like root or TWRP or Custom ROMs

Recovery lost after cache wipe

I updated to Oreo by signing up to the beta program and installed the full upgrade (~1GB) earlier today. It worked flawlessly for several hours and then the phone froze; I was unable to boot it up after that. I booted into recovery, performed a cache wipe, but since that, it still won't boot and now I can't go to recovery either (just get a blank screen after the Google logo). My device is locked, so I can't do a fastboot flashing unlock
Do you have any ideas what to do next? I can still go to fastboot and issue fastboot commands and the phone charges if I connect a charger in a powered-off state, but that's it.

refurbed and still bootlooping

LG refurb updated the ROM to 20x, and (supposedly) replaced MB & RF.
Now I can't get into bootloader, with either ADB or power/vol down combo. Bootloops instead and takes 15 mins to become a working phone again.
I've factory reset 2x today.
Perhaps factory reset and don't restore from Google?
Perhaps 20x is corrupt?
I have no idea what to do next other than deal with the apparent idiots at LG Texas. This is the 2nd "refurb" in a month and 3rd since I've had the G4.
HTC M7 is saving my sanity as backup.
finally got out of bootloop. OEM unlock was the issue in Developer options.
But now having problem getting it to boot into twrp.
fastboot flash recovery twrp.img - went ok, as per past experience.
but - fastboot boot twrp.img - is a no go.
I get this back - cannot load 'twrp.img': No such file or directory.
Can't power down with power button held for 10secs.
Only fastboot reboot works.
What happens if you try to boot into recovery with the key combo (power and vol down until lg logo appears, then release power briefly whilst still holding vol down and then press power again whilst still holding vol down - should bring you to "factory reset page" but once factory reset is confirmed should go to TWRP)
nope, goes to factory reset. tried that twice.
Ok so even after you have flashed twrp, when you enter that factory reset page and click yes twice, it actually factory resets it (that screen is there for everyone but it normally goes to twrp afterwards). Did you boot into your phones OS inbetween flashing twrp and booting to it? LG software replaces twrp with stock recovery if you don't patch the os.
The way to permanently install twrp is:
1) reboot to bootloader and perform "fastboot flash recovery twrp.img"
2) fastboot reboot
3) AS SOON AS IT REBOOTS (<-- that is important) - use key combo and click yes twice - do NOT let it boot back into the main android system inbetween, or you will need to start again
k, I'll give that a go tonite after work. Don't recall the issue with the earlier OS, 20v (before "refurb"), but I'll do oit.
What model of phone is it?
In terms of flashing twrp, that has always been the process (I have a G4 on v20g firmware and it took me a while to work out why twrp kept being wiped)
it's a G40 w/20x. Never had this issue before 20x.
still actually having an issue on reboot. Takes about 7 mins now as it optimizes 1 unknown app.
used this method from fastboot:
fastboot boot twrp.img and pointed (d&d) to twrp on my drive.
then installed twrp from memory as described on twrp page/Fastboot Installation Method.
Ding Ding Ding!
thanks.

Categories

Resources