I encountered this problem yesterday. Every time the phone would sleep, when awaking it, the system with momentarily freeze then reboot. Here is the real mystery, it also would not power down. Instead of powering down, it would reboot. It would reboot into system if powering down from the desktop, if power down or recovery was selected from bootloader or if power down was selected from the recovery screen. The only way I could reach recovery would be to allow it to boot to the desktop, plug in the USB port to a computer and ADB reboot recovery. Bottom line, you couldn't turn the thing off!
I'm running Captain Throwback's 4.13.651.4 Custom ROM, TWRP 2.8.5.0, HBOOT 2.10.0000, Radio 1.13.11.1105, UNLOCKED, S-OFF, rooted with SuperSU. I loaded the Captain's ROM according to the instructions, electing to run the stock 4.13.615.3 RUU before flashing his custom ROM. I've been running fine on this config for about a month.
Here is what I did to fix it. First, I wiped Dalvic Cache, Cache, System, Data, and Internal Storage. Then, I tried to do a full restore from a TWRP backup I had done after I loaded the stock 4.13.651.3 RUU. The restore ran for about a 30 seconds and suddenly, rebooted into system before the restore finished. Obviously, it didn't complete the boot and was locked on the boot screen. Now, all I had could reach was bootloader. Bootloader still would reboot into system (unsuccessfully) if recovery or power down was selected. I'm thinking brick at this point. All things start from boot so, I decided to try replacing boot. I connected the USB cable to the computer and fastboot flashed the copy of boot.emmc.win (same as the existing running version) from the TWRP backup done after I loaded the stock 4.13.615.3 RUU. Rebooted into bootloader (flashed copy, I assume) but, no change except, now, the phone would reboot if I connected the USB cable to the computer in fastboot. However, it would not reboot if I connected a wall charger in fastboot. I'm definitely thinking brick now.
Tried one last thing before frisbeeing it. I took phone out of the mid-frame and pulled the battery cable to the motherboard. I left it off for a minute or so before reconnected it. When I reconnected the battery cable, the phone immediately booted into system (unsuccessfully) instead of staying powered off. Now, I'm sure it's Frisbee time. I pulled the battery cable to the motherboard and went to dinner. Got back from dinner and reconnected the battery cable and started putting it back together. But, the phone stayed powered off this time. I finished putting it together and it started working normally. Bootloader would power off the phone and would boot recovery. Recovery would also power off. I reflashed Captain Throwback's 4.13.615.4 custom ROM and everything seems back to normal.
Does anybody have any insight into this? I've never heard of a phone behaving like this. If it was a corrupted HBOOT, it seems reflashing it would have fixed it. Why did leaving the battery disconnected for a long period finally resolve it?
I'm running Captain Throwback's 4.13.651.4 Custom ROM, TWRP 2.8.5.0, HBOOT 2.10.0000, Radio 1.13.11.1105, UNLOCKED, S-OFF, rooted with SuperSU. I loaded the Captain's ROM according to the instructions, electing to run the stock 4.13.615.3 RUU before flashing his custom ROM. I've been running fine on this config for about a month.
Here is what I did to fix it. First, I wiped Dalvic Cache, Cache, System, Data, and Internal Storage. Then, I tried to do a full restore from a TWRP backup I had done after I loaded the stock 4.13.651.3 RUU. The restore ran for about a 30 seconds and suddenly, rebooted into system before the restore finished. Obviously, it didn't complete the boot and was locked on the boot screen. Now, all I had could reach was bootloader. Bootloader still would reboot into system (unsuccessfully) if recovery or power down was selected. I'm thinking brick at this point. All things start from boot so, I decided to try replacing boot. I connected the USB cable to the computer and fastboot flashed the copy of boot.emmc.win (same as the existing running version) from the TWRP backup done after I loaded the stock 4.13.615.3 RUU. Rebooted into bootloader (flashed copy, I assume) but, no change except, now, the phone would reboot if I connected the USB cable to the computer in fastboot. However, it would not reboot if I connected a wall charger in fastboot. I'm definitely thinking brick now.
Tried one last thing before frisbeeing it. I took phone out of the mid-frame and pulled the battery cable to the motherboard. I left it off for a minute or so before reconnected it. When I reconnected the battery cable, the phone immediately booted into system (unsuccessfully) instead of staying powered off. Now, I'm sure it's Frisbee time. I pulled the battery cable to the motherboard and went to dinner. Got back from dinner and reconnected the battery cable and started putting it back together. But, the phone stayed powered off this time. I finished putting it together and it started working normally. Bootloader would power off the phone and would boot recovery. Recovery would also power off. I reflashed Captain Throwback's 4.13.615.4 custom ROM and everything seems back to normal.
Does anybody have any insight into this? I've never heard of a phone behaving like this. If it was a corrupted HBOOT, it seems reflashing it would have fixed it. Why did leaving the battery disconnected for a long period finally resolve it?
from xda-developers http://ift.tt/1Ew8SkC
via IFTTT
Aucun commentaire:
Enregistrer un commentaire