I have had this error on stock and custom roms and the only ways I have found to fix it are by removing and inserting the sim card, factory resetting through the bootloader, or by removing the top of the case. Now hopefully there is a fix but I encountered this error pretty shortly after unboxing the device so could it be an error with the device itself and not software related?
Related
Hi, everyone
I got promblem with my HTC DHD, it appeared the notice to "force close" many app all time so I cant do anything on my phone. I tried to re-up rom by sd card, everything was in normal process during flashing rom until i reboot the system after finishing flashing, it was stuck on logo screen althought i take time to wait, it was still stuck. I dont know how to shut it down or restart so i took the battery out for a while and put it back then power on again. The strange thing is it didnt show the rom i've just flashed, it worked with everything same like before flashing rom (require pass to unlock device, home screen, apps... Speicially is the error "force close" still same) . I wiped data, cache and everything before flashing. I tried to restart many times but same problem, sometimes stuck on logo screen, sometimes boot to old rom.
Then I decided to up the ship rom by laptop, after running RUU...exe file, it aks me to update the rom version for device without other option. I click update and wait, It appear the error (#171) and ask me to check the cable connection but 100% nothing wrong with the cable or connection. I tried to redo this several times as well but still same. My friend said the emmc chip is damaged and need to replace.
Could anyone help me? I still can go to recovery, hboot/fastboot screen. If emmc chip damaged, i think we still can fix it by software because it not dead.
thanhbom83 said:
Hi, everyone
I got promblem with my HTC DHD, it appeared the notice to "force close" many app all time so I cant do anything on my phone. I tried to re-up rom by sd card, everything was in normal process during flashing rom until i reboot the system after finishing flashing, it was stuck on logo screen althought i take time to wait, it was still stuck. I dont know how to shut it down or restart so i took the battery out for a while and put it back then power on again. The strange thing is it didnt show the rom i've just flashed, it worked with everything same like before flashing rom (require pass to unlock device, home screen, apps... Speicially is the error "force close" still same) . I wiped data, cache and everything before flashing. I tried to restart many times but same problem, sometimes stuck on logo screen, sometimes boot to old rom.
Then I decided to up the ship rom by laptop, after running RUU...exe file, it aks me to update the rom version for device without other option. I click update and wait, It appear the error (#171) and ask me to check the cable connection but 100% nothing wrong with the cable or connection. I tried to redo this several times as well but still same. My friend said the emmc chip is damaged and need to replace.
Could anyone help me? I still can go to recovery, hboot/fastboot screen. If emmc chip damaged, i think we still can fix it by software because it not dead.
Click to expand...
Click to collapse
Same problem here with one desire hd. Force closing many apps and wipe/flashing new rom doesn't help at all. Guess it's the emmc chip, indeed.
I have a LG G3 with rooted stock rom running xposed.
So I pulled my phone out of my pocket today only to see the Verizon boot logo in effect. I was thinking "that's weird, guess my phone needed to reboot? Strange." But the only problem is it never stopped. It will only boot up to the lock screen and occasionally it will display an error message telling me the systemui has stopped. Then about 10 seconds later, it reboots itself. It continues this process until I pull the battery.
I've tried booting into safe mode, no luck. It doesn't even actually boot into safe mode (it doesn't say safe mode in the bottom left corner.)
I tried wiping the cache, no luck.
I don't want to just do a factory reset because that hasn't seemed to help anyone else with this issue as far as I've seen. I have not found any helpful information on how to fix this problem.
My question is, what do I do? I feel lost on this subject. Normally I've always been able to diagnose problems on my own, but not in this situation.
I have all my apps and data backed up to Titanium Backup on my SD card.
Any suggestions?
Xposed is more than likely the cause. Boot into TWRP and open a terminal, then type the commands as shown in the OP of this thread to bypass it...
How to Disable Xposed on Lollipop when stuck in Bootloop
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
I was trying to unlock a Note 4 with my Z3X box, but the process just stopped and said "software security damaged" now the phone keeps rebooting by itself right after the samsung logo appears. I tried HARD RESET, and installing stock firmware available for that model and replacing the battery but still the same keeps rebooting after the logo, it did not happen before try to unlock it
D851 phone running stock lollipop
I had an issue the other day where my WiFi and Bluetooth were refusing to connect and just said "connection not allowed" so I tried a few things and then resorted to a factory reset.
Luckily the factory reset fixed the WiFi issue but now another issue has come up, an almost endless boot loop.
Occasionally the phone will actually boot but it never stays on for long even when plugged in. I've tried factory resetting again but to no avail.
Prior to this issue my phone would have the occasional random reset but nothing too frequent, my battery is relatively new but I'm not ruining out the possibility of a faulty battery and am in the process of getting a replacement.
Does anyone have any ideas what this issue could be caused by and how to fix it? The fact that it occasionally boots makes me think it IS a battery issue but I'm a complete noob to this kind of thing.
My Pixel XL 128GB on Android 10 just randomly started bootlooping during normal use. Totally stock with Verizon sim card, but received directly from Google (actually it is a warranty replacement received about 2 years ago for a Nexus 6P that I bought directly from Google in Feburary of 2016 due to faulty battery).
Bootloader is still locked. USB debugging is disabled.
Google logo just keeps appearing and disappearing on screen. I can get into fastboot by holding power and volume down, but choosing recovery mode just goes back into bootloop.
Am I hopelessly bricked?
thomase00 said:
My Pixel XL 128GB on Android 10 just randomly started bootlooping during normal use. Totally stock with Verizon sim card, but received directly from Google (actually it is a warranty replacement received about 2 years ago for a Nexus 6P that I bought directly from Google in Feburary of 2016 due to faulty battery).
Bootloader is still locked. USB debugging is disabled.
Google logo just keeps appearing and disappearing on screen. I can get into fastboot by holding power and volume down, but choosing recovery mode just goes back into bootloop.
Am I hopelessly bricked?
Click to expand...
Click to collapse
After looping several times I was able to reboot once. I went into developer mode and enabled "USB debugging" soon after which it crashed again. Only then did I realize that I was SUPPOSED to enable "OEM Unlocking" rather than "USB debuging"!
I still haven't been able to boot it again since. Any suggestions? Would heating or cooling the device help? What are the chances that re-flashing the factory image will even help?
thomase00 said:
After looping several times I was able to reboot once. I went into developer mode and enabled "USB debugging" soon after which it crashed again. Only then did I realize that I was SUPPOSED to enable "OEM Unlocking" rather than "USB debuging"!
I still haven't been able to boot it again since. Any suggestions? Would heating or cooling the device help? What are the chances that re-flashing the factory image will even help?
Click to expand...
Click to collapse
Well, I was able to get in again and barely had enough to enable "OEM Unlocking". I proceeded to unlock the bootloader and re-flash the latest Android 10 factory image (the one ending in .20). I can't get through the new phone setup process before it crashes and eventually reboots. It might get as far as connecting to Wifi but always eventually crashes while "Checking for updates...".
I could try an older Android 9 image, but it seems like I have a straight-up hardware failure (SoC, DDR, flash memory, etc.).
At this point I'm resigned to the fact that it is most likely dead. Are there any custom recovery images that I can flash that can run hardware diagnostics so I that I can pinpoint the failed component?
The same thing happened today to my wife's xl pixel still with android 9, now I've updated it to 10 and for now it works but I think it seems like there's a battery problem. I think the battery is bad but it is strange that it happens this way
Looks like i have the same issue. If you remember one of the android betas (beta 4 i believe) had this issue where the phone got stuck in bootloop. I had this issue and im unable to fix it. My phone keeps bootlooping on the google logo...i tried reflashing the factory image for 9.0 or 10.0 but no luck. I even tried installing a custom rom and that too reboots on the google/custom rom logo. Is there any other way to fix this? Is this a hardware issue? please help