Hi there, so I have a lovely AT&T HTC one x that's having all sorts of problems. It will boot loop several times to the HTC icon, and if IM lucky and patient, I can get to the initial startup screen. After I get to the home screen, every process stops and I have to go through it all over again.
Steps I've tried:
1) Boot to bootloader, factory reset, clear days, recovery
All of these options take me to the same sync screen, then straight back into the bootloop. Locked bootloader btw.
2) Power down completely (after many tries) and let it sit for a day before repeating step 1.
This has netted the same results
3) Flash the 5.18 ruu straight from the HTC site
This have me the most promising results. It flashed, I had the phone running, installed a couple apps, made a few texts, all was good. After about half of a day, the processes started failing, the phone rebooted, and I was back at square one. I've tried this method twice now.
Phone specs (not the best with all this, but I'll play from memory):
HTC one x AT&T
Android 4.2.2
HTC version 5.18
Locked bootloader
No root
Phone is basically 100% stock
thebobgoblin said:
Hi there, so I have a lovely AT&T HTC one x that's having all sorts of problems. It will boot loop several times to the HTC icon, and if IM lucky and patient, I can get to the initial startup screen. After I get to the home screen, every process stops and I have to go through it all over again.
Steps I've tried:
1) Boot to bootloader, factory reset, clear days, recovery
All of these options take me to the same sync screen, then straight back into the bootloop. Locked bootloader btw.
2) Power down completely (after many tries) and let it sit for a day before repeating step 1.
This has netted the same results
3) Flash the 5.18 ruu straight from the HTC site
This have me the most promising results. It flashed, I had the phone running, installed a couple apps, made a few texts, all was good. After about half of a day, the processes started failing, the phone rebooted, and I was back at square one. I've tried this method twice now.
Phone specs (not the best with all this, but I'll play from memory):
HTC one x AT&T
Android 4.2.2
HTC version 5.18
Locked bootloader
No root
Phone is basically 100% stock
Click to expand...
Click to collapse
If it's still occurring after running the RUU you're most likely dealing with hardware failure, probably the emmc.
Transmitted via Bacon
Related
Hi all,
I hope this is the correct forum.
I noticed that my Desire had downloaded an update (v1.11.11) and I quickly proceeded to updating to this version. When the phone rebooted into the CWR, I installed from sd card just like I had done for the past 3 versions of MIUI (didn't do any wipe before update), then hit reboot phone.
The HTC splash screen came up (green writing against white background), and the phone is stuck there. I have tried removing the battery a few times but to no avail. I tried holding down the vol. down button while powering up to access the bootloader, but that doesn't work either (i.e. I can't get to the boot loader). The result is the same, the phone locks up on the HTC splash screen.
I really don't understand what could have caused this since the phone was working just fine before I did the update. Note the phone is an HTC Desire (GSM) which was unlocked with unrevoked some months ago. I can't remember the exact version of CWR I have, but it is definitely 5.x.x series.
Thanks in advance.
Regards,
Hilkiah
My Nexus 5 seems to get stuck at the update screen (the standing green android with the spinning polyhedron) after flashing to stock(+unroot) with softbrick/bootloop checked. The flash completed without error. I've left it at this screen for over an hour and not only does it not progress it doesn't even get to the progress bar at the bottom.
This afternoon my (unrooted, bootlocked, stock) N5 turned itself off 3 times while on the charger. Powered back on and then would find it turned off 20 or so minutes later when I checked it again. After the third time it booted to the "Google" screen and would go no further. I tried a hard reset but it gave an error. So I plugged it into my laptop and fired up Wug's NRT, unlocked the bootloader (at which point it got stuck at the same update screen described above for around an hour). I held power till it went off, booted back into bootloader (which showed as unlocked) and performed the flash to stock(+unroot) with softbrick/bootloop checked and ended up at the update animation again. Any thoughts other than RMA?
****Edit: Finally got the phone to boot after fastboot booting twrp. Was able to to wipe the phone (after multiple attemps blocked by can not mount storage/cache/etc/etc errors). Flashed 4.4 and the phone now boots to android BUT radio is non-functional (no signal despite being in my normal coverage area), any attempt to add an APN causes a hard reboot (had to go through all the setup screens again). Additionally, the phone won't turn off, even hard power downs (holding the button for 30 secs) lead to an immediate reboot. Still RMAing but I was able to relock the bootloader.
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Chromium_ said:
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Click to expand...
Click to collapse
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
gallahad2000 said:
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
Click to expand...
Click to collapse
Yep, I would agree.
Hi there,
For the past few days my Nexus 5 has been stuck on the Google screen when I try boot it up, it never reaches the boot animation.
How it all started:
I was installing a random game from the Play Store when it suddenly rebooted and froze on the Google screen. I tried multiple methods, and eventually flashed a new stock Lollipop build using the flash-all.bat method. I worked, for an hour or so, then it would keep rebooting and freezing on that start screen.
What I've done so far:
So far, I've tried almost every method to try and fix the issue. I've used the Nexus Wugfresh Toolkit, then I manually flashed the stock build with that flash-all.bat method, as well as manually flashing each file, also having no luck. I've tried that Nexus All-in-one-bootloop-fix, that didn't help, as well as flashing the stock KitKat build with no luck either. Also take note that it never gave me any errors, and I even tried installing the stock build on another PC to see if that would help (it didn't).
So yeah, I can get it into the bootloader, flash ROMs/zip files, install CWM, but no matter what J do I still can't get past this Google boot screen. Any ideas/help would be greatly appreciated, as I don't think this is hardware issue, but I'm all out of ideas and thinking of going to buy a new phone tomorrow.
It's your power button - seems to be a relatively common thing. It happened to mine and the Play store got me a new one in less than 24 hours. (united states)
this is my first htc and so far i am missing my samsung and motos
the phone is now completely non responsive and is stalled at the HTC boot screen with the text "this build is for development purposes only " i have the verizon htc one m8 ive tried removing the sd and sim holding power holding volume and power nothing makes a difference.
rooted with s off twrp is my custom recovery
started by putting slimrom on for a change of pace i had horrible signal strength and decided to try another rom somewhere in the process of flashing venom one my sd lost its backups the phone had stayed on the same screen for a while but eventually booted to a stable seeming venom rom and had 3g but no 4g service i ended up rebooting the phone today around 11 am and its been in this loop / screen since. i let the battery die down and was able to get to recovery and searched for my back ups but they were gone i ended up rebooting and now am stuck on the same screen as before. even after trying to enter recovery twrp it goes back to htc and not twrp
i tried every combination of buttons the few times and have drained the battery twice and now it just boots to this screen and is non responsive. hope that i can manage to find a way to push something to it or enter recovery and go back to stock using ruu's
anyone with input or advice would be a blessing at this point id be happy to make a donation for any useful help / anything to get me out of this screen even so i can push another rom or ruu to get me to stock
im afraid ive ruined a perfectly awesome phone
update got back to twrp and tried to re flash the venom one rom after full wipe but used their option for "stock" install said 100% and sucessful but upon the reboot is now seems to be stuck in the same screen.
got into the recover after battery died re flashed venom
after about 15 minutes on the htc screen it went to set up ....still very buggy more so than last time the phone was actually working but it is at least from what i can tell working ... going to try to get back to square one somehow
screen wont turn on and acts very buggy only time it stays on is holding power and gives reboot options... i done f ' ed this phone up.
How long are you waiting after I restarts when the install is finished? It will take a long time on that first boot. I have seen them take more than 5 minutes and if you interrupt it it can cause problems.
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.