Hello, about a month ago my phone randomly shut off (full battery) and when I tried to turn it back on I was in a bootloop. I was able to boot into recovery mode (TWRP) and it said I had no OS installed so I installed the rom (viper) again. Tried to boot and was still in a bootloop, went back into twrp and noticed it said I had -1 mb of storage available. I needed a phone ASAP so I went out and got a new one but I miss my HTC so I figured I would try and get it back on its feet.
This is were I am lost. Whenever I turn it on it bootloops still. I can access Bootloader mode but when I try and access download mode it says "Failed to boot to download mode." and whenever I try to access recovery it just puts me into a bootloop. I am S - ON bootloader is unlocked. Whenever I try to use RUU it just says my battery is below 30%
Whenever I use fastboot getvar I get :
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT565SV00478
Any help would be appreciated!
i was just about to request on the same topic, i've just come across an m9 with what sounds like the same issue, and id really love to restore it back into working condition, fastboot doesnt give me any info or able to send any commands but i have access to a xtc2clip so i was able to read some info on its current state
Sending getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54GYJ03824
Sending oem readsecureflag
... (bootloader) read secure flag: 3
Click to expand...
Click to collapse
Kiwasad said:
Hello, about a month ago my phone randomly shut off (full battery) and when I tried to turn it back on I was in a bootloop. I was able to boot into recovery mode (TWRP) and it said I had no OS installed so I installed the rom (viper) again. Tried to boot and was still in a bootloop, went back into twrp and noticed it said I had -1 mb of storage available. I needed a phone ASAP so I went out and got a new one but I miss my HTC so I figured I would try and get it back on its feet.
This is were I am lost. Whenever I turn it on it bootloops still. I can access Bootloader mode but when I try and access download mode it says "Failed to boot to download mode." and whenever I try to access recovery it just puts me into a bootloop. I am S - ON bootloader is unlocked. Whenever I try to use RUU it just says my battery is below 30%
Whenever I use fastboot getvar I get :
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT565SV00478
Any help would be appreciated!
Click to expand...
Click to collapse
If u get in TWRP, format your partitions in TWRP before installing a new ROM from your SD.
If not, take it in service.
I cant access TWRP. I'm avoiding sending it in for service since I have a phone to use now and just want to try myself to get this one running. I tried to flash a hosd.img to get download mode back but I get :
target reported max download size of 536870912 bytes
sending 'hosd' (22228 KB)...
OKAY [ 0.688s]
writing 'hosd'...
FAILED (remote: image verify failed. cannot flash this partition)
finished. total time: 0.917
for some odd reason I've turned on the phone today to find out i can now access download mode, but its going to be a fun filled day trying to find the correct ruu as im not able to request cid
sorry edit that, it allowed me to access the recovery today when it wouldn't yesterday. still no joy messing around with it today. the recovery wouldn't let me mount the sdcard to install an update and it wouldn't let me sideload a zip file via adb sideload. would anyone know what update i should use to sideload ??
Still having this problem, any help is appreciated
yeah same, after coming across two m9's with this issue and still no further with my research. but i wont give up and ill report back if i find anything.
Kiwasad said:
Still having this problem, any help is appreciated
Click to expand...
Click to collapse
did you ever find a resolution?
I'm stuck as well
getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT59MSV01213
https://forum.xda-developers.com/sp...print-htc-one-m9-1-32-651-17-t3073355/page106
I have the exact same problem..... plus my laptop updated to Windows 10 so now when I try to install the RUU it just tells me to make sure my USB cable is connect... i have tried every driver.
I seriously need help and instructions on what to do!!
My phone does not enter in recovery mode nor can I restore it from the factory, since it does not enter into recovery mode it only stays in fastboot, the last commands that it used were: adb kill-server and then fastboot -w, that's when the problem started, any solution? Thank you.
:good:
omnismart said:
:good:
Click to expand...
Click to collapse
does not enter into recovery mode, when I select recovery, it returns to fasboot mode
luiguy said:
does not enter into recovery mode, when I select recovery, it returns to fasboot mode
Click to expand...
Click to collapse
can you flash any recovery image and see if it enters the recovery after that?
It's possible that the is no recovery image in the recovery partition to boot hence it is taking back to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
shibaa987 said:
can you flash any recovery image and see if it enters the recovery after that?
It's possible that the is no recovery image in the recovery partition to boot hence it is taking back to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
can be done by having the boot loader blocked?
luiguy said:
can be done by having the boot loader blocked?
Click to expand...
Click to collapse
you mean to say that you have a locked bootloader?
Sent from my [device_name] using XDA-Developers Legacy app
shibaa987 said:
you mean to say that you have a locked bootloader?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
that's right, and I'm in the stock ROM, the bootloader has never been unlocked
You keep posting the same question all over the place, but you're not helping anyone to help you. I've asked a couple times to see your flashfile, but it has never been posted. Maybe there is something wrong with it. We really need to try and flash the bootloader, that will tell us what we're up against. If you can flash the bootloader, then you can flash back to stock and get out of this mess, but if you get a permission denied and you're using an official signed, then that's another problem.
You said you've tried, but no you haven't. You've tried to use your flashfile and nothing happened, hence the reason I keep asking to see it. Your main goal right now, and I've said this before, is to determine whether you can flash or not. A locked bootloader will only accept official signed firmware from the same carrier with the same revision or higher. So pretty please, don't post the same question anymore but do post your flashfile so we can see if there is anything wrong with it. Better yet, if anyone has a working flashfile for the lastest -05 variant please post it so we can rule it out. In the meantime run this command in fastboot and post the output, but be sure that you don't post your imei info. Not trying to be a ****, but posting the same question all over the forum does nothing to help and will get you banned.
Code:
fastboot getvar all
Post the output of this command minus your imei info.
Code:
fastboot getvar all
Post the output of this command minus your imei info.[/QUOTE]
all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-b48569f-170628
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: no
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: NGRL470061
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 86027E05
(bootloader) securestate: engineering
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-29-2017
(bootloader) sku: XT1789-05
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4172
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_amx/nash:7.1.1/NPX26
(bootloader) ro.build.fingerprint[1]: .122-49/53:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.53.nash_amx.am
(bootloader) ro.build.version.full[1]: x.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.7.r1-09300-8x98.0
(bootloader) version-baseband: M8998_24.71.01.87R NRS
(bootloader) kernel.version[0]: Linux version 4.4.21-perf-gb6ca254 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 2015012
(bootloader) kernel.version[2]: 3 (prerelease) (GCC) ) #1 SMP PREEMPT We
(bootloader) kernel.version[3]: d Jun 28 08:50:20 CDT 2017
(bootloader) abl.git: MBM-3.0-nash_retail-b48569f-170628
(bootloader) xbl.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) pmic.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) rpm.git: MBM-3.0-nash_retail-d3e45a4-170628
(bootloader) tz.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) hyp.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) devcfg.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib64.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) keymaster.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) storsec.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) prov.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.146s
41rw4lk said:
You keep posting the same question all over the place, but you're not helping anyone to help you. I've asked a couple times to see your flashfile, but it has never been posted. Maybe there is something wrong with it. We really need to try and flash the bootloader, that will tell us what we're up against. If you can flash the bootloader, then you can flash back to stock and get out of this mess, but if you get a permission denied and you're using an official signed, then that's another problem.
You said you've tried, but no you haven't. You've tried to use your flashfile and nothing happened, hence the reason I keep asking to see it. Your main goal right now, and I've said this before, is to determine whether you can flash or not. A locked bootloader will only accept official signed firmware from the same carrier with the same revision or higher. So pretty please, don't post the same question anymore but do post your flashfile so we can see if there is anything wrong with it. Better yet, if anyone has a working flashfile for the lastest -05 variant please post it so we can rule it out. In the meantime run this command in fastboot and post the output, but be sure that you don't post your imei info. Not trying to be a ****, but posting the same question all over the forum does nothing to help and will get you banned.
Code:
fastboot getvar all
Post the output of this command minus your imei info.
Click to expand...
Click to collapse
there are the data that you asked me
What were you trying to do when all your trouble initially began? I see that you still have nougat on that slot and the bootloader secure state is engineering, that's not right. Can you still boot into your system? If so make sure adb is enabled. I assume oem unlock is greyed out and unavailable right? What firmware have you tried to flash? Also, if you're able to boot into your system you should disable fingerprint/lockscreen security until you have everything resolved.
41rw4lk said:
What were you trying to do when all your trouble initially began? I see that you still have nougat on that slot and the bootloader secure state is engineering, that's not right. Can you still boot into your system? If so make sure adb is enabled. I assume oem unlock is greyed out and unavailable right? What firmware have you tried to flash? Also, if you're able to boot into your system you should disable fingerprint/lockscreen security until you have everything resolved.
Click to expand...
Click to collapse
I just tried to update it to Android 8, if I can enter the system and I have USB debugging enabled, EOM is in gray, the ROM I wanted to install was: https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ . Android 8
luiguy said:
I just tried to update it to Android 8, if I can enter the system and I have USB debugging enabled, EOM is in gray, the ROM I wanted to install was: https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ . Android 8
Click to expand...
Click to collapse
In fastboot mode switch slots and run the getvar command again. Post the results and see if the other slot boots. If not switch back. You're currently on _a
Code:
fastboot devices
fastboot --set-active=b
fastboot getvar all
fasboot reboot
Post the results of the getvar command. If the phone boots to system on slot _b check out your settings, see if oem unlock is available and make sure adb debugging is on. If it doesn't boot, it should automatically fall back to slot _a but if it doesn't just run the commands above again only set active to a. You don't need to run the getvar command again once you're back to _a. *Note when you run the getvar command the 'current-slot' entry tells you what slot you're on.
41rw4lk said:
In fastboot mode switch slots and run the getvar command again. Post the results and see if the other slot boots. If not switch back. You're currently on _a
Code:
fastboot devices
fastboot --set-active=b
fastboot getvar all
fasboot reboot
Post the results of the getvar command. If the phone boots to system on slot _b check out your settings, see if oem unlock is available and make sure adb debugging is on. If it doesn't boot, it should automatically fall back to slot _a but if it doesn't just run the commands above again only set active to a. You don't need to run the getvar command again once you're back to _a. *Note when you run the getvar command the 'current-slot' entry tells you what slot you're on.
Click to expand...
Click to collapse
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-b48569f-17062
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: no
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: NGRL470061
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 86027E05
(bootloader) securestate: engineering
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-29-2017
(bootloader) sku: XT1789-05
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4301
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_amx/nash:7.1.1
(bootloader) ro.build.fingerprint[1]: .122-49/53:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.53.nash_
(bootloader) ro.build.version.full[1]: x.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.7.r1-09300-8x98.0
(bootloader) version-baseband: M8998_24.71.01.87R NRS
(bootloader) kernel.version[0]: Linux version 4.4.21-perf-gb6ca254
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 2
(bootloader) kernel.version[2]: 3 (prerelease) (GCC) ) #1 SMP PREE
(bootloader) kernel.version[3]: d Jun 28 08:50:20 CDT 2017
(bootloader) abl.git: MBM-3.0-nash_retail-b48569f-170628
(bootloader) xbl.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) pmic.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) rpm.git: MBM-3.0-nash_retail-d3e45a4-170628
(bootloader) tz.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) hyp.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) devcfg.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib64.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) keymaster.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) storsec.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) prov.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.193s
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.193s
You're still on slot a, you need to be on slot b
After you run the command set-active, reboot the bootloader then do a getvar. Also, see if it will boot.
Code:
fastboot --set-active=b
fastboot reboot bootloader
fastboot getvar all
fastboot reboot
41rw4lk said:
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.193s
You're still on slot a, you need to be on slot b
After you run the command set-active, reboot the bootloader then do a getvar. Also, see if it will boot.
Code:
fastboot --set-active=b
fastboot reboot bootloader
fastboot getvar all
fastboot reboot
Click to expand...
Click to collapse
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
luiguy said:
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
Click to expand...
Click to collapse
Either your fastboot file is out of date, or that engineering state is limiting your accessibility. Close any command prompt windows. Download this utilities zip, it has known good adb and fastboot files in it. Extract it to a folder somewhere, open the folder, hold shift and right click a blank area inside the folder, then choose open a command window here. Verify that your device is connected in fastboot 'fastboot devices', then try setting the active slot again and proceed from there.
*Note - Make sure you're using a 2.0 usb port off the motherboard, not a hub from the front of the pc and such. Most people don't have problems with this, but it has caused problems for some. Not all usb ports are so universal, ports on the mobo tend to have more consistent power supply and transfer rates; less interference as well.
41rw4lk said:
Either your fastboot file is out of date, or that engineering state is limiting your accessibility. Close any command prompt windows. Download this utilities zip, it has known good adb and fastboot files in it. Extract it to a folder somewhere, open the folder, hold shift and right click a blank area inside the folder, then choose open a command window here. Verify that your device is connected in fastboot 'fastboot devices', then try setting the active slot again and proceed from there.
*Note - Make sure you're using a 2.0 usb port off the motherboard, not a hub from the front of the pc and such. Most people don't have problems with this, but it has caused problems for some. Not all usb ports are so universal, ports on the mobo tend to have more consistent power supply and transfer rates; less interference as well.
Click to expand...
Click to collapse
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
luiguy said:
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
Click to expand...
Click to collapse
It has to be your phone that limiting your commands. I ran the same commands right out of the utilities zip and had no troubles. I think since you can't really do anything else, and you can't flash back to stock normally you might need to blank flash to get the gist of things back in order. First though, I would open your flashall file and paste the lines one by one in the command prompt and see if you could manually flash your phone. As it stands now, whenever you try to run the .bat file it just does nothing. Skip the fb_mode set and the getvar and start with the actual flashing. It will either flash or you'll get a permission denied most likely.
If you can't manually flash the oreo firmware, then you'll most likely need to blank flash. Several people have had their phone go wonky after trying to upgrade from nougat. So much for seamless updates.
luiguy said:
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
Click to expand...
Click to collapse
Just noticed, you're entering the command wrong. The only space in this command is between the 't' and the '-' fastboot --set-active=b
You need to check out the _b slot, see what is on it and whether it will boot or not. If it does boot, check the settings and take note of everything. If it doesn't boot then we'll go from there. Just copy the fastboot command as I typed it.
My wifes Pixel XL bricked tonight. Out of the blue it started rebooting, while she was using it. It started up, but then froze shortly after entering into the OS.
I went into recovery mode and performed a factory reset, it started up normally but half way through the setup guide is froze again, and went into a bootloop. And that's where I'm at now.
I have performed two more factory resets, but it never even boots into the setup guide anymore. Just straight to bootloop. The vast majority of times I can't even get into recovery mode anymore, when I try to it just gets into the bootloop. If I leave it turned off for a while, sometimes I can get it into recovery mode though.
Fastboot works, but the bootloader is locked and usb debugging isn't activated (I assume) so I can't flash anything through there or unlock the bootloader.
Considering how it started, and that the bootloop returned like 5 minutes after the first factory reset, I assume there is hardware problems, right? But is there anything more I can do, if we suppose that it's just soft bricked somehow?
Same issue here, would love to see if we could put our heads together with some folks. I have been wrestling with a Google Pixel XL on and off since August that has been doing roughly the same thing. Pixel is the direct-from-Google version (NOT Verizon), bootloader is locked, OEM unlocking is not enabled.
- Began rebooting consistently
- Would boot into OS for a limited amount of time then freeze and reboot, or freeze on G logo w/ loading bar then reboot
- I had been systematically uninstalling apps and downloading data to "cross them off my checklist" (probably a dumb idea in hindsight, if storage is corrupted)
- sometimes being left alone would allow the device to boot, seemed to only work within certain range of battery charge, perhaps until it heated up a certain amount?
- Will consistently boot into bootloader w/ Vol Down button
- Used to be able to consistently boot into Recovery from bootloader, but now choosing Recovery Mode will load Google logo and begin bootlooping.
- On one instance that Recovery Mode successfully booted, attempted to update via ADB. ADB seemed to install the update to 94% in PowerShell, and showed "success = 0" or something similar, which I take to be a failure lol.
- Much functionally in fastboot other than showing devices, rebooting, and getvar seems to require the bootloader to be unlocked, which I cannot do without access to the OS.
Things I've tried:
- sideloading update via ADB (failed the one time I was able to get recovery to load)
- unlocking bootloader via fastboot (requires oem unlocking in OS, so not successful)
- changing a/b partition via fastboot (unlocked bootloader required)
Here's a dump of getvar, seems like maybe one of the partitions is shot:
(bootloader) version:0.5
(bootloader) hw-revisionVT
(bootloader) mid:G-2PW2100
(bootloader) version-main:0.12.999.1
(bootloader) imei:[redacted]
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slotg2fs:no
(bootloader) has-slotg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slotersist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slotmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) slot-retry-count:b:2
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4240000
(bootloader) variant:US
(bootloader) secure:yes
(bootloader) unlocked:no
(bootloader) version-baseband:8996-130361-1905270421
(bootloader) version-bootloader:8996-012001-1908071822
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1c8d800000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:[redacted]
(bootloader) kernel:lk
(bootloader) product:marlin