Hi, i own a HOX, i had alot of problems with it..
Now the problem i got yesterday, my phone just turns off randomly, after a while it will turn on after it booted, i find it weird, dont know if its related but it wont let me flash a kernel also, if i enter into bootloader and fastboot then plug in into the pc, the phone frezzes and the pc wont recognize it, so im stuck with paranoid android, another thing, if i go to the recovery and i try to do something heavy, like backup whole system and data, to see if the phone turns off, it doesnt happen, just when i turn on the phone, if i delete cache then boot up, it will upgrade all my 300+ apps in the start up, but once its finished it will just turns off, it happend me with Miui v 5, though it was the rom, switched to aokp, the same, then paranoin, no change, now i cant switch kernels, any idea why is happening? please help
Seems like a hardware failure of some kind, because it also happens in the recovery
Mr Hofs said:
Seems like a hardware failure of some kind, because it also happens in the recovery
Click to expand...
Click to collapse
it doesnt happen in the recovery, for bein unable to flash a kernel, somehow the drivers were missing, reinstalled, working, since the phone only turns off when android its actually on, but no in bootloader or recovery i assumed it was kernel failure, so i repacked the paranoid with the mx kernel and everything seems fine now.
Sorry i misread that part, completely my mistake ! But good you got the driver thing sorted, hope it stays okey now :thumbup:
Related
Hey guys,
I have a Problem with my HOX. I just unlocked it via HTCDev and flashed ViperX + Kernel.
That all went well but theres one Problem. If I try to shutdown my phone it always restarts insted of shutting down.
I tried a dozen factory resets, wiped everything and re-flashed the kernel a dozen times but that doesnt change a thing.
My HOX:
CID: o2_102
Hboot: 1.39.0000
Did you tried to press and hold power button for 10 seconds? That will simulate battery-pull.
Yes I did also about 10 times now. Right now I am flashing another ROM...
EDIT:
Ok, that didnt work either. Does anyone know what to do right now?
EDIT2:
If I start the HOX with the Charger plugged in, I have no Problem shutting it down. As soon as I pull the Cable the HOX starts like I pushed the Powerbutton.
Sounds like you've done a pretty thorough job. The only other thing I could suggest would be to try the ARHD superwipe tool in the Lextermina Abster Rom thread. It seems to do a more thorough cleaning. Fist go to recovery and wipe cache/dalvic and system and then go to install and run the superwipe. Hope that works out for you, if not might be a hardware fault.
from my Viped out one x
Hell Yeah, that worked...THX a lot to you Sir!
I flashed Lextermina and the Stock Kernel did a "Superwipe" and turned it off. Till now it didnt restart once.
What I dont know is if the Kernel or the Wipe fixed it.
Ok, I have another Update. I tried flashing ViperX again and again the phone wont shutdown.
So I thought that it cant be a flashing Problem but sth. else.
After some flashing, wiping etc. I went back to Lextermina and just looked trough the whole rom.
I stopped at "Fast Boot" or "Schnellstart" in German. Other than in most roms, FastBoot was activated.
So I unchecked FastBoot and bääm...Shutdown = Restart.
After that I activated FastBoot again and voila...my HOX shuts down like it is supposed to.
My question is, what really is Fastboot and why does it affect the Shutdown-Sequence?
Is it like "Force Quiet" for all the running apps?
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Why don't you try flashing the latest version of ICJ (3.4) with a full wipe and see whether the problem persists? Can you enter recovery now??
However, there's always a possibility of a hardware failure... and your situation with the random reboots / recovery reboots suggests somethings wrong!
ViktorN said:
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Click to expand...
Click to collapse
Sounds alot like a issue I had on ICJ quite a while ago.
If you select recovery at the bootloader, do you see the recovery for a split second and after that it reboots? I did flash multiple recoveries but it all didn't help. The luck I had is that fastboot was still working
I tried everything to get it to work, but nothing seemed to help. The only luck I had was that fastboot worked, and with that I managed to flash a RUU. What actually happend I don't know, but it worked again.
My KF gets stuck in cyanogen boot logo when 1. KF suddenly turns off or 2. Battery becomes low. I need to reflash it just for it to work again. PLEASE HELP any idea?
Plug the device into a power source
Hold the power button for 10 seconds to shut it off
Let it charge
soupmagnet said:
Plug the device into a power source
Hold the power button for 10 seconds to shut it off
Let it charge
Click to expand...
Click to collapse
no, the issue is more complicated than that.
Here's a scenario, for example i'm using it still @ 60% battery, then suddenly it will shut-off, when i try to re-start it it won't boot properly, it get stuck in the cyanogen logo, it seems some file gets corrupted, the only for it to work again is to reflash. (which im getting tired off )
vertcam9 said:
no, the issue is more complicated than that.
Here's a scenario, for example i'm using it still @ 60% battery, then suddenly it will shut-off, when i try to re-start it it won't boot properly, it get stuck in the cyanogen logo, it seems some file gets corrupted, the only for it to work again is to reflash. (which im getting tired off )
Click to expand...
Click to collapse
I see.
There was a user a while back that ended up with the eMMC bug and had to repartition his device to skip over the bad blocks. In doing so, he didn't allocate enough space for a proper cache partition (something like 150MB, I believe) and his device would do the exact same thing.
I would suggest clearing your cache and see if that helps. You may have to do a true wipe though, because I don't think a wipe in custom recovery will cut it.
You might want to check the cache, system, and boot partitions for bad blocks while you're at it.
Try other ROM
vertcam9 said:
My KF gets stuck in cyanogen boot logo when 1. KF suddenly turns off or 2. Battery becomes low. I need to reflash it just for it to work again. PLEASE HELP any idea?
Click to expand...
Click to collapse
From my experinces with KF1 for two years, switch to stock ROM 4.3 AOSP from Hashcode and everything became wonderful. better battery life, no freezing
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.
Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
xdaaccount123 said:
Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
Click to expand...
Click to collapse
Maybe its a stupid inquiry but does battery work as it should in stock rom? so that you can be absolutely sure its not faulty battery that's creating issues.because two things happen(in my experience when something goes wrong with boot.img) either its stuck at splash screen (hboot) with red text OR it goes blank but not off, just blank
Definitely isnt the battery. I am not experiencing any drain and it functions completely normally when plugged it. When I unplug, it works fine for a few min and then switches off. It will then not turn on, despite it showing 90%+ when I plug it in
but it happens in stock rom also? thats what i wanted to know .if you can full wipe and phone works when connected to usb,maybe you can run ruu and confirm that as well . If you can go to recovery ,make a nandroid backup.and try a ruu.
Yup, happens on stock as well.
Also, I think the recovery is messed up as well since it just crashes now when trying to flash something. It's having issues doing a nanroid backup as well
And no love for exe ruu as well?