I am not sure if anyone experience this but then again my phone is rooted. I was just browsing around the internet and it started heating up, next thing i know the phone just shutdown and all kind of error popout then it just hard reset by itself where I had to set all the stuff again. But after a while all those error kept popping out again and now I can't even do anything anymore.
Pretty much it just get stuck with HTC logo & beats now, I still can access the recovery menu. Trying to find the right RUU file and which I am not sure myself now where to download or what to download.
The phone CID is HTC_044, I remember using the latest update available and so on. Any idea what am I suppose to do now? I was looking at the nandroid copy from this thread and downloaded my but I have no idea how to use it
Do the command
Fastboot getvar version-main
Post back the number please
Mr Hofs said:
Do the command
Fastboot getvar version-main
Post back the number please
Click to expand...
Click to collapse
Thanks for the quick reply, anyway how can I do that? using adb? (sorry for the noob question)
I am in fastboot usb now
Phone in fastboot usb / bootloader
Then open a command window in the folder where also the fastboot files are ! Point in the folder with the mouse and hold shift + right click the mouse - select open new window here
And type there the command
Mr Hofs said:
Phone in fastboot usb / bootloader
Then open a command window in the folder where also the fastboot files are ! Point in the folder with the mouse and hold shift + right click the mouse - select open new window here
And type there the command
Click to expand...
Click to collapse
Got it forgot it was a exe file, anyway I am stuck trying to get the phone to (on) the screen is black now, holding down the power button for more then 10 second don't seem to work nor the volume button+ power button too works.
Got it:
version-main: 3.14.707.24
finished. total time: 0.006s
Try it with the volume - and the power button
Mr Hofs said:
Try it with the volume - and the power button
Click to expand...
Click to collapse
version-main: 3.14.707.24
finished. total time: 0.006s
(Pretty much getting annoyed with this phone, I should have just use a custom rom rather then this unstable version of stock rom)
Here it is
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Phone in the bootloader and lock it
Fastboot oem lock
Keep the phone in the bootloader and execute the ruu from the pc with admin rights. Right click the ruu and select
Run as administrator
Mr Hofs said:
Here it is
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Phone in the bootloader and lock it
Fastboot oem lock
Keep the phone in the bootloader and execute the ruu from the pc with admin rights. Right click the ruu and select
Run as administrator
Click to expand...
Click to collapse
Thanks
Installed back all my apps... now after did all those I try to sign into the htc friend steam and only to make the phone reboot. Like what is wrong with this phone
seems like it is stuck at the htc logo now... and back to square one. Should I claim for warranty?
This is the second time it factory reset by itself now, so like I don't think this is an software issue
Also I notice now I can't turn off the phone, it just restart and I get some error notification.
Warranty it is.....
Mr Hofs said:
Warranty it is.....
Click to expand...
Click to collapse
I used One_X_All-In-One_Kit_v2.3 to lock back the boot, will I need to do anything else before I send for warranty? all my files are gone, seems like not only it hard reset but also deleted and created a new partition in the phone lol
adkz said:
I used One_X_All-In-One_Kit_v2.3 to lock back the boot, will I need to do anything else before I send for warranty? all my files are gone, seems like not only it hard reset but also deleted and created a new partition in the phone lol
Click to expand...
Click to collapse
Make sure its on stock firmware and stock recovery.
My pal sent his back with boot loader unlocked but all stock firmware and they repaired it.
Sent from my HTC One X using xda app-developers app
He used a ruu already so he is as stock as he can be.....
treebill said:
Make sure its on stock firmware and stock recovery.
My pal sent his back with boot loader unlocked but all stock firmware and they repaired it.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Mr Hofs said:
He used a ruu already so he is as stock as he can be.....
Click to expand...
Click to collapse
After noticing the overheat problem seems to be commen, I bought myself a S3 and might actually be happy with it. I mean like leedroid is no more around, htc service is not available in my state plus I got to wait like almost a month to get a board replacement or the whole phone. I am gonna sell it off lol.
Then again thanks a lot for the help :good: it made me choose wisely now.
Oke ...
CASE CLOSD !
Just wanted to inform the rest about my warranty status, finally got my phone back but.. it is being recond :laugh: I gave htc service center a call last Thursday and was inform that my phone was on the way back to my city. Best part was, the operator didn't know what did they do with it lol
Attached the repair report and seems like they even added a dent to my top left? I was using otterbox defender since I gotten this, not too sure how that dent was created but then should not have been around while i was on still using the phone before it just died on me. Then again a free hardware upgrade to 32gb for this phone sure did make me happy.
Not too sure what to do with this phone now, some how I don't feel like selling it so might just switch around with my sIII once in a while lol
Related
Hi Guys,
Recently, my HTC One X's screen has gone a bit crazy. At first, the screen image would get corrupted, but now the screen won't even turn on. I know my phone still works because I can feel the vibrations on it, and when I call it I hear the ringtone.
Rarely, my phone's screen works, but this is a 1% chance, after rebooting my phone a million times. This problem seems to occur on whichever rom I use, so I suspect it's a hardware problem.
I would go into HBoot and restore to stock using RUU, but the screen is blank no matter what, so I don't know what's happening. My phone is rooted and unlocked on a MIUI rom, so I don't know if my warranty still applies and whether service centre will fix it for me.
Any help would be greatly appreciated.
Best Regards,
DarkyHero
Can you do adb or fastboot commands ?
Adb reboot bootloader
Or
Fastboot reboot bootloader
MarcelHofs said:
Can you do adb or fastboot commands ?
Adb reboot bootloader
Or
Fastboot reboot bootloader
Click to expand...
Click to collapse
Sadly I'm not brave enough to do so, as my phone remains blank even when I hold the button combination to get into HBoot.
The thing is I know that my phone is still working as I can hear the notification sounds from it, and the LED light shows when charging.
Do you have any idea what else I should do?
Take it to a repair shop.....i don't know what else
If you can do fastboot commands you might be able to flash it back to stock, if the problem is not gone after that you might want to send it in for warranty
MarcelHofs said:
Take it to a repair shop.....i don't know what else
If you can do fastboot commands you might be able to flash it back to stock, if the problem is not gone after that you might want to send it in for warranty
Click to expand...
Click to collapse
OK thanks, but do you know if I can tell me if there is a computer programme that tells me what mode the phone is in, so I know when it is in fastboot mode with? Then I would be able to flash RUU back to stock.
Execute
Code:
fastboot devices
If you see your serial number, you are in fastboot mode. This is the only way I'm afraid.
TToivanen said:
Execute
Code:
fastboot devices
If you see your serial number, you are in fastboot mode. This is the only way I'm afraid.
Click to expand...
Click to collapse
Thanks. If my computer sees that my phone is in fastboot mode but my phone's screen still stays blank, is it safe to execute RUU or do I need some input on my phone?
This might sound a bit random, but do I need to enable USB Debugging?
Thanks so much for your help.
Yes USB debugging should be enabled....if you do fastboot devices and the serial comes up you are oke
To run the ruu you have to relock the bootloader
Fastboot oem lock
After that wait some time (10 sec)
And run the ruu with admin rights from pc
You should only do this if you have already the correct ruu
No need for usb debugging.
It would only allow the ruu to put phone in fastboot mode, but it isn't needed if the phone already is in fastboot mode.
No screen input needed during ruu afaik.
Sent from my HTC One X
TToivanen said:
No need for usb debugging.
It would only allow the ruu to put phone in fastboot mode, but it isn't needed if the phone already is in fastboot mode.
No screen input needed during ruu afaik.
Sent from my HTC One X
Click to expand...
Click to collapse
Ah yes sorry my bad on that !
MarcelHofs said:
Ah yes sorry my bad on that !
Click to expand...
Click to collapse
Thanks so much for your help guys!
My phone's screen is working again, so I will try to execute RUU now.
So steps are as follows:
1. Lock bootloader
2. RUU
There is just one more thing I would like to ask you awesome guys, do I need to first flash stock recovery like it says in this video?
http://www.youtube.com/watch?v=SZuAjz4PIjU Around the 3:45 mark.
Thanks a lot!
DarkyHero
No ....
The ruu will flash back the stock boot.img, stock recovery and it will bring back the rom to its original state.
MarcelHofs said:
No ....
The ruu will flash back the stock boot.img, stock recovery and it will bring back the rom to its original state.
Click to expand...
Click to collapse
Thanks so much, you are my HERO!!!
Why ? Did it work ?
Ok guys ive not posted much as ive had no need to... im fairly competant when it comes to messing with my phone but im baffled now.... Ive rooted desire hd, sensation xl and a few other phones so im not a complete noob i wouldnt say... although you lot may haha
OK, so ive tried to go stock from all of the different nandroid back ups that correspond with my device (because my hard drive crashed and killed all my data,) on this site to no avail. Every single one no matter how i do it, or in what manner, give me the same issue, an md5 checksum mismatch error. Doesn't matter what its called or where its unzipped too, i get the exact same thing every time. Also since starting this process abd no longer works.... The laptop sees the phone and if i try to use fastboot or any of the fastboot commands they work fine. If i do adb devices it shows nothing in the list. I can fastboot boot boot.img and then clear the cash but i just cannot get it to restore the back up at all so i can then flash the recovery after and get it running again.
Im currently in the process of downloading what i believe is the RUU for this phone so we will see if this works.
I need to reset back to factory because i want to sell the phone as a stock unrooted phone to a family member who will want to be able to do ota updates etc. And if it ever breaks or needs sending back it needs to be stock. so........ i was wondering if anyone on here could help me in any way to get my current brick back to a working stock HOX.
CID is H3G_001
version is 2.17.771.3
currently on the lastest CWM
on my fastboot screen ive got
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.12.0000
CPLD-None
MI CROP-None
RADIO-2.1204.135.20H
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH : OFF
Jun 28 2012,11:31:28
Now is it possible usb debugging may have been turned off thus stopping the adb commands? I cannot get past the boot loop so i am unable to check...
All im trying to do is get back to the stock phone. If anyone is able to help me do that i would gladly show my appreciation....
Kind Regards
Brett (Nibbzy)
1. DL this: http://androidfiles.org/ruu/securek...adio_2.1204.135.20H_release_277220_signed.exe
2. do 'fastboot oem lock' (locks the bootloader)
3. Phone in fastboot mode, right click on RUU and run as admin.
3. Sit back and wait.
TToivanen said:
1. DL this: linky
2. do 'fastboot oem lock' (locks the bootloader)
3. Phone in fastboot mode, right click on RUU and run as admin.
3. Sit back and wait.
Click to expand...
Click to collapse
HI mate,
My bootloader is now in ***RELOCKED *** status. I
Ive already got 2 x copies of that exact file from that exact link. but it tells me to turn the phone on and will not do anything untill i do. If it turn it on. it boots for about 30 seconds and goes right back round to htc screen again and then just loops eternally.
thanks for your help....
edit.... i think it was the admin rights i was missing! your an absolute legend and if you have a donate button anywhere post me the link in a pm.
Hold the volume down and power button pressed together as long as it takes to see the bootloader ....
Do not let go of the buttons
Hold volume down and power. Then in the bootloader menu, select fastboot. EDIT:
TToivanen said:
Hold volume down and power. Then in the bootloader menu, select fastboot. EDIT:
Click to expand...
Click to collapse
ABSOLUTE PAIR OF LEGENDS.... 8 HRS ive been ready to smash the b**tard thing for..... lolol
Ha ha
Don't mention it
TToivanen said:
Ha ha
Don't mention it
Click to expand...
Click to collapse
Ive been struggling with a similar problem. i want to get back to stock so that i can sim unlock my device. It seems to me that i need to run the correct RUU file in order to get back to stock, however im not sure which file i should be running. my CID is ORANG001 and my HBOOT is 1.36.
LiamKenny said:
Ive been struggling with a similar problem. i want to get back to stock so that i can sim unlock my device. It seems to me that i need to run the correct RUU file in order to get back to stock, however im not sure which file i should be running. my CID is ORANG001 and my HBOOT is 1.36.
Click to expand...
Click to collapse
Please do the fastboot command 'fastboot getvar version-main'
Sent from my Nexus⁴ using Tapatalk 4 Beta
version main: 3.16.61.6
TToivanen said:
Please do the fastboot command 'fastboot getvar version-main'
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
version main: 3.16.61.6
LiamKenny said:
version main: 3.16.61.6
Click to expand...
Click to collapse
RUU is not available but you can get back to stock using a nandroid backup. Download the one that matches your main version here: http://forum.xda-developers.com/showthread.php?t=1975140
If it's zip/far, extract it and copy the files onto your sdcard nandroid folder. Then restore the backup in recovery just like you normally would. You may also flash stock recovery and lock the boot loader if you want.
Sent from my Nexus⁴ using Tapatalk 4 Beta
i went into clockwork mod and did a factory reset data, then i wiped the dalvik cache and then tried to restore the file which you linked to me, but it says "MD5 mismatch". do you know where i have gone wrong?
LiamKenny said:
i went into clockwork mod and did a factory reset data, then i wiped the dalvik cache and then tried to restore the file which you linked to me, but it says "MD5 mismatch". do you know where i have gone wrong?
Click to expand...
Click to collapse
Maybe a bad download? Did you extract it?
Sent from my Nexus⁴ using Tapatalk 4 Beta
yeah, i did. and then i put the extracted folder on my sd card. ill download it again and see if it works, but can you tell me what are all of the steps i need to do, in case I'm a complete noob and missed out something crucial
I've downloaded the nandroid backup from a few places now and none of them seem to work. the phone just stops on the boot animation and goes no further
I had the same on my hox flashed boot img erased cache,stuck on boot animation
Sent from my 801n M7_UL
Hi,
I have HTC One X, I did unlock and Root the device, but since then I face a screen off problem
meaning
whenever I want to turn the screen on using the power button it takes up to 3 or 10 presses to be on and allow me to use my device, sometimes it didn't respond at all, that I have to turn my device off entirely by long press the power button,
this thing happens after 2 to 5 hours of me installing any room, and some times it didn't happen for half hour or hour, but then it happens again,
I tried everything
from backing to Stock ROM to flashing over 10 different ROMS they all work fine but the screen off problem remains,
now I'm sure it's not a hardware issue since it wasn't there before unlocking my device, I tried relocking the device and flashing a stock ROM but it didn't work.
Some searching results says that it's a booting up problem that the graphic card have a wrong boot info, but if so how can I solve that ?!
my CID is 044 If anyone knows of have a hboot file or boot.img file or anything that can help me solving this problem I would be very grateful
waiting >>>
Maybe a problem with the power button?
Sent from my HTC One X using xda app-developers app
athulele said:
Maybe a problem with the power button?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
It wasn't there before unlocking the device, it happens after that particular action
+ that the power button works fine and the screen three lower main touch buttons light up while the screen it self stay off !
Such problems are extremely hard to pin point... May be a hardware issue... Since you have have tried different roms!
Go back to stock and try sending it for warranty...
vin4yak said:
Such problems are extremely hard to pin point... May be a hardware issue... Since you have have tried different roms!
Go back to stock and try sending it for warranty...
Click to expand...
Click to collapse
the problem is when I go back to stock the hboot says relocked, how can I make it Locked !?!
another problem is that my device warranty over
EngASM said:
the problem is when I go back to stock the hboot says relocked, how can I make it Locked !?!
another problem is that my device warranty over
Click to expand...
Click to collapse
You can't get back to ***Locked***...
Hmmm... if it's a hardware issue then, you will have to shell out if you want to fix this....
vin4yak said:
You can't get back to ***Locked***...
Hmmm... if it's a hardware issue then, you will have to shell out if you want to fix this....
Click to expand...
Click to collapse
Well, I'm leaving the Hardware Issue thing to the bottom of my list, as I said before the problem exists only after I unlocked my device, so I think that something went wrong during that process maybe boot.img file or Hboot file error that makes the graphics out of order in such a way that it didn't boot correctly,,
do you know how can I get hboot file for my device !? or at least how can I upgrade it or downgrade it to a different number !?
EngASM said:
Well, I'm leaving the Hardware Issue thing to the bottom of my list, as I said before the problem exists only after I unlocked my device, so I think that something went wrong during that process maybe boot.img file or Hboot file error that makes the graphics out of order in such a way that it didn't boot correctly,,
do you know how can I get hboot file for my device !? or at least how can I upgrade it or downgrade it to a different number !?
Click to expand...
Click to collapse
Unlocking the device can't cause power buttons problem... That's for sure!
You can't downgrade your hboot/base if you have a S-ON device.. you can only upgrade it...
what is your base? run the following command in fastboot and post the result here:
Code:
fastboot getvar version-main
vin4yak said:
Unlocking the device can't cause power buttons problem... That's for sure!
You can't downgrade your hboot/base if you have a S-ON device.. you can only upgrade it...
what is your base? run the following command in fastboot and post the result here:
Code:
fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 3.14.707.24
finished. total time: 0.006s
EngASM said:
version-main: 3.14.707.24
finished. total time: 0.006s
Click to expand...
Click to collapse
Your on the latest firmware available for your device... You can try flashing the same firmware over but I don't think it's gonna be of any help for correcting the Power Button problem...
Download: http://www.androidrevolution.nl/downloader/download.php?file=3.14.707.24.zip
vin4yak said:
Your on the latest firmware available for your device... You can try flashing the same firmware over but I don't think it's gonna be of any help for correcting the Power Button problem...
Download: http://www.androidrevolution.nl/downloader/download.php?file=3.14.707.24.zip
Click to expand...
Click to collapse
ok
so you say that it's a hardware issue for sure and there is no connection between unlocking the device and it's occurring ?!
EngASM said:
ok
so you say that it's a hardware issue for sure and there is no connection between unlocking the device and it's occurring ?!
Click to expand...
Click to collapse
Yeah! 'Unlocking bootloader' just allows you to flash custom recovery by which you can flash custom roms!
However, just to make sure, try locking the bootloader again and then try using the power button and see if it registers the click everytime?!
vin4yak said:
Yeah! 'Unlocking bootloader' just allows you to flash custom recovery by which you can flash custom roms!
However, just to make sure, try locking the bootloader again and then try using the power button and see if it registers the click everytime?!
Click to expand...
Click to collapse
Where can I get a Stock ROM compatible with my Device
EngASM said:
Where can I get a Stock ROM compatible with my Device
Click to expand...
Click to collapse
Lock your bootloader and then run this RUU : http://bugsylawson.com/files/file/1...24-radio-5120416229-release-296434-signedexe/
Run with admin privileges.
vin4yak said:
Lock your bootloader and then run this RUU : http://bugsylawson.com/files/file/1...24-radio-5120416229-release-296434-signedexe/
Run with admin privileges.
Click to expand...
Click to collapse
I'll try that and then back to you
EngASM said:
I'll try that and then back to you
Click to expand...
Click to collapse
same problem
I Noticed that the power button works correctly in the first couple hours, then after that or in another word after 2 to 3 hours it start miss-responding to presses !!
EngASM said:
same problem
I Noticed that the power button works correctly in the first couple hours, then after that or in another word after 2 to 3 hours it start miss-responding to presses !!
Click to expand...
Click to collapse
What to say m8!! You have tried different roms, kernels, locked bootloader, Hell even went full stock with RUU...
If still the problem persists, it must surely be a hardware issue!
vin4yak said:
What to say m8!! You have tried different roms, kernels, locked bootloader, Hell even went full stock with RUU...
If still the problem persists, it must surely be a hardware issue!
Click to expand...
Click to collapse
Well Now I'm trying my last shot, Install CWM10.1 and enable the volume Roker keys to wake the screen up, it works till now, needs 24 hour to be sure,
but this ROM is really a power hungry ROM
do you know anyway I can minimize battery lose when I use this ROM !?!
EngASM said:
Well Now I'm trying my last shot, Install CWM10.1 and enable the volume Roker keys to wake the screen up, it works till now, needs 24 hour to be sure,
but this ROM is really a power hungry ROM
do you know anyway I can minimize battery lose when I use this ROM !?!
Click to expand...
Click to collapse
Yes, flash XM kernel (repack) and then install trickster mod and do the following settings:
Governor : Smartmax/PMC
IO Scheduler: row/noop
CPU cap: 1.2 GHz
When you want to play games, just change governor to interactive and scheduler to row... 1.2 Ghz is more than enough to run games... If you want you can get back to 1.5 Ghz...
All this might sound a long procedure, but it's just a few clicks! and you can set this on boot, so once configured, you can forget about it!
vin4yak said:
Yes, flash XM kernel (repack) and then install trickster mod and do the following settings:
Governor : Smartmax/PMC
IO Scheduler: row/noop
CPU cap: 1.2 GHz
When you want to play games, just change governor to interactive and scheduler to row... 1.2 Ghz is more than enough to run games... If you want you can get back to 1.5 Ghz...
All this might sound a long procedure, but it's just a few clicks! and you can set this on boot, so once configured, you can forget about it!
Click to expand...
Click to collapse
I didn't understand a word [email protected]! Literally !
So me being the impatient guy that I am decided to unroot/relock my HoX. I followed this guide http://forum.xda-developers.com/showthread.php?t=1859714
I downloaded the nandroid that matched my ID, HTC_044. Restored the backup, all was fine but the ROM was rooted. Flashed stock recovery and kernel too.
I then deleted the SU files from system/app and system/bin and /xbin. Rebooted, but somehow SU was still there. So I deleted the files again and wanted to boot into stock recovery to do a wipe.
So I boot into the bootloader, tried getting into recovery. Had the red ! exclamation mark. So I flashed the recovery again and that's where the problem started. My phone is going crazy right now.
It's bootlooping at the HTC quietly brilliant screen. 2 seconds and it reboots forever. I tried forcing my way into the bootloader, but then the bootloader has a mind of it's own and bootloops as well. Whenever I manage to get into the bootloader, it boots for 2 seconds then it goes back into bootlooping.
Here's a video of everything happening. I need help! Battery is at 100% last I checked, but it's been bootlooping for 3 hours now ):
Nobody? ): My phone's been bootlooping for 7 hours now D:
ArmedandDangerous said:
Nobody? ): My phone's been bootlooping for 7 hours now D:
Click to expand...
Click to collapse
Can you carry out a fastboot command??
If yes, give the output of
fastboot getvar version-main
Sent from my HTC One X using xda app-developers app
Why fastboot getvar version-main ?
Ow good morning btw
Mr Hofs said:
Why fastboot getvar version-main ?
Ow good morning btw
Click to expand...
Click to collapse
So he can run a RUU??
Good Morning to you too!
Sent from my HTC One X using xda app-developers app
Yeah good thinking but a bootlooping device can't run a ruu because fastboot usb connection is lost at reboot, therefore no communication between phone and pc
Mr Hofs said:
Yeah good thinking but a bootlooping device can't run a ruu because fastboot usb connection is lost at reboot, therefore no communication between phone and pc
Click to expand...
Click to collapse
So what to do?
Sent from my HTC One X using xda app-developers app
Mr Hofs said:
Yeah good thinking but a bootlooping device can't run a ruu because fastboot usb connection is lost at reboot, therefore no communication between phone and pc
Click to expand...
Click to collapse
As long as I know, RUU can be run while in fastboot
The problem is that he can't stay in it more than 2 seconds... Mmm
Maybe fastboot erase cache will help.
I also have seen reports that it stopped out of its own
Difficult issue
Mr Hofs said:
Maybe fastboot erase cache will help.
I also have seen reports that it stopped out of its own
Difficult issue
Click to expand...
Click to collapse
Let's wait for him to reply....
Sent from my HTC One X using xda app-developers app
Good idea !
I've been trying to get to fastboot at the right time for erase cache to activate but it restarts too fast and fasboot hasn't fully initialized yet ):
Let it drain out, then charge the phone. Hopefully its gone by then. Its the only thing you can do now
Mr Hofs said:
Let it drain out, then charge the phone. Hopefully its gone by then. Its the only thing you can do now
Click to expand...
Click to collapse
It has drained out, but every time I plug it in it starts bootlooping again.
Then there is not much you can do
Mr Hofs said:
Then there is not much you can do
Click to expand...
Click to collapse
So it's a hard brick and there's no way to save it?
EDIT : I got lucky and managed to fastboot erase cache but it's still bootlooping. I've got the RUU ready and rom.zip extracted, but with the bootloader looping as well, I don't know what to do.
Why don't you try running the RUU?? I know the phone needs to be in connection with the PC all the time but still.. worth a try...
If you can't access bootloader on the One X, it's a hard brick!
You can try to start the ruu, hope it works. But i have my doubts.
Nothings else you can do atm, maybe somebody with more knowledge or this experience pops up !
ArmedandDangerous said:
It has drained out, but every time I plug it in it starts bootlooping again.
Click to expand...
Click to collapse
Why don’t try to open it and disconnect the battery. I think letting it drain out doesn’t mean the battery is 0% (no power).
moom999 said:
Why don’t try to open it and disconnect the battery. I think letting it drain out doesn’t mean the battery is 0% (no power).
Click to expand...
Click to collapse
He is full stock ATM and even the bootloader is relocked, he has better chance of claiming warranty via HTC and letting them fix it instead of opening it himself and trying to fix it (which I doubt would be of any help)... again there's a chance that he could damage or tear one of the cables while doing it...
@ OP
If you don't get any solution within two days, it's better you send it to HTC if you are still under warranty... If you have experience opening up the device, then go with @moom999 soln...:good:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16
ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).
Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:
ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.
Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse
It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it
ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.
Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?
Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
It now says Relocked then underneath security warning. Is that good?
ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.
Will i have to re unlock the boot-loader for the RUU.exe to work?
ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.
Yeah it says updating 0 out of 7 sending ........................
ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.
This is what comes up
It send that 1 had been sent then it said error