I have a problem with my Htc Wildfire S. It charges very slowly, its slow to start up (about 20 mins, sometimes doesn't start and vibrates 10 times) and the touch wont work. I don't know if this means something but when its started up it have like a red light next the the htc text on the screen.
Please help if u can. Sorry for my bad English.
random_word said:
I have a problem with my Htc Wildfire S. It charges very slowly, its slow to start up (about 20 mins, sometimes doesn't start and vibrates 10 times) and the touch wont work. I don't know if this means something but when its started up it have like a red light next the the htc text on the screen.
Please help if u can. Sorry for my bad English.
Click to expand...
Click to collapse
That is strange, is the bootloader unlocked and have you installed any custom roms on it? The more ifno you cabn give about the phone and its present condition the better
robt77 said:
That is strange, is the bootloader unlocked and have you installed any custom roms on it? The more ifno you cabn give about the phone and its present condition the better
Click to expand...
Click to collapse
yes it's unlocked and i've installed cm9. Phone was working well and suddenly it happened. Phone didn't turn on. After that i've installed stock rom (that was really really hard) and now it starts up. (about 20 mins)
random_word said:
yes it's unlocked and i've installed cm9. Phone was working well and suddenly it happened. Phone didn't turn on. After that i've installed stock rom (that was really really hard) and now it starts up. (about 20 mins)
Click to expand...
Click to collapse
Do you still have the custom recovery installed? If so the best bet would be to do a wipe data from the revcovery and re isntall CM9 personally i would isntall CM10 and see how you get on. Have added different Roms to phones and sometimes a fresh install will sort out most problems.
No even soft bricked....
But why so slow boot no idea. It's very weird 20 mins boot!
Sent from my HTC Wildfire S A510e using Xparent SkyBlue Tapatalk 2
20 minutes for a boot ?
Did you install anything prior to this ?
Did you modify anything prior to this ?
All I can think of is a system file being misplaced ...
Bazinga
Can u boot into recovery, or do u have a nandroid backup... check that u format system as well as data.
robt77 said:
Do you still have the custom recovery installed? If so the best bet would be to do a wipe data from the revcovery and re isntall CM9 personally i would isntall CM10 and see how you get on. Have added different Roms to phones and sometimes a fresh install will sort out most problems.
Click to expand...
Click to collapse
No, stock rom installed. Yes i formatted as well as data. Phone isn't charging (actually it's charging but very very slowly) and touch screen isn't work. Can't install cwm after stock rom. (bootloader is unlocked.)
any help?
Try wipeing the delvic cache.. maybe itll help.
I think it's the hardware problem.
Sent from my HTC Wildfire S A510e using Tapatalk 2
Related
hi, i've just flashed PrimoS-v3.3, booted my phone and i'm stuck..can't do anything on the main screen because i've got the transparent stuff saying "Pull down to see notifications...Press....."
I've got a cross on the top bottom of the monitor but it doesnt work..
Anyone, help?! :\
Pull the batter reboot if it doesn't solve do a fullwipe and reinstall...
Sent from my HTC Desire HD using xda premium
re
tommy2601 said:
Pull the batter reboot if it doesn't solve do a fullwipe and reinstall...
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Dude i've done what u said, i formatted everything, now the phone doesnt boot :x ...
When trying to boot into recover, power+up volume all i got is a blinking red light :x
so i managed to flash the rom again, and i think now it's working!
i tried to install this rom on my dhd.i make full wipe and install,but when i reboot.i see htc logo and after the blacvk screen.Anyone can help for me?
wifi disconnects when open Facebook app
When I open Facebook app after few sec's wifi disconnects. It's like ON but not scanning and there are no available networks.
I must restart to be in normal.
Anyone else have this problem.
I'm on a 3.3 and DHD
3.3 version slow processing speed
On 3.3 during call when the screen is off volume buttons regulate Media volume instead In-call volume.
Desire HD
be sure that you have s-off and bootloader unlocked in the mean time this rom is a port so i suggest you try a normal rom while this rom is still work in progress
ghalyoum said:
be sure that you have s-off and bootloader unlocked in the mean time this rom is a port so i suggest you try a normal rom while this rom is still work in progress
Click to expand...
Click to collapse
Be sure that you never try to run S-OFF tools while your bootloader is unlocked...
Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone
WasifSal said:
Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone
Click to expand...
Click to collapse
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2
Kevin Ma said:
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I Re-Locked the phone
Will that flash the Recovery?
WasifSal said:
I Re-Locked the phone
Will that flash the Recovery?
Click to expand...
Click to collapse
unlock the phone again. flash the latest recovery. then go into fastboot. fastboot erase cache , then flash the kernel, go into recovery flash superwipe, flash rom and reboot and job done..
before you do all that though backup your current rom
I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use
WasifSal said:
I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use
Click to expand...
Click to collapse
well then leave it overnight to charge..see what happens in the morning then
Goku80 said:
well then leave it overnight to charge..see what happens in the morning then
Click to expand...
Click to collapse
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)
WasifSal said:
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)
Click to expand...
Click to collapse
man i am sorry then i wish i had more knowledge to give you help. hopefully someone else with more experience and knowledge can come and advise you different. just never had that issue you see.
if you say you can not go into bootloader or recovery then it does not sound right...maybe take it back to retailer or something might be the best option if no one can help out
have you tried the power button with the volume button down for ten seconds to see if the phone reboots?
Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(
WasifSal said:
Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(
Click to expand...
Click to collapse
try what i said to you in my last sentence mate
Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190
PatsFan1286 said:
Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
OK so I managed to get the phone UNLOCKED (Finally)
Now when I flash the 5.8.4.0 recovery it says
"unknown partition 'recovery-clockwork-touch-5.8.4.0-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.4.0-end
eavoru.img'"
So i booted the phone into the recovery mode instead of flashing.
I am finally getting somewhere but how do i know it's charging there? I don't see the red LED turn ON :/
LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??
WasifSal said:
LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??
Click to expand...
Click to collapse
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium
rayford85 said:
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Woah! That's spot on... I was surely gonna mess up my phone if i had done the RUU.
Its charging while the screen is off as we speak. But I think there is a problem with the charge thingy.
Its off and charging.. but sooner or later it turns off due to low battery (IM SUCH A NOOB I DNT KNW IF THE LOW BATTERY IS CAUSING THE PROBLEM)
I'll wait for it to charge again though and connect to the PC again
In the meanwhile can u answer me something regarding this
1. Does the red light turns on while charging in CWM 5.8.4.0
2. Does the mount USB Drive works? :'( Cuz when the phone was working fine. The mount USB Drive failed and gave an error of having a "lunfile missing" :/
Both of your questions can be found :
http://forum.xda-developers.com/showthread.php?t=1594819
i flashed the boot.img like ray said. then i turned the phone to recovery mode it went there and then mounted the usb it worked etc.
but I didnt flashed just yet.. i wanted it to be charged so i turned it off.. I am again getting that "not turning off" habit again
OH God what am i doing wrong here
PLEASE!! Someone help me! It's got that nasty thing that gets HTC Queitly Brilliant thing again.. It's charging but won't go into the recovery mode now!!!!!!!!!!!!!!!
How can I charge my phone while on Relocked Bootloader. I need help u guys!
Hi and firstly. thanks for your help!!
A friend gave me his hox for a repair after he tried putting in a new rom the wrong way...
so ive managed to put the rom he wanted (revolution hd 22) and the phone is now working ok...
calls, data, heavy apps... all works fine.
UNLESS- and thats the awkward part- unless you plug the usb data\charging cable out.
once the usb is out- the phone freezes for 30 seconds> reboots >than works fine for 30 seconds and than freezes whole over again
-this can happen until battery dies.
ive tried putting a new RUU
ive tried different kernels
ive tried wiping anything with fastboot or from the recovery
also tried TWRP and CWM- altough it dosnt even seems to be related
ive tried locking, unlocking, clearing fastboots cache... and NOTHING...
Now, the most weird thing, is when the phone is in recovery mode- it works on battery just fine!!
it can install my roms and kernels ok!
problem only occours when system goes up- than it will work only if its connected.
because of that- i can tell this isnt a hardware problem, and there must be a solution
does anyone has a clue with my issue please?
pazush said:
Hi and firstly. thanks for your help!!
A friend gave me his hox for a repair after he tried putting in a new rom the wrong way...
so ive managed to put the rom he wanted (revolution hd 22) and the phone is now working ok...
calls, data, heavy apps... all works fine.
UNLESS- and thats the awkward part- unless you plug the usb data\charging cable out.
once the usb is out- the phone freezes for 30 seconds> reboots >than works fine for 30 seconds and than freezes whole over again
-this can happen until battery dies.
ive tried putting a new RUU
ive tried different kernels
ive tried wiping anything with fastboot or from the recovery
also tried TWRP and CWM- altough it dosnt even seems to be related
ive tried locking, unlocking, clearing fastboots cache... and NOTHING...
Now, the most weird thing, is when the phone is in recovery mode- it works on battery just fine!!
it can install my roms and kernels ok!
problem only occours when system goes up- than it will work only if its connected.
because of that- i can tell this isnt a hardware problem, and there must be a solution
does anyone has a clue with my issue please?
Click to expand...
Click to collapse
try a custom kernel...if that doesn't wprk just go into a store or so and ask there what could the issue...if it wasn't there when he had the stock rom on it than he had a really bad flash and it is maybe rom or mainboard problem in some way
Sounds like a power issue. I think its hardware
Yep its maybe HW problem but why he can charge then in Recovery Mode
Solution:Your friend could charge in Recovery Mode and then boot up to the Rom
or you could try another ROM (your last hope ?)
Hey, thanks for helping,
There is no problem with charging it...
Problem is it cant work on battery
Only recovery works with bat power.
When using rom on bat- it freezes.
Edit: oh and one more thing, the phone is almost brand new, it has been used for only one week and worked ok. Until my friend took it to a store here for adding other lang...
Sent from my GT-I9300 using xda app-developers app
Recovery mode is taking less battery power then if you are using it with a rom booted up... Maybe the battery is now broken or the connectors are bad or so...
And what do you mean with adding other lang?
Gesendet von meinem HTC One X mit Tapatalk 2
One-X-master said:
Recovery mode is taking less battery power then if you are using it with a rom booted up... Maybe the battery is now broken or the connectors are bad or so...
And what do you mean with adding other lang?
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
i thought about it, but i think installing a new rom via recovery is taking more power
than just staring at the regular booted screen while its on idle
30 seconds of staring- freeze and than reboot...
i just cant figure how its a hardware issue, the device is almost new... how is it possible that im the first one meeting this issue?
and i ment my friend wanted to add another os language that didnt come stock (rom change)
pazush said:
i thought about it, but i think installing a new rom via recovery is taking more power
than just staring at the regular booted screen while its on idle
30 seconds of staring- freeze and than reboot...
i just cant figure how its a hardware issue, the device is almost new... how is it possible that im the first one meeting this issue?
and i ment my friend wanted to add another os language that didnt come stock (rom change)
Click to expand...
Click to collapse
try a complete full wipe ...wipe system, data, dalvik-cache and cache...and before maybe try factory reset from bootloader and be sure to save all content from sdcard to pc ...if that doesn't help try the complete full wipe ...if that doesn't help it's an hardware issue and he maybe pulled the caable wrong out or so or i really don't know...
One-X-master said:
try a complete full wipe ...wipe system, data, dalvik-cache and cache...and before maybe try factory reset from bootloader and be sure to save all content from sdcard to pc ...if that doesn't help try the complete full wipe ...if that doesn't help it's an hardware issue and he maybe pulled the caable wrong out or so or i really don't know...
Click to expand...
Click to collapse
hey, ive done that already.
whats the deepest way to rewrite the onex's software?
i tried ruu, is there anything other i dont know?
pazush said:
hey, ive done that already.
whats the deepest way to rewrite the onex's software?
i tried ruu, is there anything other i dont know?
Click to expand...
Click to collapse
Go into a store or ask and say you have this problem or your friend have to go and if he ask if you unlocked say yes but this problem was even on stock therefore you flashed a custom Rom because you thought it will fix it...
Gesendet von meinem HTC One X mit Tapatalk 2
Thank you for trying to help again,
But it isnt resonable to determine the phone mainboard is dead, all signs shows its software...
If it helps, the hox makes a long beep, or drawing stripes on the screen sometimes before it restarts, the other times it just freezes.
Sent from my GT-I9300 using xda app-developers app
pazush said:
Thank you for trying to help again,
But it isnt resonable to determine the phone mainboard is dead, all signs shows its software...
If it helps, the hox makes a long beep, or drawing stripes on the screen sometimes before it restarts, the other times it just freezes.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Flash completely another Rom...and also other kernel...some ppl had those issues too but it was problem with mainboard maybe its the mainboard problem...
Gesendet von meinem HTC One X mit Tapatalk 2
Hello folks,
this morning i wanted to check the watch on my phone and noticed it was very slow. As i am on a cm 11 nightly, i decided to reboot.
The phone shut down correctly but didnt come up afterwards, the screen stayed black. About 4 minutes later, the "HTC quietly brilliant" logo appears. About another 1-2 min. the cyanogenmod boot screen appears. I can repeat that behaviour every time. same with boot to recovery or fastboot. After booting up completely, the phone usage appears to be normal excep the display brightness sensor is not working automatically.
Please note that i am on the same nightly for about 10 days now without any issues except a few reboots. I didn't change anything in the last days, same setup, same usage.
I wiped the caches, installed newest nightly, nothing changed. i cant logcat during boot because adb devices says no device attached.
does anybody has any idea what i can do? i am afraid it seems to be some kind of hardware failure...?
regards,
In fastboot use
Fastboot erase cache
and also backup apps and messages and wipe everything expect battery stats and sd card I had that problem too
big noob said:
In fastboot use
Fastboot erase cache
and also backup apps and messages and wipe everything expect battery stats and sd card I had that problem too
Click to expand...
Click to collapse
Thanks for your answer. Unfortunately, as i anticipated, it did not work. I factory resetted the phone and erased all caches (not via fastboot but cwm, i guess it does the same).
I don't think it is a ROM problem as there are no issues when android is booting but at the, i will call it POST (the htc quietly brilliant logo )of the phone.
I think the proximity sensor/brightness sensor is defective and the phone recognizes it during the "POST" and runs in some kind of timeout and then starts booting.
Can somebody confirm a phone does have something like a hardware check before booting the OS?
Kind regards,
two_handed said:
Thanks for your answer. Unfortunately, as i anticipated, it did not work. I factory resetted the phone and erased all caches (not via fastboot but cwm, i guess it does the same).
I don't think it is a ROM problem as there are no issues when android is booting but at the, i will call it POST (the htc quietly brilliant logo )of the phone.
I think the proximity sensor/brightness sensor is defective and the phone recognizes it during the "POST" and runs in some kind of timeout and then starts booting.
Can somebody confirm a phone does have something like a hardware check before booting the OS?
Kind regards,
Click to expand...
Click to collapse
Are you tryed with diferent rom? I think it is not a problem if your prox sensor not working!!!
Thant said:
Are you tryed with diferent rom? I think it is not a problem if your prox sensor not working!!!
Click to expand...
Click to collapse
No, i did not try a different ROM. Why should i? it worked with CM11 before without any issues...
two_handed said:
No, i did not try a different ROM. Why should i? it worked with CM11 before without any issues...
Click to expand...
Click to collapse
Obviously, it is ROM's problem. Because it is nightly. Although I have installed nightly too, one from 23 feb. And I have no problems. By the way, snapshot built l built is released now and I'm gonna try it today.
Sent from my One X using xda app-developers app
Timofey_K said:
Obviously, it is ROM's problem. Because it is nightly. Although I have installed nightly too, one from 23 feb. And I have no problems. By the way, snapshot built l built is released now and I'm gonna try it today.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Still i really don't think it is a ROM problem. I just noticed that the phone even in fastboot behaves REALLY slow (changing the menu with volume buttons takes 1-2 minutes). And fastboot definately is independent from the ROM.
Anyways, i am just downloading CM 10.2 stable realease and flash it just to be sure.
Yep, as i thougth, still black screen for 4 minutes until the HTC quietly brilliant logo appears.
Guess it's faulty hardware then... Would be nice if someone could confirm my assumption that there is some kind of POST before the ROM is loaded.
regards
two_handed said:
Yep, as i thougth, still black screen for 4 minutes until the HTC quietly brilliant logo appears.
Guess it's faulty hardware then... Would be nice if someone could confirm my assumption that there is some kind of POST before the ROM is loaded.
regards
Click to expand...
Click to collapse
Try to flash sense rom like ARHD it is close to stock and see what will heppend then if it is the same it is hardware if not is problem it CM
Hey Guys I really need your help.
I'm really worried as my phone just wont switch on. I was having issues with CM11, so I reverted back to ViperX 4.0.7, flashed the heartbleed patch, installed regular apps and the phone was working fine. With around 25% charge, I did a restart and the phone just won't switch ON again. Couple of times earlier when the phone wouldn't switch one I would hold the Power+Vol Down and it would start in the bootloader. But right now even that is not working. I tried keeping it under direct light and holding the buttons that too isn't working. Have charged it for nearly 18 hours now. Its out of warranty. Guys any help Whats wrong with it? How do I fix this ? Any help would be really appreciated.
xtr0ngrid said:
Hey Guys I really need your help.
I'm really worried as my phone just wont switch on. I was having issues with CM11, so I reverted back to ViperX 4.0.7, flashed the heartbleed patch, installed regular apps and the phone was working fine. With around 25% charge, I did a restart and the phone just won't switch ON again. Couple of times earlier when the phone wouldn't switch one I would hold the Power+Vol Down and it would start in the bootloader. But right now even that is not working. I tried keeping it under direct light and holding the buttons that too isn't working. Have charged it for nearly 18 hours now. Its out of warranty. Guys any help Whats wrong with it? How do I fix this ? Any help would be really appreciated.
Click to expand...
Click to collapse
Connect phone to pc and hold the power button...if you don't have luck your phone is stuck in apx mode so only HTC can fix it...if not then you may have luck and it will turn on the normally
Gesendet von meinem HTC One_M8 mit Tapatalk
One-M8-Master said:
Connect phone to pc and hold the power button...if you don't have luck your phone is stuck in apx mode so only HTC can fix it...if not then you may have luck and it will turn on the normally
Click to expand...
Click to collapse
Thanks One-m8-master. I connected the phone to the PC and in device manager under 'Other Devices' it showed up as APX. Then I tried pressing the Volume down key for 10 Seconds+ and then pressing the Power key for 10 seconds without the usb. And then after reconnecting it to the PC it displayed 'USB Device not recognized' and under 'USB controllers' shows Unknown device. Does it mean its still in APX mode?
xtr0ngrid said:
Thanks One-m8-master. I connected the phone to the PC and in device manager under 'Other Devices' it showed up as APX. Then I tried pressing the Volume down key for 10 Seconds+ and then pressing the Power key for 10 seconds without the usb. And then after reconnecting it to the PC it displayed 'USB Device not recognized' and under 'USB controllers' shows Unknown device. Does it mean its still in APX mode?
Click to expand...
Click to collapse
Yes, your phone is bricked....even if you get out of apx mode like I sometimes was able after a reboot or so you will stuck again and after a few times it will never turn on again....so send in
Gesendet von meinem HTC One_M8 mit Tapatalk
One-M8-Master said:
Yes, your phone is bricked....even if you get out of apx mode like I sometimes was able after a reboot or so you will stuck again and after a few times it will never turn on again....so send in
Click to expand...
Click to collapse
i was dreading those words
Just a recap. I was running CM11. Phone switched off at 50%. Dint Turn on for a long time. Turned it on by pressing Power+Vol Down (holding it for a while). Phone ran fine till it discharged completely and shut down. After charging it for a while, had to restart it again by Power+Vol Down. And apps started crashing. Next:
1) Booted into bootloader >fastboot USB>Flashed ViperX.4.0.7 boot img. included in full rom zip file.
2) In CWM recovery the The viper Installation failed. Back to Bootloader
3) Flashed the TWRP recovery.
4) Fastboot flash Viper boot.img again followed by fastboot erase cache.
5)Flashed the Viper Rom. Installed Apps. All went fine.
6) Did a restart it worked ok. After sometime I did a restart again and it Never came back.
Any idea what I screwed up with those steps so i dont mess it up again??
xtr0ngrid said:
i was dreading those words
Just a recap. I was running CM11. Phone switched off at 50%. Dint Turn on for a long time. Turned it on by pressing Power+Vol Down (holding it for a while). Phone ran fine till it discharged completely and shut down. After charging it for a while, had to restart it again by Power+Vol Down. And apps started crashing. Next:
1) Booted into bootloader >fastboot USB>Flashed ViperX.4.0.7 boot img. included in full rom zip file.
2) In CWM recovery the The viper Installation failed. Back to Bootloader
3) Flashed the TWRP recovery.
4) Fastboot flash Viper boot.img again followed by fastboot erase cache.
5)Flashed the Viper Rom. Installed Apps. All went fine.
6) Did a restart it worked ok. After sometime I did a restart again and it Never came back.
Any idea what I screwed up with those steps so i dont mess it up again??
Click to expand...
Click to collapse
You Should Use Phizl'recovery (5.19.5),do not Fullwipe in Aroma. I think it ll be OK.
Sent from my One X using XDA Free mobile app
Namautoenx said:
You Should Use Phizl'recovery (5.19.5),do not Fullwipe in Aroma. I think it ll be OK.
Click to expand...
Click to collapse
Thanks for the reply. But even to load Phizl'recovery, How do i get somewhere to install it without the phone turning on??
xtr0ngrid said:
Thanks for the reply. But even to load Phizl'recovery, How do i get somewhere to install it without the phone turning on??
Click to expand...
Click to collapse
Yeh, ị misunderstand your comment, I don't know your phone can not switch On.
Sent from my One X using XDA Free mobile app
Mr Hofs said:
As one M8 said, a APX is a bricked hox. No wrongs steps caused that it's just a hardware fault. Replacing the mainboard will solve it permanently.
Click to expand...
Click to collapse
Thank you Mr. Hofs. I guess Im out of luck then. I had purchased the phone from a different county and its been well more than 1.5 years. I love this phone too much
Does using aosp roms brick the device ? Or changing roms does that ?
My device is running aosp ROM and when it runs out of battery, i cant switch it on normally after putting it on charge. I have to keep pushing the power button to boot it (capacitive buttons flashes)
Is my phone also dying ?
a.broken.star said:
Does using aosp roms brick the device ? Or changing roms does that ?
My device is running aosp ROM and when it runs out of battery, i cant switch it on normally after putting it on charge. I have to keep pushing the power button to boot it (capacitive buttons flashes)
Is my phone also dying ?
Click to expand...
Click to collapse
Don't know, ask it in the Q&A section, maybe someone knows there about this issue. Or ask it in a AOSP rom thread if more people suffer from this matter. This should be the development thread for the Viper X rom
a.broken.star said:
Does using aosp roms brick the device ? Or changing roms does that ?
My device is running aosp ROM and when it runs out of battery, i cant switch it on normally after putting it on charge. I have to keep pushing the power button to boot it (capacitive buttons flashes)
Is my phone also dying ?
Click to expand...
Click to collapse
Guess that should Not be the reason. Many use AOSP Roms and even switch between sense and aosp roms often. My phone was working fine with both CM11 and Viper no problems absolutely until yesterday where apps started crashing and after a fresh install, its just not turning on.
xtr0ngrid said:
Guess that should Not be the reason. Many use AOSP Roms and even switch between sense and aosp roms often. My phone was working fine with both CM11 and Viper no problems absolutely until yesterday where apps started crashing and after a fresh install, its just not turning on.
Click to expand...
Click to collapse
I really hope somehow your phone starts ... Its sad to see someone's phone getting bricked...
a.broken.star said:
I really hope somehow your phone starts ... Its sad to see someone's phone getting bricked...
Click to expand...
Click to collapse
Thanks buddy. I took it to the HTC Centre today and they said motherboard needs to be replaced which would cost a bomb almost equal to buying a new phone. I just have one query, with the phone looking more or less hard bricked, is JTAG a good solution? Do the phones go the distance once they have been fixed via JTAG. Thanks for all the support guys.
xtr0ngrid said:
Thanks buddy. I took it to the HTC Centre today and they said motherboard needs to be replaced which would cost a bomb almost equal to buying a new phone. I just have one query, with the phone looking more or less hard bricked, is JTAG a good solution? Do the phones go the distance once they have been fixed via JTAG. Thanks for all the support guys.
Click to expand...
Click to collapse
It's a hardware issue... you didn't accidentally brick the device so it should not help.
xtr0ngrid said:
Thanks buddy. I took it to the HTC Centre today and they said motherboard needs to be replaced which would cost a bomb almost equal to buying a new phone. I just have one query, with the phone looking more or less hard bricked, is JTAG a good solution? Do the phones go the distance once they have been fixed via JTAG. Thanks for all the support guys.
Click to expand...
Click to collapse
Jtag could help but it's really hard or even impossible to do it with this phone...also the apx mode/bricked phone is due to some problems in system partitions which can't be modified by flashing roms or kernels without s-off...it's just a fault which earlier devices of one x are having...it can also happen if you flash too Many times different roms without wiping system or even wiping system too many times...but for now you can ether get a new device because buying new mainboard is stupid if it costs like a new device xD
Gesendet von meinem HTC One_M8 mit Tapatalk
One-M8-Master said:
Jtag could help but it's really hard or even impossible to do it with this phone...also the apx mode/bricked phone is due to some problems in system partitions which can't be modified by flashing roms or kernels without s-off...it's just a fault which earlier devices of one x are having...it can also happen if you flash too Many times different roms without wiping system or even wiping system too many times...but for now you can ether get a new device because buying new mainboard is stupid if it costs like a new device xD
Gesendet von meinem HTC One_M8 mit Tapatalk
Click to expand...
Click to collapse
a RUU won't help ? just a suggestion !
xeloni said:
a RUU won't help ? just a suggestion !
Click to expand...
Click to collapse
Ruu wud be helpful if the phone atleast booted to bootloader
So he can't do that
Sent from my HTC One X using Tapatalk
kantry123 said:
Ruu wud be helpful if the phone atleast booted to bootloader
So he can't do that
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
xeloni said:
a RUU won't help ? just a suggestion !
Click to expand...
Click to collapse
Nope even if the phone could boot by luck it won't help...there are damaged partitions which only can be fixed by replacing mainboard or use different hardware to repair them...a ruu just format and wipes them...if we had s-off we maybe could repartition whole phone...so only help is replacing majnboard or buying new phone
Gesendet von meinem HTC One_M8 mit Tapatalk
One-M8-Master said:
Nope even if the phone could boot by luck it won't help...there are damaged partitions which only can be fixed by replacing mainboard or use different hardware to repair them...a ruu just format and wipes them...if we had s-off we maybe could repartition whole phone...so only help is replacing majnboard or buying new phone
Gesendet von meinem HTC One_M8 mit Tapatalk
Click to expand...
Click to collapse
I will never buy a nvidia phone !!
Only Qualcomm !!