[Q] automatic and continuous reboot - HTC One X

First off: I have an AT&T HTC one X
I am an almost total noob when it comes to this stuff so please bear with me here.
I had my roommate put cyanogenmod onto my phone when I got it and all was well until I moved to Asia and got an unlock code from AT&T to be able to use it over here. The unlock code wouldn't work and I found some stuff online saying that it might be a problem with cyanogenmod. I followed a youtube instruction guide on how to get rid of the mod and everything was going fine until right at the end when I got a windows notification that the RUU had stopped working. I figured I would just do it again, but the actual program itself said it was successful. As I waited for it to reboot and load the roms, it started a loop. The loop is the white screen with the green htc letters for a few seconds and then it goes to a black screen with a phone logo in the middle. Around the phone logo is what looks like a recycling symbol except circular instead of triangular and on the screen portion of the phone logo there is an arrow facing down. I assume this is just telling me I need to actually download some software on the phone, but it won't connect via USB and every time it starts up it says that the drivers were not successfully installed and htc sync manager doesn't recognize that a device is even connected. The loop continued and i tried to boot it back into the fastloader which did nothing. I held down the buttons as if to boot it into fastloader, but this time for about 15 seconds which took me to a battery charging screen and finally ended the loop. I assume(hope) that since it's actually responding to input from the buttons that it's not irreversibly bricked. Is there any way I can get some version of android back on this thing? Any help would be much appreciated

Wrong forum buddy, you belong in the HTC ONE XL forum. Don't use anything from here because you risk a serious brick !

Related

Load issue

FIXED NOW!
Need help.
I burned the new Kavana ROM. everything was working ok.
placed my microSD and the device didn't recognize it, so i rebooted.
upon reboot the device got stuck on the white HTC screen.
pulled battery
tried again, rebooted, past the HTC screen to the Windows Mobile welcome screen but freeze again. hard reboot didn't respond.
pulled battery, then turned back on. device didn't even turn on!
tried several times with/without battery hooked up to power , and with/without SIM and/or microSD (all possible combinations) and nothing.
had lunch
went back to it and the device magically booted it but after the white HTC screen i got a blue screen asking about error from last reboot. said yes to correct. rebooted went past white HTC and into Windows mobile welcome screen and froze again.
repeated the process several times and finally got to the blue screen again asking about error from last boot, this time said 'no' and device continued boot in a white screen without HTC logo and froze.
all hard reset attempts were unsuccessful (if i'm doing it right: hold two soft keys and then power button).
now the device boots to the white HTC screen and then is stuck.
what to do?
edit: got the hard reset to work and reconfigured my phone. i only noticed the black screen for a split second because my Dash has issue that it thinks that the green send button is being pressed all the time (anyone know how to fix that?).
Thanks
Find your original rom in sticky, go into bootloader and flash original rom, then flash to wm6.1.
have the same issue!!... did you fixed? the main problem is activesync is not running so how do i install another ROM?
Active sync doesnt have to be working aslong as u got ur s621 pluged in and u wait for a few seconds before starting the ROM it will work.

Desire hangs at bootup screen and just vibrates a few times..:( (broken??)

Hey!
Im new to this forum but there seems to be a lot of experts here so i thought i'd try and see if anyone could help me!
Yesterday i put my desire to charge and after one hour i came back and it was showing the boot screen! The white background with the 3 green letters HTC! so i took out the battery and put it in again and restarted the phone but it only gets to that screen vibrates like 10 times and then hangs there! tried waiting for it for 30 min but nothing...
So then i tried to hard reset it and cleared the storage! but afterwards still the same!
Also when in "recovery mode" i sometimes see some green text flashing by for just a sec saying something like "warning...no image...."
Everything is in its original state, i havent rooted or reflashed it or anything... but i am willing to do so if it can solve my problems since warranty matters in my case will take ages!
The phones language is Swedish btw!
Can anyone help me?? its first now that u realize how much the phone means to you Miss my desire!
it sounds like the firmware is somehow corrupted. If you can boot the phone by pressing power and volume down, this will take you to the bootloader. From here you should be able to root the handset by following any number of threads here or on modaco!
Then I'd go Here and install this recovery. From then on you can choose a custom or stock rom to install.
You need to know though that rooting will void your warranty.
Have you also tried booting the phone normally with the SD card removed?

[Q] Screen Issues Lead To Bricked Device

I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery

Probably bricked, don't know what to do

Hey all,
So like about a year ago I installed twrp and rooted my one m8s and couldn't care less to update anything but everything was working fine.
Recently I bought a new phone so today I thought lets wipe the device and factory reset it. Well thats where it went wrong.
After the reset it tried to boot but was just stuck on the white screen with the HTC logo.
I then held the power + vol up, which triggered something and showed an other logo for a second then just going dark, but the device is still on and backlit.
I cant get out of this for some reason neither will the device turn off. When i connect it to my pc it gets recognized but I cant get into storage.
Also adb and fastboot won't see the device and the htc_fastboot.exe I got from here throws an adbwinapi.dll missing error.
I am really stuck on what to do and i was hoping maybe someone could help me out here?
Thanks in advance.
Regards,
Bart
EDIT: got the phone to turn off when the battery died and was able to boot into fastboot from there, lets see where this gets me.
EDIT #2: Welp I fixed it I suppose. If someone please could remove this thread since I can't

Nexus not booting up. Only fastboot and download mode while charging

Hello there everyone! Let me explain my problem:
Backstory
I have a Samsung Galaxy Nexus GT-i9250 maguro since 7-6 years or so. I've been flashing some roms into it and everything went well since a week ago.
I had installed from a very long time this version of CM "cm-13.0-20160921-NIGHTLY-maguro" and I have not updated it, so I basically was running that from a very long time.
Three weeks ago the phone started behaving strangely, it was closing automatically, and I thought that it was a temperature problem (being a very hot summer) so I did not worry too much.
Everything was working fine, charging and connecting via USB .
Problem
Last week the phone once again died and I tried to boot it up normally as I would normally do, but nothing happened, not even the Google logo popped up.
So I removed the battery and put it back in, the phone booted up to the Google logo, then after two or three seconds the Google logo flashed like brightness went up to 100% and black screen.
Went into fastboot, booted TWRP to see if that was working, and the recovery was working fine.
Things got worse.
At the moment
I cannot get the phone to do anything if it's not connected to a power source.
If the phone is connected via USB, or charger, I can get it to go ONLY on fastboot, and download mode. If I unplug the phone while on fastboot or download mode, the screen brightness goes up to 100% for half a second then it glitches out and goes into black screen immediatelly. I can not access bootloader nor recovery mode from fastboot, because the phone reboots, shows the Google logo and then it dies.
What I tried
Thinking that maybe the ROM went crazy, I followed this guide to flash the phone with all the original ROM and recovery (I downloaded "yakju-jwr66y-factory-4cadea65" and followed the instructions of the guide).
Nothing changed, if the phone is not connected to a power source, it is basically dead, if I put it to a power source it shows the charging logo for a second, then black screen, and I can only boot up fastboot and download mode.
I don't know if this might help but I've also tested the battery voltage and it seems to be fine.
Last thing, if I connect the phone to the PC (with the battery or without) every 2 seconds it shows up that an unidentified device is being detected.
I currently am using a laptop running windows 8.
On my desktop computer the same thing happens (the device detection) but from device manager I see a OMAP4400 (something like that) popping up but at the moment I cannot use my desktop PC since I'm traveling.
I would really like to know what happened to my phone, any answer will be appreciated.
Thanks in advance!
Update [solved]
After doing some research and trying different methods I gave up. But then I realized that maybe trying the stupidest thing could be the solution, so I went to a phone shop and asked them if they had some sort of test battery that I could plug in my phone temporarily to see if it was booting up.
Turns out, it was the battery.
I bought a new battery and now the phone runs smoothly like it's new.
I feel so dumb and I'm so sorry if I've made some of you people waste your time by reading the poem of the first post.
Hopefully this will someday help someone that will have the same problem of my GT-I9250!
(This thread can be closed now)

Categories

Resources